9.379 Moxa-ioLogik-4000

This page describes the device driver and the device window for the Moxa ioLogik 4000 data acquisition unit. The device driver monitors and controls the digital inputs/outputs of various modules hosted by the ioLogik 4000 unit. The driver supports digital I/O modules and the M6200 temperature measurement module (see below for details about the latter one).

The Moxa-ioLogik-4000 device driver is part of the sat-nms framework for M&C of plain digital I/O functions. Monitoring alarm circuits or controlling waveguide switches are indicatives for applications of this framework.

The application configuration normally does not access the Moxa-ioLogik-4000 device driver directly. There are a couple of application level logical devices (e.g. Input , Output or WG-Switch ) which may use the Moxa-ioLogik-4000 device driver as a low level driver to access the physical I/O ports.

Port adressing

The ioLogik device must be configured to work in dynamic address mapping mode to work with the driver. In this mode, each module gets assigned the lowest possible Modbus address. As a result, the modules can be accessed as a continuous sequence of registers.

The driver supports up to 32 16-bit input registers and 32 16-bit output registers appearing as variables I0000 to I001F and Q0800 to Q081F. The variable names reflect the Modbus addresses of these registers in hexadecimal notation. Beside I0000 to I001F, the driver provides 31 variables called J0000 to J001E containing the input registers shifted by 8 bit. J0000 for example contains the high byte if I0000 as low byte and the low byte of I0001 as high byte.

The Moxa administration tool for the ioLogix 4000 (for the NA-4010 also the Web-GUI of the device) shows the addresses, the device has assigned to each module.

The ioLogix 4000 does not permit to read non-existing registers, hence the device driver needs to know, how many input and output registers the device has configured. Evaluate these numbers from the address map shown in the Moxa administration utility and set the driver configuration variables accordingly.

M-6200 Temperature modules

Beside all digital I/O modules the driver also supports The M-6200 temperature measurement module. However, the device window shows the temperature values in hexadecimal notation (tenths of centigrade), which is hard to read / interpret.

For a temperature display in °C the sat-nms software provides the Moxa-ioLogik-Temperature logical device, which translates this value into a readable floating point number. The device also recognizes the special reading '0x8000' which is shown by the module to signal a broken cable to the temperature sensor and generates a fault flag from this.

Configuration settings

If used with the sat-nms framework for M&C of plain digital I/O functions, the Moxa ioLogik device acts like an unprogrammed PLC device. It is intended, that the device driver processes switch settings and changes of input circuits as fast as possible. The following settings are necessary to achieve this:

• When defining the ioLogik device in the device setup window, there must not be defined any other devices beside this module for this interface.
• The ioLogik unit is controlled through Modbus/TCP. The device's IP address must be set as an interface name like with serial devices controlled through a network terminal adapter: "aaa.bbb.ccc.ddd:502" where 502 is the standard Modbus/TCP port number.
• The IDLE time for the interface must be set to 200 msecs for a fast response of the driver.

Device window pages

The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .

• --- Shows / commands I/O port states.
• --- The faults page.
• --- The device info page.
• --- The maintenance page. The configuration parameters described below are set at this page.

Configuration parameters

At the maintenance page of the device window there are a couple of configuration parameters which must be set to make the software talk to the device.

Variables defined by this device driver