Tesla Charger alternative firmware

[EV_Builder]

Oh, my CHAdeMO test didn't go well, it turns out I have a super charger charger

That makes two of us then working on this i guess, lets keep in touch about how it goes.

[Johaljaswant]

Hello Johannes

Sir, I did try again EVSE kick in it looks like charging ,but my battery voltage
Is dropping so it not charging here is the screenshot.
Please guide

[johu]

I think your version of the datalogger has a limitation, only 8 values can be logged. Can you reduce your selection to the relevant ones and post the data as a text file, not image?

[Johaljaswant]

Could not save text file attached better image
Thanks

[Johaljaswant]

On the same setting it show different data for same parameters and also repeat same value in all parameters.
Please advice
Thanks

[johu]

Hmm, no AC voltage reported on c1
Also, do you have B3 board?then uaux reads too low

[Johaljaswant]

My board is V5aB2.
But I have V4 board which works on both car charger without any problem.
Is my board V5aB2 Faulty.?

[jon volk]

As you might have seen here I'm using a Gen2 Tesla charger as CHAdeMO EVSE. I had to make some small changes to the software to make it work:

- Fix the 0x102 message (enable bits now start at bit 40, not 32)
- Added an "enablepol" parameter to start charging when the enable pin is LOW

Internally I added a pull-up resistor to the enable pin. You can also use this parameter to skip the enable pin all together. Try it, pin stays valid over all future upgrades.

EDIT: when I say "make it work" I only made changes that I anticipated. Actual test is tomorrow.

Just getting back up to speed on this and havent had a chance to upload the latest firmware.
When you say you added a pull up resistor, was the STM32 internal pullup not enough that it warranted a hardware pullup? So basically you can toggle the enablepol value over CAN to say enable/disable via BMS/VCU output?

[johu]

Just getting back up to speed on this and havent had a chance to upload the latest firmware.
When you say you added a pull up resistor, was the STM32 internal pullup not enough that it warranted a hardware pullup? So basically you can toggle the enablepol value over CAN to say enable/disable via BMS/VCU output?

The enable input has a low impedance voltage divider, so the 30k internal pull-up won't do much. If you just want to take the enable pin out of the loop you can set the parameter to ActiveLow and it will just always be enabled. With CAN control switched on you should have what you want.

[johu]

My board is V5aB2.
But I have V4 board which works on both car charger without any problem.
Is my board V5aB2 Faulty.?

Your second datalog looks strange, like "0.17" for opmode. Not sure what happened there. I would need to get access to your charger via remote support to clarify. Can you install the latest firmware: viewtopic.php?p=27210#p27210

[Bryson]

After some use, I think we should change the software to terminate charge after it gets down to 4A DC at constant voltage, instead of the two voltage target/shutoff combination. This would be consistent with how Tesla themselves terminate a charge session.

A simple sum and divide filter checked against 4A would do it. I don’t have a working STM32 dev setup or I’d knock it out myself.

[johu]

Sounds easy to do

[jon volk]

As you might have seen here I'm using a Gen2 Tesla charger as CHAdeMO EVSE. I had to make some small changes to the software to make it work:

- Fix the 0x102 message (enable bits now start at bit 40, not 32)
- Added an "enablepol" parameter to start charging when the enable pin is LOW

Internally I added a pull-up resistor to the enable pin. You can also use this parameter to skip the enable pin all together. Try it, pin stays valid over all future upgrades.

EDIT: when I say "make it work" I only made changes that I anticipated. Actual test is tomorrow.

I'm updating some BMS and VCU code to toggle the enablepol over CAN to request charge. Was the node ID changed on this firmware? I think in an earlier post you were changing it to 5 i.e. 0x605 to send parameter changes to the charger.

[johu]

Yes, 5 it is.

[jon volk]

Excellent. Enable toggling over CAN works perfect. Nice addition.

[jon volk]

Would it be possible to add proximity status to byte 6 or 7 of CAN ID 0x108 or 0x109? EVSELIM might be interesting as well but primarily the proximity for drive-away protection.

[Bryson]

That’s a fantastic idea, I’d implement that as well.

[larsrengersen]

Would it be possible to add proximity status to byte 6 or 7 of CAN ID 0x108 or 0x109? EVSELIM might be interesting as well but primarily the proximity for drive-away protection.

Why in 0x108 or 0x109?
These are part of the CHAdeMO process/standard.
Not sure what unintended consequences could ever emerge but would it not be better to do that in a separate message?

[jon volk]

Another ID is fine. Custom CAN mapping just isn’t available and those were already set transmit IDs.

[johu]

Yes will look into it soon. Either directly adding it or getting the custom CAN working.

[Roadstercycle]

Hi Everyone, I'm planning on getting my Tesla Under Glass VW Rabbit build back this week after some dyno testing and want to install the new firmware in the Tesla Gen 2 charger that's in it. Is everything still working fine in the units it's installed in? Any issues to be aware of? Everybody happy? Thank you in advance.

[johu]

I have unlocked the CAN mapping feature. It won't allow you to unmap anything past "version" so that you can't mess up the internal CAN messages.

I haven't run this on hardware yet, will do that later today. So if anyone is brave enough to test anyway, you can do so now.

[jon volk]

Ill probably have a chance to try the CAN mapping in a week or so. Haven't had time to touch anything on my own car lately.

[janosch]

Would it be possible to add proximity status to byte 6 or 7 of CAN ID 0x108 or 0x109? EVSELIM might be interesting as well but primarily the proximity for drive-away protection.

Yes, adding this somewhere in CAN would be great! I posted about this in the support thread. I ended up building drive-away protection by tapping into proximity and connecting it to one of my VCU analogue inputs.

[johu]

Well, with the above firmware you should be able to map it to some CAN message of your choice