AnsweredAssumed Answered

Foxboro AIM*OPC fills up strings with blanks

Question asked by mgrein on Oct 19, 2015
Latest reply on Oct 26, 2015 by jrueda


We have just converted a number of Foxboro I/A fxbais interfaces over to their AIM*OPC server (v2010?).


As of then, all the string type tags do not only contain the expected information we had before the change,

but rather they are filled up with trailing blanks to a total length of 80, which causes all sorts of issues downstream.

Q: Is this something we can overcome/handle on the OPC DA interface side?
Or: Does anyone know how to manage this on the Foxboro side?

I had a look at all the available settings for both parties, but did not find anything.


Thanks a lot in advance!!