CalAmp FOB10-BL Скачать руководство пользователя страница 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 electronically, and continues until terminated. If you fail to comply with any 

provision of the License, termination is automatic, without notice from CalAmp and without the 

necessity for recourse to any judicial authority. Upon termination, you must destroy the Related 

Materials, the Software, Documentation and all Software and Documentation copies. CalAmp can 

also enforce its other legal and equitable rights. 

 

D

EVELOPER 

L

ICENSE 

O

NLY

—U

SES 

P

ERMITTED

: Software and Documentation may be used for the sole 

purpose of developing Applications and only by a licensed Developer. Software and Documentation 

may be installed onto a hard disk drive or a Server, access to which is restricted to Developers for 

which a Developer License has been purchased and may also be stored or installed on a storage 

device such as a network server, used only to install or access the Software or Documentation on 

your other computers over an internal network; however, you must have acquired a license for each 

separate computer on which the Software or Documentation is installed or accessed from the 

storage device. A Developer License may not be shared or used concurrently on different computers. 

One backup copy may be made for each legally obtained media copy or electronic copy you have 

received, provided that all CalAmp and third party licensor information — including copyright 

notices — are maintained and possession of the copy is retained in a secure location. In addition, 

you agree to use reasonable efforts to protect the Software and Documentation from unauthorized 

use, reproduction, distribution or publication. All rights not specifically granted in this License are 

reserved by CalAmp. 

 

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 Copyright and Government Restricted Use notice in all documentation and in any 

Application on-line help or readme file. 

 

“Portions of this computer program are owned by CalAmp DataCom Inc., Copyright © l999 – 2015, 

CalAmp DataCom Inc., All Rights Reserved. Use, duplication or disclosure by the Government is 

subject to restrictions as set forth in subparagraph ©(1)(ii) of the Rights in Technical Data and 

Computer Software clause at DFARS 252.227-7013 or subparagraphs ©(l) and (2) of the Commercial 

Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is CalAmp 

DataCom Inc., 1401 North Rice Ave. Oxnard, CA 93030. Rights are reserved under copyright laws of 

the United States with respect to unpublished portions of the Software.” 

 

D

EVELOPER

(

S

)

 

L

ICENSE

—U

SES 

N

OT 

P

ERMITTED

:

 

U

NLESS 

O

THERWISE 

A

GREED 

T

I

W

RITING WITH 

C

AL

A

MP

,

 

Y

OU 

M

AY 

N

OT

 (1) Make derivative works including but not limited to translations, adaptations, 

arrangements or any other alteration (each of which would become the property of CalAmp or its 

licensors, as applicable) or make copies of the Software or Documentation except as permitted 

above; (2) Make copies of the Related Materials; (3) Use any CalAmp product to translate the 

product of another licensor unless you have the legal right to do so; (4) Allow a greater number of 

Developers to access the Software at any one time than the total number of Developer licenses for 

which you have paid; (5) Rent, lease, sublicense or lend the Software, Software Copies, 

Documentation, Documentation Copies, Related Materials or your rights under this License or allow 

access to the Software for unlicensed users; (6) Alter, decompile (except to the limited extent that 

decompilation by the licensed Developer only is necessary as the only available way to achieve 

interoperability with other programs and, in that situation, any resulting information cannot be used 

in developing, producing or marketing any software substantially similar in expression to the 

Содержание 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...

Отзывы: