bigmotherwhale wrote: ↑Fri Sep 29, 2023 2:25 pm
Bodge completed however I want to have a good look over the gate driver again to see if all the transistors are OK before its powered up.
Hi Bigmotherwhale,
Mind sharing the pcb/schematics?
I also suffered from the dead-alternator message today!
Would be great to see details and or find a working solution
I believe so, at least some of them should be similar or better than original.
I did some research in Chinese, the repair guys seems to really like this as they do not fail again as often compare to if you just put another OEM one back in.
hi has anyone made progress on this, im building an autonomous Ami and can control the motor but need help with the CRC check as this is causing some problems
it uses an IBSG just like the vw/audi
messages are send to address 0x3c0, byte 0 is CRC byte 1 is cyclic for the first half of the byte (0 to F) and the is enable signal byte 6 is forward/reverse (3f/40) and byte 7 is throttle 0-100 for forward and 100-0 for reverse.
this is known values motor idling
26 01 00 00 3f fe 3f ff
eb 11 00 00 3f fe 3f ff
a1 21 00 00 3f fe 3f ff
6c 31 00 00 3f fe 3f ff
35 41 00 00 3f fe 3f ff
f8 51 00 00 3f fe 3f ff
b2 61 00 00 3f fe 3f ff
7f 71 00 00 3f fe 3f ff
00 81 00 00 3f fe 3f ff
cd 91 00 00 3f fe 3f ff
87 A1 00 00 3f fe 3f ff
4a B1 00 00 3f fe 3f ff
13 C1 00 00 3f fe 3f ff
de D1 00 00 3f fe 3f ff
94 E1 00 00 3f fe 3f ff
59 F1 00 00 3f fe 3f ff
hopefully someone can help with figuring how the checksum CRC is calcuted
Nice, im glad someone has made progress, there is always the problem of finding a can log from a working car. I have a Valeo one from a different model, i wonder if the message structure is the same. What does the unit transmit over CAN when powered?
the one i have sends these messages:
00000190 8 10 92 a0 48 04 70 00 09
00000192 8 00 00 00 00 00 00 00 6a
00000193 8 00 00 00 00 00 00 00 6a
golfdubcrazy wrote: ↑Wed Apr 16, 2025 1:59 pm
hi has anyone made progress on this, im building an autonomous Ami and can control the motor but need help with the CRC check as this is causing some problems
it uses an IBSG just like the vw/audi
messages are send to address 0x3c0, byte 0 is CRC byte 1 is cyclic for the first half of the byte (0 to F) and the is enable signal byte 6 is forward/reverse (3f/40) and byte 7 is throttle 0-100 for forward and 100-0 for reverse.
this is known values motor idling
26 01 00 00 3f fe 3f ff
eb 11 00 00 3f fe 3f ff
a1 21 00 00 3f fe 3f ff
6c 31 00 00 3f fe 3f ff
35 41 00 00 3f fe 3f ff
f8 51 00 00 3f fe 3f ff
b2 61 00 00 3f fe 3f ff
7f 71 00 00 3f fe 3f ff
00 81 00 00 3f fe 3f ff
cd 91 00 00 3f fe 3f ff
87 A1 00 00 3f fe 3f ff
4a B1 00 00 3f fe 3f ff
13 C1 00 00 3f fe 3f ff
de D1 00 00 3f fe 3f ff
94 E1 00 00 3f fe 3f ff
59 F1 00 00 3f fe 3f ff
hopefully someone can help with figuring how the checksum CRC is calcuted
Wow this is good progress. I’ve been busy with life and haven’t gotten a chance to mess with it much.
golfdubcrazy wrote: ↑Wed Apr 16, 2025 1:59 pm
messages are send to address 0x3c0, byte 0 is CRC byte 1 is cyclic for the first half of the byte (0 to F) and the is enable signal byte 6 is forward/reverse (3f/40) and byte 7 is throttle 0-100 for forward and 100-0 for reverse.
...
hopefully someone can help with figuring how the checksum CRC is calcuted
If we have more data with different content of the same message, it should be not to difficult to find out and verify the CRC calculation. I did this recently for two tesla and one VW message https://github.com/uhi22/tesla-crc
and most likely the 3c0 follows the same schema just with other magic bytes.
