OIF Fault Parameters
Posted 11 January 2005 - 04:29 PM
- LINE VOLTAGE MONITOR / REPORT LVM VIA NETWORK
- POWER SUPPLY TEMPERATURE MONITOR (Is this part of Thermal Error?)
- IOC MONITOR / REPORT IOC ERROR VIA NETWORK
- REPORT SUPERVISOR ERROR VIA NETWORK
- THERMAL ERROR / REPORT THERMAL ERROR VIA NETWORK
Other OIF entries look promising, but I just don't know enough about them to know (i.e. Proportional VCC Monitor, Sharc workload, Power Supply Current). Are there addtitional critical faults that I can access through UDP-IP that I have not listed? Are there other faults tied to the front panel Fault Indicator that I can tap into?
Also, the UDP protocol says that application errors are only broadcast to controllers that have sent an idGetState within the past 30 seconds. Can I send ANY idGetState to qualify, or does it have to be a poll of that specific error? In other words, do I have to continuously poll all errors that I want to monitor?
Posted 14 February 2005 - 02:09 PM
Posted 18 February 2005 - 12:14 AM
I am sorry that you feel this way about our documentation. The documentation is provided as a service for anyone who wants to develop their own control and monitoring with third party controls. We have had many people use it successfully nationally and internationally without any problem. When it is provided we tell everyone straight out that we do cannot support it other than providing it as each third party control system operates differently.
My apologies for the delay in getting you a response I will try to get you an answer as soon as I can. Since your posting on the "IQ Forum" we have moved to a new server and expanded to become the "Crown Forums" and were shut down for a while during this transition. It appears your question has fallen through the cracks. Again my apologies as we take all questions seriously and try to provide answers as best we can.
Posted 22 February 2005 - 09:37 AM
Posted 22 February 2005 - 07:26 PM
I have asked checked for some additional information regarding error states and keeping a subscription open. Object 16385 lists all the possible error strings. ANY idGetState message qualifies to keep a subscription open.
Business Development Manager - Crown International
Posted 20 April 2005 - 10:13 AM
"Object 16385 lists all the possible error strings."
How do I call object 16385? I tried issuing an IdGetState request and referenced
HEX . I received the following error: "error: bogus object id in description: 16385". I am running firmware v1.301 in an ITech8000.
I also get the same "error: bogus object id in description: 16272" when I query the Component Online status and "error: bogus id in description: 16312" when I query the IQ Address. These last two are listed in the OIF file, while the error string object is not. Any help is appreciated.
If easier, it would be a huge help if you could cut-n-paste the error string dump to this forum. Thanks.