Re: Protecting Environments
Have a look at B0193MQ (Display Engineering for 50 Series). This document covers these topics. It explains how to protect you environments. If this does not solve your issue and you are using DM, you can try to have a double set of environments. This would leave you with two sets, one for instance in the default location: "/usr/fox/sys/Change_Env", and one in, for instance, "/usr/fox/remote_oper/sys/Change_Env". When you refer to this location in the "/usr/fox/customer/hi/dmcfg" file you get something like this in the DM configuration section of the file: TYPEfoxDefault DSM O - TYPE_DEFAULTDSM O Proc_Op_Env TYPEOperatorDSM B Proc_Op_Env TYPEAuxillaryOper QLRSM O Proc_Op_Env TYPERemoteOperator DSM O /usr/fox/remote_oper/sys/Change_Env/Proc_Op_Env TYPEEngineerDSM E Proc_Eng_Env Now you can have a "safe" set of environments in /usr/fox/remote_oper/sys/Change_Env. This won't go with FoxView however. Regards Ron Deen (Foxboro) Stefano Persico wrote: >hi list >is it possible to have on an AW51 and on a Xterminal connected to the >same environment unprotected in AW and protected on XTerm ??? > >Thanks >My contact >Persico Stefano >Tel +39 586 9488514 >No Fax >[EMAIL PROTECTED] > > >--- >This list is neither sponsored nor endorsed by the Foxboro Company. All >postings from this list are the work of list subscribers and no warranty >is made or implied as to the accuracy of any information disseminated >through this medium. By subscribing to this list you agree to hold the >list sponsor(s) blameless for any and all mishaps which might occur due to >your application of information received from this mailing list. > >To be removed from this list, send mail to >[EMAIL PROTECTED] >with "unsubscribe foxboro" in the Subject. Or, send any mail to >[EMAIL PROTECTED] > > --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: Remote Displays
Hummingbird is just fine, but you need a UNIX system for that to work. Windows is not capable of remote displaying proces graphics. You can opt for packages like PCAnywhere or (what we at Foxboro user) NetOp. These packages "take over" the screen and display this to another Windows machine. (either simultaniously or on one screen only). Advantage: you get the same exact screen the operator gets. Disadvantage: you don't get an additional workplace. Foxboro has the server 70 solution which will allow for more than one user connected to a server. This will get you the additional screens you may want. It is NT though. Ron Deen Foxboro Nederland N.V. Moss, Bruce B EQUILON wrote: > Hi List, > I have a I/A system consisting of Micro I/A's, AW70's and WP70's. >How can I get process displays (for read only purpose)to desktop PC's? I see >hummingbird exceed mentioned in some notes. Is that the only option? How >much should I expect to spend for the necessary software? >Thanks. > > G. Bruce Moss > Equilon Enterprises-( WICS) > Westhollow Instrumentation & Control Systems Group > * (281) 544-6212 > Pgr. (877) 242-0497 > * [EMAIL PROTECTED] > (c) ALL RIGHTS RESERVED EQUILON ENTERPRISES LLC 2001 > >--- >This list is neither sponsored nor endorsed by the Foxboro Company. All >postings from this list are the work of list subscribers and no warranty >is made or implied as to the accuracy of any information disseminated >through this medium. By subscribing to this list you agree to hold the >list sponsor(s) blameless for any and all mishaps which might occur due to >your application of information received from this mailing list. > >To be removed from this list, send mail to >[EMAIL PROTECTED] >with "unsubscribe foxboro" in the Subject. Or, send any mail to >[EMAIL PROTECTED] > > --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: Cron
Never edit the "crontab" files without the use of "crontab". "crontab" sends a signal to "cron" that the "crontab" file has changed so "cron" knows what to do. Most convinient (I use the vi editor): set the "EDITOR" variable to reflect the editor you want to use: In the Bourne shell: EDITOR=vi; export EDITOR In the csh: setenv EDITOR vi And then run "crontab -l", to see what you "crontab" file looks like. Run "crontab -e", to edit the "crontab" file Every user has it's own "crontab" file so make sure you login as the correct user. Sun recommends NOT to use "su" because the system can get confused. Be very carefull though with "crontab". Regards Ron Deen dhawly hawpyt wrote: > Hello, > >After editing /var/spool/cron/crontab/root file to execute a Script at > regular interval it is required to reboot AW?If no than what is to be done? > >I just tried by killing cron process and then again writing cron command > but it gives some FIFO error.What is that? > > Regards , > > Sawly Hawl > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: AW: Remote Backups of AW70
I'm not really sure but I thought I read that Ghost 7.0 (Enterprise Edition) can Ghost to a FAT32 partition. This would make the space to store a bit larger. Ron Deen "Weiss, Andreas" wrote: > Sorry, > I've wrote faster as thought. > > Well, you need a second or third disk with a FAT filesystem. > > Andreas > > -Ursprüngliche Nachricht- > Von: Stephan Meyer [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 5. September 2001 14:34 > An: 'Foxboro DCS Mail List' > Betreff: RE: Remote Backups of AW70 > > Ron, > > I use Norton Ghost to backup my hard drives. It does not support NTFS > and only works for FAT16/32. It also requires that the disk is not in > use, meaning that none of the files are in use, which is usually not the > case in a running machine. > > Stephan Meyer > CAE-Tools, Inc. > 781 784 3368 > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > [EMAIL PROTECTED] > Sent: Wednesday, September 05, 2001 8:21 AM > To: Foxboro DCS Mail List > Cc: [EMAIL PROTECTED] > Subject: Re: Remote Backups of AW70 > > I envision installing something like ghost on my server that is > connected > to all of my 70 boxes with secondary NIC's. Then having the server to > automatically backup each remote box triggered by a scheduler. > Basically > hands-off automatic backups of remote boxes by the server. > > > > Ron Deen <[EMAIL PROTECTED]> > > Sent by: To: Foxboro > DCS Mail List > <[EMAIL PROTECTED] > <[EMAIL PROTECTED]> > oject.org> cc: > > Subject: > Re: Remote Backups of AW70 > > > 09/05/01 12:30 AM > > Please respond to "Foxboro > > DCS Mail List" > > > > > > What do you mean with "remote backups"? > > Take control of the remote 70 series station and make a backup (local or > remote) > or > Take local control of the 70 series station and make the backup to > remote > location (a server for example)? > > Ron Deen > > [EMAIL PROTECTED] wrote: > > > If anyone is doing this, I would like to get the nitty gritty details > of > > doing this. My understanding is that the latest version of Ghost > should > > make this doable. > > > > Thanks, Sam > > > > > --- > > This list is neither sponsored nor endorsed by the Foxboro Company. > All > > postings from this list are the work of list subscribers and no > warranty > > is made or implied as to the accuracy of any information disseminated > > through this medium. By subscribing to this list you agree to hold the > > list sponsor(s) blameless for any and all mishaps which might occur > due > to > > your application of information received from this mailing list. > > > > To be removed from this list, send mail to > > [EMAIL PROTECTED] > > with "unsubscribe foxboro" in the Subject. Or, send any mail to > > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due > to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due > to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] > > -
Re: Remote Backups of AW70
What do you mean with "remote backups"? Take control of the remote 70 series station and make a backup (local or remote) or Take local control of the 70 series station and make the backup to remote location (a server for example)? Ron Deen [EMAIL PROTECTED] wrote: > If anyone is doing this, I would like to get the nitty gritty details of > doing this. My understanding is that the latest version of Ghost should > make this doable. > > Thanks, Sam > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: Speaking of Save_All
I'm not sure about the name, but I think on the harddrive in the save_all directory, there's a file named "compound.dir" which contains the names (in order) of the compounds to be loaded. This is the same sequence as they appear in in ICC. Follow that list to create the diskette and you will be assured that the compounds will be loaded in the same sequence. I believe ECB's still go first, put these on the first diskette. Load_all's can be performed from the commandline too. Go to /opt/fox/ciocfg/api and run load_all for some usage info. The command take two arguments: "station" and "location/station" or the other way around, I can never remember. I could have them mixed up but I think: load_all / comes close. You should not need it too often I hope... Regards Ron Deen@home "Stear, Bo" wrote: > I suspected as much. Is there anything special about savealls that span more than >one disk? just copy the directories to multiple disks however they may fit? > > -Original Message- > From: David Johnson [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 04, 2001 7:45 AM > To: Foxboro DCS Mail List > Subject: Re: Speaking of Save_All > > Bo, > > You should be able to do a cp -r on the directory that you put the save-all in. > > If the save_all command for CP3001 was: > save_all CP3001 /tmp/CP3001 > > Insert a BLANK FORMATTED Solaris diskette > Mount it on /f0 > cp -r /tmp/CP3001/* /f0 > > and that should do it. > > David > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: CP30 to CP60 upgrade
I noticed you have CP60FT. The filedbus cabling can be confusing and you may have both fieldbusses connected to eachother. Take care of termination and as mentioned here: do not branch. Termination will not be correct. Only two must be installed per fieldbus. Ron Campbell John C wrote: > Yes they were all updated. This doesn't seem to be the problem, but we'll > keep checking. > > Thanks for your assistance. > > John > > > > > I know all FBM's require EEPROM update for version 6.2.1. But you have done > that > I guess... > > Ron Deen > > Campbell John C wrote: > > > We are currently upgrading one of our sites from a CP30FT to a CP60FT and > > are experiencing some difficulties. The actual upgrade went relatively > > smoothly but after the AW was placed back on line with the new CP60's we > > started to receive numerous fieldbus failure alarms (PIOBUS A/B) that > would > > randomly come in and out. Sometimes we would have no alarms for about 1/2 > > hour and then continuous alarms for the next 20 minutes. There was no > > pattern as to when the alarms would occur. Occasionally when the alarms > > occurred we would lose communication to the fieldbus altogether (blue flu > on > > the operator screen). Until we do some more detail investigations (with > Fox > > Mass.) we have gone back to the old CP30 system. > > > > Has anyone else experienced similar problems and what did you do to get > > around it. > > > > Some back ground information: The switchover is being performed at the > same > > time as a revision upgrade from 6.1 to 6.2.1 on a AW/WP51B system. All > > fieldbus modules are of the traditional rack mounted type (no din rail > > mounted modules). > > > > Much appreciation for any assistance. > > > > John Campbell > > Dofasco > > [EMAIL PROTECTED] > > > > --- > > This list is neither sponsored nor endorsed by the Foxboro Company. All > > postings from this list are the work of list subscribers and no warranty > > is made or implied as to the accuracy of any information disseminated > > through this medium. By subscribing to this list you agree to hold the > > list sponsor(s) blameless for any and all mishaps which might occur due to > > your application of information received from this mailing list. > > > > To be removed from this list, send mail to > > [EMAIL PROTECTED] > > with "unsubscribe foxboro" in the Subject. Or, send any mail to > > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: /etc/wplns and /etc/aplns or Sigh... I fired off withoutthin king
There's always an excuse Ron "Johnson, Alex (Foxboro)" wrote: > I forgot about AWs. Sigh... > > I'm in the UK, think I can blame jet lag? > > Regards, > > Alex Johnson > 10707 Haddington > Houston, TX 77043 > 713.722.2859 (office) > 713.722.2700 (switchboard) > 713.932.0222 (fax) > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > -Original Message- > From: Ron Deen [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, May 03, 2001 6:41 PM > To: Foxboro DCS Mail List > Subject:Re: /etc/wplns and /etc/aplns > > The /etc/wplns file contains the logical names of the WP's on your > system. The > /etc/aplns contains (you might have guessed) the logical names of > the AP in you > system. > If you have only AP's and WP's you would normally use the letterbug > as the > logical name. > If you have AW's you have a problem: the AW containss a logical AP > AND a logical > WP and only one can be be letterbug name. This is why you may see > "strange " > names on you system. Some time you can have a letterbug AW0101 which > will have > aplns: AW0101 and wplns: AWWP01 for instance. > > Solved problem?? > > Ron Deen > > Stan Brown wrote: > > > I have some utilites thta check varios system stauses on a given > Foxboro > > node. > > > > I am trying to deploy these on a newly installed node, here. These > utilites > > use the files /etc/wplns and /etc/aplns to determine what > computers are > > supposed to exist on the node. > > > > On this node there seem to be 2 entries for non existent machines > in > > /etc/wplns. Should this not be a reliable way to determine this? > > > > -- > > Stan Brown [EMAIL PROTECTED] > 843-745-3154 > > Charleston SC. > > -- > > Windows 98: n. > > useless extension to a minor patch release for 32-bit > extensions and > > a graphical shell for a 16-bit patch to an 8-bit operating > system > > originally coded for a 4-bit microprocessor, written by a > 2-bit > > company that can't stand for 1 bit of competition. > > - > > (c) 2000 Stan Brown. Redistribution via the Microsoft Network is > prohibited. > > > > > --- > > This list is neither sponsored nor endorsed by the Foxboro > Company. All > > postings from this list are the work of list subscribers and no > warranty > > is made or implied as to the accuracy of any information > disseminated > > through this medium. By subscribing to this list you agree to hold > the > > list sponsor(s) blameless for any and all mishaps which might > occur due to > > your application of information received from this mailing list. > > > > To be removed from this list, send mail to > > [EMAIL PROTECTED] > > with "unsubscribe foxboro" in the Subject. Or, send any mail to > > [EMAIL PROTECTED] > > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. > All > postings from this list are the work of list subscribers and no > warranty > is made or implied as to the accuracy of any information > disseminated > through this medium. By subscribing to this list you agree to hold > the > list sponsor(s) blameless for any and all mishaps which might occur > due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information receive
Re: /etc/wplns and /etc/aplns
The /etc/wplns file contains the logical names of the WP's on your system. The /etc/aplns contains (you might have guessed) the logical names of the AP in you system. If you have only AP's and WP's you would normally use the letterbug as the logical name. If you have AW's you have a problem: the AW containss a logical AP AND a logical WP and only one can be be letterbug name. This is why you may see "strange " names on you system. Some time you can have a letterbug AW0101 which will have aplns: AW0101 and wplns: AWWP01 for instance. Solved problem?? Ron Deen Stan Brown wrote: > I have some utilites thta check varios system stauses on a given Foxboro > node. > > I am trying to deploy these on a newly installed node, here. These utilites > use the files /etc/wplns and /etc/aplns to determine what computers are > supposed to exist on the node. > > On this node there seem to be 2 entries for non existent machines in > /etc/wplns. Should this not be a reliable way to determine this? > > -- > Stan Brown [EMAIL PROTECTED]843-745-3154 > Charleston SC. > -- > Windows 98: n. > useless extension to a minor patch release for 32-bit extensions and > a graphical shell for a 16-bit patch to an 8-bit operating system > originally coded for a 4-bit microprocessor, written by a 2-bit > company that can't stand for 1 bit of competition. > - > (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: Remote Displays using Exceed
My experience with Windows 2000 is limited, but the Foxboro box does not really care too much if you are in the hosts file or not. The DM usage display does not really know what to show in the field in the display that tells you where the DM is running. The go_dm script will find out which IP address is requesting the DM and send it over.(I works like this in our office where the PC use DHCP and the Foxboro boxes do not) The "connection closed" thingy is something else. DM and Foxview do not keep the connection alive by themselve and for that reason I always set the "close connection timeout" to "minus one" (-1) in the xstart window. You can find this setting under the "Other..." button. The default value is 10 sec, you should change this to "-1" which results in "no timeout" This should have been a problem before though and you mention you used an xstart session you have always used? I'm trying to find the time to install exceed 7.0 in W2K soon. I know I did NOT see this problem with exceed 6.2 and Windows 2000. Tried the admin account as well as the operator account I created on the box. No problems with that. Is the version exceed you are using fit for Windows 2000? I thing exceed 7 is the first to be native for Windows 2000. Hope this helps. Ron Deen "Joe Gale (MP)" wrote: > We have been using exceed for years to open remote display managers using > the telnet start method without much for problems. The IT people have been > upgrading the PC's in the plant with new PC's that are running Windows2000 > and have been having problems opening a DM after installing exceed. Several > have worked by installing exceed while logged in as Power User, while some > didn't work that way either. The error they get is a "connection closed(3)" > when trying to open a DM. They are able to open a x-window into another > application (a unit optimization program) running on a non Foxboro sun box > without a problem. The new installs are using the same xstart and xconfig > setups as the older installs are using. Does anyone have any ideas on what > may be the conflict here? > > Thank You, > > Joe Gale > > DCS Administrator > Minnesota Power > Boswell Energy Center > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: CP30 to CP60 upgrade
I know all FBM's require EEPROM update for version 6.2.1. But you have done that I guess... Ron Deen Campbell John C wrote: > We are currently upgrading one of our sites from a CP30FT to a CP60FT and > are experiencing some difficulties. The actual upgrade went relatively > smoothly but after the AW was placed back on line with the new CP60's we > started to receive numerous fieldbus failure alarms (PIOBUS A/B) that would > randomly come in and out. Sometimes we would have no alarms for about 1/2 > hour and then continuous alarms for the next 20 minutes. There was no > pattern as to when the alarms would occur. Occasionally when the alarms > occurred we would lose communication to the fieldbus altogether (blue flu on > the operator screen). Until we do some more detail investigations (with Fox > Mass.) we have gone back to the old CP30 system. > > Has anyone else experienced similar problems and what did you do to get > around it. > > Some back ground information: The switchover is being performed at the same > time as a revision upgrade from 6.1 to 6.2.1 on a AW/WP51B system. All > fieldbus modules are of the traditional rack mounted type (no din rail > mounted modules). > > Much appreciation for any assistance. > > John Campbell > Dofasco > [EMAIL PROTECTED] > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: save_all.sh failers on new node
Hi Stan, Wat type of module is the FoxWatch module? I would not expect a comms processor to be in /etc/cplns on the system. (FOXWATCH is usually a COMM10 and does not contain a control database) Was the system configuration passed through all stations? (just to sync the system files like /etc/cplns, /etc/aplns, the hosts table, System Monitor files and the like, on all of them). I do not have an Allen-Bradly station at hand and of course the thing you cannot test will fail! Can it be CSA died on you? I will have to check tomorrow since I don't have a lab at home, sorry. The log will be of some help. Ron Deen@home Stan Brown wrote: > One of the other groups here, has just put in a new Foxboro node, and I was > seting up save_all.sh to autobackup the control config's for them. > > However, much to my suprise it failed to bacxkup the AB integrator, and > FoxWatch modules on that node. > > Her's the log: > > Save-all for all stations in /etc/cplns selected > Stations selected for save_all: > Station Host name > CP0101 AW0101 > CP0102 AW0101 > AB0101 AW0101 > FOXW01 AW0101 > Checking directories... > Creating directory /opt/SAVEALLS > Creating directory /opt/SAVEALLS/backup > Creating directory for CP0101... > Creating directory for CP0102... > Creating directory for AB0101... > Creating directory for FOXW01... > All directories OK. > Checking for available diskspace > Available space on system: 12910445 > Space required on system: 8000 > Enough space available, continuing... > # > # Automatic save-all procedure started > # Date: Thu May 3 07:58:48 GMT 2001 > # Started on: AW0101 > # Save-all Location: /opt/SAVEALLS > # Backup location:/opt/SAVEALLS/backup > # > # > # Save_all starting for: CP0101 on AW0101 > # > No previously stored save-all found to backup. Continuing... > Starting upload/checkpoint... > Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 > DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 > DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 > DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 > DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 > DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 > DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 > upload/checkpoint Complete > Save_all for CP0101 started > Save-all for CP0101 successfully completed. > # > # Save_all starting for: CP0102 on AW0101 > # > No previously stored save-all found to backup. Continuing... > Starting upload/checkpoint... > Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 > DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 > DONE 2 UPLOAD CP0102!: Thu May 3 08:51:03 2001 > DONE 3 SHRINK CP0102!: Thu May 3 08:51:04 2001 > DONE 4 CHECKPOINT CP0102!: Thu May 3 08:52:12 2001 > DONE 5 CLOSE CP0102!: Thu May 3 08:52:12 2001 > DONE 6 EXIT CP0102!: Thu May 3 08:52:12 2001 > upload/checkpoint Complete > Save_all for CP0102 started > Save-all for CP0102 successfully completed. > # > # Save_all starting for: AB0101 on AW0101 > # > No previously stored save-all found to backup. Continuing... > Starting upload/checkpoint... > Thu May 3 08:52:33 GMT 2001 --- upload and checkpoint AB0101 > DONE 1 OPEN AB0101!: Thu May 3 08:52:33 2001 > DONE 2 UPLOAD AB0101!: Thu May 3 09:16:33 2001 > DONE 3 SHRINK AB0101!: Thu May 3 09:16:34 2001 > DONE 4 CHECKPOINT AB0101!: Thu May 3 09:19:49 2001 > DONE 5 CLOSE AB0101!: Thu May 3 09:19:49 2001 > DONE 6 EXIT AB0101!: Thu May 3 09:19:49 2001 > upload/checkpoint Complete > Save_all for AB0101 started > There were errors for AB0101. > FAIL 1 open AB0101!: Thu May 3 09:19:50 2001 -14 ICCopen error: class= 1 error= >0 text= icConnectCp: icCpConnect problem > # > # Save_all starting for: FOXW01 on AW0101 > # > No previously stored save-all found to backup. Continuing... > Starting upload/checkpoint... > Thu May 3 09:19:58 GMT 2001 --- upload and checkpoint FOXW01 > FAIL 1 OPEN FOXW01!: Thu May 3 09:19:58 2001 -14 ICCopen error: class= 1 error= >0 text= icConnectCp: icCpConnec
Re: AW51D with RAID Drive
I have come across several RAID units in the field some on 51E's and some on 51D (either AP or AW) I have also seen these problems you mention. However, beeing very critical about these units, I have learnt that installation if the things is a VERY DELICATE matter. Except for one case (where the RAID SCSI controller cabinet was defective) all of the problems I have seen where due to poor installation. In all of the cases the problem was either caused by bent pins on the SCSI cables (including the interconnection cables on the RAID unit itself) Be aware that the damageg cable can (and at least once has) damage the connector in the RAID unit. This can be hard to discover. Try running with the RAID unit as the onlt SCSI device on the chain. Be aware that the RAID unit is always the LAST device (no execeptions!!!) on the SCSI chain and preferably the ONLY device on the SCSI chain. The only device that can cause problems in this case is the tapedrive, which is a "narrow device" despite its wide (68 pin) SCSI connector. ON the 51D the CD-ROM is an IDE device so this one should not be causing trouble on the SCSI chain. Hope this helps RD (FoxboroNL) "Kinoshita, Lisa:" wrote: > > Does anyone else have an AW51D with RAID drive operating? We have had > nothing but problems since we installed ours for a small control system...it > locks up and dies continually (usually identifies a "SCSI" problem and has > to be hard rebooted). We have replaced just about every component - the box > itself, the entire RAID assembly including disk controller and disks, and it > still dies (last night it locked up and could not be rebooted - the RAID > drive was corrupted and had to be restored from tape). > > Thanks. > > Lisa Kinoshita > Process Controls - SFR Rodeo > (510) 245-4581 > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: Saveall Script
Hello everyone, Being one of the authors of the save_all.sh script version that is on Cassandra, I would like to inform you beforehand we are almost done with Version 2.0 if this thing. I'm sure my collegue does'nt mind, if he does, I'm sure he will have forgotten it by monday... What has changed over the previous version: -- An option -h hostname was added to allow for selected hosts to be save_all 'd. Yhe -s station_lbug can be used in combination with this -- A "bug" was fixed to restore the last backup made before the last attempt to save_all a station had failed. -- The best of all (credits to Marco de Waal on this one) The version 2.0 of the script will hunt down your #include files and save them too. -- some minor fixes and cleanups. We where thinking of sending the script through the list, but the script is about 25k. (OK it does a LOT of testing...) Is this a problem??? I hope this is worth waiting fore just a little longer. Kindest regards Ron Deen @home and @Foxboro "Ball, Patrick G." wrote: > > Hey all, > I am using the save_all.sh Version 1.3.2, I have not had time to > update to 1.3.3. Here's my problem, the program runs fine, but I get a > message on the system printer that like this: > > 2 ICC session opened for CP, security level = 5. > > I checked to see if any other ICC is running and did not find one. I think > this started after a QF was installed. Any help will be appreciated. > > Thanks, > Patrick G. Ball > Internet Address -- mailto:[EMAIL PROTECTED] > Intercompany -- 8-824-5877 > Bell Phone -- 1-205-670-5877 > Beeper -- 1-877-986-6814 > <http://psdf.southernco.com/> > > --- > This list is neither sponsored nor endorsed by the Foxboro Company. All > postings from this list are the work of list subscribers and no warranty > is made or implied as to the accuracy of any information disseminated > through this medium. By subscribing to this list you agree to hold the > list sponsor(s) blameless for any and all mishaps which might occur due to > your application of information received from this mailing list. > > To be removed from this list, send mail to > [EMAIL PROTECTED] > with "unsubscribe foxboro" in the Subject. Or, send any mail to > [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with "unsubscribe foxboro" in the Subject. Or, send any mail to [EMAIL PROTECTED]
