General Information
The core functionality of the Well Test application is to configure Realflo for a specific set of gas and liquid product types before starting a test. This functionality allows the same measurement path can be used to accurately measure flow from a number of different wells, each of which has a unique product type.
The Well Test application implements 3 independent testing loops. Each loop has its own configuration, its own set of Status Parameters and its own Control Parameters.
Program Execution
The Well Test application waits until a specific well test is started. The user can select a specific test from all of the available tests, and then start a test. When a test is started, the Well Test application retrieves the desired gas and liquid configuration from the application's memory and pushes the configuration to Realflo.
Configuring Realflo takes multiple steps. For each configuration change, the complete current configuration must first be read from Realfo and then copied to the desired configuration registers. Then the new values that are changing are loaded into the desired configuration registers and a command is sent to Realfo. After that, the Well Test application verifies that Realfo accepted the configuration change and that there were no errors before moving onto the next set of configuration changes.
An error code from Realflo during this process results in the test being stopped and an entry being made in the application's diagnostic log. The log entry will contain the error codes from Realfo. These codes are described in the Realflo Reference Manual, and can be used to pinpoint the problem that occured.
If no errors occur during the configuration of Realflo, the Well Test application moves to the Purge state. In this state, flow is accumulated until the purge volume for each enabled run (gas, liquid or water) is exceeded. The time spent in this state is dependent on the flow rate, and can take a variable amount of time.
Once the purge state is complete, the Well Test application starts the configured Realflo batch and moves to the Test state. The application will stay in the Test state for a user configured amount of time. When the test is complete, the Realflo batch will be stopped and the Well Test application will move to the Accept or Reject state.
In the Accept or Reject state, the user has the ability to accept or reject the completed test. Accepting or rejected a test does not affect Realflo's history or batch history in any way. It simply provides a record of whether a test was accepted or rejected. This record can be aligned with the batch history to see which batches are good and which ones should not be used.
Realflo's batch history contains the test result.
Once a test is accepted or rejected, the Well Test application will move back to the waiting state. At this time, a user can select another well to test, and issue another Start command.
If a separator is not licensed, then the Start command will not be accepted. When this occurs, an entry will be made in the application's diagnostic log.
A Stop command can be issued at any time during the well testing process. If the Stop command is issued in the states before the batch is started (Configure and Purge states), then the Well Test application will go back to waiting for another start command. If a Stop command is received after the batch is started, in the Test state, then the Well Test application will immediately move to the Accept or Reject test state. The Stop command has no affect in the Accept or Reject state.
The Well Test application executes once every 5 seconds. A complete configuration or Realfo can take up to 90 seconds (1.5 minutes). Note that only one test can configure Realflo at one time. That means that if a test is started, and then another test is started immediately afterwards, the second test will have to wait until the first test is done working with Realflo until it can start configuring Realflo. This is indicated when a test is in the Waiting for Realflo state, as indicated by the appropriate Test State status parameter.
