openrcforums

Try using PPM7 and PPM8 as sources on channels 7 and 8..
Ch7 100% PPM7
Ch8 100% PPM8

This should be a good start point..

João

It works !
Thank you João !
I was trying different things and I was just not getting it right.
It was too simple for me. Thanks again,

Bob B.

ErSky9x/Taranis change Primary Telemetry Data to external XJT/DJT module.

Hi Mike,
Could there be a setting, in the hidden radio screen settings for an option to select which transmitter would have the primary Telemetry Data and maybe become the primary transmitter.

Because now when using both internal and external transmitters at the same time, the Telemetry Data is used from the internal XJT only which locks us to only using PXX with its Swr data reporting.
Having the option to change it to the external transmitter would allow us to use the PPM and our favorite TSSI data reporting with our favorite D8R-II plus and/or D8R-XP Receivers.

Having this option to make the external transmitter module primary and the internal to be the secondary transmitter, I think would be a good option to have.

The D-series transmitter and receivers with telemetry are FrSky's best products, which has built their good name.

Bob B.

bob195558 wrote:
The D-series transmitter and receivers with telemetry are FrSky's best products, which has built their good name.

Bob B.

I totally agree with you

João

When using the external DJT, how are you connecting the telemetry data?
If you use an external XJT, then you have a problem as both internal and external share the SPort connection, so we can't choose between them.

Mike.

I use com2 external DJT
Same with external XJT PPM/Dip switches.

Taranis (erSky9x-x9d) telemetry using external transmitter modules
XJT module to X8R receiver/S.Port telemetry works with both DipSW OFF/com1/PXX/D16.
XJT module to D8R-II receiver/telemetry works with both DipSW OFF/com1/PXX/D8.
XJT module to D8R-II receiver/telemetry works with DipSW 1 ON & 2 OFF/com2 external cable/ PPM/D8.
DJT module to D8R-II receiver works with both DipSW OFF/com2 external cable/PPM/D8.

MikeB wrote:If you use an external XJT, then you have a problem as both internal and external share the SPort connection, so we can't choose between them.Mike.

This may not be a problem when I am using Comport 2 ?

I have used and it works properly:
XJT module to D8R-II receiver/telemetry works with DipSW 1 ON & 2 OFF/com2 external cable/ PPM/D8.
DJT module to D8R-II receiver works with both DipSW OFF/com2 external cable/PPM/D8.

Bob B.

Hi Mike,
Could firmware be written,
when using external DJT/XJT module as primary telemetry transmitter,
it can only be use with comport 2 for the telemetry data ?

Bob B.

Add edit: It's something that OpenTX can not do!

It could leave out using S.port as this would only be used for the D-series receivers.

In our small RC group for the second time a member is having failures with his internal XJT transmitter and with some of the S.port sensors too.
So we like to use the more reliable D series, they all just keep working without any trouble.

Bob B.

So is the problem that when you have the internal XJT operating and the external DJT (using COM 2), that the internal XJT telemetry is automatically used, and you would rather use the external DJT?

Mike.

Hi Mike,
Yes, the internal XJT is limited by locking us to only use PXX which only uses Swr and has a lower RSSI signal compared to using the external XJT/DJT modules.
Because the internal XJT has no way to bind it when using PPM (which then works like the DJT), I lose the TSSI way reporting its telemetry data also.

Maybe there is a bug with the Swr or something.
When trying to use the Swr I find it useless data as it dose not seem to work correctly.
The Swr just stay at 0 (which I know is an indication that it is working properly) and only wakes up (changes values) after I have lost the RSSI signal.
Swr is not working like TSSI, Swr goes from 0 and jumps to 25 number value or some other higher, lower number value when it is close to losing its telemetry signal and this is after the RSSI signal is lost.
There is no to very little graduation of number values changes as the receiver (model) moves further away from its radio transmitter when using the Swr.

Also because the two Taranis-x9d in our small RC group are before FrSky made the improvements to the internal XJT transmitter and the earlier purchased Taranis -x9d has it's second internal XJT failing.
So it's prudent to not use the internal XJT as the primary transmitter.
And I need more then 8 channels, so it's prudent to use the more reliable external transmitter as the primary and the internal XJT (being less reliable) as second transmitter for the less important channels needed.

Added link about Taranis Com2 Telemetry Cable: (viewtopic.php?f=96&t=4393&start=60#p79427).

Bob B.

OK, I'll take a look. It my be a few days before I can look properly as I'm just moving all the source files from googlecode (which is closing down) to Github. I have most of it done, but just need to get all the build functions working from the files in their new locations, then test everything.

Mike.

Thank you Mike.
I appreciate you taking a look at it after all the source files from Google Code are moved to Github.

Google-Code will becomes read only August of this year.
You will be able to read and view the source code, issues and wikis, until January 25, 2016 and then the this service will be shut down.

Bob B.

Hi Mike,

Could there be a mode to upgrade the Taranis processor some day ?

Have you had time to see, if possible to have an option to choose making the external transmitter primary for telemetry (through com2) ?

Bob B.

I'm not sure the Taranis processor needs upgrading, it is already quite powerful. A STM32F405 should fit as a replacement, and is code compatible. This will run faster, and also include a floating point unit.

I've not had time to look at choosing the telemetry source, but I've put it on my "todo" list.

Mike.

I think it might be possible to handle:
Internal module PXX
External module PPM
Telemetry port COM2
Assumes you want to use FrSky hub protocol from the external module.
If Telemetry port COM1 is set, then it uses SPort from the internal module.

Mike.

Hi Mike,
I think that sounds right.

When using both internal and external transmitters and setting external transmitter as Primary module
uses com2 for hub protocol telemetry with D8R-II plus or D8R-XP receiver.

Internal module PXX / is then used as secondary transmitter no telemetry from port com1
(com1 turned off as will be set to port com2 for primary external module).

External module PPM when used as Primary module uses port COM2 for Telemetry
(I use telemetry cable through back of taranis case to DJT or XJT modules COM2).
Using FrSky hub protocol from the primary external module to be used with D8R-II plus receiver and its telemetry.

And when internal transmitter is set as Primary module goes back to using port com1 for telemetry
and so uses SPort from the internal module (as how it now works as when it is used as the primary transmitter.

Bob B.

Looks to be generally working with a few changes I've just put in. You simply select the COM port you want to use, 1 for SPort and 2 for DJT hub. The only problem at the moment is when switching from COM2 to COM1, there seems to be a Tx reboot a while later, when the RSSI value changes, then it works properly.

Mike.

Hi Mike,
That sounds like a really simple way to select the option.
So when both external and internal modules are turned on in the Protocol menu (internal PXX and external PPM / DJT or XJT)
and in the Telemetry menu select com2 and the telemetry then works only with the external module by way of com2 / FrSky hub protocol .
I like it!

Bob B.

I've just posted a test version (for standard and plus). I think I've fixed the reboot problem as well. When not used for anything else, the COM2 port is used for a debug task. This was receiving all the telemetry data from the DJT and may well have caused a problem.
I've added an extra option to the entry "COM2 baudrate", which isn't really used at present. Keep this now set to "OFF" and the debug task is suspended.

I switched the "FrSky COM Port" option between 1 and 2 several times and the telemetry switch between the internal PXX and the external DJT-hub with no problems.

Unless it is possible to disable a XJT from sending telemetry data, using two of these is not possible as the telemetry from both is on the SPort.

Mike.

Thank you Mike,
It's becoming late here too, tomorrow I will implement the new test x9d_rom firmware.
Hope to have some results tomorrow before the day ends.

Bob B.

Hi Mike,

Did a partial quick test of the new July 30 test x9d firmware using only one D8R-II plus 8 Channel Receiver to the external (PPM) transmitter.
Both internal (PXX) and external (PPM) transmitters turned on with telemetry set to com2.
After flashing new test firmware, powering radio off and on and making the proper setting change to the selected model eeprom,
when viewing telemetry screen the TSSI label is change to the SWR when making the setting for the internal transmitter to PXX.
This is not a problem for me as it is behaving like it should as a traditional TSSI and is reporting this telemetry data through the
external transmitter set to PPM with the D8R-II plus receiver / FrSky hub protocol.

I hope to add the secondary D8R-II plus receiver to internal PXX transmitter later today and will report results.

Bob B.

Hi Mike,

Have added secondary D8R-XP receive (D8R-II plus)
and using a servo for testing, it is working !

Thank you very much !

I needed to remember to set the internal transmitter to First Channel: 17.
Its working very well ! Thank you Mike !

Added link about Taranis Com2 Telemetry Cable: (http://openrcforums.com/forum/viewtopic ... =60#p79427).

Bob B.

I think I have the fix for the TSSI/SWR label, just need to test it.

Mike.

I've managed to install ersky9x erx9d-r218 on my Taranis (not Plus). I did this by flashing the FW using Companion9X Version 1.52 on a PC running Ubuntu 14.04. For some reason Companion has connection issues with the USB in Windows 7, hence the use of Ubuntu. Meanwhile, I have saved my models via an eeprom file off my 9XR that is running er9x r-819 using eepe. I now need to burn my eeprom to the Taranis. I've launched eepskye (from the eepe folder) but when I attempt the burn it complains that it can't find sam-ba.exe (which isn't in the file where it's looking and it's an .exe which won't run in any case). Any ideas how I can now get my models installed on the Taranis?

Go to the "Burn" menu/ configure and make sure the box "Use SAM-BA" is not ticked.

Then start your taranis with both horizontal trims towards the center. You should be in bootloader mode. Now plug your USB cable. Two drives should appear on your desktop after a few seconds. One is your SD Card. And the other the radio's internal drives..
Now just try to read the eeprom with eepskye

João

Hi João,
You were fast then I was.

Bob B.

Hi mapes12,
You should use the bootloader way of connecting with USB, its the default setting and a way better way to do it.
To use Samba, if it works with Taranis-x9d I am not sure it dose as I never have tried it,
you may need to click the check-mark in the configuration window (Configure).

Bob B.

Edit: You will like ErSky9x on Taranis !

jhsa wrote:Go to the "Burn" menu/ configure and make sure the box "Use SAM-BA" is not ticked.

Then start your taranis with both horizontal trims towards the center. You should be in bootloader mode. Now plug your USB cable. Two drives should appear on your desktop after a few seconds. One is your SD Card. And the other the radio's internal drives..
Now just try to read the eeprom with eepskye

João

Done this but it still doesn't work. I think the problem is that the EEPROM saved from my 9XR is an .eepe file and eepskye is looking for a .bin file. I can read the EEPROM on the Taranis OK and if I want to save it then it defaults to .bin format.

Hi mapes12,

Sorry I misunderstood your question, my error.

I am not sure, I did see a post somewhere about this several weeks ago and have not been able to find it yet.

Edit: This may not help (viewtopic.php?f=7&t=7143&p=98416&hilit= ... kye#p98416)

Bob B.

Open eepskye and download your eeprom from the taranis onto it.. Now open eepe and open your saved eeprom from the 9XR. Drag the models one by one from the 9XR eeprom to the taranis eeprom in eepskye. This will copy them. An error will be displayed but you can ignore it. Now burn the taranis eeprom back to the radio. Check all settings on the models to make sure all is ok. Expect some settings to be changed.

João