RE: telnet_mail and a poke at contact information.
Actually, I think it is an excellent idea. Not to say that David Johnson may agree. Now, if you would all just add your socual security number and perhaps a credit card number or two, I could get on with it and retire in style... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 19, 2001 8:11 AM To: Foxboro DCS Mail List Subject: Re: telnet_mail and a poke at contact information. David is right. Anyone who's capable of _using_ the I/A info here for nefarious purposes is certainly capable of bluffing their way onto the list. As David said, are you going to call those contact phone numbers each time you post to the list, even the ones on the other side of the planet? Didn't think so. Mike Adams Mitsubishi Polyester Film, LLC From: David Johnson [EMAIL PROTECTED] on 09/19/2001 12:53 PM GMT Please respond to Foxboro DCS Mail List [EMAIL PROTECTED] To: Foxboro DCS Mail List [EMAIL PROTECTED] cc:(bcc: Mike USA9192 Adams/MFAP/USA) Subject: Re: telnet_mail and a poke at contact information. Hi Duc, I did the write up on the various methods of e-mailing. I would be willing to write it up more formally for the FAQ. I'll have it to you by Friday. As far as contact information goes: This is kind of silly. It is ridiculously easy to make an alternate e-mail address and subscribe to the list server. Are we really going to start making phone calls before we answer questions on the list? Most of the information provided here is freely available to anyone willing to read the Foxboro manual set (although the list is often helpful with the interpretation, tricks, etc). If this is a real security concern then we should start sending PGP authenticated signatures with the messages, and do we really want that? I am also sending Mark Holts latitude and longitude to our spy satellites to see if he is really there. Regards, David Johnson Of course I'm who I say I am, why would anyone want to be me. Premier System Integrators (256) 355-1732 --- 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: PLC Question
Hear Hear on the 70 bit... -Original Message- From: Glen Bounds [mailto:[EMAIL PROTECTED]] Sent: Friday, September 14, 2001 9:15 AM To: Foxboro DCS Mail List Subject: Re: PLC Question First, thanks for all the responses. Second, I have issues with all of the listed methods of communication from ControlLogix to I/A because of the following reasons: 1. AB Integrator 30 to AB 1770-KF2 or 1779-KFL DH+ module in single or redundant ControLogix configuration. I have nine overloaded AB30's connected to one PLC-3 that I plan on updating to a ControlLogix 5550. This is absurd. I would like to have something LIKE an AB30 (with no hard drives, moving parts, configure in ICC, ...) but with a much larger capacity - like a CP60 communicating over Ethernet to ControlLogix. 2. AW51 or AW70 with Ethernet interface, FoxBlocks and AB Interchange or RSLinx software. I actually purchased AB Interchange for Solaris and was considering installing it when I realized how much maintenance and configuration is required. One of our plants does us this method and is not happy with the results. 3. AW70 with DH+ interface, FoxBlocks and AB RSLinx software. If it has a 70 anywhere in the model number, it will not reside in my control system. (Sorry, Foxboro!) 4. Micro I/A with AB Ethernet interface. This was actually something I was very interested in until I found out the true performance and it isn't much better than the AB30. I would still end up with many stations. 5. AW70 with FoxBlocks and DDE I/O Gate through a serial or Ethernet interface which addresses data in the native ControLogic naming structure. See answer for #3. 6. AW51 or AW70 through an Ethernet interface with a third party OPC software which addresses data in the native ControLogic naming structure. This is what I will probably have to end up doing. AW51 with a third party OPC server. I just wish I didn't have go this way. It has a hard drive, has to be configured a couple of places instead of one, and I will have to deal with finger pointing when something goes wrong. So, in conclusion, I want a CP60 like performance and form factor, with the ability to configure C:B.P directly in ICC or FoxCAE communicating over fast Ethernet. We have many plants around the world that could use this technology today. Is that too much to ask? Glen Bounds [EMAIL PROTECTED] Corn Products International - Original Message - From: Jason Wright [EMAIL PROTECTED] Subject: RE: PLC Question Glen, I don't think there is a real good answer, but I've seen it done. I have copied some old information I found below for reference (from Foxboro tech). There are several options depending on the amount of data and type of communications. From the Foxboro perspective, the easiest way would be to communicate to the ControlLogix as a PLC-5. This would require a little bit of configuration on the Rockwell side. I hope this is helpful. Regards, Jason ___ Jason Wright Regional Technical Specialist ControlSoft (216) 397-3900 x201 A-B ControlLogix PLC's Many Foxboro customers are purchasing the new Allen Bradley ControLogix PLC and asking how would we interface it to I/A Series. The ControLogix product is designed around their new ControlNet data highway and uses an object oriented data naming structure. Fortunately, Allen Bradley also supports Ethernet and DH+ with PLC5 data table structure so that all of our traditional interfaces can be used. When a data object (up to 40 characters in length) is created, a pull-down menu is available to assign the data object to a PLC5 data table. In addition, Allen Bradley will be introducing a fault-tolerant ControLogix configuration with two processors and shared I/O. As a result, we can interface via the following methods: 1. AB Integrator 30 to AB 1770-KF2 or 1779-KFL DH+ module in single or redundant ControLogix configuration. 2. AW51 or AW70 with Ethernet interface, FoxBlocks and AB Interchange or RSLinx software. 3. AW70 with DH+ interface, FoxBlocks and AB RSLinx software. 4. Micro I/A with AB Ethernet interface. 5. AW70 with FoxBlocks and DDE I/O Gate through a serial or Ethernet interface which addresses data in the native ControLogic naming structure. 6. AW51 or AW70 through an Ethernet interface with a third party OPC software which addresses data in the native ControLogic naming structure. -Original Message- Subject: Re: PLC Question I for one would be interested in some more detailed information. I have asked Foxboro about this for a couple of years now with no results. Glen Bounds [EMAIL PROTECTED] Corn Products International - Original Message - Foxboro does not yet endorse connectivity to ControlLogix. We (FeedForward, a Foxboro Systems Integrator) have, however, successfully integrated the two for one of our customers. I was not directly involved with this project, but from my understanding, it requires no
RE: Putting ECBs on/off line without using System Monitor
The reason you can not set the ACTION bit with omset is because it is NOT SETTABLE. However, one can still set it with the ever hazardous tool 'setpars'. -Original Message- From: Michael J Wing [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 31, 2001 8:43 AM To: [EMAIL PROTECTED] Subject: RE: Putting ECBs on/off line without using System Monitor When I try to set the ACTION parameter with omset (only testing!) I get an errror code of 15. This corresponds to omopenlist already open. Is this perhaps because I'm talking about an ECB that is used to communicate with an AB PLC on an AW51 integrator rather than a more common FBM ECB? omget for this parameter returns a 0. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Holger Dahl Sent: Tuesday, July 31, 2001 2:37 AM To: [EMAIL PROTECTED] Subject: Putting ECBs on/off line without using System Monitor David, You can set the ACTION Parameter of the ECBs. Setting this Parameter to 1 turns the ECB on, setting it to 2 turns the ECB off. Regards, Holger Dahl erpicon software development GmbH Neusser Str. 724-726 50737 Koeln Tel: 0221-97460-70 Fax: 0221-97460-99 Email: [EMAIL PROTECTED] mailto:[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]
V6.3 and Exceed
Help! Since we have upgraded our workstations to version 6.3 the displays served via the 2nd Ethernet port (Hummingbird Exceed) no longer work at any other desktop setting than 1024 X 768 and 256 colors. Otherwise they simply get a window filled with black. Prior to the upgrade, MOST of the 100 or so users could get it to work at 800 X 600 and SOME of those with High Color. Any suggestions? --- 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: Synchronization (was RE: HLBL REF.)
Other tools to check synchronization of all the pertinent data files can be obtained and aren't mentioned here. When installed, check_db_sync and ck_multi_cps in the directory check_sync located in /opt/fox/bin/tools will give you a warm and fuzzy feeling when it successfully reports databases are synchronized. These tools are a part of the (now partially defunct) 'bootless upgrade' feature. I run these once a week and have discovered problems long before they cause real trouble. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, July 09, 2001 7:29 PM To: Foxboro DCS Mail List Subject: Synchronization (was RE: HLBL REF.) Corey, It is critical that the CSA database, the station volume workfile and the checkpoint file stay synchronized. Because parameters are constantly changing on the CP, it is normal that the setable parameters in the CP will not match the other files, although the non-settable parameters must match. There are several things that can cause a problem between CP, CSA, station workfile and checkpoint file. Some of these include: 1) Power failure or system reboot during ICC session 2) Improper exit from ICC 3) Tape restore 4) setpars 5) CSA tools 6) ICC use with severe station overloading Other causes probably exist. Corruption of CSA, work file or checkpoint file is possible too. Of the list above, #1 is the one I have seen most often. Typically, an ICC session is left open and is still open when the computer or xterminal it is running on is rebooted (before checkpoint). Tape restore of an AP or AW is a tricky one. If changes have been made in ICC since the tape you are restoring from was made, and if no current SaveAlls exist, you will probably need to restore from tape, reboot the CP (to checkpoint file from tape) and re-create the changes in ICC made after the tape. A couple of items that may not be obvious: 1) Upload only updates settable parameters from CP to workfile. Assumption probably is that non-settable parameters shouldn't need to be updated from CP. 2) A SaveAll is not made from the CP but from the workfile. If setpars is used to change a non-settable parameter on the CP, a SaveAll won't reflect that change even after an upload. Tools are available for troubleshooting mismatches: Select views parameters in CP. iccprt views parameters in workfile. dbvu views parameters in checkpoint file (-t option, needs checkpoint file, map file and image file). CSA_save exports an ascii copy of the CSA database. Regards, Kevin FitzGerrell Systems Engineer Foxboro New Zealand Tel: +64 (9) 573 7690 Fax: +64 (9) 573 7691 Corey R Clingo [EMAIL PROTECTED] To: Foxboro DCS Mail List [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: RE: HLBL REF. oject.org 07/10/01 11:17 AM Please respond to Foxboro DCS Mail List OK, you've gone and confused me now (don't get the big head; it's not that hard to do ;-). I am kind of new to I/A, and this whole checkpoint/workfile/CP's memory thing has me asking a lot of questions, to say the least. I had thought that the checkpoint at least was a direct copy of the CP's memory, but from what you say below this is not the case. (Emotional state on discovering this deleted...) Sois there anything else supplied by Foxvensys that can make changes to the CP's
RE: HLBL REF.
What Alex did NOT mention although I feel he should have, is that using setpars should be avoided period. There are other more graceful (omset class) methods that are not nearly as dangerous. -Original Message- From: Johnson, Alex (Foxboro) [mailto:[EMAIL PROTECTED]] Sent: Monday, July 09, 2001 12:22 PM To: Foxboro DCS Mail List Subject: RE: HLBL REF. Re: Sequence Block Resources HLBL is slow. Each line of HLBL code is roughly equivalent to the CPU requirements of an AIN block. External references to CBPs in the same CP take even longer. Re: Setting External OM Variables from within HLBL HLBL allows OM variables (C:B.Ps and SVs) to be set directly using the following syntax: :variableName := value; where variableName is a C:B.P name or a Shared Variable Name value is the new value for the variable. The leading colon is required. Two examples are: :TOWER:OVRHD_LEVEL.SPT := 50.0; :WP0001DMCMD := dmcmd applic /opt/prog/myScript $DMNAME ; NAME := SN0001, DMCMD; :'NAME' := dmcmd applic /opt/prog/myScript $DMNAME ; This is documented in the appropriate manuals. There are a couple of gotchas though: 1) If the variable being set is secured or missing, you will get an operational error that will either cause an SBX to be fired or suspend the block. 2) Each external reference suspends the execution of the HLBL code for one block period if the target is outside the CP. If the target is inside the CP, the call does not suspend the code, but it can take quite a long time. The former issue is difficult to handle properly if one has several external references in the code since they will all fire the same SBX and you will probably want different handling for each case. Personally, I do not use this approach. I prefer to use a program like cpShell and send it messages from SENDCONF (see below). The second issue causes subtle problems in the code. I had one customer call because his emergency shutdown logic took 10s to execute and it was only 20 lines of code. The problem was that he did not know about the suspension of execution on an external reference. Since his block ran every 0.5 seconds though, 10s to execute the code was as good as he could expect. There is no workaround for this delay other than to not use external references, i.e., connect the targets to the output of the block. Of course, that can lead to conflicts with the operator if the operator needs to set the same targets. Re: Executing Scripts and Programs from a Sequence Block There was a long discussion on how to run scripts on demand. The options boil down to: * Using the external reference capability of HLBL to set the DMCMD global of a DM/FV instance * Using SENDMSG or SENDCONF to send a message to a program that will execute the command. There are issues with the first approach related to error handling, i.e., what happens and how do you handle it if the DMCMD variable does not exist or someone overrides your command before it can be executed. These are actually quite difficult to handle. The latter approach is much more controllable. The SENDCONF command has a timer. It suspends execution of the sequence block and sets the SUSPND parameter. When the SUSPND parameter is reset or the timer expires, the sequence block awakes. If it awakes because of a timeout, the flow of control goes to a particular part of your logic associated with exactly that failure. If it awakes because the SUSPND parameter is reset, the flow of control moves to the next line. Sadly, we do not ship such an application with the standard system. However, you can get a copy of one by ordering cpShell. This is a VAS-IT item which means that it is sold as reusable application engineering. It is licensed on a per unit basis where we trust you to have a reasonable process unit. To order, tell your account rep that you want: Part No: VAS-IT Description: cpShell for Solaris Order Type: ZZPB or ZZPR Item Tag: cpShell for Solaris Special Shipping Instructions: Contact Ruby Chapman in Houston to fill the cpShell order. Delivery: 4 to 8 weeks ARO. List Price (US): 2,200 USD I'll send you the manual separately. I'm sure that there are others with similar products. 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: Jones, Charles R. (Chuck) [SMTP:[EMAIL PROTECTED]] Sent: Monday, July 09, 2001 8:59 AM To: 'Foxboro DCS Mail List' Subject:RE: HLBL REF. If the operators can interact with the process, I recommend putting GDEV blocks to AUTO (then WAIT 2 seconds for the block to see it) right before you use each one. It is the only way to be sure that the GDEV will be in the correct auto/manual state when you need it to be. If you are going to change state on several
RE: Speaking of Save_All
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]
Speaking of Save_All
I can't seem to locate the helpful hint that describes how to put these ICC API created save alls that are in a file on the hard disk onto a loadable diskette. Anyone know where that is? --- 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: Version 4.3 to 6.2.1 upgrade question
-Original Message- From: James Kahlden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:14 AM To: [EMAIL PROTECTED] Subject: Version 4.3 to 6.2.1 upgrade question Hello List, We are looking at updating our version 4.3 system to version 6.2.1 in order to expand our system to include the new CP60. We currently use AW/WP51B's with Display Manager and the Legacy Historian. Our CP's are fault tolerant CP40A's. We have 5 nodes connected via Carrier Band LAN. We can not shut down all nodes at once, since this system controls two 600 megawatt coal fired power generators. Questions? These are the answers as I know them, someone from Foxboro will probably give a more detailed answer: 1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes exist at 4.3 while part of the node is at 6.2.1? No, but you will have to do some special tricky stuff with the Device Manager. 2. Can we continue to use our Display Manager displays, or do we have to change to the Fox View displays? Yes, you can still use the DM 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to convert to the AIM historian? Yes, you can still use the Legacy Historian 4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for this upgrade? Yes, this is a Day 0 upgrade and requires a CP reboot. Thanks for any guidance that you can give, as we are looking to see what windows of opportunity we have for doing this type of upgrade. Jim Kahlden [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: Version 4.3 to 6.2.1 upgrade question
It will be a dead heat as to whether you or we are the last to migrate to FoxView -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:36 AM To: [EMAIL PROTECTED] Subject: RE: Version 4.3 to 6.2.1 upgrade question Jim, We did an upgrade like yours last year (with a slight difference, we went from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the same). Here are our take on your questions: 1. No, the nodes can be converted individually. Foxboro recommends that you upgrade the node where CSA resides first. Luckily it works out for us without having to move the CSA server to the first node to be converted. 2. Yes, most definitely. We'll be the last system to be forced to migrate to FoxView. 3. Again, yes. Legacy historians work fine. 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't make any difference to us if the CP images were new or not. Duc -- Duc M. Do Process Control Systems Dow Corning, Carrollton Plant Carrollton, KY, US -Original Message- From: James Kahlden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Version 4.3 to 6.2.1 upgrade question Hello List, We are looking at updating our version 4.3 system to version 6.2.1 in order to expand our system to include the new CP60. We currently use AW/WP51B's with Display Manager and the Legacy Historian. Our CP's are fault tolerant CP40A's. We have 5 nodes connected via Carrier Band LAN. We can not shut down all nodes at once, since this system controls two 600 megawatt coal fired power generators. Questions? 1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes exist at 4.3 while part of the node is at 6.2.1? 2. Can we continue to use our Display Manager displays, or do we have to change to the Fox View displays? 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to convert to the AIM historian? 4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for this upgrade? Thanks for any guidance that you can give, as we are looking to see what windows of opportunity we have for doing this type of upgrade. Jim Kahlden [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: Version 4.3 to 6.2.1 upgrade question
According to Websters: Adventure (ad-ven'tur), n. an event the issue of which is determined by chance: v.t. to hazard or risk. Hmmm, risk, hazard, chance... gimme a break! -Original Message- From: Julie Monsour [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:29 AM To: Foxboro DCS Mail List Subject: Re: Version 4.3 to 6.2.1 upgrade question Where's your sense of adventure, Bo? Foxview is GREAT! Julie Monsour - Original Message - From: Stear, Bo [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 7:46 AM Subject: RE: Version 4.3 to 6.2.1 upgrade question It will be a dead heat as to whether you or we are the last to migrate to FoxView -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:36 AM To: [EMAIL PROTECTED] Subject: RE: Version 4.3 to 6.2.1 upgrade question Jim, We did an upgrade like yours last year (with a slight difference, we went from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the same). Here are our take on your questions: 1. No, the nodes can be converted individually. Foxboro recommends that you upgrade the node where CSA resides first. Luckily it works out for us without having to move the CSA server to the first node to be converted. 2. Yes, most definitely. We'll be the last system to be forced to migrate to FoxView. 3. Again, yes. Legacy historians work fine. 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't make any difference to us if the CP images were new or not. Duc -- Duc M. Do Process Control Systems Dow Corning, Carrollton Plant Carrollton, KY, US -Original Message- From: James Kahlden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Version 4.3 to 6.2.1 upgrade question Hello List, We are looking at updating our version 4.3 system to version 6.2.1 in order to expand our system to include the new CP60. We currently use AW/WP51B's with Display Manager and the Legacy Historian. Our CP's are fault tolerant CP40A's. We have 5 nodes connected via Carrier Band LAN. We can not shut down all nodes at once, since this system controls two 600 megawatt coal fired power generators. Questions? 1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes exist at 4.3 while part of the node is at 6.2.1? 2. Can we continue to use our Display Manager displays, or do we have to change to the Fox View displays? 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to convert to the AIM historian? 4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for this upgrade? Thanks for any guidance that you can give, as we are looking to see what windows of opportunity we have for doing this type of upgrade. Jim Kahlden [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: Version 4.3 to 6.2.1 upgrade question - Why not FoxView?
Since you asked seriously, I'll respond properly. We that have had Foxboro I/A on our sites for many years had to deal with an especially slow call up time for displays in the early days, something on the order of 15 seconds or more. As time went by, the DM was improved and the hardware was updated to faster processors and now the DM is a real zinger as far as speed is concerned. Early releases of Foxview were an instant reminder of the slow speed of the DM in its early stages because the call up time for it was something on the order of 15 seconds or more on the, then prevalent, WP51 Style 'B' workstations. Even now, the current Foxview is 3 to 5 times slower in call up time than the DM on the 'B' style workstations. Since we have some 80 style 'B' workstations in house now, even the very best advantage upgrade to a faster processor would be too expensive and so is not possible. If we were to switch to Foxview today, I expect that our operators would soon hang me from some pipe rack by my thumbs because they are used ! to the speed. SO, I do not dislike Foxview for any particularly detrimental reason and others that agree with me probably do so for the same reasons (but they should speak for themselves). -Original Message- From: Anderson, Gary T(Z02256) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 9:33 AM To: 'Foxboro DCS Mail List' Subject: RE: Version 4.3 to 6.2.1 upgrade question - Why not FoxView? I have to jump in here and ask why the reluctance to use FoxView? What don't I know? What should I know? We are a relatively new IA site and have never used the old Display Manager. Other than potential processor loading of older hardware and converting the displays, I can't see any reason not to use FoxView. The old style look of the Display Manager was enough incentive to cause us to start with FoxView. Gary Anderson Arizona Public Service -Original Message- From: Julie Monsour [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:29 AM To: Foxboro DCS Mail List Subject: Re: Version 4.3 to 6.2.1 upgrade question Where's your sense of adventure, Bo? Foxview is GREAT! Julie Monsour - Original Message - From: Stear, Bo [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 7:46 AM Subject: RE: Version 4.3 to 6.2.1 upgrade question It will be a dead heat as to whether you or we are the last to migrate to FoxView -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:36 AM To: [EMAIL PROTECTED] Subject: RE: Version 4.3 to 6.2.1 upgrade question Jim, We did an upgrade like yours last year (with a slight difference, we went from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the same). Here are our take on your questions: 1. No, the nodes can be converted individually. Foxboro recommends that you upgrade the node where CSA resides first. Luckily it works out for us without having to move the CSA server to the first node to be converted. 2. Yes, most definitely. We'll be the last system to be forced to migrate to FoxView. 3. Again, yes. Legacy historians work fine. 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't make any difference to us if the CP images were new or not. Duc -- Duc M. Do Process Control Systems Dow Corning, Carrollton Plant Carrollton, KY, US -Original Message- From: James Kahlden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Version 4.3 to 6.2.1 upgrade question Hello List, We are looking at updating our version 4.3 system to version 6.2.1 in order to expand our system to include the new CP60. We currently use AW/WP51B's with Display Manager and the Legacy Historian. Our CP's are fault tolerant CP40A's. We have 5 nodes connected via Carrier Band LAN. We can not shut down all nodes at once, since this system controls two 600 megawatt coal fired power generators. Questions? 1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes exist at 4.3 while part of the node is at 6.2.1? 2. Can we continue to use our Display Manager displays, or do we have to change to the Fox View displays? 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to convert to the AIM historian? 4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for this upgrade? Thanks for any guidance that you can give, as we are looking to see what windows of opportunity we have for doing this type of upgrade. Jim Kahlden [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
RE: Version 4.3 to 6.2.1 upgrade question
Perhaps FUBAR? -Original Message- From: Julie Monsour [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 1:13 PM To: Foxboro DCS Mail List Subject: Re: Version 4.3 to 6.2.1 upgrade question hmmm...Well, maybe adventure was a poor choice for a word, then. - Original Message - From: Stear, Bo [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 10:29 AM Subject: RE: Version 4.3 to 6.2.1 upgrade question According to Websters: Adventure (ad-ven'tur), n. an event the issue of which is determined by chance: v.t. to hazard or risk. Hmmm, risk, hazard, chance... gimme a break! -Original Message- From: Julie Monsour [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:29 AM To: Foxboro DCS Mail List Subject: Re: Version 4.3 to 6.2.1 upgrade question Where's your sense of adventure, Bo? Foxview is GREAT! Julie Monsour - Original Message - From: Stear, Bo [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 7:46 AM Subject: RE: Version 4.3 to 6.2.1 upgrade question It will be a dead heat as to whether you or we are the last to migrate to FoxView -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:36 AM To: [EMAIL PROTECTED] Subject: RE: Version 4.3 to 6.2.1 upgrade question Jim, We did an upgrade like yours last year (with a slight difference, we went from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the same). Here are our take on your questions: 1. No, the nodes can be converted individually. Foxboro recommends that you upgrade the node where CSA resides first. Luckily it works out for us without having to move the CSA server to the first node to be converted. 2. Yes, most definitely. We'll be the last system to be forced to migrate to FoxView. 3. Again, yes. Legacy historians work fine. 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't make any difference to us if the CP images were new or not. Duc -- Duc M. Do Process Control Systems Dow Corning, Carrollton Plant Carrollton, KY, US -Original Message- From: James Kahlden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Version 4.3 to 6.2.1 upgrade question Hello List, We are looking at updating our version 4.3 system to version 6.2.1 in order to expand our system to include the new CP60. We currently use AW/WP51B's with Display Manager and the Legacy Historian. Our CP's are fault tolerant CP40A's. We have 5 nodes connected via Carrier Band LAN. We can not shut down all nodes at once, since this system controls two 600 megawatt coal fired power generators. Questions? 1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes exist at 4.3 while part of the node is at 6.2.1? 2. Can we continue to use our Display Manager displays, or do we have to change to the Fox View displays? 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to convert to the AIM historian? 4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for this upgrade? Thanks for any guidance that you can give, as we are looking to see what windows of opportunity we have for doing this type of upgrade. Jim Kahlden [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
RE: Version 4.3 to 6.2.1 upgrade question
That is, Foxboro Unconditionally Backs All Releases.. -Original Message- From: Julie Monsour [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 1:13 PM To: Foxboro DCS Mail List Subject: Re: Version 4.3 to 6.2.1 upgrade question hmmm...Well, maybe adventure was a poor choice for a word, then. - Original Message - From: Stear, Bo [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 10:29 AM Subject: RE: Version 4.3 to 6.2.1 upgrade question According to Websters: Adventure (ad-ven'tur), n. an event the issue of which is determined by chance: v.t. to hazard or risk. Hmmm, risk, hazard, chance... gimme a break! -Original Message- From: Julie Monsour [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:29 AM To: Foxboro DCS Mail List Subject: Re: Version 4.3 to 6.2.1 upgrade question Where's your sense of adventure, Bo? Foxview is GREAT! Julie Monsour - Original Message - From: Stear, Bo [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 7:46 AM Subject: RE: Version 4.3 to 6.2.1 upgrade question It will be a dead heat as to whether you or we are the last to migrate to FoxView -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 7:36 AM To: [EMAIL PROTECTED] Subject: RE: Version 4.3 to 6.2.1 upgrade question Jim, We did an upgrade like yours last year (with a slight difference, we went from 6.1 to 6.2.1 -- for all practical purposes, 4.3 and 6.1 are the same). Here are our take on your questions: 1. No, the nodes can be converted individually. Foxboro recommends that you upgrade the node where CSA resides first. Luckily it works out for us without having to move the CSA server to the first node to be converted. 2. Yes, most definitely. We'll be the last system to be forced to migrate to FoxView. 3. Again, yes. Legacy historians work fine. 4. We did this as a Day 0 install, so we reboot the CPs anyway. It didn't make any difference to us if the CP images were new or not. Duc -- Duc M. Do Process Control Systems Dow Corning, Carrollton Plant Carrollton, KY, US -Original Message- From: James Kahlden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 8:14 AM To: [EMAIL PROTECTED] Subject: Version 4.3 to 6.2.1 upgrade question Hello List, We are looking at updating our version 4.3 system to version 6.2.1 in order to expand our system to include the new CP60. We currently use AW/WP51B's with Display Manager and the Legacy Historian. Our CP's are fault tolerant CP40A's. We have 5 nodes connected via Carrier Band LAN. We can not shut down all nodes at once, since this system controls two 600 megawatt coal fired power generators. Questions? 1. Do all of the nodes need to be converted at one time to 6.2.1 or can some nodes exist at 4.3 while part of the node is at 6.2.1? 2. Can we continue to use our Display Manager displays, or do we have to change to the Fox View displays? 3. Can we continue to use the Legacy Historian at version 6.2.1, or do we have to convert to the AIM historian? 4. Is there a different CP image at version 6.2.1 that requires a reboot of the CP for this upgrade? Thanks for any guidance that you can give, as we are looking to see what windows of opportunity we have for doing this type of upgrade. Jim Kahlden [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: Variable selection in a sequence
Can anyone actually believe that Alex Johnson lost his COLON?
-Original Message-
From: Johnson,Alex [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 17, 2000 2:07 PM
To: Foxboro DCS Mail List
Cc: Wilfred Kram (E-mail)
Subject: RE: Variable selection in a sequence
Let me try that again. A colon was lost! or MS Outlook messed with my
incoming message. I can't tell:
Here's some sample code for you.
APP_NAME : SN0001;{ Name of DMC application }
CNTDWN : SN0009;{ AOA reference for CNTDWN }
...
{ This stores the destination tag as a string into CNTDWN}
CNTDWN := APP_NAME,:DMCOP.CNTDWN;
{ This clears the count down timer. Note the use of : and ' }
{ In case you can't see it, the line reads 'colon''single quote''variable
name''colon''equal''zero' }
:'CNTDWN' := 0;
You can use string variables rather than parameters. I like to use the
parameters as a debugging aid.
Hope this helps.
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
-Original Message-
From: Johnson,Alex [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, October 17, 2000 1:37 PM
To: Foxboro DCS Mail List
Cc: Wilfred Kram (E-mail)
Subject:RE: Variable selection in a sequence
Here's some sample code for you.
APP_NAME : SN0001;{ Name of DMC application }
CNTDWN : SN0009;{ AOA reference for CNTDWN }
...
{ This stores the destination tag as a string into CNTDWN}
CNTDWN := APP_NAME,:DMCOP.CNTDWN;
{ This clears the count down timer. Note the use of : and ' }
:'CNTDWN' := 0;
You can use string variables rather than parameters. I like to use
the
parameters as a debugging aid.
Hope this helps.
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
-Original Message-
From: Baltus, C.J.M. [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, October 17, 2000 1:27 PM
To: Foxboro DCS mailing list (E-mail)
Cc: Wilfred Kram (E-mail)
Subject:Variable selection in a sequence
Hi All, (I think this is the standard opening)
I will introduce myself first, I am a DCS engineer working
for 2
years with
Foxboro IA, in a small wet country.
I am following this list since I started with Foxboro IA and
I saw
many
problems solved. Now here is my problem (perhaps its a
stupid one,
but I'm
breaking my wooden shoe on it).
I want to make a variable selection in a sequence, its
written in
SFC.
First I made a macro called:
PUMP1 :TEST:GDEV1.AUTDSR
PUMP2 :TEST:GDEV2.AUTDSR
Then I made a variable called:
PUMP and attached to BOOL
In the first selection I want
PUMP := PUMP1;
the following step:
PUMP := TRUE;
and when I return to the beginning I perhaps want PUMP
select to:
PUMP := PUMP2;
the following step:
PUMP := TRUE;
But what I tried, it didn't work, has someone got a solution
?? This
will be
written for a selection of 32 posibilties
With Kind Regards,
Cor-Jan Baltus
DCS Engineer
KH-AMEC Engineering
Bergen op Zoom
the Netherlands
* [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
RE: Rolling average
Here's a way to do it using a TIMER and an IND block. You could do without
the timer and just use the WAIT for the period but then you might run into
problems if your CP goes into overrun.
This is set for a flow but will work on anything..
INDEPENDENT_SEQUENCE{***
** **
** INDEPENDENT SEQUENCE **
** CONTROL BLOCK**
** **
*}
CONSTANTS {*
* specify any Constants *
* in the following format: *
**
* 12_char_name = value ; *
*}
VARIABLES {*
* specify any Block Local Variables *
* in the following format: *
**
* 12_char_name [ , 12_char_name ] : type;*
**
*where type is one of B, I, R, S, S12, S6*
*}
AVG:R[360];
ICT:I;
USER_LABELS{
* specify any user labeled parameters*
* in one of the following formats: *
**
* 10_char_name : BI00nn; n = 01 -- 24 *
* 10_char_name : BO00nn; n = 01 -- 16 *
* 10_char_name : BA000n; n = 1 -- 4 *
* 10_char_name : RI00nn; n = 01 -- 15 *
* 10_char_name : RO00nn; n = 01 -- 15 *
* 10_char_name : RA000n; n = 1 -- 2 *
* 10_char_name : II000n; n = 1 -- 8 *
* 10_char_name : IO000n; n = 1 -- 5 *
* 10_char_name : IA0001; *
* 10_char_name : SN00nn; n = 01 -- 10 *
*}
FI3050: RI0001; {MEASURED FLOW}
FA3050: RO0001; {AVERAGE FLOW}
CNTIDX: IO0001; {AVERAGER INDEX}
SUM:RO0002; {TEMPORARY SUM}
TIM:RI0002; {10 SECOND TIMER INPUT}
REMOVE: RO0003; {VALUE TO REMOVE FROM SUM}
BTU:RI0003; {ENTERED VALUE FOR BTU}
BTU_VAL: RO0015; {CALCULATED BTU VALUE FOR CURRENT FLOW}
{*
* Specify any Subroutines*
**
**
* SUBROUTINE name ( formal arguments ) ; *
* VARIABLES subr. local variables ;*
* STATEMENTS*
* ; *
* ENDSUBROUTINE *
*}
{*
* Specify any*
*Standard Block Exception Handlers *
**
**
* BLOCK_EXCEPTION exc_name [ DISABLE ] *
* STATEMENTS*
* ; *
* ENDEXCEPTION *
*}
STATEMENTS{*
* Specify the statements here *
*}
CNTIDX := 1;
AVG := SET_ARRAY(FI3050);
SUM := FI3050 * 360.0;
START_TIMER(::10SECONDS.TIMR1,0.0);
START
REMOVE := AVG[CNTIDX];
AVG[CNTIDX] := FI3050;
SUM := SUM - REMOVE;{REMOVE THE OLD VALUE}
SUM := SUM + AVG[CNTIDX]; {ADD IN THE NEW VALUE}
CNTIDX := CNTIDX + 1;
IF CNTIDX 360 THEN
CNTIDX := 1;
ENDIF;
FA3050 := SUM / 360.0;
{CALCULATE BTU VALUE}
BTU_VAL := FA3050 * BTU;
::10SECONDS.TIMR1V := 0.0;
WAIT 1;
WAIT UNTIL TIM = 10.0;
GOTO START;
ENDSEQUENCE
-Original Message-
From: Steve Rigby [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 06, 2000 8:01 AM
To: 'Foxboro DCS Mail List' (E-mail)
Subject: Rolling average
Hi all,
What I would like is a way to calculate the average position of a valve over
the last hour, updated say every minute.
and then available as an input for a block. Any ideas?
Thanks in advance.
Steve Rigby
Air Liquide Industrie BV
Merseyweg 10
3197 KG Botlek-Rotterdam
The Netherlands
Tel: +31(0)181-271131
Fax:+31(0)181-271100
Email:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
RE: rexecing without password
The invisible .rhosts file in the root directory must be created or modified to allow remote access without passwords. This file sets up a 'trusted' station that does not require passwords. Create or modify the .rhosts file to contain the LETTERBUG name of all of the stations that you want to be 'trusted'. -Original Message- From: Sascha Wildner [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 31, 2000 7:17 AM To: Foxboro Mailing List Subject: rexecing without password Hello, does anyone know if it is possible to remotely execute commands on other hosts (either AW70 or AW51) without having to enter a password? My application must be able to do this from either architecture, all four combinations (AW70-AW70, AW70-AW51, AW51-AW51 and AW51-AW70). Regards, Sascha Wildner erpicon Software Development GmbH --- 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: upload/shrink/checkpoint problems
Check the drive space on the host AP for this CP. Shrink uses extra space and you may be running out. I'm not certain but since the ICC session failed during the 'shrink' it may have left the database locked causing the remaining sessions to fail. I hate to be a killjoy but it's just these types of problems that cause me to avoid 'automatic' scripts to handle my CP's. These are fragile databases that can sometimes be easily corrupted. Everything has to go just right or the synchronization between the running CP, its workfile, it's locks, and CSA can be fowled. -Original Message- From: Stan Brown [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 02, 2000 7:29 AM To: [EMAIL PROTECTED] Subject: upload/shrink/checkpoint problems I jsut deployed my new upload/shrink/checkpoint script on a new node, and it failed during the run last night. Can anyone give me some insight into what this failure means? Here is the ouput of one station: Starting upload/checkpoint... Mon May 1 23:00:05 GMT 2000 --- upload and checkpoint CP0401 DONE 1 OPEN CP0401!: Mon May 1 23:00:06 2000 DONE 2 UPLOAD CP0401!: Mon May 1 23:04:53 2000 FAIL 3 SHRINK CP0401!: Mon May 1 23:06:53 2000 -15 ICCshrink error: class= -30 error= 0 text= ICCinit: CCshrink problem FAIL 4 CHECKPOINT CP0401!: Mon May 1 23:06:53 2000 -15 ICCchkpt error: clas s= 20 error= 1 text= Session not in progress FAIL 5 CLOSE CP0401!: Mon May 1 23:06:53 2000 -16 ICCclose error: class= 20 error= 1 text= Session not in progress DONE 6 EXIT CP0401!: Mon May 1 23:06:53 2000 I _think_ all the later errors are trigered by the shrink problem, but I am not certain of this. Any insight would be greatly appreciated. -- 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]
RE: Re: Scripts to backup CP database and CSA to an alternate sta tion
OFHA has some problems that won't be resolved. See CAR 100053 and you'll find that OFHA will skip filenames when they are more than 14 characters in length. The CAR response recommends I rename these files so they are shorter kinda strange since they're either SYSTEM or FOXBORO created files. The CAR also states that Foxboro has NO intentions of fixing this problem and have turned it into a PRODUCT ENHANCEMENT... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 29, 2000 3:57 PM To: Foxboro DCS Mail List Subject: Re: Re: Scripts to backup CP database and CSA to an alternate station If you are using model 51 stations, you should consider using the OFHA product that is included in the baseline software supplied with AW51s and AP51s Best Regards, Fred Yes I'd be happy to donate them. And I don't consider it an intrusion. Thanks for doing such a good thing with the Cassandra Project. I wonder how long it will be before we see Foxboro using the Project as a selling point. Duc M Do [EMAIL PROTECTED]@lists.TheCassandraProject.org on 04/18/2000 03:15:46 PM Please respond to Foxboro DCS Mail List [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To: Foxboro DCS Mail List [EMAIL PROTECTED] cc: Subject: Re: Scripts to backup CP database and CSA to an alternate station Hi Ed, Sorry for one more intrusion: I forgot to ask you if you are donating your ez_archive scripts to the Cassandra Project? If affirmative, please let me know so I can add the proper GNU Open Source text block to the files. Thanks! Duc M. Do At 02:46 PM 4/18/00 -0500, you wrote: Duc M. Do was kind enough to upload the scripts I use to back-up the control database and CSA information to an alternate station to the cassandra server The scripts are located at http://thecassandraproject.org/archive/ez_archive.zip Duc also created a compressed tar-format file: http://thecassandraproject.org/archive/ez_archive.tar.Z I think this is an important utility. I believe if a few of you hacker types could take a look at the scripts it could be improved greatly. --- 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]
