Here is info on how to connect to the 3 dataloggers through the wireless router. 192.168.1.1 Router IP root admin 250m logger IP 192.168.1.132 100m logger IP 192.168.1.107 Tower base logger 192.168.1.105 sonic sonicuser su sonicroot minicom -s in PUTTY terminal window will allow you to configure the serial port need to be root Have to change serial ports Data collection programs shouldn't be running minicom will start ctrl A A starts linefeed On 1/15/2008 Dan checked cabling into 250m logger and found that the 200 and 300m loggers we switched from what the diagram from UMass indicates. Table below reflects that. Note 300m sonic has lots of bad points as compared to the 200m sonic 250m Serial port no 0 1 2 3 4 5 Sonic no 1 2 3 4 5 6 Level/side 200/N 250/N 300/N 100m Serial port no 0 1 2 3 4 5 Sonic no 1 2 3 4 5 6 Level/side 150/S 150/N 100/S 100/N 50/S 50/N Tower base Serial port no 0 1 2 3 4 5 Sonic no 1 2 3 4 5 6 Level/side 22/N 10/N This is according to Vince's and Mario's drawing N = north boom S = south boom ipconfig is a command to look at IP and network information ntpq -p will check if the GPS is working and the clock reference etc/ntp.oncore.o contains the GPS initialization information ps -fx will show is collection programs are running (sonic) nohup run_sonics_250 & starts data collection in background with the ability to logout run_sonics_100m run_sonics_10m Can use winscp to collect data from raw_data directories. Because file names aren't unique at each level, you need to save them in separate directories. Hi Dan, I am attaching a schematic of our setup that is valid for the period 8/11-8/27. Hopefully it clears some of the confusion. From the data and notes I have, only 6 sonics ran during July: sonics 1-6 on the 100m logger. See BaoTowerSetup_Aug2007_001.jpg file for numbering diagram. Vince