Industrial FAQs
What is the optimal placement for an Atom on a motor?
For vibration and temperature monitoring, place the Atom directly on the motor housing, preferably on a flat surface. Ensure the Atom is securely attached using the appropriate mounting method (adhesive or magnetic mount). For vibration monitoring, place the device as close as possible to the bearing housing for best results.
How do I ensure proper adhesion of the Atom to equipment?
Before attaching: Clean the surface thoroughly to remove any oil, dust, or debris Allow the surface to completely dry For permanent installation, use industrial-grade adhesive For magnetic mounts, ensure the surface is ferrous and flat
How do I ensure proper Gateway placement for optimal connectivity?
Place Gateways with a clear view of the sky for GPS capability Ensure Gateways have strong cellular connectivity Position Gateways within Bluetooth range of all connected Atoms (AT-R and AT-C devices) For large facilities, multiple Gateways may be required to ensure coverage
How can I check if my Atom has established a connection?
Check the dashboard for: Online/Offline status in the Status Summary “Last Uploaded” timestamp in the Devices tab “Last KA” (Keep Alive) timestamp for Gateways
What should I do if my device shows as “Offline” after installation?
Verify the Gateway is online and has cellular connectivity Check if the device is within Bluetooth range of its assigned Gateway (for AT-R and AT-C devices) For Stand-alone units (AT-U), check cellular connectivity status Ensure the device has been properly assigned to the correct Gateway in the dashboard Consider using “Deployment Mode” during installation to increase connection attempts
What is “Deployment Mode” and when should I use it?
Deployment Mode is designed specifically for initial installations. When activated, it increases the frequency of Keep Alive signals and data uploads for a 3-hour period, allowing installers to verify connectivity and proper setup before finalizing the installation.
What are the recommended vibration threshold settings for motors?
While specific thresholds depend on your equipment’s characteristics, a general starting point for vibration is 0.4G for the lower threshold and 1G for the upper threshold.
How often should I set my devices to take readings?
For most motor applications: Sampling Timer: 12 or 24 hours for periodic readings (battery-optimized) Event Check Frequency: Every 5 minutes is typically sufficient for monitoring without excessive battery drain For critical equipment, more frequent checks may be warranted at the expense of battery life
What is the recommended Event Check Frequency for vibration monitoring?
For most motor applications, checking every 5 minutes provides a good balance between timely detection and battery life. For more critical applications, you may reduce this to 1-2 minutes, understanding that this will impact battery longevity.
How should I configure Post-Event readings?
For motors experiencing anomalies: Number of Samples: 5-10 readings is typically sufficient to determine if the condition persists Frequency of Samples: Every 5 minutes will provide a 25-50 minute window to observe if conditions return to normal
Why isn’t my device showing its location on the map?
Several factors affect GPS location: Stand-alone units and Gateways require a clear view of the sky Devices only attempt to secure GPS every 48 hours AT-R devices only provide location if the “Read Now” button was pressed in the app during installation Indoor installations often have limited GPS capability
Can I manually enter the location for my device?
Yes. For devices without GPS capability (or indoor installations), you can manually enter the latitude and longitude coordinates in the Device settings page under the Management tab.
How do I ensure the right people receive alerts for specific equipment?
Alerts are managed at the Unit level: Navigate to the Units tab in Management Select the Unit associated with your motor/equipment Add the specific users or contacts who should receive alerts for this equipment Remember that each Unit must have users/contacts added individually
Why aren’t team members receiving alerts for threshold violations?
Several factors could cause this: The user/contact may not be added to the specific Unit in the Management section The user’s phone number may be incorrect or missing the country code (+1 for US) The thresholds may not be properly configured The device may not be communicating with the Gateway or cloud
How will my monitoring configuration affect battery life?
Several settings impact battery life: Event Check Frequency: More frequent checks reduce battery life Sampling Timer: 1-hour periodic readings significantly reduce battery life Number of active sensors: More sensors consume more power Post-Event readings: Frequent or numerous post-event readings increase power consumption
What is the expected battery life for a typical motor monitoring setup?
With standard settings (12-24 hour Keep Alive, 5-minute Event Check Frequency, 2-3 active sensors), the expected battery life is approximately 2-3 years. More aggressive settings will reduce this estimate.
How can I quickly identify which motors are experiencing issues?
Use these dashboard features: Status Summary: Shows devices with trigger events Alerts section: Provides a chronological list of recent alerts Events Report: Lists all trigger events by device and type Analytics: Shows run-time and idle time for specific equipment
What’s the best way to compare performance across multiple motors?
Use the Insights section: Navigate to the Insights tab Create a graph with multiple motors’ vibration or temperature data Use the comparison feature to overlay data from similar equipment Save important comparisons to the Overview tab for quick access
How can I tell if a motor is deteriorating over time?
Use the Graph Builder to create time-based trends of vibration readings Look for gradually increasing vibration levels Monitor the frequency of alerts over time Track patterns in post-event readings to identify recovery time after alerts Compare current performance to historical baselines
