Help! Stranded w Software Error 0x1533, 0x400

I don't see it matching anything here Roadster - Tesla Motors Club - Enthusiasts & Owners Forum

I haven't seen that error before. Did you already open and close the charge port door? (Like a reboot.) That's resolved things a few times for me.

Panicopticon said:

No love. She had to go for a 125 mi flat bed ride. Shes back in the garage at home now. We'll see what Tesla says tomorrow when the techs are available.

Click to expand...

Sorry to hear about the error code requiring a visit to the service centre.

But I'm curious - on the bottom of your posts you state you have Roadster #931 ... Is this correct ? .. I ask because my car is 'also' #931 !

I would have thought chassis numbers are unique irrelevant of the territory in which they were sold. So this is seems like a bit of a mystery ..

Amusing coincidence for post #6 about VIN 931: Last edited by PV4EV; Today at 09:31 AM.

Panicopticon said:

Car will be taking a trailer trip down state early next week. Sigh.

Click to expand...

Sorry to ear about the long trip 'home' to the SC...
Be sure to come back and update us and the http://www.teslamotorsclub.com/forumdisplay.php/108-Wiki for this new error code when you learn more!

Good luck!

Panicopticon said:

From the USB logs, flash/firmware.rc:
vms : vms.image : 906028 : 15.1.0 : 0.0.0 : VMS-R4 : 1 :

And from the linux console & boot messages, flash/messages:
Aug 24 19:15:35 syslog: VMS: VMS restarted - version 13.3.0

There in lies the problem I suspect. No idea why it reverted though. Perhaps a failing flash part?

Click to expand...

So the VMS restarted, couldn't load the new firmware, so reverted to old. Then, version mismatch.

Neat. Could be a one-off (ie; another reboot could fix it), or as you say something corrupt on the new firmware.

What are the odds that it would cause the version number to be wrong?

Click to expand...

It could be that "version mismatch" is kindda generic message that is also displayed when hash codes mismatch.
And hash is there to detect failing flash.

markwj said:

.... Neat. Could be a one-off (ie; another reboot could fix it), ...

Click to expand...

I assume he already pulled and reinserted the ESS service disconnect.

spaceballs said:

I assume he already pulled and reinserted the ESS service disconnect.

Click to expand...

You might want to expand on that, no one proposed this so far to him AND the car is not at the SC yet (only supposed to go next week).

I also remember reading about 'rebooting' the VMS by disconnecting & reconnecting its power cable that is dangling somewhere close under the dash on the passenger side?

...mind you if you succeed in clearing the error either way because the flash failing(or other problem) is intermittent,
you'll end up hiding the problem away for the SC investigation until it fails more permanently and you get stranded again :-(

Roadrunner2013 said:

I also remember reading about 'rebooting' the VMS by disconnecting & reconnecting its power cable that is dangling somewhere close under the dash on the passenger side?

Click to expand...

I've seen this done, and wouldn't suggest it. That cable is damn tight - the rangers have a special tool for removing it without damage.

Hate to be stupid but........
What's a failing flash???

You don't need to pull the ESS to get the computer to reboot, the main harness plug can be accessed right in front of the center shift console. Anytime the USB stick can't be recognized Tesla pulls / reinserts the plug which reboots it.