Search the Community

Showing results for tags 'alarm'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • DAQFactory
    • Alarming
    • Channels, Conversions and general data acquisition
    • Graphing
    • Logging
    • Modbus
    • Networking: web, email, FTP etc.
    • PID
    • Screen Components and User Interface
    • Sequences and scripting
    • Serial Communications
    • General DAQFactory
    • DAQFactory and the LabJack
    • DAQFactory Express
    • DAQConnect
    • DAQFactory New Feature Requests
    • The DAQFactory Guru's Articles
    • DAQFactory Newletters

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Terry

    Alarm Summary

    New at this. I was surprised and disappointed that DAQF does not include an alarm banner on the operating screen showing all active alarms. What is typically done to allow easy access to alarm information to the operator? Thanks, Terry
  2. raining010

    Resident Alarm Data

    Hi, Admin I met a strange thing about DF alarms today. While I started program, there were some active alarms, but actually there was no alarm (no alarm data from outside via communication). I checked the data, these alarm happened in last year. I tried to restart the program many times, but these alarms were always active. Why? And how to clean these? I use 5.87a Thanks
  3. bmillereng

    Alarm reset

    I send a group of alarm bits to DAQConnect in a word, then decode the individual bits to recover specific alarm conditions. That part is working fine. I have them configured to automatically reset. When an alarm occurs for an extended period of time, it appears that DAQConnect fires, resets, then fires again, creating a series of new alarms. It repeats this on essentially the same timing as the data updates (fire on one, reset on the next, etc.). I would have expected the alarm to remain fired until an update had that bit clear, then reset, creating one alarm. I suspect that requiring manual reset might solve this, but I would prefer to reset automatically. Any suggestions on how to change this?