Brand lock-in
Different FSU vendors expose different UIs, debug flows, and internal models — raising training cost and blocking unified operations.
Field Supervision Unit Operating System
Open-interface FSU software that turns locked collectors into a white-box edge layer
FsuOS (Field Supervision Unit Operating System) is Junguang’s software runtime for power and environmental monitoring at the site edge. It decouples control software from FSU hardware so operators and OEMs can standardize acquisition, alarming, and northbound publishing — without ripping out every box.
US go-to-market is software licensing (Site / Fleet / OEM Runtime). Hardware remains partner- or customer-owned Linux FSU platforms.
Protocol-ready northbound: Modbus · SNMP · IEC 61850 · dual-send · open driver/extension model
Why white-box FSU software exists
Mixed-vendor FSU fleets create locked stacks: each hardware brand ships a closed control plane. Swap a box and you rewrite drivers and northbound maps. FsuOS attacks that failure mode at the software layer.
Retrofit friction
Sites already have Linux collectors in the field. Replacing hardware just to modernize software burns CapEx and risks downtime.
Northbound mismatch
Upstream SCADA/DCIM/BMS want clean Modbus/SNMP/API feeds — often to more than one consumer at once.
Architecture (operator view)
FsuOS is built as an FSU runtime: drivers southbound, apps for alarming/history/mapping, and northbound servers for open protocols. White-box means the same software logic can target supported Linux FSU platforms.
DevicesUPS · rectifier · battery · HVAC · sensors · DI/AI
DriversProtocol / device libraries
FsuOS AppAlarm · history · schedule · maps
FSUServersModbus · SNMP · 61850
UpstreamDCIM · EPMS · BMS · cloud
Core components
FSUWeb — local commissioning UI and configuration.
FSUServers — northbound service endpoints.
Drivers — southbound device protocols.
Apps — alarm logic, history/cache, point mapping.
I/O abstraction — hardware interface layer for multi-board support.
Design principles
Decouple software from a single OEM binary. Keep field wiring and devices. Prefer remote image/update workflows where hardware allows. Preserve operator debugging habits where possible so white-box rollout does not throw away tribal knowledge.
White-box FSU
Retrofit-first
OEM runtime
Dual-send
What FsuOS standardizes at the edge
Acquisition & control
Collect from power plant and environmental objects — UPS, switching power, battery strings, CRAC/HVAC, DI/AI sensors — then normalize points for upstream systems.
Open northbound
Publish via Modbus TCP/RTU, SNMP, and IEC 61850 where required. Dual-send supports two upstream consumers without forking the site stack.
Fleet operations
Unify mixed FSU brands under one software control plane for commissioning, alarm policy, and driver extension — aimed at operators and OEM partners.
FSU & device catalog (supported ecosystem)
Below is Junguang’s own FSU and field-device family commonly paired with FsuOS. In the US we lead with software; these models show the hardware depth behind the runtime. Full list on the catalog page.
| Model / item | Class | Role with FsuOS | Highlights |
|---|---|---|---|
| SMD-303X | FSU | Primary Linux FSU host | 1U multi-I/O collector; DI/DO, AI, serial, network; Cortex-A7 Linux; cabinet or wall mount |
| SMD-303Pro | FSU | Carrier-grade FSU target | China Unicom / China Telecom B-interface certified FSU lineage (China market); full FsuOS support story |
| SMD-303Pro-NG (RISC-V) | FSU | Next-gen FSU platform | RISC-V FSU variant announced for open ISA edge deployments |
| SMD-303mini | FSU | Compact site / outdoor hut | Built-in temp/humidity + leak; serial + Ethernet/4G options; Class-D / outdoor station focus |
| JG-980 | Core board | OEM module | In-house Linux core board (UART/USB/Ethernet/4G) for custom FSU bases |
| Temp/humidity · smoke · leak | Sensors | Southbound objects | Analog or RS-485 TH; photoelectric smoke; conductive leak rope/probe to DI |
| Battery monitor (JC-TA/TC) | Battery | String health telemetry | Per-cell voltage/resistance/temperature + string current module |
How a software-first rollout looks
Fit check
Share FSU hardware matrix, I/O map, and northbound targets (Modbus/SNMP/61850/API).
Share FSU hardware matrix, I/O map, and northbound targets (Modbus/SNMP/61850/API).
Evaluation license
30-day eval, node-capped, dual-send included — validate commissioning time and alarm quality.
30-day eval, node-capped, dual-send included — validate commissioning time and alarm quality.
Production package
Site, Fleet, or OEM Runtime quote (quote-only in early US phase). Optional NRE for new board bring-up.
Site, Fleet, or OEM Runtime quote (quote-only in early US phase). Optional NRE for new board bring-up.
How to buy FsuOS
FsuOS is sold as software licenses (not hardware checkout). US buyers follow one path: fit check → evaluation → quote → PO.
Standardize the edge software layer
Keep your Linux FSUs. Validate protocols and dual-send in a 30-day evaluation, then purchase Site or Fleet licensing.
Ship Runtime with your hardware
License OEM Runtime for your collector line. Optional NRE if a new board needs bring-up.
Fit check
Send FSU/collector models, point list, southbound protocols, and northbound targets (Modbus / SNMP / IEC 61850 / dual-send).
Evaluation
30-day evaluation license, node-capped, dual-send included. Prove commissioning time and alarm quality on your site.
Quote → PO
Choose Site, Fleet, or OEM Runtime. Early US phase is quote-only (no public MSRP).
Start here
Use the button that matches where you are. Each email is pre-filled so we can respond with a fit checklist.
What you are buying: software entitlement + support window. Hardware stays yours or your partner’s.
See FsuOS on your hardware matrix
Send your collector model list and upstream protocol needs. We’ll return a fit checklist and evaluation terms — no public MSRP in the first 90 days.
Contact: contact@jgcxtech.com · Product: fsuos.com · Company: jgcxtech.com