Are there limitation to the Ethernet/IP protocol or Profinet protocols? I saw that CIPSync is not supported. Our project scope does not require it, but I'd like to know if there are any other limitations in regard of the Object/Item creation etc. Any special limitation one should be aware of before the design start? Is there maybe an application note regarding protocol limitations for ethernet/ip and profinet in regard of the fido5x00 controllers?
My name is Chris Stelmar. I am a Product Applications Engineer for the Deterministic Ethernet Technology Group. CIP Sync is really a function of the host processor.
There are two design paths using the fido5x00.
Path 1: The RapID Platform: This uses the fido1100 and the fido5x000. The user has a processor that talks to the fido1100 by means of a UART or Parallel Interface. The fido1100 then communicates to the fido5x00 to do all the needed tasks for the given protocol. The user only needs to worry about the Parallel or UART communication.
Path 2: Fido5x00 interfaced with a customer processor: In this case the user needs to provide their own stack and use the protocol specific version of the fido5x00 driver that is distributed as portable C Code.
The hardware of the fido5x00 has been designed to support the key features of Industrial Ethernet communication. Therefore there are not any features in EtherNet/IP or PROFINET that are not supported. In the case of something like CIPSync, there is a lot of work that needs to be done on the part of the host processor. In the case of the RapID Platform, this feature is not supported. A user would be able to support CIPSync(though there is some significant work to be done in the user's application). as long as they have the proper stacks and support on their host processor application.
Please let me know if you need any more clarification.
Thank you very much.