This is the error. In state B the Foccci should have only 2k7 resistor, which leads to 9V nominally. [Edit] On Foccci there is a LED for state C. You could try to switch this via the parameter ActuatorTest. This should lead to - LED off, is state B, is 9V - LED on, is state C, is 6V [Edit 2] And che...

5.6v is not state B. B is 9V.

Two ideas: - check the voltage levels of the PWM with the oscilloscope. It should be -12V and +9V after plugged-in, and later, when the charging is active, it shall be -12V and +6V. - Foccci does not contain more than the blue box. But if Foccci would have closed the state C switch, some chargers ma...

Definitely. The plan could look like this: Add a CAN shield to a Raspberry or similar, to have a CAN which controls the huawei power unit. Then some lines of python are necessary in pyPLC to send the voltage and current demands on CAN, and to read the present voltage and present current from CAN. Lo...

image.png If your charging station tells you a CP error, it want's to say that it did not detect the circuit in blue box. I see three potential root causes: 1. The charging station is defect and tells bullshit. 2. The wiring between the charging station and Foccci is wrong. 3. The Foccci does not b...

Did you follow the syncofs calibration process that Damien explained?

What do you mean with CP error? Where/how do you observe this? Do you use CAN to control the state C? Does the charger close the relay if you just connect 2k7 and diode, and in a second step the 1k3? Foccci should do nothing else.

Maybe watch Damiens video where he and Johannes explain the connection and parametrization of resolver, syncoffs, and so on, also manual mode.

To divide the search range I propose to look on the CAN, eg using SavvyCAN. In best case this shows that the messages are on bus (multiple times per second) and you could check their content.

It would be helpful if you describe your observed behavior and expected behavior. E.g. nothing is shown on your display, or values are arriving but with wrong values or missing completely or start ok and later are stuck or or or.

Looks good. Just wire CANH, CANL and ground to the wifican and add a 12V supply. Then clip it to a CAN and show us what you see. What is missing?

This leads to the next question. Which is the expected behavior? (E) It is normal, that the angle spot value changes multiple times from 0 to 360°. Because the angle is a "virtual angle" which counts per (resolver?) pole pair, not per physical revolution. (F) During one physical revolution...

In the description of the parameters and spot values https://openinverter.org/wiki/Parameters we find "dir", with the explanation Rotation direction. -1=REV, 0=Neutral, 1=FWD This could help, to split the search range into two two smaller search ranges. There are two possibilies: (C): The ...

So, I got my CANcrocodile, along with an ESP32-S3-Pico board. My wonderful friend CHATgpt just doesn't seem to be able to dumb things down enough for me to create an interface to use the CANcrocodile to sniff the CAN Bus. Did not get the point where you are stuck. Do you have the CAN hardware runni...

There is confusion, maybe due to the translation. Which of the statements is true? (A) The motor is spinning in the opposite direction. You select forward, and it moves backwards. You select backward, and it moves forward. (B) The car always moves backwards. You select forward, it moves backwards. Y...

There are also 11kW public chargers, and drawing 22kW from them could blow the fuse. Means: evaluating the PWM makes sense.
And: There are public chargers with fix cable and plug. Means: Having a type 2 socket in the charger gives more flexibility.

As I'm not using a linux system, I wasn't able to get trace message I recommend to record the SPI traffic, and convert the SPI data into a pcap file, which can be inspected e.g. using wireshark. The workflow is described here: https://github.com/uhi22/Ioniq28Investigations/blob/main/CCM_ChargeContr...

Slightly off-topic, but does anyone have spare QCA7005 chip to sell, 1-2pcs? Good question, did anybody find a reasonable priced source in the meanwhile? (I'm dreaming of below 10€) Regarding the versioning: The latest version is on johus wakeup branch. If further tests are turning out that this is...

For the beginning, find out how many CAN busses go to the battery (hopefully 1). Find out the baud rate (with oscilloscope). Record some CAN traces (savvycan). Eg recording a complete short charging session and a short drive.

Great, congratulations! - The "maxPower" parameter didn't seem to stop me from setting voltage/chargeCurrent to values exceeding the set max wattage. - MaxVoltage didn't seem to prevent me from setting target voltage higher (did not prevent the output power) - MaxCurrent did not prevent me...

It does not help to try random things. The goal is to find the root cause, why the PP resistance is not 150 ohm. This is a simple resistance measurement, where not much can go wrong. Theres a certain chance, that fixing this issue could also fix the failed cablecheck. To find the issue with the PP r...

There are physical connection issues. Back to 8th of May: 2. When plugging and unplugging, you should see in the web interface resistanceproxpilot changing between 10000ohms (means infinite) to whatever your charger has. 3. If nothing helps, disconnect everything, use a resistor (something between 1...

Created https://github.com/uhi22/ccs32clara/issues/17 regarding missing stack pointer initialization, which is one reason that Clara crashes on the iso-test branch. Any hint welcome. [Edit] The missing stack pointer initialization is solved now on the iso-test branch. DIN works again, ISO not yet te...

Normally there should be no need to "call .ino files" and "adding header files". The arduino IDE should automatically treat the ccs32.ino as main file and show all the files in the project, without the need of calling or adding something. The only arduino-specific things need to ...

serh270 wrote: ↑Sun May 12, 2024 8:56 am There's this odd change in log value numbering.

Do you talk about this: [705380]? This is not a "log value numbering", this is the time since Foccci was powered-on, in milliseconds.