That makes sense then, I removed my token as I didn't want the API randomly waking up my car; i don't know how to read the code to tell if its coded in a good way
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
That makes sense then, I removed my token as I didn't want the API randomly waking up my car; i don't know how to read the code to tell if its coded in a good way
All was working fine for weeks but recently I got a problem, not really related to the script but more to the serial-to-usb driver it seems:
Of course the script crashes after this. Is it a faulty hardware or a cable broken or what am I suppost to do now?
Code:
[18830.252081] usb 1-1: USB disconnect, device number 3
[18830.252457] ftdi_sio ttyUSB1: error from flowcontrol urb
[18830.252930] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[18830.253007] ftdi_sio 1-1:1.0: device disconnected
[18830.451813] Indeed it is in host mode hprt0 = 00021501
[18830.651727] usb 1-1: new full-speed USB device number 4 using dwc_otg
[18830.651963] Indeed it is in host mode hprt0 = 00021501
[18830.887408] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
[18830.887426] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18830.887433] usb 1-1: Product: USB-RS485 Cable
[18830.887440] usb 1-1: Manufacturer: FTDI
[18830.887446] usb 1-1: SerialNumber: FT2FZ7WG
[18830.909034] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[18830.909237] usb 1-1: Detected FT232RL
[18830.909847] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0Of course the script crashes after this. Is it a faulty hardware or a cable broken or what am I suppost to do now?
K-MTG
Sunshade Captain of TMC
Thanks for sharing the video! Could TWCManager be used to broadcast its own WiFi network? For instance, can I use it to to prevent other people from using my wall connector in an apartment complex garage (that doesn't have wifi signal)?
It would be cool if I can manually shutoff and turn on the wall connector from my phone.
It would be cool if I can manually shutoff and turn on the wall connector from my phone.
Update here for Powerwall users with a couple of bug fixes and damping of the green energy amps. When monitoring mine it was suffering from slight delays with the powerwall charging so it was switching between 9A and 6A every 10 seconds. This is fixed by altering the green amps offered by a max of 1A each 10s.
I've also attached a screenshot of the powerwall screen showing how the charging tracked the solar once my powerwall got up to the target 70% charge. As the sun dipped, the charging stopped as the green energy dropped and the powerwall picks up the excess for the rest of the day.
I've also attached a screenshot of the powerwall screen showing how the charging tracked the solar once my powerwall got up to the target 70% charge. As the sun dipped, the charging stopped as the green energy dropped and the powerwall picks up the excess for the rest of the day.
Attachments
Ulmo
Active Member
Thanks for all your work!
Can we know what these magical new VIN commands are for the newest firmware?
whitex
Well-Known Member
@CDragon
Not sure whether you saw this or not, but Tesla has released the HPWC control spec, at least to Maxem (according to this article). Have you tried reaching out to Tesla to see if you can get a copy too?
Not sure whether you saw this or not, but Tesla has released the HPWC control spec, at least to Maxem (according to this article). Have you tried reaching out to Tesla to see if you can get a copy too?
whitex
Well-Known Member
Probably to track car capabilities (older cars may not support everything). This also opens up a possibility for access control list for HWPC (allowing or disallowing cars on any particular HPWC, say you have one installed in a shared apartment complex parking - prevent people stealing your electricity while you're not there).
WinterDragoness
Member
Hi all,
Wow, as soon as I stop paying attention, suddenly there's a ton of interest in this project!
I've gotten really busy lately and have been hired to code stuff for chargers professionally so my time has become really limited, but let me try to answer all the questions from the last couple months...
First, I'm still interested in knowing when/if Tesla releases new firmware versions, so if anyone has a newly purchased TWC, please continue to send me its firmware version and date of manufacture as follows:
I think Master mode will respond to most messages like firmware version and VIN but I haven't tested.
I considered offering this but there are too many legal issues of liability in the US for me to feel it's worth the risk. You could probably ask a local electronics repair place to put the parts together for you though.
It would be great to upgrade the firmware, but unfortunately it requires a piece of hardware that costs about $30, plus a specialized cable that is a bit tricky to solder together. Or you can probably buy a specialized adapter but I didn't bother spending much time trying to source one. And then you need to install and figure out the software that reads/writes the firmware. Overall, it's not something an average home user would be able to do.
Hopefully someday Tesla will get their TWC firmware update through the car system working and then everyone will have the latest firmware.
Something like powerwall integration should be added using a "Branch" in the git repository. When I change anything in the main repository it's generally easy to merge in those changes to the branch. Putting support for every type of green energy system in the main repository would make it too complicated unless we come up with a system to have each type of system in its own file and users can pick which file gets loaded, but I don't feel I have time to try to orchestrate that.
If someone wants to start a branch, you will need to create an account at github.com. If you can't figure out how to branch the TWCManager repository, click my name at the top of this post, then click 'Start a conversation' and ask me how.
Potentially useful commands in firmware 4.5.3 are:
People I know have reached out and they only share that info with large corporate users like Maxem. However, thanks to firmware decoding, I'm 99% sure I know all the commands in the latest TWC RS485 control set (1% unsureness comes from the extraordinarily unlikely possibility that they hid additional commands using some form of obfuscation).
Wow, as soon as I stop paying attention, suddenly there's a ton of interest in this project!
I've gotten really busy lately and have been hired to code stuff for chargers professionally so my time has become really limited, but let me try to answer all the questions from the last couple months...
First, I'm still interested in knowing when/if Tesla releases new firmware versions, so if anyone has a newly purchased TWC, please continue to send me its firmware version and date of manufacture as follows:
- Visit this URL: http://<raspberry pi address>/index.php?sendTWCMsg=FB1B&submit=1
- If it returns 4.5.3 or later:
- Please get me the date of manufacture by visiting:
- http://<raspberry pi address>/index.php?sendTWCMsg=FB19&submit=1
- and the extended firmware version by visiting:
- http://<raspberry pi address>/index.php?sendTWCMsg=FBEC7777<TWCID of slave>&submit=1
- where <TWCID of slave> must be replaced by your TWC's 4-digit ID which is shown in the web UI.
- Send me results by clicking my name at the top of this post, then click 'Start a conversation', or post here if you prefer.
I think Master mode will respond to most messages like firmware version and VIN but I haven't tested.
I considered offering this but there are too many legal issues of liability in the US for me to feel it's worth the risk. You could probably ask a local electronics repair place to put the parts together for you though.
It would be great to upgrade the firmware, but unfortunately it requires a piece of hardware that costs about $30, plus a specialized cable that is a bit tricky to solder together. Or you can probably buy a specialized adapter but I didn't bother spending much time trying to source one. And then you need to install and figure out the software that reads/writes the firmware. Overall, it's not something an average home user would be able to do.
Hopefully someday Tesla will get their TWC firmware update through the car system working and then everyone will have the latest firmware.
Something like powerwall integration should be added using a "Branch" in the git repository. When I change anything in the main repository it's generally easy to merge in those changes to the branch. Putting support for every type of green energy system in the main repository would make it too complicated unless we come up with a system to have each type of system in its own file and users can pick which file gets loaded, but I don't feel I have time to try to orchestrate that.
If someone wants to start a branch, you will need to create an account at github.com. If you can't figure out how to branch the TWCManager repository, click my name at the top of this post, then click 'Start a conversation' and ask me how.
Potentially useful commands in firmware 4.5.3 are:
- Remember, these commands won't work in TWCs containing firmware with a lower number than 4.5.3. 4.5.3 was included in TWCs manufactured around March 2018 and later.
- FC B1 SS SS RR RR
- Tell TWCID RR RR to start charging. SS SS is the fake master TWCID.
- FC B2 SS SS RR RR
- Tell TWCID RR RR to stop charging. SS SS is the fake master TWCID.
- Stop charge command is seriously bugged in that it will cause a plugged-in Tesla to show a red ring around its charge port as soon as you send the command. Car will refuse to charge again until you send start charge command and then physically re-plug the car.
- If you set DIP switch 2 in the TWC to the down position, it turns off CAN communication to the car and start/stop charge actually work correctly except if you stop and start charging more than once, the car will randomly decide the charger is bad and refuse to charge again until you re-plug the car. The car may also decide to limit itself to 30A charging and that change is permanent unless you raise amps using the car UI.
- Basically I'm saying stop/start charge commands are useless for most purposes as they are implemented in firmware 4.5.3.
- The reason cars respond badly seems to be that stop/start simply turn the relays in the TWC off or on but do not send any CAN message to the car telling it to stop or start (I reached those conclusions by looking at the firmware). My 2014 Model S responds to this by trying to use CAN to start the charger again (car ring flickers blue to show CAN communication) and after a bit it enters perma-error state unless DIP 2 is down which disables all CAN communication. Conceivably, Model 3 or X don't respond badly which is how this escaped quality control? If anyone has a 3 or X or a newer S, please test and let me know.
- FB B4
- Get plug state. All TWCs on network return FD B4 RR RR XX where RR RR is the TWCID reporting its plug state and XX is 00 when TWC is unplugged, 01 when charging, 03 when plugged in but not charging for any reason (including error). Rarely, 02 is returned but I've seen no pattern to why - I suspect it means the TWC is booting or currently updating the plug state.
- FB EE SS SS RR RR
- Tell TWCID RR RR to return first 7 characters of VIN of connected car. SS SS is the fake master TWCID. Response message is FD EE RR RR VV VV VV VV VV VV VV where VV is an ascii character code representing a letter or number. VV will be all zero when car CAN communication is disabled (DIP switch 2 down) or when a non-Tesla vehicle is plugged in using something like a JDapter.
- FB EF SS SS RR RR
- Tell TWCID RR RR to return the middle 7 characters of VIN of connected car.
- FB F1 SS SS RR RR
- Tell TWCID RR RR to return the last 7 characters of VIN of connected car. US cars only have 3 characters to return with this message but maybe some in other countries have more?
People I know have reached out and they only share that info with large corporate users like Maxem. However, thanks to firmware decoding, I'm 99% sure I know all the commands in the latest TWC RS485 control set (1% unsureness comes from the extraordinarily unlikely possibility that they hid additional commands using some form of obfuscation).
Last edited:
marlan99
Member
Here the extended FW Information of my second Signature TWC
Can not find out the FW of the second TWC behause it shows just the first one
Response: FD EC 21 61 04 05 03 02 00 00 00 00 00 00 00 7C
Can not find out the FW of the second TWC behause it shows just the first one
Response: FD EC 21 61 04 05 03 02 00 00 00 00 00 00 00 7C
WinterDragoness
Member
In my last post I said people wanting to create versions to support things like Tesla Powerwall should create a Branch. I should have said they should create a Fork. To do so:
- Log in or create an account at github.
- Visit the TWCManager github repository.
- Click the word "Fork" in the upper right:
- After a minute or two you'll arrive on a page like this:
- Click the green Clone or download link button (circled in red) to get a link to download the forked code to your raspberry pi using this git command:
- git clone -b master --single-branch <link revealed by green button> ~/MyTWCFork
- Copy code from ~/TWC to ~/MyTWCFork, or maybe swap their names to keep developing in ~/TWC.
- If you made changes to the html code, you'll also have to run cp / var / www / html / * ~/MyTWCFork/HTML
- Use git commit, then git push to push changes from your local files to your code on github, then give out your github link for people that want to use your fork.
Thanks for this tip, its working in Master mode (TWCManager is running with fakeMaster=2).
Code:
Response: FD 1B 04 03 0D 00 00 00 00 00 00 00 00 2F
Decoded response
Firmware version: 4.3.13
Response: FD 19 41 31 36 4B 30 30 xx xx xx xx xx 75
Decoded response
(S)TSN: A16K00xxxxx (manufactured between May 20th and Jun 2nd 2016, TWCID 9861)
Response: FD 1A 45 56 57 32 54 33 32 48 4C FF 00 8A
Decoded response
Model: EVW2T32HLHey all,
This is a great project and I have an idea to adapt it to my current situation. My Tesla Wall Connector is fed by a DCC-9-30, which is necessary due to the low rating of my main circuit breaker. Its purpose is to cut off the wall connector once overall current reaches 80% of the rating of the main breaker (56A out of 70A in my case). What I'd like to create is a design that instructs the wall connector to actively dial back the current as the total household approaches the limit. This way my car can continue to charge at a slower rate as opposed to being cut off altogether.
I know my way around embedded Linux systems pretty well but I'm thinking this application may be better suited for a flash-based microcontroller (ie Atmel SAM, Freescale/NXP Kinetis, STM32, etc) since there are existing resources for implementing energy monitors with them. Has anyone made any effort to port this project - or maybe a portion of it - from Python to C?
This is a great project and I have an idea to adapt it to my current situation. My Tesla Wall Connector is fed by a DCC-9-30, which is necessary due to the low rating of my main circuit breaker. Its purpose is to cut off the wall connector once overall current reaches 80% of the rating of the main breaker (56A out of 70A in my case). What I'd like to create is a design that instructs the wall connector to actively dial back the current as the total household approaches the limit. This way my car can continue to charge at a slower rate as opposed to being cut off altogether.
I know my way around embedded Linux systems pretty well but I'm thinking this application may be better suited for a flash-based microcontroller (ie Atmel SAM, Freescale/NXP Kinetis, STM32, etc) since there are existing resources for implementing energy monitors with them. Has anyone made any effort to port this project - or maybe a portion of it - from Python to C?
WinterDragoness
Member
Unfortunately Tesla has not enabled updating TWCs through cars at this point. There was some evidence that they tried to enable it and it ended up stalling during update, which they probably fear could brick TWCs or at the very least create calls to support asking about error messages. I'm working with a few TWCs at this point that get plugged into many cars each day (including model 3s) and they remain stuck on older firmware.
Oh, thanks I didn't know that. Thought this was enabled by default: "Charge Connector Update in Progress..."
Hi All, I’ve been following this thread for a while and have read all through it but haven’t seen anyone doing what I’d like to do, I’d like to use this but read the grid feed from my SMA Sunny Home Manager 2.0, I’m currently pulling the values from that device and storing them in an influxDB and graphing them using Grafana, is there an easy way to do this? Thanks to all that have put the time and effort into the system already and offering it for use
WinterDragoness
Member
I just noticed this question. The last line, "FTDI USB Serial Device converter now attached to ttyUSB0" sounds like it's working to me. What exact error are you seeing? If you're still convinced it's the USB device, try ordering another one. I did find a slightly cheaper ($25) version of the official FTDI RS485 chip board here.
@CDragon thanks for getting back to me.
I have changed some lines in your code to take an alternative USB device once the original failed. That worked very well as a workaround so far. No more problems even though I don't think my way is a good one to handle it.
I will probably get another device next year (once I can get some decent Amps from my PV again).
I will also publish my changes on github for everyone having same issues and/or a SolarEdge Inverter to get the required data for green-energy-tracking.
I have changed some lines in your code to take an alternative USB device once the original failed. That worked very well as a workaround so far. No more problems even though I don't think my way is a good one to handle it.
I will probably get another device next year (once I can get some decent Amps from my PV again).
I will also publish my changes on github for everyone having same issues and/or a SolarEdge Inverter to get the required data for green-energy-tracking.
Similar threads
- Article
