This document contains proprietary information and is not intended for public distribution. Pason
Systems and all other trademarks and trade names used in this document, unless otherwise
specified, are the property of Pason Systems Corp.
No part of this document may be reproduced by any means, nor transmitted, nor translated, nor
translated into computer language, in whole or in part, without written permission from Pason
Systems Corp.
As updates and modifications occur, a new document will be made available as appropriate.
The revision date on the title page determines the most current version of the document.
Documents with the latest date replace any and all previous versions of the same document.
The most current is definitive in case of contradictions, errors, omissions, or misstatements.
While all reasonable care has been taken in the preparation of this document, no liability is
accepted by the author(s) for any errors, omissions or misstatements it may contain, or for any
loss or damage, howsoever occasioned, to any person relying on any statement or omission in
this document.
Figure 13: Changing a custom WITS code used for sending ..................................................................... 28
Figure 14: WITS in All tab ........................................................................................................................... 30
WITS communication requires a physical connection between Pason and third-party
systems. This section includes information about how to complete the required hardware
connections.
3.1 Connection Instructions for Third-Party Users
Third parties can connect their systems to Pason’s using one of these three methods:
• Connect to a Pason Workstation computer (TPC and VSP systems).
• Connect to the toolpush connection box (TPC systems) or network panel
(VSP systems).
•Connect to a Pason Doghouse Computer (DHC), SideKick, or Universal
Junction Box (UJB) (TPC and VSP systems).
Important:
Pason only supports the three above methods to connect WITS devices to our system.
Specifically, note that the RS-232 ports on trailer access points (TAPs) do not support WITS
connections. WITS connections to TAPs haven’t been fully tested and their reliability is unknown.
Connecting a WITS device to a DHC or SideKick can in some cases adversely affect wireless
communications between the DHC and the network.
All of the parts and cables described in the following connection procedures are
available for purchase from your Pason representative.
Once third parties connect their hardware, Pason recommends that a Pason field
technician inspect the connections and complete the initial WITS set up in the EDR.
Connecting a WITS Device via a Pason Workstation
Connecting a WITS device via a Pason Workstation is the most common connection
method. Follow these steps to connect a WITS device to the EDR via a Pason
Workstation:
1. Ensure that the Pason Workstation is powered on.
2. Use a Pason Send to Hub cable (CBLASS155), or a generic DB9 9-pin serial null
modem cable, to connect the WITS device to comm port 1 on the Pason
Figure 1: Connecting a WITS device to a Pason Workstation
Connecting a WITS Device via the Toolpush Connection Box or Network Panel
using a COMM022
This method involves using an RS-232 to RS-422 communication box (COMM022) to
connect the WITS device. Toolpush connection boxes and network panels are typically
located on an outside wall of the rig manager’s trailer. Look over the illustrations below
to see the connections to the different types of panels. Figure 4 on page 11 shows a
COMM022 in more detail.
Note:
Pason COMM022 communication (comm) boxes ship with full duplex communication enabled.
COMM022 comm boxes have a jumper that enables you to choose half or full duplex, but Pason
recommends using the default full duplex setting.
Figure 2: Connecting a WITS device to a toolpush connection box
If connecting to a SideKick, ensure that the port you’re using is set to Auto (Port Info >
Port Setup from the SideKick’s main screen). If connecting to a UJB, ensure the port is
set to WITS (Setup Ports > Change to WITS from the UJB local interface). This requires
UJB firware version 11 or higher.
Figure 6: Connecting a WITS device to a DHC, SideKick, or UJB
3.2 Testing WITS Connections
If you are having problems with WITS communication, a Pason field technician can test
WITS connections using the proprietary Pason WITS RSVP application. For help testing
your WITS connections, contact Pason Technical Support at 1-877-255-3158.
After connecting the hardware, you need to use the EDR to set up WITS communication.
Set up procedures vary depending on whether you connected the WITS device to the
EDR via a comm box or via a Workstation, DHC, or SideKick. The following sections
describe the required procedures.
4.1 Set up on UJB
If connecting to a UJB, ensure the port is set to WITS. This requires UJB firmware
version 11 or higher. Select Setup Ports > Change to WITS from the UJB local
interface. Then select either WITS 9600 or WITS 19200.
4.2 About Handshaking
Setting up and maintaining WITS communication between a WITS device and the EDR
requires the use of a handshake. The handshake is important because it prompts the
EDR to recognize that a WITS device has been connected to the system, and is
necessary for the EDR to keep WITS communication active. If you connected the WITS
device via a toolpush connection box or a network panel, handshaking also prompts the
EDR to display a WITS protocol in the Comm Port Setup screen, so handshaking is
useful for determining which ports are connected to WITS devices.
Important:
Failure to continuously send at least one packet to the EDR every 30 seconds causes the EDR’s
communication engine to time out, stopping WITS communication. This is a major cause of WITS
communication problems.
Establishing and Maintaining WITS Communication
To establish and maintain WITS communication with the EDR, the third-party WITS
device must send at least one WITS packet to the EDR continuously every 30 seconds,
even if the third-party has no other need to send WITS packets. The only exception to
this requirement is when the WITS device is connected via a toolpush connection box or
a network panel, and the EDR comm port is set to Send Only. This requirement can be
met in one of the following two ways:
• The third-party WITS device continuously sends at least one WITS packet to the
EDR every 30 seconds as part of the desired operation, or
second. To change the transmission speed, select a protocol that uses the desired
speed.
Important:
High speed settings are a major cause of WITS transmission errors. For WITS, Pason
recommends using a speed of 9600 bits per second. If you experience errors when using WITS,
try decreasing the transmission speed.
Follow the steps below to configure the assigned WITS comm port protocol if you
connected the WITS device to the TPC via a COMM022:
1. From the EDR main screen click Menu > Setup > Comm Ports. The Comm Port
Setup screen opens.
2. Select the assigned comm port and use the ToggleNext button to scroll through
the list of available protocols until the desired protocol is listed under Configured
Protocol.
3. Click Exit to save the settings.
4.4 Setting the Send/Receive Mode
How you connect the WITS device to the Pason system determines which Send/Receive
options are available.
Send/Receive Options for WITS Connections to a DHC, Workstation, SideKick, or
UJB
DHC, Workstation, SideKick, and UJB hardware is hard-coded to send and receive, so
you cannot use send only mode or receive only mode when you connect to a WITS
device via these devices. With these setups, the handshaking procedure on page 14
instructs the EDR how to communicate with the WITS device.
Send/Receive Options for WITS Connections via Toolpush Connection Box or
Network Panel
If you connected the WITS device to one of these panels with a COMM022, you can set
the EDR to send WITS data, to receive WITS data, or to send and receive WITS data.
Once you have connected to the TPC via a comm box and have established a
handshake as described in Establishing and Maintaining WITS Communication on page
14, follow the procedure below to set up whether the EDR sends, receives, or sends and
receives WITS data through the assigned comm port:
1. From the EDR main screen on the RMPC, click Menu > Setup > Comm Ports.
The transmission and interval settings you select are applied to all
the WITS codes in a record group.
Important:
For WITS devices connected to a toolpush connection box or
network panel, conflicts between transmission settings and the
EDR’s comm port settings can cause problems. For example, if
you select Request-Response, but the comm port is set to Send
Only, then the EDR will fail to receive the third party’s data, and it
will not respond.
Unit Use this drop-down to select the display units for the WITS value.
Data Summary Use this drop-down list to select how the EDR calculates the WITS
value.
Import and Export See Sending Gamma and Gamma Lag Calc
When sending Gamma (code 0824) and Gamma Lag
Calc (code 0821) data to the EDR, make sure you
meet these packet and frequency requirements:
•Send both codes in the same WITS
packet. Problems occur when Pason
receives one or the other, but not both.
•Send the packet at a minimum 0.2 m (1 ft)
interval.
A well-formed gamma packet looks like this:
&&
1984PASON/EDR
08211780.2
082463.8
!!
Importing and Exporting Your WITS Settings on page 30.
Factory Reset Clears all your selections and returns the settings to the defaults.
Table 1: WITS setup screen elements
In addition to choosing individual WITS codes, the EDR provides the option of using
preconfigured Full WITS or Half WITS settings to determine which WITS codes it sends.
click the Decimals drop-down box in the highlighted row and select 0, 1, 2, or
3 decimal places.
•Shelf Life
To select the length of time the EDR displays the WITS data, click the Shelf
Life drop-down listand choose 5 Mins (minutes), 15 Mins, 1 Hour, 12
Hours, 1 Day, or Never Expires. Once the shelf life period is exceeded, the
EDR changes the value of the trace to null, represented by two dashes (– –).
Important:
Shelf life is an important selection for time sensitive data. The EDR displays the last
received WITS value until the sender transmits a new value, or until it reaches the
end of the shelf life period. WITS data with a long shelf life can be misleading if users
don’t know the data’s age.
5. To enable your custom code to be sent or received, click on the code’s Enable
check box.
6. Click Save > Exit to return to the Setup Menu.
When you are finished, click Save > Exit. The EDR can now receive the custom WITS
code. To send this code, follow the directions in Selecting Custom WITS Codes to Send
below.
You can return all custom WITS settings to default at any time by clicking the Factory
The EDR enables you to physically connect and monitor up to 50 custom sensors. If you
enter a name for the custom sensor when you set it up in the EDR’s Custom Calibration
Menu, you can assign it a custom WITS code, which you can instruct a Pason computer
to send.
Follow these steps to set up a Pason computer to send a custom WITS code for a
connected custom sensor:
1. Ensure that the custom sensor is connected, and assigned a name in the EDR’s
Custom Calibration Menu.
2. From the EDR main screen on the RMPC, click Menu > Setup > WITS. The
WITS setup screen opens.
3. On the WITS out tab of the Pason computer you want to send the custom WITS
code, click the Custom button.
4. Scroll down to the Custom Analog Port section. You should see the name of the
custom sensor listed.
5. Click in the custom code’s row. The EDR highlights the row.
6. Click under Code in the highlighted row, and enter a four digit WITS code.
Ensure that the code is different from existing WITS codes. If the code you enter
conflicts with a current EDR WITS code, the EDR highlights your entry in red and
does not allow you to save your settings.
7. Select a transmission type from the Transmission drop-down list.
8. To enable the selected Pason computer to send your custom code, click on the
code’s Enable check box.
9. Click Save > Exit. The Pason computer starts sending the custom WITS codes
you selected.
Note:
If you do not see any custom sensors listed in the Custom Analog Port section, ensure
that you assigned your custom sensor a name in the EDR’s Custom Calibration Menu.
The EDR will not list any custom sensors in the Custom Analog Port section unless you
have assigned a name to at least one of them.
•Send both codes in the same WITS packet. Problems occur when Pason
receives one or the other, but not both.
•Send the packet at a minimum 0.2 m (1 ft) interval.
A well-formed gamma packet looks like this:
&&
1984PASON/EDR
08211780.2
082463.8
!!
4.10 Importing and Exporting Your WITS Settings
The EDR enables you to import and export saved WITS settings, for sharing via email or
USB memory stick.
Follow these steps to export WITS settings:
1. Select the WITS out tab of the Pason computer whose settings you want to
export.
2. Click the Export button.
3. Select a save location from the Save In drop-down list.
4. Enter a name for the saved settings file. Note that the default file name includes
the name of the Pason computer the settings are currently applied to, which is
useful.
5. Leave the file type at the default of WITS Out Template Files.
6. Click Save.
Follow these steps to import WITS settings:
1. Select the WITS out tab of the Pason computer you want to apply the imported
settings to.
2. Click Import.
3. Navigate to and select the settings file you want to import. This file must have a
.wto file extension.
4. Click Open. The EDR applies the saved WITS settings you selected, and
refreshes the WITS setup screen.
Note:
When you import WITS settings, the EDR overwrites your existing settings, including any
custom codes you have set up. Custom codes not included in the import file are deleted.
Figure 16: WITS monitor raw data (left) versus interpreted data (right)
Tip:
Use the times logged on the WITS monitor to determine WITS transmission rates. The monitor
displays WITS packets in the order the EDR receives or sends them.
Note:
If a Pason technician needs to troubleshoot WITS communications using CommEngine log files,
they can use the Port and Port Name details to identify the CommEngine to work on. Each WITS
device is represented by its own CommEngine process. WITS CommEngine troubleshooting
information is available to Pason personnel in KBase 1125 Debugging WITS Data Using CommEngine Log Files.