changes to SR3_* stream rate params and OSD support

[Andrew Tridgell]

Hi All,

I've just pushed patches to enable uartD in rover/plane/copter. This
enables the secondary telemetry port on Pixhawk, and also allows for a
secondary telemetry port on PX4 and SITL.

The patches include some parameter changes, so may require some mods in
MissionPlanner and other GCS implementations. Specifically:

the SR3_* parameters are now SR1_*

there are additional SR2_* parameters for boards that have a secondary
telemetry port

the SR0_* parameters are unchanged

the SERIAL3_BAUD parameter is now named SERIAL1_BAUD.

there is a new SERIAL3_BAUD parameter on boards with a secondary
telemetry port

the SERIAL0_BAUD parameter on rover and plane is unchanged

The aim of the changes it to make it easier to setup an OSD system
properly on PX4 and Pixhawk, and to make it easier to connect an onboard
computer via MAVLink to the second telemetry port.

On a Pixhawk there are two 6 pin DF13 serial ports marked as
"telemetry". One is "telemetry 1" and the other is "telemetry 2". You
should use "telemetry 1" for higher power devices (up to 1A), such as
the RFD900 radio. Both ports will be active for communcation.

On a PX4v1 you can enable the second telemetry port by create a file
called "uartD.en" in the APM directory on your SD card. That will change
the 5 pin DF13 connector on the corner of the board from being 4 PWM
outputs to being a second telemetry port.

I'd also like to point out something that people may not realise about
using OSD devices on ArduCopter. As you may know, ArduCopter defaults
the telemetry rates to zero to try to keep CPU loads down. If you change
the rates via the REQUEST_DATA_STREAM MAVLink message then ArduCopter
doesn't save those rate changes. It will however save the rate changes
if you change the SR1_* and SR2_* parameters directly in the advanced
parameter list.

This makes it possible to setup for OSD usage by using the advanced
parameter list to enable the right messages on the port used for
OSD. Those values will then persist over reboots.

Cheers, Tridge

PS: I think we need a common-telemetry-ports page in the wiki!

[Randy Mackay]

     Attached is a screen shot of the Mission Planner page that directly sets the SR3_ parameters at the moment to force the telemetry updates for the MinimOSD so that it gets data even if a radio is not attached.  This is the page that will need to be modified to update the SR1_ parameters instead once we're closer to the AC3.2 release.

     Here's the mission planner issue for this request: https://github.com/diydrones/MissionPlanner/issues/247


-Randy

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discuss+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Gary McCray]

Hi Tridge,

As to PS - Me too, Ill see if I can get started tomorrow, but you will probably hear back from me.

Best Regards,

Gary

[criro1999]

Well, I did also have issues with OSD after update to rc7.

When I did connect the minimOSD (power), I did press "Enable telemetry" in MP button and after some seconds I did have a en error message, like "OSD... failed...", never see this message before.

What is strange is that the "modes" on MissionPlanner were not more displayed and not voice (Mode changed to...) also when OSD was connected. 

Then I did try the throttle failsafe. Before connecting the OSD, when Tx was off, throttle failsafe did trigger and it was OK, Failsafe message was on HUD.

After that, being sure throttle failsafe was tested OK before, I did power again OSD and I did test again throttle failsafe in air. This time, with OSD connected, throttle failsafe was not more triggered and quad felt to ground, instead of failsafe and RTL.

Please provide more details what exaclty need to be change in parameters to have the OSD working again as before (at least in rc2 abd before was OK),

That MP button "Enable telemetry" is not enough for me and I did get that error.

When I disconnect OSD, modes and voice fro mode are OK. But I am flying FPV and OSD is important for me.

[Randy Mackay]

Criro, It's hard to imagine how these changes which also aren't in -rc7 could be related to the failsafe issue. If you have logs we can take a look but to save me some time it would be good if you could do a bench test to ensure your failsafe works according to the wiki. -Randy Sent from Yahoo! Mail on Android

---

From: criro1999 <crir...@gmail.com>;
To: <drones-...@googlegroups.com>;
Cc: mic...@oborne.me <mic...@oborne.me>; Randy Mackay <rmac...@yahoo.com>;
Subject: Re: [drones-discuss] changes to SR3_* stream rate params and OSD support
Sent: Fri, Nov 29, 2013 10:30:51 PM

To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.

[Randy Mackay]

Criro, It's hard to imagine how these changes which also aren't in -rc7 could be related to the failsafe issue. If you have logs we can take a look but to save me some time it would be good if you could do a bench test to ensure your failsafe works according to the wiki. -Randy Sent from Yahoo! Mail on Android

---

From: criro1999 <crir...@gmail.com>;
To: <drones-...@googlegroups.com>;
Cc: mic...@oborne.me <mic...@oborne.me>; Randy Mackay <rmac...@yahoo.com>;
Subject: Re: [drones-discuss] changes to SR3_* stream rate params and OSD support
Sent: Fri, Nov 29, 2013 10:30:51 PM

To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.

[criro1999]

Hi Randy,

Thanks for your reply.

I did try again to duplicate the issue and I was not able.

What I did notice for me, when I did setup my dx6i for Autotune (to force ch7 for 1800), I did "lost" my config for Throttle failsafe when I rebind to radio.

I did reconfigure again dx6i for failsafe (throttle travel to +125 and rebind) and now looks OK (tested inside, no props, when switch off TX, it enter failsafe and RTL).

I will keep you on touch, thanks again for you and your team for this great project.

Chris

[Gary McCray]

Hi Tridge,

I'm getting started on Wiki page and I have a question (I'll have more), On the PX4v1 you tellus how to enable a second Telemetry port.

"That will change the 5 pin DF13 connector on the corner of the board from being 4 PWM outputs to being a second telemetry port."

Is that on the PX4FMU or I am really guessing the PX4IO and if so which port is it, I do not see any port with 4 PPM outputs on it.

In fact the only PPM output port is the main servo out port with 8 PWM outputs.

The only 5 pin DF13 port I can find on a corner of either board is the FMU-USART2 port on the PX4IO board, is this the one you mean?

And if so, is it the connector you say has 4 PWM outputs on it which seemingly could not be the case because 2 of the pins are power and ground.

Best Regards,

Gary

On Monday, November 25, 2013 6:20:10 PM UTC-8, Andrew Tridgell wrote:

[Bill Bonney]

Hi

> there is a new SERIAL3_BAUD parameter on boards with a secondary
> telemetry port

I’m a bit confused by this statement wouldn’t this be the 4 serial port?

or are you saying we have SR0, SR1, SR2 parameters with SERIAL_BAUD3 setting the baud rate for the ports 1 and 2?

Bill