I was more thinking of a close inspection of E-03 as there could be some contact issues.That link you sent seemed to conclude with the guy fiddling around a lot and then it's miraculously working so I'll give it back to the client. Quality.
I was more thinking of a close inspection of E-03 as there could be some contact issues.That link you sent seemed to conclude with the guy fiddling around a lot and then it's miraculously working so I'll give it back to the client. Quality.
The SA rarely go bad unless it was hit by lightning.components in the AC Input section of the charger (fuse, ZNRs, spark arrestor, X2 safety caps, ceramic resistors, etc)
You could keep the OBC ‘awake’ by bypassing the OBC relay (i.e. jumper the 12V feed from the DC/DC on E-03) and see if you can access it with Diagbox if your ‘proper’ type 1 doesn’t yield any clues??Do you know of something I can do / disconnect in the charger that would throw a known obc fault code without causing damage? Then I could, using diagbox, check that the code is being successfully
You also mentioned that the 12V to the OBC drops very quickly; no power, no communication…When I run the diagbox diagnostic with the charging cable plugged in as instructed, the OBC shows as accessible. But as the only thing I can do is read codes, and there are none, it's not totally convincing. That is why I thought it would be good to create an internal obc error code so that I could check it flagged and was reported. I just don't know how.
Maybe that was the problem all along, the EVSE looking for a 32A load, or did you try lower settings?I've ordered the cheapest Chinese type 1 evse I could find. It has variable current from 8 to 16a at 230v so can maximize the OBC. 60€ delivered. It's from the series I use with my Leaf (only that is adjustable up to 32a). Fingers crossed the Ion 'likes' it!
I’ve see this ‘hack’ on a German forum, symptoms: newer type 2 public EVSEs wouldn’t work with older clones using type 2 to type 1 cable/adapter.Maybe I didn't say my prayers right.