Wanted: wireless replacement for serial/bluetooth

[Hamburger]

I want to replace the bluetooth bridge I currently use for serial communications between tbe fc and a terminal/ ground station.
Requirements would be
+ range >500m
+ not 2.4GHz
+ ttl serial on both ends
+ >38400 on the ttl, if possible support 115200 mwc native
What are current options? I remember apc220 was favoured earlier but hoperf has better duplex caps ....

[alll]

+1

[crashlander]

? I remember apc220 was favoured earlier but hoperf has better duplex caps ....

APC220/802 is only 19.2kb in the air and as such not suitable for fast two-way comm.

Regards
Andrej

BTW: If you lessen that 2.4GHz restriction than SHUNCOM SZ05-TTL-ADV could be the one (suggested by city_kid).

[cGiesen]

? I remember apc220 was favoured earlier but hoperf has better duplex caps ....

APC220/802 is only 19.2kb in the air and as such not suitable for fast two-way comm.

In fact, the really result is less than about 12kb

[copterrichie]

Here is an option however the baud rate is not stated.

http://www.hobbyking.com/hobbyking/stor ... 15Mhz.html

One would have to assume "This product is based on the 3DRadio Project from 3D Robotics."

[Hamburger]

? I remember apc220 was favoured earlier but hoperf has better duplex caps ....

APC220/802 is only 19.2kb in the air and as such not suitable for fast two-way comm.

BTW: If you lessen that 2.4GHz restriction than SHUNCOM SZ05-TTL-ADV could be the one (suggested by city_kid).

I do not necessarily intend to saturate the 115k but would prefer to be lazy and keep both ends at the preconfigured 115k line speed. lcd.Telemetry is usable for me when sending about 50 bytes every 23th cycle (3ms/cycle). That would result in 600 bytes/s or 6kbit/s raw traffic data.

When extending range beyond the 50m bluetooth range then I would prefer to not have data transmission back channel interfere with tx-rx communications. At least the fpv guys keep emphasizing this point.

[crashlander]

At least the fpv guys keep emphasizing this point.

In that case reconsider switching TX-RX to 433MHz (video on 1.2G) and put telemetry to 2.4G That way you will first notice no telemetry than video and in the end TX (you will not crash with no control but perfect telemetry and/or video).

Regards
Andrej

[NikTheGreek]

How about this....?

http://www.hobbyking.com/hobbyking/stor ... duct=27096

which is used here

viewtopic.php?f=8&t=3101

[Alexinparis]

How about this....?

http://www.hobbyking.com/hobbyking/stor ... duct=27096

which is used here

viewtopic.php?f=8&t=3101

This solution is good only for MSP messages, but is not transparent to something which is not MSP (reason: as we can insert some additional MSP for RC control, we need to control the input in order to not break an incoming message in the middle)

with 2x OLRS I can however make a special version with a real UART transparency with the following features :
- guaranteed 20ms delay
- air speed: 57600 (same as OLRS => same expected range)
- UART interface: 115200 with a buffer of 256 bytes
- real efficiency: symmetrical and around 25kb per way

[thebgrian]

Alex, this will be great!
With the low price of the RF modules and the ease of making your own (with a Arduino pro mini for example) or just buying one this will be a very valuable solution .
It will be useful for a lot more than just multiwii telemetry.
Thank you for starting and working on this project.