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:
- When using lvcanopenalldoors / lvcanclosealldoors, does the vehicle CAN network need to be awake?
- Can the FMC130 or LVCAN adapter wake up the vehicle CAN bus before sending the lock/unlock action?
- If the vehicle CAN controller is asleep, should we expect the LVCAN lock/unlock command to fail or have no effect?
- What is the recommended production setup to make lock/unlock reliable after the vehicle has been stopped for a long time?
- 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.