EOSBandi wrote:did you wait about 10 minute to let sensors cool down ?
nope... i think at -15 no need to wait for 10 min. They cool quickly. Well maybe im wrong.... I will test again!! Thanks
RTH and poshold works well.
EOSBandi wrote:did you wait about 10 minute to let sensors cool down ?
leocopter wrote:I tried to compile -navi-b5-baro_fix for a Mini MWC FC and got "wp_distance was not declared in this scope". Looking at the code, the problem seems to be that I am selecting #define I2C_GPS (needed with this FC). Is there any way around this ?
kenpappas wrote:Will we get this working with the MW SE that has the ATMega 328P Microcontroller?
1.) Is my board I2c and therefore not compatible?
2.) For configuration, do I just make the same changes in the NAVI Config.h that I made to MW v2.3?
*** It enables you to upload specific settings / firmware for MW use at 57600 baud3.) I see in the thread that there is a 3DR Config program. I have downloaded this but.......
3.1.) What does this do?
*** YES3.2.) Do I need it?
*** Here: https://mw-wingui.googlecode.com/files/Sik-mw-2.3.zip3.3.) Where do I get it from?
*** No.3.4.) In the 3DR Config program and in the thread, there is mention that you can upload firmware.
3.4.1.) Does this mean that I can upload MultiWii firmware to my CRIUS board via 3DR rather than via USB?
*** No, connect using your USB, wired connection.5.) I want to make sure that I do not loose any of my hard earned settings in MW2.3. Therefore is the correct/safe procedure of uploading the NAVI firmware and retaining me flight settings as follows?
5.1.) In WIN_GUI 2.3 r8,
5.1.1.) Connect to the CRIUS board via 3dr or Bluetooth.
5.1.2.) Ensure that PIDS, AUX and other settings are present
5.1.3.) Hit "Save File"
5.1.4.) Save the file to a known location like Desktop
5.1.5.) Disconnect from the CRIUS board.
*** Then load your saved settings back onto your board...6.) Make the necessary changes to the Config.h file within the NAVI b5 Baro Fix code (latest) Ivia Arduino
7.) Compile the code to ensure no errors
8.) Upload the firmware to the board
9.) Re-start WIN_GUI
9.1.) Connect to the CRIUS board
YesDo I still need to run 3DRRadio.exe) and load the radio~hm_trp.ihxfirmware?
You will find it in the downloads list on Googlecode page for WinGui. Sik-mw-2.3.zip https://code.google.com/p/mw-wingui/downloads/listI mentioned that I already had 3DRRadio.exe) but I thought it was in the zip file. Where do I get this from cause a Google search has not found it!
Not necessary.Also, I already have the 3dr air module connected, do I need to disconnect it before I go through this procedure?
Jimbo385 wrote:Right, next issue!
I am now trying to update the config.h file in the Navi b5 Baro Fix Sketch.
When I either double click the Multiwii file or select it within Arduino, I get the following error message
The file "MultiWii.ino" needs to be inside a sketch folder named "MultiWii". Create this folder, move the file, and continue?
If I click "Cancel" Arduino stops.
If I click "OK", the folder is created and ARDUINO loads the MultiWii.ino file only! All other files are missing!
-ralf- wrote:You need to update the air-module too ....
-ralf- wrote:Move all files to a subfolder named MultiWii ...
Jimbo385 wrote:-ralf- wrote:You need to update the air-module too ....
How do I do this as it's not mentioned anywhere?
Jimbo385 wrote:-ralf- wrote:Move all files to a subfolder named MultiWii ...
This worked. Thanks.
I've never had to do that before though!
EOSBandi wrote:There are no significant changes in the code since last release. Mostly preparation for integration to _shared. So if you have time, it's perfectly fine to test with B5. IF you can do, please test the autoland, it is important that this function works perfectly.
I'll putting together a site to deliver new releases, since google disabled the file upload function in google-code.
-ralf- wrote:EOSBandi wrote:There are no significant changes in the code since last release. Mostly preparation for integration to _shared. So if you have time, it's perfectly fine to test with B5. IF you can do, please test the autoland, it is important that this function works perfectly.
I'll putting together a site to deliver new releases, since google disabled the file upload function in google-code.
I`d like to have the EXTENDED_AUX_STATES of r97 ..... I only have VS-Express 2010 so I cannot compile myself.
EOSBandi wrote:-ralf- wrote:EOSBandi wrote:There are no significant changes in the code since last release. Mostly preparation for integration to _shared. So if you have time, it's perfectly fine to test with B5. IF you can do, please test the autoland, it is important that this function works perfectly.
I'll putting together a site to deliver new releases, since google disabled the file upload function in google-code.
I`d like to have the EXTENDED_AUX_STATES of r97 ..... I only have VS-Express 2010 so I cannot compile myself.
OK, I'll put up a snapshot this evening, but be warned ! I did not had time to flight test the EXTENDED_AUX_STATES yet, so be careful.
Perry wrote:I've tested the autoland function indoor, and here it seems don't work.
It's necessary to be outdoor?
While you're doing a mission?
Is it not possible to test the autoland function indoor?
Thanks
Perry
-ralf- wrote:Is it necessary to erase the EEPROM by uploading the EEPROM_CLEAR-sketch?
-ralf- wrote:At initial startup of the gui all default directories are set to c:\windows\system32.
Changing the directories to sub-directories of WinGUI hasn't any effect. Error Message is
the same .... gui_settings.xml is searched in system32.
-ralf- wrote:And what will happen when the ground level at landing zone is higher
than at starting point?