SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Connecting to remote PLC's

5/23/2006 11:15 AM	Rate (0)
Jeebs Posts: 218 Rating: (28)	Hey, I have a project which consists of multiple PLC's S7-400's, S7-300 and S7-200, all connected to a main PLC S7-412 through either Profibus or Ethernet. I have 7 similar projects, all working fine on one Field PG. With that PG I can see every station, connect to every station. But when I archive the project and then retrieve it with my second PG it instantly refuses to 'see' any station when using the Ethernet connection. With profibus, every thing works fine, but when trying to use Ethernet on the second PG it just refuses. It doesn't even try to connect, it instantly gives me the message: 'Remote partner is not responding'. This only happens on one of the projects, which was working fine till recently. Out of idea's on this one. Any idea on how to fix this besides reconfiguring every connection? Jeebs
Jeebs Posts: 218 Rating: (28)
Suggestion To thank Quote Answer

5/23/2006 1:00 PM	Rate (0)
Chris Silver Member Joined: 8/31/2005 Last visit: 10/24/2024 Posts: 217 Rating: (41)	Are the IP addresses of the second Field PG in the same subnet as the IP addresses of the PLCs? If not, you have to adjust the IP address and the subnet mask of the Ethernet card in you Field PG. Are you able to "ping" the PLCs via the command promt of your Field PG?
	Last edited by: Chris at: 5/23/2006 1:01 PM Last edited by: Chris at: 5/23/2006 1:01 PM Greetings, Chris
Suggestion To thank Quote Answer

5/23/2006 2:29 PM	Rate (0)
Jeebs Posts: 218 Rating: (28)	Both PG's get IP's assigned by the DHCP, they have the same subnet, same gateway, same DNS server, same WINS server. The PLC's with Ethernet connection can be pinged and reached, but that is because they are connected to our industrial net. Reaching the PLC's that are connected through profibus to the central PLC is what proves to be a problem. The central PLC is used as a gateway to the Profibus network. It works fine on one PG, but refuses to work on the other. Which is weird, cause the project was originally created on the PG that doesn't work anymore.
Jeebs Posts: 218 Rating: (28)
Suggestion To thank Quote Answer

5/23/2006 5:08 PM	Rate (0)
Chris Silver Member Joined: 8/31/2005 Last visit: 10/24/2024 Posts: 217 Rating: (41)	In order to access a PLC via a gateway station (PG routing) all S7 stations within your project need to know, which nodes (PLCs, PGs, ...) are connected to the subnets. Therefore you have to add a PG, that is connected with the gateway PLC, into your STEP 7 project (you have done this already, I think). These informations are saved in routing tables in the CPUs or CPs. Once you download the system data to your PLCs, they get the information, that a PG with a specific IP address is connected to the gateway PLC. If you want to use a PG to access a PLC via the gateway PLC, this PG needs to have the same IP address, as the IP address in the system data (the routing table) of the gateway PLC. This IP address can be found in the STEP 7 project, that was originally downloaded to the gateway PLC. More information on PG routing can be found here: Configuring Hardware and Communication Connections STEP 7 V5.4 (Chapter "11.7 Networking Stations that Represent Network Gateways")
	Last edited by: Chris at: 5/23/2006 5:09 PM Greetings, Chris
Suggestion To thank Quote Answer

Share this page:

Share this page on...