Re: [foxboro] COMM 10 not rebooting

Kashif,

Have you gotten this to work yet?

Red-green LEDs should mean the module is trying to boot.  In my
experience the most common causes for a module not successfully trying
to boot are:
1) Letterbug or nosecone problem so that actual letterbug is different
from the letterbug that the module thinks it has.  From a VT100 window
type:
snoop -x 0 01:00:6c:0f:0f:0f
and reset the module.  Within a few seconds you should see the boot
requests.  The letterbug that the module thinks it has should wrap
around the last two lines of each boot request packet shown.  Make
sure it matches your physical letterbug - bent pins, short or long
pins or problems in the nosecone can cause the letterbug to be
misinterpreted.
2) For some reason the host AW does not know it's supposed to boot the
modules.  On the host AW in a VT100 window, type:
/usr/fox/swi/ds_stasict LETTERBUG
where LETTERBUG is the letterbug of your COMM10 to see if it knows
it's supposed to boot it.  You should get a list of the files used for
booting this module.
3) Check that the required processes: "lsap_dsp", "romload_svr", and
"mles" are running on the host AW - I've periodically seen problems
with "mles" not running.  They can be restarted if not running, but
I'd normally just reboot the host AW.
4) The host AW is not communicating properly on the network, or there
is some kind of comm problem between the AW and your COMM10 module's
slot.  Try booting the COMM10 with a letterbug of CSBOOT (especially
if there is only one host AW on the system)

Regards,

Kevin FitzGerrell
On Dec 16, 2007 3:52 PM, Kashif Ijaz <kashifijaz93@xxxxxxxxxxx> wrote:
>
> My print commands were not working on I/A version 7.1.1. I cancelled all the 
> print requests and then rebooted my COMM 10 processor (P0400-VP). But it's 
> red and green LEDs remain on continously. I have tried hardware reset switch 
> on the module.
>
> I replaced the station with identical spare but the still the same status. 
> Tried replacing the letterbugs with spare ones but still behaving same.
>
> When I try to reboot from SMDH, message " INVALID STATION STATE FOR 
> OPERATION".
>
> Can anyone help on this.
>
> REgards,
>
> Kashif Ijaz
> INTECH Process Automation
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: