Page 2 of 3
Re: Spirit Telemetry no current and capacity
Posted: Sun 04. Jun 2017 20:52:22
by Adrian
I'm speaking about the Data wire, not hole data Cable.
So, test it without fan, as you did with the Data cable, but take black and red wire pin out of the socket. So there is only the yellow data wire on the right plugged in (S). Make sure you isolate the pins you took out. Pins can be taken out with a needle to lift the little plastic lip and pull gently on wire.
I don't know if it really helps, maybe Tomas can comment, but that's how I use it.
Re: Spirit Telemetry no current and capacity
Posted: Sun 04. Jun 2017 21:02:39
by Scout
I dont know if i get this right I'm sorry

I should unplug the fan completely than plug the Telemetry Cable in the Dataport of the ESC but only with the yellow wire?
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 8:49:22
by Adrian
On the left what you should do for testing with only Telem UNI Data Cable using it's data wire.
On the right my final cabling, where I just extended the yellow data wire from Spirit Telem UNI cable into the fan port.
Telem UNI cable
http://store.spirit-system.com/en/acces ... cable.html
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 12:24:26
by Scout
Did not work
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 18:02:59
by Scout
It seems like the hobbywing is the problem.
I asked in a german forum and there are some People who have the same problem.
https://www.rc-heli.de/board/showthread.php?t=260688 this is the thread if you guys are interessted and understand german

Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 20:37:35
by Adrian
Looking at the German Forum (I'm Swiss) they think it's a Hardware issue with HW160A also based on JLog experience.
Lets compare:
On Spirit I'm running FW 2.4.1
I have HW 160A HV
Hardware Version: HW160_V1.00456NB
SW: PL-04.0.06
Not that this Hardware Version numbers means anything to me but we might be able to compare and we find a pattern.
Beside, you mentioned my proposal with Data wire only is not working.
Do you mean not working at all or does it not give better results?
regards, Adrian
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 21:11:10
by Scout
Looks quite identical.
Your proposal gave exactly the same result as the Y Cable, so current much to low all the time.
I tried the spirit correction factor (I-motor shunt) today,
hovering with 1500 rpm 0 amps
hovering with 1700 rpm 0-4 apms
hovering with 2100 rpm about 6-9 amps
Pitchpump with 2100 335 amps
So complete nonsense.
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 21:34:49
by ZeXx86
This is really strange. It really seems to be a hardware issue as it is working well with other identical ESC.
We will contact Hobbywing and ask how this could be possible.
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 21:49:42
by Scout
If found some guys in german forums who have the same problems with their JLog, i found one post and in this someone said he had Firmware 05 and it didn't count right, than he downgraded to 04 and it worked.
And in the forum I've linked some posts ago there are 2 guys who couldnt solve the problem.
I have no idea whats wrong with this ESCs but I'm not the only one with this issue. Maybe there was a bad batch with wrong calibrated sensors or something like that...
I've already contacted Hobbywing aswell, they said that they have to ask some technicians first and than they will tell me what i have to do.
But i guess they will be even keener to find it out when a developer like you asks them.
Re: Spirit Telemetry no current and capacity
Posted: Mon 05. Jun 2017 22:54:11
by Scout
Scout wrote:
Looks quite identical.
Your proposal gave exactly the same result as the Y Cable, so current much to low all the time.
I tried the spirit correction factor (I-motor shunt) today,
hovering with 1500 rpm 0 amps
hovering with 1700 rpm 0-4 apms
hovering with 2100 rpm about 6-9 amps
Pitchpump with 2100 335 amps
So complete nonsense.
Oh I forgot to mention that this values were with correction factor 300%...