Earlier iQunet servers
Find the model code on your installed server, choose its matching documents and plan software updates or support for your installation.
Find the model on your server
Use the model code on the label to choose the matching specifications and installation guide.
5.1 V iQunet Server
SERV199010-USB-5V2A
A compact single-board server connected to an iQunet Base Station, with Ethernet, Wi‑Fi and a 5.1 V supply.
- Power
- 5.1 V DC, 2.5 A supply with micro‑USB cable in the original package.
- Housing
- 120 × 102 × 18 mm, 105 g; ABS, IP20; 35 mm DIN‑rail installation.
- Environment
- 0°C to +55°C.
- Network
- Ethernet up to 300 Mbps; 2.4 / 5 GHz Wi‑Fi; USB connection to the Base Station.
Model documents
5.1 V server datasheetD1033-en-CUST-20081924 V DIN-rail iQunet Server
SERV199210-IND-24V1A
A server in a DIN‑rail housing for control-cabinet installations, connected to an iQunet Base Station. The source specifies Ethernet, Wi‑Fi and a 9–24 V DC supply.
- Power
- 9–24 V DC input; 24 V DC, 1.2 A maximum in the original specification. Reverse-polarity and supply-surge protection.
- Housing
- 58 × 107 × 95 mm, 180 g; ABS, IP20; 35 mm DIN‑rail mounting.
- Environment
- 0°C to +50°C.
- Network
- Ethernet up to 300 Mbps; 2.4 / 5 GHz Wi‑Fi; USB connection to the Base Station.
Industrial Edge (IPC) iQunet Server
SERV199310-IPC-FR201
A fanless industrial server with SSD storage, Ethernet, Wi‑Fi and DIN‑rail mounting. This is a separate model from the Edge Gateway M4; use its own specifications and quick-start guide.
- Processor & storage
- Quad-core ARM Cortex-A72, 1.5 GHz; 4 GB RAM; 64 GB M.2 SATA SSD.
- Power
- 8–24 V DC, 22 W maximum through a 3-pin terminal block. PoE is an optional configuration, not standard equipment.
- Housing
- 102.5 × 129 × 38 mm excluding antenna; 400 g including antenna. Back or edge DIN‑rail mounting, IP20 for indoor use.
- Environment
- −20°C to +60°C; 10–95% relative humidity, non-condensing.
- Network
- Gigabit Ethernet, dual-band 802.11ac Wi‑Fi with external antenna and USB-A connection to the Base Station.
Software, support and the next step
The original server documentation describes a browser-based Sensor Dashboard, local data logging, embedded OPC UA and GraphQL interfaces, and Google Sheets or CSV export. Features and connection procedures depend on the software version installed.
These servers collect and store data locally and can continue local monitoring without an internet connection. Wireless sensors connect through the matching Base Station. The original software also describes Wi-Fi hotspot or Ethernet access, WebRTC remote access, a system clock, Storage Manager and Data Explorer. Available tools and connection methods depend on the installed release.
Support for your server
Contact iQunet about support, updates, replacement options and availability for your specific model.
CloudLink (deprecated)
CloudLink is deprecated. The following documentation is retained as a historical reference for existing installations.
The original service mirrored the local server namespace and values, including historical measurements. It made synchronized data accessible through CloudLink while an edge server was offline.
It provided one access point for one or several edge servers, with OPC UA and a MySQL proxy for compatible tools such as Grafana.
CloudLink was a separate annual subscription for each synchronized server. It was distinct from local gateway monitoring and from the Anomaly Detection Service.
Original connection reference
The documented setup first adds the edge server through WebRTC with a unique OPC UA username and password. Those credentials are used for both the OPC UA and MySQL frontends.
In the original guide, synchronization begins when an OPC UA or MySQL client first connects. The address space may initially be empty; allow synchronization to complete and browse the Objects node again.
The original guide uses Root > Objects > Server > ServerStatus > SyncStatus in the OPC UA client. Its documented states are idle, syncing and error; normal updates could alternate between idle and syncing.
The MySQL proxy supported a limited SQL command set. The original manual preserves the version-specific commands and connection details.