Okay, I'll look into that to get that issue sorted.
In the meantime I read the STM32 reference manual section on the timers and specifically the PWM settings.
The idea was to understand the meaning of the code in the hwinit.cpp.
I started experimenting with replacing some of the settings and finally ...

Python 3.10.12 is installed as confirmed by "python3 -V"

Not sure if this is in anyway related, but when I cloned the repository, the magical "make get -deps" command resulted in some errors, so I just copied all the internals of the related libopencm3 and libopeninv folders from a working Zombie project. At least the compiling started working like that ...

Moving on from obsticle to another. Now the inputs seem to work, but I get no PWM output.
I have active low setting, so in off-mode the PWM1-TOP is high. When the system goes to run-mode, PWM1-TOP goes low and stays there.
It even stays there if I artificially generate a current sensor value higher ...

So, as the precompiled FW was acting strange, I reverted to playing around with the one that I compiled myself.
I was suspecting the IIR filter function and took it out from the current value.
Sure enough, I started seeing values in RUN mode. Then I noticed that for some reason, I had a negative ...

Binary attached.


Flashed in that FW and now my Web interface is showing strange things:
When I apply voltage to IN_START -> din_emcystop goes "on" in the spot values.
When I apply voltage to IN_EMCYSTOP -> din_ocur goes "on" in the spot values.
soc is showing the LV supply voltage.
I have 10V ...

Is it possible that something goes wrong in my compiling?
Can somebody attach here a precompiled bin?

As I wrote. Goes to run mode and there are no errors, but still no current reading.

Code is here: https://github.com/jsphuebner/stm32-charger


I am trying to make a buck charger with this code, but I cannot get any reading from IL1 nor IL2 to the spot values.
I have IL1 and IL2 connected together and I am just supplying a variable voltage from a benchtop PSU to verify that I ...

Perfect :) please continue to do some testing and let me know if you can break it ;)


I think I found some sort of a bug...
During a long charging session, the charging power stops following the request intermittently, for a very long time and then at some point it starts following the request ...

Bench test confirms errors in my population of voltage and current into the BMS spoof message, will fix now.

EDIT
Update for fixing the mapping issue, will review logs to see if anything else is not behaving. But if you get a chance it be good to test with this change.

https://github.com/Tom ...

This is captured in your log? I will compare this situation to my code log and analyze.


No, it is not in the previous log of your V2.22A, but I went and took a datalog for you.

This is the datalog of the Main branch V2.20A FW with my changes to the Stm32.ccp to execute the Inverter 10ms task ...

Good evening. I hate to bring bad news, but after testing a bit further, I have to say we still have issues.
Now the charging mode activates consistently and the charging power starts to flow, but only at a very low level and the power does not follow the request according to the parameter Pwrspnt ...

I was too curious to know, so I had one more go at it now, that I am actually compiling the correct version...
And sure enough - Driving and Charging both work! :D
Here is a datalog of the operation.
- Starting the datalog first and then applying the permanent 12V power
- Going into RUN-mode and ...

I am really a Github n00b and for that reason I made a mistake in the cloning.
I was compiling the default branch, hence missing the whole LeafMng...
Now I cloned with the -b extension and double checked that I have all the newly added files.

Not sure if I still have time to test today, but just ...

Now I just cloned and directly compiled your V2.21A without any changes.
The first log is...
- Going into RUN-mode and spinning the motor (works fine)
- Going into OFF-mode and waiting a few seconds (>10 sec)
- Plugging in the charger and waiting a few seconds (System goes into charging mode, but ...

Okay. I'll make a new test, but this time without my changes.

Okay, I will do that.
How long should I wait after switching off from RUN mode, before I plug in the charger?

Thanks for taking the time to investigate this issue, Tom.
I cloned your latest FW and made my changes to cope with my setup, then went ahead and tested.
Driving works, then I went to off-mode and wait several minutes to make sure all units are sleeping.
Then plugged in the charging. Pre-charge ...

I think you are on the right track on this issue.
I forgot to mention in my earlier post, but the problem seems to only be the startup of the PDM into charging mode. Once the EVSE relay is closed and charging power is flowing, the PDM does not need the inverter 10ms task. I confirmed this by ...

Here is a datalog of a successful charging event after a hardware reset with the above described code modifications:

I have found an intermediate solution to my issue of not charging.
This is how my Ms10Task in the stm32VCU.cpp looks like:

if (Param::GetInt(Param::opmode) == MOD_RUN) //!!!THROTTLE CODE HERE//
{
torquePercent = utils::ProcessThrottle(ABS(previousSpeed)); //run the throttle reading and checks ...

Probably your issues are originating from these (which have already been pointed out):
1. Improper fixing of the diff (this however is propably not the source of vibration)
2. Universal joint fixed onto a rubber bushing (U-joints should always be used in pairs and the alignment of the input and ...

Here you go. The PDM wakeup is there in the log.

tom91 wrote: ↑Sat Jan 04, 2025 4:25 pm Can you please turn off the Inverter parameter (only change besides the nissanPDM.cpp) and grab me a log of trying to charge?

I went ahead and did this, but as I suspected, with the Leaf INV required for DC-link voltage measurement in my setup, I get a pre-charge fail.