Scheneider M241 Modbus tcp/ip connect S71200 siemens

[Ricardo Carmo]

Hello;

i'm having some troubles with a com test i'm handling.
i have another end for it, but for now i would like to have :
M241 in io_scanning, trough modbus tcp/ip
and s7 1200 in client mode accessing it

i uploaded in the pictures of the DB in siemens(s7 1200) side, witch says it is connect to the server and the server is replying.

and the pictures on the Schneider(m241) side, that does not receive inf. http://plctalk.net/qanda/images/icons/icon8.gif

i already connected two s7 1200 on client server basis -> ok
i already connected the m241 on io scaning to other Schneider devices -> OK

so, the manual on M241 says it only need ethernet port for this function
https://www.se.com/us/en/faqs/FA304472/
and it should be a easy integration as long i respect the offsets of wr/rd.
https://support.industry.siemens.co...neider-tsx57-server/156583?page=0&pageSize=10
it's 1500 and a tsx but !
i do not see where i got it wrong

hope some one help's me,

 

[Lare]

It would be easier if you post also your network screenshots of Siemens side also.



M241 is having IP address 192.168.1.1?
and IP ending to 21 is device which you IO-scan on M241?


It is maybe MB unit id needs to be 1 instead of 255.




Also if you several different coms to simultaneously to same IP and port from siemens, then you need to queqy them so that only one communication is actve at one time.

(What are statMBclientinput_2 and _3 on DB2?
Different MB client blocks?

 

[Lare]

MB unit ID is on static area of MB_client block, by default it is 255.

I have to check, but thinking that it maybe needs to be 1 instead of 255, even that you have TCP MB



Then there are also Tcon_IP_V4.ID number.


You have there also 255, but it only need to be different to every block (start from 1,2,3 and query every block individually. 255 should work for that ID number, if it isn't used to elsewhere)





https://cache.industry.siemens.com/...95681/v1/s71200_system_manual_en-US_en-US.pdf


https://support.industry.siemens.co...80c8-in-modbus-tcp/180357/?page=0&pageSize=10


pages 1177 and 1187-1190

 

[Ricardo Carmo]

MB unit ID is on static area of MB_client block, by default it is 255.

I have to check, but thinking that it maybe needs to be 1 instead of 255, even that you have TCP MB



Then there are also Tcon_IP_V4.ID number.


You have there also 255, but it only need to be different to every block (start from 1,2,3 and query every block individually. 255 should work for that ID number, if it isn't used to elsewhere)





https://cache.industry.siemens.com/...95681/v1/s71200_system_manual_en-US_en-US.pdf


https://support.industry.siemens.co...80c8-in-modbus-tcp/180357/?page=0&pageSize=10


pages 1177 and 1187-1190

Ty very much for you reply;

i was not doing anything wrong.
i ended up solving my problem with a a simple test.

i thought the maping had to be done in the M241 in scheneider side -> THIS IS NOT TRUE

for everyone having such problems with MODBUS wat you need to do is the following.

S7 -> Client
M241 -> Server

the S7 will point to the word stack on the M241 and the index points to the firt word, it does not matter the maping you do on the M241 side.
you just need to add the slave to the hardware to let the M241 knows he will be scanning the nwtwork.

so i was already writing to the M241 and i didnt know because i was loking at the wrong mem area, i will leave the two projects here

just be careful on the scheneider side to match:
- the ip of the slave
- the id of the slave

on the siemens side you will use this
and on the modbus mode use:
0 -> for reading
1 -> for writing

Word index:
M241 %mw0
siemens index 40001+ offset you desire after %mw0(if you use this index the PLC automatically send the right string for writing and reading word, start on 0 for bit mem)

hope this saves some one time
siemens (tiaportal 15)
scheneider(somachine 4.3)

 

[Ricardo Carmo]

here is the link for my mega account more then 300kb not permited got around it

https://mega.nz/folder/gLwn3ToY#AvXgoOumHLPOYP9ulFHd3Q