CalAmp FOB10-BL Скачать руководство пользователя страница 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 

(“CalAmp”). By installing and/or using the software or documentation, you are consenting to the 

terms of this License. If you do not agree to the terms of this non-exclusive License Agreement, DO 

NOT INSTALL OR USE THE SOFTWARE, APIs OR DOCUMENTATION. For a full refund, return the 

unused media package and all accompanying materials within seven (7) days to CalAmp. Where 

there is no packaging or media, use of the software and/or documentation constitutes acceptance. 

 

D

EFINITIONS

: As used in this License Agreement, “Software” means CalAmp’s LM Direct™, LMU 

Manager™,  LapTop Locator™, LMU Application/Programmable Event Generator™, CDMA LMU 

Provisioning Tool, GPRS LMU Provisioning Tool, iDEN™ Provisioning Tool, LMU Status, Clone Config, 

Hex Dump, LM Exchange™ Traffic Monitor, Freewave Base Station Config, Remote Serial Port, App 

Watcher Service and/or other software products licensed by CalAmp for use in computer 

applications development or integration including the computer programs, libraries and related 

materials either contained on the media provided to you by or from CalAmp, or which you have 

received or downloaded electronically. “Application” means a compiled or executable software 

program created by Developer that uses some or all of the functionality of the Software. “Software 

Copies” means the actual copies of all or any portion of the Software including backups, updates, 

merged or partial copies permitted hereunder or subsequently licensed to you. “Documentation” 

means the non-Software information contained on the media provided with this package or 

downloaded and which is used with and describes the operation and use of the Software. 

“Documentation Copies” means the actual copies of all or any portion of the Documentation 

including backups, updates, merged or partial copies permitted hereunder or subsequently provided 

to you. “Related Materials” means all other materials and whatever is provided by or from CalAmp, 

and the non-Software and non-Documentation contained on the media supplied, downloaded, or 

otherwise supplied by or from CalAmp for use with the Software and Documentation. “Server” 

means a single, networked computer that is accessible to other client machines on the network. 

“User” means (i) a single person using an Application for his/her internal, use or (ii) a single terminal 

or a single workstation of a computer used only by a person (and not accessed otherwise) for 

accessing an Application. “Use License” means limited rights granted by CalAmp for deployment of a 

single Application to a User. “Developer” means a single programmer developing an Application. 

“Developer License” means the grant of certain limited rights to use and maintain the Software, 

Software Copies, Documentation, Documentation Copies and Related Materials in development of 

Applications. 

 

B

ACKGROUND

: A Developer License is required for each Developer who uses the Software in building 

Application(s). A Use License is required and must be purchased by Customer for each User to which 

Customer provides access to an Application (unless a Server or Site license for unlimited or a 

specified number of users has been purchased). Each Use License is specific to one client-side 

Application only and may not be used for any other client-side Application. Each Server license is 

limited to Server-based Applications deployed on that Server for which the license has been 

purchased as specified in a CalAmp License Certificate. The Software is licensed on a per Developer, 

and on a per User, per Application basis. In order to preserve and protect its rights under applicable 

law, CalAmp is not selling you ownership rights to Software or Documentation (owned by or licensed 

Содержание FOB10-BL

Страница 1: ...BLE KEYFOB Hardware and Installation Guide Version 1 0 0 SEPTEMBER 1 2015...

Страница 2: ...ith and describes the operation and use of the Software Documentation Copies means the actual copies of all or any portion of the Documentation including backups updates merged or partial copies permi...

Страница 3: ...lAmp Customer agrees to include the notice Copyright 1999 20015 CalAmp DataCom Inc All Rights Reserved in Applications developed with the Software Customer agrees to include the following CalAmp Copyr...

Страница 4: ...are maintained and possession of the copy is retained in a secure location 2 Allow access to the Application for unlicensed users 3 Rent lease sublicense or lend the Application or its rights under t...

Страница 5: ...M OR OCCASIONED BY YOUR USE OF THE SOFTWARE DOCUMENTATION OR RELATED MATERIALS EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES IN THE EVENT THE FOREGOING IS FOUND BY A COURT OF COMPETENT JURISDICTI...

Страница 6: ...County for resolution of any dispute related to this Agreement U S GOVERNMENT PROTECTED RIGHTS The Software Documentation and Related Materials are provided with RESTRICTED RIGHTS Use duplication or d...

Страница 7: ...munications However there is no guarantee that interference will not occur in a particular installation If this equipment does cause harmful interference to radio or television reception which can be...

Страница 8: ......

Страница 9: ...Fob data contents 13 Version letter encoding 14 txpw contents 14 Scan response packet contents 15 Overview of Bluetooth Automatic Driver ID process 15 State Machine for driver ID discovery 15 State M...

Страница 10: ...te diagram below will only work if the KeyFob is connected to BTDB button state coded as 2 bits Not pressed 00 Pre short press 01 Short Press 10 Long Press 11 The three buttons are bit coded into a si...

Страница 11: ...sage on long press repeat timeout 00x1xxxx generate message on long press release 001xxxxx Keyfob configuration Stored on individual Keyfobs units bit size bytes default Short Press minimum 100ms 1 2...

Страница 12: ...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 pres...

Страница 13: ...onfigured 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...

Страница 14: ...above that will include CID button config etc Actual crc polynomial TBD This is to be used to determine if the configuration is as expected N A s 1 button state see above 0x00 no buttons pressed r 1...

Страница 15: ...n range of several LMUs the LMU will only look for FOBs when the PEG script executes PEG action State Machine for Finding Fobs using Beeps and Buttons Description LMU is asleep saving power Key Fob s...

Страница 16: ...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...

Страница 17: ...n agent TBD o If required LMU will download new config or firmware for fob the BT middleware will contact the config service to update the config as necessary the BT middleware will contact the OTA se...

Страница 18: ...Sequence diagram of discovery of driver id when only one fob in range...

Страница 19: ...Sequence Diagram of discovery of driver ID using buzzer and button...

Страница 20: ...Sequence diagram of connecting to a single fob to sound buzzer during driver id discovery...

Страница 21: ...ew custom primary service button r 2 1st byte is the button state 2nd byte is the reason code identical to the advertisement packet Config control New custom primary service Config r w 16 read write f...

Страница 22: ...have a greater RSSI than all other discovered keyfobs exceeding by at least this configured amount BT_KEYFOB_MODE 8 9 USE_FOB_RSSI 10 USE_FOB_BUTT BT_KEYFOB_QUERY_DRIVER_TIMEOUT 8 1s bit wait for this...

Страница 23: ...D discovery process option 3 Both of the above Over the Air Update Note that it is possible that a different fob could be connected after an OTA upgrade and so the next ID report for the upgraded fob...

Страница 24: ...of Server Checks fob s version against any queued nupdates and determines if one is available Format of Fob OTA ID report This is the LM Direct ID report for the Bluetooth fob that is sent from the LM...

Страница 25: ...0 0 which 1 1 Note that the order within JSON arrays is fixed but the order in JSON objects is not fixed and so for example the ids member is not necessarily the first member and within the extensions...

Страница 26: ......

Страница 27: ...des different advertisement timing detection of button states and reason coding Keyfob configuration storage done or only ATE Keyfob Config service Keyfob measure rssi service characteristic This is m...

Страница 28: ...selection of keyfob by measuring rssi on the key fob Includes state machine to connect to each candidate keyfob and request RSSI measurement LMU selection of keyfob by beep and button on the key fob...

Отзывы: