Project major steps:

• build of several HW interfaces:

a. Analogic I/O Interface (between BLE device and FESTO) (3V - 10V)

b. Digital I/O interface (between BLE device and FESTO) (3V - 24V)

c. Serial to USB dongle for BLE device

• Real Time SW App for the BLE Nano device (central module) which will be used as serial dongle for devices that have no BLE 4.0 interface;

• Windows (or Linux) SW App to visualize and control remote the processes. It will be defined as an HMI or other similar console operator device;

• Android SW App to visualize and control remote the processes. It will be defined as an HMI or other similar console operator device;

Components - under construction

1. Peripheric Device (HW setup & SW Setup)

2. Central Device (HW Setup & SW Setup) (aici intra si modulul serial to usb converter)

3. BLE SYS CONTROL Android App Setup

4. BLE SYS CONTROL Python App Setup for Windows/Linux

5. BLE SYS CONTROL Matlab App

This project is diveded into several work packages in order to assure modularity. During development, the interaction of these work packages has to be taken into account. The level of interaction is not the same between all of them and they don't interact all at the same time.

WP1. Requirements Definition, Design, Implementation of Hardware Interfaces

a. Define the HW interface design specifications; (4h)

b. Define HW design's options (digital interface, analog interface, power supply, serial to USB converter & driver). (20h)

c. Describe the solution's options and present arguments in favor of the chosen one (cost-benefit); (6h)

d. Part List (cost and provider); (6h)

e. HW Solution's Implementation (10h)

f. Solution's Documentation (Drawings, Photos, Maintenance) (10h)

**Work space: HW intro

WP2. Requirements definition, architecture, design, SW implementation for peripheral device

a. Define SW application's specifications (control mode automatic / manual, identification mode , communication module) (6h)

b. Define software architecture (Diagram of classes, modules, UC, data flow, data structures, back bone app, application framework used services provided by MBED, useful services to deploy, etc.) (32 h)

c. Proposed architecture's documentation, modules' and internal interfaces' implementation; (32h)

d. Modules' implementation and features' description (70h)

e. Testing implemented functionalities (20h)

f. Implementation's documentation (20h)

**Work space: SW NRF51822 Intro

WP3. Requirements definition, architecture, design, SW implementation for central device, Windows PC

a. Define SW application's specifications (visual interface, features, options, etc.); (8h)

b. Define Windows application's software architecture (programming environment, structure modules, classes, flowdata, etc, serial communication) (32h)

c. Define BLE Nano - Dongle application's software architecture (structure modules, classes, flowdata, etc. Bluetooth communication) (32h)

d. Solution's proposed architecture documentation and implementation of internal interfaces and modules (Windows) (32h)

e. Possible proposed solutions' architecture documentation and implementation of internal interfaces and modules (Central BleNano) (32h)

f. Implementing code (Windows) (60h)

g. Implementation Code (Central Nano BLE) (50h)

h. Testing functionalities (20h)

i. Implementation code's documentation (Windows) (20h)

j. Implementation code's documentation (Central Nano BLE) (20h)

**Work space: SW NRF51822 Intro

WP4. Requirements definition, architecture, design, SW implementation for central device, Android

a. Define SW application's specifications (visual interface, features, options, etc.); (4h)

b. Define setup and SW development mode (10h) c. Define software architecture (32h)

d. Solution architecture's documentation and implementation of internal interfaces and modules (32h)

e. Implementation code and functionality (50h)

f. Testing funcitonalitati (20h)

g. Implementation code's documentation (20h)

WP5. System Integration, Testing, Setup configuration

a. Setup workspace for work-in-progress (10h)

b. Setup working procedures to update firmware, SW, etc. Links tool used; Versioning tool's (20h);

c. Management of configurations and versions (10h);

d. Testing applications integration, reconfiguration (20h)

e. Documentation: User's Manual, Setup Procedure, etc. (40h)

USE CASES:

UC1: The control and acquisition solution will be split between 2 distinct HW components:

1. Peripheral Device – this will be connected directly to the I/O connexion panel of the FESTO platform(e.g. Level Process, Flow Process or Pressure Process). Hardware interfaces should be defined for digital and analog I/O and also for power input of the peripheral device. The development board to be used BLE Nano.
2. Central Device – can be considered one of the following :
   1. Dongle USB-serial + BLE Nano Module which connects to a desktop PC; In this way the desktop PC will be enabled to support BLE connection, and therefore to control the peripheral device.
   2. Smart Device with BLE v4.0 at least (e.g. Smartphones, Tablets). A software application will be developed for Android OS.

The central device will connect to a peripheral device and allows an user to configure it and choose specific use scenarios.

PERIPHERICAL DEVICE:

UC2: Shall connect to a single device at the time (to a central device); When disconnected the system will be in an advertising state;

UC3: (automatic control)A feedback control generic solution (real time) shall be implemented. Shall support digital control laws like u[k] = f(u,y,r), with f- a nonlinear function, and the control variables values should be hold up to 25 samples each. 

The control law configuration, setting of the sampling period and of other parameters shall be done from the central device via Bluetooth connection. Also particular cases like PID or RST control shall be considered.

UC4: Manual control (the device will be controlled remotely by the central device). The value of the command is received from the Bluetoothcommunication and the measured variables should be send to the central device by using the same interface;

UC5: System Identification procedures shall be also allowed on the peripheral device: PRBS signal generator, measurement data acquisition;

UC6: A default state of device functioning shall be defined when disconnected (e.g. outputs disconnected, command on low, etc)

UC7: The BLE Nano device SW image update shall be done via Bluetooth (bootloader – FOTA).

UC8: A suitable security policy shall be defined to protect from unwanted access or software alteration.

UC9: PLC/NI AQ Card monitoring functionality.

CENTRAL MODULE:

UC10: It shall connect to one or multiple peripheral devices at the same time. The selection of the peripheral connection shall be performed by the means of the SW app.

UC11: Shall offer a rich user interface:

1. Visualizing the FESTO plant parameters ( I/O status, command and output values , etc)
2. Selection of remote or local control
3. Peripheral control solution configuration
4. System identification option selection and configuration
5. [optional] Automatic control solution implemented on the central device (tot test remote control)
6. [optional] Hierarchical supervision and control of all FESTO stands;