Driver identification retention after engine shutdown

TELEMATICS
1

Hello community,
We tested an FMC130 with customized scenarios for a specific need: a buzzer connected to DOUT2 that sounds as soon as the ignition is turned on to force the driver to identify themselves via a 1-wire RFID reader.

image
image296×522 8.74 KB

This part works well.
Now, the driver can stop regularly throughout the day.
We need to program a 30-minute delay, for example, after turning off the engine. During this time, if the ignition is turned back on, the driver is still recognized and the buzzer doesn’t beep.
How could we manage this, please?

2

Hi,

Immobilizer feature will help, use it instead of custom scenario

image
image322×503 8.95 KB

Best Reagrds
Maynard C

4

Hello, and thank you for this feedback, Maynard.

The Immobilizer scenario is already used with DOUT1 on a relay for the immobilizer.
Could it work with this:

image
image305×232 4.68 KB

Thank you

5

Hi @Momo

This will only be deactivated via DIN not ibutton/1wireRFID

Best Regards
Maynard C

6

Hi Maynard,

Thank you for your feedback.
Do you have another solution for managing this feature outside of immobilization, please?

The Immobilizer scenario is already linked to another DOUT.
Thanks

7

Hi Momo,

If the features are unavailable in our existing base firmware, kindly contact your sales manager for a possible CDP.

Best Regards
Maynard C

8

Hi Maynard,

Thanks.
I will contact our sales manager