Generally, this log is really not very understandable! The log is being maintained on-line for the sake of completeness. Much of the information included in the log applies to specific software, and contains names of programs, computers, or what-have-you, that may make sense only to technicians who were intimately familiar with the radar system as it was configured for this project.
Very little attempt has been made to edit any of the technician's comments. Use the info in this log at your own risk.
Information in this log was written by Joe Vincent, RSF. Much of the content of the log is concerned with testing of, and corrections to, the radar prior to its deployment for WISP94; please watch your dates when evaluating information. For the most part, there were very few problems with CP4 during WISP94. With that in mind, the information in this log is less important than it might have been! This also explains the relatively infrequent log entries during the WISP94 operational period. Be sure to also review the operator log for comments that might be more relevant for day-to-day data quality.
Lines are used to separate individual log entries.
Document Maintenance: Bob Rilling / NCAR Remote Sensing Facility / ( rilling )
Tue Oct 5 15:40:38 MDT 1993 This is a test.
Wed Oct 6 09:20:21 MDT 1993
Thu Oct 7 09:37:42 MDT 1993
Fri Oct 15 08:30:04 MDT 1993 testing notes
Thu Oct 21 15:39:53 MDT 1993
Wed Nov 10 14:58:19 MST 1993 a couple of new bugs to report. 1. Sur scans will not step up if you start the azimuth at zero degrees. so start the azimuth at 1 degree until its fixed. 2. If you have the processor in half prf mode 1392 gates it will crash when you start. It will also crash if you zoom in or out.
Wed Nov 10 15:01:55 MST 1993 re-tuned the antenna today. I changed az proportional and derivitive gain and elevation proportional and derivitive gain. seems to work ok.
Wed Nov 10 15:15:21 MST 1993 if you do a surveillance scan and you use repeat, prepoint doesn't run so you can get an extra tilt at the bottom. I guess to get around this you would have to write a schedule to do repetitive sur scans. If you want to avoid the extra tilt, use the next button on the sur and that gets it to the left of the start angle and then you just get the one tilt at the bottom.
Tue Nov 23 15:17:13 MST 1993 repaired the cable 60 mhz in the stalo drawer. fft distortion due to a lack of 60 mhz to the mixers. It was 6 to 8 db low in 60 mhz injection
Wed Nov 24 11:25:19 MST 1993 checked out the doppler phase shifter and it looks ok.
Wed Nov 24 12:45:37 MST 1993 took a look at the cp4 doppler shifter circuit with the logic analyzer and it looks ok.
Wed Nov 24 12:53:25 MST 1993 I noticed that the elevation gain is acting kind of strangely. sometimes the antenna can't get to its desired elevation, its undershooting and lacks enough gain. Sometimes its got too much gain. I haven't been able to run this down yet, but here are a few tips to try If the antenna has problems getting to its desired elevation on the vxworks console, type: tcl pmac i231 and see what it returns try setting i231 to 3800 pmac i231 = 3800 and see if that helps. If i231 is too low you may get oscillation in the elevation, but its too high you may not get to your desired position I like three numbers for i231 3800 6500 and 8500
Mon Nov 29 14:16:02 MST 1993 DANGER If you start up the radar with the antenna below zero degrees, the pmac get confused about which quadrant its in. You must start the pmac with the antenna between zero and 95 degrees so it knows where its at. to get it out of the limit, type: pmac #2 pmac o 20 ( it should go up, just let it go into the upper limit) reboot vxworks check the angle with pmac control p
Wed Dec 1 09:09:26 MST 1993 I shorted out the elevation optical stuff going to the pedestal and the antenna performance perked right up. need to wire this better as its just a cable lying on the ground. started working on the schedules for wisp94 and programming the scans
Thu Dec 16 08:26:51 MST 1993
Tue Jan 11 12:00:27 MST 1994 11 Jan. 1994 0900 Arrive at radar. 1000 Print out radar angle, scan, sqd list 1200 Lunch this is a test of the note taker
Tue Jan 18 13:43:45 MST 1994 added two pmac variables, p992 and p993 which are used to set the proportional gain in elevation. P992 is usually set to 700000 and p993 is set to 450000. If the proportional gain is too high the rhi's velocity will not be smooth, and if the proportional gain is set too low, the elevation will not go to where it is supposed to go. You can change the value of p992 and it will affect the elevation gain in sur scans and ppi scans for pointing. You can change the value of p993 and it will affect the elevation gain in rhi scans.
Wed Jan 19 09:43:14 MST 1994
Tue Jan 25 23:01:13 MST 1994 ran a schedule this morning and got this: starting fronts1 schedule terminated : restart_sched checking @ 06:01:expected integer but got "09" but the second time it worked.
Sun Jan 30 11:36:55 MST 1994 cleaned the tape drives today
Tue Feb 8 02:00:28 MST 1994 schedule terminated : ABORTED detailed error: ABORTED while executing "rwait until $theTime - $early" (procedure "wait_item" line 19) invoked from within "wait_item $hour $item" ("foreach" body line 2) invoked from within "foreach item $sublist { wait_item $hour $item }" ("uplevel" body line 39) invoked from within "uplevel 1 $body" ("for" body line 2) invoked from within "for {set i 0} {$i < $count} {incr i} { uplevel 1 $body }" (procedure "repeat" line 2) invoked from within "repeat $count { set tlist [fmtclock [expr [getclock]+14] "%H %M %S"] set hour [lindex $tlist 0] set minute [lindex $tlist 1] set second [lindex ..." (procedure "restart_sched" line 4) invoked from within "restart_sched {{0:00 LOW_SUschedule terminated : ABORTEDschedule terminated : ABOR2} {0:50 LOW_SUR} {1EVAD ABORT 02/08/94 0 RTED:45 RHI_ACTIVE} {3:30 8:18:33detailed error: its still broke!
Tue Feb 8 03:00:54 MST 1994 run_volume ending restart_sched checking @ 09:59:32 schedule terminated : expected integer but got "09" detailed error: expected integer but got "09" (reading value of variable to increment) invoked from within "incr hour" invoked from within "if {$found == 0} { incr hour if {$hour == 24} {set hour 0} }" ("uplevel" body line 32) invoked from within "uplevel 1 $body" ("for" body line 2) invoked from within "for {set i 0} {$i < $count} {incr i} { uplevel 1 $body }" (procedure "repeat" line 2) invoked from within "repeat $count { set tlist [fmtclock [expr [getclock]+14] "%H %M %S"] set hour [lindex $tlist 0] set minute [lindex $tlist 1] set second [lindex ..." (procedure "restart_sched" line 4) invoked from within "restart_sched {{0:00 LOW_SUR2} {0:50 LOW_SUR} {1:45 RH
Thu Feb 24 21:05:14 MST 1994 I came out a couple days ago and changed a couple of pmac variables around. I changed the dac outputs to +-10 volts as the pedestal was having some torque problems in the wind. today I see that the antenna is now scanning better in the wind in azimuth, but not much better in elevation. the wind is still causing some trouble in elevation stability.
Mon Feb 28 11:14:36 MST 1994 changed the file on halyard /etc/dp/conf to use the 303 area code for dialing boulder. restarted the dialer daemon /usr/dp/bin/dpd (remember) this stuff is on halyard, not bibb.
Mon Feb 28 12:55:14 MST 1994 added bowie theatre button to the joepanel radar control panel. I have a copy of the old guy called joepanel.old in case. copied this new guy to /rsg/cband/aux/uxscripts END of LOG