We build rugged LoRa, RS485 and IoT nodes at Siliqs — the SQC485Iv2 industrial node, the SQS-TH-I sensor, and the mesh, gateway and provisioning tooling that sits around them. A lot of the interesting work never makes it onto a product page, because a product page has to sell the product, not walk through how it actually works.
This blog is where that second part lives. Expect posts about:
- Protocol design — how a private LoRa mesh carries Modbus RTU traffic without pretending to be Modbus RTU, and where that abstraction leaks.
- Firmware tradeoffs — flash budgets, OTA slot sizing, and the kind of bring-up problems that only show up on real hardware.
- RF and hardware — antenna matching, SIR thresholds, and the gap between a datasheet number and what you actually measure on a bench.
Nothing here is marketing copy. If a post is wrong or a measurement doesn't hold up, we'll say so in a follow-up rather than quietly editing it away.
If you have a specific question about how one of our nodes works under the hood, get in touch — it might turn into the next post.
Siliqs 做的是堅固耐用的 LoRa、RS485 與 IoT 節點——SQC485Iv2 工業節點、 SQS-TH-I 感測器，以及圍繞它們的 mesh、gateway 與燒錄設定工具。這些東西背後 有很多有趣的細節從來沒機會寫進產品頁，因為產品頁的任務是把產品賣出去， 不是講清楚它實際是怎麼運作的。
這個 blog 就是用來放這些內容的地方。之後會陸續寫：
- 協定設計 — 私有 LoRa mesh 怎麼扛 Modbus RTU 流量，卻又不假裝自己 「就是」Modbus RTU，以及這層抽象在哪裡會露餡。
- 韌體取捨 — flash 空間預算、OTA slot 大小規劃，以及那些只有在真實硬體 上才會冒出來的 bring-up 問題。
- RF 與硬體 — 天線匹配、SIR 門檻,以及規格書上的數字跟實際在工作台上 量出來的數字之間的落差。
這裡不會放行銷文案。如果哪篇文章寫錯了，或量測結果站不住腳，我們會在後續 文章裡講清楚，而不是悄悄改掉了事。
如果你對我們某顆節點底層怎麼運作有具體問題，歡迎 跟我們聯絡——搞不好就變成下一篇文章的題目。