Skip to main content
All CollectionsKnowledge Articles (Internal base)Car sharing
Ride Share object cannot lock/unlock the doors
Ride Share object cannot lock/unlock the doors
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

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.

Possible causes of the issue:

  • User mistake (Open doors/hood/hatch);

  • Incorrect LCV door state is received ("open doors" while they are closed in fact);

  • Delayed or incorrect reception of "CAN door lock state";

  • Physical connection issue;

  • Faulty CAN communication (rare case, needs to be investigated individually).

Troubleshooting steps:

Note: The troubleshooting steps provided here are generalized for all vehicle models. Information regarding specific models is provided in the follow-up articles below.

1. Open the object and webuser according to Basic troubleshooting for Car sharing objects;

3. Check for possible user mistakes (door/window is open, while client is trying to lock the car (normal behavior):

blobid0.png

Note: if possible, confirm with the client whether all doors and windows are closed.

4. Identify abnormal behavior:

ATH_FAIL without specific comments:

mceclip7.png

Example: "open door" error when client cannot unlock the car:

mceclip0.png

In case DEVICE_OFFLINE error is displayed, it may be a different type of issue.

4. Check the vehicle model in Object settings in LCM:

mceclip0.png

5. Check the installation method used in the vehicle from the Confluence page:

mceclip2.png

Note: Be careful - some vehicles can be connected using older methods! Which method is being used in the specific device can be checked in CFG update module, with configuration file name used:

mceclip1.png

6. Take notes which DOUTs are used for commands execution for this specific car model, this information will be needed during diagnostics. Notes on the right side shall be useful as well.

Note: "ATH" means DOUT used for Ignition blocking.

7. Open raw data report in TT2.

For quick investigation (while being on the call, SupportMode should be enough):

mceclip1.png

Raw data report in Excel format takes longer to download but allows easier investigation (strongly recommended for deeper investigation):

mceclip0.png

Note: In case Excel file is used, special color-coded formatting is recommended for easier visual identification. In the examples, a color-coded file will be used.

7. Continue on the respective Knowledge article, depending on the connection method:

Note: in most cases, ATH_FAIL type of errors lead to a physical check-up, therefore it's recommended to check with the technician on the spot. In case the Technician is near the car, you shall try troubleshooting on the spot.

Did this answer your question?