- 94: ADAMs, Site , Mon 25-Sep-2000 18:47:33 PDT, plugged in power to daisy
We moved the generator this afternoon and extended the power cable
to daisy. Unfortunately, we forgot to plug the power cable into
daisy again. I plugged it in around 1837 PDT and daisy is now
running. All daisy sensors operating okay.
- 78: ADAMs, Site , Mon 18-Sep-2000 14:36:04 PDT, testing matrix cards using daisy
We used daisy to test our current
stock of matrix cards, so daisy
was rebooted a few times during the
last hour.
The card marked "marigold" is the
matrix card that we have been
using for the last couple of days,
having swapped it in on Sep. 13.
It is has been involved in a few
periods of flaky behavior on daisy,
although there is no proof that it
has been the cause.
The card marked "daisy" is the one that
we had used up until Sep. 13. It booted
up just fine during the test today. This
is the card that had failed attempting network
access on Sep. 13th. Today however,
the whole ADAM worked fine, with serial
measurements coming in from the Ironics
card.
The unmarked card would boot just fine,
but the backplane network appeared not to
work. I couldn't rlogin into chicory from
aster, or from daisy. rserial did not
work either. During one boot I did see
the message come across the console: "socket
connected to serial card". However, we didn't
get any serial data.
- 75: ADAMs, Site , Sun 17-Sep-2000 15:55:21 PDT, daisy heartburn
Daisy started it's reboot game
around noon.
Eventually it stopped booting at
all. The field terminal showed that
it was completely hung; no response
at all.
Cycled power on it to get it going.
It looks like the current matrix power
supply has an intermittant power switch,
as noted by a post-it note (which disappeared
a couple of days ago).
After cycling the power, reseating the power
supply, and exercising the front panel
power switch, daisy rebooted and has run now
for 90 minutes.
- 71: ADAMs, Site , Sun 17-Sep-2000 06:21:04 PDT, daisy reboot
daisy rebooted several times again yesterday, amounting
to 9 reboots between 1500 and 1800.
Had to restart sonic a.8m and b.8m using reserial.
Sep 16 08:42:36 daisy daisy booted
Sep 16 15:05:42 daisy daisy booted
Sep 16 15:20:06 daisy daisy booted
Sep 16 15:22:08 daisy daisy booted
Sep 16 15:24:00 daisy daisy booted
Sep 16 15:57:17 daisy daisy booted
Sep 16 16:10:17 daisy daisy booted
Sep 16 16:15:22 daisy daisy booted
Sep 16 16:51:07 daisy daisy booted
Sep 16 18:00:26 daisy daisy booted
- 70: ADAMs, Site , Sat 16-Sep-2000 15:34:02 PDT, Daisy rebooted
Daisy rebooted itself 3 times. I restarted sonic a.8m and b.8m,
as well as the propvane at 2m by rserial connection.
- 60: ADAMs, Site , Wed 13-Sep-2000 15:19:44 PDT, how to reconfigure a matrix card
If matrix cards are swapped out in
an adam, the new card needs to be
configured so that it is addressed
correctly on the network.
If you are lucky enough to have
the first card still running,
you can see how it is currently
configured by entering the vxWorks
command:
bootParamsShow 0x700
However, probably the reason you are
changing it is because it is dead.
The two pieces of information that you
need are the IP address of the
matrix card and the IP address of
backplane network that the matrix
card will implement. Let's say that
you are replacing the matrix card known as
daisy. You can look in aster:/etc/hosts to find
the IP address of daisy, and of daisy-bp.
The latter is the backplane IP address.
Once you are armed with this info, you can
use the field terminal plugged into the
ADAM to reconfigure the matrix card.
Just enter the command - be sure to include
the parenss:
bootChange()
A series of questions will be asked
of you. Enter a return after a question
to keep the current value. Enter a period
in order to set a value to a null value.
Here are the questions you will be asked, and
the proper values:
boot device : med
processor number : 0
host name : aster
inet on ethernet (e) : 128.117.80.195:ffffff00
inet on backplane (b) : 128.117.80.196:ffffff00
host inet (h) : 128.117.80.29
user (u) : aster
flags (f) : 0x108
target name (tn) : daisy
The (tn), (e) and (b) parameters are the ones which
will change depending on the particular ADAM that you
are configuring.
- 59: ADAMs, Site , Wed 13-Sep-2000 14:59:42 PDT, daisy restored 1430
Daisy is back online at around 1430.
After the failure this morning, daisy was
not able to restart. It was a problem in the networking
on the matrix card. VxWorks would reboot from
ROM okay, and run it's "startup" task. The startup
task would then hang while trying to connect
to aster. An error message would come forth complaining
that getHosts (via RPC) was failing.
On Gordon's suggestion, I swapped the matrix card
and reconfigured it as daisy. This fixed daisy's problem
immediately, and it has been running fine for the last
couple of hours.
See a following enter for a description on setting the
matrix boot parameters when the matrix cards are swapped.
- 56: ADAMs, Site , Wed 13-Sep-2000 09:37:12 PDT, Replaced Daisy power supply
Daisy stopped again at 0815 PDT. I replaced its power supply
around 0900 PDT, but daisy did not successfully reboot.
- 55: ADAMs, Site , Wed 13-Sep-2000 08:14:48 PDT, Daisy last reboot 7 hours ago
Daisy last rebooted at 01:33:36 PDT, Sept 13. All sensors
appear to have kept running after the reboot.
- 54: ADAMs, Site , Tue 12-Sep-2000 19:05:12 PDT, daisy status
Daisy has had a spate of reboots this afternoon, as reported
in the previous posting.
As with the incident on Sept. 7, some of the sensors had
jammed serial connections. Using rserial, we we able
to reset most of them, but at one point an ati sonic (b.4m)
could not be restarted this way, and we had to cycle its
power to get it running again.
After some of the daisy reboots, different serial sensors
would be jammed. It sure appears that the reboot, or some
other problem, is sending out junk to the serial sensors
and causing their firmware to become confused.
I beleive that this is an old problem; i.e. it sure
sounds familiar.
Daisy has now been running smoothly for almost an hour.
- 53: ADAMs, Site , Tue 12-Sep-2000 17:14:43 PDT, daisy is flaking out
Daisy is rebooting continuously. The ingestors and displays will
start, but no data is received. It seems to have the same problem
that it had on 7 Sep. It started doing this at 1342 (local) today,
and has rebooted 16 times since then.
- 42: ADAMs, Site , Sun 10-Sep-2000 13:13:03 PDT, rserial and rlogin
With a PC connected to the adam console port, bring up procom-plus.
(On the toshiba, pcplus is on the b: drive)
From the VxWorks prompt, rlogin to aster, then run rserial:
-> rlogin "aster" note the quotes around "aster"
Last login...
Sun Micro...
$ASTER: rserial cosmos 200
$ASTER: exit
Use ctrl-c or ctrl-d to exit rserial.
To rlogin into an adam from aster:
rlogin cosmos
VxWorks login: aster
Password: asterize
-> i
-> logout
- 37: ADAMs, Site , Thu 07-Sep-2000 11:52:06 PDT, daisy reboots
Daisy rebooted herself on Sep 6 15:21 PDT, and then four times again
this morning, Sep 7 10:11, 10:12, 10:21, 10:37.
Jan was out at daisy on Sep 6 at 15:00 measuring voltages on the
filter board (debugging krypton). Perhaps a power connection was
bumped.
I tightened the power connectors under the external power supply.
The connector for the adam power was a bit loose, and the AC input
connector was tweaked to the side a bit.
The VME power supply was off (no lights) when the adam was opened,
which I hope is due to low input power because of a loose connector.
This VME power supply is the one with the questionable rocker switch.
(We have a spare VME power supply).
The voltage on an external plug looked OK at 118 V.
I moved the adam power cable to another connector under the external power
supply, and booted daisy. Several serial sensors were not
transmitting (two ATI sonics and one prop), and needed some
nudging with rserial. After bringing up rserial, and hitting
CR, the ATIs display a menu. Enter 0 to exit the menus and enter
run mode. rserial to the prop and hit return until it starts transmitting.