FMC130 + LVCAN lock/unlock issue after vehicle stays stopped for a long time

Hello Teltonika Support,

We are using an FMC130 with an LVCAN/CAN adapter for vehicle lock/unlock in a connected car rental project.

In general, everything works correctly:

  • The FMC130 connects to our platform.
  • We receive AVL data.
  • We can send commands/actions to the device.
  • LVCAN lock/unlock commands work when the vehicle is recently active or awake.

The issue appears when the vehicle stays stopped/inactive for a long time.

After a long inactive period, the FMC130 can still be connected, but the LVCAN lock/unlock action may not work. We suspect that the vehicle ECU/BCM or CAN controller goes to sleep, so the vehicle CAN network may not be ready to receive the lock/unlock command.

We would like to confirm the expected behavior:

  1. When using lvcanopenalldoors / lvcanclosealldoors, does the vehicle CAN network need to be awake?
  2. Can the FMC130 or LVCAN adapter wake up the vehicle CAN bus before sending the lock/unlock action?
  3. If the vehicle CAN controller is asleep, should we expect the LVCAN lock/unlock command to fail or have no effect?
  4. What is the recommended production setup to make lock/unlock reliable after the vehicle has been stopped for a long time?
  5. Is using DOUT relay as a fallback recommended when LVCAN cannot control the vehicle because the CAN network is asleep?

Our goal is to understand the correct installation and configuration approach for reliable lock/unlock in production.

Thank you.

Good Day,

Thank you for providing the detailed information.

The CAN Adapter not executing the lock/unlock commands may be related to either the CAN Adapter entering sleep mode or the vehicle ECU going into sleep mode.

The vehicle ECU usually enters sleep mode after the ignition is turned off. The CAN Adapter may also enter sleep mode if it is no longer receiving data on the CAN lines, or if the tracker itself enters sleep mode.

Kindly check the following:

  1. Ensure that device sleep mode is disabled.

  2. Set the ignition source to either DIN1 or Accelerometer.

  3. When the CAN commands are not being executed, please check whether any CAN data is still being received from the vehicle.

This will help us understand whether the issue is related to device sleep mode, CAN Adapter sleep behavior, or the vehicle ECU no longer being active on the CAN bus.

Thanks, and best regards,
Imran S.

@Ayoubmaj Have you found any solution for this?