This document has only the specific information about the device connection settings and its address syntax.
Refer to the User Guide for more information on the Device Module.
On this page:
Communication Driver Information | |
---|---|
Driver name | MelsecA |
Assembly Name | T.ProtocolDriver.MelsecA |
Assembly Version | 1.0 |
Available for Linux | False |
PLC types supported | Mitsubishi MelsecA Series PLCs and compatibles |
Manufacturer | Mitsubishi |
Interface | Serial and MultiSerial |
PC requirements | Ethernet port |
Default configuration:
DataBits: 8.
StopBits: 1 if parity is used, 2 if no parity.
Set the other fields according to your Serial or MultiSerial port configuration.
SlaveId: Set this field with the address of the slave device in the network. They can be addressed from 1 to 247 for serial nodes. The address 0 is used for the broadcast.
Station syntax: <SlaveId>
Ex: 1
Station syntax: <ComPort>;<SlaveId>
Where : <ComPort> = COM Port of the slave device in the network (default is com1).
Ex: com1;1
The syntax for the MelsecA communication points is: <Operand> <Address>
Where :
Operand | Read | Write | Data Type | Address size |
---|---|---|---|---|
D - Data register | Yes | Yes | Short | 2 bytes |
W - Link register | Yes | Yes | Short | 2 bytes |
R - File register | Yes | Yes | Short | 2 bytes |
D9 - Special Register | Yes | Yes | Short | 2 bytes |
TN – Timer Current value | Yes | Yes | Short | 2 bytes |
TS – Timer Contact | Yes | Yes | Bit | 1 bit |
TC – Timer Coil | Yes | Yes | Bit | 1 bit |
CN – Counter Current value | Yes | Yes | Short | 2 bytes |
CS – Counter Contact | Yes | Yes | Bit | 1 bit |
CC – Counter Coil | Yes | Yes | Bit | 1 bit |
X - Input relay | Yes | Yes | Bit | 1 bit |
Y - Output relay | Yes | Yes | Bit | 1 bit |
M - Internal relay | Yes | Yes | Bit | 1 bit |
L - Latch relay | Yes | Yes | Bit | 1 bit |
B - Link relay | Yes | Yes | Bit | 1 bit |
F - Annunciator | Yes | Yes | Bit | 1 bit |
M9 - Special Relay | Yes | Yes | Bit | 1 bit |
The status of the driver execution can be observed through the platform built-in diagnostic tools. Refer to the Using Diagnostic Tools topic in Devices Communication page.
MelsecA Revision History | |
---|---|
Version | Notes |
1.0 | Initial release on new documentation standards. |