openinverter forum

Documentation error! Enable Bit and Soc must be moved one byte up. So Byte 5 and 6 not 4 and 5. For all versions > 1.06.R

What's 0x3D8?

johu wrote: ↑Wed Aug 03, 2022 9:08 am Documentation error! Enable Bit and Soc must be moved one byte up. So Byte 5 and 6 not 4 and 5. For all versions > 1.06.R

That explains that!

Now I have canenable = 1 and enable = 1, good so far.
But state=off (and proximity is off)

Can it work without the J1772 signals or is this a bad exercise? Version is 1.16.R

Thanks!

Need to select inputype=Manual(-3p) then

johu wrote: ↑Wed Aug 03, 2022 1:39 pm Need to select inputype=Manual(-3p) then

Will that give me the automatic 3 phase selection though!?

OK, one more question.
I tried to go back to stand-alone operation (cancontrol off and terminator link in place), and it no longer works. I have enable=true, proximity=true and EVSE and cable limits are sensible. But mode stays at “waitstart”. What does this indicate?

et0 wrote: ↑Wed Aug 03, 2022 7:20 pm Will that give me the automatic 3 phase selection though!?

No, you're right. Would need another mode Manual-Auto (weird name, huh)

et0 wrote: ↑Wed Aug 03, 2022 7:20 pm OK, one more question.
I tried to go back to stand-alone operation (cancontrol off and terminator link in place), and it no longer works. I have enable=true, proximity=true and EVSE and cable limits are sensible. But mode stays at “waitstart”. What does this indicate?

That would be caused by timedly. Is it >0 ?

2 settings one for auto 3ph and one for auto / manual CP / PP

johu wrote: ↑Thu Aug 04, 2022 12:11 pm

et0 wrote: ↑Wed Aug 03, 2022 7:20 pm Will that give me the automatic 3 phase selection though!?

No, you're right. Would need another mode Manual-Auto (weird name, huh)

I guess we are being too ambitious. I will leave it configured "stand alone" for now, and just cut the enable signal to the charger when the BMS detects end of charge conditions.

et0 wrote: ↑Wed Aug 03, 2022 7:20 pm OK, one more question.
I tried to go back to stand-alone operation (cancontrol off and terminator link in place), and it no longer works. I have enable=true, proximity=true and EVSE and cable limits are sensible. But mode stays at “waitstart”. What does this indicate?

That would be caused by timedly. Is it >0 ?

It is -1.
I have tried it at 0 also, same result, stays on WaitStart
All the Cxxx variables show 0, so I wonder if the board is actually talking to the modules. Any way to tell that?

Must have messed up that new function. Try the attached binary.

johu wrote: ↑Thu Aug 04, 2022 12:33 pm Must have messed up that new function. Try the attached binary.

Awesome, thanks for the quick action Johu, I'm away for the next couple of days but will try this as soon as I get back on Tuesday.

Alright cool. And thanks for clearing up the CAN instructions

OK - new update installed. Same behavior though - staying at WaitStart.

Just to reiterate, it did work correctly "out of the box", and after that I tried setting up CANBUS and updating the firmware,so either some setting is incorrect now or the charger or control board has broken.

edit: I loaded the .bin file from the thread title post, dated 05/03/21 - this works. So I guess still some problem with the new FW?

edit 2: OK with the new FW, and "timedly" set to 1, it does wait 1 minute and then start!

I'll work back towards CAN control during the week.

Managed to install this firmware and eneble wifi. Charger started and works, yay! But hang on... i see that darn 13.3A limit per module again. The same as with open firmware. Anyone knows if this limit is caused by the cable or is it set inside charger? Is it possible to reset this to 16A per module?

EDIT: I checked with another cable, both of them have PP-PE resistance 220R = 32A limit! That shouldnt be the case then...
also i tested various charging stations and i see the same result. 13.3A AC limited modules. I want 16A!!!

What is hwaclim? It is currently sitting at 13.3A. Can it be changed anyhow?

Attached is a CAN log of charging session with alternative firmware. Byte numbers are left to right.
I am also posting here a section from one x109 telegram to the other.

2 53:12,8 0xA6CE2 109 8 x| 00 00 05 00 00 01 81 00
3 53:12,8 0xA6CE5 108 8 x| 00 00 00 00 2D 01 AC 00
4 53:12,8 0xA6CE7 368 8 x| FF 40 0C 00 11 29 49 03
5 53:12,8 0xA6CE9 043C 8 x| 00 00 00 FE 4E 00 BB 42
6 53:12,8 0xA6CEC 044C 8 x| 00 00 00 FE 4E 00 BB 42
7 53:12,8 0xA6E0F 349 8 x| 00 00 00 00 00 00 00 00
8 53:12,8 0xA6E11 209 8 x| B6 A0 00 C8 D5 F2 EC 76
9 53:12,8 0xA6E14 229 8 x| D1 EC 00 00 8E 98 A3 6E
10 53:12,8 0xA6E16 239 8 x| 00 00 00 00 00 00 41 47
11 53:12,8 0xA6E18 249 8 x| 00 20 00 05 39 F7 7D 44
12 53:12,8 0xA6E1B 347 8 x| 00 00 00 00 00 00 00 00
13 53:12,8 0xA6E1D 207 8 x| B6 A0 00 C8 DB 32 F2 79
14 53:12,8 0xA6E1F 227 8 x| D1 EC 00 00 8F 26 A8 FF
15 53:12,8 0xA6E22 237 8 x| 00 00 00 00 00 00 41 47
16 53:12,8 0xA6E24 247 8 x| 00 20 00 05 65 F6 7D 44
17 53:12,8 0xA6E27 467 8 x| 00 00 00 00 00 00 06 17
18 53:12,8 0xA6E29 469 8 x| 00 00 00 00 00 00 06 17
19 53:12,8 0xA6E2B 717 8 x| 00 00 00 00 00 00 00 19
20 53:12,8 0xA6E2E 719 8 x| 00 00 00 00 00 00 00 19
21 53:12,8 0xA6E72 359 8 x| 00 00 00 00 00 00 00 00
22 53:12,8 0xA6E7E 357 8 x| 00 00 00 00 00 00 00 00
23 53:12,8 0xA6E9C 034B 8 x| 00 00 00 00 00 00 00 00
24 53:12,8 0xA6E9E 020B 8 x| B6 A0 00 C8 E2 32 EE 77
25 53:12,8 0xA6EA0 022B 8 x| D1 EC 00 00 8E 7A A5 BD
26 53:12,8 0xA6EA3 023B 8 x| 00 00 00 00 00 00 41 47
27 53:12,8 0xA6EA5 024B 8 x| 00 20 00 05 49 F7 7D 44
28 53:12,8 0xA6EA7 046B 8 x| 00 00 00 00 00 00 06 17
29 53:12,8 0xA6EAA 071B 8 x| 00 00 00 00 00 00 00 19
30 53:12,8 0xA6EAF 217 8 x| 00 02 92 96 01 7F 00 39
31 53:12,9 0xA6ECB 219 8 x| 00 03 92 94 01 00 C0 39
32 53:12,9 0xA6ED6 329 8 x| 00 00 00 00 00 00 00 00
33 53:12,9 0xA6EE2 327 8 x| 00 00 00 00 00 00 00 00
34 53:12,9 0xA6EFF 035B 8 x| 00 00 00 00 00 00 00 00
35 53:12,9 0xA6F39 369 8 x| 00 00 00 00 00 00 00 00
36 53:12,9 0xA6F45 367 8 x| 00 00 00 00 00 00 00 00
37 53:12,9 0xA6F4D 021B 8 x| 00 04 92 94 00 81 00 39
38 53:12,9 0xA6F62 032B 8 x| 00 00 00 00 00 00 00 00
39 53:12,9 0xA6F9C 379 8 x| 00 00 00 00 00 00 00 00
40 53:12,9 0xA6FA8 377 8 x| 00 00 00 00 00 00 00 00
41 53:12,9 0xA6FC6 036B 8 x| 00 00 00 00 00 00 00 00
42 53:12,9 0xA7029 037B 8 x| 00 00 00 00 00 00 00 00
43 53:12,9 0xA70C0 045C 8 x| 8C 90 00 00 2E 14 A4 10
44 53:12,9 0xA70C2 042C 8 x| 00 00 00 FE 4E 00 BB 42

hwaclim is received from the charger and supposedly is the upper limit of AC current. I would have to change the scaling factor to change its value but I'm not sure if that actually ups the power or if 13.3A just IS the limit

johu wrote: ↑Mon Aug 15, 2022 5:25 pm hwaclim is received from the charger and supposedly is the upper limit of AC current. I would have to change the scaling factor to change its value but I'm not sure if that actually ups the power or if 13.3A just IS the limit

Only one way to find out .
My car is open at the back and i have as good access to the charger as i will ever going to have.

I managed to reflash charger board and enter your key. Charger works and i get CAN reports as well.
But hwaclimit remains at 13.31 as well aas normal aclimit at 13.31. It doesnt matter that i have aclimit set to 16A or at 25A.
Cable and EVSE setting is at 32A.
@Johu, is it possible to set a parameter in code so we can tweak that hwaclimit as a parameter in wifi interface?
I would volonteer to test this and report back.

Later on you could also put a conditional loop in code to keep calculated hwaclimit from over 16A ever ...

This one has hwaclim completely ignored

johu wrote: ↑Tue Aug 16, 2022 5:27 pm This one has hwaclim completely ignored

Tnx
I uploaded and set ac limit to 32A. Again i got hwaclimit reported at 13.31! Dc current was at 20A, voltage at 400Vdc.
Would that mean Elon set my charger to lower value?
How is hwaclimit taken anyways? Is it possible to reset it?

hwaclim is received via CAN from each module. It cannot be changed.
So yes you'll still see 13A but it is ignored and will no show up in aclim
If this didn't do the trick then the modules simply ignore any value above hwaclim

johu wrote: ↑Tue Aug 16, 2022 6:32 pm hwaclim is received via CAN from each module. It cannot be changed.
So yes you'll still see 13A but it is ignored and will no show up in aclim
If this didn't do the trick then the modules simply ignore any value above hwaclim

Dang! Elon fooled me good!
OK... what would happen if i connect each module to its own phase and set the charger to single phase mode? Would charger be ok?
it is still 3x one phase they are just shifted by 120deg...

You said hwaclimit is read from a single module, whichever is on first? Could i try various modules and phases?

I have a task for you. Can all of you make your charger run on full power and inspect what you get returned in spot values in hwaclim value?
My charger is vidently limited to 13.3A per phase and i can only get 8.8kW on the whole out of it.

I would like to see others write their limits here with their P/Ns.

tnx

Mine regularly charges at a hair under 10kW according to my EVSE, if that helps

Arber make a can log for me with savvy can I will inspect and you get the answer.

Bryson wrote: ↑Tue Aug 16, 2022 8:52 pm Mine regularly charges at a hair under 10kW according to my EVSE, if that helps

Can you tell me your PN please?

EV_Builder wrote: ↑Tue Aug 16, 2022 9:17 pm Arber make a can log for me with savvy can I will inspect and you get the answer.

DOH! I dont have savycan setup right now. I posted my CAN some posts back...
Tomorrow i will try to get savycan working on my DUE.