3 - Connection Types
DynaPro Go| Handheld PIN Pad Device with MSR/Contact/Contactless | Programmer’s Manual (COMMANDS)
Page 35 of 247 (
D998200136-31
)
3.3.2
How to Send Commands Using Network Connections
Data the host sends to the device via the network connection must follow the SLIP protocol as defined in
Part D, Section 3 of
Specification of the Bluetooth System, Host Controller Interface, Volume 4
,
which is available at https://www.bluetooth.org/Technical/Specifications/adopted.htm. Note the reference
to bluetooth.org is intentional, and the specification does indeed apply to the device’s network
connection.
The host software should begin and end commands with SLIP’s frame delimiter
C0
, and must take into
account SLIP escape sequences that deal with occurrences of C0 inside the SLIP data frame:
If outbound data contains the byte value
C0
, software should encode it into SLIP as
DB DC
; if
inbound SLIP data contains the byte sequence
DB DC
, software should decode it to
C0
.
If outbound data contains the byte value
DB
, software should encode it into SLIP as
DB DD
; if
inbound SLIP data contains the byte sequence
DB DD
, software should decode it to
DB
.
To communicate with a device using the network connection, the host should wrap all commands in the
following block:
Table 3-3 - Network Connection Command Wrapper
Bit
7
6
5
4
3
2
1
0
Byte 0
0xC0 = SLIP frame delimiter
Byte 1
0x00 = Get
0x01 = Set
Byte 2 ..
Byte n
. See SLIP specification for requirements
about re-encoding occurrences of frame delimiter C0.
Byte n+1
0xC0 = SLIP frame delimiter
The device wraps all responses in the following block:
Table 3-4 - Network Connection Response Wrapper
Bit
7
6
5
4
3
2
1
0
Byte 0
0xC0 = SLIP frame delimiter
Byte 1
0x02 = Response to a command
0x03 = Unsolicited transmission for an event.
Byte 2 ..
Byte n
Response as defined in section
. See SLIP specification for requirements
about decoding
DB xx
byte sequences.
Byte n+1
0xC0 = SLIP frame delimiter
