QCA7000 Foccci+Clara User thread

[muehlpower]

With my AC charging implementation, locking works as long as the two treshholds are the same or with feedback if the mechanism is not blocked. A mechanical opening remains unnoticed. With AcObcState I have not found a value that unlocks again. I could help myself if I use the new ActuatorTest for closing and opening, then only the switching of the 1k3 resistor remains for AcObcState, since I don't use the LED control anyway.

[uhi22]

Does UdcDivider 2.72 not work?

[muehlpower]

I didn't try any decimal numbers, but you're right. Now it works and I get 320V.

[uhi22]

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 feedback in the spot value LockState is calculated in software, just based on the time.

1=TimeBased_HwFeedback. The motor is controlled for the LockRunTime, once a new request comes in. Independing of the actuation, the hardware feedback is always transferred into the spot value LockState. This only will have the states Closed or Open. No intermediate states Opening or Closing. Not sure whether this needs to be improved.

2=FeedbackBased. This is the old behavior. Motor is driven as long as the target state is not reached. Risk for smoke. Some unclear implementation for the "states in between", in two dimensions: Level-wise, what shall happen if the analog feedback is in the middle range. And time wise, do we need to artificially create the states Opening and Closing even we have a digital feedback switch. Needs to be analyzed whether we want to keep / improve this behavior.

So for the muehlpower use case, the option TimeBased_HwFeedback should be the solution.

Binaries: Build #101 in https://github.com/uhi22/ccs32clara/actions

[muehlpower]

I have installed the new software and adapted my programming. It works well. My system is activated with a button (white light). If nothing is plugged in within 30 seconds, it is deactivated again. After plugging it in, it locks, regardless of the PWM (orange light). If a suitable AC PWM is present, the main contactors are closed and the control unit for the cooling and the DC-DC converter are started (blue light). As soon as the EVSE supplies current, charging begins (blue flashing light). The charging process is interrupted if the PWM is missing and then starts again. The main contactors are opened and the other things are also shut down. The second video shows an error when the plug is not fully inserted (red light).