openinverter forum

Is there a cross-reference for spot value definitions?

I see some things change, but a lot of zeros where I think there should be values? I'm guessing idc and udc would be key parameters to look it (DC current and DC voltage?), but both are zero. Proximity is "Off", but I have the proximity and pilot wires connected from the charge port to the control board. I realize I'm making assumptions here about what things mean what.

I cannot see what you see. Show your parameters and spot values via screenshots.

You say you wired proximity and pilot, did you also wire the ground to the charger and the charger to the 12V ground?

Parameters?

None of the modules are reporting anything, are the leds on?

Parameters are here:



Module LEDs are on.

tom91 wrote: ↑Thu Jul 11, 2024 5:41 pm Spot values.

You setup your controller properly and check the EVSE values populate as expected?

https://openinverter.org/wiki/Tesla_Mod ... N3_Charger

https://openinverter.org/wiki/Tesla_Mod ... 5_Software

Does that mean my parameters are incorrect? I think I have it setup correctly, but I'm not certain.

Does state = run mean it's actively charging the battery?

RobCote wrote: ↑Mon Jul 15, 2024 2:32 pm Does state = run mean it's actively charging the battery?

It means it is trying, there are spot values that show the battery voltage (udc) at the charger modules and values for the DC current (idc).

tom91 wrote: ↑Mon Jul 15, 2024 2:45 pm It means it is trying, there are spot values that show the battery voltage (udc) at the charger modules and values for the DC current (idc).

These are always zero. I measure 298VDC at the battery connection terminals on the charger (this is the pack voltage) when the contactors are closed. Just to be very clear, am I correct in assuming the values for udc and idc are what the charger is outputting as opposed to just a measurement of the battery?

Voltage is the measurement from the charger modules

Current is what the charger modules report outputting

All measurements are reports from the charge modules, each with their own spot values with a "c1" "c2" or "c3" in the beginning of the name

That's what I thought, but thank you for verifying. So, something is preventing the charger from doing its thing still, but I'm not sure what.



Do any of these parameters jump out at you as needing to change? I've tried iaclim at 6A to avoid overloading my outlet (15A 120VAC source). Chargerena = 5 because I have only two charger modules (48A US-spec charger). I've tried all available options for inputype. I think it should be type 2, but I'm a little unclear on the specifics of each option.

input type should be set to your charge port. Do you have a Type 1 charge port used then set it to this.

This then will have it read the EVSE Control Pilot and Proximity and use this to try and start charging upon plugging in.

Oops I wasn't sure if it was a reference to the EVSE or the source outlet type. It refers to the charge PORT?? I don't even know, in that case. It's a model S charge port, just without the actuator for the cover thing.

Set it to Type 1, check is the control pilot populates. If it is using CANsw which Tesla use it wont work. You need a "standard" J1772 EVSE and control pilot.

Oh, crap. I'm using a Tesla charger. I guess that's my issue. Thanks, I'll try a different one.

I tried a different charger - no change. What am I missing?

Does it start the EVSE and go into run mode when you connect the EVSE?

Yes. EVSE shows it's supplying 0.2A and flashing green which indicates charging. Udc and idc remain at 0.

This is a stupid question but so am I. The battery pack was in a pretty decent accident which exploded all the airbags, but the pyrofuse seems to not be blown. It's not an open circuit - is there some other way to test it? I have heard that by design the pyrofuse is supposed to blow when the airbags do.

You need to apply the DC HV at almost same time as EVSE activate, there is an output for this. OUT1 - HV enable

The modules should get activated and report some CAN before stopping. Do you see the modules start and the LEDs light up?

The modules light up, yes.

Is out1 12V?

It doesn't seem like timing of events makes any difference. How tight is the window?

Is charger module temperature an interlock to charging? I'm not certain what this 2-wire component embedded in epoxy is:



But my best guess is a temperature sensor? Anyway, didn't realize they were connected when I removed the modules, broke the leads. Not sure how to ID them to replace them, so kind of hoping they're not strictly necessary.

Is there a way to temporarily ignore temperature within the software if that's a potential roadblock, to see if that's the hangup? Then I can work on figuring out how to replace them if necessary.

RobCote wrote: ↑Fri Jul 19, 2024 9:59 pm Is out1 12V?

It doesn't seem like timing of events makes any difference. How tight is the window?

Timing is ciritical so best let the software take care of it.

The outputs are lowside, so pull to ground.

tom91 wrote: ↑Sun Jul 21, 2024 1:10 pm Timing is ciritical so best let the software take care of it.

Can you expand this a bit? I'm not quite sure what you mean. You said that it's important to apply HV at nearly the same time as connecting EVSE, but now you say to just let the software handle it?