Jaguar "Whiplash"

[Zme]

alright, this makes much more sense, i think we may have had one fail like this but never really bothered explaining why... is there a specific fault code/blink that this generates?

[Al Skierkiewicz]

When TI took over Luminary Micro, they dropped the use of Fairchild components and started using other devices. The black Jag uses an Allegro gate driver.

[s1900ahon]

Originally Posted by Zme

alright, this makes much more sense, i think we may have had one fail like this but never really bothered explaining why... is there a specific fault code/blink that this generates?

Yes, but the blink code depends on the firmware revision of the Jaguar in question.

In previous year's Jaguars, the over current fault was bundled into the standard fault and is slow blinking red. With revision 92 of the Jaguar firmware, this was changed to a slow alternating red/yellow blink (all other fault conditions generating the original slow red blink still). You can update older Jaguars to v92 using CAN.

[Zme]

for the over current fault yes but i was referring to the behavior described by 1075guy, is there a way to diagnose this as being the problem or is it simply a "it doesn't work right"

[Al Skierkiewicz]

Zme,
Not sure what you are asking. The gate driver failures in early production models did not show a fault indicator. They would either not drive in one direction or not drive at all. If the power supply was not affected by the failure, (some were) then the internals thought everything was fine. When Jags were first introduced, CAN was not allowed. So there was no way to get any info back from the device.

Scott,
Does the v92 firmware change the delay time for an overcurrent fault? That would be a handy change. Show the LED fault but let the Jag go back to output enable.

[Team2944]

Hey so I don't know if this will be any help, but if the issue actually is whiplash, I've made a quick little VI that when put between a joystick output and a drive input, will change the motor speed value at a constant rate in the direction of the joystick value. Since the rate of change is dependant on the time taken to complete the loop it's in, I've added another input kind of as a scaler. 2-4 seems to work nicely.