Home Forums General Discussion Technical Questions ovf 30 drive

anyone ever have a F39 fault on a ovf 30 drive.

had an intermittent F10 fault to begin with, car would run a few days and get F10.
we sent drive in for repair, they replaced the current sensors in the drive and after sending back and me installing, the drive fires up, brake picks and instantly drive faults on F39. repair shop is saying it is not the drive, however the car was running before it was sent in, so I'm leaning on something happened in repair shop that made it not able to run. unless I'm missing something. any ideas

F39 Bases Dropped

The DSP sends a bit to the host which indicates whether the IGBT bases are enebled or disabled, i.e. whether or not the transistors are allowed to switch. Once PTR is received, the bases should be enabled and remain enabled until the end of the run. This fault is declared if for some reason the transistors bases enable line is inhibited by the DSP in a drive state where the bases should be enabled.

I think the repair shop made a mistake...

thats what I'm thinking, the fault sounds like the drive mode should enable the bases , but for some reason, the dsp is disabling them, ha ha i like the line " for some reason" the enable line is inhibited. I'm just hoping the "some reason" isn't something I'm missing, but the car was running, so hopefully the "some reason" is the repair shop mishap.

maybe the software in dsp was damaged under the repair? (static discharge). If you have another drive, try swapping the eproms...

sent it back, if it still does not work when it gets back, i will try to swap dsp board with another car. Any issues if i swap dsp boards?

if the machine is the same, it should not be a problem. But there is always a chance it will run in the wrong direction...

Drop me a pm if you want the parameter doc...

Check the plug on the bottom left of the LVIB. It has red and black wires. If it's plugged in on the board, open the drive and make sure it's plugged in on that board. Had same problem and the shop left it unplugged on both ends.

Never mind I missed where you said sent it back.

thanks guys, got the drive back it works fine now, strange they only had it back for 1/2 day. he originally replaced one current sensor , and said all was good, now he indicates that he replaced the entire board that has the 3 current transformers on it. any way it runs. another question though, we have 6 CARS, I WAS writing down all the drive parameters on the other cars and came across a car that was running with the drive indicating drive fault, check m421 for the error , the error is F58 E2 checksum error.
i reset fault with reset fault on drive to see if i could clear it, cleared the event list, but the fault came up again, can't clear it. strange the car runs fine . any ideas?

That is good news! Thanks for letting us know the result!

F58 E2 checksum err (Fault Severity Level 1 = Log only)

On power-up and after each EEPROM parameter change the 80186EC Host performs a checksum test on its EEPROM. If the test fails, this fault is declared.
---------------------------------------------

Replace the EEPROM when you have the opportunity....

It's a perameter out of range. Sometimes happens if you adjust the pretorque trim or inertia to reduce rollback. I have a building with two units both have that fault but run fine. one of these days I'm gonna go thru all the parameters and compare them to the originals.

I have seen this before, units runs fine with the fault, but when you get "BadE2P" error at same time, all sorts of things can happen. I/O coding can change as well as install parameters...

thanks guys for the input. if i get a breather, i may dig into it further, but for now, have 12 down cars to deal with.