THe UFL interface is tha last resort interface to pump data into the PI Data Archive. AS with all things in it land, this can go wrong…
Debugging:
In the UFL interface’s INI file you can up the debug level.
set the DEB to 4.
[SETTING]
‘ Debug Levels
‘0 (Default) No debug output.
‘1 Tasks that are normally performed once, such as startup and shutdown messages, points added to the interface’s cache, etc.
‘2 More detail than level 1.
‘3 Include raw data.
‘4 Include data about to be sent to PI Server.
‘5 Include read scan cycles start and end time, interface internal cache refresh cycles starts and ends times, etc.
‘6 Log lines read from input before processing.
DEB=4
MSGINERROR=E:\Logs\interfaces\Interface_error.txt
OUTPUT=E:\Logs\interfaces\Interface_log.txt
And start a buftrace on the pipoint causing trouble. To determine the pipoint, use pi point builder in SMT, look for you poit, go to the system tab and write down the pipointid. Then execute this command to start a trace on that point.
C:\Program Files\PIPC\bin>pibufss.exe -trace 8703 >> c:\temp\PiTracePID8703.log
This will write buffer events on pipoint 8703 to the temp folder in a logfile.