A mechanical opening remains unnoticed


Now introduced a parameter to select the intended lock control behavior: LockControlVariant
with the possibilities
0=TimeBased_VirtualFeedback. The motor is controlled for the LockRunTime, once a new request comes in. The hardware feedback is ignored. The ...

Exactly. Or find the wire inside the car, cut it and plug the electronics in between.

Does UdcDivider 2.72 not work?

For the inlet voltage plausibilization, implemented a draft. It works like this:
- The voltage measured by the hardware board is always reported in spot value InletVoltageHw.
- The voltage reported by the charging station is available in spot value EvsePresentVoltage.
- If the hardware measurement ...

Good ideas.

- For the separate control of the DC contactors via ActuatorTest, created issue https://github.com/uhi22/ccs32clara/issues/53 and implemented the feature. Binaries available in the continuous integration build #99 on https://github.com/uhi22/ccs32clara/actions

- For the inlet voltage ...

Oh, and when you're testing it I suggest doing so with an actual plug rather than through the web interface. For some reason it doesn't always want to respond to open/close commands there. So you could find yourself confused why it's not working, only to realize it's actually working just fine ...

How to kill the lock motor? Just tested, and found:
Preconditions: LockClosedThresh=2000, LockOpenThresh=1900. LockRunTime 1500ms. Feedback line open, so it is at high level, I get AdcLockFeedback=4036.
Action: Power-on.
Observed: Lock motor is controlled into direction "unlock" for ever.
Expected ...

I also have seen cases where the 1.2V got higher then intended. These were solder issues, like missing ground on certain pins or missing ground on center pad. The good news is: all my QCAs survived these situations and work perfect after proper soldering .

I had some frustrating experiences with such jumper wires and in the meanwhile I'm back to soldering. Sure with good quality connectors there is no issue, but the cheap jumpers which I got were best placed into the trash bin.

messages are send to address 0x3c0, byte 0 is CRC byte 1 is cyclic for the first half of the byte (0 to F) and the is enable signal byte 6 is forward/reverse (3f/40) and byte 7 is throttle 0-100 for forward and 100-0 for reverse.
...
hopefully someone can help with figuring how the checksum CRC is ...

Really a pity. Some ESP are more crappy then others, maybe you can try whether an other one feels better. Power supply may be one issue. They need a lot of current for WiFi, and if the capacitors are too small they run into strange effects. Maybe add some 100n ceramic Cs and 100uF elcap.

Regarding the lock motor control and feedback variants, created a separate issue for the detailled discussions.
https://github.com/uhi22/ccs32clara/issues/51

A UdcOffset parameter in addition to the UdcDivider would also be good, as the BMW measuring system, for example, does not output 0V at 0V HV.


Just added the parameter UdcOffset (in digits) and a spot value AdcInletVoltage for easy calibration. Have set the default values to fit (nearly) to ...

The currently implemented range detection is:
- We have two cases: (A) "closed" is higher resistance and (B) "open" is higher resistance.
- For (A):
if AdcLockFeedback is low (between 0 and <LockOpenThresh), we detect OPEN.
if AdcLockFeedback is middle (between LockOpenThresh and LockClosedThresh ...

I see room for improvements:
- It is not clear, how to adjust the two threshold values. It does NOT help to adjust them to exactly the measured values in both states, because then we just get random behavior. We need to define whether they shall be set below or above the measured values. Or set them ...

If the plug is not fully inserted, I have the choice between “I don't notice that it's not locked” and “the motor smokes because it doesn't switch off”.


Good point. Need to check what happens in case of not fully inserted plug. The goal would be: do not allow charging, set an error to make the ...

What is the half price of the 7kW? Is this three-phase euro 230/400V?

Good news: The CRC algorithm is the same as used in Tesla. Created a program which reads the above two log files, calculates the CRC for each message and compares it with the transmitted CRC. Result: All pass. CRC ok: 91622, CRC fail: 0
Github: https://github.com/uhi22/tesla-crc/tree/main/vag

I see two ways:
1. The cheap: capture the SPI traffic in the vehicle or charger, between the modem (QCA7000) and the host, using a Saleae logic analyzer (clone). I have a python script on my github to convert the saleae data into pcap, to view it with wireshark.
2. The expensive, universal, state-of ...

Ahh, I just see the attached logs above, I will have a look into them in the next days.
If you have longer logs you could extract the lines with the esp_21 message (eg using linux grep command) and provide the extract.

The snippet of the DBC above shows that the checksum is at bit 0 and has 8 bits, and the counter starts at bit 8 (means: in the second byte), and has four bits.
The CRC algorithm may be similar to one of the profiles described in the AUTOSAR E2E specification. I described a similar method which ...

The shown code does not include the alive counter (which should increment with each message), and also does not contain the table with magic bytes. So it cannot produce valid E2E protected messages.

The orange connector is just the power connector, L, N, PE, containing a HV-interlock bridge to detect an unplugged connector. Seems the CP and PP was running on a separate connector that was cut during dismantling.

The "CCS plug" is female. The pins are intended for "low-power" vehicles.

The PE pins of 32A CEE red have the matching diameter and length. Found two different types.