equal
deleted
inserted
replaced
1 ====================================================================== |
1 ====================================================================== |
2 R E A D M E . M A C O S X |
2 R E A D M E . M A C O S X |
3 doc: Thu Jan 19 09:43:38 2006 |
3 doc: Thu Jan 19 09:43:38 2006 |
4 dlm: Wed Jan 25 15:47:58 2006 |
4 dlm: Thu Aug 26 00:18:47 2010 |
5 (c) 2006 A.M. Thurnherr |
5 (c) 2006 A.M. Thurnherr |
6 uE-Info: 108 0 NIL 0 0 72 3 2 4 NIL ofnI |
6 uE-Info: 109 18 NIL 0 0 72 3 2 4 NIL ofnI |
7 ====================================================================== |
7 ====================================================================== |
8 |
8 |
9 This file contains MacOSX-specific notes for installing and running the |
9 This file contains MacOSX-specific notes for installing and running the |
10 LDEO LADCP operator scripts. |
10 LDEO LADCP operator scripts. |
11 |
11 |
84 scanbb is part of Eric Firing's LADCP processing software, which is |
84 scanbb is part of Eric Firing's LADCP processing software, which is |
85 available from http://moli.soest.hawaii.edu/software/ladcp. While |
85 available from http://moli.soest.hawaii.edu/software/ladcp. While |
86 binary versions are available for a variety of systems, MacOSX is not |
86 binary versions are available for a variety of systems, MacOSX is not |
87 one of them. Compilation is non-trivial and requires hacking of the |
87 one of them. Compilation is non-trivial and requires hacking of the |
88 source. If scanbb is not available, LADCP-data-file checking can be |
88 source. If scanbb is not available, LADCP-data-file checking can be |
89 disabled by modifying the procedure check_data in [DEFAULTS.expect]. |
89 disabled by modifying the procedure check_data in [CRUISE_SETUP.expect]. |
90 This is not recommended, however. |
90 This is not recommended, however. |
91 |
91 |
92 ====================================================================== |
92 ====================================================================== |
93 TTY DEVICE NAMES |
93 TTY DEVICE NAMES |
94 ====================================================================== |
94 ====================================================================== |
104 serial line has two associated /dev entries: /dev/tty.* and /dev/cu.* |
104 serial line has two associated /dev entries: /dev/tty.* and /dev/cu.* |
105 --- ONLY /dev/cu.* WORKS!!! With the current driver version, the first |
105 --- ONLY /dev/cu.* WORKS!!! With the current driver version, the first |
106 device is called /dev/cu.KeySerial1, but the second one has a |
106 device is called /dev/cu.KeySerial1, but the second one has a |
107 "geographical" (containing bus number, &c) name, such as |
107 "geographical" (containing bus number, &c) name, such as |
108 /dev/cu.USA49W3b13P2.2. The name depends on where it is plugged in, |
108 /dev/cu.USA49W3b13P2.2. The name depends on where it is plugged in, |
109 i.e. [DEFAULTS.expect] MAY HAVE TO BE MODIFIED AFTER RE-CONNECTING THE |
109 i.e. [CRUISE_SETUP.expect] MAY HAVE TO BE MODIFIED AFTER RE-CONNECTING |
110 USB CABLE(S). |
110 THE USB CABLE(S). |
111 |
111 |