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
Loading...
+ 30 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.