-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VIN not available for 2 of 3 TWC #528
Comments
I don't know the cutoffs of production dates, but I think it has been noted that older TWCv2 units don't report the VIN of the connected car. If Tesla were of a mind to push firmware updates, they probably could, but at this point it's safe to assume they won't do that. Assuming that the lack-of-VIN stays with the TWC and not the vehicle, that's probably what you're seeing. |
Hi Mike, My "lucky guess" is the following: Best regards PS: My TWC that doesn't show the VIN is reacting to the ampere-change-command correctly but doesn't react to the start/stop-command at all. Whereas my VIN-reporting-TWC works like a charm with that. |
In my case one it's showing VIN and the other one nothing... But the one it's showing VIN, is #3123 and the #6856 (this one being DC for Tesla only) doesn't show any VIN. And both are (S)TSN: "A17...") |
I have two chargers, one shows the VIN and one doesn't. I have one of -01-x and one -02-x. The -02-x is the only one that shows the VIN. the 'x' above could be any letter. I don't think it is of any consequence. |
Hi there! Just one quick question:
I have three TWC installed separately but only one device is telling me the VIN of the connected Tesla...
The one showing the VIN has the ID 8906 - the two devices that don't show the VIN have the ID 2013 and 7835 (so older production date I guess).
Perhaps someone can give me a hint wether I am doing something wrong - or is this feature only working with "newer" IDs from 8000 up or something? I use TWCManager v1.2.3 - each TWC connected separately via its own RS485-USB-adapter and docker container with the same settings.
The text was updated successfully, but these errors were encountered: