February-12th-2018, 02:55 PM
Well vdupont this question can be easily answered.
Yes RPi 3 + netHAT behave the same as netPI. Even if netHAT uses netX52 industrial network controller and netPI uses netX51 they both communicate across SPI0.0 device with the raspberry CPU and have the same function API.
But with netPI you have more possibilities than with netHAT. netHAT is just a product for evaluation for all those who have interest in simple real-time ethernet connectivity. The driver that comes with netHAT in the download section here https://www.netiot.com/interface/nethat/ configures the module always to fix 32 bytes input and output. No flexibility.
With netPI we opened the whole netX interface to users. On one hand we have examples how to program netX yourself in C-language and for an easy understanding we have programmed a netX node for node-red that you can use.
You have recognized well that netPI is a docker host and only containerized software can be loaded into it. But no worry, you can of course connect to netX directly in a container.
To support all customers with examples we are providing ready-to-use docker containers here https://hub.docker.com/u/hilschernetpi/ which all have a direct link to their source code on Github.
I have one tip for you. This docker container example here https://hub.docker.com/r/hilschernetpi/n...-fieldbus/ is made for netPI and netHAT both. The container detects whether it is running on a Rpi with netHAT or netPI and then provides you a node-red with netx nodes where you have immediate access to real-time ethernet data of netX chip in node-red.
You are right that netPI does not have SSH and Cli. Instead you have a web page you start the containers with. For clearance watch the netPI videos showing you how all this works https://www.youtube.com/user/HilscherAutomation
Both netX51 and netX52 are "slave" chips in the view of the real-time ethernet system. They cannot be a master. But netX51 and netX52 can both be standard TCP/IP supporting devices in a container. So in this case netPI get three standard ethernet ports. The example container how to set up netPIs ethernet ports to be standard ethernet ports you find here https://hub.docker.com/r/hilschernetpi/n...ernet-lan/.
And of course netPI can include PLC functionality and send data across the standard ethernet ports. We have made a container where CoDeSys is running in a container on netPI here https://hub.docker.com/r/hilschernetpi/n...sys-basis/. I personally tested it with profinet as a master and it works fine. There is video with CoDeSys here https://www.youtube.com/watch?v=N4ePYf-9cS8.
Yes RPi 3 + netHAT behave the same as netPI. Even if netHAT uses netX52 industrial network controller and netPI uses netX51 they both communicate across SPI0.0 device with the raspberry CPU and have the same function API.
But with netPI you have more possibilities than with netHAT. netHAT is just a product for evaluation for all those who have interest in simple real-time ethernet connectivity. The driver that comes with netHAT in the download section here https://www.netiot.com/interface/nethat/ configures the module always to fix 32 bytes input and output. No flexibility.
With netPI we opened the whole netX interface to users. On one hand we have examples how to program netX yourself in C-language and for an easy understanding we have programmed a netX node for node-red that you can use.
You have recognized well that netPI is a docker host and only containerized software can be loaded into it. But no worry, you can of course connect to netX directly in a container.
To support all customers with examples we are providing ready-to-use docker containers here https://hub.docker.com/u/hilschernetpi/ which all have a direct link to their source code on Github.
I have one tip for you. This docker container example here https://hub.docker.com/r/hilschernetpi/n...-fieldbus/ is made for netPI and netHAT both. The container detects whether it is running on a Rpi with netHAT or netPI and then provides you a node-red with netx nodes where you have immediate access to real-time ethernet data of netX chip in node-red.
You are right that netPI does not have SSH and Cli. Instead you have a web page you start the containers with. For clearance watch the netPI videos showing you how all this works https://www.youtube.com/user/HilscherAutomation
Both netX51 and netX52 are "slave" chips in the view of the real-time ethernet system. They cannot be a master. But netX51 and netX52 can both be standard TCP/IP supporting devices in a container. So in this case netPI get three standard ethernet ports. The example container how to set up netPIs ethernet ports to be standard ethernet ports you find here https://hub.docker.com/r/hilschernetpi/n...ernet-lan/.
And of course netPI can include PLC functionality and send data across the standard ethernet ports. We have made a container where CoDeSys is running in a container on netPI here https://hub.docker.com/r/hilschernetpi/n...sys-basis/. I personally tested it with profinet as a master and it works fine. There is video with CoDeSys here https://www.youtube.com/watch?v=N4ePYf-9cS8.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
