Description of the issue: the customer Ride Share (also known as Spark) reported that the vehicle does not react to lock/unlock commands properly, the car cannot be locked or unlocked. The system on the customer's side shows ATH_FAIL or similar error.
This article is applicable for vehicles that use ATH_INV installation method using 1 DOUT to control Lock/unlock commands +1 DOUT for ATH (Ignition blocking). This includes but is not limited to:
Renault Zoe
Peugeot e-208
Peugeot e-2008
Opel e-Mokka
Common causes:
User mistake (Open doors/hood/hatch);
Incorrect LCV door state is received ("open doors");
Delayed or incorrect reception of "CAN door lock state";
Physical connection issue;
Faulty CAN communication (rare case, needs to be investigated individually)
Troubleshooting steps:
1. Check whether "CAN door lock state", ignition blocking (DOUT2) state and Lock/Unlock control (DOUT1) are changing correctly:
Normal unlocking (UNLOCK_UNBLOCK) behavior:
Normal locking (LOCK_BLOCK) behavior:
Note: "CAN door lock state" value "255" is typical for some vehicles during the moment of command execution:
Note: in case the LOCK_BLOCK command was sent to the car which was already locked (with remote commands), the car will unlock shortly for a few seconds and the lock again. This is due to only one DOUT controlling both locking and unlocking.
2. Detect abnormal behavior when commands are sent:
Lock/Unlock DOUT is not triggered -- most likely, command does not reach the device. Check DCS commands whether they are executed properly. Additional investigation may be needed.
Note: Also check whether it could be DEVICE_OFFLINE issue.CAN door lock state does not update (remains "1" or "0") -- most likely the doors were locked by a physical key (remote control). Double check the raw data whether the car could have been locked by the key and inform the client that the car was probably locked with a physical key (they should unlock them with a secondary spare key from their office);
CAN door lock state does not update (is stuck on "255") -- most likely either there is an installation issue or the on-board computer is "sleeping. Try to send several different commands to the device and check if the states are changing. If not (state "255" remains), testing on the location is needed after the car is unlocked with a secondary spare key.
Ignition (un-)blocking is not triggered -- Check whether the vehicle doors are unlocking and "CAN door lock state" is updating properly (refer to the points above);
Ignition (un-)blocking is triggered but does not work -- most likely there is an issue with a blocking relay. Double check before registering a repair or suggesting a physical check-up.
3. In case the scenario is unclear, consult with EU Global support.