system log

Hi,

I have an embedded pc-104 stack running qnx on a helicopter. I am
connecting to the stack using 802.11b. Sometimes I loose network
connectivity to the stack , and the only way to regain connectivity is
to reboot the stack. This happens only during testing of the helicopter.
Since we test the helicopter in the filed I am not able to connect it to
a monitor. I am thinking that there might be a problem either with the
power connecotr or the network driver.

I would like to test whether the stack is loosing power every time we
loose connectivity or whether it is some other proble. Is there an easy
way to log data in the system such that I can tell when the computer
rebooted or if the network crashed. The sloginfo gives only the recent
information after a reboot, but I would like to know things like when
the last reboot was.

Any help would be appreciated.

Thanks
Srikanth

I have an embedded pc-104 stack running qnx on a helicopter. I am
connecting to the stack using 802.11b. Sometimes I loose network
connectivity to the stack , and the only way to regain connectivity is
to reboot the stack. This happens only during testing of the helicopter.
Since we test the helicopter in the filed I am not able to connect it to
a monitor. I am thinking that there might be a problem either with the
power connecotr or the network driver.

What we did in WARG (http://ece.uwaterloo.ca/~warg/) was have a serial
connection you can debug on should there be a network failure. Are you
guys trying to use a stock 802.11b device on the 'copter?

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

“Srikanth Saripalli” <srik@robotics.usc.edu> wrote in message
news:3DC330D5.3040501@robotics.usc.edu

Hi,

I have an embedded pc-104 stack running qnx on a helicopter. I am
connecting to the stack using 802.11b. Sometimes I loose network
connectivity to the stack , and the only way to regain connectivity is
to reboot the stack. This happens only during testing of the helicopter.
Since we test the helicopter in the filed I am not able to connect it to
a monitor. I am thinking that there might be a problem either with the
power connecotr or the network driver.

I would like to test whether the stack is loosing power every time we
loose connectivity or whether it is some other proble. Is there an easy
way to log data in the system such that I can tell when the computer
rebooted or if the network crashed. The sloginfo gives only the recent
information after a reboot, but I would like to know things like when
the last reboot was.

First you need some device to write to, flash, hardisk, sram, etc, or even
better as Chris suggested output of serial port you can log.
You could have some software that monitor activity and log when something
goes wrong.

Best way to log reboot is to store date and time each time the machine
boots, it will be up to you to analyse the data and figure out if cause of
booting was normal or not. However unless you have some special hardware I
don’t beleive you can tell if it’s a warm or cold boot (I vaguely remember
some variable in bios area that can tell if it’s warm or cold boot, not sure
if it standard or not).

As for program crash, I like to monitor for any program that sigsegv (that
includes io-net) and log the info. Under QNX6 I don’t know how to do that
(but I know it’s possible), if you have enough space you could run dumper
and after you reboot check if dumper as created a file.

Hope this help

Any help would be appreciated.

Thanks
Srikanth

As for program crash, I like to monitor for any program that sigsegv (that
includes io-net) and log the info. Under QNX6 I don’t know how to do that
(but I know it’s possible), if you have enough space you could run dumper
and after you reboot check if dumper as created a file.

dumper has the -m option to suppress dumping of memory(ie only the status and
registers),whcih might still be useful to track down a culprit.

\

cburgess@qnx.com