If it will not work then maybe the purchase of a new one is necessary, then it should work -
Regards
Matthias
Spirit1 telemetry Hobbywing V4
Alexander my FrSky-Integration cable has before changeing (adding the additional plug) also two black connectors -
In the online-shop the integrationcable is also with two black connectors
If it will not work then maybe the purchase of a new one is necessary, then it should work -
Regards
Matthias
If it will not work then maybe the purchase of a new one is necessary, then it should work -
Regards
Matthias
Hello,
it is very important to do correct cable wiring. Also direction is very important.
Without modification of the cable Futaba telemetry will never work unfortunately.
Can you take a photo of the modified cable/wiring please?
it is very important to do correct cable wiring. Also direction is very important.
Without modification of the cable Futaba telemetry will never work unfortunately.
Can you take a photo of the modified cable/wiring please?
Spirit System developer
Please make sure that your receiver is powered by another stright cable.
Could you control at least servos with this wiring?
If no, is receiver powered on?
Could you control at least servos with this wiring?
If no, is receiver powered on?
Spirit System developer
Hi,
OK, after a long search I found that there was a faulty pin in the Y-cable for the power supply to the receiver, I now have the following status:
The yellow cable of the ESC is connected to the PIT pin.
The modified integration cable is connected as prescribed.
Receiver is connected with just power (no data-line) of the BEC.
After switching on, the Spirit is initialized first, then the initialization of the ESC (3S-Lipo) is indicated by the triple beep.
Servos can be controlled, Governor works as expected.
In the settings telemetry window, the values provided by the ESC are displayed, but unfortunately not on the transmitter.
In the settings software HobbyWing V4 is selected, Kontronik ESC is selected in the transmitter and for testing Hobbywing ESC was also selected, neither of which shows anything.
Also still noticeable is the different RPMs displayed at some point between 2600 and 2700 RPM, when suddenly a lower value is displayed in the telemetry window, see screenshots.
OK, after a long search I found that there was a faulty pin in the Y-cable for the power supply to the receiver, I now have the following status:
The yellow cable of the ESC is connected to the PIT pin.
The modified integration cable is connected as prescribed.
Receiver is connected with just power (no data-line) of the BEC.
After switching on, the Spirit is initialized first, then the initialization of the ESC (3S-Lipo) is indicated by the triple beep.
Servos can be controlled, Governor works as expected.
In the settings telemetry window, the values provided by the ESC are displayed, but unfortunately not on the transmitter.
In the settings software HobbyWing V4 is selected, Kontronik ESC is selected in the transmitter and for testing Hobbywing ESC was also selected, neither of which shows anything.
Also still noticeable is the different RPMs displayed at some point between 2600 and 2700 RPM, when suddenly a lower value is displayed in the telemetry window, see screenshots.
I’m using Futaba telemetry with an Align 130A which is a rebranded V4 HobbyWing 130A.
I’m using a Spirit GT which requires a different connection than yours, but I have the same issue you’re having with the RPM value shown in the Spirit Settings Telemetry page, but the RPM readings shown in the Futaba Tx telemetry are correct though.
I’m using a Spirit GT which requires a different connection than yours, but I have the same issue you’re having with the RPM value shown in the Spirit Settings Telemetry page, but the RPM readings shown in the Futaba Tx telemetry are correct though.
I also have Spirit GTs with Hobbywing ESCs and Futaba and they work well. These helicopters are larger and have RPMs up to a maximum of 2400. In this context, the RPMs are displayed correctly in the governor window, in the telemetry window and on the TX. The problem seems to occur at higher RPMs.
In my particular case, however, the values are unfortunately not displayed on the TX.
In my particular case, however, the values are unfortunately not displayed on the TX.
If you have noticed that in your case it is displayed correctly up to 1200 RPM, in my case up to about 2600, then it seems to be a calculation error of the sensor value, possibly related to the number of poles.
However, if this behavior only occurs in the telemetry window, then I could live with it.
Now the values shown in the governor window would only have to be received correctly by the TX, then I would be satisfied. Unfortunately, the TX does not receive any data.
However, if this behavior only occurs in the telemetry window, then I could live with it.
Now the values shown in the governor window would only have to be received correctly by the TX, then I would be satisfied. Unfortunately, the TX does not receive any data.