Speed alarms in Factbird are triggered based solely on production counts compared to the validated speed. They are not influenced by stop events - whether micro stops or full stops - and do not reset when a stop ends. The alarm activates when the average speed, calculated from the counts, drops below the configured threshold.
Articles in this section
- What calculations do you use for OEE?
- How do I purchase a Factbird?
- Can I override sensor data for a specific time period?
- What is NPN/PNP Sensor types?
- Where can I find the API Documentation?
- Can I change validated and expected speed for past production?
- Why do I get "Error Message: Company does not have access to device: [Device ID]"?
- How does stops affect speed alarms?
- Why does the system display "You do not have access to #" when opening a line, or why does my Factbird View not appear?