Re: [foxboro] FBM type?

  • From: duc.do@xxxxxxxxxxxxxx
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Mon, 3 Mar 2003 14:54:35 -0500

Alright, Dave, I'm coming clean.

Way back in November I asked this list for a utility to quickly scan my
system for information on FBM serial numbers, with the ultimate goal of
determining the age of all the FBMs in my system. While nobody offered any
readily-available tool, Andreas Weiss gave a tantalizing hint: all the info
I need to know about the FBMs is in the checkpoint file. It's just a
pattern-matching exercise after that.

I wrote a simple script file using strings and nawk to get the info out of
the checkpoint files. Here's a partial output for one of my CP-60s, which
has legacy FBMs attached via FBIs as well as 200-series FBMs attached via
FCMs.

  CP      FBM     Part   Man H/W  S/W  Serial  PROM  H/W
LbugID   LbugID  Number Date Rev  Rev  Number   Lvl Type
21CP04 21A400   P0972AJ 0025  0H 1.09
21CP04 21A400   P0972AJ 0027  0H 1.09
21CP04   210101 P0400DA 9445  0P 42.4 00008285 61.1   01
21CP04   210102 P0400YC 9450  0V 42.4 00007357 61.1   02
21CP04   210103 P0400YC 9531  0V 42.4 00009585 61.1   02
21CP04   210104 P0400YC 9531  0V 42.4 00009589 61.1   02
21CP04   210105 P0400YE 9503  0P 42.3 00007236 61.1   04
21CP04 21B400   P0972AJ 0025  0H 1.09
21CP04 21B400   P0972AJ 0027  0G 1.09
21CP04   210116 P0902XA 9812  0C 41.1 00002968 61.1  41A
21CP04   210118 P0400YE 9512  0P 42.3 00009029 61.1   04
21CP04   210201 P0400DA 9640  0L 42.4 00003594 61.1   01
21CP04   210202 P0400DA 9640  0L 42.4 00003603 61.1   01
21CP04 21C400   P0972AJ 0025  0H 1.09
21CP04 21C400   P0972AJ 0025  0H 1.09
21CP04   210210 P0400YE 9512  0P 42.3 00009098 61.1   04
21CP04   210211 CM400YL 9301  0B 41.1 00005098 61.1   10
21CP04 21D400   P0916CP 0140  0D 1.09
21CP04 21D400   P0916CP 0140  0D 1.09
21CP04   21D401 P0914SY 0139  0D 1.04 01397360 1.04  204
21CP04   21D402 P0914SQ 0139  0D 1.04 01392762 1.04  201
21CP04   21D403 P0914SQ 0139  0D 1.04 01392769 1.04  201
21CP04   21D404 P0914SQ 0139  0D 1.04 01392874 1.04  201
21CP04 21E400   P0916CP 0140  0D 1.09
21CP04 21E400   P0916CP 0025  0D 1.09
21CP04   21E401 P0914TG 0024  0C 1.04 00241052 1.04  241
21CP04   21E402 P0914TG 0108  0C 1.04 01081645 1.04  241
21CP04   21E403 P0914SY 0025  0E 1.04 00254043 1.04  204

The manufacturing date is what I wanted, but since everything else is
readily available, I print it all out just because I can.

The way I differentiate between the legacy FBMs, 200-series FBMs, and
FCM/FBI is by relying on our naming convention (FCM/FBI ends with 00; legacy
FBMs have all-numeric letterbug IDs, while the 200-series FBMs have an alpha
character in the 3rd position). This works great for us but it wouldn't work
for anybody else.

Hence the need to generically determine the FBM type, so that this tool can
used by everybody. Anybody has a use for something like this?

Now you know the rest of the story.

Duc

BTW, I found one of my FBMs was manufactured in the 50th week of 1987. Now
that's old!


-----Original Message-----
From: David Johnson [mailto:DRJohn@xxxxxxxxxx]
Sent: Monday, March 03, 2003 1:18 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM type?


Duc,

As Chuck Jones' button said, "You guys start writing code, I'll go see what 
they want."

Since I (we?) don't understand the ultimate goal, there are a lot ways to 
do this.

You could use /opt/fox/bin/tools/omget C:B.HWTYPE if you just want a 
utility to check an individual FBM.

Or, as suggested, something with the iccdrvr.tsk for bulk testing.

But it sounds like you are looking for something a little beyond the 
obvious answers.

David


"Quote me as saying I was misquoted."
Groucho Marx

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
 
 
_______________________________________________________________________
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:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: