Skip to main content
How Can We Help?

Search for answers or browse our knowledge base.

XSPOC Database Tables Related to Totalflow Communication

Created On
byAndrew Binning
You are here:
< Back

tblPOCTypes
tblNodeMaster
tblPortMaster
tblSystemParameters
EFMLogVerbosity

  1. “Error” logs only errors to the file.
  2. “Warn” logs errors and warnings. Warnings may or may not be a problem
  3. that needs fixing. This is a good default setting.
  4. “Info” logs errors, warnings, and informational messages to document
  5. progress in EFM device communications.
  6. “Debug” logs errors, warnings, information, and debugging messages used to help determine if a problem is happening and what it is. This should only be used when trying to diagnose a specific problem.
  7. “Trace” logs errors, warnings, information, debug, and trace messages. These messages can be long, frequent and include lots of details. Like every byte going out and coming back is included in the trace log. This should only be used when trying to diagnose a specific problem.

EFMTrendTransactionsToPerform

  • 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.

  • The program uses the LogPeriod and FileSize to calculate the total hours of data stored in the Totalflow device. It then divides this up into 48 Blocks.

EFMTrendTransactionsToPerform

  • 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 EFMCollectTrendData.

tblLACTBatchLogs
tblEFMDailyRecords
tblEFMEventCodes
tblEFMEventRecords
tblEFMHourlyRecords
tblParameters

  1. Fisher ROC “Tag” – ‘ROCTLP:91.0.11’ This is the tag for Type 91, Logical 0, Parameter 11. Which is the “Maximum Meter Runs” for the ROC 800 device.
  2. Fisher ROC Gas Orifice “Tag” – ‘ROCTLP:112.L.55’ is the tag for Type 112, Logical for the meter, Parameter 55. Which is the “Flow Today” for the specific GasOrifice Meter it is being stored for.
  3. Totalflow ‘Tag” – ‘TfReg:0.10.2’ This is the tag for App 0, Array 10, Index 2. Which is the “Radio Voltage” for a Totalflow G4 device.
  4. Totalflow Gas Orifice “Tag” – ‘TfReg:app.7.7’ This is the tag for the current meter, Array 7, Index 7. Which is the “Todays Contract day Volume” for the specific Gas Orifice meter it is being stored for.

tblSchedule
DoScan
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
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.

EFMCollectCustodyTransferData
Setup this task in the tblSchedule to collect the custody transfer data from all of the EFM devices in the system. This should be done before the “Contract” hour and again after the contract hour. This will keep the communication requirements after the contract hour at a minimum.

EFMExportToFlowCal
Setup this task in the tblSchedule to create the Flow-Cal export files for each meter for each day. This task should happen after the start of a new “Contract” day and after the Custody Transfer Data has been collected for the completed day.

LACTBatchLogTask
Setup this task in the tblSchedule to collect all LACT Batch Log entries for all of the Totalflow LACT devices on the system. New logs will be collected from the deviceds and saved in the XSPOC database.

tblTotalflowTrendConfigurations

  1. MasterNodeID = The NodeID of the Totalflow Master Device being collected.
  2. TrendFileName = The name the Totalflow uses to refer to a specific trend file.
  3. ScheduledScanEnabled = Set to True to cause this trend file to be collected by the CollectEFMTrendData scheduled task. False will cause this trend file to be not collected.
  4. OnDemandScanEnabled = Set to True to cause the XSPOC Client to show the “Receive Trend” button on the History Graph for this Device. When the button is pressed, the Trend Files will be collected that have this field set to True. Setting this False will cause this trend file to not be collected “On Demand” and if all trend files are “False” then the button will not appear in the XSPOC Client application.
  5. LastSavedDateTime = the date and time of the last saved data from this trend file.
  6. CurrentTransactionCounter = 0 means trend collection is up-to-date, any other number is the counter for times this Master’s trend data collection has been re- queued and this is the trend file that will be started with when it restarts. This number will count up to the “EFMTrendTransactionsToPerform” and then will be reset to 0.
  7. NumberOfVariables = the number of parameters that are included in this trend file.
  8. LogPeriod = the number of seconds between each data collected in this trend file. 1 seems to be event related data collection.
  9. FileSize = the size of this trend file in the Totalflow
  10. RecordSize = the size of each trend file record in the Totalflow
  11. TrendDescription = a second description for each trend file from the Totalflow
  12. CollectionStatus = Statement of the status from the last time this trend file was communicated with. “Finished this trend file.” Means the data collection for this file completed normally.

Use the browse button to navigate to a location of your choosing and then create a folder. Once it is created it will store the Flowcal reports in that created location.

tblSystemParameters

  1.  txtDailyExportPath The scheduled task, EFMExportToFlowCalTask uses this parameter to get the path string to use for exporting the .CFX files into.
  2.  txtDemandExportPath The Client Application’s On Demand EFM ExportToFlowCal task uses this parameter to get the path string to use for exporting the .CFX files into.