TELEMETRY screen EDGE v2.5 'Telemetry type' option missing #1260
Comments
pfeerick
added
color
|
For my own education: does someone know what this option is supposed to do? I had the feeling that the telemetry protocol is determined by the module/source of the telemetry data. It is not clear to me what this setting is supposed to do. Is that forcing a telemetry protocol for what is received on a particular serial port? If it is the case, which one? |
|
It was something I use/used to use on 9XR-PRO, and was to do with how the telemetry was fed into the radio - in my case it was "Frsky D (via cable)" IIRC.
Interestingly, this issue suggests it was never implemented for horus targets... which nostromo123 was a commenter in. So I would be curious to know when this became an option in OTX for colorlcd targets since it was not the case in 2.2, and under what configuration settings it becomes available. |
|
Started in 2015
https://openrcforums.com/forum/viewtopic.php?f=96&t=7275#p99610
We shifted over to a German forum in 2016
https://www.rc-network.de/threads/opentx-multiplex-mlink-konverter.581603/
Only seems to be used by users in Germany with their reliable MPX HF
equipment.
Up to you here, if you consider this obsolete .... ;-)
Am 17.12.21 um 09:37 schrieb Peter Feerick:
… Yes, it was something I use/used to use on 9XR-PRO, and was to do with
how the telemetry was fed into the radio - in my case it was "Frsky D
(via cable)" IIRC.
image
<https://user-images.githubusercontent.com/5500713/146514079-46285825-2c3b-4fab-b8f7-28c94972e010.png>
Interestingly, this issue suggests it was never implemented for horus
targets... which nostromo123 was the opener off. So I would be curious
to know when this became an option in OTX for colorlcd targets since it
was not the case in 2.2, and under what configuration settings it
becomes available.
opentx/opentx#4613 <opentx/opentx#4613>
—
Reply to this email directly, view it on GitHub
<#1260 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJB3EKSODAEZIQDSEO3ATLURLZFPANCNFSM5KGVDSXQ>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Not trying to! I was just curious where the telemetry data are fed into the handset. So, where do you plug the converter into the handset? |
|
Just to give an impression, some pics ....
My Taranis with ext converter Arduino pro mini 5V/16MHz
and inside another MPX HFMG3 module with converter based on ATTiny 841
Am 17.12.21 um 11:50 schrieb Raphael Coeffic:
… Up to you here, if you consider this obsolete .... ;-)
Not trying to! I was just curious where the telemetry data are fed into
the handset. So, where do you plug the converter into the handset?
—
Reply to this email directly, view it on GitHub
<#1260 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJB3EKAKXCWCRNPGRYJF5LURMIYDANCNFSM5KGVDSXQ>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Pictures don't come through on email ;) On the 9XR-PRO, it was via the futaba style trainer port... not sure how you did it on the Taranis (so I also will be interested to see! :) ) |
|
Just realized that. ;-) Taranis here
and this I use on my X10 Express
|
|
Hello, I have the same issue. I can't use my two MPX HF modules with my telemetry-converter because it is not possible under EDGE to select the right needed 'Telemetry type' FrSky D protocol in the option section of the radio. PLZ add this feature soon. In OpenTX using the Telemetry type FrSky D and so the MPX HF modules with a telemetry-converter is no problem! THX Alpha |
|
Ok, so we are talking essentially about connecting this converter to the telemetry/S.PORT pin of the module bay, correct? |
|
Yes, you can connect it like I did on the Taranis in the battery bay with an external Arduino pro mini as converter (could place the Arduino inside the MPX module also, but for me it was a bit cramped inside ;-)) or, as I did with the ATTiny in the module box. |
Yes, but that uses another setting, as far as I can see (serial port set to "Telemetry In"). |
|
Your are right. |
|
Radiomaster TX16S "Santa" v2.6.0 Hello, I have the same problem. I cannot use my TGS Jeti module with my telemetry converter as it is not possible under EDGE to select the 'Telemetry type' FrSky D protocol in the options section of the radio. Please add this function soon. In OpenTX, using the telemetry type FrSky D and thus the Jeti HF module with telemetry converter is no problem! |
|
This should be obsolete now as #3352 added native telemetry support of external M-Link HF modules. |
|
Nice catch, yes, that should resolve this particular instance... |
This is the telemetry screen on my X10(s) Express with OTX 2.3.14
and this is with EDGE v2.5
We are using a MPX HF modules with a MPX to FrSky converter for telemetry data.
Could activate telemetry by selecting in EDGE companion v2.6 that 'Telemetry type' option and transfer the model data to the radio, as under EDGE companion the option 'Protocol' is available.
br KH
The text was updated successfully, but these errors were encountered: