- DL manuals
- CalAmp
- Security System
- FOB10-BL
- Hardware And Installation Manual
CalAmp FOB10-BL Hardware And Installation Manual
Summary of FOB10-BL
Page 1
Ble keyfob™ hardware and installation guide version 1.0.0 september 1, 2015.
Page 2
License agreement for software, application programing interfaces (api s ) & documentation important: do not install or use the software or documentation until you have read and agreed to this license agreement. This is a legal agreement between you, the customer, and calamp datacom incorporated (“c...
Page 3
To calamp). Calamp specifically retains title to all calamp software, documentation and related materials and calamp licensors retain title to items owned by them. D uration : this license agreement is effective from the day you install or start using the software, or receive or download it electron...
Page 4
Software), disassemble or reverse engineer the software; (7) make any attempt to unlock or bypass any initialization system or encryption techniques utilized by the software or documentation; (8) alter, remove or obscure any proprietary legend, copyright or trademark notice contained in or on softwa...
Page 5
Limited warranty c overing the p hysical m edia and p rinted m aterials : calamp warrants to you, the original licensee, that the media on which the software is recorded are free from defects in materials and workmanship under normal use and service for a period of ninety (90) days from the date of ...
Page 6
Agree to assure that copies of this license agreement are distributed, read and agreed to by each developer using the software and/or documentation. G overning l aw : this agreement shall be governed by the laws of the state of california, united states, excluding its conflicts of law principles and...
Page 7
Regulatory information fcc rules compliance statement (part 15.19) the enclosed hardware device complies with the part 15 of the fcc rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference recei...
Page 9
Driver id keyfob system design table of contents driver id keyfob system design .......................................................................................................... 1 key fob button pushes ............................................................................................
Page 10
Build process ................................................................................................................................. 27 keyfob ........................................................................................................................................... 27 btc...
Page 11
Configuration for each button configuration units / bit size (bytes) default event generation mask (see below) 1 00111100 generate events on releasing button from short press & when long pressed & keep generating long press events until button is released. Event generation mask for each button coded...
Page 12
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...
Page 13
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 ...
Page 14
V 1 version of this message 0x01 cid 2 set by customer/provisioning to allow a single customer to differentiate their devices from the mass. 0x0000 p 1 app id;for the keyfob this is 0x01 0x01 fv 2 version of keyfob firmware running on the keyfob. 0xnnbb (big endian) nn coded as packed binary coded d...
Page 15
Advertisement (db) scan response packet contents may contain uuids of services, name and any other static data. Overview of bluetooth automatic driver id process state machine for driver id discovery to mitigate contention where a fob is in range of several lmus the lmu will only look for fobs when ...
Page 16
• 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 (configura...
Page 17
O while connected peg actions act_keyfob_led (config tbd) cause bt-middleware to connect to the led service (tbd) and sound the buzzer according to the modifier (tbd) o while connected bt-middleware connects to config service (config tbd) and ota management service (config tbd) and constructs a puls...
Page 18
Sequence diagram of discovery of driver id when only one fob in range.
Page 19
Sequence diagram of discovery of driver id using buzzer and button.
Page 20
Sequence diagram of connecting to a single fob to sound buzzer during driver id discovery.
Page 21
Bluetooth le services service name attribute name r/w size (bytes) notes led new custom primary service pattern r/w 3 characteristic that defines the blink pattern 1 st byte on time; 2 nd byte off time; 3 rd byte blink pattern least significant bit first is shifted to the led; bit 1 implies on; led ...
Page 22
New peg actions action modifier description act_bt_keyfob 0 – discover/connect 1 – hup start discovery for a period of time act_bt _listsend 0none send list of discovered keyfobs to server in an app message act_keyfob_output b7-b6: output dest 0 – led 1 – buzzer b5-b4: pattern 0 – slow 1hz 1 – fast ...
Page 23
Driver’s fob out-of-range ‘disconnect’ from btcs is used to signal to lmu that driver’s id is no longer valid. Option 1) new/existing peg trigger to allow peg to decide to rescan () and send a logoff message to server. Option 2) if ignition is still on, rescan automatically and follow driver id disc...
Page 24
Lmu->server: fob ota id report note right of server: checks fob's version against any queuedupdates and determines if one is available server->lmu: ota download available (app 107) note right of lmu: check if have file already in ota flash storage. Lmuserver: http download of a&b image (if requi...
Page 27
Work breakdown build process firmware version make sure that the build process automatically names the final binaries correctly and that there is exactly one place in the project that sets the version information. Keyfob keyfob over the air service we are currently working on this. Keyfob advertisem...
Page 28
Lmu modified ‘file’ handling to allow lmu to ‘cache’ file. Lmu keyfob config ??? Puls or params ? Lmu passive scan for strongest keyfob includes creating a list of ‘seen’ keyfobs; adding parameters bt_keyfob_cid, bt_keyfob_discover_time; adding peg action act_bt_keyfob_discover. Lmu report of ‘seen ...