Update: Success! After many fixes, was able to repeatable charge at 700v+, 20A+ with mostly no problems. Found the PP issue lied in the dc/dc converter we were using. There was a defect from the factory and it was not properly grounded, giving FOCCCI an incorrect reference. Replacing it with a new o...

There are physical connection issues. I do not think the issue is physical connectivity. I ran some more unloaded tests (values under 500v to negate any din/iso issues), and the PPresistance values were reading nominally until I initiated the charging sequence. I tried this with two separate charge...

I'm using screen on debian. I'm now saving the old log to gDrive, then removing and logging rather than overwriting. Conducted a loaded test today. Same Cable Check fail. It seems that PPresitance goes to 10000 in the middle of the test. Statically, a multimeter reads 150 ohm between PP-PE which see...

Whoops, looks like the output file may be partially overwritten by the new log, and the rest of it is from the first file I uploaded. Looks like screen doesn't start from fresh when overwriting a log file, but rather operates concatenates. [1191140] [PEVSLAC] from 2 entering 4 [1191170] In state Off...

More reliability issues: Having made zero changes since the last loaded test, unloaded tests today resulted in the charger faulting during CableCheck. I've attached the logs below. It has many errors still, as I couldn't secure a shorter cable/better UART-USB device but I will soon. Any thoughts as ...

johu wrote: ↑Sat May 11, 2024 9:18 pm Nice, so will this work with all chargers out there, even old ones?

Upon completion, this will exist simply as a firmware update then?

johu wrote: ↑Fri May 10, 2024 5:59 pm For Precharge TargetVoltage isn't used but BatteryVoltage. Is that mapped correctly?

I believe this was done to verify the upper limit of the charger (if you mean that the values are the same, I am a little unsure what you mean)

uhi22 wrote: ↑Fri May 10, 2024 7:39 pm Nobody tried above 500V, I guess

Hopefully this works then

Screenshot from 2024-05-10 10-41-59.png Found the problem with the incorrect target value. Silly-mistake: Can-mapping was incorrect. Above was the incorrect mapping in which only the first byte was taken in. Below is the message: image.png image.png Corrected it to this ^. I don't have access to th...

uhi22 wrote: ↑Fri May 10, 2024 8:56 am Is your charger rated for 800V?

Yes, up to 1000V (if the doc is correct)

The DIN schema, which Foccci/Clara uses, supports ususally 500V maximum voltage Is there any way around this? Our stack is 800V at ~100% soc. Possibly some sort of software workaround to fudge/nudge the numbers? I guess an option may be to split up the stack but this is also quite intensive. I'd pr...

No. In the log we see e.g. [931600] ResistanceProxPilot [ohm] 895, this is for sure not consistent (or at least the explanation is missing). And it is not consistent that later in the log the ResistanceProxPilot jumps to around 200 ohms. It would be really helpful to know the real resistance, and t...

Ran new test, no liftoff yet but almost made it off the pad. I've attached the logs from the latest test. Made it deep into pre-charge but then the EVSE would fault. Could also be normal. The PP resistor should be in the plug and nothing else is mandatory on the PP. Is it possible to take a multimet...

Opened the charger. Looks like the PP line was disconnected completely from the factory (on both chargers). Supplier seems to have confirmed that this is not intended. Will test again tomorrow and hopefully this fixes the issue

Just to be sure, "sharing the same PE" means, that the following signals are together: - Ground of Foccci - Ground of the 12V supply that feeds Foccci - PE of the CCS socket - minus of the multimeter if you measure the PP voltage on car side (around 4.5V if nothing is connected). - ground...

And there is also confusion regarding CCS1 and CCS2. The thread topic says "CCS1", also the picture shows a CCS type 1 plug. On the other hand, I read "Qingdao Penoda Portable DC CCS2 Charger. I knew there are differences between CCS1/2 (I did not order this charger)". So maybe ...

Managed to secure access to another portable charger and I seem to have found the source of connectivity-recognition issues. The charger that worked was providing 12V across cp-pp. resistanceproxpilot danced around 830ohm. CP was still 0 but that's because I hadn't activated the charger (with an rfi...

Does the charger provide 12V between CP and PE if just sticking the multimeter probes into the CCS plug? This was showing 0v. Across the inlet, CP-PP was reading <5v. IMG_8834.jpg Just flashed the new clara pushed. Thanks for the update, will test. Edit: Tested. Charger is still showing 0v between ...

The lower picture, without the switch in the connector, is CCS type 2. For this, the PP pulldown is optional and can be 2k7 or 4k7 (or not present at all). Thanks for the official data, this confirms the understanding with the 330 ohms to 5V. So in this case, if the charger is a CCS2 charger (which...

uhi22 wrote: ↑Thu May 02, 2024 8:17 pm The logs are saying all the same: No response from charger. The SOC does not matter at this stage. Any chance to measure the CP PWM, in the web interface and with an oscilloscope?

CP PWM was measuring 0, scope as well. Only non-zero was the 4.5V measurement across CP and PP.

CCS1_vs_CCS2_signaling_circuit_2.png Shows the differences Also wondering if this is a change I may have to make. I found these bits of doc in the CCS1 protocol documentation and it seems that in a certain setup, 4.7k is optional? Again, I'm not very knowledgeable in this space so I figured I'd thr...

3) It appears that SOC is not strictly for display (at least on the PhiPhong charger). It does enforce some safety monitoring. The charger faulted out and would not restart when we hit 95% SOC (number was incorrect, we were probably closer to 75%) with 80kW charge power. When the transmitted SOC nu...

Ran into trouble :) Again, the charger will not recognize when it is connected. I verified continuity across all my connections but noticed only 4.5V across CP and PP. This would seem to be outside the range you mentioned earlier. I have attached three screen shots. The first is sitting unconnected,...

Redid most of the connections and that seemed to fix the issue. My guess is that one of my temporary lever connectors wasn't totally secured and causing my headache. Wasn't able to connect the vehicle but I connected the EVSE and it recognized the connection again. My other guess as to the cause is ...

uhi22 wrote: ↑Thu Apr 25, 2024 7:13 pm The 0% CP duty is clearly pointing to an error, either of the charger, or of the wiring

The charger I am using requires a "start charge" button press once it recognizes that it is connected. Even before this initiation, should there be a >0% reading on CP duty cycle?

Keep attempting to charge but without making any hardware changes, the EVSE seems to have stopped recognizing when it is plugged into the inlet. Is there anything on the software side that could be causing this? All I am doing before charging, outside of sending can data to the charger, is set enabl...