-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
bacila4666
Member
You must update software for CID and IC 17.32.2 - after that version no problem with chademo ( difference chademo and GW,BMS,CHG firmware )
Hello guys, no activity here for a while.
I was trying to replace a gen1 charger and HVJB with GEN2 in a 2013 Model S.
The car, as expected, does not recognize the new charger, as expected it needs redeploy to match the firmware on gw and charger.
The problem is that the GEN2 charger looks like it is in a continuous reboot cycle, so the car does not detect it to update the firmware:
The power usage from the 12V DC goes up to 47 mA. it stays there exactly 10 seconds and then goes down to 11 mA, then says there 1-2 seconds then goes up to 47 mA again, and this cycle repeats forever:
When the charger is disconnected from the car, and connected to a can logging device, it powers up, then for 10 seconds outputs can data at 500kbps, then shuts down forever, until disconnect the power and reconnect:
Anybody played with this beast ? Any idea how to keep it awake until the car detects it and redeploys ?
I was trying to replace a gen1 charger and HVJB with GEN2 in a 2013 Model S.
The car, as expected, does not recognize the new charger, as expected it needs redeploy to match the firmware on gw and charger.
The problem is that the GEN2 charger looks like it is in a continuous reboot cycle, so the car does not detect it to update the firmware:
The power usage from the 12V DC goes up to 47 mA. it stays there exactly 10 seconds and then goes down to 11 mA, then says there 1-2 seconds then goes up to 47 mA again, and this cycle repeats forever:
When the charger is disconnected from the car, and connected to a can logging device, it powers up, then for 10 seconds outputs can data at 500kbps, then shuts down forever, until disconnect the power and reconnect:
Anybody played with this beast ? Any idea how to keep it awake until the car detects it and redeploys ?
It doesn't respond to UDS on either the master or slave IDs, so we can't tell and can't reprogram it
We should have all the tools necessary to do the same. Also, George and Jason aren't on the same continent
We should have all the tools necessary to do the same. Also, George and Jason aren't on the same continent
Indeed, but mail is great in a bind and yes everyone should have the tools, or Tesla should release one, or they program for free.
The short time it stays UP (10 seconds) between reboots is not enough to even connect to it, the car does not have time to identify it, neither Toolbox does. It must have a signal, input pin on the 10 pin connector coming from HVJB gen2, but I can't test as I don't have another car to measure these signals. Or maybe it expects receiving a specific CAN package to make it stay awake ? @wk057, any clue what that can be, have you ever tried to retrofit GEN2 charger and HVJB replacing GEN1 charger and HVJB ?
Last edited:
i would say the easiest and cheapest is to get an arduino UNO or raspberry and some canbus chips which will communicate via SPI. SPI is fast enough to transfer the information from canbus chip to arduino UNO /raspbi.
rasbperry has the advantage of being able to log to sdcard or even stream it via wifi , or you could code up quickly a node.js webserver.
depending on what your needs are I doubt you would need to pay 300$ if you want to play a bit with canbus frames.
krash has put together a nice list of what's available:
Diagnostic Port Index
see section:ELM ODB2 Module Alternatives
this thread is really huge, read a bit through it because i'm looking for information to access the diagnostic service screen.
my understanding is, reading on here, that you need a code that is changed daily. is this correct?
I guess we would need root to read this code? or is reading of the code off-limits so that it's impossible to now access the diagnostic screen?
just waging if I should invest time in trying to access or it's a lost cause.
thanks
my understanding is, reading on here, that you need a code that is changed daily. is this correct?
I guess we would need root to read this code? or is reading of the code off-limits so that it's impossible to now access the diagnostic screen?
just waging if I should invest time in trying to access or it's a lost cause.
thanks
thanks for the reply, from what I've read, the LAN on the ethernet port is not accessible anymore from the exposed connector. I don't want to tear the car apart, removing dashboard and so. If there was an easy way to see the info OK, otherwise I'll just try to read things from canbus as I'm currently doing.
@amund7 thanks, I'll check it out.
The only way you can get access to the car's network is by the IC - CID cable or if you can open the diagnostic port.
You can get access to the first by disassembling the dash and taking out the IC, connecting your laptop in it's place.
For the latter you need the unlock code. That you basically can't get unless you have access to official resources.
I have made the HDMI available to go thru the rear-camera channel, but the audio has got to go thru Bluetooth (expecting 1-1.5s delay). Is there alternative other than Bluetooth? Adding an external DSP with aux in to the MCU would be a hard job and it is for Premium Audio system only.
I would purchase a device that toggled between a couple of HDMI inputs plus rear view camera....
Care to start making them???
