Adrianbb wrote: ↑Wed Mar 11, 2026 3:06 pm https://github.com/jsphuebner/stm32-sine

Ah, nice! Now I'm wondering how hard it would be to port to the SPC56 on the stock board...

Got this working, below is my python script:

#send_msg
# The CANlib library is initialized when the canlib module is imported. To be
# able to send a message, Frame also needs to be installed.
from canlib import canlib, Frame
import time

#CAN
ch_a = canlib.openChannel(channel=0)
ch_a ...

I am manually encoding the messages but unpacking using cantools and the DBC. Here are my two python files for setting the parameters and packing them. (You can check the attachement)

For the recording, I'll have to do it again, looks like I've done too much cleaning in my files ...

The exact ...

Quick update, I tried building the code from the github on PC and comparing the data I get with PrepareFHybrid (C++) and your prepare_pcm_pmz_f_hybrid (Python). I also made Python bindings from the C++ code and used them in Python (ValeoExt). I get this (with 0 for every signal):
C++ : 5f 00 00 ...

I am manually encoding the messages but unpacking using cantools and the DBC. Here are my two python files for setting the parameters and packing them. (You can check the attachement)

For the recording, I'll have to do it again, looks like I've done too much cleaning in my files ...

The exact ...

I may have thought of something stupid, but hasn't anyone thought about the alternative of using an openverter mini controller board instead of an oem MCU? Or if anyone has any other ideas...? Because from a realistic point of view, this playing with CAN won't hurt anyone, but it's a huge waste of ...

I am manually encoding the messages but unpacking using cantools and the DBC. Here are my two python files for setting the parameters and packing them. (You can check the attachement)

For the recording, I'll have to do it again, looks like I've done too much cleaning in my files ...

The exact ...

Thanks to uhi22 and bananaman for your returns :)

So yes, the CRC has been implemented and I think it works (at least for some frames) as I can change torque limits in the motor. One difference with the code proposed by squidopolis is that theirs uses another "magic byte" to add another ...

Hello everyone,

I hope some people are still around on this subject, I've got myself into reusing on of these iBSG alternators from Valeo as the main motor for a small EV.
I've got my hand on a 415005 / IBSG4W025 starter-alternator from Valeo (official product link : https://www.valeoservice.com ...

This should be every signal it extracts for what I'm calling the "main handler" (nr 3 in the table I posted earlier). These have not yet been double-checked so maybe there are mistakes.
Other messages are handled by different handlers with much more logic.

I cross-referenced with the vw_mqb.dbc and ...

I was also about to do the same but from mysupercarexpert.com - I'm surprised how many types there are.

Interestingly, going throughthe logs from bigmotherwhale Aug 30, 2023, not sure which test platform he used, but I can see in the logs clearly, that there seem to be at least two different ...

Thanks for the reply!
On the firmware okay, thats sad, haven't checked the law yet. Might also depend on the jurisdiction. May I asked did you dump it yourself off the board via JTAG or was advanced voltage glitching or so required to bypass security?

You didn't hear a click when replaying the ...

Hey bananaman, I'm also currently on the mission to figure out the CAN signals.
I have the 48V BSG 4N0903028R, but the replay that works for others hasn't worked for mine. I hear a click of a relay and increase in current consumption on 12V, but no rotation whatsoever.
Do you have a firmware ...

I had a quick look at some message handlers to see which signals they pull. Cross-checked with vw_mqb.dbc from opendbc when possible.
All little endian, start/len in bits:

0x40 : lots of bit operations, skipped for now. In DBC it looks like many airbag status/crash flags. Seems plausible ...

I had "broken down" mqb_dbc data for BO_168 = 0X0A8 as per the below.Hope it helps clear the way.....There is a counter with magic bytes in this message from what I gathered.

// Data structure for Motor_12 message
struct Motor_12_t {
uint8_t Motor_12_CRC; // 8 bits, CRC checksum [0-255]
uint8_t ...

I had a quick look at some message handlers to see which signals they pull. Cross-checked with vw_mqb.dbc from opendbc when possible.
All little endian, start/len in bits:

0x40 : lots of bit operations, skipped for now. In DBC it looks like many airbag status/crash flags. Seems plausible.

0xA8 ...

I was looking into the firmware to see which CAN IDs it expects. From the filtering it looks like the messages are going into 4 main handlers, and from there other handlers are called. I assume the main ones are for different purposes (diagnostics, normal communication, …).

I didn’t go very deep ...