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
0) Button 1 is pushed
a) Button 1 ‘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.
b) Button 1 ‘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.
c) Button 2 ‘short press minimum time’; a short press event is generated and if configured a
message is broadcast with button state 0b00001010 and reason code 0b00010010.
d) Button 1+2 ‘short press repeat time’; a short press repeat event is generated and if
configured a message is generated with button state 0b00001010 and reason code
0b00010011.
e) Button 2 ‘released’; a button release event is generated and if configured a message is
generated with button state 0b00000010 and reason code 0b00110010
f) Button 1 ‘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.
g) Button 1 ‘long press time’; a long press event is generated and if configured a message is
generated with button state 0b00000011 and reason code 0b00100001.
h) Button 1 ‘long press repeat time’; a long press repeat event is generated and if configured a
message is generated with button state 0b00000011 and reason code 0b00100001.
i) Button 1 ‘released’; a button release event is generated and if configured a message is
generated with button state 0b00000000 and reason code 0b00110000.
LMU-FOB comms
Advertisement packet contents
The advertisement consists of at least 2 parts from GAP specification, Manufacturer Specific Data
called ‘calamp fob data’; and Tx Power Level called txpw.
Calamp Fob data contents
note: now using the MAC address as the fob ID.
size (bytes) Description default
L 1 length of this data 0x10
F 1 Manufacturer Specific Data as
defined in GAP
0xff
cal
2
Calamp manufacturer ID set by us
to distinguish our devices
0xca1a (big endian)
TBC
Button 1
Button 2
0 a b b b b c d e f g h h i
calamp fob data txpw
L F cal v cid p fv c crc s r b a