11-13-2018, 02:26 PM
We have a customer that has received this error on an NC5 system. This error is not one of ours so it must have been generated internal to the HMI/PComServer. Any information on source and corrective actions would be greatly appreciated.