ISCAT00: adam_field_computer Messages: 38 Entries..

I restarted the adam this evening and it seems to be running.  Collecting data from everything.  The NO inlets are buried in the snow right now.

The box temperature did not seem too warm - it certainly is warm around the heating plate, but the exhaust of the fan is < 30C.  I do not know where the T measurement is made - but, if it is on or near the heating plate I can understand the apparent elevated T.  Bottomline - the system is working and not steaming so I will leave it alone.

the tbox.ragwort seems to be off scale - I will check on that soon.

The adam is located on the ground, not tower.
Sensors are attached and running.

A ups was tried and failed. Marty and I haulde
it back to the building and will run tests.

I have one more matrix card I can try.
Why not!

I tried my last card, the datel. Ragwort
survived about 20 minutes then went down.
My last plan is to bring the adam back to the
building.

It doesn't want to stay up. My most recent
change was replacing the Ironic card. It still
goes down. It often reboots itself.

The plane is gone, so I started ragwort agian.
May the South Pole Gods look upon us in favor.
NOTE: fans are still off.

It should be noted that a plane landed in the last
10 minutes. Could this problem be all related to RF'
interference from the plane communication?

refer to message 90

It seems this adam wants to go home with me!
This is my latest change. The adam is getting power
directly from an AC outlet. The fans and sensors (12 volts)
are getting power through the power distribution box.

Creash again, decide to run with 22m fan off.

I replaced ragwort with cosmos.
We have been running for about 20 minutes and
have not crashed.
I will turn the TRH fans back on.

Ragwort still up and down. I have changed the
power supply for the VME. Did not help. One thought
is some RF interferenc from the planes. There has been
a number of flights today. A plane just took off
and we will restart it. Keep your fingers crossed.

I have restarted ragwort with a ground to tower and
no fans runnng.
time ~17:30 local

Ragwort continues to crash. The only thing I can
relat it to is the increase in blowing crystals.
may be a lot of static charge? We will ground the box to
the tower.

Ragwort went down at 14:45 local. It is back
up at 15:50 local. The only clue in ISSlog is
Nov 29 14:43:53 asteroid ragwort[2840]: ragwort select timeout 300 sec
Nov 29 14:48:53 asteroid ragwort[2840]: ragwort select timeout 300 sec
Nov 29 14:53:53 asteroid ragwort[2840]: ragwort select timeout 900 sec. Ingest stopping

I could not ping ragwort so I did a hard reboot.

The adam is back up and running. The problem
was power via the TRH fans. Would you believe
RF interference? That is the best guess. With
the long fan cables running up the tower, they
act like antennas. Everything worked ok during
the IC because those fan cables were at the ground.

The ADAM an the night outside on the deck.
There were 2 TRHs attached. It appeared to have no
problems. I had changed the muffin fan because it was
noisy. I hope the problem was due to this fan and power.
Will do some more testing on the deck before moving
out to the tower.

As one can see in the data, ragwort is down.
I have replaced the fiber. Wired it inside the box
since the other fiber connectors had gone bad.
The adam runs for a short time then stops. It even
reboots its self. I have tried different combinations
of boards with the same result.
My next thought was a power problem at the tower. This
problem started when Marty installed his system. So
I tried a different outlet and still the same results.
Right now the ADAM is outside the building. The same
optic cable is hooked up. There are no serial sensors
attached.

The heater is on in the ADAM.

I have ping running to yarrow. It seems a long
time, about 10msec. It hasn't crashed since I started
pinging it. I am going to let it keep pinging
while I go get something to eat.

As usual, when you want things to run they don't!
Ragwort has been a pain every since the move to profile.
I have tried changing matrix and ironic cards. I believe
the problem is something between yarrow and ragwort.
It boots up ok then crashes.I am able to ping ragwort
but not yarrow.

Ragwort went down during the move from IC mode to
Profile mode. Maybe a power glitch while moving the
fan power cables. I had to do a manual reboot to get it
going.

I just replaced the 16 channel with the 8 channel.
I also turned on the 100 watt heater to see how warm it
gets inside.

Yarrow went down again. I may switch back
to the 8 channel card. Maybe it is a temperature
related thing. I do not remember testing a 16 channel
card in the cold. The box temperature is around 4C.
I rebooted ragwort from the base. Yarrow still did not
come up. I am going to change back to the 8 channel card.

Yarrow went down for some reason. An mxreset did not
get the adam going. I did a hard reset and the adam came
back up.

I have changed back to the Ironic 16 channel card.
System is running

Second 8 channel Ironic is given good data rates.
I will plan to hand carry back to 16 channel card.

The 8 channel Ironic looks good. We are getting
20 hz data.
I am going to test the other 8 channel card.

The 16 channel board worked fine for proper data
rates. I have changed to the 8 channel and restarted
ragwort.

Gordon found a bug in the ingest program and made a fix.
Things look better. We will let it run for a period of time
with the 16 channel card.

I have replaced the 8 channel Ironic with the 16 channel board.
Lets hope this takes care of the throughput problem.

Steve O notice the sampling frequency for the
data was a little slow. He talked to Gordon about it,
and Gordon thought it may have to due with the sonics
being at the end of the serial channel assignments because
those channels got serviced last in the interrupt sequence.
So, I did some changes in the ADAM box and the sonics are
now on 200 and 201. The TRHs are channel 202 thu 207.
Will monitor with data_stats.

I took ragwort done to fix channel 207's communication
problem. A jumper was needed on the serial interface board.

The adam has been running for the last 4 to 5 hours without any problems.
All sensors are giving reasonable data. I'll let the system run over night.
There has been one funny response in the ISFFlog.
ragwort ingest socket write to asteroid.33177:Resource temporarily unavailable.
This has been occurring about every 7 to 8 minutes.
A question for Gordon!

I moved the test outside because the vme box was getting
hot. Will let it run for awhile.