June-2nd-2021, 07:26 AM
(This post was last modified: June-2nd-2021, 07:27 AM by Armin@netPI.)
Well Tad, netPI embeds a standard netX51 network controller. The controller needs a firmware loaded into its FLASH memory to operate in mode PROFINET, EtherNet/IP, EtherCAT and so on. So there is nothing special with netPI in relation to netX. Basically you can say that netPI is a kind of embedded Linux platform for netX51 evaluation/programming purposes.
So since netPI is a standard netX51 host all the informations about the protocols available for this controller collected on our knowledge base here https://kb.hilscher.com/display/HILKB/Technologies are valid. This comprises the documentations, the change logs and also, firmware function etc. This means in turn all the functions described on this pages are supported by netX51 used in netPI.
Since I am not the protocol expert in all details you can read on these knowledge base page about the different supported protocol functions yourself if two master communications are supported or not.
You know that we are providing netX programming examples already here: https://github.com/HilscherAutomation/ne...g-examples. But these programming examples show just the very basic functions of all the protocols. Just the plain and simple IO communication was in focus. There is not something programmed like shared a device in PROFINET or multi assemblies in EtherNet/IP for multi master support. All this can be found how to program it in the respective protocol programming manual.
Thx
Armin
So since netPI is a standard netX51 host all the informations about the protocols available for this controller collected on our knowledge base here https://kb.hilscher.com/display/HILKB/Technologies are valid. This comprises the documentations, the change logs and also, firmware function etc. This means in turn all the functions described on this pages are supported by netX51 used in netPI.
Since I am not the protocol expert in all details you can read on these knowledge base page about the different supported protocol functions yourself if two master communications are supported or not.
You know that we are providing netX programming examples already here: https://github.com/HilscherAutomation/ne...g-examples. But these programming examples show just the very basic functions of all the protocols. Just the plain and simple IO communication was in focus. There is not something programmed like shared a device in PROFINET or multi assemblies in EtherNet/IP for multi master support. All this can be found how to program it in the respective protocol programming manual.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)