Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Help Collect data from Festo cpx plc via Modbus TCP

Created by: mehmet akyuz at: 9/9/2009 10:05 AM (9 Replies)

Rating (2)

Thanks 3

10 Entries

9/9/2009 10:05 AM	Rate (0)
mehmet akyuz Posts: 5 Rating: (0)	Hi, I want communicate between Festo CPX plc and cpu 414-1 414-1XG02-0AB0 and 443-1EX11-0XE0 with open modbus TCP.cpu 414 will be master I can communicate between PC and Festo cpx plc with modbus tcp. I 'll read/write holding register. cpx's modbus device mapping is input adress (read) 45392 to 45647 output adress (write)40001 to 40256 I tried with example code but I always read CONTROL DAT.STATUS value as an error code 80A4 or 8304. How can I solve this problem.? code is in attachment Best Regards, Mehmet Attachment Modbuswi.zip (843 Downloads)
mehmet akyuz Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

9/9/2009 11:33 AM	Rate (0)
smiffy Platinum Member Joined: 1/17/2007 Last visit: 10/21/2024 Posts: 1547 Rating: (537)	Both the status codes you have quoted point to the connection not being established / open. Have you set up a TCP connection in NetPro to the target device? The local port can be any that is not used (I normally use 2000). The remote port should be 502 (which is specifically reserved for modbus). The remote IP address should be the IP address of your target device. Because you are master you will have to check the "active connection establishment" checkbox when setting up the connection (see attached pictures activecon1 and activecon2). activecon1.gif shows the connection properties. activecon2.gif shows the port/IP address details. Have you used the correct ID and LADDR parameters on the block inputs? (get them from netpro - see activecon1.gif) Is the connection shown as open in NetPro? (use the "Activate/Deactivate Connection Status" button to display the current connection status. It is selected via netpro by clicking on the icon that looks like a plug and socket with a 'i' on it). I have also included the use manual for your reference. Attachment modbus.zip (813 Downloads)
	Programming today is the race between software engineers building bigger and better idiot proof programs, and the universe producing bigger and better idiots. So far, the universe is winning...
Suggestion To thank Quote Answer

9/9/2009 1:06 PM	Rate (0)
mehmet akyuz Posts: 5 Rating: (0)	hi smiffy, I checked list and onlyI checked active connection establishment. Connection status is established and in tcp connectionproperties send andreceive status is waiting. but I can't readregister in plc andCONTROL DAT.STATUS valuehas an error code 80A4 How can I solve? I addedscreenshots in attachment Thank you for your help Mehmet Attachment screen.zip (782 Downloads)
mehmet akyuz Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

9/9/2009 2:13 PM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Hi, 80A4 is not a modbus error, it's a communication error message from AG_SEND/AG_LSEND. Compile and download the HW Config and Netpro once again and try it again. I would like to have a look at your program, but I don't have 'turkish' on my PC. Can you change it and attach again? Wüstenräuber

Suggestion To thank Quote Answer

9/9/2009 3:02 PM	Rate (0)
mehmet akyuz Posts: 5 Rating: (0)	hi Wüstenräuber, code is in attachment. thank you for your help. best regards, Mehmet Attachment Modbuswi.zip (750 Downloads)
mehmet akyuz Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

9/9/2009 3:20 PM	Rate (1)
smiffy Platinum Member Joined: 1/17/2007 Last visit: 10/21/2024 Posts: 1547 Rating: (537)	OK the connection is open. Good. From NetPro you can see the connection parameters; in your case ID=1 and LADDR=16#3FFA. Can you check that these are the value used on the modbus block inputs. If that is the case have you done a compile, download and cold restart since you setup the NetPro connection? Something that I have notced that is not realsted to this particular problem, but will give you issues later on is that you are not controlling the inputs to the modbus block correctly. Your value table shows:- START_ADDRESS = 0 - This is valid but is this what you require? This value equates to the first modbus register (e.g. 40001 for holding registers). LENGTH = 0 - This is not valid. You cannot ask for a regsiter count of zero registers. TI = 0 - This is valid, but it should be set to a new value on each new request for data (rising edge of ENQ_ENR) UNIT = 0 - This is not valid as zero means broadcast. This should equal the unit identifier of the modbus server. WRITE_READ = FALSE - This means that you are wanting to write data to the slave (TRUE means read data from the slave). This looks suspisiously like you have not got any code to set this block inputs up correctly so that it will process your requests. Read and study the manual I sent you.
	Programming today is the race between software engineers building bigger and better idiot proof programs, and the universe producing bigger and better idiots. So far, the universe is winning...
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users lawdeale

9/9/2009 3:35 PM	Rate (0)
smiffy Platinum Member Joined: 1/17/2007 Last visit: 10/21/2024 Posts: 1547 Rating: (537)	Just opened your project and it would seem that you have not parameterised the block correctly. You have set it up in OB100, but the values you have used do not match your hardware / NETPRO settings (e.g. ID=1, LADDR=16#3FFA). You are calling the block cyclically in OB1, but you are only setting the MONITOR, ENQ_ENR, DONE_NDR, ERROR, STATUS, START_ADDRESS, LENGTH, WRITE_READ, TI and UNIT inputs. You will also have to set the other inputs such as ID, LADDR, DB1, START1, END1, SERVER_CLIENT etc. Even the ones that you are setting do not look to be set correctly as I pointed out in my earlier post. You need sit down with the manual and have a good read through it.
	Programming today is the race between software engineers building bigger and better idiot proof programs, and the universe producing bigger and better idiots. So far, the universe is winning...
Suggestion To thank Quote Answer

9/9/2009 4:45 PM	Rate (0)
mehmet akyuz Posts: 5 Rating: (0)	hi smiffy, are you sure you look my attachment ?my settings (ID= 1 and LADDR=W#16#7FC) I parameterised the block in OB100with initiate_modbusFB (FB200). and I call modbus blockFB100 inFB200 and OB1 with same DB100. so I don't need set values such as ID, LADDR, DB1, START1, END1, SERVER_CLIENT etc. Other thing isIwant touse server mode and if you look at themanual, STATUS, START_ADDRESS, LENGTH, WRITE_READ, TI and UNITareoutput parameter. my question is why I getan error code 80A4on modbus function block (FB100) 'sSTATUS. best regards, Mehmet
mehmet akyuz Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

9/9/2009 8:06 PM	Rate (1)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Hi, I think there is a misunderstanding. Modbus Master is the Modbus Client and the Modbus Slaveis theModbus Server. In the program you parameterized the modbus block as a server (SERVER_CLIENT = TRUE). But in NetPro you parameterized the connection as an active connection. This is not correct. Normally the modbus server (slave)gets the port number = 502. The client (master) gets a port number unlike 502, e.g. 2000, and is responsible for the connection establishment. Ifthe S7 should be the server(slave), then Isuggest to change the configuration in NetPro: S7 gets the port number 502, the other station gets the port number 2000 and the "Active connection establishment" is FALSE. Then compile, download and try it again. If the S7 should be the client (master), then you have to change the S7 program. Wüstenräuber

Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users mehmet akyuz lawdeale

9/10/2009 8:44 AM	Rate (0)
mehmet akyuz Posts: 5 Rating: (0)	Hi Wuestenrauber, I mixed client - server definition. whenI parameterized the modbus block as a client, they can connect Thank you for your help Best regards, Mehmet
mehmet akyuz Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on