I recommend connecting 4 car batteries in series. Charge them individually, in parallel or in series beforehand. This way you have no problem with the current and can also test the recuperation. Running a charger in parallel during the test was not a good idea for me, as it was destroyed during ...

This description states that the “33” only describes the destination market. The entire type designation is also explained there.

my googling has led me to this link.https://tr.aliexpress.com/item/1005008459058700.html. The MC33771ata is sold there, the photo shows a MC35771ata. Further googling shows that it is a BMS chip from NXP. The datasheet at mouser https://www.mouser.de/datasheet/2/302/MC33771B_SDS-1517286.pdf. I think ...

I still have two.

for my understanding, what triggers an “overcurrent” message. Of the 7 inputs on IC10, 6 come from the error lines of the gate driver. One comes from IC8, and is also transmitted to the CPU. The output of IC10 suppresses the PWM. Is this suppression also output as an “overcurrent” message? If not ...

I have dismantled an older one and used the technology for a show vehicle. Many of the CAN messages are the same. It no longer looks like a Street Scooter.

LRBen wrote: ↑Mon Oct 28, 2024 9:51 pm Only thing left to crack is the CRC required

Do you mean the CRC in BO_ 536?

Why did you need 32 minutes in lap 370, it seems to take about 10 minutes normally to change the battery?

P.S.Mangelsdorf wrote: ↑Tue May 06, 2025 12:11 pm I'd probably go with a de Dion style axle

I like DeDion, I have also installed it, together with air springs and a triangulated four link.
viewtopic.php?p=15994#p15994

P.S.Mangelsdorf wrote: ↑Sun May 11, 2025 4:29 pm 2.64sec 0-60mph.

I really need your parameters
How heavy is your car?

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 ...

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

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 ...

I have now made tests with the version 0.44.100.B. The offset parameter works well. The UdcDevider is too coarse. After setting the offset to 561, I applied 318V, resulting in AdcInletVoltage of 1425. With UdcDevider = 3 I get 288V and 432V with UdcDevider = 2. My suggestion is dig/100V ...

How to kill the lock motor?


This is consistent with my observations. The immediate jump back to “open” also irritated me.

A few more ideas on inlet voltage and contactor: If a separate measuring device is selected for inlet voltage, this should not replace the voltage transmitted by the DC ...

At the end of the charging process, my charge controller and Foccci are also switched off. My current requirement is 600mA in the waiting phase. This is low enough for 3 days on my 12V battery. I will set up a timout that stops everything if no charging has started for 24 hours. I will set the timer ...

This is how I imagine charging with the OBC: The cable is plugged in. Foccci and my charging controller wake up. Foccci reports cable plugged in, my controller sends lock and waits for a valid PWM. When PMW starts further controllers for cooling etc. and the high voltage is switched on with Pre ...

Why not? Locking only needs power when locking, after that it doesn't matter. If I don't want it, I don't need to send AcObcState= Lock

I have just tried it on my OEM car. It locks even with a naked cable only with a resistance from PP to PE.

what is the version of your firmware on the Foccci?


0.44.95.B

It appears that enable must be sent and a 10% -90% PWM must be applied to the CP for the lock to change to closed. How does this work with a wallbox that is not sending PWM? I think this is the case when a wallbox is controlled by ...

Now I have the next problem. I have now set LockRunTime to 700 and the treshhold both to zero. I plug in an AC EVSE. My VCU sends AcObcState = lock. Foccci recognizes everything correctly, PortState is ready, Lock remains open, but my VCU waits for Closed!

Which resistance values do you have in your actuator, in case of locked and unlocked, @muehlpower?


My port is from Duosida. The locking mechanism is a screwed-on part with an electromagnet and a switch. Four cables are routed out, two for the magnet and two for the switch. The switch is closed ...

Now I still don't know what to set if I have 100 and 3800, for example. One to 3600, the other 400? Which one to what? or both to approx. 2000? Or even set one to 0 and the other to 4095? And will the actual position then be shown in the spot values, regardless of how the lock got there, e.g ...

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.


does it matter if the value for locked is higher (or lower) than the value for unlocked?

I have also not yet found out what there are two parameters for ...

In my opinion, the most important thing would be not to deactivate the “LockRunTime”, then I wouldn't need a new locking motor. On the car side, an incomplete locking process could be recognized by “closing” instead of “closed”. The OBC and the enable signal can then be controlled accordingly.