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 )UPDATE:
The content of the variable GUI_chargeSessionAlerts:
GTW_w061_hvacRailTooLow - this one is common, always there, probably something air conditioning related. Anyway, AC works fine.
Anybody experienced this before ? The charge port is US and I am using a US Tesla Chademo adapter.
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 ?Is the GEN2 programmed as a slave?
Ok, I understand. What I can contribute is testing data from Europe. I'm only 1 hour away from the autobahn where I can do some testing at full throttle.
I love playing around with this stuff and learning about all possible details of the car so I'd like to buy a CAN bus logger that allows me to get a maximum of data to do so.
I'm sure I would be able to help some folks in Belgium and the Netherlands that have questions on their battery health and things like that.
From what I understand, right now the SavvyCAN is probably the easiest option but I need to find a way to get it shipped at a reasonable cost. The list price of $295 is fine but adding $190.79 for shipping + probably an additional European import tax + VAT on top looks a bit much in comparison with the list price.
Respect for the work you and others are doing to offer all of this to the community for rep points only!
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.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.
I only have the CAN bus connected between the MCU and the IC currently. I'm working on getting some CAN sniffers/injectors setup now for that bus and the other *four* (five total) CAN buses on this car. Probably will be a few days before I actually have time to tinker with all of the CAN stuff.
Not sure what you mean by "the servo controller." There appear to be five CAN bus connections and some LIN connections on the MCU. The LIN stuff looks to work for homelink, the seat heaters, the electrochromatic mirror dimmers, and some 12V battery monitoring system I'm unsure about.
- - - Updated - - -
I don't feel like I'm obligated to notify Tesla of anything at all, honestly. If they provided me with the hardware and such to tinker with, and maybe even some additional info and insight to make the job easier, then sure, they would be the first to know of anything I come up with. But I purchased the hardware I'm working with myself and I'm doing so basically blind to the inner workings. Also, considering pretty much anything I do here is going to involve some form of hardware hack and not something that some random person is going to be able to do to some random Model S to cause any issues... honestly, I'll probably just post my findings here and be done with it. If Tesla wants to follow along, they're more than welcome to just like anyone else. I'll gladly entertain their questions/comments/concerns.
- - - Updated - - -
Yeah, I was honestly thinking the same thing when I came up with the initial idea. Would require a switch of some kind to toggle between the rearview cam and the connected HDMI device, though, which would likely have three settings: Rear, Aux, Auto... where auto would default to the rear cam when nothing was connected to the aux HDMI.
Honestly, this will probably be the easiest part once I get a hold of a rear cam to play with...
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....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.