Mitsubishi MELSEC
Overview
Section titled “Overview”Talks MC protocol (SLMP) 3E binary over TCP to MELSEC iQ-R, Q, L and iQ-F controllers.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Host / Port | 192.168.3.39 / 5001 |
| Connection timeout | 5000 ms (default) |
| CSV file | C:\Projects\Line1\DeviceComments.csv (optional) |
CONNECT talks MC protocol (SLMP) 3E binary over TCP — set up a matching open port in the PLC’s Ethernet configuration. Addresses are a device plus a number with an optional value type: M0, X1F, Y10, D100, D200:float, D300:int32, W1A0, T5. Supported devices are X Y M S SM D W R SD T C; X, Y and W are numbered hexadecimal, as in GX Works3, the others decimal. Word devices are 16-bit integers by default; :int32 and :float use two consecutive words, low word first. T and C read the current value.
The direction comes from the signal type: a PLCInput is written to the PLC, a PLCOutput is read. SM and SD are never written. Reads are combined into as few batch requests as the protocol limits allow, and writes send only changed values — registers between two written signals are never touched.
An error code returned by the PLC — for example a device outside the configured range — appears as a signal issue while the connection stays up. With a CSV file set, Browse lists the devices of a GX Works3 device-comment export, with filters per device type.
Create or import signals
Section titled “Create or import signals”- Manually. Enter device and number with an optional value type:
M0,X1F,D100,D200:float,D300:int32,W1A0,T5. - Browse. Only from a file. With a CSV file set in the interface settings (a path on the CONNECT machine, not uploaded from the browser), Browse lists the devices of a GX Works3 device-comment export, with filters per device type. The controller itself is not browsed.
- File import. The GX Works3 device-comment CSV above is the file source. There is no separate import dialog.
- From the model. When the model already has its PLC signals, Addresses → Fill from controller… in the signal-mapping section of the CONNECT panel previews matches by exact name against what Browse finds in the CSV and then writes the addresses. Addresses → Import address table… takes a CSV or TSV with
name;address[;dataType[;topic]]rows. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. See Configuring interfaces.
How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.
See also
Section titled “See also”- Common concepts — text signals, direction, write access, tracking signals
- Configuring interfaces — adding signals, direction and write access
- All supported interfaces
- Troubleshooting — connection and signal problems