ZeXx86 wrote:
Thank you for the details.
Well, I am relatively sure that the issue is not in the unit itself. If so, it would not work in any configuration correctly.
What can help is trying to find any difference between setup that works and that does not work.
For example CC cable, BEC voltage, throttle frequency, additional telemetry sensor.
The issue could be on two sides:
a) ESC signal for telemetry and throttle
b) Futaba SBUS2 data processing
Since it does not work correctly just with SBUS2 connection, I guess that it is second option.
In this case a FASSTest modulation, channel assignment, telemetry sensors (if connected) or FrSky cable could make a difference.
FrSky cable is rated for 15V.
1) I tested with Agena BEC from 5V~8.4V (no difference)
2) I tested with difference FrSky modded cable (no difference)
3) I have external voltage telemetry (no difference) / I turned transmitter side telemetry off (no difference)
4) Freqency used are both 200hz. (I've tested with all range and showed same results -- oh when it is 60hz, there seem more ticks)
for channel assignment
- If you mean channels assignment inside of spirit, I may turn a few last channel off after setting in one heli.
(so it's not exactly same but it supposed to be working
, could it make any difference?
- If you mean telemetry channels... I didn't count every log fields but its ch0~ch16 + 8 ESC value fields
(I think it's same, I will check later)
for FASSTest modulation
- It is beyond my boundary. But I used same SW version.
I lost from here If you say HW is okay.