Hi, I recently purchase a Frsky Q7S ACCST transmitter, I got all the sensor showing up, and I see them in the manual, like battery level, temp, rssi. But I couldn’t get the yaapu7 script work. The telemetry screen shows no Telemetry. I see the graphic in the background. Thank you much for your help.
Hi,
which version of ardupilot do you have?
make sure you set SERIAL_PROTOCOL=10, looks like you set SERIAL_PROTOCOL=4
Alex
Thank you for your reply. I use the latest version OpenTX 2.3.7. And I connect the r9mm frsky using the smartport and sbux. Where I set SERIAL_PROTOCOL=10. Is that a command I run in betaflight.
The fc is a mamba f405 mini mk2, betaflight version is 4.1.1. I’m using Q7S with external r9m module.
Thank you. I appreciate so much for your help.
Hardware
Radio Taranis X9D+, XSR Receiver or R9Slim+, Betaflight F4 PRO V3 or F405Wing. PC with Win 10 PRO
Firmware
TX 2.3.7, RX XSR 2.1.0 or 190201 R9Slim+ , Ardupilot 4.0.5
Companion 2.3.7
I use the telemetry from RC controller trough Inverted PORT of the RX
I use as well the YAAPU script version 1.8.0
The problem:
When I read the models from companion software on the PC and I change same parameters in the models (also without any changes) and I save back I have some changes in the information on the sensors as the attached pictures. The parameter changed is the SENSORS ID, from 0 or 1 to 224 or 225, and Sensors source from INTERNAL (Foto_3.jpg) to “External Module” (foto_11.jpg). Then I do not receive any values from the RC controller sensors but yaapu script works. To fix the issue I read again the sensors from the Telemetry Menu but I could have different sensors sequential number that could have issues in the special function menu of the radio, like Voice alarm. Yaapu script works also without to read again the sensors.
How to reproduce the problem:
On the radio
- Check the sensors. The sensors ID=0, 1 or GPS=251 from what I received from the RC controller : Foto_2.jpg
- Check the sensors details #4 VFAS (battery voltage): Foto_3.jpg
On the PC
3) Read the model from the radio: Foto_5.jpg
4) See the models that I have read from the radio: Foto_6.jpg
5) See the sensors detail in the telemetry Menu: Foto_7.jpg
5) Save Back the models with the following parameters: Foto_8.jpg and Foto_9.jpg
On the radio
6) Check the sensors, #4 VFAS NO VALUE and ID sensors is CHANGET from ID=0 or 2 to ID=224 or 225!!! : Foto_10.jpg
7) Check the sensors details #4 VFAS (battery voltage) and you see the Sensors source is changed from Internal to External MODULE.: Foto_11.jpg.
8) The alert voice alarms could be different after I read again the sensors.
The pictures:
1 Like
Thanks for the very detailed report @fdapport , hopefully it will save some time to anybody hitting the same issue!
I have just upgraded from the Dev version of the mapping widget to 1.181 and I do appreciate the faster processing of map tiles. However when I copy over the files to my SD card I am getting Disabled displayed on the widget screen and I cannot configure the widget. It throws a widget error ‘attempt to index a string value’
Do I have to thrash all the widget config files? Even that seems to not work!
Edit I am using opentx 2.2V0018 so I am thinking this may be the issue. Do I need to upgrade?
Hi Marc, unfortunately that error could be anything, but as you pointed out some config files might not be compatible with the latest version.
Maps should not trigger that kind of issues but to be safe you can remove them as well (or simply rename the folders inside /MAPS/sat_tiles)
Also remove /SCRIPTS/YAAPU/CFG/my_model_name_. and put them aside.
This should get you a clean start.
Alex
Edit: haven’t tested against opentx 2.2.x in a while
I do not think the config files are the issue as I renamed the model I was on to test this (put an underscore in front).
I think this is my version of Opentx. I will upgrade now and confirm.
That was it. Not compatible with the last stable version of 2.2. It broke with the beta 2 release.
You may want to add the requirement to upgrade to 2.3 in the notes.
Thanks as always.
Thanks Marc, so to recap beta2 was working on 2.2 and latest is not, I’ll do some testing myself.
Alex
I was running beta 1 on 2.2 and it worked.
I tried beta 2 and that did not work. When I upgraded to 2.3 everything worked. I must say I really appreciate the custom build of GPmapcatcher. It really makes loading maps so much easier and faster than having to use the script to process.
Also I am having some success using your widget with Pitlab, which outputs a subset of Mavlink messages. I may look at creating a stripped down version for Pitlab – if I find the time.
Hi Mark, ok beta1 is the one to check for breaking 2.2, thanks.
Pitlab support could be just a matter of designing custom left and right panels, flight modes probably need some help from @Eric_Stockenstrom .
Can’t reproduce, I tried latest version on 2.2.4 in the simulator and ran fine, mhmmm 
Odd. I can only tell you my experiences!
I may not have even had the latest Stable version of 2. It could have been older. Quite likely actually.
I would not sweat it now tbh.
1 Like
dear all!
I have exact the same issue as described above. See #1197.
Is it a problem with 2.3.7?
Ardupilot 4.1.0
Taranis X9D+ FW 2.3.7
X4R FW:2.1.0
I really like how you have designed this system. Amazing programming job for sure. I have few questions for you.
-
Is there a step by step guide explaining programming, explains wiring, cascading other SPORT devices such as which device should connect first etc.
-
Is it true that Horus X10S, will not require the external cable that connects the the RX and Ardupilot Serial port if your are using X Rx (Not sure which one)
I can help you put together a proper documentation. I think we are seriously lacking a proper step by step guide as well as how this solution works. Information is scattered all over the place and your main thread on this topic is so long that it is even impossible to scroll down to the bottom 
1 Like
The wiki section on Github has excellent documentation for these lua telemetry scripts. You need to check this out.
If you are using a convertor (Mavlink to Frsky Passthrough) that is actually another project. It is found here:
A good reference is also here at RCGroups: https://www.rcgroups.com/forums/showthread.php?3089648-Mavlink-To-FrSky-Passthrough-Converter
These projects do not actually need any more documentation. Everything you need I linked for you and Eric and Alex spent a lot of time writing it!
This thread is really for issues that arise.
Marc_DornanThanks…I have seen it. I will attempt to consolidate all the info in a simple powerpoint PPT, just for the heck of it. If people like it, we can use it going forward, else it will be for my own personal use.