Difference between revisions of "IonoPi"
| Line 24: | Line 24: | ||
!Values | !Values | ||
!Description | !Description | ||
| + | |||
| + | |- | ||
| + | |||
| + | |rowspan="2"|https | ||
| + | |rowspan="2"|false | ||
| + | |true | ||
| + | |use HTTPS to communicate with Iono Pi | ||
| + | |- | ||
| + | |false | ||
| + | |use HTTP to communicate with Iono Pi | ||
|- | |- | ||
| Line 35: | Line 45: | ||
|start generating events only after HSYCO is aligned with the current status of the system | |start generating events only after HSYCO is aligned with the current status of the system | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 12:38, 2 May 2017
Iono Pi is a versatile I/O module that combines several digital and analog input lines, power relay outputs and support for standard interfaces, typical of modern PLCs, with the powerful computing core of the Raspberry Pi.
This driver provides support for iono Pi pre-installed with the Sfera Framework and the Sfera Driver for Iono Pi.
Contents
HSYCO Configuration
Add a IONO Pi I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
- IP Address: the IP address assigned to iono;
High Availability
- Shutdown when inactive: defaults to true.
Options
| ID | Default | Values | Description |
|---|---|---|---|
| https | false | true | use HTTPS to communicate with Iono Pi |
| false | use HTTP to communicate with Iono Pi | ||
| startupevents | true | true | generate IO events also during the driver’s start-up phase |
| false | start generating events only after HSYCO is aligned with the current status of the system
|
Datapoints
For inputs 1 to 4, depending on the 'input1' ... 'input4' options, only the corresponding datapoint will be created, i.e. di<n> (if digital), av<n> (if voltage) or ai<n> (if curent).
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | HSYCO can't connect to the device | |
| do<n> | 0 | R | relay <n> (digital output) is off |
| W | switch off relay <n> | ||
| 1 | R | relay <n> (digital output) is on | |
| W | switch on relay <n> | ||
| di<n> | 0 | R | digital input <n> is low |
| 1 | R | digital input <n> is high | |
| av<n> | <val> | R | analog input <n> is reading a voltage equal to <val> (in Volts) |
| ai<n> | <val> | R | analog input <n> is reading a current equal to <val> (in mA) |
| ao1 | <val> | W | set the analog output to <val> Volts |
User Interface
To control a digital output (DO1 ... DO6), add a button or a buttonicon object to your project page and set its address field to the corresponding datapoint:
Release Notes
3.5.0
- initial release
iono is a registered trademark of Sfera Labs Srl
