Originally Posted by
Auburn02
Can you go into a bit more detail on this? While I am well aware the telemetry options are more limited, every sensor I have used with Futaba has worked well, with quirks like air pressure having to be registered as a temperature sensor. But what is it about their "protocol" that is lagging?
Well, for a start, all Fuataba telemetry values are just "anonymous" values, there is no type/priority (etc) assigned to these data. You have to tell the TX what is coming in on a specific slot. You are limited to the 31 slots (16 bit values), you have no possibility for text messages (think turbine status etc etc). The sensors are fixed on the transmitter, if a specific sensor type is not something Futaba has thought about, you are basically lost. What if I would like to display the amount of fuel left iin my tank in mL/OZ, in % etc ? I can't do that as there are no "tank" sensor type. So I can show it as a "temperature", not very nice.....
I could go on and on (oh, why are there no CRC check on the SBUS(2) data ? Only a parity bit (which is of not much use), and why are the electrical levels inverted on the bus as compared to 100% of other protocols in the world ?)
I could go on and on....
But maybe they changed it on the 32MZ....or not, time will tell