The .apc file is both an input and output file for the FoxPanels configurator. The AAtab, AApan, and horn.cfg file are output files only (although they can be imported). When you open the configuration it is the .apc file that gets opened. (Aside: This also explains why if you edit your AApan or AAtab files with a text editor, they reopened the configuration you do not see the hand edits, and they hand edits are lost when you save). The .apc file is also used by FoxPanels Run-Time (a.k.a. SoftPanels) which produces screen displays of panels. It is not used no needed when you are just using annunciator keyboards. As a matter or fact I have seen it cause problems. I would suggest saving your configuration (.apc, AAtab, AApan, and horn.cfg files) to a subdirectory and deleting the .apc file from \usr\fox\alarms. If this does not work then please answer the following (you may have answered some of these earlier but I didn't see them): 1. What I/A release are you at? 2. Are you using Windows or Solaris workstations? 3. How many annunciator keyboards do you have configured? 4. How many annunciator assignments are made in the AAtab file? 5. Do you have the correct number of possible annunciator assignments configured (init.usr for pre-8.0; ADMC Workstation Property Scheme, Other tab for 8.0+). The default is 2000 assignments, but you can configure this up to 10,000 assignments. Kathy -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Rguercio@xxxxxxx Sent: Tuesday, January 15, 2008 5:17 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] foxboro Digest V8 #14 = = In a message dated 1/15/2008 12:13:19 Central Standard Time, = foxboro@xxxxxxxxxxxxx writes: The easiest way of detecting duplicate Compound:Block entries in the file is the following: Thanks to everybody who has responded to my problem. There is still a = problem, and here is what I have done: = I am very familiar with the loadalmpnl and prtalmpnl commands and use them = all the time. They make the panel buttons work and produce the exact file = contents I would expect. I am not having trouble with the AApan file and = key-pushing functions. My problem is: I cannot get the associated AAtab file to = be recognized (can't get alarms to light ANY LED's). = Before this last round of help, I had already checked for duplicates in the = ...AAtab file using the Excel route (and thanks everyone for the other = dup-checking utilities which I will keep in my bag of Foxboro Tricks), and I = actually started from scratch with FoxPanels configurator and set up a simple = panel. Sure enough, the AApan file created made the key-pushes work, but I could = not get any LED's to light. I verified that the ...AA... files I had = previously created had both the same name and same format as those created by = FoxPanels, thus eliminating that path. The only difference was that FoxPanels, of = course, created the <LBUG>.apc file, whereas I had never seen that file in = /usr/fox/alarms before. I thought, "aha, here is the problem, even though = dozens of other workstations have been working successfully without it for = years". Despite all this, the new ...AAtab file apparently isn't getting = recognized, as the new annunciator setup would not report any alarms to the LED's. = Sorry this is so long, but I wanted to make sure everyone understood the = situation. That given, is there any wisdom to be had? = RGC 12803 Josey Creek Ct. Cypress, TX 77433 713-805-8742 cell 281-256-1111 home office/FAX 281-256-1333 home **************Start the year off right. Easy ways to stay in shape. http://body.aol.com/fitness/winter-exercise?NCID=3Daolcmp00300000002489 = = _______________________________________________________________________ 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=3Djoin to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave = * Confidentiality Notice: This e-mail and any associated files are intended solely for the individual= or entity to whom they are addressed. Please do not copy it or use it for = any purposes, or disclose its contents to any other person. Further, this e= -mail and any associated files may be confidential and further may be legal= ly privileged. This email is from the Invensys Process Systems business uni= t of Invensys plc which is a company registered in England and Wales with i= ts registered office at Portland House, Bressenden Place, London, SW1E 5BF = (Registered number 166023). For a list of European legal entities within t= he Invensys Process Systems business group, please click here http://www.in= vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77. If you have received this e-mail in error, you are on notice of its status.= Please notify us immediately by reply e-mail and then delete this message = from your system. Thank you for your co-operation. You may contact our Help= desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx T= his e-mail and any attachments thereto may be subject to the terms of any a= greements between Invensys (and/or its subsidiaries and affiliates) and the= recipient (and/or its subsidiaries and affiliates). _______________________________________________________________________ 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