When the unit starts blinking the status LED 18 times, it indicates that a fault occured. At this point the processor is halted. To reboot it, a power cycle is necessary. You can configure the RT Watchdog so that the unit resets itself if necessary.
The key here is after downloading the VIs, you only have only 384k of RAM left. As your program runs and uses more memory, you eventually run out causing the GPF. The fact that the crash is in the Logos thread may indicate that a new computer attempted to connect with the FieldPoint module, and when the FieldPoint module attempted to allocate the memory for the new link, there was none availble thus causing the crash.
Looking at your VI, it is extremely heavy in its use of local variabl
es (100 local reads, 26 local writes accoring to VI Metrics). Every local read creates an extra copy of the data in memory. Likewise, having build array functions inside of loops is not memory efficient and is generally not good coding techniques especially on RT Targets.
As a fairly simple way to save on allocating a fair portion of memory. Change the way you display the Channel Names. Instead of displaying all of the channel names for all of the modules. Have a Configuration View Tab which gives a user a choice of which module to view and load the information for that module when the user selects the data. When the user selects a different module, perform the query (Get Item List) a second time and place the data in the same indicator. I have attached an example showing this method.
Regards,
Aaron
LabVIEW Champion, CLA, CPI
