1 #====================================================================== |
1 #====================================================================== |
2 # R E A D M E |
2 # R E A D M E |
3 # doc: Sat Mar 20 23:10:10 2004 |
3 # doc: Sat Mar 20 23:10:10 2004 |
4 # dlm: Thu Aug 26 00:17:47 2010 |
4 # dlm: Mon Oct 18 12:55:18 2010 |
5 # (c) 2004 ladcp@ |
5 # (c) 2004 A.M. Thurnherr |
6 # uE-Info: 16 0 NIL 0 0 72 3 2 8 NIL ofnI |
6 # uE-Info: 63 8 NIL 0 0 72 3 2 8 NIL ofnI |
7 #====================================================================== |
7 #====================================================================== |
8 |
8 |
9 =Connecting Instruments= |
9 =Introduction= |
|
10 |
|
11 The LADCP_acquire software implements LADCP data acquisition on UN*X |
|
12 systems (e.g. Linux, MacOSX, FreeBSD, etc.). It consists of the bbabble |
|
13 program, a portable bbtalk replacement written in perl, as well as a |
|
14 number of "operator scripts", written in expect. The main purpose of |
|
15 the software is to provide a comfortable and "operator-error-tolerant" |
|
16 command-line environment for data acquisition from single- and dual-head |
|
17 LADCP systems built using Teledyne/RDI heads. |
|
18 |
|
19 The documentation assumes familiarity with UN*X and LADCP data |
|
20 acquisition. (If you do not know what a UN*X "special file" is or have |
|
21 never seen an ADCP command file, this software and documentation is not |
|
22 for you.) While I do not intend to support this software, bug reports |
|
23 sent to <athurnherr@yahoo.com> are welcome. This [README] file contains |
|
24 notes on how to setup and use the LADCP_acquire data acquisitions |
|
25 software for a new cruise. For notes on installation on different UN*X |
|
26 flavors see [README.*] files (e.g. [README.Linux]). |
|
27 |
|
28 |
|
29 =Connecting ADCP Heads to Acquisitions Computer= |
10 |
30 |
11 1) physically connect the instruments |
31 1) physically connect the instruments |
12 - many USB-to-serial adapters do not work; we use keyspan ones |
32 - many USB-to-serial adapters do not work; we use Keyspan adapters |
13 |
33 |
14 2) determine the special files of the serial ports the instruments are |
34 2) determine the special files of the serial ports the instruments are |
15 connected to: |
35 connected to: |
16 - Linux: /dev/ttyS0 /dev/ttyS1 for standard serial ports |
36 - Linux: /dev/ttyS0 /dev/ttyS1 for standard serial ports |
17 - Linux: /dev/ttyUSB0 /dev/ttyUSB1 for USB2serial ports |
37 - Linux: /dev/ttyUSB0 /dev/ttyUSB1 for USB2serial ports |
37 |
57 |
38 ---------------------------------------------------------------------- |
58 ---------------------------------------------------------------------- |
39 |
59 |
40 =Operator Scripts= |
60 =Operator Scripts= |
41 |
61 |
42 NB: [CRUISE_SETUP.expect] must have been edited to set cruise-specific |
62 NB: Before using any of the operator scripts, edit [CRUISE_SETUP.expect] to |
43 information. |
63 set cruise-specific parameters. |
44 |
64 |
45 NB: the search path must be set up to include the directory of the |
65 NB: the search path must be set up to include the directory of the |
46 operator scripts. It is NOT possible, to use the operator scripts |
66 operator scripts. It is NOT possible, to use the operator scripts |
47 with full pathnames (e.g. ./reset2) |
67 with full pathnames (e.g. ./reset2) |
48 |
68 |
54 erasemem1/erasemem2 clear recorder memory |
74 erasemem1/erasemem2 clear recorder memory |
55 interact1/interact2 enter interactive mode (similar to BBTALK) |
75 interact1/interact2 enter interactive mode (similar to BBTALK) |
56 ladcp1/ladcp2 start new cast (upload command file & start pinging) |
76 ladcp1/ladcp2 start new cast (upload command file & start pinging) |
57 abort1/abort2 abort started cast (rename cast directory) |
77 abort1/abort2 abort started cast (rename cast directory) |
58 endladcp1/endladcp2 end cast (stop pinging & download data) |
78 endladcp1/endladcp2 end cast (stop pinging & download data) |
59 checkfiles1/checkfiles2 postprocess data after download ok (check and |
79 checkfiles1/checkfiles2 post-process data after download ok (check and |
60 backup data files) |
80 backup data files) |
61 |
81 |
62 ladcp_send_cmd <tty port> <cmd-file> |
82 ladcp_send_cmd <tty port> <cmd-file> |
63 send command file to LADCP connected to specific |
83 send command file to LADCP connected to specific |
64 port; this is the command that can be used to |
84 port; this is the command that can be used to |