Siemens Plc To Plc Communication Ethernet

[Earlie Schwoyer]

Hiall, apologies for what may seem a simple question, but this is an area I've not had to deal with in the past as I've worked on stand alone installations that just use profinet/profibus! I've had a search around, but my lack of knowledge on networking is making it hard to think of the right keywords! I'm currently the middle man between our software engineers (who don't have much experience with Siemens PLC's, but know all about networking!) and our suppliers, so I'm looking to boost my knowledge on the subject so I can be of ,ore use.

Basically, we have a control system in use which communicates using ethernet (in this case it is a train and uses it's own control system). Currently we have some sub-systems using S7-1214 PLCs which communicate with this by simple digital IO, but this limits the amount of data we can extract from these systems. We would like the S7's to be able to send process data (digital signals, temperatures etc) through ethernet using DHCP on our control system. I believe a CP-1243-1 has been suggested by one of the suppliers to use as a communication device between the two systems.

Would this be a suitable way of exporting the process data to our system, and be easy enough to integrate to both systems? If anyone can point me in the direction of some information on this subject it would be much appreciated!

I am not sure that you will find everything you are looking for in this reply,but first look at the communications alternatives proposed in the S7-1200 System manual, especially the three possibilities for Open Communications (using TCP/IP, Iso-over-TCP and UDP).

I am having a S7 1500 PLC & Fanuc Robot. The Fanuc robot supports ethernet IP communication. So as for now i want to have some clarification regarding this ethernet IP communication in S7 1500?.. Please help me!!

S7 PLCs do not support Ethernet/IP natively, they are designed to work with Profibus and Profinet basically. But recent additions of specialized libraries allow other protocols such as Ehernet/IP to be run on S7-1500 PLCs, using the ntegrated Profinet port of the CPU, for example.

Searching on this topic I retrieved the sample library from the link you attached. However, it is asking me a password to compile. Do you know if I need to buy this library from siemens? Or is the password provided on another site?

I managed to solve my problem. I did some reading on the compilation requirements of know-how function blocks, and my issue was I was trying to compile it on a firmware prior to 4.3. And because a data type changed between firmwares, I needed a password to recompile the function block. Once the s7-1200 plc was migrated to firmware 4.3 the issue was resolved.

After three days of attempts with the colleague, we finally managed to establish the communication between C7 1513F-1 PN and robot Fanuc. You need the data from EDS (electrronic data sheet file), EnetScanner [OB30] block and EnetIoSystem [DB]. The specific thing for us was that, if you use 32 Bytes for Size of conPointOrigTarget and 32 Bytes for Size of conPointTargetOrig you need to set 16 Words in Fanuc.

Automotive Ethernet is a form of Ethernet network with a physical layer adapted to automotive use cases. The cost of cable is reduced by use of sophisticated Phy transceivers providing a system that is capable of automotive electromagnetic compatibility and immunity requirements in automotive conditions. It enables higher baud rate communications than traditional automotive network technologies and allows the re-use of Internet Protocol (IP) software technologies from other industries directly, or adapted to automotive use, functional safety, cyber security etc.

Automotive Ethernet offers a robust and flexible communication infrastructure that is well-suited to support the connectivity, automation, and electrification trends shaping the future of the automotive industry.

Ethernet provides high-speed data transmission, which is crucial for handling the increasing volume of data generated by advanced driver assistance systems (ADAS), infotainment systems, and other onboard electronics.

Ethernet offers improved reliability compared to traditional automotive networking protocols, thanks to features like error detection and correction, redundancy and the ability to prioritize critical data.

Ethernet is compatible with IP-based communication protocols, making it easier to integrate vehicle systems with external networks and services, such as cloud-based applications and over-the-air updates.

Support for time-sensitive networking (TSN) is an extension of ethernet for deterministic communication with precise timing, essential for real-time applications like autonomous driving and vehicle-to-vehicle communication.

The differences between Ethernet and automotive Ethernet are in the physical layer. The communication above is IP as per other Ethernet types. The physical layer has been optimized around the automotive use cases, 100Base-T1 and 1000Base-T1 are switched networks as standard Ethernet, but the Phy transceivers and cables are different, using lower cost single twisted pair with full duplex communication, rather than dual twisted pair, this may be Shielded (STP) or Un-shielded (UTP) twisted pair depending on needs. 10Base-T1S is also a single twisted pair, but a multi-drop bus (like CAN), rather than a switched network.

Communication among electronic control units (ECUs) has become more complex, and network throughput has grown in bandwidth with increased software functionality in cars. Ethernet-based communication offers high bandwidth and higher flexibility for integration with cloud services and consumer products. And while it may add a more complex set of standards and protocols, they are more scalable than specialized automotive networks with the same communication software used to make updates easier over time.

The first version of automotive Ethernet developed by Broadcom as BroadR-Reach, then standardized by the OPEN Alliance SIG as IEEE 100Base-T1 has a baud rate of 100Mbits/sec. Subsequently 1000Base-T1 has been standardized offering 1Gbit/sec, and 10Base-T1S is the latest offering a lower cost physical layer supporting 10Mbits/sec to provide an alternative to FlexRay and high baud rate versions of CAN bus. Multiple baud rates of Ethernet can be used together on the same architecture, without complex gatewaying of different protocols, easing the scalability over the life of a given E/E architecture.

There are many benefits that automotive Ethernet brings compared to traditional automotive communication protocols, but it must be adequately designed to embrace its potential fully. Additionally, OEMs have design rules and standards instructing the network design engineers which protections to use in system design scenarios. Automotive software solutions help with setting up a design model, enabling consistency checks to guide the designer toward problems and making sure the networks are correct by design and consistently described in the software configuration outputs.

I have a problem between my plc and robot. I have a siemens plc s1500 and a fanuc robot, im trying to comunicate them with ethernet ip. I have follow all the steps but i cant comunicate the plc with the robot, both of them are in the same ip range and i can ping each one from the computer. Also i can ping the plc from the robot. The plc is the scanner and the robot is the adapter

In the Fanuc robot, the ethernet ip connection is online but not running. I have checked all the EDS data from the robot and i am sending thease values correctly from the plc. Also the tcp/ip connection has been initialized.

I have a 1517TF-3 plc with v2.0 firmware, im using tia portal v15.1 and the robot controller is Fanuc R-30iB Plus. Im trying to communicate the plc with the robot using ethernet ip. In Tia portal im using LCCF enetScanner block, the plc works as scanner and the robot as adapter. Im sending to the robot the IP address, vendor identifier, product type,...

The robot is configured to work in rack 89 and slot 1, also it has the ip address and it communicates with the plc. But in the plc the scanner active signal is always off. The ethernet ip connection is activated and the status is online, but is not running, im using the first connection.

May I ask, where you get the "RPI >= 32 ms" from? I am currently configurating a Fanuc Siemens connection with this function block and did not find this value in any of the manuals. Is this something you have found out by experiments?

RPI for PLC side. Use "packetinterval" parameter of Function block. You can found parameter in instance DB of FB. If you using RPI less than 32 connection problems occured randomly. Because Siemens PLC is not powerfull CPU for Ethernet/IP

S7-1500 manages to support EIP Communication, S7-1200 does not have enough power (communicates but when loading a new configuration in the PLC, the communication drops). For me, the main problem was the incorrect configuration of the input and output registers on both sides (Robot and PLC). In the robot, the registers are 16 bits, while in the S7 they are 8 bits.

3a8082e126