• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] Use netX interface as profinet controller

I have been checking the 'netPI RE3' as profinet device/slave with netX inerface, CifX software and example provided, everything looks ok.

But i have a doubt is really there is not any chance to use this interface as profinet controller/master?? Best option recommended to work as profinet controller would be codesys and standard ethernet interface?? 

Dear Javi,

following needs to be said about netX51 industrial network controller that is used on netPI RTE 3:

The chip itself is able to carry only slave/device/adapter software as it it is stated on its official web site https://www.hilscher.com/products/produc...s/netx-51/

The netX51 was specifically designed to deliver fast and easy way to exchange cyclic ethernet/fieldbus IO data with any kind of host CPUs such as the Raspberry CPU. And to be honest the chip does it well and very good in thousands of applications (not only on netPI). From the beginning netX51 was never designed (ARM CPU power related used on netX51) to provide master functionality. So this is a dead end. We have no master software for netX51, netX52 ...

Now back to your question about Codesys:

Codesys itself comes with ready to use master stacks such as profinet, ethernet/ip and ethercat. Those are all TCP/IP based protocols and could be driven across any standard LAN ethernet interface.

As I stated before netX51 is strong in exchanging IO data fast with a host CPU, but netX51 was never designed to work as a TCP/IP standard ethernet controller. But of course it can support TCP/IP traffic too (as the LAN container example shows it), but not at a performance level equal to standard ethernet controllers you are used to cause we have to handle the traffic across acyclic messages between Raspberry and netX51. And we have the bottleneck "SPI" in general between Raspberry and netX51. All in sum the TCP/IP support of netX51 is  more or less moderately and the interface is relatively slow to manage real-time protocols such as PROFINET, EtherCAT or EtherNet/IP across. This is why driving those protocols with Codesys across will fail or show timeout effects.

This is how I would do it and at least three netPI customers I know of are doing it:

They mixed the "Codesys container" with the "netX ethernet LAN container". So initially they have 3 TCP/IP supporting ethernet ports active on their netPI RTE 3 ... and use the two (switched ports with one MAC and one ip address) netX ethernet ports in LAN mode as interface with the Windows Codesys programming tool to program the Codesys runtime and the single Raspberry ethernet port as interface to do Profinet Master/EthernetIP/EtherCAT master. This works 100% fine and well.

You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

Hi Armin,

Thaks a lot for your explanation, everything is competely clear!


Possibly Related Threads...
Thread Author Replies Views Last Post
  netPI-netx-programming-examples update slos 10 67 August-6th-2020, 11:01 AM
Last Post: Armin@netPI
  Profinet communication between plc and pc leehc 1 11 May-26th-2020, 09:03 AM
Last Post: Armin@netPI
  netX linux driver Irina Grinberg 4 25 May-7th-2020, 01:33 PM
Last Post: Armin@netPI
  how to pick up PROFINET data and store them to OPC UA server on Node-RED/netPI. tad 7 48 March-16th-2020, 10:21 AM
Last Post: Armin@netPI
  PROFINET IO startup compilation arpan.patel@slscorp.com 3 16 February-24th-2020, 12:47 PM
Last Post: Armin@netPI
  Profinet Startup Time Schranz 3 35 November-18th-2019, 03:22 PM
Last Post: Armin@netPI
  Codesys RTE profinet echteler 2 34 September-25th-2019, 09:56 AM
Last Post: Armin@netPI
  normal ethernet port using for Profinet MGharat 4 37 August-7th-2019, 10:39 AM
Last Post: hannes
  RTE3 Use real time ethernet as "normal" ethernet interface hannes 50 325 May-9th-2019, 04:28 PM
Last Post: Armin@netPI
  Detecting NetPI in Siemens TIA via Profinet andrewc 3 37 April-11th-2019, 06:42 PM
Last Post: Armin@netPI

Forum Jump:

Users browsing this thread: 1 Guest(s)