Eltek/Volvo charger

[boekel]

Does anyone know the type of the small 3 pin connector? 3mm pitch seems the same as Molex Micro-Fit but the lock is on the side...

20220509_153604.jpg

20220509_153547.jpg

20220509_153558.jpg

To answer myself: the Molex micro-fit fits fine, only the lock is on on the wide side instead of on the short side.

[tom91]

I created a simple bit of code to run on a Teensy 3.2

https://github.com/Tom-evnut/Eltek-Charger-Programming

This checks the canbus (at 500kbps) for an Eltek charger ID and then lists them out for your viewing pleasure.
Utilizing the menu you can set which ID to change to a New ID and then send the command with one simple request.

Currently the code works on the bench but not proven with an actual Eltek charger.

[tom91]

I successfully changed charger address from 1(default) to 2 which is shown in charger reports. Before charger would report on 0x301 address and now it uses 0x311!

do you have a canbus capture of you doing this as I cannot get this working.

[arber333]

I successfully changed charger address from 1(default) to 2 which is shown in charger reports. Before charger would report on 0x301 address and now it uses 0x311!

do you have a canbus capture of you doing this as I cannot get this working.

I have some photos, but it is not hard.
You just need to set your interrupt telegram ("sendCANframeURGENT" in my code) to send out trigger msg every 800ms (less than 1s). This will open Eltek to address change. Then you introduce a trigger message ("sendCANframeB") where you command the next address (or CAN speed change). I use a simple push button to gnd on specific pull_up pin for this.

After your attempt you need to disconnect charger from AC and DC voltage for changes to have effect.

See

[tom91]

I have some photos, but it is not hard.

Must be something to do with the chargers that Boekel is trying to change then.

My code does exactly same thing as yours even checked it on the bench with savvy can monitoring.

[arber333]

You could try changing protocol from oem to eltek with telegram 0...

[arber333]

I have some photos, but it is not hard.

Must be something to do with the chargers that Boekel is trying to change then.

My code does exactly same thing as yours even checked it on the bench with savvy can monitoring.

Mhm... i seem to remember i had problems using hex data values. Ie.: manual asks to send data value 1 through 4 for different function changes and i tried to send 0x04. But charger would not accept change.
Out of frustration i setup my DUE to just send intiger value 4.
And it worked! Must be additional protection from unintended changes?

[tom91]

It all of sudden decided to work. This is quite confusing but it finally has worked.