| Название | Версия | Лицензия | Источник | Языки | Автор | Описание |
|---|---|---|---|---|---|---|
| Библиотека низкоуровневых сенсоров и чипов | 1.6 | GPLv2 | OscadaLibs.db (SQL, GZip) > DAQ.tmplb_LowDevLib | en, uk, ru | Roman Savochenko Arcadiy Kisel (2017) |
Library of templates to provide access to device's data of the low-level buses.
|
Библиотека устройств пользовательских протоколов создана для предоставления доступа к данным устройств низкоуровневых шин, с протоколом достаточно простым для реализации в модуле пользовательского протокола или непосредственно на внутреннем языке подобном на Java.
Названия элементов и их параметров доступны на языках: Английский, Украинский и mRussian. Их исходный код написан в языко(человеческий)-независимом режиме с вызовом функции перевода tr() и перевод этих сообщений также доступен Английским, Украинским и mRussian.
Для подключения библиотеки к проекту станции OpenSCADA Вы можете получить файл БД как:
- такой что поставляется с готовым и соответствующим пакетом дистрибутива Linux вроде "openscada-libdb-main", "openscada-LibDB.Main";
- наиболее актуальный и непосредственно полученный из репозитория subversion, преобразованный в файл БД SQLite путём:
wget http://oscada.org/svn/trunk/OpenSCADA/data/LibsDB/OscadaLibs.sql
sqlite3 -init OscadaLibs.sql OscadaLibs.db .exit
- загрузка прикреплённого тут.
Этот загруженный файл вы далее можете разместить в каталоге проекта станции и создать объект базы данных модуля БД "SQLite", зарегистрировав файл базы данных в конфигурации.
Contents
[hide]- 1 BT: RDTech UM24C, UM25C and UM34C (RDTech)
- 2 BT: ATORCH UC96, UD24 (UC96)
- 3 BT: ATORCH S1BP (S1BP)
- 4 1-Wire (1W)
- 5 I2C: PCF8591 (PCF8591)
- 6 I2C: PCF8574 (PCF8574)
- 7 I2C: ADS101x, ADS111x (ADS111x)
- 8 I2C: MCP4725 (MCP4725)
- 9 I2C: BMP180 (BMP180)
- 10 I2C: BME280 (BME280)
- 11 I2C: SHT3x (SHT3x)
- 12 I2C: DS1307,DS3231 (DS3231)
- 13 I2C: AT24C{32|64} (AT24CXX)
- 14 GPIO: DHT11,22 (DHT)
- 15 GPIO: MAX6675 (MAX6675)
- 16 GPIO|I2C: 1602A(HD44780) (1602A)
Для DAQ-шаблонов, в целом, вам нужно создать представительский объект устройства в модуле Логического Уровня и выбрать соответствующий шаблон из библиотеки шаблонов. Далее, для корректной конфигурации, придерживайтесь специфики шаблона в персональном описании. Концепцию доступа к данным через пользовательский протокол можно изобразить как на рисунке 1.
Как можно видеть с рисунка 1, взаимодействие с устройством происходит через некоторый транспорт на котором они физически базируются. Запрос к транспорту Вы можете отправить:
- Непосредственно с помощью функции системного API OpenSCADA объекта транспорта string messIO( string mess, real timeOut = 0 );, если протоколоспецифическая часть очень проста и данные Вам нужно лишь извлечь.
- Завёрнутый запрос данных req, функцией int messIO( XMLNodeObj req, string prt ); и для протокола prt, если протокольная часть достаточно сложная и уже представлена в OpenSCADA.
- Завёрнутый запрос данных специфический к пользователю с помощью функции int messIO( XMLNodeObj req, "UserProtocol" ); и реализации пользовательского протокола, если протокольная часть достаточно сложная и ещё отсутствует в OpenSCADA. Пользователь реализует тут саму протоколоспецифическую часть в модуле UserProtocol и часть специфическую к данным в шаблоне для модуля Логического Уровня или непосредственно в процедуре контролера на внутреннем языке программирования модуля JavaLikeCalc.
-
Этот последний метод развит к возможности формирования протокольной части кода непосредственно в том-же коде шаблона, как отдельная встроенная функция через вызовом функции запроса первого метода, если нет необходимости повторного использования, или даже если такая необходимость есть и тут имеет смысл создание комплексного шаблона, который сможет объединять роль и выходного протокола, через его подключение также к модулю пользовательского протокола. И оно будет полностью храниться в одной библиотеке шаблонов.
-
Прямая работа с выходным транспортом функции string messIO( string mess, real timeOut = 0 ); не предусматривает блокирования транспорта поза вызовом этой функции, а соответственно, для сложных протоколов с посылками ответа более чем в одном пакете, что предусматривает процесс "дожидания", не можно использовать общий транспорт, по которому возможна отправка пакетов различных протоколов или даже один, но в различных задачах (объектах контроллеров). Соответственно, если есть необходимость использования совместного транспорта, то размещайте параметры опроса по протоколу в одном объекте контроллера (задаче) или используйте модуль пользовательского протокола, к которому это замечание не имеет отношения, поскольку он осуществляет такое блокирование на время вызова процедуры обработки, как и остальные модульные протоколы OpenSCADA.
Для размещения реализации протокола тут вы должны выполнить и придерживаться приведенных требований:
- быть владельцем прав или автором кода и распространять его под любой свободной лицензией, предпочтение предоставляется GPL;
- приготовить и сохранить в отдельном файле БД SQLite, или как текстовый файл, на предмет: описания параметров (ВВ), кода процедуры написанного и отформатированного согласно какой нидудь системы;
- написать краткое описание и инструкцию подключения устройства по протоколу в способ похожий на другие тут;
- написать прямой запрос в тему форума "Разработка OpenSCADA" на предмет размещения протокола тут, включая доказательства его работоспособности от любого разработчика OpenSCADA или краткое демонстрационное видео.
1 BT: RDTech UM24C, UM25C and UM34C (RDTech) |
1.1 | GPLv2 | * | en,uk | Roman Savochenko |
RDTech UM24C/UM25C/UM34C BlueTooth interface template. Tested only on UM24C now.
The RDTech (RuiDeng) UM24C, UM25C and UM34C are low-cost USB pass-through power measurement devices, and support a decent number of collection features, as well as full control via Bluetooth. This template implements most exposed commands and data collection available by the device's Bluetooth interface.
This template in first time uses the new output transports connection function SYS.Transport.outAt() and the Bluetooth interface for the data acquisition.
- Total complexity: 0.3 HD[!]
- Thanks: for Ryan Finnie at the protocol initial processing in RDUMTOOL
Template IOs
Configuring and using
- 1. Connection the BlueTooth device:
bluetoothctl
#[bluetooth]# scan on
# Discovery started
# [NEW] Device 98:D3:31:F8:52:29 UM24C
# [CHG] Device 98:D3:31:F8:52:29 RSSI: -60
#[bluetooth]# scan off
#[bluetooth]# pair 98:D3:31:F8:52:29
# Attempting to pair with 98:D3:31:F8:52:29
# [CHG] Device 98:D3:31:F8:52:29 Connected: yes
# Request PIN code
# [UM241m[agent] Enter PIN code: 1234
# Pairing successful
#[bluetooth]# trust 98:D3:31:F8:52:29
# [CHG] Device 98:D3:31:F8:52:29 Trusted: yes
# Changing 98:D3:31:F8:52:29 trust succeeded
#[bluetooth]# exit
rfcomm bind 0 98:D3:31:F8:52:29 # 0 here for binding to /dev/rfcomm0
- 2. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 3. Create a logical parameter object and select this template for it, one for each the devices. Enable the parameter.
- 4. Into the tab "Template configuration" of the logical parameter object you need to set:
- Transport — to the address of the automatically created transport with its parameters after ":", according to the function SYS.Transport.outAt() address format, where the device address corresponds to the command rfcomm bind 0 in item 1.
- Device to bind — here you may set the Bluetooth address of the device as "98:D3:31:F8:52:29" to call the rfcomm bind {N} command when starting the template, where N is respectively taken from the address of the previous item.
- The rfcomm command is normally not available to be called by a non-privileged user, and if you want to call it by such a user, you must set a corresponding sign for it as chmod u+s /usr/bin/rfcomm from the super user.
- 5. RESULT: The logical parameter object will perform gather data of and trace to modify of the writable properties.
2 BT: ATORCH UC96, UD24 (UC96) |
1.2 | GPLv2 | * | en,uk | Roman Savochenko |
ATORCH UC96, UD24 BlueTooth interface template.
The ATORCH UC96, UD24 are low-cost USB pass-through power measurement device with many interfaces and supporting a decent number of collection features, as well as control via Bluetooth. This template implements only the clearing data command and data collection by the device's Bluetooth interface.
The device sends data packages not at a request and just after establishing the connection, that is broadcasting with one second period. The device may not to send the data packages at enable not in the first screen, so you need to switch the first screen for the data appearance. The data can be missed also after suspending the PC, so this template in the first time implements the data missing detection and reconnection.
- Total complexity: 0.3 HD[!]
Template IOs
Configuring and using
- 1. Connection the BlueTooth device: performed in the standard way of pairing and trusting without PIN and to UC96_SPP
- 2. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 3. Create a logical parameter object and select this template for it, one for each the devices. Enable the parameter.
- 4. Into the tab "Template configuration" of the logical parameter object you need to set:
- Transport — to the address of the automatically created transport with its parameters after ":", according to the function SYS.Transport.outAt() address format, where the device address corresponds to the command rfcomm bind 0.
- Device to bind — here you may set the Bluetooth address of the device as "58:F4:04:33:D5:FD" to call the rfcomm bind {N} command when starting the template, where N is respectively taken from the address of the previous item.
- The rfcomm command is normally not available to be called by a non-privileged user, and if you want to call it by such a user, you must set a corresponding sign for it as chmod u+s /usr/bin/rfcomm from the super user.
- No data detection time — here you may set the time of detection of the data missing.
- 5. RESULT: The logical parameter object will perform gather data of and trace to modify of the writable properties.
3 BT: ATORCH S1BP (S1BP) |
1.0 | GPLv2 | * | en,uk | Roman Savochenko |
ATORCH S1BP BlueTooth interface template.
The ATORCH S1BP is low-cost AC energy measurement device with supporting a decent number of collection features, as well as control via Bluetooth. This template implements the command of the data clearing and switching the power mode, also as collection the data by the device's Bluetooth interface.
The device sends data packages not at a request and just after establishing the connection, that is broadcasting with one second period.
- Total complexity: 0.1 HD[!]
Template IOs
Configuring and using
- 1. Connection the BlueTooth device: performed in the standard way of pairing and trusting without PIN and to S1BP_SPP
- 2. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 3. Create a logical parameter object and select this template for it, one for each the devices. Enable the parameter.
- 4. Into the tab "Template configuration" of the logical parameter object you need to set:
- Transport — to the address of the automatically created transport with its parameters after ":", according to the function SYS.Transport.outAt() address format, where the device address corresponds to the command rfcomm bind 0.
- Device to bind — here you may set the Bluetooth address of the device as "58:F4:04:33:D5:FD" to call the rfcomm bind {N} command when starting the template, where N is respectively taken from the address of the previous item.
- The rfcomm command is normally not available to be called by a non-privileged user, and if you want to call it by such a user, you must set a corresponding sign for it as chmod u+s /usr/bin/rfcomm from the super user.
- No data detection time — here you may set the time of detection of the data missing.
- 5. RESULT: The logical parameter object will perform gather data of and trace to modify of the writable properties.
4 1-Wire (1W) |
2.1 | GPLv2 | * | en,uk | Roman Savochenko |
One Wire One Wire sensors bus implementing by 1Wire adaptors DS9097, DS9097U (DS2480B) on the bus RS232 and by the chip DS2482-100 on the bus I2C. Supported direct and parasite powering for the temperature sensors.
Supported 1Wire devices: DS1820, DS1820/DS18S20/DS1920 (not tested), DS1822 (not tested), DS2413, DS2408, DS2450, DS2438.
Template IOs
Configuring and using
- 1. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 2. Create a logical parameter object and select the template for that, one for each the devices. Enable the parameter.
- 3. Into the tab "Template configuration" of the logical parameter object you need to set:
- Transport — to the address of the automatically created transport with its parameters after ":", according to the function SYS.Transport.outAt() address format, where the device address corresponds to the serial device with a DS9097 adaptor or the I2C device like to "/dev/i2c-1".
- Address of the I2C driver — in decimal number of address the I2C driver on the bus above and in range pointed in help to the field.
- Rescan period — periodicity of rescaning for new and removed devices search.
- Only add at scan — the sign of adding devices only at scan, that is preventing also their removing (mark of removed) at any wrong request on bad busses.
- Tries after which set value to EVAL — quantity of wrong tries before setting the attributes in EVAL.
- 4. RESULT: The logical parameter object will perform at first searching to 1Wire devices on the bus and creating included parameters to the each found one. Next the logical parameter object will perform gather data of the found devices and trace to modify of the writable device's properties.
5 I2C: PCF8591 (PCF8591) |
1.0 | GPLv2 | * | en | Roman Savochenko |
I2C 8-bit 4xA/D and D/A converter. Connects through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- vRef — reference voltage of the AIs and AO.
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the AI attributes and also will take the AO and write to the chip.
6 I2C: PCF8574 (PCF8574) |
1.0 | GPLv2 | * | en | Roman Savochenko |
I2C 8-bit 8DIO. Connects through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the DI attributes and also will take the DO and write to the chip.
7 I2C: ADS101x, ADS111x (ADS111x) |
1.0 | GPLv2 | * | en | Roman Savochenko |
I2C 12/16-bit 4xA/D converter. Connect through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- range — range of voltage of the AIs.
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the AI attributes.
8 I2C: MCP4725 (MCP4725) |
1.0 | GPLv2 | * | en | Roman Savochenko |
I2C 12-bit D/A converter. Connect through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- vRef — reference voltage of the AO.
- 6. RESULT: The logical parameter object will perform interaction and take the AO and write to the chip.
9 I2C: BMP180 (BMP180) |
1.0 | GPLv2 | * | en | Roman Savochenko |
I2C Pressure and Temperature sensor. Connecting through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- oss — oversampling setting of pressure measurement [0...3].
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the Pressure and Temperature attributes.
10 I2C: BME280 (BME280) |
1.0 | GPLv2 | * | en | Arcadiy Kisel, Roman Savochenko |
I2C Barometric Pressure, Temperature and Humidity sensor. Connect through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- oss — oversampling setting of pressure measurement [0...7].
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the Pressure, Temperature and Humidity attributes.
11 I2C: SHT3x (SHT3x) |
1.0 | GPLv2 | * | en | Roman Savochenko |
Digital Temperature and Humidity Sensor for the models: SHT30
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported;
- addr — the I2C slave device's address [0...119].
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the Temperature and Humidity attributes.
12 I2C: DS1307,DS3231 (DS3231) |
1.1 | GPLv2 | * | en | Roman Savochenko |
I2C RTC chips DS1307,DS3231 with Temperature sensor and calibration for DS3231. Connects through a Serial output transport into the I2C mode.
Template IOs
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 4. Create a logical parameter object and select the template for that, one for each I2C slave devices. Enable the parameter.
- 5. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to the address of the transport into step 1. Tracing for the address changing is supported.
- addr — the I2C slave device's address [0...119].
- 6. RESULT: The logical parameter object will perform interaction and placing of gathered data to the DateTime, Temperature and some one state attributes and also will take the DateTime, some one state attributes and write it to the chip.
13 I2C: AT24C{32|64} (AT24CXX) |
1.0 | GPLv2 | * | en | Roman Savochenko |
Provides operations with EEPROM memory based on I2C chips AT24C32 (4KB) and AT24C64 (8KB). Supported random reading and writing.
Output user protocol's XML request structure
<{cmd} addr="{ChipAddr}" off="{MemOffset}" size="{ReadSize}" err="1:Error">{ReadWriteSeq}</{cmd}>
- cmd — command, for now there allowed: "read", "write";
- addr — I2C device address [0...119];
- off — memory part offset;
- size — read memory block size.
- ReadWriteSeq — Read/Write bytes sequence.
- err — sets to result of the request.
Configuring and using
- 1. Create an output transport of the type "Serial" and set its Identifier like to "i2c", one for each the I2C bus.
- 2. Set proper address of the Serial device, only the I2C bus address like "/dev/i2c-{N}". Set the symbol's time into the timeouts field to the minimum value.
- 3. Place some requesting commands directly into presented or a new internal OpenSCADA procedure like to:
req = SYS.XMLNode("read"); req.setAttr("ProtIt","AT24CXX").setAttr("addr",87).setAttr("off",1000).setAttr("size",20).setText("My message");
req = SYS.XMLNode("write"); req.setAttr("ProtIt","AT24CXX").setAttr("addr",87).setAttr("off",1000).setText("Stored data");
- 4. RESULT: Into text() for "read" you will get the read data if no errors occur.
14 GPIO: DHT11,22 (DHT) |
1.0 | GPLv2 | * | en | Roman Savochenko |
Digital Temperature and Humidity Sensor for models: DHT11, DHT12, AM2302, AM2320, ... . The module designed for the sensors connect through GPIO, mostly it's Raspberry PI BCM2835 GPIO.
Conditions: Exclusively realtime planing in the priority 199 (FIFO-99).
Template IOs
Configuring and using
- 1. Create an output controller object and a parameter into the DAQ module "BCM 2835", by default it's "pi.pi".
- 2. Create and start a logical controller object or use any presented one with the needed scheduling properties (FIFO-199).
- 3. Create a logical parameter and select the template for that, one for each sensor. Enable the parameter.
- 4. Into the tab "Template configuration" of the logical parameter object you need to set:
- addr — to the address of the "BCM 2835" parameter like "DAQ.GPIO.io.pi"; tracing for the address changing is supported;
- pin — GPIO pin number where connected the data pin of the sensor;
- tries — tries of the sensor reading;
- dev — generic device specific selection.
- 5. RESULT: The logical parameter will perform interaction and placing of the gathered data to the Temperature and Humidity attributes.
15 GPIO: MAX6675 (MAX6675) |
0.1 | GPLv2 | * | en | Arcadiy Kisel |
Cold-Junction-Compensated K-Thermocouple-to-Digital Converter (0°C to +1024°C). The module designed for the sensors connect through softSPI by GPIO, mostly it's Raspberry PI BCM2835 GPIO.
Conditions: Exclusively realtime planing in the priority 199 (FIFO-99).
Template IOs
Configuring and using
- 1. Create an output controller object and a parameter into the DAQ module "BCM 2835", by default it's "pi.pi".
- 2. Create and start a logical controller object or use any presented one with the needed scheduling properties (FIFO-199).
- 3. Create a logical parameter and select the template for that, one for each sensor. Enable the parameter.
- 4. Into the tab "Template configuration" of the logical parameter object you need to set:
- addr — to the address of the "BCM 2835" parameter like "DAQ.GPIO.io.pi"; tracing for the address changing is supported;
- pin_cs — CS pin number where connected the chip selection pin of the sensor;
- pin_sclk — SCLK pin number where connected the serial clock pin of the sensor;
- pin_miso — MISO pin number where connected the master in slave out (data) pin of the sensor.
- 5. RESULT: The logical parameter will perform interaction and placing of the gathered data to the Temperature attributes.
16 GPIO|I2C: 1602A(HD44780) (1602A) |
1.0 | GPLv2 | * | en | Roman Savochenko |
LCD Module 1602A, STN, BLUB, 16 Character x 2 Line, 5 x 8 Dots, by the direct (Raspberry PI BCM2835 GPIO) or I2C (PCF8574) wiring.
Conditions: Default planing policy but realtime one preferred.
Template IOs
Configuring and using
- 1. Create an output controller and an object of parameter in DAQ module "BCM 2835", by default it's "pi.pi" or create an output transport of the type "Serial", set address like to "i2c", one for each the I2C bus.
- 2. Create and start a logical controller object or use any presented one with the needed scheduling properties.
- 3. Create a logical parameter object and select the template for that, one for each sensor. Enable the parameter.
- 4. Into the tab "Template configuration" of the logical parameter object you need to set:
- transport — to address of the "BCM 2835" parameter like to "DAQ.GPIO.io.pi" or to address of the transport into step 1; tracing for the address changing is supported;
- addr — the I2C slave device's address [0...119];
- RS, E, D4, D5, D6, D7 — numbers of the GPIO pins where connected the proper data ones of the sensor.
- 5. RESULT: The logical parameter object will perform interaction and setting lines' values to the display.