type_base_system_entries
Return to Logbook Contents Page
Entry | Date | Title | Site | Author | #Graphics |
---|---|---|---|---|---|
14 | Fri 18-Jun-2004 | CUFF Breezecom antenna change | base | semmer | |
9 | Tue 15-Jun-2004 | data system time | all | maclean |
- 14: base_system, Site base, Fri 18-Jun-2004 17:01:36 MDT, CUFF Breezecom antenna change
-
I did some work on the antenna at the base of the cuff tower. The omni was attached to a boom. The signal strength at willow is now around 50% in rain conditions. The FCS error is at 14%. This is an improvement however not as good as the directional. WIll see how things run over the weekend.
- 9: base_system, Site all, Tue 15-Jun-2004 20:11:19 MDT, data system time
-
NTP is being used to set all computer clocks: the base system clock on aster and the data system clocks on the prometheii. Aster uses the NTP server utcnist.colorado.edu (which I found by searching the public ntp server link at www.ntp.org). Here is the ntp.conf on aster: server utcnist.colorado.edu # 4 classes of syslog messages: clock,peer,sys,sync # 4 types of messages in classes: info,events,statistics,status # class or type can be all # =: set syslog mask, +: add logconfig =syncstatus +sysevents driftfile /etc/ntp/drift The prometheii then use aster as their ntp server. On bootup (in /etc/rc.sysinit) they first do rdate aster then later they do ntpdate aster then finally they run ntpd, with the following /etc/ntp.conf: server aster logconfig =syncall +sysall +peerall +clockall driftfile /var/run/ntp.drift At first cosmos did not have the rtc.o module and was not initializing the system clock from the battery-backed clock. That is fixed now.
CME04 Publications
Data Access
Facilities & Instruments