Search results

This is what's under there, with the top board unsoldered: With the white gunk removed: How the connections are wired: Resistor R601 and capacitor C601 were damaged. I need to figure out what value R601 is, since it was burned beyond recognition. The schematic for the power supply...

Or not. According to this application note, that resistor acts as a fuse. It looks like 10 kΩ 0.25 W might be suitable, and hopefully the exact value is not critical.

Ah, I'd forgotten all that; thanks for the reminder and pointers. I think I still have some 39 k M1608 resistors here from that time. Unfortunately, it looks like these two charrgers use totally different ways of powering the un-isolated side of the isolation amplifiers. 2012+ seems to use...

Kiev, you're going to love this: there is a Viper chip down there! And that part of the circuit burned; photos and details soon. The Viper chip is SMD and has no heat-sink, but it has the classic 4 pins on one side all connected together. It seems that this Viper chip provides power on the...

From an earlier CAN bus log, I noted that the DC output current was being reported as 25.5 A, the highest possible value (0xFF = 255 tenths of an amp). Initially I assumed that this was because of my bench configuration, not getting CAN bus packets from elsewhere. But member Kiev reminded me...

Actually, that's a really good point, thanks! Indeed there must be a shunt there. I think that these are the pins up from the lower PCB at the input of the measurement op-amps: There was an X-ray, but only of the AC input module, and I'm 95% sure that the input module is working OK. It was a...

I thought I might learn something about how OBC PIDs get converted to "real" CAN bus messages, by using an old EV-ECU: Alas, I could not coax any life out of it, other than drawing a bit of current. The current twitched encouragingly as if it was sending a bunch of CAN bus messages or doing...

I can't help with another thermal image, but I can show ordinary photos. It doesn't seem to be an identical model, unfortunately. Overall, for context: The bottom board: You can see that the AC input capacitors are prone to oozing; I have seen other photos of them more or less exploding...

I've had a small win with the 2010 charrger that I'm repairing. Long ago I attempted to get CAN packets out of the charrger, but didn't get a peep, not knowing the magic CAN bus incantations to wake it up. But I think it was one of Piev's posts a week or so ago gave me that information, and all...

According to the datasheet that is archived below, the original relay coil should be 62 ohms plus or minus 10%. I vaguely recall a figure of 56 ohms. Edit: https://forums.aeva.asn.au/download/file.php?id=5663

It might be a perfect fit mechanically, but it's rated at 5 W where the original is rated at 7 W. The initial power through the pre-charge resistors, if connected to 240 V, is E²/R = 120²/4.7 = 3064 W. Much higher if the power happens to come on at the peak of the sine wave. The Mouser resistor...

What sort of codes would these translate to? I don't see any that look like good candidates.

Wow! Thanks.

Yes, these CAN related posts seem to be scattered over several topics. Interesting. Do we know where the extra chip leads to in the Laef? They (the junction connectors) are present in the schematics. That's how I thought it worked too. However, when you look at the schematic here...

Ok, that's pretty good evidence, thanks. What responses have you seen in 0x766?

What evidence is there that the OBC is at 0x765 (OBD commands) and 0x766 (OBD responses)? I had another play yesterday and it seems that you have to talk direct to the ECU (e.g. at 0x761 for the BMU), not 0x7E0. Though I see that I forgot to try 0x7DF, sigh. So if we got the CAN ID for the OBC...

What would be really great for me is if you can monitor the CAN bus while the MUT requests the internal diagnostic code of the on-board charger. It's not clear to me how this is obtained from the MUT-3, as "data list" for the OBC or perhaps EV-ECU, or as freeze frame data from a diagnostic code...

Maybe you need to be charging for the OBC to wake up? That's how it is for the MG.

Not a big surprise. If I wasn't so bad at reverse engineering Windows code, I'd have a go at VCI_bridge. Maybe one day.

How about the excellent, though long, Troubleshooting and repair for On-board Charger (OBC) .