Vector UART Telemetry via TBS Crossfire - RC Groups
Thread Tools
Mar 30, 2016, 03:18 PM
Registered User
Discussion

Vector UART Telemetry via TBS Crossfire


Well im trying to get full telemetry working from VECTOR Uart via TBS using the BRIDGE telemetry mode and not having much luck.

According to ET it is 8N1 57600baud and you only need orange and black see below

// Vector Open Telemetry Revision 0
// NOTES:
// 1) UART protocol is 8N1 (8 bits, no parity bit, 1 stop bit), 57600 baud, 3.3V input/outputs levels (input is NOT 5V tolerant!)
// 2) all fields BIG-ENDIAN byte order
// 3) The VECTOR_OPEN_TELEMETRY packet is sent as frequently as every 80mS, but timing will vary considerably
// 4) To enable telemetry output on the Vector's UART port, select the "Open Telm" option
// for the "Configure the UART port for" stick menu item, under the ""EagleEyes and Telemetry" OSD menu

// Vector UART Pinout (using standard Vector "BUS" cable colors):
// Yellow: RX (Receive data TO the Vector - note that this connection is not needed)
// Orange: TX (Transmit data FROM the Vector)
// Black: Ground
// Red: 5V Out, 150mA max (from Vector PSU or backup power input - do not exceed 1A total load on Vector PSU! Don't connect this wire unless the device receiving the telemetry requires power from the Vector)
// IMPORTANT: NEVER connect the telemetry cable to any Vector port other than UART! Doing so can damage your equipmend


Which should tie in with TBS Crossfire serial bridge mode see below excerpt from crossfire manual.

Serial
The bridge feature gives you the ability to pass any kind of serial uart data from any device connected to thereceiver to any device connected to the trasmitter’s Bluetooth. If you select “Bridge TX” for output 8, output 7will automatically change to “Bridge RX” and channel 6 to “Bridge RTS”. Please connect your device accordingto this information. The baudrate is set to 57600 8N1 and the voltage level is 3.3V. The RTS pin will change tological high when the internal FIFO is almost full and low if the FIFO is almost empty. There is no hardwareflow control for the uplink as the bluetooth module doesn’t support it. The Bluetooth mode on the TX willautomatically change to bridge on the first few bytes sent down from the receiver if the mode is not set toOFF.

I can get the GPS coords back to crossfire as per normal using GPS>BST and Mavlink EMU however other telemetry doesnt work

Anyone tried this yet.?
Sign up now
to remove ads between posts
Aug 25, 2016, 03:55 PM
Registered User
Nobody got this working then.? Oh well time to switch.
Apr 15, 2018, 09:29 AM
Registered User
Quote:
Originally Posted by keithsuth
Well im trying to get full telemetry working from VECTOR Uart via TBS using the BRIDGE telemetry mode and not having much luck.

According to ET it is 8N1 57600baud and you only need orange and black see below

// Vector Open Telemetry Revision 0
// NOTES:
// 1) UART protocol is 8N1 (8 bits, no parity bit, 1 stop bit), 57600 baud, 3.3V input/outputs levels (input is NOT 5V tolerant!)
// 2) all fields BIG-ENDIAN byte order
// 3) The VECTOR_OPEN_TELEMETRY packet is sent as frequently as every 80mS, but timing will vary considerably
// 4) To enable telemetry output on the Vector's UART port, select the "Open Telm" option
// for the "Configure the UART port for" stick menu item, under the ""EagleEyes and Telemetry" OSD menu

// Vector UART Pinout (using standard Vector "BUS" cable colors):
// Yellow: RX (Receive data TO the Vector - note that this connection is not needed)
// Orange: TX (Transmit data FROM the Vector)
// Black: Ground
// Red: 5V Out, 150mA max (from Vector PSU or backup power input - do not exceed 1A total load on Vector PSU! Don't connect this wire unless the device receiving the telemetry requires power from the Vector)
// IMPORTANT: NEVER connect the telemetry cable to any Vector port other than UART! Doing so can damage your equipmend


Which should tie in with TBS Crossfire serial bridge mode see below excerpt from crossfire manual.

Serial
The bridge feature gives you the ability to pass any kind of serial uart data from any device connected to thereceiver to any device connected to the trasmitter’s Bluetooth. If you select “Bridge TX” for output 8, output 7will automatically change to “Bridge RX” and channel 6 to “Bridge RTS”. Please connect your device accordingto this information. The baudrate is set to 57600 8N1 and the voltage level is 3.3V. The RTS pin will change tological high when the internal FIFO is almost full and low if the FIFO is almost empty. There is no hardwareflow control for the uplink as the bluetooth module doesn’t support it. The Bluetooth mode on the TX willautomatically change to bridge on the first few bytes sent down from the receiver if the mode is not set toOFF.

I can get the GPS coords back to crossfire as per normal using GPS>BST and Mavlink EMU however other telemetry doesnt work

Anyone tried this yet.?
Hi, I spent considerably time on this yesterday and also couldn't get it working. I attempted many many wiring and setup variations without success. Did you get it working or did you abandon it???? Thanks, Todd


Quick Reply
Message:

Thread Tools