How to configure Modbus tcp/ip data in M580

[MrBong]

How to read data from modbus tcp/ip in M580. I tried ADDM & ADDMX and Read_var but not getting data.

Please guide further.

[YONGHO-KIM]

Are you trying to do Modbus TCP/IP communication with the M580 CPU or are you trying to communicate through BMENOC?

[MrBong]

@YONGHO-KIM I am trying to do Modbus TCP/IP communication with M580 CPU.

[YONGHO-KIM]

1.Change FFB Type
AS-IS : ADDMX
TO-BE : ADDM

2. Accoding to the information you set, SLAVE is as follows.
Please check if the information is correct.
1) IP : 192.168.0.120
2) Slave ID : 14
3) Holding register

[MrBong]

@YONGHO-KIM I have tried with ADDM also but no result. I have 16 device in loop.

[RoozeeR]

In addition to the previous:

1: Set the timeout value (GEST parameter 3rd word) to a value other then 0 (=infinite) example 20;

2: Do this for all GEST parameters of alle communication functions;

3: INIT and (re)start the CPU

4: Check GEST parameter 2nd word for any errors (see control expert help on READ_VAR)

[YONGHO-KIM]

Please refer to the attached files.

[Sophearak]

Hi,

For ADDM we will use IP for modbus TCP not IP of CPU ?

[YONGHO-KIM]

- Do not enter the CPU's IP.
- Enter the IP of the device you want to communicate with.

[Sophearak]

Dear ,

I am new for modbus TCP with M580 I have a few question as below:

1. For M580 CPU will work with ADDM or ADDMX?

2. How to create string for input ADDM or ADDMX for CPU 580?

3. In order to read data Modbus TCP we must to do both DTM and function block READ_VAR? 

Thanks.

[YONGHO-KIM]

1. Use ADDM.
2. Please refer to the attached file
ex) ADDM('{192.168.1.40}TCP.MBS')
3. Yes

[Bosswaffle]

3. Would be a no. You do not need to use a DTM and READ_VAR at the same time. Either will work by themselves, and it would probably work better to only use one at a time.

[Sophearak]

Dear 

I has follow the step and I do not received any data from power meter. Can you me to check ? because I still can not found the mistake for reading modbus TCP.

      

[YONGHO-KIM]

Please upload the PLC project file, and I will review it.

[Sophearak]

Dear ,

I will use NOC for reading modbus TCO of power meter brand lovato.

Thanks 

[YONGHO-KIM]

What is the password?

[Sophearak]

PW:Ats!@#123

[YONGHO-KIM]

After reviewing the attached file, please proceed with testing. Once the testing is completed, kindly share the results.

[Sophearak]

Dear ,

Thanks for your support now it work.

[Simplicio]

Hello! Can I poll modbus rtu over tcp (moxa nport) data in the M580? Nport is running in TCP server mode. I am interested in the format of the addm or addmx string.

[YONGHO-KIM]

If the nport is a Modbus tcp server, the m580 supports Modbus tcp clients, allowing communication.

Please refer to the attached file for addm and addmx information.

[Simplicio]

If I use plcsim, what channel number should I specify in addm?

 

 

[YONGHO-KIM]

Please try as below.

[Adib]

Hi I would like to ask for the power meter how do you decide the slave ID as 1? doesnt modbus tcp does not require slave id

[YONGHO-KIM]

The ID setting of Slave is also required in modbus tcp.
Below is an example of when the slave id is number 2 in modbus tcp.

If the M580 is the master of Modbus tcp and you want to send a signal to slave device 2, set the yellow marking to 2 and test it.

[JezielRmz]

How do I do Modbus TCP/IP communication using just the M580 CPU

[YONGHO-KIM]

Please refer to the link below.

https://youtu.be/QhkIQCOyxjo?si=voJQf6g0BhovJqUF

[BBB1]

Dear Yongho Kim! 

I remain hopeful for your guidance, and thank you in advance for any assistance you can provide

We are facing  reading data issues with a Schneider LTMR motor controller (IP: 192.168.10.20) using the READ_VAR function block in EcoStruxure Control Expert on an M580 (BMEP58) PLC without a DTM or NOC module.

We are attempting to read register 455 (System Status 1) using:

• ADR: '0.0.3.192.168.10.20 TCP.MBS' althougt we should address with 0.0.0 cause I reading data from m580 itself with no additional modules....but its not works that way
• OBJ: 4
• NUM: 455 register from official manual (in attachment) I also tried: 900/800-according to internal LTMR mapping by SoMove and also tried without mapping
• NB: 13

Symptoms:

• The GEST[0] value is 5121 and constantly changing, indicating some response.
• GEST[1] =0 no errors
• However, DATA_READ array stays at all zeroes.
• GEST[3] (bit status) remains 0, suggesting no data is being updated.

We kindly request clarification on:

1. Is it valid to use READ_VAR without a DTM or NOC to access the LTMR via Modbus TCP?
2. Is NUM := 455 correct for accessing System Status 1, or is any offset/adjustment needed?
3. Are there any known limitations when directly communicating with LTMR over TCP from M580?

Relevant screenshots of the setup, Modbus mapping, and observed data are attached.

Thank you for your support.

[YONGHO-KIM]

1. Yes, it is possible.
The M580 CPU has a built-in Modbus TCP client capability, so you can communicate with external Modbus TCP slave devices (like the LTMR) without needing a separate NOC module. However, please ensure the following:

Use the correct ADDM format:
The address should be '0.0.0.192.168.10.20 TCP.MBS'.
The '0.0.3' format is used when a Other module is present.

Slave ID configuration:
LTMR typically uses slave ID 1. You can confirm this in SoMove if needed.

Port 502:
This is the default Modbus TCP port. Ensure it is open and not blocked by any firewall or network configuration.

2. NUM := 455 may not be correct.
LTMR Modbus addresses may be 1-based in documentation but 0-based in actual communication. Based on this:

If System Status 1 is listed as Modbus address 455 (Holding Register 455) in the manual,
you may need to set NUM := 454 in the READ_VAR block.

Some LTMR models use addresses in the 900 range for internal mapped status values.
You should verify the correct address using SoMove and adjust the NUM value accordingly.

3. Yes, here are some known limitations:
READ_VAR only supports INT arrays.
If the LTMR returns REAL (floating-point) values, they will be split across two INTs and require post-processing.

GEST[0] = 5121 typically means “response received but data is invalid.”
This could be due to incorrect addressing, wrong NUM value, or a mismatch in the expected response format.

GEST[3] = 0 indicates that the data is not being updated.
This may happen if the LTMR responds but the requested address does not contain valid or expected data.

[BBB1]

Thank you 

[wpschuster]

Just curious....but all documentation for read_var, data_exch outline using ADDMX with M580.  

Why do you suggest to use ADDM?

[FrancescoRibero]

I have the same question of @wpschuster . All documentation that i've found suggest me to use ADDMX for Modicon M580.
Moreover, i have a big question related the input string of ADDMX/ADDM: in my application i need to read data from a Device connected directly on CPU. In documentation i red that ADDMX is used exclusively for Ethernet drop. 
Last question: @BBB1 use 0.0.3, but theoretically must use 0.0.0? Which is the correct one?

please @YONGHO-KIM could you help me to clarify?
Thank you

[YONGHO-KIM]

Hi,

Here is the clarification regarding your questions based on Schneider Electric's official manual (Control Expert Communication Block Library😞

1. ADDM vs ADDMX for Modicon M580

• Answer: You can use both ADDM and ADDMX on the M580.

• Details: For standard communication EFs such as READ_VAR and WRITE_VAR, both ADDM and ADDMX are supported. However, if you are using M580-specific function blocks (e.g., READ_STS_MX, READ_PARAM_MX) or addressing modules in an EIO Drop, you must use ADDMX.

2. Direct Connection to CPU Embedded Ethernet Port

• Answer: Yes, ADDMX/ADDM is used for devices connected directly to the CPU as well.

• Details: Although ADDMX is widely used for EIO Drops, it is also required when communicating with Modbus TCP slaves connected directly to the CPU's embedded Ethernet port.

3. Address Syntax: 0.0.3 vs 0.0.0

• Answer: 0.0.3 is the correct notation for the M580 CPU embedded Ethernet port.

• Details: While 0.0.0 is used for M340 embedded ports, the embedded Ethernet port on the Modicon M580 CPU is assigned to Channel 3 (Rack 0, Slot 0, Channel 3).

• Therefore, the correct path syntax for communicating via the CPU embedded port is '0.0.3{IP_Address}' (e.g., '0.0.3{192.168.1.50}'). @BBB1 used the correct address format.

[sandeepacharya26]

@YONGHO-KIM  Kindly confirm, whether BMENOC0321 can act as both Modbus master and Modbus Slave simultaneously in a network? Can you please share a sample program both the configurations? Thanks.

[YONGHO-KIM]

1) The BMENOC module can operate simultaneously as both a Modbus Master and a Modbus Slave.

2) Example of BMENOC Operating as a Modbus Master.
- The BMENOC module is installed in Slot 2 of the CPU rack.
- The IP address of the BMENOC module is configured as 172.168.12.1.
- In the example below, the BMENOC operates as a Modbus Master and requests Holding Register data from a Modbus Slave device with IP address 172.168.12.10

3) Example of BMENOC Operating as a Modbus Slave.
- A Modbus Master device can request data using the BMENOC IP address and the standard TCP Port 502
- The Master device can read from or write to the memory areas of the Modicon PLC (such as %M, %MW, etc.).
- In this case, the BMENOC functions as a Modbus TCP Server (Slave), allowing external Modbus Masters to access PLC data.