September-20th-2018, 02:00 PM
Well Philipp,
we have netX Network-Contoller (netX100) chips that are able to represent a Real-Time Ethernet Slave and can be a "sniffer" at the same time. But the used netX Controller in netPI is not able to provide such functionality. Even more the real bottle neck between used netX51 on netPI and raspberry CPU is the SPI interface in between. This is good to exachange a certain amount of inputs and outputs (I know you don't care) with the Raspberry CPU, but it would never be good to record and transport all the traffic coming from EtherCAT to the Raspberry CPU.
I am sorry that I have no better answer for you.
Armin
we have netX Network-Contoller (netX100) chips that are able to represent a Real-Time Ethernet Slave and can be a "sniffer" at the same time. But the used netX Controller in netPI is not able to provide such functionality. Even more the real bottle neck between used netX51 on netPI and raspberry CPU is the SPI interface in between. This is good to exachange a certain amount of inputs and outputs (I know you don't care) with the Raspberry CPU, but it would never be good to record and transport all the traffic coming from EtherCAT to the Raspberry CPU.
I am sorry that I have no better answer for you.
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)