<aside> <img src="/icons/swap-horizontally_gray.svg" alt="/icons/swap-horizontally_gray.svg" width="40px" />

Quick overview:

1. Turn on the instrument (Power supply)
2. Start acquiring the instrument data (DEV1)
3. Start the winch control system (DEV2)
4. Start plotting the incoming data (DEV3)

</aside>

Lucid Chart flow chart of data collection and processing steps. https://lucid.app/lucidchart/927b0769-db72-4dff-b721-8e231e21e8eb/edit?invitationId=inv_5835916e-1f2f-4cee-a032-ed96f78386b4&page=0_0#

Detailed instructions:

On the deckbox

1. Turn on POWER button (on the left).
2. Flip switch for PSI modem to on.
3. Flip big switch (on the right) to on.
4. Turn on OUTPUT button (sends power down the line).
5. Wait for PSI modem lights to turn steady green and red.

<aside> <img src="/icons/flash_blue.svg" alt="/icons/flash_blue.svg" width="40px" /> **Watch for voltage and current

·** On MOTIVE, with a 3000 m cable, we are setting the box to 167V + 48V. · For a 1500 m cable, we would use less. · If you’re doing tests in the lab, use 60V + 48V

· V = IR The longer the cable, the more resistance. We want the current to be the same, and we want the voltage on the fish end of the cable to be 100 V, so the longer the cable, the more voltage we need.

</aside>

On DEV2 - Start LabView

1. Open LabView from the Dock
2. Open winchcontrol2024_MOTIVE_20240609.vi
3. Hit white arrow in top left corner to start

• To view the control box panel, open a web browser and go to 192.168.1.160

  • TC/IP port 50500
  • UDP port local 60500
  • UDP port remote 60500

• Stuff that I don’t think applies anymore:

🟨 On DEV1 - Start data acquisition

• Eventually we might have yaml-to-Setup file. This isn’t working yet, so skip this toggle

<aside> 👨‍💻

If you need to find/change the name of ports:

Unplug and replug dongles to see what each one is called.

We have three ports, one for data, communications, and one for GPS. | | Change CTD.CTDPortName to the incoming data port name | You only need to do this at the beginning of the cruise or if you swap an RS-232 dongle. | | Change CTD.CommandPortName to in communications port name | | | If you’re using GPS, uncomment TCPIPSocket.portnum, UDPSocket.portnum, PCode.PCodePortName, and PCode.speed. Change PCode.PCodePortname to match GPS port name | | | Make sure Ascii_dataFile.path points to /Users/Shared/FCTD_EPSI_DATA/Current_Cruise | | </aside>

• In a Terminal window:

  What to type	What this is doing
  fctd_epsi_dir	Change directory to the latest version of the FCTD Epsi acquisition code.

  If this shortcut doesn’t work, navigate directly to this directory, or add an alias in ~/.bash_profile:

  cd /Users/Shared/Software_current_cruise/Acquisition/fctd_epsi_acq/build/fctd_epsi/Build/Products/Debug | | vi Setup | Open the Setup file in vi | | i | Enter insert mode so you can edit the Setup file | | Change CTD.SerialNum to match the serial number of the Seabird you’re deploying. Make sure SBE SN is four digits (0537). | You need to do this anytime you change instruments and have a new SBE number. | | Edit CTD.survey to reflect the current deployment name. | Use format yy_mmdd_d##_[FISHNAME]_[DESCRIPTION] | | Edit CTD.experiment to reflect the current module | | | Hit esc button | Get out of editing mode | | :w | Save your changes | | :q | Quit and get back to the command line. | | ./fctd_epsi | Start the fctd_epsi data acquisition. The terminal screen should pause for a moment and then you should see a line with DCAL. If you don’t see DCAL, type q, wait 5 seconds, and run ./fctd_epsi again. |

  <aside> <img src="/icons/exclamation-mark-double_gray.svg" alt="/icons/exclamation-mark-double_gray.svg" width="40px" />

  If you stop ./fctd_epsi and restart it, there’s a bug that causes it to reboot itself. Just wait a minute and try again.

  </aside>

  

  Example Setup file. Yellow highlighted lines show the lines you should check/change for a new FCTD deployment.