FAAC S p A BU Parking BLEPARK Users Manual

BLEPARK

USER MANUAL

V1.2.1

FCC & IC statements (1/2)

Caution

The user is cautioned that changes or modifications not expressly approved by the party responsible for compliance could void the user's
authority to operate the equipment.

This device complies with Part 15 of the FCC Rules and Industry Canada licence-exempt RSS standard(s). Operation is subject to the following
two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation.

Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée
aux deux conditions suivantes: (1) l’appareil ne doit pas produire de brouillage, et (2) l’utilisateur de l’appareil doit accepter tout brouillage
radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.

FCC & IC statements (2/2)

NOTE

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses
and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to
radio communications. 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 determined by turning the equipment off and
on, the user is encouraged to try to correct the interference by one or more of the following measures:

● Reorient or relocate the receiving antenna.

● Increase the separation between the equipment and receiver.

● Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

● Consult the dealer or an experienced radio/TV technician for help.

FCC and IC Radiation Exposure Statement:

This equipment complies with FCC and Canada radiation exposure limits set forth for an uncontrolled environment. This transmitter must not be
co-located or operating in conjunction with any other antenna or transmitter.

This equipment should be installed and operated with a minimum distance of 20cm between the radiator and your body.

Déclaration d’IC sur l’exposition aux radiations:

Cet équipement est conforme aux limites d’exposition aux radiations définies par le Canada pour des environnements non contrôlés. Cet
émetteur ne doit pas être installé au même endroit ni utilisé avec une autre antenne ou un autre émetteur.

Cet équipement doit être installé et utilisé à une distance minimum de 20 cm entre l’antenne et votre corps.

HARDWARE DESCRIPTION

● Main components:
○ Chip antenna
○ Jtag connector for programming
○ Power supply header
○ Serial port connector

● Power Supply
○ Voltage range: +12 .. +24V DC
○ Current consumption: 10mA MAX

SERIAL AND JTAG PINOUT

Chip characteristics

The board uses SoC nrf51422 from Nordic Semiconductor with integrated RF transceiver.

The following list gathers the main characteristics

● 2.4 GHz transceiver

● -90 dBm sensitivity in ANT mode

● -93 dBm sensitivity in Bluetooth® low energy mode

● 250 kbps, 1 Mbps, 2 Mbps supported data rates

● TX Power +4 dBm in 4 dB steps

● TX Power -30 dBm Whisper mode

● 13 mA peak RX, 10.5 mA peak TX (0 dBm)

● 9.7 mA peak RX, 8 mA peak TX (0 dBm) with DC/DC

● RSSI (1 dB resolution)

MECHANICAL DRAWINGS

BLEPARK

Application protocol specification

V3.1

Changelog

● Changelog for V2.1
○ First release: w.r.t to JunglePass board, the following have been added:

■ keepCtrlAlive() and keepHostAlive() messages to allow both the

● Changelog for V2.2
○ For APP developers only

■ Added routines to calculate MAC to PASSWORD transformation (for APP developers only)

■ Added map of GATT server characteristics
○ Added a NOTE on calibration
○ Added sequence diagram for keep alive messages
○ Added description of keepCtrlAlive() message missing in the previous release
○ Compressed number of ticket types to 2 (transient and subscriptions). Specific types must be addressed in ticket record length.

● Changelog for V3.1
○ Major version updated to allow retro compatibility with hosts attached to Junglepass controllers. The “JunglePass Board V2.X”

documents indeed overlap with V2.X of BLEPARK specifications in terms of major protocol number and produces problems in
fields.

■ NOTE: every BLEPARK boards shall be interfaced with a major protocol version >= 3. Major version number 2 is
reserved for existing installations of Junglepass board.

○ Integrated missing portion related to firmware update protocol subset in the documentation

GATT server characteristic list

Device calibration

NOTE ON CALIBRATION
Calibrator has to write to characteristic 0x0021 to set the transmitted power
value. This is done automatically by Operator APP.

Firmware version “blepark_app_V1_2” stills allows to set such value without
previous authentication. From blepark_app_V1_3 this is no more possible.

CRC generation for password
generation (only for APP team)

#define WIDTH (8 * sizeof(crc))
#define TOPBIT (1 << (WIDTH - 1))
#define POLYNOMIAL 0x04C11DB7

crc crcGen(uint8_t *message, int nBytes)
{

crc remainder = 0;

for (int byte = 0; byte < nBytes; ++byte)
{

remainder ^= (message[byte] << (WIDTH - 8));

for (uint8_t bit = 8; bit > 0; --bit)
{
if (remainder & TOPBIT)
{
remainder = (remainder << 1) ^ POLYNOMIAL;
}
else
{
remainder = (remainder << 1);
}
}

}
return (remainder);

}

Message format

The format of messages exchanged between a host (peripheral software) and
BLE controller is described in the following table.

Name Length (bytes) Description

Module ID 1 Module ID

Opcode 1 Operation Code

Payload Length 2

Payload N

Message format

It’s fields are explained below:

- Module ID: it represents a specific functionality to be addressed. For
example, firmware update or bluetooth communication.

- Opcode: identifies the specific message the host or the controller wishes to
send to peer.

- Payload length: length of payload

- Payload: message contents

Modules IDs

The following table shows the module ID used in BLEPARK. For
re-compatibility with JunglePass protocol, codes do not start from 1.

Modules IDs table

Short name Value

(hex)

HUB_MOD_BLE 0x12

HUB_MOD_NRF_SBL 0x16

HUB_MOD_NONE 0x1B

Opcodes

Host -> BLEPARK

Modules IDs table

Message name Opcode

sendConfig() 0xaa

reset() 0xac

endTransaction() 0xae

startTransit() 0xf0

endTransit() 0x0f

ticketEmission() 0x81

checkTicketResponse() //same format as ticketEmission() 0x82

keepHostAlive() 0x83

Opcodes

BLEPARK -> Host

Modules IDs table

Message name Opcode

requestConfig() 0xab

sessionEnd() 0xaf

requestTicket() 0x18

identifyCustomer() 0x19

conf() 0x42

verifyTicket() 0x99

checkTicket() //same format as verifyTicket() 0xa0

keepCtrlAlive() 0xa1

Opcodes

Common between BLEPARK and Host

Modules IDs table

Message name Opcode

ACK 0xff

NACK 0xf0

Messages

APDU sendConfig(bt,dt,dn,ic)

<8-bit module> HUB_MOD_BLE

<8-bit opcode> 0xaa

<16-bit len> 9+ic_len

<8-bit brand type> (bt) #0

<8-bit device type> (dt) #1

<32-bit device number> (dn), little endian #2-#5

<8-bit major protocol number> #6

<8-bit minor protocol number> #7

<8-bit installation code length> (ic_len) #8

<ic_len-byte installation code> (ic) #9-(#9+#ic_len-1)

NOTE1: the installation code can be either in hex or ascii format.

NOTE2: the maximum length for installation code is 12 bytes

Messages

APDU sendConfig(bt,dt,dn,ic)

dt value Device type

0x00 Entrance

0x01 Exit

0x04 APM

0x05 Exit+APM

bt value HUB Brand

0x00 FAAC

0x01 ZEAG

0x02 DATAPARK

0x03 CTR

0x04 HUB

Messages

APDU reset()

<8-bit module> HUB_MOD_BLE

<8-bit opcode> 0xac

<16-bit len> 0

<variable data> null

NOTE: this command logically resets JANUS BLE, i.e. it restarts waiting for start transit event for I/O
devices

Messages

APDU startTransit ()

<8-bit module> HUB_MOD_BLE

<8-bit opcode> 0xf0

<16-bit len> 0

<variable data> null

Messages

APDU endTransit(etr)

<8-bit module> HUB_MOD_BLE

<8-bit opcode> 0x0f

<16-bit len> 0x01

<variable data> 8-bit end transit result (etr)

NOTE: see “End Transit Result (etr) codes” section

Messages

End Transit Result (etr) codes

Message Value

Normal gate crossing 0xff

Gone backward 0xf0

Undertermined 0x18