User's Manual
Table Of Contents
- License Agreement
- Limited Warranty
- Regulatory Information
- Driver ID Keyfob system design
- Key Fob button pushes
- Keyfob configuration
- Keyfob button timing diagrams for common scenarios.
- LMU-FOB comms
- Overview of Bluetooth Automatic Driver ID process
- State Machine for driver ID discovery
- State Machine for Finding Fobs using Beeps and Buttons
- Description
- Sequence diagram of discovery of driver id when only one fob in range
- Sequence Diagram of discovery of driver ID using buzzer and button
- Sequence diagram of connecting to a single fob to sound buzzer during driver id discovery
- Bluetooth LE services
- New PEG triggers
- New Trigger modifiers
- New PEG actions
- Params
- Driver’s FOB Out-of-Range
- Over the Air Update
- Format of Fob OTA ID report
- Work Breakdown
- Build Process
- Keyfob
- BTCS
- LMU
- LMU Over the air BT Client
- LMU Modified interaction with Puls new FOB_ID message
- LMU Modified ‘file’ Handling to allow LMU to ‘cache’ file.
- LMU Keyfob config ??? Puls or params?
- LMU passive scan for strongest keyfob
- LMU report of ‘seen keyfobs’
- LMU selection of keyfob by measuring rssi on the key fob
- LMU selection of keyfob by beep and button on the key fob
- LMU PEG trigger PEG TRIG_BLE_FOB
- LMU PEG action ACT_KEYFOB_BUZZ
- LMU PEG action ACT_KEYFOB_LED
- LMU PEG action ACT_ BT_KEYFOB_HUP
OTP (factory set configuration)
Description size (bytes) default
Cal Id 2 0xca1a (** to be confirmed by
BT SIG)
tx power calibration
4 (1 for each available power
level)
measured during ATE
Keyfob button timing diagrams for common scenarios.
Short press showing de-bouncing other buttons not pressed.
0) Button is pushed at time zero.
a) After de-bouncing button is determined as pressed but no message is generated.
b) After ‘short press minimum time’ a short press event is generated and if configured a
message is broadcast with button state 0b00000010 and reason code 0b00010001.
c) After ‘short press repeat time’ a short press repeat event is generated and if configured a
message is generated with button state 0b00000010 and reason code 0b00010001.
d) After Button is released and de-bounced a button release event is generated and if
configured a message is generated with button state 0b00000000 and reason code
0b00110001
0) Button 1 is pushed
a) Button 2 is pushed before ‘short press minimum time’ for button 1. Because button 2 is
pushed before ‘short press minimum time’ Buttons 1 and 2 are now considered as grouped
for the purposes of the reason code.
b) Short press minimum time elapses on both button 1 and 2 if configured a message is
broadcast with button state 0b00010010 and a reason code of 0b00010011
c) The short press repeat time passes for buttons 1 and 2; if configured a message is generated
with button state 0b00001010 and a reason code of 0b00010011.
d) button 2 is released if configured a message is generated with button state 0b00000010 and
reason code 0b00110010
e) Button 1 is released if configured a message is generated with button state 0b00000000 and
reason code 0b00110001
Button 1
0 a b c d
Button 1
Button 2
0 a b c c c c d e