Navigation

S7 315F- 2PN/DP Communication with METTLER TOLEDO IND560

Created by: naveen_paliwal at: 6/24/2013 12:52 PM (11 Replies)

Rating (0)

Thanks 5

Result pages:: |; 1 | 2; |

12 Entries

Entries per page: 10 | all

6/24/2013 12:52 PM	Rate (0)
naveen_paliwal Bronze Member Joined: 4/25/2011 Last visit: 10/15/2024 Posts: 128 Rating: (5)	Dear Experts, I want to communicate METTLER TOLEDO IND560 with s7 PLC on ethernet. How can I do it?? thanks n rgds
	Last edited by: naveen_paliwal at: 6/24/2013 12:54 PM Naveen Paliwal Vibrant Automations Pvt Ltd Rajasthan, India +919887624827 https://www.vaplindia.co.in/ E-mail- info@vaplindia.co.in
Suggestion To thank Quote Answer

6/24/2013 3:47 PM	Rate (0)
legacy support Silver Member Joined: 7/15/2008 Last visit: 10/6/2024 Posts: 382 Rating: (44)	naveen_paliwal Dear Experts, I want to communicate METTLER TOLEDO IND560 with s7 PLC on ethernet. How can I do it?? thanks n rgds Hello naveen Please download the PLC Interface maual for the IND560 Scale from Mettler Toledo. If you did not buy the profibus interface for the IND560, then the best option would be to get the profibus interface. If not than I would suggest a ethernet/ip to profibus or profinet gateway. As far as I know the S7 300 does nor support ethernet/ip. Regards / m.f.g

Suggestion To thank Quote Answer

6/24/2013 3:52 PM	Rate (0)
naveen_paliwal Bronze Member Joined: 4/25/2011 Last visit: 10/15/2024 Posts: 128 Rating: (5)	Dear legacy support in manual it showing detail about profibus communication. But my device have two communication ports only first RS232 n second is ethernet. how can I do , plz support. thanks
	Naveen Paliwal Vibrant Automations Pvt Ltd Rajasthan, India +919887624827 https://www.vaplindia.co.in/ E-mail- info@vaplindia.co.in
Suggestion To thank Quote Answer

6/24/2013 4:30 PM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 11/4/2024 Posts: 12293 Rating: (2690)	Hello Naveen; The IND560 product guide shows that the Ethernet/IP optional board (which you should have, if you requested Ethernet connectivity)can be configured to work with Modbus/TCP, which is available on S7 Ethernet CPs (and Profinet CPUs). This is the easiest option recommended in your case, if you do not have Profibus available. Have a look at the following information on the subject: How can you establish OPEN MODBUS / TCP communication from a SIMATIC S7 and where can you find further information? Hope this helps, Daniel Chartier Attachment IND560 Ethernet options.jpg (544 Downloads)

Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users naveen_paliwal gergshlaw

6/26/2013 6:52 AM	Rate (0)
naveen_paliwal Bronze Member Joined: 4/25/2011 Last visit: 10/15/2024 Posts: 128 Rating: (5)	Dear dchartier, thank you, but I need more support. Which programming blocks needed to do the communication. What to do From IND560 side? A sample program will be very helpful for me. thanks n regards
	Naveen Paliwal Vibrant Automations Pvt Ltd Rajasthan, India +919887624827 https://www.vaplindia.co.in/ E-mail- info@vaplindia.co.in
Suggestion To thank Quote Answer

6/26/2013 7:28 AM

Rate (0)

DS SURESH KUMAR

Bronze Member

Joined: 4/17/2012

Last visit: 8/30/2024

Posts: 474

Rating:

(10)

naveen_paliwal
Dear dchartier,

thank you, but I need more support. Which programming blocks needed to do the communication. What to do From IND560 side?
A sample program will be very helpful for me.

thanks n regards

Hi,

What is your HW configuration?

If you are try to connect your device through Modbus TCP then you have to install the driver block.

In your application CPU is master so in that parameter block you have to mention the DB address to store the slave data.

FB2,3,

In Device side:

you have to set the device ID. and parity and stop bit.

In both master and slave should have same parameters.

HW requirement:

Hardware requirements
Product	Hardware requirements and belonging order numbers
Modbus/TCP CP (2XV9 450-1MB00)
	CP343-1	Blockwith AG_CNTRL	Block without AG_CNTRL
	6GK7 343-1CX00-0XE0	No	Yes
	6GK7 343-1CX10-0XE0 (*)	Yes (from FW V2.1)	Yes (up to FW 2.0)
	6GK7 343-1EX11-0XE0	No	Yes
	6GK7 343-1EX20-0XE0	No	Yes
	6GK7 343-1EX21-0XE0	Yes (from FW V1.0.17)	Yes
	6GK7 343-1EX30-0XE0 (*)	Yes (from FW V2.0.16)	Yes
	6GK7 343-1GX11-0XE0	No	Yes
	6GK7 343-1GX20-0XE0	No	Yes
	6GK7 343-1GX21-0XE0	Yes (from FW V1.0.24)	Yes
	6GK7 343-1GX30-0XE0	Yes (from FW V1.0.23)	Yes
	6GK7 343-1GX31-0XE0	Yes	Yes
	CP443-1	Block with AG_CNTRL	Block without AG_CNTRL
	6GK7 443-1EX10-0XE0	No	Yes (V2.6)
	6GK7 443-1EX11-0XE0	No	Yes
	6GK7 443-1EX20-0XE0	Yes (from FW V1.0.26, not V2.1.12)	Yes (not V2.1.12)
	6GK7 443-1EX30-0XE0 (*)	Yes (from FW V3.0)	No
	6GK7 443-1EX40-0XE0	Yes (from FW V2.2)	Yes
	6GK7 443-1EX41-0XE0	Yes (from FW V1.0.24)	Yes
	6GK7 443-1GX11-0XE0	No	Yes
	6GK7 443-1GX20-0XE0	Yes (from FW V2.0, not V2.1.12)	Yes
	6GK7 443-1GX30-0XE0 (*)	Yes (from FW V3.0)	No
	(*) These CPs support the multiple port 502. In this case the block with AG_CNTRL must be used.
	CPU: The Modbus blocks can be used from hardware release2 of CPU315 and CPU317. Modbus/TCP CP is released for standard CPUs, for F-CPUs and for PN-(H)-CPUs.
Modbus/TCP Red V1 (2XV9 450-1MB01)
	CP443-1
	6GK7 443-1EX10-0XE0		V2.6
	6GK7 443-1EX11-0XE0		V2.6
	6GK7 443-1EX20-0XE0		V2.0 (not 2.1.12)
	6GK7 443-1GX20-0XE0 (100MBit)		V2.0 (not 2.1.12)
Modbus/TCP Red V2 (2XV9 450-1MB11)
	CP343-1
	6GK7 343-1CX10-0XE0 (*)		from V2.1
	6GK7 343-1EX21-0XE0		from V1.0.17
	6GK7 343-1EX30-0XE0 (*)		from V2.0.16
	6GK7 343-1GX21-0XE0		from V1.0.24
	6GK7 343-1GX30-0XE0		from V1.0.23
	6GK7 343-1GX31-0XE0		from V3.0
	CP443-1
	6GK7 443-1EX20-0XE0		from V1.0.26 (not 2.1.12)
	6GK7 443-1EX30-0XE0 (*)		from V3.0
	6GK7 443-1GX20-0XE0 (100MBit)		from V2.0 (not 2.1.12)
	6GK7 443-1GX30-0XE0 (*)		from V3.0
	(*) These CPs support the multiple port 502.
	Modbus/TCPRed V2is released for standard CPUs, for F-CPUs and for PN-H-CPUs.
Modbus/TCP PN (2XV9 450-1MB02) Modbus/TCP 20 SENTRON PAC(6AV6676-6MA30-0AX0) Modbus/TCP100 SENTRON PAC(6AV6676-6MA30-1AX0) Modbus/TCP512 SENTRON PAC(6AV6676-6MA30-2AX0)
	300 PN-CPU
	6ES7 314-6EH04-0AB0		V3.3.1
	6ES7 315-2EG10-0AB0		V2.3.4
	6ES7 315-2EH13-0AB0		V2.6.7
	6ES7 315-2EH14-0AB0		V3.1
	6ES7 315-2FH13-0AB0		V2.6
	6ES7 315-2FJ14-0AB0		V3.2.3
	6ES7 317-2EJ10-0AB0		V2.3.4
	6ES7 317-2EK13-0AB0		V2.6.7
	6ES7 317-2EK14-0AB0		V3.1
	6ES7 317-2FK14-0AB0		V3.1
	6ES7 318-3EL00-0AB0		V2.7.2
	6ES7 318-3EL01-0AB0		V3.2
	6ES7 318-3FL01-0AB0		V3.2
	400 PN-CPU
	6ES7 412-2EK06-0AB0		V6.0.2
	6ES7 414-3EM05-0AB0		V5.2
	6ES7 414-3EM06-0AB0		V6.0.2
	6ES7 414-3FM06-0AB0		V6.0.2
	6ES7 416-3ER05-0AB0		V5.2
	6ES7 416-3ES06-0AB0		V6.0.2
	6ES7 416-3FS06-0AB0		V6.0.2
	400 PN-H-CPU (only Modbus/TCP PN)
	6ES7 412-5HK06-0AB0		V6.0.1
	6ES7 414-5HM06-0AB0		V6.0.1
	6ES7 416-5HS06-0AB0		V6.0.1
	6ES7 417-5HT06-0AB0		V6.0.1
	IM151-8 PN/DP
	6ES7 151-8AB00-0AB0		V2.7.1
	6ES7 151-8AB01-0AB0		V3.2
	6ES7 151-8FB01-0AB0		V3.2
	WinAC RTX (only Modbus/TCP PN)
	6ES7 671-0RC06-0YA0	(2008)
	6ES7 671-0RC07-0YA0	(2009)
	6ES7 671-0RC08-0YA0	(2010)
	PAC 3200 (for Modbus/TCP SENTRON PAC)
	7KM2111-1BA00-3AA0		V2.2.1
	7KM2112-0BA00-2AA0		V2.2.1
	7KM2112-0BA00-3AA0		V2.2.1

Software requirements
∙ SIMATIC STEP 7 version 5.4 or higher for the CP version of the MODBUS blocks ∙ SIMATIC STEP 7 version 5.1 or higher for the Red version 1 of the MODBUS blocks ∙ SIMATIC STEP 7 version 5.4 or higher for the Red version 2 of the MODBUS blocks ∙ SIMATIC STEP 7 version 5.4 SP4 or higher for the PN PLC version of the MODBUS blocks ∙ SIMATIC STEP 7 version 5.5 or higher for the PAC version of the MODBUS blocks

6/26/2013 7:39 AM	Rate (0)
DS SURESH KUMAR Bronze Member Joined: 4/17/2012 Last visit: 8/30/2024 Posts: 474 Rating: (10)	Hai, these are the basic blocks used for modbus tcp connection FB65 "TCON", FB66 "TDISCON", FB63 "TSEND" and FB64 "TRCV"

Suggestion To thank Quote Answer

6/26/2013 7:47 AM	Rate (0)
DS SURESH KUMAR Bronze Member Joined: 4/17/2012 Last visit: 8/30/2024 Posts: 474 Rating: (10)	Hi, https://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&objId=31535566&objAction=csOpen&nodeid4=20229805&lang=en&siteid=cseus&aktprim=4&extranet=standard&viewreg=WW Pls use the link to douwnload the file and zip folder then go ahead as per instruction , then it will full fill your requirement

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users naveen_paliwal

6/26/2013 1:35 PM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 11/4/2024 Posts: 12293 Rating: (2690)	naveen_paliwal Dear dchartier, What to do From IND560 side? thanks n regards Hello Naveen; I have not worked with this unit before, but I would expect you would have to establish Modbus/TCP as the protocol used, specify the Ethernet address and other parameters on the IND560 Since it would act as a server on the network, it cannot initiate communications (that is the privilege of the client, your PLC in this case) and you would have to read up on the Modbus mapping inside the IND560 so the client can read/write to the correct register addresses you need. Hope this helps, Daniel Chartier

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users naveen_paliwal

6/26/2013 3:43 PM	Rate (0)
UMENCHO Diamond Expert Joined: 3/21/2006 Last visit: 11/1/2024 Posts: 10229 Rating: (1181)	Hello, I would suggest you to clarify with the seller what exactly interface card has been installed in IND560. Then as suggested above check in documentation CD. Additional interface information and programming examples can be found in the IND560 PLC Interface Manual, which is included on the documentation CD. The Modbus TCP setup screen is used to configure this PLC interface option. Best regards, Hristo Mihalev

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users naveen_paliwal