Comment by vilnis.lauva on June 25, 2012 at 10:05am

Ok, tested new firmware, something is not right. I got all zeros (GPS, altitude etc). Only thing that shows up is flight mode. It changes when I switch radio, so connections is right. I use latest 2.40 version and APM1.

Also ADC does't work right. ADC shoved some 495, I tried to input voltage (which vas 7.65), first, it allows only integer, but then it shoved on osd 0.02v, if I inputed 765 in Value 1, than voltage shoved  0.20V.

Comment by Dario Lindo Andres on June 27, 2012 at 4:28am

Hi!

New ConfigTool.exe does not work for me. Open file makes an error and program goes down.

I have tried it on two machines, one with Windows 7 x32 and the other with Windows 7 x64, on both PCs occurs the same.

 

Regards from Spain,

Dario.

Moderator Comment by Graham Dyer on June 27, 2012 at 5:01am

Confirmed, crashes for me too, Win 7 x32

Comment by JohnB on June 28, 2012 at 10:20am

I'm getting all zeros here.  Didn't check the flight mode, but I'll check tonight.

Comment by kolin on June 28, 2012 at 2:28pm

Hi!

I have crashes too. So I downloaded source code, open it in Visual Studio and tried to run in debug. It shows error on one line. I has to do something with CheckedListBox component. I commented that line out :-O and crippled version of utility was running. I was able to upload hex file to OSD and upload charset (after I clicked to continue after runtime error :) ). Then I connected Remzibi to APM and it is working!!!!! I'm not able to change layout, but I don't care, default one is OK for me.

Working well with APM1, Arduplane 2.40 mavlink1.0

You could probably be able to upload new firmware with older config tool, but I have not tried.

Comment by JohnB on June 28, 2012 at 3:43pm

I re-flashing the character set.  The good news is that it fixed the 'all zeroes' problem.  The bad news is that I still have to 'reset' the minimOSD on each powerup to get it past the 'character set' issue.  I think this last issue is known and is being worked on.

Yay.. finally have a working minimOSD!!

Comment by Dario Lindo Andres on June 29, 2012 at 8:00am

Hello everyone,

 

New minor bug:

Satcount is not working with MAVLINK 1.0.

Satcount shows satellites used by aircraft´s GPS. In APM Planner I can see them, so I think the problem concerns with Mavlinks statements (see below).

 

Taking from git/ Tools/ ArdupilotMegaPlanner/ CurrentState.cs:

In Mavlink 0.9 satcount refers to MAVLINK_MSG_ID_GPS_STATUS

But in Mavlink 1.0, satcount is present in MAVLINK_MSG_ID_GPS_RAW_INT If you include satcount in this statement, satcount must work.

So, in svn/ trunk/ OSD/ src/ MavlinkClient.cpp, line 158:

 #else        

case MAVLINK_MSG_ID_GPS_RAW_INT:        

{            

osd_lat = mavlink_msg_gps_raw_int_get_lat(msg)/10000000;            

osd_lon = mavlink_msg_gps_raw_int_get_lon(msg)/10000000;            

//osd_alt = mavlink_msg_gps_raw_get_alt(&msg);            

osd_fix_type = mavlink_msg_gps_raw_int_get_fix_type(msg);        

}        

break;

#endif

MUST BE:

#else        

case MAVLINK_MSG_ID_GPS_RAW_INT:        

{            

osd_lat = mavlink_msg_gps_raw_int_get_lat(msg)/10000000;            

osd_lon = mavlink_msg_gps_raw_int_get_lon(msg)/10000000;            

//osd_alt = mavlink_msg_gps_raw_get_alt(&msg);            

osd_fix_type = mavlink_msg_gps_raw_int_get_fix_type(msg);

osd_satellites_visible = mavlink_msg_gps_raw_int_get_satellites_visible(msg);  // Included here for MAVLINK 1.0     

}        

break;

 

Thanks for your effort Hazy!

Regards from Spain,

Dario.

Comment by kolin on July 2, 2012 at 12:13pm

Dario thanks for that fix, will apply it soon. My only problems for now are not showing of coordinates after decimal point and home location isn't right. Probably same cause, probably with transition to Mavlink 1.0

Same issue anyone?

Is source for compilation with WinAVR, right?

Comment by Dario Lindo Andres on July 2, 2012 at 2:29pm

Hi kolin!

I couldn't test the code yet because I'm still in college examinations.

I'll check the code concerning Mavlink to see if your problem may be due to a syntax error between versions 0.9 and 1.0.

I do not know how to compile the code to generate a .hex file. It would be great for me to know how to compile the code for help to debugging.

I can understand about 80% of the code (thanks to Arduino and c++), but nothing about compile (just Arduino IDE).

Last exam tomorrow... summer begins for me and I can start trying new things.

Greetings from Spain,

Dario.

Comment by hazy on July 3, 2012 at 6:42am

Hi, everyone. Thank you for you patience and helpful comments. I have fixed some issues. Please download the new firmware and config tools.

To Dario, the firmware is generated by using the "make" tool in WinAVR. Please add the "bin" and "utils\bin" directories under WinAVR to the executable path, and run "make" command in the "OSD" directory (i.e. where the "Makefile" is placed).

Comment

• ‹ Previous
• 1
• …
• 3
• 4
• 5
• 6
• 7
• …
• 10
• Next ›
• Page