Serial Port Question & NSH Command Help

1

I own an AUAV-X2 and I have connected Telemetry and OSD to Date to the Top Serial Connector (UART 2 / Serial 1).

As I have new Telemetry HW which has stronger Signal but lower DC I wanted to use dedicated Ports for Telemetry and OSD. So I thought I might use UART 3 / Serial 2… I can see that there is some sort of Signal getting out of there but if I connect the OSD it does show waiting for Data, if I connect the Telemetry it blinks but I’m not able to get a connect to QGC.

If I connect Telemetry to Serial 1 it is recognized after Boot:

instance #0:
.GCS heartbeat:.319175544 us ago
.mavlink chan: #0
.type:…3DR RADIO
.rssi:…88
.remote rssi:.0
.txbuf:…54
.noise:…89
.remote noise:.0
.rx errors:.0
.fixed:…0
.flow control:.ON
.rates:
.tx: 0.847 kB/s
.txerr: 0.000 kB/s
.rx: 0.034 kB/s
.rate mult: 0.311
.accepting commands: YES
.MAVLink version: 1
.transport protocol: serial (/dev/ttyS1 @57600)

instance #1:
.mavlink chan: #1
.no telem status.
.flow control:.ON
.rates:
.tx: 0.906 kB/s
.txerr: 0.124 kB/s
.rx: 0.000 kB/s
.rate mult: 0.466
.accepting commands: YES
.MAVLink version: 1
.transport protocol: serial (/dev/ttyS2 @57600)

If I connect it to Serial 2 it is not:

instance #0:
.mavlink chan: #0
.no telem status.
.flow control:.ON
.rates:
.tx: 1.087 kB/s
.txerr: 0.000 kB/s
.rx: 0.000 kB/s
.rate mult: 0.561
.accepting commands: YES
.MAVLink version: 1
.transport protocol: serial (/dev/ttyS1 @57600)

instance #1:
.mavlink chan: #1
.no telem status.
.flow control:.ON
.rates:
.tx: 0.827 kB/s
.txerr: 0.000 kB/s
.rx: 0.000 kB/s
.rate mult: 0.466
.accepting commands: YES
.MAVLink version: 1
.transport protocol: serial (/dev/ttyS2 @57600)

So I’m wondering why it behaves like this? Anybody a hint for me?

Secondly I’m missing a Command Line Documentation for the BuiltIn Commands. For instance I could not figure out how to use the various Switches of the Command MAVLINK (obviously other thant Status). Is there any Docu available on the Net (Google or me could not find it).

As a goodie I might want to connect a Collision Warning Device to the AUAV-X2 (a FLARM) for Testing reasons - has anybody already done a similar thing? I have seen that there are pending Pull Requests in the Code.

Thanks for any help on this.

2

Check the SYS_COMPANION parameter. It controls what’s started on telem 2 at boot.

There’s not a lot of documentation for using the apps via command line. If you find the simple usage output on the command line is incorrect please open a github issue and it can be fixed easily.

3

Thanks for you help. Some (very) basic help is given, but many Parameters are not explained - so it’s not really incorrect just incomplete. Is there some Helpsystem like info or man (Unix alike) or some Internet Docu?

AFAIK SYS_COMPANION only affects TELEM2 which currently works for me (SERIAL 1)? I tried setting it to OSD or TELEMETRY but no change in behavior.