Centinel Frequently Asked Questions List (FAQ) Ver.

1v6
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.

Im going out to do my first Centinel install. What do I need to know? ..................................................................... 2

What Centinel Surface Electronics Panel (SEP) do I have?...................................................................................... 2
Whats with the Master / Slave jumper on the front label, it seems to be backwards?.............................................. 3
How do I configure a Centinel Interface Module (CIM) as a CITIBus Slave so it can be integrated with a Vortex or
Electrospeed GCS? ................................................................................................................................................... 3
How do I configure a Centinel Interface Module as a CITIBus Master so it can be operated independently, without
a Vortex or Electrospeed GCS?................................................................................................................................. 3
How do the Centinel Analog Outputs work? .............................................................................................................. 4
How do I configure Analog Outputs to track Centinel Module data if the Centinel is a CITIBus Module? ................ 4
How do I configure USER DEFINED ALARMS for Centinel Data? ........................................................................... 5
How Can I Simulate Changes in Centinel Channel Data to Test Analog Outputs or Setpoint Control (PID)............ 7
The Centinel stand-alone initializes properly and displays data but the Centinel output appears to be stuck at
approximately 15 mA. (Using an outside 4-20 mA source confirms that the ICS drive analog inputs seem to
function properly.) ...................................................................................................................................................... 7
The Centinel stand-alone initializes properly and displays data but the Centinel 4-20 mA outputs do not change
from 0 (3.5mA 4 mA out)......................................................................................................................................... 8
The Centinel stand-alone initializes properly, displays data and the analog outputs from the expansion I/O module
track the Centinel data properly, but the ICS drive analog inputs read 0 or some very small number...................... 8
The Analog Outputs from the Centinel are not accurate. .......................................................................................... 9
When I enter values to calibrate the Expansion I/O module, the numbers revert back to the original or 0. Why
cant I complete the calibration? ................................................................................................................................ 9
Setpoint Control from Centinel Inputs does not function properly ............................................................................. 9
When the drive is stopped, the Centinel Data transfers to the ICS properly. Once the drive is started, the GCS
Display updates are very slow and the ICS Analogs are not reading properly.......................................................... 9
My Centinel in Master mode boots up, I hear relays click 4 times but the power supply level never changes from
100%, then everything stops with no fault annunciation or a Centinel Short Circuit alarm. Any suggestions?...... 10
The Centinel in Master mode boots up and starts working but doesnt seem to recognize the gauge. I hear relays
click 4 times and then everything stops with NO error annunciated. What now?................................................... 10
Why does my User Defined Alarm cause a low threshold shutdown on Centinel pressure even though the reading
is above the threshold? ............................................................................................................................................ 11
Is there any way to annunciate a high or low alarm using a digital output on a Centinel Stand-alone?.................. 11
My Centinel is communicating intermittently. Is there something I can try? ........................................................... 12
How do I check the calibration of my CIM?.............................................................................................................. 12
Is it possible to re-calibrate a CIM module as a stand-alone device: ...................................................................... 12
How can I configure my Centinel to cause a shutdown if the system detects a gauge problem?........................... 13
My Centinel gauge is communicating intermittently, but I want to keep running the well. How do I prevent the
system from shutting down if communication to the gauge is lost?......................................................................... 13
My Centinel temperature is displaying as expected but the pressure is reading 0. Whats the problem? ............. 13
Is it possible to view the results of the auto-ranging process? ................................................................................ 14
We have a GCS Electrospeed that shows invalid input voltage values but only when the Centinel is connected as
a slave GCS device. What is wrong?...................................................................................................................... 14
Weve upgraded a Centinel Interface Module with the new software revision 2.40 and now the Centinel Intake
Pressure displayed 358 bar, while it has to be 35.8 bar. What should we do? ...................................................... 15

Im going out to do my first Centinel install. What do I need to know?

1. Read the Manual.
2. CAUTION: When working with the Centinel with Datalogging Option (see What Centinel Do I Have below)
ensure that that the terminal marked Neutral on the Vortex GCS is the return connection and that 120VAC on the
Vortex is Hot. If these connections are reversed the panel may appear to function properly until an external
ground is introduced to the panel (Connecting the GCS Programmer kit or a laptop serial port). This will result in
a direct short from hot to ground and will damage the Vortex, and most likely the computer or GCS programmer.
3. Ensure that the Centinel surface panel is loaded with the latest matching software versions. Do this before the
panel gets to the field if possible. The latest versions as of this publication are listed below.
CIM: 2.40
Expansion I/O: 1.40
Vortex GCS (Datalogging Option): 8.30
GCS Display: 6.20
4. Review this FAQ, it contains information we have learned to help you deal with application specific issues. (ICS
drive interface, alarm setup, analog configuration etc)

What Centinel Surface Electronics Panel (SEP) do I have?

Any Centinel Surface Electronics Panel (SEP) contains, at a minimum, a Centinel Interface Module (CIM) and a
Centinel Power Supply (CPS 902260). The Block Control Schematic in Appendix B of the manual contains details
about other modules in each panel. In general there are two basic flavors of SEP.
1. Centinel Interface Module (CIM) as a Controller of the CITIBus, where all CITIBus transmissions are initiated
by the CIM.
2. Centinel Interface Module (CIM) as a CITIBus Module, where the CIM responds to requests for data from
some other CITIBus Controller but is not in charge of the CITIBus traffic.
How do you tell the difference?
If there is a GCS Vortex or a GCS Electrospeed on the CITIBus that device will be the CITIBus Controller
and therefore the CIM will be a CITIBus Module (MR/SL Jumper IN).
If there is no Vortex or Electrospeed to take control of the CITIBus, then the CIM will be configured as
a CITIBus Controller (MR/SL Jumper OUT).
As per Appendix B of the Manual, the CIM is a CITIBus Controller in the following part numbers:
902533 - Stand -Alone Surface Electronics Panel
902534 - Stand -Alone SEP with analog output
902822 - Stand -Alone SEP with Centinel 3, analog output
The CIM is a CITIBus Module in the following part numbers:
902536 - Stand-Alone Dataloggable SEP with Analog
902537 - Stand-Alone Dataloggable SEP with Enhanced SCADA (VCI-142)
902823 - Stand-Alone Dataloggable SEP with Centinel 3, Analog Output
902637 - GCS Retrofit Kit
To make a stand-alone SEP Dataloggable or give it SCADA capabilities, a Vortex GCS controller is added to the
SEP to act as the CITIBus Controller, thus the CIM becomes a CITIBus Module and the MR/SL jumper is inserted.

Whats with the Master / Slave jumper on the front label, it seems to be backwards?
The original drawing for the CIM label was Black on White (Left Below). This clearly illustrates that the jumper should be
IN to set the Centinel Interface Module as a Slave. When the production label was made, the colors were reversed (right
below) and as a result the meaning of the jumper gets confusing. Consider that the small circles in both drawings are the
jumper PINS visible through the opening when no jumper is installed.

NOTE: This same issue applies to the CPS config Jumpers. Again consider the circles to be visible pins NOT covered by
a jumper.

How do I configure a Centinel Interface Module (CIM) as a CITIBus Slave so it can be

integrated with a Vortex or Electrospeed GCS?
To set the CIM as a GCS Slave device, complete the following steps (Refer to pictures above and below):
1. Insert the Master / Slave shunt on the front panel.
2. Remove the End Of Line (EOL) shunts on the front panel.
3. Check and remove the fail-safe biasing shunts directly behind the CITIBus connector INSIDE the CIM
module (requires removing the 2 screws on the lid and sliding the CIM circuit board out of its enclosure)

How do I configure a Centinel Interface Module as a CITIBus Master so it can be operated

independently, without a Vortex or Electrospeed GCS?
To set the CIM as a GCS Slave device, complete the
following steps (Refer to pictures above and right):
1. Remove the Master / Slave shunt on the front
panel.
2. Insert the End Of Line (EOL) shunts on the front
panel.
3. If operating in electrically noisy environments,
consider installing the fail-safe biasing shunts
directly behind the CITIBus connector INSIDE
the CIM module (requires removing the 2 screws
on the lid and removing the CIM from its
enclosure)

How do the Centinel Analog Outputs work?

Centinel analog outputs are handled differently depending on whether your Centinel is a CITIBus Controller or
CITIBus Module. (See previous question)
Centinel as a CITIBus Controller
When the Centinel is a CITIBus Controller, it is automatically programmed to send its internal Pressure and
Temperatures to analog outputs IF GCS Expansion I/O modules are connected (as in 902534, 902822).
In this case the output signals will be as per the table on the Centinel Manual page 8.
EIO1, Analog Out 1 = Well Pressure
EIO1, Analog Out 2 = Well Temp
EIO2, Analog Out 1 = Motor Temp (Centinel 3)
Centinel as a CITIBus Module
When the Centinel is a CITIBus Module the information from the Centinel is passed digitally to the GCS Vortex or
GCS Electrospeed. In this case the Centinel data is equivalent to any analog in the GCS system. A GCS Vortex
or Electrospeed system allows any analog value to be sent to an analog output or configured to alarm on a user
defined threshold. Configuring analog outputs and alarms follows the standard for any GCS analog, and is
documented in the GCS Operators Manual. We explain the process specific to Centinel below.

How do I configure Analog Outputs to track Centinel Module data if the Centinel is a CITIBus
Module?
NOTE: This procedure requires 7.20 of System Controller and 5.22 of Graphic Display software.
Select Prog Logic Funct.

Select Analog Output Control

Select an analog output in the system to configure (X1 = Expansion I/O Module 1)

Scroll thru the list (left / right arrow keys) to select the specific Centinel Data for the Analog Output and press
Enter

Example configuration for Centinel 3.

How do I configure USER DEFINED ALARMS for Centinel Data?

To setup a User alarm, go to the bottom right hand corner of the main menu and enter the Prog Logic Funct.
screen.

Then select User Defined alarms

Once you press ENTER, youll see this screen for user alarm 1, inactive.

Press ENTER while the cursor is on DATA SOURCE and youll get this next screen.

Move the cursor to Cntl Mtr Tem and press ENTER to get the next screen.

At this point, pick Alarm Type Hi Thld, then enter your high threshold value, and set the enable/disable and time
delays the same as all other GCS alarms.

How Can I Simulate Changes in Centinel Channel Data to Test Analog Outputs or Setpoint
Control (PID)
The minimum reading of a GCS analog must not be edited. The best way to simulate a range of pressures
or Temperatures from a Centinel to check the scaling of an external device (such as an ICS) is to use the offset
parameters. These are only accessible when you have Field Service Security. This is equivalent to inserting the
code enable jumper on a system control board. Since there is no jumper on the Centinel board, you will need to
create a field service security PC Card and insert that into the display unit. Once the security card has been
recognized, the GCS Centinel setup screen will show additional parameters as illustrated by the before and after
screen shots below.

No Code Key Access

Code Key Access

To make a code key access card, simply create a file called code.kee on a PC Card and the PC Card into the GDI.
The file need not contain any data, so long as it is called code.kee.
Once you have these additional parameters available, use the Pres Offset parameter to experiment with your
pressure reading. It can only be adjusted between -3276.7 and +3276.8, so you cannot simulate a full 5000 PSI if
you have less than 1724 PSI downhole. (5000-3276 = 1724psi). Be aware that the offset values you enter into
these parameters take effect only after the next full reading packet is received from down hole. That means it
could take up to 20 seconds or so for the offset value to be added to the reading. Just be sure to reset those
offsets to zero when you are finished testing.
If you must simulate a full 5000 PSI reading, youll have to use an I/O module that is not slaved to the Centinel
device so that you can manually adjust the output of the 4-20mA. Alternatively, you can use a commercially
available current loop test box that both produces and measures a 4-20mA signal.

The Centinel stand-alone initializes properly and displays data but the Centinel output appears
to be stuck at approximately 15 mA. (Using an outside 4-20 mA source confirms that the ICS
drive analog inputs seem to function properly.)
BOTTOM LINE: Dont mess with the Max & Config or Min Reading parameters.
This is a known software issue described in a recent tech brief (MATB 05-002) that can occur in the following
cases:
a. A Stand-alone Centinel in Datalogging configuration (c/w a Vortex GCS) has had its Analog Output
Source parameters set to Centinel channels and then at some time afterward the 'max and config'
parameter OR the 'minimum reading' parameter has been changed.
b. The Centinel automatically configured the analog outputs at boot-up, but someone has modified the
minimum rdng or the span and config of one of the analog output readings.
In either case the 4-20 mA output calculation is corrupted and the output value can get stuck at one specific value,
typically about 15 mA.

If you find yourself with these symptoms I suggest you try each of the following, in order, testing to see if the issue
is resolved after each step:
a) Check the Modules Status submenu in GCS Modules to ensure the I/O module(s) are enabled. If not,
highlight the module and press the Enter key.
b) Using a Field Service Level PC Card (if available) press the right arrow from the GCS Modules Status
menu to view the CITIBus diagnostics menu. Check the % error rate for communication to the IOM. High
error rates could indicate CITIBus problems.
c) Enter the Contrast Adjust menu and note the CITIBus Rate. This value should be 20 /s or greater. If you
see a value below 10, suspect CITIBus problems or see # 6 below.
d) Re-boot the Centinel system (power down for 10 seconds). This seems to resolve the problem most of
the time.
e) If previous steps didnt work: and IF you have a Centinel with the datalogging option, set the analog
source parameters to a value of <none>, press the enter key, and then set each one back to the specific
Centinel channel (see accompanying FAQ list for details)
f) If you are still not seeing proper analog outputs, I suggest re-loading software in the Centinel Interface
Module (CIM). NOTE the CAUTION above however.

The Centinel stand-alone initializes properly and displays data but the Centinel 4-20 mA
outputs do not change from 0 (3.5mA 4 mA out).
This can occur on a Centinel with datalogging option that has not had its analog output source parameters set
properly. See the previous question about configuring analog outputs.
If the CIM is a CITIBus Master, it could be that the system is still in Factory Calibration Mode. Check the
SYSTEM menu and ensure there is no option labelled Factory Calibration Mode with a setting of YES. If so, set
this parameter to NO, after which the menu option will disappear and the analog outputs should now track the
proper Centinel values.
Another possibility is that the leads from a meter set to milliamp mode were connected directly across the analog
output terminals for testing or calibration purposes. This could have resulted in damage to the analog outputs
from the Expansion I/O Module. (Future revisions of the Exp I/O modules will be immune to this kind of damage).

A final possibility is that the Expansion I/O Module is not functioning or connected properly. Check connections
and refer to the document Troubleshooting CITIBus Problems on the Controls Support Web Site.

The Centinel stand-alone initializes properly, displays data and the analog outputs from the
expansion I/O module track the Centinel data properly, but the ICS drive analog inputs read 0
or some very small number.
During our shop testing we
found that the cabling between
optional boards in the ICS must
be connected as indicated on
the boards to ensure the analog
input signals lines get connected
to the OIB.
For example the Analog Input
board MUST be connected as
indicated on the PCB. The
connector with pins straight out
the top of the board MUST be
connected to the OIB. The right
angle connector with pins off the
side of the board is then
connected to the DCB.
Reversing these connectors may
allow the cables to fit neater, but will not connect the analog inputs to the OIB, resulting in readings of 0 or a few
bits of noise.

If the ICS has a PHD Signal Conditioner installed, this board should be removed when an analog input board or
CIB is installed so that the PHD board does not interfere with the analog signals from the Centinel I/O.

The Analog Outputs from the Centinel are not accurate.

Most likely the expansion I/O module is not properly calibrated. This could have occurred because the IOM was
not calibrated before a software upgrade or when setpoints were not reloaded previously. When loading software
version 1.30 into the IOM, the existing calibration information will be retained assuming it is valid.
Alternately, consider the FAQ below that discusses improper operation while the ICS is running.
We have a procedure for re-calibrating the IOM when it is attached to a Vortex GCS (Centinel Datalogging option)
on the Controls Web Site on the GCS Software page. The IOM calibration procedure with a CIM should be
similar, though we are working on a specific procedure. Generally we would avoid calibrating IOMs in the field
unless you have the proper 4-20 mA meter or unless no spares modules are available. For now, call us if you
have to do this and need help.

When I enter values to calibrate the Expansion I/O module, the numbers revert back to the
original or 0. Why cant I complete the calibration?
We have had reports that after re-loading software calibration values entered would not stay or revert back to 0.
This is likely caused by reloading software in the IOM before reloading software in the GCS Vortex. As a result
the IOM factory calibration mode (wormhole) is closed.
The solution is to reload software in the IOM a second time and then proceed with the calibration procedure.

Setpoint Control from Centinel Inputs does not function properly

This is likely a result of one of the other symptoms listed in this FAQ. Try to determine if your symptoms are
similar to any of the others. If NOT, please contact us.
Note the following known issues with ICS software:
When the lo alarm is set at or below the zero value the drive will accelerate to the low speed clamp
frequency and stay there.
If the controller enters an alarm state, it will lock the output frequency until the alarm goes away or the
drive is stopped. This was to compensate for PHDs that would have some dead spots in their operation
caused by the wiper of the pot loosing contact.

When the drive is stopped, the Centinel Data transfers to the ICS properly. Once the drive is
started, the GCS Display updates are very slow and the ICS Analogs are not reading properly.
This symptom was discovered in our testing but may be responsible for inaccurate readings on the ICS.
It has been discovered that the electrical harmonic noise from a VSD can greatly affect CITIBus communications
under certain situations. Since the CITIBus communication link is a high speed RS-485 system, proper
termination is required on both ends of the bus. If the terminations are not present, the system is more susceptible
to electrical noise.
Make sure that the CITIBus controller has the shunt blocks in for the termination and failsafe bias resistors. The
CITIBus controller can be:
a) a Vortex-GCS motor controller in a dataloggable stand-alone Centinel system (see Figure 1),
b) a Centinel Interface module (CIM) in a non-dataloggable stand-alone Centinel system (see Figure 2),
c) or a System Control board in a dataloggable Centinel system. (There are no shunt blocks for
terminations on this board. Terminations are always present).

The shunt block locations are circled in the diagrams below.

Figure 1 Vortex GCS Shunt Blocks

Figure 2 Centinel Interface Module Shunt Blocks

On a typical CITIBus system with a display unit at the end of the line, the addition of just the two shunt blocks
(termination resistors) provides acceptable communications. For systems without a permanent display, it is
advisable to have all shunt blocks installed.
We also found that adding a ferrite core inductor similar to those used on other cables in the ICS cabinet
improved the situation significantly. The inductor was added to the signal wires between the Exp I/O module
analog output and the Analog Input board. This marked improvement was witnessed when the shunt blocks on
the CITIBus controller boards were not installed.
Note 1: By default, all six (6) shunt blocks are installed for the Vortex GCS motor controller.
Note 2: By default, just the two EOL shunt blocks are installed for the Centinel Interface module. In our test
configuration using an ICS drive, CITIBus communication with the CIM as the controller was solid with or without
a display with just the two shunt blocks providing end-of-line terminations.

My Centinel in Master mode boots up, I hear relays click 4 times but the power supply level
never changes from 100%, then everything stops with no fault annunciation or a Centinel
Short Circuit alarm. Any suggestions?
Depending on the display software version, you may need to reboot the display (see next faq)
Centinel Short Circuit alarm simply indicates that the CIM did not receive any change in signal from the down hole
gauge, thus no data. This could be caused by several factors.
Check the CPS Config jumpers on the CIM and ensure they are installed closest to the Bottom of the module.
Similar to the MR/SL jumper FAQ above, consider the circles in the label to be pins visible and not covered by a
jumper.
Next consult the troubleshooting steps found on page 28 of the Centinel Manual (Rev 1.39)

The Centinel in Master mode boots up and starts working but doesnt seem to recognize the
gauge. I hear relays click 4 times and then everything stops with NO error enunciated. What
now?
There is a known issue with Display software 5.22 when connected to a Centinel Master. In this case the alarm
annunciation is only updated when the display is powered up and will not update after that time. If the Centinel
does not appear to be working and there is no indication of what is wrong, try unplugging the display and plugging
it back into the CITIBus. This will reboot the display without restarting the Centinel and should allow the
Centinel alarm to annunciate properly.

Next consult the troubleshooting steps found on page 28 of the Centinel Manual (Rev 1.39)

Why does my User Defined Alarm cause a low threshold shutdown on Centinel pressure even
though the reading is above the threshold?
During the development of the Centinel there were several changes mad to the spanning capabilities for
parameters and alarm trip calculations. Some parameters are spanned 0-9999, some versions were spanned 32768 to +32767 and the latest versions span Centinel pressure 0 to 65535 for maximum resolution.
GCS products support User Definable Alarms in latest software versions accessed via the User Prog Func menu.
Problems can be encountered when combining older versions of system controller, CIM and IOM software. We
recommend you upgrade all software to the latest available versions as per the first FAQ at the top of this
document.

Is there any way to annunciate a high or low alarm using a digital output on a Centinel Standalone?
If the Centinel stand-alone product has the Datalogging option (comes with a GCS Vortex in the panel) it is
possible to configure a contact closure to indicate a high or low alarm condition. This is made possible by
combining two GCS features: User Alarms, and Digital Output Control.
Two configuration steps are required assuming a working Centinel SEP:
1. Configure a User Alarm with the desired Centinel data as the data source. Set the threshold as high or low,
enable the Alarm and set the desired threshold.

2. Configure the Digital Output Control for the desired digital output. Select the Alarms column and scroll down
to User Alarm configured in #1 (approximately 7 right key presses). Note that the name of the user alarm in
the list of alarms will have changed to the data source name.

The system will change the state of the digital output as soon as the Centinel data exceeds the user alarm
threshold. The shutdown and bypass delays on the user alarm configuration menu are not relevant because the
GCS Vortex is not actually controlling a motor.

My Centinel is communicating intermittently. Is there something I can try?

Centinel software versions 2.00 and previous use an auto-ranging algorithm to determine optimal voltage to the
downhole tool. In certain applications this algorithm could select an output voltage that is right at the minimum
level required for the gauge. This results in the gauge dropping out on an underpower situation intermittently. It
is possible to adjust the power level to the gauge using the following procedure:
1. From the main Menu select GCS Modules then Onboard I/O.
2. press the right arrow key 2 times to change to the Analog Output 1 menu.
3. increment the present value by a few percent monitoring the gauge operation.
One other source of intermittent communication to a downhole tool is an improperly calibrated CIM module. It is
recommended that the calibration information on intermittent units be checked as per the FAQ below.

How do I check the calibration of my CIM?

1. Configure the CIM as a Master (Master/Slave Jumper OUT) and supply it 24 volts.
We can get 24 volts from a CIM Auxiliary Power supply (902455 &
902538). Alternately it is possible to 'steal' power from a GCS Vortex or
Electrospeed by making a special cable that only connects CITIBus power and
ground from these units. +24 is on pins 7&8 of a CITIBus cable and ground is on Pins 3&4. If we take a
standard CITIBus cable and cut the wires to pins 1,2,5 and 6 then there will not be any CITIBus conflicts.
2. Connect a Graphic Display.
3. Insert a Code Key PC Card.
4. Navigate to the System menu and select the Diagnostics sub-menu that now appears
5. In this menu select DAC Lvl:

6. The calibration values for AO1 are on line 4 in the 3rd (min) and 4th (max)
columns. If the max value is 255, the calibration has likely been
corrupted. The other values in this table are not used in the CIM.

Is it possible to re-calibrate a CIM module as a stand-alone device:

1. Configure the CIM as a Master (Master/Slave Jumper OUT) and supply it 24 volts.
o We can get 24 volts from a CIM Auxiliary Power supply (902455 &
902538). Alternately it is possible to 'steal' power from a GCS Vortex or
Electrospeed by making a special cable that only connects CITIBus power
and ground from these units. +24 is on pins 7&8 of a CITIBus cable and
ground is on Pins 3&4. If we take a standard CITIBus cable and cut the
wires to pins 1,2,5 and 6 then there will not be any CITIBus conflicts.

2. Connect a Graphic Display.

3. Re-load CIM software version 2.20 or newer.
4. With power disconnected, connect a 4-20 mA measurement device or a 100 ohm resistor with a voltmeter to
measure Analog output1.

5. Power up the system and use the standard Factory Calibration menu on the System menu to view the Analog
Output 1 calibration menu

Select Enter, Press right arrow twice

6. Set a value in the A01 Raw parameter that causes the output to read 4 mA. Typically this is a value of 7 or 8.
7. Enter the Raw value that produced 4 mA out into the Minimum Value parameter.
8. Adjust the A01 Raw value again to produce a value of 20 mA output. Typically in the range of 187 to 220.
9. Enter the Raw value that produced 20 mA output into the Maximum Value parameter.
10. These steps should be repeated for analog output 2 (one right key press).
11. Once the 4 values are entered, go back to the System menu and set Factory Calibration to NO.

NOTE: The CIM will not start it's auto-ranging algorithm unless the Enable Cal parameter is set to no.

How can I configure my Centinel to cause a shutdown if the system detects a gauge problem?
My Centinel gauge is communicating intermittently, but I want to keep running the well. How
do I prevent the system from shutting down if communication to the gauge is lost?
The parameter on the Centinel Setup menu labelled Centinel Receiver Com Alarm controls whether the system
will cause a shutdown if the CIM looses communication with the downhole gauge. If this parameter is set to NO,
the system will annunciate the alarm condition in the alarm window but will not shut the well down or prevent it
from being started.

My Centinel temperature is displaying as expected but the pressure is reading 0. Whats the
problem?
This is a known issue with version 2.00 of Centinel software that occurs when the pressure reading is greater than
3276.7. In this case the data actually overflows a signed data type and is negative. As a result the system forced
the value to 0.
This has been fixed in Centinel software version 2.20.

Is it possible to view the results of the auto-ranging process?

There is one CIM troubleshooting capability that may not be widely known. The CIM automatically ranges the
output voltage to achieve the optimum signal strength from the downhole gauge. This is completed by setting the
output voltage in 12.5% increments and measuring the maximum and minimum signal at each output level. Then
the level where the largest difference between max & min is noted selected for operation.
It is possible to view the data collected for signal strength in the auto ranging process using the following steps:
1. The CIM must be in MASTER mode. Jumper OUT.
2. Insert a Code Key PC Card (a PC Card with a code.kee file on it)
3. From the main menu, select Status to view the Centinel Status menu.

4. Position the cursor over the Intake Pressure parameter and press ENTER to display the calibration menu

The calibration shows the min and max values read at the analog input (signal from Centinel gauge) for each
output voltage level (DAC ranges from min calibration value to max calibration value, thus 4-20 mA.
In the example above the table has been initialized to maximum and minimum values but since NO gauge was
connected, the system never detected any signal from the CIM and never even tried to auto-range.
If the gauge was ever detected, the values in this table should be in the range of 300 to 1000 counts. The
difference between the min an max values at each DAC Level (output voltage level) is the strength of the
signal. The DAC level of 14 above represents and output of 12%, the 40 is 25% etc up to 222 which represents
100% power supply output.
Looking at this table may give us some additional information about why the re-initializers do what they do. It may
also provide more clues to some of the non-working Centinels.

We have a GCS Electrospeed that shows invalid input voltage values but only when the
Centinel is connected as a slave GCS device. What is wrong?
This is a known issue with CIM software version 2.20. When the CIM is used as a CITIBus slave along with an
I/O module in an Electrospeed or Electrostart switchboard the CIM responds with invalid data which overwrites
analogs in the system controller. You may also notice that the system controller will report that an RDCM module
has been noted on the CITIBus. (GCS Modules -> Modules Status).

The solution to this issue is to update to version 2.40 of CIM software. Also, unless there really is an RDCM in
the system, navigate to the GCS Modules-> Modules Status menu and disable the RDCM so the system does not
waste time trying to communicate with a module that is not in the system.

Weve upgraded a Centinel Interface Module with the new software revision 2.40 and now the
Centinel Intake Pressure displayed 358 bar, while it has to be 35.8 bar. What should we do?
The work-around is to change the Centinel Unit setting (basic setup menu) from SI to IMP. Wait for a while and
set it back to SI. This should correct the decimal problem.