2 of 2 people found this helpful
I would check the SDK Logs for more information on the interface node. You can access the logs using the command line application pigetmsg.exe located in %pihome%/adm or %pihome64%/adm (%piserver%/adm if this is a PI Data Archive node). For example, type:
cd /d %pihome%/adm
pigetmsg -f >SDKLogs.txt
This will output all current logs to SDKLogs.txt in %pihome%/adm.
Restart your interface and wait for your PI Points to update.
Stop pigetmsg by typing CTRL+C in the command prompt.
If this doesn't help, the next step would be to set some debugging on the interface.
Hope this helps,
Thanks for the response. The SDK logs did indicate that the points were timing out. After further digging into this issue, it was found that there were limitations with the serial connections between the MOXA converters and the Ethernet off-boarding device that the interface is connecting to. So basically, we were sampling at a higher rate than the the components were capable. After adding a second interface and updating scan classes, we are getting values for all the point now.