Contents 1. Introduction ............................4 2. Hardware Information ........................7 2.1. Appearance..........................7 2.2. Specifications ......................... 10 2.3. Wiring Connections ....................... 11 2.4. Dimensions ..........................12 2.5. Mounting the Hardware ......................13 3. Configuration ............................ 15 3.1. Assigning an IP address to MDC‐700 ..................16 3.2. Editing the config.csv file ....................... 18 3.3. Importing/exporting the config.csv file................. 23 4. HMI Web Interface ........................... 25 5. Troubleshooting ..........................29 6. FAQ..............................31 Q1: What are the maximum numbers of polling definition and local register?......
2. Hardware Information 2.1. Appearance Connectors: (For MDC ‐714/MDC714) COM3 COM4 COM5 LED Indicator Configuration Display Connectors: Power COM2 Reset Ethernet Port COM1 LED Indicator The LED is used as a heartbeat indicator and slows to approximately one flash per second. Ethernet Port The MDC‐700 is equipped with a RJ45 port for Ethernet LAN connection. When 100BASE‐TX is operating, the 10/100M LED is lit orange. When 10BASE‐T is operating or the machine is ...
Page 8
Power Connector Configuration Display MDC‐700 includes a 5‐digit 7‐Segment LED display to indicate configuration in a module as below: The IP address for the MDC‐700 11111. (192.168.255.1) 1. 192 2. 168 ...
2.2. Specifications MDC‐711 MDC‐714 MDC‐741 Ethernet Port x1, 10/100 Base‐TX Protocol Modbus/TCP Slave Max. Connection 8 COM Port RS‐232 x1, (TXD, RXD, RTS, CTS, GND) x4, (TXD, RXD, RTS, CTS, GND) RS‐485 x1, (Data+, Data‐) x4, (Data+, Data‐) x1, (Data+, Data‐) Baud Rate 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 (bps) Data Format N81, E81, O81 Protocol Modbus RTU Master Max. Node 32 nodes for each RS‐485 port Polling Definition 250 definitions for all RS‐232/485 ports Shared Memory 9600 registers for each of AI, AO, DI and DO Data System System 5‐Digit 7 Segment LED Yes, to display IP address Display System LED Indicator Yes, to display heartbeat Mechanical ...
2.5. Mounting the Hardware Wall/Panel mounting Step 1: Install the four mounting screws into the 4 keyhole mounting holes. Step 2: Fasten the screws securely. DIN Rail mounting Step 1: Align the screw holes of the DIN‐rail clip with the holes on the back side of the module, and then fasten the screws securely. 1 ...
Page 17
STEP 4: Confirm the connection status icon is open on the page. Denotes the connection between the computer and the MDC‐module is open. Denotes the connection between the computer and the MDC‐module is failed. STEP 4: Choose a valid IP address of the network for your MDC‐700 module Scroll down to ‘Ethernet Configuration’ section, input the IP/Subnet mask and Gateway addresses and click on the “Apply” button. Make sure that the IP address you pick is not currently in use by another device on the network. ...
Page 19
Modbus Connection The Modbus Connection section is used to configure the Modbus ID of the MDC‐700 and the TCP port number for Modbus TCP communication. # TCPPort ModbusID * 502 TCPPort: Defines the TCP/IP Port number, in the example set to 502. (Default value) ModbusID: Defines the Modbus ID of the MDC‐700, in the example set to 1. (Default value) Module Information The Module Information section is used to record auxiliary description for the MDC‐700. It will be displayed on the main page of the MDC‐700, and can be used to identify one MDC‐700 from the others. # ModuleInfo * this is my data concentrator ModuleInfo: Defines the auxiliary description for the MDC module. The string constant has a maximum length of 32 characters. ...
Page 20
COM Port Configuration The COM Port Configuration is used to configure the parameters for the RS‐485 Modbus communication connection between the MDC‐700 and the RTU slave devices. NOTE: Only one set of configuration settings is allowed for each COM port. # ComPortNo BaudRate DataBit Parity StopBit Timeout PollDelay OperatingMode * 1 115200 8 20 Master * 2 115200 8 20 Master * 3 115200 8 20 Master * 4 115200 8 20 Master * ...
Page 21
Polling Definition The Polling Definition is used to define Modbus commands to read data from the slave devices. Before attempting to configure the parameters for the Polling Definition, be sure to check the COM port number that the target device is connected to, the Modbus ID setting for the target device, and the function code, start address, and the quantity for reading data. # UseComPort SlaveModbusID FunctionCode RegStart Timeout Preset RegCount Addr EventProcess Value * 1 1 2 * 2 2 2 * 3 3 2 * 4 4 2 * 5 5 2 Each Polling Definition consists of 8 parameters listed as below: ...
Page 22
NOTE: NOTE: The maximum number of all the polling definitions is 250. The maximum number of all the polling definitions is 250. The MDC‐700 provides 9600 internal Modbus registers each table (DI/DO/AI/AO) to hold data The MDC‐700 provides 9600 internal Modbus registers each table (DI/DO/AI/AO) to hold data collected from the RTU slave devices. collected from the RTU slave devices. The Modbus ID for the MDC‐700 is defined in Modbus Connection section. The Modbus ID for the MDC‐700 is defined in Modbus Connection section. By setting different types for a polling definition to retain register space mapped for specific By setting different types for a polling definition to retain register space mapped for specific devices, or to release those space mapped but reserve the definition, the main program on the devices, or to release those space mapped but reserve the definition, the main program on the Modbus master device can be applied in different applications where users would like to change Modbus master device can be applied in different applications where users would like to change or stop some devices without modification or with minimum level of modification. or stop some devices without modification or with minimum level of modification. The TimeoutEventProcess and the PresetValue parameters are only available to firmware The TimeoutEventProcess and the PresetValue parameters are only available to firmware version 1.08 and later. If a config.csv file for firmware version 1.06 or prior is imported to a version 1.08 and later. If a config.csv file for firmware version 1.06 or prior is imported to a MDC‐700 with firmware version 1.08 or later, the TimeoutEventProcess parameter is auto set to MDC‐700 with firmware version 1.08 or later, the TimeoutEventProcess parameter is auto set to 2, and the PresetValue parameter is set to 0. 2, and the PresetValue parameter is set to 0. ...
3.3. Importing/exporting the config.csv file Go to the web interface at http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address set in your MDC module. Any standard browser such as Mozilla Firefox, Internet Explorer or Google Chrome can be used to interface the module. NOTE: If you haven’t changed the default IP address in the MDC‐700, refer to “3.1. Assigning an IP address to MDC‐700” to configure it. After the import process is finished, the MDC‐700 will reboot in 5 seconds. Importing a CSV file to MDC‐700 STEP 1: Scroll down to the Import/Export Config.csv section of the page, click the CHOOSE FILE button, and then select your config.csv file. STEP 2: Click on the Import button to import the config.csv file to the MDC‐700. ...
4. MDC‐700 Web Interface Go to the web interface at http://xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address in your MDC‐700. Any standard browser such as Mozilla Firefox, Internet Explorer or Google Chrome can be used to interface the MDC‐700. The MDC‐700 web page includes the following sections: 1. The connection status between the user device and the MDC‐700 2. The connection information for each polling definition 3. The communication configuration information on the MDC‐700 4. Ethernet configuration 5. Importing/exporting the config.csv file 6. OS version, firmware version and MAC address information Connection status between your device and the MDC‐700 Module Name Auxiliary Description Connection Status Denotes the connection is successfully established Denotes the connection is failed ...
Page 26
Modbus Connection In the Modbus Conncetion section (on the MDC‐700 with firmware version 1.08 and later), it provides the scan time information for each COM port. The Master device can refer to the scan time to extend or shorten the time interval for each requesting data command. Current Scan Time MAX. Scan Time Min. Scan Time Reset Record Expand the polling definitions by clicking on the [+COMn], information including the polling definition number, SlaveModbusID, Starting Address of Register and Count of Register on both slave client and MDC‐700, and the connection status are provided. Connection Status: Good Connection Failed ...
5. Troubleshooting In this chapter, we will explain how to troubleshoot the communication problems. Possible causes of TIMEOUT Situation #1: The slave device is not active or the transfer function of the slave site may fail. Solution: Check the slave device is powered up and the communication function is enabled. Situation #2: The COM port number to which the slave device is connected is not the same with the UseComPort setting in the polling definition. Solution: Connect the slave device to the COM port number that is defined in the polling definition, or fix the UseComPort parameter to the virtual COM port number that the slave device is connected to. Situation #3: The wiring for communication is wrong. Solution: Exchange the D+ and D‐ wiring of RS‐485 connection, or exchange the Rx and Tx wiring of RS‐232 connection, and check the GND pin on the slave device is properly connected to the MDC‐700. Situation #4: An incorrect Baud Rate or/and Data Format setting is being specified. Solution: Check and fix the difference of the Baud Rate and Data Format settings between the polling definition and the slave device. ComPortNo BaudRate DataBit Parity StopBit Timeout PollDelay Operating Mode 1 9600 8 100 Master 2 9600 8 3000 1000 ...
Page 30
Situation #5: An incorrect ID of the Modbus slave device is being specified. Solution: Check and fix the difference of ID number between the polling definition and the slave device. Situation #6: The Timeout or PollDelay setting is not long enough. Solution: Lengthen the Timeout or PollDelay setting until it is suitable for communication with the slave device. ComPortNo BaudRate DataBit Parity StopBit Timeout PollDelay Operating Mode 1 9600 8 100 Master 2 9600 8 3000 1000 Master 3 9600 8 3000 1000 Master 4 9600 8 100 Master 5 9600 8 ...
Q3: How are the local registers mapped to the polled data in a MDC‐700? A3: Only the function code 01/02/03/04 can be used in the polling definition section in config.csv file. 01: Read Coil Status (Read DO) 02: Read Input Status (Read DI) 03: Read Holding Registers (Read AO) 04: Read Input Registers (Read AI) Refer to the example below, # UseComPort SlaveModbusID FunctionCode RegStart Timeout Preset RegCount Addr EventProcess Value * 1 1 2 * 1 1 2 * 2 1 2 * 2 2 2 * 2 ...
Page 33
The local registers mapping is listed on the main page of the MDC‐700 module. Slave device ID followed by register addresses for each polling definition The mapped addresses on the MDC‐700 The MDC‐700 allows users to enable/disable a polling definition by changing the first field of the polling definition section in the config.csv file. There are three types that users can use: “*”: Asterisk symbol means that this is a valid polling definition. The MDC‐700 will assign local register for data defined in the definition and save the polled data to the mapping local register. “‐”: Minus sign means that this is a disabled polling definition. The MDC‐700 will assign local register for data defined in the definition but will not poll the data. “”: Empty means that this is a null polling definition. The MDC‐700 will neither assign local register for data defined in the definition nor poll data. # UseComPort SlaveModbusID FunctionCode RegStartAddr RegCount * 1 ...
Q4: How to write data to output channels on a Modbus RTU slave device? A4: Step 1: Edit the polling definition for the output channels with read function code in the config.csv file. (For example, use 01 to read DO channels, 03 to read AO channels) # UseComPort SlaveModbusID FunctionCode RegStart Timeout Preset RegCount Addr EventProcess Value * 1 1 2 * 2 2 2 * 3 3 2 * 4 4 2 * 5 5 2 Step 2: Import the config.csv file into the MDC‐700, wait the MDC‐700 reboot in 5 seconds, and ...
Q5: How to read the status of each connection? A5: The status for each connection is saved in the sequence of polling definition from local register address 39600. The maximum number of polling definition in the config.csv file is 250, so the available address for the connection status is from 39600 to 39849. A Modbus master use function code 04 to read the status, up to 126 register of status can be read in one command. For example, the status of the graph shown above is presented as the third column in the following table. Def. number Address Status Status display on web page Def.#001 39600 0 GOOD Def.#002 39601 0 GOOD Def.#003 39602 0xFFFF TIMEOUT Def.#004 39603 0x8201 ERROR: ILLEGAL FUNCTION Def.#005 39604 0 GOOD Def.#006 ...
Need help?
Do you have a question about the MDC-700 Series and is the answer not in the manual?
Questions and answers