| Field | Recommended Setting | |-------|---------------------| | | mqtt://broker.mycompany.com:1883 | | Client ID | auks-043-<serial> | | Username / Password | As provided by your cloud service | | TLS | Enable, upload CA certificate (PEM) | | Topic Prefix | auks/043/<site-id>/ |
| Task | Frequency | How‑to | |------|-----------|--------| | | Monthly (or as released) | Portal → System → Update, or use ssh and run sudo apt update && sudo apt upgrade . | | Disk health check | Quarterly | Portal → System → Storage → Run fsck . | | Cleaning | Every 6 months | Power off → wipe exterior with a dry microfiber cloth; avoid liquids. | | Backup configuration | After any major change | Portal → System → Backup → Download config.tar.gz . | | Restore configuration | When migrating or after a failure | Portal → System → Restore → Upload config.tar.gz . | | Thermal paste replacement (CPU/NPU) | Every 2 years (if operating >50 °C) | Open the rear panel (see Service Manual, Appendix B). | auks-043
You can also enable or Webhooks under Integrations → Outbound for services like Azure IoT Hub, AWS Greengrass, or Google Cloud IoT Core. | | Backup configuration | After any major
| Port | Typical Use | Tips | |------|-------------|------| | | Primary data link, PoE | Use Cat‑6 or higher for gigabit speeds. | | Wi‑Fi antenna (on board) | Wireless LAN | Keep the enclosure away from metal shielding. | | BLE | Short‑range sensor mesh | Pair devices via the web UI (Section 6). | | GPIO | Custom sensor/actuator | Refer to the pin‑out diagram (Appendix A). | | Analog Inputs | Voltage or current transducers | Use proper scaling (0‑3.3 V or 0‑10 V) and shielding. | | CAN / RS‑485 | Industrial bus connections | Terminate the bus with 120 Ω (CAN) or 100 Ω (RS‑485) at the far end. | | USB‑C (OTG) | External storage, dongles | Power‑delivery limited to 900 mA; use a powered hub for high‑draw devices. | | You can also enable or Webhooks under