Hi,
I am trying to connect the Spirit-FBL with a DSMX Satellite with DMSX protocol.
But channels are terrible mixed up:
Watching the Diagnostic-Tab in the config Software the following could be observed:
=== DSMX ===
Ch1:
from -100% to ~0% moves Throttle
from ~0% to +100% moves Aileron
Ch2:
from -100% to ~0% moves Elevator
from ~0% to +100% moves Rudder
Ch3:
from -100% to ~0% moves Gyro
from ~0% to +100% moves Pitch
Ch4:
from -100% to ~0% moves Bank
=========
Channel assignment is:
Ch1: T
Ch2: A
Ch2: E
Ch4: R
Ch5: Gyro
Ch6: Pitch
Ch7: Bank
So I tried to bind with DSM2
This seems to be working.
But even there is a minor issue I don't understand:
Although in the TX all Channels are set to be from -100% to +100% the Diagnostic Tab shows values from -98% to 102%
My Equipment:
- spirit-fw-1.0.25.1.bin
- Walkera Devo10 with Deviation FW http://deviationtx.com
- original Spektrum DSMX Satellite.
- Powersupply: 4xNiMH AA Battery = 4,8V
- PC: Linux USB and Android Bluetooth
Hope this helps to resolve the issue.
Let me know, if I could do anything else to help.
Greetings
Manfred
[SOLVED] DSMX Satellite - channels mixed up
-
linux-user
- Posts: 45
- Joined: Fri 19. Dec 2014 18:37:00
- Location: near Munich
Last edited by linux-user on Fri 26. Jun 2015 20:29:55, edited 1 time in total.
Hello,
this TX should be binded with DSM2 as you have did - this is because DSMX in our case require 11ms currently, but this feature is not supported by your TX. With upcoming FW it will be possible to bind it properly to 22ms @ DSMX. All in all, even it is binded as DSM2 it will in reality work as DSMX without any issue.
Next issue is very minor - there are nearly always differences between transmitter. Values that are displayed in TX are not the same that unit can see so you should little bit change with Travel Adjust endpoints for these channels.
2% are very small difference, but it can be configured exactly in your TX.
This is nothing to worry as it is normal phenomenon.
this TX should be binded with DSM2 as you have did - this is because DSMX in our case require 11ms currently, but this feature is not supported by your TX. With upcoming FW it will be possible to bind it properly to 22ms @ DSMX. All in all, even it is binded as DSM2 it will in reality work as DSMX without any issue.
Next issue is very minor - there are nearly always differences between transmitter. Values that are displayed in TX are not the same that unit can see so you should little bit change with Travel Adjust endpoints for these channels.
2% are very small difference, but it can be configured exactly in your TX.
This is nothing to worry as it is normal phenomenon.
Spirit System developer
-
linux-user
- Posts: 45
- Joined: Fri 19. Dec 2014 18:37:00
- Location: near Munich
Thanks for your quick and informative reply.ZeXx86 wrote:Hello,
DSMX in our case require 11ms currently, but this feature is not supported by your TX. With upcoming FW it will be possible to bind it properly to 22ms @ DSMX.
I am looking forward to the new FW
-
linux-user
- Posts: 45
- Joined: Fri 19. Dec 2014 18:37:00
- Location: near Munich
Yes, solved since v1.1.0Nafets77 wrote: Has the issue with European DSMX only using 22ms been solved. It's not mentioned in the change log for v1.2.0.