...

Tool string depth and tension are readily consumable gauges of the progress and status of logging operations. During logging operations, JRSO convention widely distributes Schlumberger winch position (WPS) data via RigWatch displays. 

...

Schlumberger provides JRSO with winch position telemetry. Software systems have (repeatedly) been implemented to make that data more widely available. The present "SLB to RW system" converts Schlumberger WPS protocol winch position data to WITS. The WITS data is passed to RigWatch.

SLB to RW is presently hosted on a Dell laptop. The software system processes WPS telemetry through three serial devices:

• COM4 - Input. WPS Winch position telemetry is received via an RS485 serial connection from the Schlumberger rack.
• The telemetry is a binary stream.
• It is delivered at 19200 baud, 8 bits, no parity, 1 stop bit, no flow control.
  These settings are supplied by the software. These are not the defaults you will see in Windows Device Manager.
• COM3 - Output. SLB to RW--a LabVIEW 2020 executable program--processes incoming WPS telemetry (COM4) to WITS format. The WITS stream is output via COM3 (RS232).
  • The decoded telemetry is readable text. No need to run PuTTy--SLB to RW displays the data stream.
  • It is delivered at 9600 baud 8 bits, no parity, 1 stop bit, no flow control.
• COM1 - SLB to RW output; RigWatch input.
  • COM3 is physically connected in loopback fashion to COM1. The loopback cable is known as a null-modem or cross-over cable.
  • The data is delivered at 9600 baud, 8 bits, no parity, 1 stop bit, no flow control.

During operations the RigWatch Master receives WITS data on device "COM1 - Remote 6" (via the network)--i.e. via the winch telemetry laptop aka  RigWatch Remote 6 aka 192.168.1.11.

...

• COM3 - Output. "SLB to RW" formats incoming winch telemetry (COM4) to WITS. The WITS stream is forwarded to COM3 (RS232).
• COM1 - Output from "SLB to RW". Input WITS to RigWatch.
  • COM3 is physically connected in loopback fashion to COM1. The loopback cable is known as a null-modem or cross-over cable.
• During operations the RigWatch Master receives WITS-formated winch telemetry--across the network--on device "COM1 - Remote 6". Rephrased: the RigWatch instance on the Dell laptop (i.e. Remote 6  or 192.168.1.11) passes COM1 data to the RigWatch Master--only when the Master is configured to listen for that device.

Image Added

This diagram accurately depicts the flow and handling of winch position telemetry through the present Dell laptop (and any subsequent system that may be put in place). The COM port numbers in the diagram are inaccurate and superseded by the text above.

Starting the Winch Telemetry Laptop

...

• COM4 is a National Instruments device RS-485 to USB.
  • The RS485 connector is tied to the Schlumberger WPS output.
  • The USB connector ties to the (only) left-hand-side (toward the back) USB connector.
• COM3 is provided via a Tripplite Keyspan USB to Serial RS232 device.
  • The USB cable ties to the (only) laptop backplane (right-hand-side) USB connector.
  • The 9-pin RS232 connector attaches to a null-modem cable.
  • The null-modem cable attaches to the only 9-pin RS232 connector on the laptop backplane (left-hand-side).

...

1. A single deliberate press of the laptop power button suffices (upper-right of the built-in keyboard).
2. Login as DAQ. The usual. Wait, up to a minute.
   • SLB to RW is run automatically.
   • RigWatch is run automatically.
   • Windows profile startup processing takes precedentprecedence. It may be up to 30 seconds 30 sec - 1 min before SLB2RW and RW start.
   • SLB2RW will typically launch faster than RW.
   • If the Schlumberger winch feed is on, SLB2RW will begin displaying winch telemetry within 3 secondsis on, SLB2RW will begin displaying winch telemetry within 3 seconds.

Because logging occurs at such wide intervals, it is best to catch the RigWatch startup before it defaults to the previously used hole. Choose "Start New Well", register to reconnect to the Master (192.168.1.7), and then continue RigWatch startup.

Notes

• The DAQ profile is configured for Windows Remote Desktop access via 192.168.1.11.
• SLB to RW is installed in C:\Users\daq\Documents\WPS to WITS - SLB to Rigwatch: SLB2RW.exe
• RigWatch is installed in C:\RWPRO. The executable resides at C:\RWPRO\Tools\interfaces\rw.exe.
• The shortcuts used to launch both programs reside in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\.

...

That "seen once" was corrected by a restart of RigWatch. Not a desirable activity during rig-floor operations and continuous data collection.

Change

20210804 df Smoke test. Last logging run of the expedition. TBD.

20210803 df Adapt Schlumberger Winch Data transfer to RigWatch System (SLB to RW) document to this form.

...

• Last bit: restart RigWatch Master. It was insufficient to "hang-up" and reconnect the "COM1 - Remote 6" device.
  Full system observed to operated end-to-end. But once again only for the latter portion of a logging cycle.
• Run a repair install of NI Serial. Some event (unplug?) caused the driver to uninstall.
• Observed that COM1 and COM2 designations in software were swapped with respect to the physical configuration. Re-assigned the serial ports using the Device Manager > Properties > Advanced... settings.
• Conducted a variety of tests to gauge the effects of serial port driver removal, device disable/enable, and COM port renumbering. Every variant requires a host system restart.Incidentally useful background toward making sense of WinTemp inability to quickly recognize the availability of the APCT tool.enable, and COM port renumbering. Every variant requires a host system restart.

20210720 df Delivered winch telemetry over the Dell 53043. Demonstrated workable for the latter half remainder of that logging cycle.

20210718 df, nl Commit to rebuilding winch telemetry on new hardware. Selected the ruggedized Dell (53043), though any of the others would sufficean NI RS4585 USB-to-serial device, and a Tripplite Keyspan USB-to-serial device.

• Repeated install and rollback attempts with the NI PXI-8106 embedded controller led to the realization that its on-board network controller is failing.
• The device has been carried forward as a one-off without spares for some time.

Archived versions

Logging Winch Telemetry to Rigwatch - 27Sept2022