Code: Select all
if (byte == 0x5e) {
state = TS_DATA_ID;
return;
}
if (state == TS_IDLE) {
return;
}
if (state & TS_XOR) {
byte = byte ^ 0x60;
state = (TS_STATE)(state - TS_XOR);
}
if (byte == 0x5d) {
state = (TS_STATE)(state | TS_XOR);
return;
}
Code: Select all
state = (TS_STATE)(state - TS_XOR);
}
else if (byte == 0x5d) {
.
). . Mr. Westerteicher from ACT told so day after day but nobody listen to him .It might be the case for Multiplex stuff, but FrSky uses the same power both ways... and it's how it should be IMO, those who don't are doing it wrongTobi wrote: By the way, using rssi for range warning is not quiet sensible, because the retrieve power is normaly less than the Tx power. Mr. Westerteicher from ACT told so day after day but nobody listen to him
I'm really glad telemetry gives up before we lose control, and when that happens it's really time to land. But as Kilrah said both TX and RX power is equal, and I also think that is the way it should be.. It makes for a very accurate report..Tobi wrote:
By the way, using rssi for range warning is not quiet sensible, because the retrieve power is normaly less than the Tx power. So if rssi goes kritical telemetry gives up long time before. If telemetry gets lost, this is a (not critical) trigger for coming home but not rssi
Now I go for more testing...
best regards
Tobi
). First time I could realy use telemetry in air without looking on display or getting a text overflow. Verry good work of all OpenTX-experts! 
) to use OpenTX telemetry functionality.Sensors have a "Positive" attribute/checkbox you would need to uncheck if you want to send negative values.Tobi wrote:2. Negative values for altitude leads to values greater than 65000! This could only be, if there is a wrong type casting in telemetriy code of OpenTX, I beleve. Please tell me if I am wrong. To fix this, I only send absolut values at this time.
The FrSky protocol doesn't specify more than 6 cells per "logical" sensor. You should group your cells in packs of 6 and increment the data ID by one for each new one. They will appear as separate "Cels" sensors in OpenTX.Tobi wrote:4. On Mlink-protocol it is possible to send up to 16 different voltage values. I tried to map this using the Cell-ID of FrSky-D protocoll. But only sometimes it apppears a sensor called "Cell". The visualized values do not correspond wiht the send data.
Could you give me some mere information? I do not understand how to transmit a data ID. At this point I only know how to send a cell-ID in first 4 bit and the data on the rest.Kilrah wrote:
The FrSky protocol doesn't specify more than 6 cells per "logical" sensor. You should group your cells in packs of 6 and increment the data ID by one for each new one. They will appear as separate "Cels" sensors in OpenTX.
) and the lower 12bits are the voltage value. Using LUA script? I can not find any other kind of formula...You can then get "details" (lowest, highest, highest-lowest, and any individual cell) using Calculated sensors you create with formula "Cells"
Tobi. My module arrived and I have made up the ProMini board. I have a problem with your arduino file. It stops with error messages when I try to upload it. I'm using the latest Arduino 1.6.5. Do I need to use an earlier version? Thank youaduncan wrote:Thank you. I will report back when my module arrives. I have a spare Arduino proMini to use.
Regards
Andrew
. 
