Differences

This shows you the differences between two versions of the page.

--- terra4d:moxa [2019/03/29 13:48]
editor [TERRA 4D Configurator:]
+++ terra4d:moxa [2022/07/28 10:10] (current)
editor [Other hints]
@@ Line 1: / Line 1: @@
 ====== Moxa IO device through Modbus ======
-TERRA 4D comes with a Modbus plugin which allows integration of different types of Modbus devices.
+TERRA 4D comes with a Modbus plugin which allows integration of different types of Modbus devices. Here we focus on Moxa devices.
 ===== Supported features: =====
@@ Line 8: / Line 8: @@
 ===== Installation instructions: =====
+=== Webbrowser: ===
+  * Connect the Moxa device to Ethernet and open the browser
+  * Connect to address 192.168.127.254 which is normally the default IP address of the Moxa devices
+  * Main things to configure: Password, Security/Service Setting/Modbus!!!, Network/LAN, IO/Channel Mode (especially for DIOs)
+  * alternatively you can use IOxpress software
 === Moxa IOxpress software: ===
-  - Connect the Moxa device to Ethernet and install the Moxa IOxpress software (download from Moxa website)
+  * Connect the Moxa device to Ethernet and install the Moxa IOxpress software (download from Moxa website)
-  - Start the Moxa IOxpress and select Device/Search... to find your device
+  * Start the Moxa IOxpress and select Device/Search to find your device
-  - Main things to configure: Password, Security/Service Setting/Modbus, Network/LAN, IO/Channel Mode (especially for DIOs)
+  * Main things to configure: Password, Security/Service Setting/Modbus!!!, Network/LAN, IO/Channel Mode (especially for DIOs)
+  * on the Device Library page you find in the Deployment combobox the device actions, like up- and download of configuration files
+  * on the Configuration Library page you can change all settings and store it to a local file
 === TERRA 4D Configurator: ===
-  - create a subsystem plugin device Modbus with default settings
+  * create a subsystem plugin device Modbus with default settings
-= Input: =
+  * Input:
-  - create a IO device of type Modbus and select SubType "Input"
+    * create a IO device of type Modbus and select SubType "Input"
-  - IP port: 502, Server address: 0, Start address: 0, Input number: 0...N
+    * IP port: 502, Server address: 0, Start address: 0, Input number: 0...N
-= Output: =
+  * Output:
-  - create a IO device of type Modbus and select SubType "Output"
+    * create a IO device of type Modbus and select SubType "Output"
-  - IP port: 502, Server address: 0, Start address: 0, Output number: 0...N
+    * IP port: 502, Server address: 0, Start address: 0, Output number: 0...N
+  * Input register (e.g. for PWM counter):
+    * create a IO device of type Modbus and select SubType "Input register"
+    * IP port: 502, Server address: 0, Start address: 17, Input number: 0...N
+  * Analog Input:
+    * create a IO device of type Modbus and select SubType "Analog Input"
+    * IP port: 502, Server address: 0, Start address: 520, Input number: 0...N
+    * Configure low/high threshold depending on application to generate events when reading goes outside the expected range.
 ===== Other hints =====
+  * Within the device web page, in the main menu, within User-Defined Modbus Addressing, select Analog Inputs, Digital Input/Outputs (or similar):
+     * Make sure "Enable Modbus/TCP Slave Protocol" is enabled
+     * Within the table all the addresses of the available data points are listed. E.g. "AI Scaling Value (Float)" at "0520" as Input Register (read-only), Reference Address "30521"
+     * Within Terra4D use "Analog Input" with the address 520 (the 30000 is automatically added by selecting Analog Input).
+ * [[https://store.chipkin.com/products/tools/cas-modbus-scanner|CAS Modbus Scanner]] Tool to read/check Modbus device and see the values returned by the device.

User Tools

Site Tools

Differences

Page Tools