All FrSky radios have always had switched power to both modules.
Mlink-FrSky-Telemetry converter
Re: Mlink-FrSky-Telemetry converter
Good to know, thanks.. I think it was not known that the X9E had support for another module.. at least not very known..
João
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
Re: Mlink-FrSky-Telemetry converter
Hello Willy,
ubs, I forgot to eleminate the act-servo from the header-file - sorry. I did it now.
The act_servo is a implementation of ACT-DSL-protocol and Master Westerteicher ask me not to publish so I
put it in its own lib. Sorry, I can not provide this new lib...
MLink and FrSky-protocol are not perfectly compatible in every case. So not all values send by MLink could transform to FrSky-protocol.
I did some changes in MLink lib and FrSky lib to implement STM32F1.. But the implementation in FrSky is not finaly tested - so please be carefull!
Additional there is a new schematic with the fixes wich are discused here in the last days and there is now the doku-pdf of MLink-protocol.
best regards
Tobi
ubs, I forgot to eleminate the act-servo from the header-file - sorry. I did it now.
The act_servo is a implementation of ACT-DSL-protocol and Master Westerteicher ask me not to publish so I
put it in its own lib. Sorry, I can not provide this new lib...
MLink and FrSky-protocol are not perfectly compatible in every case. So not all values send by MLink could transform to FrSky-protocol.
I did some changes in MLink lib and FrSky lib to implement STM32F1.. But the implementation in FrSky is not finaly tested - so please be carefull!
Additional there is a new schematic with the fixes wich are discused here in the last days and there is now the doku-pdf of MLink-protocol.
best regards
Tobi
- Attachments
-
- MLink-FrSky S.Port-Adapter.zip
- (1.65 MiB) Downloaded 357 times
Re: Mlink-FrSky-Telemetry converter
Hi Tobi, just a little hint: That transmitter is called X9E (not 9xe as in your schematic)
https://www.engelmt.de/mt1marken/frsky- ... anis-x9e/1
https://www.engelmt.de/mt1marken/frsky- ... anis-x9e/1
Re: Mlink-FrSky-Telemetry converter
Thanks for correction. I will fix this
Re: Mlink-FrSky-Telemetry converter
Hallo Tobi
It's going pretty well with me. My current problem is RPM on class 5. I get here - (minus values) purely.
Es läuft bei mir schon recht gut. Mein aktuelles Problem ist RPM auf klasse 5.
Ich bekomme hier - (minuswerte) rein.
ca. Werte,
rpm ist = 10230 ..... Anzeige = -1536000
Differenz 1670.......................16800
rpm ist = 11900 ..... Anzeige = -1519200
Differenz..2330.......................23500
rpm ist = 14230 ..... Anzeige = -1495700
Differenz...670.........................6500
rpm ist = 14900 ..... Anzeige = -1489200
Sigi
It's going pretty well with me. My current problem is RPM on class 5. I get here - (minus values) purely.
Es läuft bei mir schon recht gut. Mein aktuelles Problem ist RPM auf klasse 5.
Ich bekomme hier - (minuswerte) rein.
ca. Werte,
rpm ist = 10230 ..... Anzeige = -1536000
Differenz 1670.......................16800
rpm ist = 11900 ..... Anzeige = -1519200
Differenz..2330.......................23500
rpm ist = 14230 ..... Anzeige = -1495700
Differenz...670.........................6500
rpm ist = 14900 ..... Anzeige = -1489200
Sigi
Mlink-FrSky-Telemetry converter (Sailplane/Vario - refresh optimized)
Hello All
My converter is running and like Tobi told us it's sometimes necessary to tune a little.
My ACT-Receivers are all in sailplanes and so the huge functionallity is not necessary for me. I just need RSSI, RxBt, Height, Distance, V_vert(Vario). On the other hand the update-cycle of the Vario has been a little poor for challenging thermal flights. So I tried to tailor me a perfect fitting solution - and I'm satisfied with the result.
Here you can see the update-rates (RxBt is slowed down to 5s because there's hopefully no quick change): https://youtu.be/GqcXRXqhB3o
Here's my current code: I don't have any further docs that will explain the necessary points to tailor, but if necessary I will prepare a little explanation.
Greetings
Willy
Btw: If necessary, it would be possible to have two switchable Arduinos installed (one quick for Sailplanes, one with full functionallity) - it's just some bucks.
My converter is running and like Tobi told us it's sometimes necessary to tune a little.
My ACT-Receivers are all in sailplanes and so the huge functionallity is not necessary for me. I just need RSSI, RxBt, Height, Distance, V_vert(Vario). On the other hand the update-cycle of the Vario has been a little poor for challenging thermal flights. So I tried to tailor me a perfect fitting solution - and I'm satisfied with the result.
Here you can see the update-rates (RxBt is slowed down to 5s because there's hopefully no quick change): https://youtu.be/GqcXRXqhB3o
Here's my current code: I don't have any further docs that will explain the necessary points to tailor, but if necessary I will prepare a little explanation.
Greetings
Willy
Btw: If necessary, it would be possible to have two switchable Arduinos installed (one quick for Sailplanes, one with full functionallity) - it's just some bucks.
Re: Mlink-FrSky-Telemetry converter
Hello Sigi,
thanks for your error listing. I will check it.
best regards
Tobi
thanks for your error listing. I will check it.
best regards
Tobi
Re: Mlink-FrSky-Telemetry converter
Hallo Tobi
Ich habe jetzt alle Sensoren mit Testdaten im Arduino simuliert. In der Taranis bekomme ich dann 17 Sensoren angezeigt, meine Testdaten werden sauber übertragen.
Auch die Drehzahl auf Einheit 0x05 von 0 - ca 100000 rpm.
Bei der Übernahme der Drehzahl aus der ACT Telemetrie bekomme ich jedoch die negativen Werte, wie gepostet.
Ich vermute das bei der 32Bit Wandlung die Byte Reihenfolge gedreht wird. Ich konnte es jedoch im Programm nicht finden.
Ich hoffe du kannst da nochmal nachschauen.
Sigi
Ich habe jetzt alle Sensoren mit Testdaten im Arduino simuliert. In der Taranis bekomme ich dann 17 Sensoren angezeigt, meine Testdaten werden sauber übertragen.
Auch die Drehzahl auf Einheit 0x05 von 0 - ca 100000 rpm.
Bei der Übernahme der Drehzahl aus der ACT Telemetrie bekomme ich jedoch die negativen Werte, wie gepostet.
Ich vermute das bei der 32Bit Wandlung die Byte Reihenfolge gedreht wird. Ich konnte es jedoch im Programm nicht finden.
Ich hoffe du kannst da nochmal nachschauen.
Sigi