Config help- desat-overcurrent

[zippy500]

I have a replacement leaf motor, I have had the inverter up and working previously.

I am trying to setup the syncofs again as it a different motor, no matter what settings I try I am getting,

[26107]: STOP - OVERCURRENT
[29663]: STOP - DESAT

I ran the test again without the 60v so I could view if the angle was being read, which it is, but I am still getting overcurrent and desat !!

any tips or advice I can try

Thanks

[Isaac96]

Hi,
Have you measured the signals coming out of the current sensors? Maybe a sensor is acting weird. I hope ocurlim is set nice and high? Although without power there should be no current...
Do the errors fire as soon as you start outputting power? Or are they always after a specific period of time? (same timestamp)

DESAT is signaled specifically by the power stage, not by current sensors. I'm not familiar with the Leaf board but it probably connects the Nissan desat signal to the desat input on Johannes' board. Maybe the Nissan board is annoyed that it isn't getting enough voltage?

-Isaac

[zippy500]

When first power up the board there are no errors

When I press manual start, I can hear PWM , but any config settings with the 60v and its stops.

[zippy500]

went to have anther go, removed inverter cover, re-seated all the plugs and v3 board

Have set manualid to 1amp , getting the same errors.

when i scrolled down to the mapping UDC is 50.06 but my DMM is showing 64.1v would this be a issue ?

The inverter was working perfectly before, I dont know what has changed

[zippy500]

even without any HV connected, the inverter is tripping out on DESAT and OVERCURRENT

any ideas anyone ?

[johu]

What is the value of din_desat before and after the trip?

[zippy500]

When I power the inverter and plot din_desat status OK with plot 1
after tripping din_desat Error with plot value 0

I reinstalled the firmware and leaf config file, but error is the same

[johu]

Ok, so it really is throwing desat. So the route is
- 2 error signals are generated on the Leaf driver board (probably desat and something else)
- The signals are high when all is good
- They travel via CN501 to the adapter board
- Here they hit a 1k pull-down resistor each (R9, R10)
- Then they enter the NAND gate 74*00 on pins 1 and 2
- The NAND function exits on pin 3 -> must be low when all is good
- The signal is inverted and exits on pin 11 of the 74*00 -> must be high when all is good
- It then enters the mainboard where you can test it to the right of C38 -> must be high when all is good

So now you can trace out the signal path and check whether the signal is lost on the way. Otherwise it might be falsely generated by the driver board itself in which case you'd be on your own to find out why. Desat detection works by injecting a small test current to the collector of the IGBT and testing the voltage against some threshold. If the connection to the collector is broken, desat is asserted as soon as you try to turn on the IGBT. Maybe that helps.