Skip to main content
How Can We Help?

Search for answers or browse our knowledge base.

PCSF Device Communication

Created On
byAndrew Binning
You are here:
< Back

XSPOC Server Applications

DoScan

                i.         Setup this task in the tblSchedule for each Port that you need to scan. The data will be collected from the devices at the frequency that the task runs.

DoSetpointScan

                i.         Setup this task in the tblSchedule for each Port that you want to collect setpoint data from it’s devices. This data is normally not changed often and possibly only collected once per day.

PCSFCollectTrendDataTask

i.         The PCSF device can log it’s own trend datapoints at the frequency that is setup in the PCSF. Setup this task in the tblSchedule to collect all of the trend files from all of the PCSF devices on the system. There are multiple settings to control how much time this task is allowed to tie up the communication port.

                i.         Devices Supported:

1.     During Data collection all data is collected from one of the PCSF Master Controllers. AutoLift Master (POCType 71), MultiWell Master (POCType 73), and the GasLiftMaster (POCType 218).

2.     After the data is collected it may be saved under the Controller or if it relates so a specific well, it is saved under the individual PCS Slave Controller for that well. AutoLift Slave (POCType 72), MultiWell Slave (POCType 74), and the GasLift Slave (POCType 219).

              ii.         Steps prior to Starting

1.     Setup and configure the PCSFMaster Device to have trend data collected from.

2.     Confirm proper communication of this device and perform the initial scan. Create any required Slave Devices and also perform the initial data scan on them.

             iii.         Steps to perform initial Setup

1.     Confirm the tblSchedule entry:

a.     EventName = “PCSFCollectTrendDataTask”

b.     PortID = “100”

c.     Enabled = “True”

d.     Interval = number of seconds between collecting each trend data collection.

                            I.      THE VALUE YOU SELECT WILL DEPEND ON HOW MUCH DATA YOU ARE COLLECTING AND HOW YOU WANT TO USE IT.

                           II.      THE INTERVAL CAN BE SET SOMEWHERE BETWEEN 2 HOURS (7200 SECONDS) AND 9 HOURS (32767 SECONDS)

e.     StartAt = hour and minute to start at if you set the interval to 0. Note: setting up one or two daily scans at specific times is also a possibility.

             iv.         Steps to Configure

1.     Setup the tblSystemParameters entries:

a.     PCSFLogVerbosity = “Warn” for normal system operation. You will change this to “Debug” when confirming proper operation and trouble shooting potential problems. “Trace” would be used mostly for troubleshooting communications questions or if Debug does not show what is needed to diagnose the problem. Note: always remember to put this back to “Warn” when finished troubleshooting. The more verbose logging will cause the file to not include a long enough period of time and has too much information to be able to check for problems. This value can be changed anytime and does not require a restart.

b.     PCSFTrendBlocksToReadPerTransaction = Number of blocks to read per transaction. This sets the length of time that the port is tied up without allowing other transactions to be processed.

c.     PCSFTrendTransactionsToPerform = number of times this trend collection will be re-queued. Once this is reached, the System will stop collecting this Device’s trend until the next Scheduled PCSFCollectTrendDataTask.

              v.         Initial Data Collection

1.     As the system collects data for each PCSF Master NodeID, it will create an entry in the ttblPCSFDatalogConfigurations table for each Datalog in the Master Device and will mark each Datalog’s ScheduledScanEnabled = True and OnDemandScanEnabled = True.

2.     This means that data will be collected on the initial data collection scan. Also it means that you must turn off the ScheduledScanEnabled in order to have this Datalog not collected on a Scheduled Scan, and the OnDemandScanEnabled in order to have the “Receive Trend” button not available on the XSPOC Client application to request this datalog to be collected “On Demand”

3.     For the PCSF 8000 master devices, the DatalogName and the Field Names are loaded into this table from the device. For the PCSF 4000 master device you must enter the DatalogName and the Field Names into this table manually.

             vi.         Ongoing Data Collection

1.     The following useful fields are available in the table “tblPCSFDatalogConfigurations”

a.     NodeID = The NodeID of the PCSF Master Controller being collected.

b.     DatalogNumber = Number identification of each enabled Datalog. These are from 1 to 56.

c.     ScheduledScanEnabled = True to collect this datalog each scheduled scan, False to not collect on scheduled scan.

d.     OnDemandScanEnabled = True to allow the XSPOC Client to display the “Receive Trend” button. When the button is pressed, all Datalogs with “True” in this field will be collected. False to not collect this datalog when the “Receive Trend” button is pressed and if all Datalogs are False then do not make the button available.

e.     LastSavedIndex = Index of the most recent data saved for this Datalog.

f.      LastSavedDateTime = Date and time of the most recent data saved for this Datalog.

g.     CurrentTransactionCounter = 0 means trend collection is up-to-date, any other number is the counter for times this Master Controller’s Trend data collection has been re-queued and this is the datalog that will be started with when it restarts. This number will count up to the “PCSFTrendTransactionsToPerform” and then will be reset to 0.

h.     IndexOfNewestRecord = The index of the newest record in the controller. If the LastSavedIndex is not this, then the data is not completely collected.

i.      IndexOfOldestRector = The index of the oldest record in the controller.

j.      NumberOfRecords = then number of trend records in the controller for this Datalog.

k.     MaximumNumberOfRecords = The size of this Datalog when it is full.

l.      Field2IsWellID = True if the second Field is the WellID. False if not. Data will be saved for the specific Well NodeID if this is True and if the NodeID exists for that well Number.

m.   NumberOfFields = number of the possible 12 fields that are being used.

n.     IntervalMinutes = Number of minutes between data samples for this Datalog.

2.     The actual data is saved in the tblPCSFDatalogRecords

a.     NodeID = Master or Slave NodeID for this datapoint.

b.     DatalogNumer = Datalog that the data came from. This is used to match the field names to the field values.

c.     LogDateTime = The date and time of each data sample. (Value 1)

d.     RecordIndex = the Index of each data sample. Mostly useful for troubleshooting.

e.     Value 2 – Value 12 = data values.