Home Forums General Discussion Technical Questions swift futura error message

I have a swift futura that indicates "Overload" on the diagnostic screen display.
the car will not run f[rom the machine room on inspection or normal. I have checked the load weighing overload input, from the tocc board and it is not on.
I have checked the GPI1 led on the spu link thinking that maybe a thermal sensor in the system had tripped. the led is on. does anyone have any ideas?
I also turned off bit 9 of CS7 , which disables the loadweighing overload input thinking that maybe the input board was bad or the cpu was bad, but no luck.

Hey Scott, I think I've had this one before. If I remember correctly I had to replace the SPU link.

thanks lift-tech, i was leaning towards replacing the spu link also, but something about the car not running on inspection bothered me. I looked at the actual error codes, and was getting a code that said there was a problem with the door and and gate lock bypass circuit. the input module for the door and gate lock bypass was defective. Just so you know, if you ever see OVERLOAD on the diagnostic screen it doesn't necessarily mean overload condition literally, it is a generic display, that indicates some kind of abnormality with the inputs to the system.

The SPU link causes many "unrelated problems", unfortunate its such a weak link, can drive you nuts

A few checks:

This is a common problem on new controller start ups. Check your bits on CS8. Command BITD
If you are using a brake switch, you must have your brake switch bits in status word 8 set properly depending of your brake switch is normally open or normally closed.

As a check you can set cs8 to 8hex and see if the problem goes away. Type cs8=8h then WRT to save it.
This effectively makes the system ignore a brake switch.

Also make sure your rope gripper is not causing problems if you have one. Some of the jobs around the early 2000's had not incorporated all the now redundant checks that CEC provides around the rope gripper circuit. GTS module must be active for you to run. You should get different errors on newer jobs.