You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

For the wide array, from Jun 26 to Jul 18, there is some confusion about the bottom level downwind sonic anemometers on towers 4, 5 and 6. The variable names from these sonics have suffixes of 4b, 5b and 6b, indicating what tower they were on.

Intended Configuration for 4b,5b,6b

The intended configuration for the sonics is as follows, along with the serial numbers that Kurt wrote in his setup notes:

location

serial port

sensor id

serial number

4b

ttyS6

2040

744

5b

ttyS7

2050

745

6b

ttyS8

2060

376

The samples are archived with the sensor ids, so after the data has been sampled, knowing the relation between location and sensor id is critical, and is what needs to be determined for these sonics.

So far nothing has indicated any error in Kurt's setup notes of the relation between location and serial number.

The configuration of the later arrays also confirms Kurt's notes for the wide array, because when the sonics were moved to the medium and narrow arrays, care was taken to keep them in their respective locations.

Tom's documentation of the serial number/serial port relation for array 2, https://wiki.ucar.edu/x/OYWgAQ, agrees with the above serial port to serial number relation.

SteveO's entry for array4, https://wiki.ucar.edu/x/W4CqAQ, also agrees with the above.

In setting up these arrays, care was presumably taken to get the cabling right, so that we're also confident of the mapping from serial port to location during those configurations.

The archive will contain the results of the rserial sessions that were done to show the sonic serial numbers, and this can be used to confirm the sensor id to serial number mapping. These serial number messages, by sensor id will be available soon.

Possible Cross-cabling in Wide Array

In log entry https://wiki.ucar.edu/x/tBR_AQ, Tom used rserial to record the sonic serial numbers at each serial port for the wide array, and noted the following results:

serial port

serial number

ttyS6

745

ttyS7

376

ttyS8

744

From this he concluded that the cabling from serial ports to the sonics was crossed up from the intended configuration.

The XML specifies what sensor id is assigned by the DSM to each sample received on a serial port. It is likely that the mapping of serial port to sensor id in the XML was correct, matching the intended configuration. Assuming so, it then seems that the actual relation between sensor id and location on the wide array was as follows:

location

serial port

sensor id

serial number

4b

ttyS8

2060

744

5b

ttyS6

2040

745

6b

ttyS7

2050

376

If the above relation of sensor id to location is true, then our data processing, which used the intended configuration, assigned wrong location suffixes to the data from those sonics for the wide array.

Evidence of Actual Sonic Location

There are several counter-arguments to the above, indicating that Tom somehow confused the serial ports in his log message, and that the cabling matched the intended configuration in the wide array.

First, the serial number to sensor id relation can be read from the data archive, since the rserial output is archived. Assuming Tom progressed through the serial ports in order, they show the serial number sequence to be 744, 745, 376, and not 745, 376, 744. The sensor ids are also in time order, 2040, 2050, 2060:

data_dump -A -i 2,2040-2060 downwind1_20080629_153516.dat | fgrep ET=
sample for sensor id 2,2040, with SN 744
2008 06 29 22:30:34.0640 0.02535 2,2040    516 \n>-Reset. EEProm_sig=10244. Prom_sig=17263. \n>??\r\nET= 60 ts=i XD=d GN=112a TK=1 UP=5 FK=0 RN=1 IT=1 DR=102 rx=2 fx=038 BX=0 AH=1  AT=0 RS=1 BR=0 RI=1 GO=00000 HA=0 6X=3 3X=2 PD=2 SD=0 ?d tf=02600 02600 02600\r\nWM=o ar=0 ZZ=0 DC=1  ELo=008 010 010 ELb=010 010 010 TNo=eeb d TNb=eec JD= 007\r\nC0o=-2-2-2 C0b=-2-2-2 RC=0 tlo=6 8 8 tlb=8 8 8  CA=1 TD=  duty=092  AQ= 60 AC=1 CD=0 SR=1 UX=0 MX=0 DTU=02320 ss=1 XP=2 RF=018 DS=007 SN0744 07nov07 JC=3 CB=3  MD=5 DF=05000 RNA=1 sa=1 rev 3.0f cs=10244 &=1 os= \r\n>DD\xe9\xf1\xd3U\x04\xd8/\xe4\x0fU\xaa

sample for sensor id 2,2050, with SN 745 is 2.5 minutes later
2008 06 29 22:33:09.7736  0.0125 2,2050    516 \n>-Reset. EEProm_sig=46481. Prom_sig=17263. \n>??\r\nET= 60 ts=i XD=d GN=100a TK=1 UP=5 FK=0 RN=1 IT=1 DR=102 rx=2 fx=038 BX=0 AH=1  AT=0 RS=1 BR=0 RI=1 GO=00000 HA=0 6X=3 3X=2 PD=2 SD=0 ?d tf=02600 02600 02600\r\nWM=o ar=0 ZZ=0 DC=1  ELo=010 010 010 ELb=010 010 010 TNo=dcf d TNb=ede JD= 007\r\nC0o=-2-2-2 C0b=-2-2-2 RC=0 tlo=8 8 8 tlb=8 8 8  CA=1 TD=  duty=093  AQ= 60 AC=1 CD=0 SR=1 UX=0 MX=0 DTU=02320 ss=1 XP=2 RF=018 DS=007 SN0745 05nov07 JC=3 CB=3  MD=5 DF=05000 RNA=1 sa=1 rev 3.0f cs=46481 &=1 os= \r\n>D\xfd\xdd\xd8\xde\x01\x01\x02/\xf6\x0fU\xaa

sample for sensor id 2,2060, with SN 376 is  1.5 minutes later
2008 06 29 22:34:38.8956 0.01639 2,2060     522 \n>-Reset. EEProm_sig=28394. Prom_sig=17263. \n>T\n>\r\n>??\r\nET= 60 ts=i XD=d GN=222a TK=1 UP=5 FK=0 RN=1 IT=1 DR=102 rx=2 fx=038 BX=0 AH=1  AT=0 RS=1 BR=0 RI=1 GO=00000 HA=0 6X=3 3X=2 PD=2 SD=0 ?d tf=02600 02600 02600\r\nWM=o ar=0 ZZ=0 DC=1  ELo=010 010 010 ELb=010 010 010 TNo=dde d TNb=dee JD= 007\r\nC0o=-2-2-2 C0b=-2-2-2 RC=0 tlo=8 8 8 tlb=8 8 8  CA=1 TD=  duty=094  AQ= 60 AC=1 CD=0 SR=1 UX=0 MX=0 DTU=02320 ss=1 XP=2 RF=018 DS=007 SN0376 09nov07 JC=3 CB=3  MD=5 DF=05000 RNA=1 sa=1 rev 3.0f cs=28394 &=1 os= \r\n>D\n\xc9\x14\xc9\xb3\x00\xe61\xf7\x0fU\xaa

Perhaps two mistakes were made which cancelled each other: cross-cabling, and making the wrong association between serial port and sensor id in the XML? Or perhaps the XML on the DSM was corrected to match the cabling shortly after the wide array started, and then corrected back for array2? Both seem unlikely. The sequence of the above serial numbers suggest that neither of the above occurred, and that the serial ports were recorded incorrectly in Tom's log message.

I (Gordon) also do not believe that the sensor ids were altered in the archive after it was recorded.

Steve Oncley also looked at data during dust devil events from these sonics during the wide array, and the spacial continuity of the relative wind directions indicate that the sonics were in the intended configuration.

The tt_adjust program has been run on the AHATS unsorted raw data. One of the results of the processing is a linear fit of the relation of the sample time tag to the sample number, for every 1/2 hour. The slope of the fit is the sampling period of the sensor, which for sonics at 60Hz, should be about 16666.7 microseconds. Systematic differences between the sample periods of individual sonics can be seen, which provide another indication of the relation between the sensor id and the sonic serial numbers.

The sampling rates show a diurnal temperature dependence, but one can distinguish the individual sonics. Below is a plot of sample delta-T for sensor ids 2040, 2050 and 2060 for the entire project, showing that the serial number to sensor id mapping did not change for these sonics during the project. The sensor id is shown in the trace legend.

The data is a bit noisy during the wide array, but it seems quite certain that the relation of serial number to sensor id did not change:

  • No labels