Data Trawler - Event Details

Please login if you have access to particular applications.

Event details

Voyage: IN2015_V02       [details]
Subject: Tried KSync on OS150 and changed OS150 to Narrow Band mode
When: 2015-05-19 05:33:20 UTC

- entered into Elog/Everlog as 2015-05-19 05:33:20
Log: in2015_v02
Equipment: ADCP

75/150 KHz ADCP [view]
Station/Location: EAC off Brisbane
Position: Latitude: -27.21513 Longitude: 154.65465

- entered into Elog as 27 12.908S, 154 39.279E
Action: Stop

Having diagnosed that the 150Khz and 75 Khz ADCPs interfere with each other, we tried to use Ksync to prevent this. Edited config files to try it on the 150 first.

Stopped acquisition at 19/05/2015 at 0415

Tried restart with Ksync config (external trigger) - got corrupted output in log file and adcp kept restarting. Did a hard reboot at the deck box and tried again. We had the same problem. Acquisition stayed off.

Dr. Google found us a very enlightening report written by UHawaii - likely jules hammon. She recommends to not use Ksync due to its degradation of ping numbers but to rely on post processing in CODAS to remove the interference.

She also recommended using NB on both instruments in internal trigger mode to maximize ping numbers, range and reduce the effect of bubbles - particularly for the OS150 (Gabi will explore this on our 150).

So, we reconfigured the OS150 into narrowband internal trigger 8m bin mode.

After several false starts, acquisition was resumed at 0525 UTC.

NCMI Information and Data Centre  »  Applications  »  Data Trawler