Simulation of Powerlink Devices

[Armin@netPI]

Question 1:
"netPI is not fast enough ... ": this is not a root cause of netPI ... it is a root cause of Linux and the included Linux SPI driver (not coming from Hilscher) which is "slow" and has a jitter.
Question 2:
"Hardware modifications ..." not possible, since on netSHIELD the signal line going to pin 24 is hardware in the schematics of the PCBA.
Question 3:
"Faster with nucleo ..." I don't know nucleo baord ... still the communication goes across SPI and this is the limiting factor.
Question 4:
"Cycles ..." ... the memory of netX is read/written in a request/response manner. So application wants to read input puffer and sends request. Then the driver get in indication that the request has been accepted. Then the netX aquires the data and give response. Then the application gets an indication that data is available and request for the data. So overall at least 4 cycles until the input puffer data is in the application. The same number is needed when data is written to netX buffer. So overall at least 8 cycles.
Question 5:
"Frequency ..." the used frequency on netPI/netHAT is 25Mhz today.

Thx
Armin