Application · Project rescue
Yes — and you probably don't have to reverse-engineer their black box. The field devices are almost always standard RS485 / Modbus, so a fresh Siliqs node reads them directly, independent of whatever the old contractor built. The data comes out over an open mesh, everything is set up in a browser, and the protocols and tools are open — so you finish the project, own it, and never get orphaned again.
A monitoring or automation project was half-built when the original contractor — the system integrator who installed it — went out of business, walked away, or simply stopped answering. What's left is a partial installation with no documentation, no source code, and no passwords. Some points still report, some are dead, and nobody will touch it because nobody understands it. The project is an orphan.
Read the devices fresh, bring them out on open standards, hand you the keys.
A Siliqs node connects to an existing meter, sensor or PLC over its standard RS485 / Modbus port and reads it fresh. It doesn't need to know anything about the old contractor's system.
The readings come out over a self-healing LoRa mesh — standard and documented, not a proprietary gateway only one company can service.
Configure, extend and maintain it yourself — or with any integrator — using free browser tools. No source code to inherit, no single vendor to depend on.
No original contractor, no passwords, no source code — just the label on the device.
The reason this project became an orphan was lock-in. The fix is openness.
Usually yes. The field devices almost always speak standard RS485 / Modbus, so a fresh Siliqs node reads them directly and brings the data out over an open mesh — you bypass the abandoned system instead of decoding it.
Usually not. Siliqs reads the devices fresh and independently, so it doesn't need the old system's internals. What matters is the device's standard interface, which is still there.
You don't need the old settings. Read the brand and model off the device's label, download its datasheet (the Modbus register map), and have an AI assistant such as ChatGPT turn that into the config blob. Load it into the node in the browser and read the values back to confirm — often under ten minutes per device.
No. You reuse the field devices and finish incrementally — recover the working points first, then complete the parts that were never wired, node by node.
Openness. Modbus is a standard and the mesh runs open-source Meshtastic; the tools are free and documented, and the Gateway is open-source. Any competent integrator can maintain it — you're not locked to us either.
Anything that exposes a standard RS485 / Modbus interface we read directly. A device that's entirely closed may need replacing — we'll look and tell you straight which is which.
Yes. Add a node at each unfinished point; it joins the same mesh, so recovering and completing the project happen the same way.
Tell us what's installed and what's dead, and which devices you can still identify. We'll tell you straight what can be recovered.
