[jackbauer]

The captures from today are up on github https://github.com/damienmaguire/Tesla-Charger

Looks good Tom

 

[Tomdb]

I know, but is that including the one where you mention you hit 370V at 1.5A?

Got most of the commands found, so sending out message 0x368 at fixed values and then in message 0x42C steping byte 1 from 100 to 196 and then applying the AC voltage to see if the charger will click.

Possibly you will also require in 0x42C to step change byte 4, looking at it there is a change it influeces/controls the precharge.

In message 0x45C byte 2 and 3 also do a step change. these sync up with byte 1 in 0X42C.

 

[jackbauer]

Sorry no I didn't log that one. Can do tomorrow.

 

[Tomdb]

Might I suggest Tweaking some values by hand, like what we think the voltage set point is to snuff it out. Same with the current value.

Then working on getting a script/arduino controlling the charger.

 

[electro wrks]

Basic Tesla charger question: Does the Tesla DC fast charge(and possibly other DC fast charge protocols) go through the charger? If so, can it be enabled as well as the AC charging functions?

 

[CKidder]

Basic Tesla charger question: Does the Tesla DC fast charge(and possible other DC fast charge protocols) go through the charger? If so, can it be enabled as well as the AC charging functions?

In general, no. I don't have in-depth knowledge of the Tesla super charger but how fast charging tends to work is that the car has contactors that connect the car's battery straight to the DC fast charger itself. The fast charger then has all the charger goodies in it and handles the current and voltage limiting outside the car. The car reads voltage and current itself and sends commands to the external charger about what it would like to do. In an emergency the car always has the option to open its contactors. So, the on-board charger really isn't involved in all this but the battery management system most certainly is. Now, that all holds for CHAdeMO which I do know about. But, I can't imagine the super charger is any different.

 

[jackbauer]

I suspect from the wiring diagrams and the complexity of the charger logic board that the charger handles the Supercharging control. One question for Colin : now can I tell the frequency of a message in Savvycan? going to attempt to write a simple program to get the charger to ramp up to 2A and stay there.

 

[DrJeff]

I suspect from the wiring diagrams and the complexity of the charger logic board that the charger handles the Supercharging control. One question for Colin : now can I tell the frequency of a message in Savvycan? going to attempt to write a simple program to get the charger to ramp up to 2A and stay there.

I suspected it was the HVJB that engaged or not the charger, and thus handled DC supercharging.

Jeff

Sent from my Nexus 7 using Tapatalk

 

[Tomdb]

Time stamps.

looks like the contol messages 0x368, 0x42C and 0x45C are not as fixed as the response. varying from I believe 100ms to 200ms. or 5-10 messages/second

 

[electro wrks]

I suspected it was the HVJB that engaged or not the charger, and thus handled DC supercharging.

OK, in the Gen 1&2. It looks like the Gen 3 has the JB incorporated in the charger housing. This would be the next charger to hack with this feature, and up to 72A AC capacity: https://teslamotorsclub.com/tmc/threads/model-x-3rd-gen-72-a-charger-hacking.88952/

 

[CKidder]

I suspect from the wiring diagrams and the complexity of the charger logic board that the charger handles the Supercharging control. One question for Colin : now can I tell the frequency of a message in Savvycan? going to attempt to write a simple program to get the charger to ramp up to 2A and stay there.

You can just look at timestamps but there are far more powerful options too. Under "RE Tools" you'll find "Frame Data Analysis" this window will tell you all sorts of things about a given ID - the number of bytes it has, the minimum time between frames, max time, average. It also can tell you which bits and bytes had changes and how many times a certain bit or byte had a certain value. But, I suppose you'd really be interested in the average inter-frame timing for each ID.

 

[jackbauer]

Never knew that was there! Thanks Colin Looks like all 3 messages are on 100ms time interval.

Gotta get me a 72A charger

 

[Tomdb]

I bett the charger will work with almost the same setup.

As why change something if it aint broke. And again three modules making up one unit.

 

[jackbauer]

We have arduino control of the charger

 

[Tomdb]

Yessss

So you can make any voltage or current you want?

Now it would be fun to test it in a three phase setup, if you have a three phase socket to test from.

 

[jackbauer]

Won't need three phase. Just 45Amps at 230v single phase for a full power run. Video on the way

 

[Tomdb]

Shall I change your hard coded messages into something more useable?

Like setting output voltage and current plus ramp up time?

 

[jackbauer]

Here is the video :
https://youtu.be/7GwXQtd7RPY

Yes please Tom. I need to spend some of that Patreon money on a programming book

 

[jackbauer]

Uploaded 3phase_command_msgs_22kw.csv the github. We did a capture in my friends car today running from a 22kw 3 phase public evse. Car has dual chargers. Interesting thing is the command messages are identical for each power module. Should be very easy to run at full power.

Another finding today is the charger will work down to less than 150v and current increases with decreasing voltage for the same setpoint.

 

[Tomdb]

Damien, did you command 150V?

Otherwise the charger is just hitting the constant current as defined in the control message.

how ever one of the parameters that get sent to the charger will contain the AC current limit.

Can you ask your friend if you can monitor the charger when you plug in the wall adapter charger, should be limited to 13Amp ac.