Il1 Il2 input does not display any data

[lumax]

Hi guys,

I did the UDC calibration without any trouble, but Il1 And Il2 input does not read any signal (Start 2 mode)

I use LEM current sensor HC5F700-S (from BMW IGBT driver board) the output of this sensor is 0-5V (2.5V=0A) so I build a voltage divider to lower the voltage 0-3.3V to interface with the Hubner V3... But what ever I tried, this the only reading I got

Il1 stuck to -2.93
Il2 stuck to -1.15

I tried to connect il1 and il2 input to my lab PSU, from 0 to 3V I got no reading at all... Do I'm missing something... ???

[Isaac96]

Hi,
After sending the start 2 command can you send 'get opmode' to the board?
This will make sure it's actually in the running mode. The UDC does not care about the mode, but IL1 and IL2 do. If opmode stays at 0 then send 'errors' and it will tell you all the errors that have happened.

I'm not sure where to measure the incoming voltages on the V3 board, maybe poke around carefully with a multimeter on the comparator? If you look at the schematic and at the board you can find where the current sensor signals go, and make sure they are actually changing.

-Isaac

[lumax]

Thanks Isaac,

Your bet was right...
Opmode = 0.00

Errors:
501 Stop - precharge
4070 stop - mprot
8 warn - hicurofs 2
8 derate - tmphsmax

[johu]

Seems not much is connected to the board? https://openinverter.org/wiki/Errors

Go over these procedures to get going: https://openinverter.org/wiki/Schematic ... structions

[lumax]

Yes, I figure it out...
I followed the procedure but I was not aware that the hardware shutdown pin was enable in start mode 2... my mistake!

Thanks Guys!

[lumax]

Now i'm stuck to the gate driver test procedure (output clean 50/50 duty cycle)...

set fslipspnt 1 ... return (unknown parameter fslipspnt)
set ampnom 1 ... return (value out of range)

[Isaac96]

Okay if you're in start 2 mode that should not be happening. Are you using the ESP8266 or a serial monitor program? You might have a strange newline or carriage return on.

[lumax]

I'm using ESP

[lumax]

It do the exact same thing with the serial terminal

[Isaac96]

Are you using the sine or FOC firmware? That's all I can think of...
-Isaac

[lumax]

Latest FOC

[Isaac96]

Okay so the fslipspnt and ampnom are parameters for the sine software, not the FOC version.
I'm not familiar with FOC, maybe check the wiki pages or look at some threads here.
-Isaac

[lumax]

Exactly, it seem that they are not implemented in the FOC firmware
I flashed it with the sine version and they do work, but I got no pwm at the output... I still have 2 warnings (pwmstuck) and (lowresamp), more time and investigation needed...

Thanks for your help, this is much appreciated !

[Isaac96]

Pwmstuck seems to happen whenever it wants to. Lowresamp also shows up when it feels like it. Do you have a resolver connected? If so try rotating it a bit (just turn the motor a few degrees) and see if the error goes away.

[johu]

PWMSTUCK shows up a bit randomly when using a line driver between processor and gate driver (like on Tesla boards). It might also show when no gate drivers are connected. And it might show when the STM32 has slight ESD damage on the output drivers (such a thing seems to exist). What it means is that the floating pins are not at GND level at startup. Can be completely irrelevant indeed.
LORESAMP has recently been improved upon but it will of course show up when no resolver is connected and you selected resolver mode.

I edited the wiki instructions that the steps will only work with the sine software. didn't think of that!

Finally I thought about the V3 kit. It has voltage dividers on the current sensors both on the little sensor boards themselves AND on the mainboard. Might be worthwhile to bypass them (remove R2, bypass R1).

[lumax]

Isaac, the resolver is not yet connected, might be the problem...

Johu, I'm not using the small current sensor board, I use the original BMW LEM current sensor and gate driver, so I should be good with the main board voltage divider... by the way does the pin 17 is still used in both FOC and SINE newest firmware or I can get rid of it?