SDU Commisioning whoess

[EV_Builder]

Ok guys my actual status right now.

I uploaded latest software R wich is 4.94.R-sine is that correct?

The accelerator pedal works as in pot1 and pot2 values seem to move.

I don't see the 'potnom' value it stays at zero so i don't like that.
Because it would be foolish to crank it up only discovering that its at a non zero value (albeit it displays zero) i would like to confirm it works.

second problem is that it says overcurrent.
and i cant remember if it started doing that after my firmware update (and reloading the config) or because i started the inverter in manual mode.

So i searched in the forum and found out that i needed to check some values:

(Board V6)

C5=1.69 (output curr sens 1)
C8=1.69 (output curr sens 2)
C11=0.04 (is this really still upperlimit it says so somewhere but 0,05 has been given as ballpark figure..)
C14=1.45 (lower limit)

R15=4.94 vdc
R7=1.99 vdc

R8=2.42K
R7=2.10K

Hope someone can step in and help me out.
I mounted the newly received current sensors (champfer facing outwards..)

[Isaac96]

4.94 is correct. Potnom won't change unless the inverter is in run mode IIRC, so that's fine.
Have you calibrated pot1 and pot2? Use pot1min, pot1max, etc to do that.

What is your ocurlim at? If it's too low that would do the trick. Also look at il1 and il2.

1.69 seems correct, usually 1.65 is the centerline but it's totally fine to be that far off and the software compensates for that.

What happens if you send "errors" in the command line? Do you get multiple errors and warnings back or just the overcurrent?

[EV_Builder]

4.94 ok txs

Potnom I don't agree that it's fine, but atleast it's the wanted behaviour then ( i want to check the throttle before i enable a device..)

Yes, i grabbed the values from the ''live'' page and wrote them down and filled them in the parameter placed.


When i start inverter manual mode the values change:

ocurlim = 1200amps
il1 and il2 are like 1400
udc = 2.09 and if i press the throttle it goes up to: 3.56 no clue wy...

din_ocur = Error (i guess 1400>1200??)

errors:

[500]: STOP - PRECHARGE
[223721]: STOP - OVERCURRENT

My feeling says all this came after my new firmware upload...

[EV_Builder]

Ok with ocurlim = 1500 i don't get an error so that means that the circuitry to the comparator seems to work then...

I plotted and logged the value its a dead steady 1404 and 1395 Amps for il1 and il2.
I fear something is broken there.

[Isaac96]

Hmm...
udc should not be changing with the throttle. Do you have any voltage connected there? (not sure how the SDU board does voltage scaling)
And il1 and il2 should of course sit at zero. So either you've got bad sensors or they're wired wrong (that might be it?)

If you need to you can definitely downgrade to an older version; there might be a bug in this latest version.

[johu]

Wait, have I destroyed manual mode? I changed offset calibration recently to get rid of spurious HICUROFS warnings. Yes go back to 4.90.R. Or start with digital start input, then switch over to manual mode.
There is always a bit of crosstalk on ADC channels, so udc going up 1V isn't too worrying.

[EV_Builder]

I went back to 4.90.R-sine...
And now it looks normal:
il1= 0.65Amps
il2=-1.31Amps...

Can i offset that?

Should be dead zero now....

[johu]

Good, will fix that asap.
ADC always jitters so will never be dead 0

[EV_Builder]

Well i must admit this is waaaay easier then hacking Tesla.

It works now!

Only thing i observed is that the 12volt consumption when pressing the throttle rises substantially (i hear my power supply's pitch lowering).

Only thing i got was an overvoltage shutdown while regen. I suspect that my used inductor/resistor inline did this!
(i used a 230vac water boiler element) so beware that it can damage the HV inverter part.

I once got a overcurrent i think to happy with the throttle but i did wonder wy we don't PI control the current (is that possible at all??!?)

HVIL is not bridged nor connected to anything (only the connector in the board) and the motor ran...

[johu]

The PWM is stopped when the there is no power demand. As soon as you slightly press it PWM starts and the gate drivers will pull quite some current to clock the IGBTs.

PI control would require FOC which further complicates things as you can see in the various sync motor threads.