Specifications
- Last UpdatedFeb 16, 2022
- 2 minute read
The hardware and software requirements to integrate peripheral devices with AVEVA Mobile Operator are as follows:
Hardware and Software Requirements
|
Bluetooth |
Supported by AVEVA Mobile Operator |
Remarks |
|
Version |
- Version 2.x (with EDR support) - Version 4.x (only if both the mobile and peripheral devices are Bluetooth Smart Ready) |
Not supported: For v4.x, source code will require changes, if the peripheral device is Bluetooth Smart and the mobile device is Bluetooth Smart Ready |
|
Profiles |
Serial Port Profile (SPP) |
Other Requirements
|
Feature |
Supported by AVEVA Mobile Operator |
Remarks |
|
Device discovery and pairing (Mandatory) |
General/Limited discoverable mode Ensure that the peripheral device has a static MAC address, and allows discovery and pairing |
Peripheral devices that support Bluetooth version 2.x allow discovery, pairing, and connection process |
|
Connection (Mandatory) |
Ensure that the peripheral device allows connection establishment from the mobile device |
Not supported: - Peripheral devices that send advertising packets to provide basic information for connection - Peripheral devices that only transmit data without allowing any connection process |
|
Session establishment (Optional) Establish a session and set properties for the session |
Supported |
|
|
Multiple models (Optional) Multiple models may exist for the same peripheral device to provide different set of data. For example, different models for different temperature ranges Identification of the model used in the round could be based on the advertisement/data packets sent by the peripheral device |
Supported only for peripheral device model identification based on data packet parsing |
Not supported: Peripheral device model identification based on advertising packets |
|
Data transfer mechanisms |
- Command/response - Broadcast |
Not supported: Peripheral device data transfer without connections using advertising packets |
|
Triggering mechanism (for peripheral devices that support command/response data transfer) Manually trigger the peripheral device to collect data or send commands from the mobile device, and to instruct the peripheral device to start collecting data |
Supported |
|
|
Endianness support for the commands |
Big endian |
|
|
Custom commands creation Customize commands sent to the peripheral device on runtime based on other parameters. For example, generate commands based on input/data settings |
Not supported |
|
|
Command/data encoding format |
- UTF8 - HEX (Source code will require changes to switch based on the declared type in the Peripheral Information XML) |
Not supported: - Octal - UTF-16 |
|
Support to transition the peripheral to park/sleep/hold /active modes by sending commands |
Not supported |
|
|
Data command encryption and fault detection techniques (like CRC) |
Not supported |
|
|
Data parsing Parse data received from the peripheral device Parsing data based on the offset and the length of the data in the packet. (Configurable) Delimiter based parsing Parsing and deriving multiple field values |
Supported |
|
|
Large data and complex types |
- Data up to 1024 bytes (retrieving data more than that needs to be analyzed for performance issues) - Primitive data types (string, number, and datetime) |
Not supported: Complex types |