Note, at least with a V7.X/V6.X Unix mixed system (except for 2 AW70 OPC gateways), a similar problem also occurs when you eliminate alarms by changing the hex address to 0 for the Station Block Alarm Group assignments in ICC. To get the alarm groups to work again (i.e. report alarms to the WPs, etc.) later as they originally did, you have to enter the same hex address and then pick on each of the alarm devices in the Station Block (that were never removed from the list) and hit the enter key, before hitting the DONE button in ICC. Neil Martin Huntsman Performance Chemicals "Ron Schafer" <rschafer@xxxxxxx ebirchpaper.com> To Sent by: <foxboro@xxxxxxxxxxxxx> foxboro-bounce@fr cc eelists.org Subject Re: [foxboro] Station Block group 08/27/2007 02:32 assignments PM Please respond to foxboro@freelists .org We had the same problem at 6.3 and had whitespaces after the names. The solutions was: I believe you need to enter your devices by selecting from ICC SHOW -> AVAILABLE WP's and then select the desired station and confirm with Enter key. Then I found the whitespace issue. Ronald G. Schafer 10026 Old Ridge Rd. Ashland Va. 23009 804-227-4034 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Pat Martens Sent: Monday, August 27, 2007 2:47 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Station Block group assignments Would not know if it is still the case with 6.5.4 but we had similar problems with 6.3. I believe you need to enter your devices by selecting from ICC SHOW -> AVAILABLE WP's and then select the desired station and confirm with Enter key. Typing or setting with icc script could give unpredictable results. Kind regards, Patrick Martens -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Goldie, Shaun S Sent: maandag 27 augustus 2007 20:35 To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Station Block group assignments Hi I am looking for an explanation for a bit of a hole we dug ourselves into. The job was to move a CP60 eeprom and load a new OS version To prevent the operators from getting all the alarms reissued (twice) we took the operator workstations out of the station groups did the job and reinstated the station groups. It was into plant startup that we realised the workstations were not getting alarms from that CP. With a CP reboot not possible we tried Workstation reboot & Reentering group assignments of 0 checkpoint then enter the correct value Which didn't make any difference What worked for us was change all the device names to a device that was working (we never reassigned our engineering station so it kept working) and generate an alarm for each group then change the device names back ? relevance but Solaris 6.5.4 and the CP60 6.5.5b QF1008936 Shaun =0A=0ANOTICE - This message and any attached files may contain informatio= n that is confidential and intended only for use by the intended recipien= t. If you are not the intended recipient or the person responsible for de= livering the message to the intended recipient, be advised that you have = received this message in error and that any dissemination, copying or use= of this message or attachment is strictly forbidden, as is the disclosur= e of the information therein. If you have received this message in error = please notify the sender immediately and delete the message. _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave -- No attachments (even text) are allowed -- -- Type: text/x-vcard -- File: rschafer@xxxxxxxxxxxxxxxxxxxxxxxxxx -- Desc: rschafer@xxxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave