July-16th-2018, 11:49 AM
Here the exact explanation: if you dig into all details about netPI's Ethernet based firmware you will detect that we are providing it as a PROFINET IO device/Ethernet combo firmware where just the PROFINET part is disabled/remaining unused.
The combo firmware consumes so much RAM space that it can run on netX51 controllers only using external RAM like it is populated on netPI. netHAT has a netX52 controller only that can't connect to external RAM, so this combo firmware will never get running on netHAT from the physical point of view ... and now comes the point: there is no alternative, we never developed an Ethernet only firmware that could consume less RAM. So for you the netHAT will remain unusable for your kind of application.
But buy a netPI at amazon and if it doesn't work for you and your application just send it back. But before I would containerize the POWERLINK thing on your Raspberry to be able to run it on netPI with zero effort later.
The combo firmware consumes so much RAM space that it can run on netX51 controllers only using external RAM like it is populated on netPI. netHAT has a netX52 controller only that can't connect to external RAM, so this combo firmware will never get running on netHAT from the physical point of view ... and now comes the point: there is no alternative, we never developed an Ethernet only firmware that could consume less RAM. So for you the netHAT will remain unusable for your kind of application.
But buy a netPI at amazon and if it doesn't work for you and your application just send it back. But before I would containerize the POWERLINK thing on your Raspberry to be able to run it on netPI with zero effort later.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
