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
• Peg ignition trigger causes Peg BT_KEYFOB_DISCOVER action (TBD) for
BT_KEYFOB_DISCOVER_TIME (configurable TBD) time.
• BT middleware starts discovery
• BT middleware populates discovered devices list including FOB ID and RSSI and TxPwr for all
calamp keyfobs that match the BT_KEYFOB_CID (configurable 0-FFFE standard CID, FFFF is
special case).
• BT middleware stops discovery after BT_KEYFOB_DISCOVER_TIME timeout
• BT middleware calculates path attenuation for all discovered keyfobs based on RSSI and
TxPwr.
o If a single KeyFob has (config TBD) smaller path attenuation [BT_KEYFOB_PATHATT]
than all others, that key fob is selected as the driver’s fob.
o If a single KeyFob has advertised a button push that key fob is selected as the
driver’s fob.
o Otherwise a set of candidate fobs is created from those fobs within
BT_KEYFOB_PATHATT of the least attenuated.
if configured with BT_KEYFOB_USE_FOB_RSSI (config TBD) BT middleware
connects in turn to each candidate fob and uses a config/control service to
measure the RSSI at the fob
• If a single KeyFob measures the RSSI with a
6dB/BT_KEYFOB_PATHATT less than all the rest this fob is selected
as the driver’s fob.
otherwise if configured with BT_KEYFOB_USE_FOB_BUTT (config TBD) BT
Middleware connects to each candidate fob and requests the buzzer to
sound for TBD on bench, start with 200) ms. BT middleware waits for
BT_KEYFOB_QUERY_DRIVER_TIMEOUT (config TBD) for a button press
response from the driver.
• if button defined in BT_KEYFOB_USE_FOB_BUTT is received from a
single fob, this fob is selected as the drivers fob
otherwise the driver’s fob is set to null.
• if driver’s fob is non null
o BT Middleware invokes PEG TRIG_BLE_FOB (already used) trigger with a button code
(TBD) as the modifier; having populated (config TBD) ACC_BLE_RSSI_HILO (already
used) accumulator with RSSI and ACC_BLE_FOB_BATT (config TBD) (already used)
with battery status.
o BT Middleware invokes DID_DriverId_Event()(already used) with FOB ID (not MAC
address) as the driver’s ID
o BT Middleware connects to Drivers fob and connects to the ‘button notification’
service; the ‘LED’ service; the ‘Buzzer’ service; and the ‘Configuration’ service.
o button notification service provides the button state and reason codes as per
advertisement packet.
o while connected PEG actions ACT_KEYFOB_BUZZ (config TBD) cause BT-middleware
to connect to the buzzer service(TBD) and sound the buzzer according to the
modifier (TBD)
Comment [n1]:
Optional for phase 2