update charset stuck

[GoogleCodeExporter]

What steps will reproduce the problem?
1. updated last firmware
2. updated last charset
3. "UPDATE CHARSET" is showing when booting and stays there

What is the expected output? What do you see instead?
"UPDATE CHARSET" is showing when booting and stays there

What version of the product are you using? On what operating system?
19

Please provide any additional information below.

Original issue reported on code.google.com by avnerric...@gmail.com on 2 Mar 2012 at 10:41

[GoogleCodeExporter]

What FTDI cable are you using? Looks like it isn't updating the CharSet due it 
don't reset the board from cable. Please check on Windows if the com port has 
enabled the checkbox for "Set RTS on Close".

Original comment by sbeni...@gmail.com on 2 Mar 2012 at 7:33

[GoogleCodeExporter]

i am doing the reset manually.
i press the read\write\update commands in the software then immediately press 
the reset button.

it seem to work now but ive got another problem.
if i dont connect the minimOSD's TX pin to the APM (because i have the xbee) it 
won't start sending Mavlink messages.
if i connect the OSD's TX to APM even on startup it gets the data and then i 
can disconnect it and it will keep sending the data

Original comment by avnerric...@gmail.com on 2 Mar 2012 at 7:45

[GoogleCodeExporter]

So, your XBee isn't linking the APM board to a GCS properly. The GCS (or the 
OSD, by its TX) needs to request rates (what MAVLink msgs and at what 
frequency). Please, you need to test the GCS connected through two Xbees First 
without OSD.

Original comment by sbeni...@gmail.com on 3 Mar 2012 at 3:22

[GoogleCodeExporter]

That will work.

but what happens if i want the OSD to get the data when i fly without the 
ground xbee ?

i believe a quick solution will be a switch to select either OSD TX pin OR XBEE 
TX pin will be connected to APM.
that way i can switch between ground station to OSD.

while i should still be able to get the OSD data when in ground station mode 
and vice versa

Original comment by avnerric...@gmail.com on 3 Mar 2012 at 3:26

[GoogleCodeExporter]

When you fly without the Ground Xbee, you need to connect TX from OSD to APM. 
It is not a limitation of the OSD, it is a limitation of sharing the same 
serial port. Furthermore, it's a limitation of ArduCopter only. ArduPlane saves 
the previous requested rates, so that problem don't affects it.
Anyway, your idea about adding a switch between them is interesting hacking, 
though it can't be switched in flight without extra hardware and a free rc 
channel.

Original comment by sbeni...@gmail.com on 3 Mar 2012 at 3:49

• Changed state: Fixed