Hi,

do you have any success with Bently Nevada?

I tried today establish Modbus TCP connection with my S7-1516 but without success. I have connected BN card 3500/92 to CPU port X2 via Scalance X208. Port X1 is use for Profinet ring. CPU IP is 192.168.1.2 and BN IP is 192.168.1.6. I can ping BN so card should be available.

Settings of BN are attached. Settings of SW and results are also attached.

Result what I get is still the same - error with status value 809B. I tried set Modbus Server and also Modbus Client but no change.

Please help if you know how to fix it.

Thank you.

RomanST

------------------------------------------------------------------------------------------
Split from S7-1513-1 PN communication with Bently Nevada 3500 via Modbus TCP.

Hello,

which local/remote port value?

Hello,

remote port was set to 0.

local port was set to 502, 503, 0, 1. But still same result.

Unfortunatelly I don't know which port should be set there.

Thank you.

Roman

Hello,

port value 0 isn't right way. Your Nevada acts like Server with standard defined MB TCP port value, probably 502 so check it in Nevada. Your PLC acts in this case as Client, so you need set correct IP address of Server and that Server's port to properly connect. I recommend for first study some <standards> in Modbus TCP problematic, then you can better understand that. You can also try simulate both devices on PC with some applications running and connected locally, this is also good study way for you to better understand.

Hello,

recommend here:

https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

Hi,

thank you for that link.

I will be by PLC tommorow so I will check new settings and let you know.

I will set S7 as MB_Client and set MB_Client DB as this:

InterfaceId = 72 - this is hardware identifier Profinet interface X2 on my PLC

ID = 1

ConnectionType =  11 - TCP/IP

ActiveEstablished = 1

RemoteAddress = 192.168.1.6 - IP address of Bently Nevada communication card 3500/92

RemotePort = 502 - Modbus protocol

LocalPort = 0 - Any port

ModbusMode = 103 - Read 1 to 125 holding registers on the remote address 0 to 65,535

modbusDataAddress = 45001 - set in Bently Nevada

modbusDataLen = 500 - set in Bently Nevada

Hello,

Modbus connection is working. MB_Client used for S7-1516, Bently Nevada is Modbus Server.

Interface ID = 72 - PLC CPU ethernet port hardware ID where Modbus is connected

ID = 1 - any unique number

ConnectionType = 11 - TCP/IP connection

ActiveEstablished = TRUE

RemoteAddress = 192.168.1.6 - IP of Modbus card 3500/92

RemotePort = 502 - Port dedicated for Modbus

Local port = 0

request = TRUE - permanet 1

modbusMode = 0 - any other settings doesnt work

modbusDataAddress = 45001 - Modbus start address

modbusDataLen = 95 - must be exactly same number as is set in BN

Hello,

yes, 502 port is that's what I've recommended to you before. Pls take a look to help about MB_CLIENT instruction, especially MB_MODE parameter. There is table which shows perfectly how configure Mode due your requests of data. You simply can't test any number, due your requirements about Register address value in Server you need set proper MODE, DATA_ADDR and DATA_LEN. Check that DATA_LEN parameter, there is clear info how much max (WORDs in this case) you can poll with one request from Server. Important is also check column Function and Data type where you can see how correctly set proper address in MB_CLIENT due address in Server. Look that addresses start from 0 to some value, so if your Nevada register is defined as 45001, you can't simply set this value in your MB_CLIENT parameter. Your value due this Nevada register you need count via this Function and Data type description values. So I see your problems here:

1. not correct request address

2. not correct LEN set, because there is restriction how much data you can request per one call.

I can give you little hint depended to your situation and that LEN parameter. If you need data from more registers as is described in help (as one request permitt), you need prepare more requests for more register range.

Hi,

my connection is working as I wrote before.

I have only one complication with ModbusMode. First I tried set 101 - 104 but that was not working. It works only when 0 was set.

And you have right. Exact lenght of communicated data must be set.

And also I had problem when I used optimized data block for data writing. But that could be some my mistake.

Roman

Hi Roman, could you please send me the software zip file so I can go through it as I am facing the same problem.

Thank you very much in advance.