Knowledge
homeappabout
English
English
  • Home
  • About Ardexa
    • Our Security Principles
    • What makes us different?
    • Collecting Data
    • Device Remote Control
    • Tunnel (VPN) Access
    • File Transfers
    • Machine Plugins
  • Getting Started
    • What is Ardexa?
    • Connectivity in 60 Seconds
    • The Ardexa Data Store
  • Configure the Edge Device
    • Edge and Cloud Connect
    • Edge Device Configuration
      • ArdexaLinux Operating System
      • Approved Hardware
        • Dell Industrial Computers
          • Dell PowerEdge Installation
        • Advantech Industrial Computers
          • Configuring Advantech Devices
            • UNO-2271G, UNO-2272G
            • UNO-2362G
          • Advantech ArdexaLinux Installation
          • Advantech Serial Driver
        • Siemens Industrial Computers
          • Siemens IPC 127E Installation
          • Siemens IOT2050 ArdexaLinux Installation
        • Raspberry Pi
          • Install the Raspbian Image
          • USB On-The-Go (OTG) support
          • Raspberry Pi 4 EEPROM update
          • Display hardware version of Raspberry Pi
        • Virtual machines
      • Internet Connection
        • Connecting
        • Complex Network Management
      • Networking
        • Network Configuration Using Ardexa Cloud
        • Config Static IP - Manually
        • Add static route
        • Add secondary IP
        • Access via SSH
        • Update password
        • Test Network Access
        • Reconnecting Offline Device
        • Cisco VPN Access
        • USB Tethering
      • Using a local Network Time server (NTP)
      • Serial Communications
        • Testing the serial ports
      • Antivirus
      • Time Zone
    • Connecting to Plant Equipment
      • TCP (Ethernet)
        • Standard Industrial Protocols
        • OPC Protocols
        • Database Protocols
        • PLC Protocols
        • Miscellaneous
      • Serial (RS-485, RS-422, RS-232)
        • Standard Industrial Protocols
        • Proprietary Protocols
      • Others (Bluetooth, etc.)
    • Ardexa Agent
      • Installation (ARM64 or X86/AMD64)
      • Installation Raspberry Pi
      • Install (opkg)
      • Install on Docker
      • Check it's working
      • Increase system limits
      • Data types and formats
        • Decimal
        • CSV file format
      • Scenarios
        • Run
        • How does the UNIX_SOCKET scenario work?
      • Dynamic Configuration
      • Manual Configuration
      • Replacing a Device with a New One
      • Replacing a Device with an Existing One
      • Uninstall
    • Ardexa Machine Plugins
      • Safety & Risk Notice
      • Modbus
        • Modbus Server
        • Modbus Python Plugin
        • Modbus Plugin
      • Programmable Logic Controllers (PLCs)
        • Access to OPC DA Data
        • Installing the OpenOPC utility
        • Mitsubishi PLC Plugin
        • Siemens S7 PLC Plugin
        • Omron PLC Plugin
        • README
      • OPC Plugins
        • OPCUA Plugin
      • Solar Inverter Plugins
        • Satcon Inverters
        • Sungrow Inverters
          • Sungrow SG Grid Scale Inverters
          • Sungrow SG1000MX Inverters
          • Sungrow SG String Inverters
        • Delta Inverters
        • Connecting to Huawei
        • Huawei Logger
        • Huawei Logger
        • ABB Inverters
          • Configuring ABB Inverters
          • ABB Aurora Inverters
          • ABB PowerOne Modbus Inverters
          • ABB Pro 33 Inverters
          • ABB PVS 800 Inverters
          • ABB Trio Inverters
        • SolarEdge Inverters
        • Sunspec Inverters
        • SMA Inverters
          • Connecting SMA Inverters
          • SMA Central Inverters
          • SMA Cluster Controllers
          • SMA "YASDI" Inverters
          • SMA Sunny Tripower (non Sunspec)
          • SMA Power Plant Controllers
          • SMA Central 1850-2750 Inverters
          • SMA Sunny Webbox
        • Kostal Inverters
          • Connecting via Kostal Proprietary Protocol
          • Kostal Proprietary Plugin
          • Kostal Modbus (non Sunspec) Plugin
        • Kaco Inverters
          • Configuring Kaco Inverters
          • Kaco Inverter Plugin
        • SolarMax Inverters
          • Configuring SolarMax Inverters
          • SolarMax Inverter Plugin
        • Refusol Inverters
        • JEMA IFX Inverters
        • Ginglong Solis Inverters
        • Growatt TL3 Inverters
        • HEC Freesun Inverters
        • Next Tracker Plugin
        • Ingecon 100TL Inverters
        • Tristart MPPT Charger
        • Zenergy PID Boxes
        • Eaton Inverters
        • SolarCheck Strings
        • Soltec Trackers
        • GE Inverters
        • TMEIC Solar Ware Ninja Inverters
        • Power Electronics Inverters
        • Ingeteam Inverters
        • Delta Logger
        • FTC Trackers
        • Trina Trackers
        • Solivia Inverters
        • Dunext Inverters
      • Data Logger Plugins
        • Connecting SolarLog
        • SolarLog Logger
        • MaxWeb Logger
        • Gantner Logger
        • MeteoControl Logger
        • Bluelog Logger
        • Kaco proLOG
        • Sinapsi Logger
        • Skylog Logger
        • SMA Sunny Webbox Logger
      • Electricity Meter Plugins
        • Janitza Meters
        • Cube Meters
        • ECS Meters
        • Gavazzi Meters
          • Gavazzi EM24 Meters
          • Gavazzi WM Meters
        • KBR Meters
        • Plus ES Meters
        • RPI Current Transformers
        • Schweitzer Meters
        • Schweitzer Protection Relays
        • Schneider Electric Meters
          • Schneider ION Meters
          • Schneider Sepam Meters
        • Fanox Relay
        • Elspec Meters
        • Landis Gyr Meter
      • Wind Turbines
        • Wind Park Networks
        • Vestas Wind Turbines
          • Vestas ODBC
          • Vestas OPCUA
        • Clavis XML Server
        • Gamesa Wind Turbines
          • Gamesa ODBC Wind Turbines Plugin
          • Gamesa Windnet OPCUA
          • Gamesa Wind Turbines via Config Files
        • Nordex Wind Turbines
          • Nordex OPCXML Wind Turbines Plugin
          • Nordex Plugin ODBC with Config Files
          • Nordex Plugin OPCXML with Config Files
        • Enercon Wind Turbines
          • Enercon Wind Turbines Plugin
          • Enercon Wind Turbines Plugin with Config Files
        • GE ODBC Wind Turbines
        • Senvion Wind Turbines
          • Senvion Wind Turbines Plugin
          • Senvion Plugin with Config Files
        • Siemens Wind Turbines
          • Siemens Wind Turbines
          • Siemens Wind Turbines with Config Files
      • Weather Stations
        • Kipp and Zonen
        • IMT Si-RS485 Sensors
        • Webdom
        • Lufft Weather Stations
        • Campbell Weather Stations
        • DustIQ Soiling Sensors
        • Geonica Weather Stations
        • Groundwork Zenith Meteorological Stations
        • Hukseflux Pyranometers
      • Solar Powered Computers
      • Energy Storage
        • BYD ESS C648
        • BYD ESS
        • NetMan 204
        • Narada Batteries
      • IEC
        • IEC 61850
        • IEC 60870
      • Management Plugins
        • RESI Real Time Clock Plugin
        • Logrotate Plugin
        • Interface Manager Plugin
          • Automatic Modem Connection
          • Manual Modem Connection
          • Troubleshooting Modem Usage
        • Black Box Plugin
        • Log Rotation and Deleting Old Logs
        • Antivirus
        • Backfill
      • Computer Vision
        • Photo Capture Plugin
      • Testing Plugins
        • Dynamic Test
        • JSON Test
        • Ping Test
        • Schema Test
        • Serial Test
        • Solar Demo Plugin
        • Vestas Demo Plugin
        • Service Load Test
        • Resource Usage
        • Edge Statistics
      • Control
        • Ardexa Control Plugin
    • Variable Naming Guide
    • Communications Hardware
      • USB to WIFI Converter
      • Teltonika RUT950 router
      • Huawei E8372 (3G) Modems
      • Modems
  • Ardexa Cloud
    • Ardexa Account
      • Multi-factor Authentication
      • User profile
      • Browsers
      • Navigation
    • Ardexa Remote
      • Install Ardexa Remote
      • Using the Tunnel
      • Using the VPN
      • Troubleshooting
    • Data Access
      • KPIs
      • Users and Permissions
      • Device Groups
      • Limit user access to a subset of devices
      • Limit Access to Searches
      • API Tokens
      • Device access to the API
      • Images
      • Power BI
    • Analysis
      • View Types
      • Charts
      • Formulae
      • Device Logs
    • Searches
      • Creating Searches
      • Sharing Searches
      • CSV Downloads
      • Scheduled Search
      • Search Admin
      • Search Visualisations
      • Search Statistics
      • Search Analysis
      • Audit Logs
      • Other Resources
    • Devices
      • Edge and Cloud Devices
      • Device Summary
      • Device Bulk Actions
      • General Info
      • Remote Shell
      • File Transfer
      • Machine Plugins
      • Manual Configuration
      • Live Feed
      • Network (Edge Devices)
      • Network (Cloud Devices)
      • Discovery
        • Modbus
      • Commands
      • Tunnel (Ardexa Remote)
        • Install ArdexaRemote command line interface (CLI)
      • NAT Gateway
    • Entities
      • What is an entity
      • Create new entity
      • View entities
      • Managing entities
      • Recommendations
    • Standard UI components
    • Dashboards
      • Creating and Editing
      • Card types
        • 📈Chart Card
        • Button Stack
        • Active Incidents
        • Camera Control
        • Command Template
        • Cylinder
        • Energy Summary
        • Energy Tally
        • Gauge
        • Heat Map
        • Indicator light
        • Indicator light table
        • Inverter performance
        • KPI Chart
        • KPI Value
        • Latest Values
        • Link Stack
        • Live Calculation
        • Map
        • Metadata
        • Photo
        • Radial Histogram
        • Remote Web
        • Satellite Image
        • Scatter Plot
        • Single Value
        • Switch Toggle
        • Dynamic Text
        • Static Text
        • Value Table
        • Pie Chart
      • Lookup Table Integration
      • Timeframe and Timezone
    • Alerts
      • Incident Logs
    • Administration
      • Security Services
      • Metadata
      • Workgroup Settings
      • Labelling
      • Moving a Device Across Workgroups
      • External Sources
      • Lookup Table
      • Access Control
    • Energy Solutions
      • Energy Reports
        • Configuring the Daily Energy process
        • Configuring Meter Data
        • Configuring Performance Ratio
          • Irradiation Extract
    • Control
      • Schedules
    • Photos
  • FAQ
    • Difference between "Datetime", "event_time" and "store_time"
    • How can I manually upgrade the agent?
    • What ports does the agent require?
    • Can the agent subscribe to data streams from other agents?
  • Troubleshooting
    • ardpkg error: TypeError: 'NoneType' object is not subscriptable
    • Offline device (Ardexa agent is offline)
      • Remote checks
      • On-site checks
    • Agent continually restarts
    • Workgroup Invitations
    • Slack Invitation
    • Advantech Computer will not connect to the Internet
    • Edge Computer is not fully serviceable
    • The agent won't connect
    • My agent is online, but there is no data in the cloud
    • Agent upgrade failed: Unknown error
    • Device Config Update every log interval
    • Other Agent related issue
    • Running the agent in Debug Mode
    • Agent Maintenance on SysV
    • Connecting a device securely to a network segment that does not have Internet access
    • EXPECT_ERROR: Decimal conversion failed
    • Docker Interface Conflict
    • Failed to fetch...IP Not Found
  • Ardexa API
    • API
      • API Quick Start Guide
      • Python examples
      • Automated API Token Renewal
      • General
        • Issue API token
        • Examine API Token
        • WebSockets
      • Consumer
      • Security
      • Devices
        • Websocket
      • Search
        • API Search Functions
        • Search scrolling
        • Timeframe
        • Consuming data via the API
      • Energy
Powered by GitBook
On this page
  • Purpose
  • Usage
  • Example Configuration
  • Network Configuration
  • Arguments
  • Arguments
  • Example of "bit" lookup
  • Example of "str" lookup file

Was this helpful?

  1. Configure the Edge Device
  2. Ardexa Machine Plugins
  3. Programmable Logic Controllers (PLCs)

Omron PLC Plugin

Purpose

Purpose of this plugin is to read from Omron PLCs, using the FINS protocol. It MUST run with Python 3.9 or above.

Usage

You run a log to send data to the cloud, or a discover to only display information. There must be a config file when running log or a discover. The config file defines which variables need to be collected, what names they appear on the the Ardexa cloud, units and scaling, what table(s) they variables will be sent to, and the source name(s). An example configuration is shown below.

Example Configuration

The memory location defines which memory relates to which variable. It can begin with the following letter combinations, to designate different types of memory and configuration, as follows:

    D16_    =   Read a 16 bit word, from DATA MEMORY
    DL16_   =   Read a 16 bit word, little endian, from DATA MEMORY
    D32_    =   Read a 32 bit word, from DATA MEMORY
    DL32_   =   Read a 32 bit word, little endian, from DATA MEMORY
    W16_    =   Read a 16 bit word, from WORK MEMORY
    WL16_   =   Read a 16 bit word, little endian, from WORK MEMORY
    W32_    =   Read a 32 bit word, from WORK MEMORY
    WL32_   =   Read a 32 bit word, little endian, from WORK MEMORY
    EM0_   =    Read a 16 bit word, from EM0 MEMORY

If the memory location DOES NOT start with one of the combinations above, it will read a 16 bit word from CIO_MEMORY. For example, the memory location 9000 will read a 16 bit WORD memory from CIO MEMORY, whereas D16_9000 will read a WORD (16 bit) from DATA MEMORY. Reading from CIO MEMORY is always as 16 bit words. In the case of an integers, they will always try to read the value as a signed integers. Example config file as follows. Always verify data accuracy by running a discover first, before committing the plugin to collect data.

    # Table,    Source Name,    Variable Name,      Memory Location,    Type,       Units,  Scale,      Invalidate,    Lookup Table
    hydro,      hec,            AC Voltage 1,       20015,              dec,        V,      1+10,       , 
    hydro,      hec,            Grid Freq,          D16_20016,          dec,        Hz,     0.01,       , 
    hydro,      hec,            Cos Phi,            DL16_20017,         dec,        ,       100,        , 
    hydro,      hec,            PT100 Temperature,  20018,              dec,        C,      1,          , 
    hydro,      hec,            Total Hours,        D32_20019,          dec,        h,      0.1,        , 
    hydro,      hec,            DC Current 1,       20030,              dec,        A,      1,          , 
    hydro,      hec,            HDG Setpoint Mode,  20031,              bitb,       ,       1,          ,             1
    hydro,      hec,            Run Manual,         W16_20033,          bitb_int,   ,       1,          ,             3
    hydro,      hec,            Key Switch,         20040,              str,        ,       1,          ,             mode.dict
    hydro,      hec,            Key Switch2,        20045,              str_rep,    ,       1,          ,             mode.dict
    hydro,      pid_box,        PV- Voltage,        W32_20050,          int,        V,      1,          , 
    hydro,      pid_box,        PV- Current,        20051,              int,        mA,     1,          ,
    hydro,      alarm,          Alarm 0 Keyword,    20061,              bit,        ,       1,          ,             container_alarm0.dict
    hydro,      alarm,          Alarm 1,            20063,              bool,       ,       1,          ,
    hydro,      alarm,          Alarm 4,            20064,              int_bool,   ,       1,          ,
    hydro,      hec,            Total Current,      EM0_20065,          dec,        h,      0.1,        >100000,

Network Configuration

The Omron FINS protocol uses 6 network node numbers to communication with a PLC.

  1. The source network specifies the address number of the source network (the computer running the driver). The Source Network Address is sometimes referred to as SNA in Omron FINS documentation. The valid range is 0 to 127. The default setting is 0.

  2. The destination network specifies the address number of the destination device and is sometimes referred to as DNA in Omron FINS documentation. The valid range is 0 to 127. The default setting is 0.

  3. The source node specifies the number of the source node (the computer running the driver). The valid range is 0 to 254. The default setting is 0. However, we have noticed that using a number of 104 makes the plugin work ok.

  4. The destination node specifies the node number of the destination device. The Destination Node is sometimes referred to as DA1 in Omron FINS documentation. The default setting is 0, but it should sometimes be set to the last octet of the PLC's IP address.

  5. The destination unit specifies the number of the destination device unit number, sometimes referred to as DA2. The valid range is 0 to 255. The default setting is 0.

  6. The source unit specifies the number of the destination device unit number, sometimes referred to as DA2. The valid range is 0 to 255. The default setting is 0.

The Arguments section below details the arguments covering these items. If you find that you can read data from the PLC, but the data doesn't make sense, it usually means one or more of these arguments have been set incorrectly.

Arguments

  • Anything that starts with # is a comment line, and will be ignored

  • The Memory Location is the Ormon memory location/address.

  • Scale will only be used for decimal and integer types. An error will be reported if you try and divide an integer, or multiply by anything other than a whole number. The scale can also be a value such as 0.75-9, where the -9 is a BIAS value (addition or subtraction). In which case it will FIRST subtract the 9, THEN multiply by 0.75. If using a bias value, then it can ONLY be used with a decimal type.

  • Invalidate. This column will only do the following task": If an entry starts with >, it will invalidate ALL entries in a configuration file, if the value for this entry is greater than the specified amount. For example; if the Invalidate column entry is >10000, then a value of 12,000 will ensure ALL readings in the configuration file are invalidated. Use this item with caution. Also, it will ONLY work on dec values. This invalidation feature is intended for those machines that have poor quality control, and sometimes transmit wildly wrong values.

  • In Lookup Table; Sometimes you want to convert an INT to a keyword, through a lookup table. Or you may want to get a register bit and convert it to a keyword. See examples below.

  • Allowable Type column values are as follows:

    • dec ... Converts the Omron memory location to a decimal. Can be scaled (including division).

    • int ... Converts the Omron memory location to an integer. Can only be scaled upwards (not divided). So a scale value that is not a whole number will be rejected. See also the explanation for scale above, since it can include a bias and scale factor.

    • bool ... Omron memory location is converted to an INT. This value is then check as follows: Anything other than 0 will output a True. Else, output will be False.

    • int_bool ... Omron memory location is converted to an INT. This value is then check as follows: Anything other than 0 will output a 1. Else, output will be 0.

    • bin ... Converts the Omron memory location to an integer, then to a binary representation.

    • bit ... Used with a lookup table (in the Lookup Table column) to define a bit being turned or off. See example contents of file below. Bits start at "1" (not "0"), and are defined in the Lookup Table column.

    • bitb ... If a bit in the Omron memory location is turned on/off, it will reflect a boolean ("True"/"False") output.

    • bitb_int ... If a bit in the Omron memory location is turned on/off, it will reflect a boolean ("1"/"0") output.

    • str ... Treated as an ASCII character. If it can't be converted, it will output an empty field

    • str_rep ... Same as str, but it will clear \0 values in the resultant string.

Arguments

  • ip_address This is the IP Address of the Omron PLC. Make sure that Port 9600 is open.

  • config_path. This is the config file location. There must be a config file.

  • --attempts Is the number of attempts to make to get data from the PLC. The default=2

  • The network parameters can be set using the following arguments. They all default to 0.

--dest_net  = Destination Network
--srce_net  = Source Network
--dest_unit = Destination Unit
--srce_unit = Source Unit
--srce_node = Source Node
--dest_node = Destination Node

Example of "bit" lookup

Bit starts at 1. Include a 0 value to display something (or blank) if no bits are turned on

0 : 
1 : electric leakage sensor#1
2 : AC surge protection device
3 : key-operated switch
4 : scram button
5 : switcher signal from UC PCB Control Board
6 : electric leakage sensor#2
7 : electric leakage sensor#4
8 : electric leakage sensor#3
9 : signal 8 abnormal 
10 : energy-saving contractor KM1 return signal
11 : electric bad leakage sensor#2
12 : electric bad leakage sensor#1
13 : electric bad leakage sensor#4
14 : electric bad leakage sensor#2
15 : signal 14 abnormal
16 : signal 14 abnormal

Example of "str" lookup file

Numbers can be anything, since they are read from a single Omron memory location

-1 : 
51 : Closed
267 : Inverter
276 : Instantaneous value
295 : MPP
303 : Off
308 : On
309 : Operation
311 : Open
336 : Contact the manufacturer
337 : Contact the installer
338 : Invalid
381 : Stop
455 : Warning
569 : Activated
1041 : Leading
PreviousSiemens S7 PLC PluginNextREADME

Last updated 2 years ago

Was this helpful?