LICOR looks to be working fine, no DTR/RTS jumpers to be seen. (This is a PC104 DSM, so maybe the todo task confused it with a Pi?)
Added a pic board for the leaf wetness sensor, cycled power on the mote, then verified messages are coming in with ID 0x8239.
Mote ID2 is radiation, ID1 is soils.
We were not sure what to do about swapped IDs for rsw in and out, since we assume there's no cable swapping to be done, and we probably don't want to reconfigure the individual sensors. Should we just override the NIDAS sensor XML at this site to match up the right IDs?
Kurt and Dan connected v04 to power, I visited later to get it on the net and check the data.
Ubiquiti
- Turned off frequency list.
- Fixed AP MAC, replaced current setting with tnw10 WSW: 44:D9:E7:C2:D5:A8.
- Changed name to Vall_04.
Eventually it linked successfully, signal at -75 dbm, and the dsm could ping the Internet.
DSM
- KZRAD in port 6 looks like a mote binary message.
- 12.8V on one mote (probably soil?), 13.3V on the other
- I see mote IDs in the 0x54 to 0x6b range, so I think KZRAD is working.
- 2m sonic on port 1 looks good.
- 10m winds on port 5 look good (repo config still had port 2).
- USB archive at 5% and growing.
At first there was nothing for 10m LICOR on port 3. Port 3 has 3A fuse and the fuse is good. Port 3 is jumpered for 232. When I checked the fuse that cycled the power on the LICOR, and that seems to have fixed it...
Cannot update eol packages, apparently because somehow some of the directories in the EOL debian ftp archive have become inaccessible. So until I can fix that, I updated the DSM manually by installing xinetd and check-mk, and downloaded and installed the latest package files for isfs-field-erpdigao, eol-daq, and isfs-daq.
The repo config has been fixed to match what was running on the DSM.
At the moment, none of our cal_files have Vazimuth entries, so everything is in instrument coordinates. This isn't useful for our users. We are expecting "exact" angles to be measured using the laser multistations during operations, but until then probably need to do something else. One complication is that we are using Gills, METEKS, RMYs, and CSATs. I assume the Gills were all set to have north=north. We set the METEKS and RMYs to have north=along boom away from the tower, though some may have been opposite(!). The CSATs are all along the boom, pointing away from the towers. So, we also need to know the tower orientation. The booms are nominally parallel to the ridge, pointing in the SE direction. Call this direction 142degrees.
In one case, I oriented 10m.tse12 antiparallel to the other sonics (boom pointing in the NW direction) to avoid a local tree.
Thus:
Gill: (For Gill R3s, Vaz is the N arrow direction + 240 degrees.)
vaz = 0 + 240 = 240
CSAT: (For ATI and Campbell CSAT3 sonics, Vaz is the direction relative to true north, straight into the array from the un-obstructed direction, minus 90 degrees.)
CSAT.10m.tse12: vaz = 142 - 90 = 52
RMY: (from me: +v is "from north", oriented perpendicular out from the connection box. Assuming we mounted the box away from the tower, this is the boom direction away from the tower:)
vaz = 142 (it seems that 142+180 works better – perhaps we put the connection box towards the tower?)
METEK: (from me: manual seems to show +v is perpendicular to N arrow – essentially East)
vaz = 142 + 90 = 232 (sign convention appears to be left-handed. we'll change this in NIDAS. Also, this makes vaz = 232-180 = 52)
All this now implemented in cal_files and config.
got tnw05 partially setup today (need N.D. and O.U. sonics to flesh out the station).
Access is particularly difficult, but do-able.
Sea containers still have not arrived but Jose Carlos says they will be here this evening.
Not sure which container holds the sensors we need, or where in the container they reside, but we will attempt to retrieve them tomorrow. This site and tnw06 are the only towers erected left to instrument, then it is all maintenance till Samortechnica gets more in the air. Jose tells me that they plan on a big push next week. Time will tell.
I plan on at least two days per tower for these since they have a lot of levels, and solar panels.
tnw05 also has a lot of trees, one right next to the tower that is about 10 meters high, so I plan to place all sonics 12 meters and lower 60 degs to the west, (upper levels still are aimed SE), unless you want me to cut the tree down.
installed TNW01
20 m ARL RMY 81000 s/n 1359
10 m ARL RMY 81000 s/n 645
2 m ARL RMY 81000 s/n 712
mote # 55
PTB220 s/n U4110003
DSM power panel fried upon hookup, power was ok at cable end before attaching, but the smoke was let out at power up.
will install spare DSM tomorrow?
added 2nd battery at TSE 02 and grounded DSM
TNW 11 installed 14 v P/S
RiNE 07 swapped port 4 and 6 (NRO1, and EC150), data streams now look OK
verified that Tr NW 06 and Tr NW 05 towers are installed - 05 is a real bugger to get to.
Attempted to power up V04 but power run is about 42 meters, and would exhaust our supply of long power cables, so I am making a cable out of the zip cord and will attempt to install tomorrow.
At Gary's inquiry, I have plotted Qsoil from tnw09 for the last 20 days. This sensor has read mostly negative values consistently, but clearly is responding, for example to a precip event 17 days ago. We should check the sensor cable connection at this site. (All of the Wisard boards are plugged directly into the mote boxes, so this connector is easily accessible.) Qsoils should be the red Wisard board.
In any case, we should take regular soil cores at this site (of course, we should take them at every site), to be able to create an in-situ calibration.
Just playing in minicom, I get "sort of" the correct data from this Licor using 19200baud 7-E-1. This tells me that the baud rate is correct and the instrument is trying to report. I would suspect a bad ground connection, either in the cable (not too likely) or (much more likely) in the screw terminal cable terminations inside the Li7500 electronics box.
We set up station TrSE01 today, long and hard. Dan spent about 6.5+ hrs on the tower with NO complaints - what a trooper!
Spent lots of time trying to get the 10m sonic (csat3a) on line.
Very frustrating. The sonic was working well in the ops center this morning, but refused to cooperate once on the tower.
Tried multiple grounding techniques, isolation, etc. to no avail.
Will have to revisit later.
We may need to have more power cable sent over to accommodate solar panel and power pole to station runs, will assess tomorrow.
Power is down at the ops center, so we don't know if TrSE01 is reporting.
No other sites visited today.
got valley 3 instrumented today, and after replacing the 2 meter CSAT3A head got all the instruments working. Original head gave only NAN's. Waiting on INEGI to supply batteries to power up the station.
replaced the cable at TNW 07 20 meter TRH, and replaced the 12v P/S with a 14 volt unit. (60 meter TRH now working on its own)
Having issues with Valley 07 20 meter Licor and CSAT3A, will explore other avenues tomorrow hopefully.
Questions about needing serial #'s for TNW 07 - all NCAR sensors there are TRH's, and they report their S/N's - do we need the ID's from the RMY sonics that are the only other sensors on the tower?
Power pole and drop for Valley 04 is about 35 yds from tower, will attempt to run DC cable, but am concerned about IR drop for that distance, will use 14 v P/S to compensate, but that takes another 14 v supply from other needy stations......
only 2 more towers to instrument until user sensors arrive.
These are PC104 DSMs (I can't remember which are Titans and which Vipers) which have not been online even though their ubiquiti radios are online. I visited each to see what I could figure out.
rsw02
My first realization was that I didn't have a console cable for these DSMs, so I didn't try to log into this one. I did notice that the ethernet ribbon cable was disconnected from the interface panel, but I wasn't sure of the orientation of the plug. I rebooted it anyway and left to check on the plugs in the other DSM. At rsw05 I saw that the ribbon cable gets plugged in with ribbon exiting away from the RJ45 jack:
So that's how I plugged it back in at rsw02 on the way back.
Nagios on ustar reported that rsw02 then started responding to pings, for another few hours, until I tried to run an ansible playbook on it from ustar, and now it has not responded since. I should have tried to log into it first to see whether anything else was working, but I didn't.
rsw05
Rebooted, just to start from scratch, but maybe not necessary. The ethernet ribbon cable is plugged in and I see lights, so I can't see anything obviously wrong.
So I disconnected the ubiquiti at the bulgin port and connected my laptop to the internal RJ45 jack. Ssh works, I can log into the DSM. The IP address is correct: 192.168.1.173, GPS is locked and chrony in sync, usb is at 50%.
No data from the METEK sonic.
Next I disconnected the ethernet ribbon cable, plugged ubnt radio back in, with my laptop still plugged into the internal RJ45 jack. I cannot ping or browse to rsw05u, but I know it's up because it has been pingable for the last week.
So should it be possible to connect to the ubiquiti through the internal RJ45 jack? If so, does that mean there is a problem with the ethernet connections on the interface panel?
Next steps
I'm considering what to try next:
Log into the DSM with the console cable and investigate from there. Ping the radio, look for log messages about errors in the ethernet device.
I have one of the RJ45 jacks which plug directly into the CPU card for either the Titan or Viper. I could at least isolate the ribbon cable with a patch cable between the CPU jack and the RJ45 jack on the interface panel, but I don't think that works for both Titans and Vipers.
Work on a scheme to isolate the interface panel ethernet port. My best guesses:
- Use a cable with a bulgin female plug and RJ45 plug to convert the Ubiquiti cable to RJ45 end, then plug that into a PoE injector which gets power from somewhere, either by tapping the power panel or the external bulgin ethernet port. If the internal RJ45 works to connect to the CPU, then that can be used to patch the CPU into a switch, also powered off the power panel.
- Replace the bulgin cable entirely and run an ethernet cable up the tower same as the Pi towers. Use the same PoE injector, but it might need a different power plug. Connect that to the internal RJ45 jack same as above.
- If there is a problem between the internal RJ45 and CPU card, then I don't know what you do. Can we attach the ribbon cable to a new RJ45 jack? Use a USB ethernet interface instead of the onboard interface?
- Just replace the entire interface panel. If we don't have spares here, take one from VERTEX. Or replace the entire DSM with one from VERTEX, but keep the CPU stack.
TSE 02 was instrumented yesterday, some issues with the network but we may move an antenna soon.
The mote was not reporting but found the problem rather quickly. Measured for voltage - 0 volts. Turns out that the cable was chewed in two (gray PVC cable, not the standard green serial cable)
replaced power supplies at V 06 and V 07 with 14 volt supplies
installed anti twist plate on 2m sonic at V 07 and got the DSM's on line again, but port 3 is not working (Licor). Possibly the fuse. Will look at later.
V06 has intermittent NAN's for the 20 m sonic.
installed USB stick at V 06 (was borrowed for another station back in Feb.)
Today (4/7) instrumented RSW 08, all data coming in, but voltage is low at DSM (10.9 volts), should be fine. Explored and found 2 towers which were erected, but not according to the spreadsheet. Will instrument those soon.
April 6th setup notes: Gary, Dan and I arrived late yesterday. Wednesday we rearranged the ops center and attempted to find all the sensors and equipment left in the beginning of Feb. with some success, and some failures (we can't seem to locate at least one Metek sonic, and the PTB 220 pressure sensors as of yet).
We set up station V06 this afternoon, but are missing a USB memory stick (forgot that stick was "borrowed" for another station back in Feb). Will attempt to bring that station up tomorrow.