Jump to content


AeroSimRC: new model simulator supported by OpenPilot HiTL


  • Please log in to reply
73 replies to this topic

#21 metRo_

metRo_

    Key Member

  • Members
  • PipPipPip
  • 610 posts
  • LocationAmarante (Porto)
  • Country: flag of Portugal Portugal


Posted 26 April 2012 - 11:18 PM

I'm getting errors trying to compile the plugin:



C:\Users\ze\Downloads\hhrhhr-Aerosim-plugin-for-CopterControl-6629a25>qmake

C:\Users\ze\Downloads\hhrhhr-Aerosim-plugin-for-CopterControl-6629a25>mingw32-ma
ke
cd src/ && c:/QtSDK/Desktop/Qt/4.8.0/mingw/bin/qmake.exe c:/Users/ze/Downloads/h
hrhhr-Aerosim-plugin-for-CopterControl-6629a25/src/plugin.pro -o Makefile.plugin

cd src/ && mingw32-make -f Makefile.plugin
mingw32-make[1]: Entering directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin
-for-CopterControl-6629a25/src'
c:/QtSDK/mingw/bin/mingw32-make -f Makefile.plugin.Debug
mingw32-make[2]: Entering directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin
-for-CopterControl-6629a25/src'
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_S
SE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I'c:/QtSDK/Desktop/Qt/4.
8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtNetwork'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/default' -
o debug/qdebughandler.o qdebughandler.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_S
SE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I'c:/QtSDK/Desktop/Qt/4.
8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtNetwork'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/default' -
o debug/plugin.o plugin.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_S
SE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I'c:/QtSDK/Desktop/Qt/4.
8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtNetwork'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/default' -
o debug/udpconnect.o udpconnect.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_S
SE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I'c:/QtSDK/Desktop/Qt/4.
8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtNetwork'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/default' -
o debug/settings.o settings.cpp
g++ -mthreads -shared -Wl,--out-implib,debug/libplugin_AeroSIMRC.a -o debug/plug
in_AeroSIMRC.dll debug/qdebughandler.o debug/plugin.o debug/udpconnect.o debug/s
ettings.o -L'c:/QtSDK/Desktop/Qt/4.8.0/mingw/lib' -lQtNetworkd4 -lQtCored4
Creating library file: debug/libplugin_AeroSIMRC.a
cp "debug/plugin_AeroSIMRC.dll" ../CopterControl
mingw32-make[2]: Leaving directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin-
for-CopterControl-6629a25/src'
mingw32-make[1]: Leaving directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin-
for-CopterControl-6629a25/src'
cd src/ && c:/QtSDK/Desktop/Qt/4.8.0/mingw/bin/qmake.exe c:/Users/ze/Downloads/h
hrhhr-Aerosim-plugin-for-CopterControl-6629a25/src/tools.pro -o Makefile.tools
cd src/ && mingw32-make -f Makefile.tools
mingw32-make[1]: Entering directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin
-for-CopterControl-6629a25/src'
c:/QtSDK/mingw/bin/mingw32-make -f Makefile.tools.Debug
mingw32-make[2]: Entering directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin
-for-CopterControl-6629a25/src'
c:/QtSDK/Desktop/Qt/4.8.0/mingw/bin/uic.exe udptestwidget.ui -o ui_udptestwidget
.h
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNO
W -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_Q
MAIN -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4
.8.0/mingw/include/QtNetwork' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtGui'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'.' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/defa
ult' -o debug/udptestmain.o udptestmain.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNO
W -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_Q
MAIN -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4
.8.0/mingw/include/QtNetwork' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtGui'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'.' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/defa
ult' -o debug/udptestwidget.o udptestwidget.cpp
C:/QtSDK/Desktop/Qt/4.8.0/mingw/bin/moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DQ
T_DLL -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW
-DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_QMA
IN -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4.8
.0/mingw/include/QtNetwork' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtGui' -I
'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/inc
lude/ActiveQt' -I'debug' -I'.' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/defaul
t' -D__GNUC__ -DWIN32 udptestwidget.h -o debug/moc_udptestwidget.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -
DQT_DLL -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNO
W -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_Q
MAIN -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtCore' -I'c:/QtSDK/Desktop/Qt/4
.8.0/mingw/include/QtNetwork' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include/QtGui'
-I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/include' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/i
nclude/ActiveQt' -I'debug' -I'.' -I'c:/QtSDK/Desktop/Qt/4.8.0/mingw/mkspecs/defa
ult' -o debug/moc_udptestwidget.o debug/moc_udptestwidget.cpp
g++ -mthreads -Wl,-subsystem,windows -o ../tools/udp_test.exe debug/udptestmain.
o debug/udptestwidget.o debug/moc_udptestwidget.o -L'c:/QtSDK/Desktop/Qt/4.8.0/
mingw/lib' -lmingw32 -lqtmaind -lQtGuid4 -lQtNetworkd4 -lQtCored4
mingw32-make[2]: Leaving directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin-
for-CopterControl-6629a25/src'
mingw32-make[1]: Leaving directory `c:/Users/ze/Downloads/hhrhhr-Aerosim-plugin-
for-CopterControl-6629a25/src'
c:/QtSDK/Desktop/Qt/4.8.0/mingw/bin/qmake.exe c:/Users/ze/Downloads/hhrhhr-Aeros
im-plugin-for-CopterControl-6629a25/copydata.pri -o Makefile.copydata
mingw32-make -f Makefile.copydata
mingw32-make[1]: Entering directory `C:/Users/ze/Downloads/hhrhhr-Aerosim-plugin
-for-CopterControl-6629a25'
cp -r C:\Users\ze\Downloads\hhrhhr-Aerosim-plugin-for-CopterControl-6629a25\shar
e\cc_off.tga C:\Users\ze\Downloads\hhrhhr-Aerosim-plugin-for-CopterControl-6629a
25\CopterControl\
cp: cannot create regular file `C:\\Users\\ze\\Downloads\\hhrhhr-Aerosim-plugin-
for-CopterControl-6629a25\\CopterControl /C:\\Users\\ze\\Downloads\\hhrhhr-Aeros
im-plugin-for-CopterControl-6629a25\\share\\cc_off.tga': No such file or directo
ry
mingw32-make[1]: *** [FORCE] Error 1
mingw32-make[1]: Leaving directory `C:/Users/ze/Downloads/hhrhhr-Aerosim-plugin-
for-CopterControl-6629a25'
mingw32-make: *** [sub-copydata-pri-make_default-ordered] Error 2

C:\Users\ze\Downloads\hhrhhr-Aerosim-plugin-for-CopterControl-6629a25>


Feel free to correct my english, you can post or pm me, thanks :)

#22 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 28 April 2012 - 08:06 AM

  • qmake
  • make release
Then:
  • copy by hand all files from the share subdirectory into the CopterControl subdirectory (this step fails, patches are welcome)
  • copy or move whole CopterControl subdirectory into AeroSIM-RC/Plugin subdirectory
  • copy files QtCore4.dll, QtNetwork4.dll, libgcc_s_dw2-1.dll, mingwm10.dll into the AeroSIM-RC directory
Run simulator and choose CopterControl from the Plugin menu.

#23 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 28 April 2012 - 09:56 AM

Here is a translation of plugin manual from original Russian post.

GCS plugin settings.

You should configure HITL Simulation (v2) in the GCS:

Attached File  HITLv2.png   74.25KB   107 downloads

Local and remote IP and ports: used for UDP communication with the plugin running on the AeroSimRC machine. Values shown could be used for running them on the same computer. But you also can run AeroSimRC with plugin on one PC and GCS on another.

Executable and data paths: not used.

Attitude data: defines data which could be used by the CC hardware.
  • AttitudeRaw: should be checked. You may uncheck them only if you want to see other data without real CC hardware connected. Refreshe rate is not currently used.
  • AtittudeActual: there are 3 choices:
    - send raw data: not recommended. It could be used to send raw gyro/accel to the CC. Then CC uses them to calculate the attitude. The update rate is set by the AeroSimRC. It probably sholdn't be more than 60Hz (using vsync option in the sim). Otherwise it can be as high as 200+ Hz, and current GCS implementation can hang on not so fast machine. GCS needs to be improved to handle higher update rates, but you can try for yourself.
    - use values from simulator (default): data is calculated using simulator-provided rotation matrix and free from noise.
    - calculate from AttitudeRaw: uses the same code as original CC attitude module. The difference is that it integrates using simulator-provided time step and not internal CC timer. This adds some precision.

    As a note, it is recommended to start using the 2nd option. Then if you want to play, say, with guidance, you may enable the 3rd one. Then you'll see yaw drift, etc. The 1st option could be used as well, but since sim can provide max 300Hz update rate, the accuracy could be lesser than with real CC which runs it at 500+ Hz.
HomeLocation: fill the object with launch GPS position coordinates, 0sec refresh rate means "set the position just once after plugin start", any other value will update it accordingly,

GPSPosition: provides data for GPS location, altitude, ground speed, course. Satellites count is set to 8, PDOP to 3, GeoidSeparation to 0. 200msec corresponds to 5Hz GPS data update rate.

SonarAltitude: provides sonar data if enabled. Not currently supported by the CC firmware.

Map command from simulator: mapped to GCSReceiver object. This means that any sim-provided controls will be mapped to the GCSReceiver object. It can be configured now in the CC to be used for controls. Note that you do not have to use GCSReceiver and can use any of available receivers on the CC including multi-receiver feature.

But please note that if you use sim in windowed mode, and use USB-connected joystick to control it, and switch from sim to the GCS window, the latter will catch the joystick. The manual control GCS plugin needs some rework to prevent this behavior. Now you can't disable GCSControl module, you only can remove the DLL to stop this behavior.

#24 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 28 April 2012 - 10:02 AM

Sample 4-channel fixed wing configuration for AeroSimRC

It is similar to the real model configuration (arrows show important details).

There is no reason to set servo update rate more than 60Hz.
Pitch should be inverted from both sides.
The 5th channel is Flight Mode switch controlled by Plugin channel 1 (keys U, J, M for 3-pos switch).
The 7th input is manual FPV camera pitch control. The 6th output channel is camera servo for the same axis.

Attached Files



#25 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 28 April 2012 - 12:46 PM

Plugin configuration file example

Spoiler


Only few comments (patches and fixes for English are welcome to the author of plugin):

General - common settings, including IP and ports.

Input - here 10 input channels from the CC board are mapped to internal AeroSimRC channels (servo or ESC). Most planes in the sim are 4-channel, but there are few exceptions like Extra with separated elevator. If some channel is empty or commented out, the channel value in that case always will be 0.0.
  • send_to defines where to send all the channel data. RX means the values are for servo or ESC directly, w/o any sim mixers. TX - the controls will replace internal simulator controller. It makes sense only if you use external for sim control source (like the CC board).
Output - you can choose up to 8 channels to send to the CC. They could be sim joystick, flight mode, camera control, etc. For unmapped channels the value will be -1.0.
  • take_from option is similar to the send_to. TX sends raw controls, RX - after mixers. The values are put into the GCSReceiver object and can be used in the CC.
Video section allows to define some number of window sizes and positions. Sim can be run in full screen mode and also in windowed mode. After you define some resolutions here, you can cycle through them using plugin menu from the sim. Positions are screen-based with absolute coordinates, so you may place the sim window over the GCS to take nice demo videos :)


Important notes

Currently you may need to remove all Linear widgets, disable smooth options for other widgets and in general keep as few of widgets as possible. 60Hz data stream can hang the GCS easily. Sometimes you may revive it clicking the ON/OFF button on the plugin CC image, it stops the network. The GCS needs to be reworked to improve such behavior.

Also you may need to set the vsync video option in the sim configuration. It looks like sim sends data with the frame rate, and w/o vsync it could be 200+ Hz, see above.

#26 Kenn Sebesta

Kenn Sebesta

    Banned

  • Banned
  • PipPipPip
  • 2788 posts
  • Country: flag of Luxembourg Luxembourg


Posted 02 May 2012 - 07:23 PM

Hey, it works! Just a couple extra things that weren't mentioned.

1) Compiling the GCS on Windows with Qt 4.8.1 failed, because make was looking in the wrong spot to copy libgcc_s_dw2-1.dll and mingwm10.dll. I don't know why this is the case.
2)The GCS in hhrhhr's examples is an older version, and is not visually the same on the stab tab as the GCS compiled from hhrhhr's gitbranch. This has only a visual effect.
3) It is also necessary to enter "Edit Gadgets Mode" and load the HiTL Simulation (v2) gadget, and then to click "Start".
4) Lastly, for those who do not know, "GCS Control" and "Armed" need to be checked (look on the HiTL tab, right above the virtual control gimbals.)

Attached Files



#27 Kenn Sebesta

Kenn Sebesta

    Banned

  • Banned
  • PipPipPip
  • 2788 posts
  • Country: flag of Luxembourg Luxembourg


Posted 10 May 2012 - 01:25 AM

This is weird. I'm not quite sure I understand where the GCS jitter is coming from in this video:


View on Vimeo

Notice that I have GCS Control on. What you don't see is that I have no input to the GCS right now, as AeroSimRC is not running and the USB TX-->PC dongle is not installed. This jitter makes flying with AeroSimRC very difficult, because I'll be flying along and all of a sudden the jitter just drives my control inputs crazy.

#28 hhrhhr

hhrhhr

    Advanced Member

  • Members
  • PipPipPip
  • 229 posts
  • LocationVeliky Novgorod
  • Country: flag of Russian Federation Russian Federation


Posted 10 May 2012 - 12:14 PM

maybe throttle neutral is very high???
Attached File  Clipboard01.jpg   3.56KB   21 downloads

have GCS Control on

you don't need this if you use ASim dongle or your transmitter as input.

#29 Kenn Sebesta

Kenn Sebesta

    Banned

  • Banned
  • PipPipPip
  • 2788 posts
  • Country: flag of Luxembourg Luxembourg


Posted 10 May 2012 - 12:24 PM

maybe throttle neutral is very high???
Attached File  Clipboard01.jpg   3.56KB   21 downloads


Neat idea but:

1) that shouldn't provoke the jitter, should it? In fact, having the neutral throttle high should reduce the stick jitter, since it increases the amount of resolution between -1 and 0.
2) I see this same behavior on the aileron axis, I just didn't capture it in this video. It's all intermittent, confoundingly.

you don't need this if you use ASim dongle or your transmitter as input.



#30 hhrhhr

hhrhhr

    Advanced Member

  • Members
  • PipPipPip
  • 229 posts
  • LocationVeliky Novgorod
  • Country: flag of Russian Federation Russian Federation


Posted 10 May 2012 - 12:46 PM

try this:
throttle input 1000-2000, neutral 1050
throttle output 1000-2000, neutral 1050
do not enable GCS Control and it is better just to disable this plugin (that the GCS does not intercept the command from dongle when it receives focus)

#31 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 28 May 2012 - 07:59 PM

os/AeroSimRC branch is now based on current next and works with AeroSimRC. But only tested with CopterControl, I think it won't work with CC3D due to sensor handling differences (I found that with CopterControl as well but was able to fix that for CopterControl only since have nothing else).

It still is a bit unfinished: a lot of checks in the GCS code are missing - as in other GCS plugins. Say, if you don't edit the HITLv2 configuration - GCS will crash. You also need to disable many GCS widgets. This could be fixed by interested parties. I have sample CopterControl, GCS and AeroSimRC configs which work for Manual, Attitude and AxisLock modes for a fixed wing. But didn't commit them (not sure if that's the right place for that).

Also it could be interesting only for navigation due to high processing delays in the current GCS code.

#32 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 28 May 2012 - 08:12 PM

Attached are my settings for GCS, CopterControl, AeroSimRC (rename cc_plugin.ini.txt to cc_plugin.ini).

You don't need GCS control checkbox checked if you control the system using AeroSimRC controllers (USB, joystick or keyboard). It uses GCS Receiver to send controls from the sim to OP board.

Don't remember that you can switch flight modes using plugin channel 1, mapped by default to U-J-M keys for low-mid-high values (thus 3 flight modes).

Attached Files



#33 Jose Angel

Jose Angel

    Team Iberian Lynxes (TIL)

  • Members
  • PipPipPip
  • 298 posts
  • LocationMadrid
  • Country: flag of Spain Spain


Posted 07 July 2012 - 11:11 AM

Does this work with the aerosimrc demo version (without the usb dongle)?

I would like to give it a try before purchasing...

#34 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 07 July 2012 - 02:21 PM

Yes it does with the latest version, but you can fly only 2 minutes of flight time. Then you have to restart AeroSimRC for another 2 minutes.

Also please note that configs above (at least, one for the CopterControl) are obsolete now due to changes in UAVobjects. I will try latest cc guidance branch with new config which I've got from Astron yesterday. He's reported that it works. But please check the free RAM on CopterControl, it seems to be the limiting factor. I have to disable USB telemetry when enabled serial one, etc.

#35 metRo_

metRo_

    Key Member

  • Members
  • PipPipPip
  • 610 posts
  • LocationAmarante (Porto)
  • Country: flag of Portugal Portugal


Posted 15 July 2012 - 06:59 PM

Yes it does with the latest version, but you can fly only 2 minutes of flight time. Then you have to restart AeroSimRC for another 2 minutes.


But we can control the quad with the controller connected to CopterControl or we need to use the keyboard in the demo version?
Feel free to correct my english, you can post or pm me, thanks :)

#36 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 15 July 2012 - 08:19 PM

Demo is fully functional. You can control using keyboard, mouse, AeroSimRC own controller, any system joystick and also (if configured properly) using CopterControl.
The limitation is flight time 2 minutes.

But I think that for manual control purpose CopterControl is not the best option, because whole path has significant delay. It is best for navigation, but results can vary.

#37 metRo_

metRo_

    Key Member

  • Members
  • PipPipPip
  • 610 posts
  • LocationAmarante (Porto)
  • Country: flag of Portugal Portugal


Posted 18 July 2012 - 10:59 PM

os/AeroSimRC branch is now based on current next and works with AeroSimRC. But only tested with CopterControl, I think it won't work with CC3D due to sensor handling differences (I found that with CopterControl as well but was able to fix that for CopterControl only since have nothing else).


Should I download the plugin from https://github.com/h...r-CopterControl or can I use openpilot git? If I can use the openpilot git where should I look for the plugin?

Thanks
Feel free to correct my english, you can post or pm me, thanks :)

#38 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 19 July 2012 - 08:07 AM

The plugin sources still aren't in the OP repository.
I am adding them right now (this will take some time), but you should use github sources until there are here.

#39 arachnida

arachnida

    Key Member

  • Members
  • PipPipPip
  • 542 posts
  • LocationBrecht
  • Country: flag of Belgium Belgium


Posted 19 July 2012 - 08:45 AM

Gee, I don't understand this. I'm not a programmer, so please excuse me If I ask a stupid question. :huh:

Where can I find the plugin_AeroSIMRC.dll or the .plg file? Do I really need to compile the source code or can I just dowload it somewhere? Compiling is not really my thing.

#40 Guest_osnwt_*

Guest_osnwt_*
  • Guests

Posted 19 July 2012 - 09:09 AM

Yes, currently the AeroSimRC plugin (proxy to relay sim data to GCS HITLv2 plugin) is not included into the distribution - nobody asked :)

The system works like this:

AeroSimRC - SimPlugin (proxy) - local network (or the same PC) - HITLv2 GCS plugin - GCS - USB - CopterControl


Blue GCS plugin is a part of GCS and is included into the distribution.
Green proxy DLL is a simulator plugin, it is for Windows only and it is not yet included into the distribution. And the source is currently on GitHub only (not OP repository).

This is so because the AeroSimRC was expected to be mostly the development tool for navigation. And every developer can build it from source. But because many users ask how to play with it, I think we will integrate the proxy source into the main GCS tree (what I am doing right now), and include it into the Windows distribution (what I'm going to do as well).