Is it possible to get more than 255 loops using the looping command? Can the user nest
loop? What is the best strategy to achieve an interface stress test where the user
read/write from/to several locations thousands of times per second, and want to check
for NACKs or Parity errors and maybe data errors?
The LoopCount parameter in the GUI is currently capped to a maximum value of 255 only. For use cases where the user would like to loop a command more than 255 times, we have provided API support on the PGY-I3CEX-PD using Python and C++. The user can perform an iteration of multiple READ/WRITE commands thousands of times and also check for NACK, Parity Errors, and Data Errors by either generating a report in .CSV format or using some of our functions like GetResults() in API which allows the user to get an idea of the last transaction that occurred on the line.
The LoopCount parameter in the GUI is currently capped to a maximum value of 255 only. For use cases where the user would like to loop a command more than 255 times, we have provided API support on the PGY-I3CEX-PD using Python and C++. The user can perform an iteration of multiple READ/WRITE commands thousands of times and also check for NACK, Parity Errors, and Data Errors by either generating a report in .CSV format or using some of our functions like GetResults() in API which allows the user to get an idea of the last transaction that occurred on the line.
