I have some problem with location 2 configuration, included:
- when I put any value on the location 2, sometimes it makes the interface down and we must restart the foxapi then
- when I put any value on the location 2, sometimes the value appear but it was not the right value untill I put 0 value on it

Any advice what could be the problem of this?
And also I was wondering where do we configure the location 2 for the interface?

many thanks for your help.

OSIsoft vCampus is a subscription-based, online offering that consists of providing everything people need to develop applications on the PI System.
We invite you to take a "tour" of the OSIsoft Virtual Campus - also feel free to consult the FAQ  or contact OSIsoft vCampus for more details.

Hi Maria,

Assuming you're using the Foxboro I/A 51 and 70 Series Interface to the PI System then (from the manual)

'The Location2 attribute determines whether the Interface adds the point to a FoxAPI data set and retrieves “buffered” values from the FoxAPI. Buffered values are those updated by the FoxAPI in the system-shared memory. Unbuffered access to I/A objects makes requests to the Foxboro CP for each data retrieval call. OSIsoft recommends the use of buffered access to reduce the load on the Foxboro system.

The value of Location2 is the PI list number. Set the value of Location2 to a positive number to indicate that PI-Foxboro should use buffered access to retrieve I/A data. For tags with a common value of Location2, the Interface groups these tags into a list for use with the FoxAPI scopen() call. This FoxAPI function returns a unique data set number, which may be different than the Location2 value.

Tags for read values must be in a PI list that is separate from those tags for write values. Tags referencing I/A objects from different Foxboro CP modules must also be in different PI lists.

Some customers have experienced performance problems when there are many (~250) tags in a PI List. So, you may want to keep the size of a PI List within this number.'

Regards,

Burnikell1

Maria,

Location2=0 means you want unbuffered access and Location2>0 means buffered access. When Location2>0, the interface tries to create a list of the tags with common Location2 values in the FoxAPI shared memory. Some thoughts:

-Have you confirmed that the version of FoxAPI is compatible with the version of the interface you're using?
-Have you tried to enter a 3-digit location2 value, for example "111" or "123" etc.?
-Location2=4 seems to be reserved for string tags, if you have used 4 consider changing it...
-Does the interface have full access to create its list (using the FoxAPI command SCOPEN() ) ... is the interface being run as an Administrator user? From the interface manual:
"For Windows systems, the interface service must be started with an account that has local administrator rights, and so we recommend the standard Foxboro user “fox”. "
-From the interface manual:
"Confirm the correct operation of the FoxAPI. Run Foxboro’s foxtst program. When using netFoxAPI, make sure that the netFoxAPI client machine (the machine running the Interface) has permission to create, name, and read objects on the netFoxAPI server machine."

Those are some initial thoughts...
Hope that helps
Douglas

Hi Maria,

Glad you got your issue resolved.
Many thanks for sharing your solution with everyone!

Rhys.