Hey folks;
Long story short I have the only Roadster left in our country. 2010 model year EU VIN278 around 60k miles. It has not worked snce the owner washed the car in May 2018, had a little drive and parked the vehicle. Thankfully Gruber has been helping me for the past 4-5 months over e-mails but I seldom get a reply, maybe once a month at best, as they're super busy with their projects.
We repair Model S&X vehicles so I have little to no experience on the Roadster. Thanks to online resources I've been reading a lot and learning but information on Roadster is still quite limited. I figured maybe you guys could help me with this battle.
Problem is that the contactors do not close. So ESS is isolated and does not power APS. Hence to power the vehicle we jump it from the APS posts on rear right. When jumped the screen turns back on, even the IP needles jump when ignition is on but the car of course does not shift. Shows the fault lamp and regen disabled lamp alongside a 110 mile range. The error messages are;
- ID265 BSM: V_batt too low
- ID264: BSM: PEM cable fault
- ID50: BMB: No data fault
- ID258: APS output 2 (PEM) reset
- ID1552 VMS: Not receiving BMB version number (yellow warning)
- ID53 GPS: No data fault(yellow warning)
- ID1561: VMS: Not receiving CPLD version number(yellow warning)
- ID1556: VMS Not receiving PM version number(yellow warning)
- ID43 VMS: APS inhibited due to low brick voltage
- ID885: BMB No Data Fault can't start
- ID888: VMS/PEM key mismatch
Actions taken so far;
- My first contact was Gruber and they told me it was a communications issue. We did check every connector outside of ESS and indeed did find corrosion with few. However that didn't solve it.
- Then we took a buzzer and measured every cable in all harnesses to check if there was a problem. Found that one blue wire wasn't passing through from front to mid harness connector. Pin #15, that was ESS can low as per Gruber. Made another twisted pair wire coupled with pin #14 red as CAN high of ESS, yet it wasn't solved again. Just when I thought we were so close.
- As per Gruber we hooked up an oscilloscope to those wires and saw that CAN bus was functioning properly. We saw square waves. Low was between 0-2.5V and high was between 2.5-4V. The signals indeed were can messages. Resistance between can high and low was fluctuating between 116-132ohm in an energized state so 120ohm should be the resistance when powered off.
Now tomorrow I'll measure all 99 of the bricks from BMBs with probes and see if there is a faulty brick/module indeed. Possibilities in my mind are;
1) There is a dead module/brick. We need to remove and charge it to hopefully recover it, or replace it.
2) I read a thread here about something similar. There was a fuse blown in the front 400VDC controller that blew up the ESS fuse. Worth checking as well after the brick measurements.
3) Some kind of ROM went bad and it needs firmware flashing? (Hope not since all is Tesla proprietary and is impossible to take it to an official Tesla service especially during COVID19)
4) There indeed is a CAN issue, just not with the canbus but with one of the nodes.
I would appreciate your feedbacks and tips. It would be epic for the only Roadster left in our country to be back on the roads. I'm sending a photo of the firmware screen from service menu in case it means something. BMB not having a firmware really does mean communications issue but I did saw the bus function properly so I'm lost. Hopefully dead modules or blown fuses in ESS also somehow affect the comms.
Best;
Long story short I have the only Roadster left in our country. 2010 model year EU VIN278 around 60k miles. It has not worked snce the owner washed the car in May 2018, had a little drive and parked the vehicle. Thankfully Gruber has been helping me for the past 4-5 months over e-mails but I seldom get a reply, maybe once a month at best, as they're super busy with their projects.
We repair Model S&X vehicles so I have little to no experience on the Roadster. Thanks to online resources I've been reading a lot and learning but information on Roadster is still quite limited. I figured maybe you guys could help me with this battle.
Problem is that the contactors do not close. So ESS is isolated and does not power APS. Hence to power the vehicle we jump it from the APS posts on rear right. When jumped the screen turns back on, even the IP needles jump when ignition is on but the car of course does not shift. Shows the fault lamp and regen disabled lamp alongside a 110 mile range. The error messages are;
- ID265 BSM: V_batt too low
- ID264: BSM: PEM cable fault
- ID50: BMB: No data fault
- ID258: APS output 2 (PEM) reset
- ID1552 VMS: Not receiving BMB version number (yellow warning)
- ID53 GPS: No data fault(yellow warning)
- ID1561: VMS: Not receiving CPLD version number(yellow warning)
- ID1556: VMS Not receiving PM version number(yellow warning)
- ID43 VMS: APS inhibited due to low brick voltage
- ID885: BMB No Data Fault can't start
- ID888: VMS/PEM key mismatch
Actions taken so far;
- My first contact was Gruber and they told me it was a communications issue. We did check every connector outside of ESS and indeed did find corrosion with few. However that didn't solve it.
- Then we took a buzzer and measured every cable in all harnesses to check if there was a problem. Found that one blue wire wasn't passing through from front to mid harness connector. Pin #15, that was ESS can low as per Gruber. Made another twisted pair wire coupled with pin #14 red as CAN high of ESS, yet it wasn't solved again. Just when I thought we were so close.
- As per Gruber we hooked up an oscilloscope to those wires and saw that CAN bus was functioning properly. We saw square waves. Low was between 0-2.5V and high was between 2.5-4V. The signals indeed were can messages. Resistance between can high and low was fluctuating between 116-132ohm in an energized state so 120ohm should be the resistance when powered off.
Now tomorrow I'll measure all 99 of the bricks from BMBs with probes and see if there is a faulty brick/module indeed. Possibilities in my mind are;
1) There is a dead module/brick. We need to remove and charge it to hopefully recover it, or replace it.
2) I read a thread here about something similar. There was a fuse blown in the front 400VDC controller that blew up the ESS fuse. Worth checking as well after the brick measurements.
3) Some kind of ROM went bad and it needs firmware flashing? (Hope not since all is Tesla proprietary and is impossible to take it to an official Tesla service especially during COVID19)
4) There indeed is a CAN issue, just not with the canbus but with one of the nodes.
I would appreciate your feedbacks and tips. It would be epic for the only Roadster left in our country to be back on the roads. I'm sending a photo of the firmware screen from service menu in case it means something. BMB not having a firmware really does mean communications issue but I did saw the bus function properly so I'm lost. Hopefully dead modules or blown fuses in ESS also somehow affect the comms.
Best;