Could the following concept work: - for the high-power stuff use a 22kW charger from a car. This takes 3 phase AC and provides HV DC. I think Damien reverse-engineered a MG charger which seems to be controllable via CAN easily. - into the type 2 direction, use an Arduino which measures the CP PWM an...

To simplify trouble shooting the CP and PP lines, added ResistanceProxPilot to the serial logging. If the charger is plugged in, we should see something like cpDuty [%] 5 ResistanceProxPilot [ohm] 1495 The CP PWM duty cycle should be between 4 and 6 percent (5% nominal), and the PP resistance betwee...

On my daily way, I see a Tesla M3 (or Y?) at a "dealer". It has quite some crash impact on the back, but I think a lot of parts are still in a good shape (battery, drive unit). It is sitting there since weeks. Personally I do not have plans, but if anybody is interested, maybe it is possib...

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? There are two different use cases: CCS type 1 and CCS type 2. The upper picture, with Rs3 and Rs4 and button in the connector, ...

Does the charger provide 12V between CP and PE if just sticking the multimeter probes into the CCS plug?

1. At room temperature, after running some minutes, my AR7420 is around 52°C (measured with infrared thermometer). Touching with the finger is okay for 10s, then it hurts. If yours is much hotter, just use a new one. Maybe killed by overvoltage or something. 2. I see no error in your original.pib. I...

The plan is, that the bin and hex files are available at the link https://github.com/jsphuebner/FlyingAdcBms/actions How does this work? Johu configured a "continuous integration job" to the github. This job automatically builds the software and stores the results. Each run is listed on th...

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?

The "conversion" of your findings into a DBC file is indeed a manual process. You found out, e.g. for Lamp1, which CAN ID and which bit in this message controls the lamp. This information you put manually into the data base file (dbc). You can do this with the DBC editor which is included ...

Do you plan to have isolation between the CAN and the shunt terminals?

Great. In case you are charging (or run into trouble) it would be nice to provide a logfile, and the charger type if possible.

Great. I just used a random ID, for me it does not matter.

Using the bus number 3 the transmitting works. This number is also shown in the main window. Not sure why it is number 3, but at least it works.

One topic to improve in pyPLC, maybe this improves the Tesla behavior: We are sending in the PreChargeRes "EVSEStatusCode_text": "EVSE_NotReady". The alpitronic and the supercharger are sending "EVSEStatusCode_text": "EVSE_Ready" [Edit] Pushed the fix: https:/...

Cross referencing a potential root cause: mixup of PP and CP: viewtopic.php?p=70247#p70247

Regarding the "8 bit" for the ChargeCurrent: Cannot confirm this issue at the moment. Using SavvyCAN to transmit the value 499A (hex 01F3), and this shows up in the web interface: image.png Using this CAN mapping: image.png The path in the software from the parameter itself to the CCS stru...

Just noticed, that the transmit path of WifiCAN has a problem. The transmit messages, which I configure in SavvyCAN are not physically on the bus. Investigation is ongoing.
https://github.com/uhi22/wifican/issues/1

Nobody knows. Best would be a scope to check

Not sure I got it right. You moved the Instruments using vcds and recorded the CAN Düring this? And then play back this recording? This does not help. The vcds uses diagnostic commands (uds on isotp), but you want plain CAN in the car.

Ok, at least the results are stable, that's a good basis for finding the issue. There are two indications, that something with the wiring is wrong: - The CP PWM is reported with 0%. This shows that either the CP is not wired to the charger, or the charger does not provide the PWM at all. - The cable...

The 0% CP duty is clearly pointing to an error, either of the charger, or of the wiring. First point is to take a multimeter, and measure on the unconnected charger whether there are 12V between CP and PE. Second, check whether the CP of the inlet is connected to the CP pin of foccci. Third, with re...

Many thanks for updating the wiki. I also now updated the wifican documentation, and added links to the wiki and to this thread.
https://github.com/uhi22/wifican?tab=re ... tart-guide

Edit 4: Tesla ... also OK now Do you say thay that you convinced the Model Y to close the contactors, without providing physical voltage during the PreCharge? We tried, but without success, using the latest pyPLC and two different Model Y, as I understood one quite old and a newer. They stop the se...

Physically this exacty is the case. You can charge and discharge. The only blocker may be the software of the car, which could have a supervision that stops the thing. Some results are mentioned above in the thread, the MG is showing how great it could work.

serh270 wrote: ↑Tue Apr 23, 2024 7:28 pm is there an upper bound to how many times a sec it can be sent?

Good point. Not sure if somebody tested what happens if you send it each 250µs. But I think everything between 5ms and 500ms cycle time is fine.