February-18th-2020, 05:18 PM
Well you might got the impression that with netPI and "support of just a single input and output module in PROFINET" there is a dead end if you want to have more modules. This is not the case.
netPI is a unit that uses netX51 as underlying network controller. It is the very same thing as if a customer would come to us and want to design-in netX in his own embedded device, but this time it is Hilscher itself making use of their own network controller to build such an embedded device - named netPI.
What I want to say is, if you are a netX customer you have to go through all this documentation here: https://kb.hilscher.com/display/NETX/netX+51. Tons of material needs to be studied and also a workshop is offered that provides much more knowledge than a simple code example can provide. The netX support team welcome you for a workshop at any time to help out.
One word to the single input and output module. Next to the PROFINET example there is EtherCAT, EtherNet/IP, POWERLINK, SERCOS ... da da da. Aim with the examples was to deliver source code that behaves the very same for all networks. There are some network that do not support multiple slots/submodules like PROFINET does ... and hence the decision has been made to find a common denominator by stipping down all the fulminant capabilities to a level that applies to all networks. So now in the end there is just the app.h file to be edited deciding on the IO size and the rest is all hidden and handled in the subordinate network specific files. So the easiest way was to implement the single slot solution in PROFINET here ... while accepting cutting off 90% of the possibilies you really have with netX51.
Another thing I want to mentioned here is that the source code we provide on github is 100% based on the source code we provide to real netX51 customers when they come for a netX workshop.
netX52 chip has no external RAM. The software V4.x is a PROFINET stack with less capabilities to fit in the internal RAM memory of netX52. With netPI we have netX51 with external RAM ... so forget any discussion about V4 stack. It is the same as V3.x but with reduced functionality.
Thx
Armin
netPI is a unit that uses netX51 as underlying network controller. It is the very same thing as if a customer would come to us and want to design-in netX in his own embedded device, but this time it is Hilscher itself making use of their own network controller to build such an embedded device - named netPI.
What I want to say is, if you are a netX customer you have to go through all this documentation here: https://kb.hilscher.com/display/NETX/netX+51. Tons of material needs to be studied and also a workshop is offered that provides much more knowledge than a simple code example can provide. The netX support team welcome you for a workshop at any time to help out.
One word to the single input and output module. Next to the PROFINET example there is EtherCAT, EtherNet/IP, POWERLINK, SERCOS ... da da da. Aim with the examples was to deliver source code that behaves the very same for all networks. There are some network that do not support multiple slots/submodules like PROFINET does ... and hence the decision has been made to find a common denominator by stipping down all the fulminant capabilities to a level that applies to all networks. So now in the end there is just the app.h file to be edited deciding on the IO size and the rest is all hidden and handled in the subordinate network specific files. So the easiest way was to implement the single slot solution in PROFINET here ... while accepting cutting off 90% of the possibilies you really have with netX51.
Another thing I want to mentioned here is that the source code we provide on github is 100% based on the source code we provide to real netX51 customers when they come for a netX workshop.
netX52 chip has no external RAM. The software V4.x is a PROFINET stack with less capabilities to fit in the internal RAM memory of netX52. With netPI we have netX51 with external RAM ... so forget any discussion about V4 stack. It is the same as V3.x but with reduced functionality.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
