bubbarives / minimosd-extra

Automatically exported from code.google.com/p/minimosd-extra
0 stars 0 forks source link

no mav data solution #121

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
for all people who have the no mav data issue:

you have to disable either BRD_SER1_RTSCTS or BRD_SER2_RTSCTS by setting it to 
0 (or maybe both). i had this problem a year ago already and it drove me almost 
crazy back then. still amazed that so many people have that issue as it doesn't 
seem to be properly documented. somebody maybe add this into this wiki under 
apm settings?

see this link for more info: 
http://ardupilot.com/forum/viewtopic.php?f=72&t=8321 stefang advises against 
disabling it but it's the only solution that worked for me. let me know if 
you're still having issues with it...

also make sure you have disabled the "apm-reset" option disabled under 
config/tuning under planner before you set the sr1 or sr2 params, otherwise 
mission planner will reset them next time you connect

Original issue reported on code.google.com by md86.cha...@gmail.com on 23 Feb 2015 at 4:35

GoogleCodeExporter commented 8 years ago
Yes there is somthing wrong with the APM latest software as it is telling me 
that it is trying to change parameters that are not there? eg,SR3 parameters 
when it lists SR1 parameters.I know that SR1 and SR3 are the same but it seems 
the APM isn't aware of this!.I'm trying to load some older software but this 
often means Mavlink 0.9 protacol so I'll go back on the Minim-Extra OSD 
software as well and see if this makes any difference.I'll report back if it 
solve's the issue of no mavlink data coming out of apm 2.6 with telem connected.

Original comment by jca...@yahoo.com.au on 15 Mar 2015 at 4:46

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
What do we do if we get this error but we don't have PixHawk, but APM instead? 
(thus we don't have BRD_SER1_RTSCTS or BRD_SER2_RTSCTS to disable)? I have 
tried MinimOsd_Extra_Copter_R800 as well.  I can't get this error message to go 
away. 

Original comment by Darre...@gmail.com on 8 May 2015 at 9:40

GoogleCodeExporter commented 8 years ago
I had the same problem when trying to use the arducam extra software yesterday. 
 I had it connected to Telem 2 on a Pixhawk with arducopter 3.2.1.  I was 
unable to get anything other than No Mav data with the recent firmware images 
(r719 and newer) up to r800.  Throughout this process the yellow heartbeat LED 
would blink when connected to the pixhawk which makes me think it's some sort 
of software issue.  As soon as I downgraded back to the regular MinimOSD 
firmware (v2 stable) it worked fine.  I tried with all combinations of the 
RTSCTS values set, and none of them made any difference.

Original comment by rearden...@gmail.com on 10 May 2015 at 11:44

GoogleCodeExporter commented 8 years ago
Same issue as #4. I have 3 Pixhawk with Firmware 3.2.1 and they only work with 
MinimOSD V2 stable and MinimOSD V2.2 Copter. Connected to Pixhawk: no mav data. 
On the only APM with Firmware 3.2.1: Minim-Extra-R800-Copter works perfect. Is 
there any idea? RTSCTS changes does not made a difference. 

Original comment by jolan...@gmail.com on 14 May 2015 at 3:41

GoogleCodeExporter commented 8 years ago
To get MAV data with Pixhawk you have to apply the settings called out for SR1 
here https://code.google.com/p/minimosd-extra/wiki/APM to SR2 in order to get 
the telemetry 2 channel to send data to the Minim OSD. So now I finally have 
the latest Minim-Extra-R800-Copter working perfectly with my Pixhawk on telem 
port #2.

Original comment by tme...@gmail.com on 15 Jul 2015 at 5:40