Support & Docs
FAQ & Contact
Check the FAQ first; if it doesn’t help, leave us a message — we reply within 24 hours on business days.
FAQ
Can I use it without coding?
Yes. Drag-and-drop widgets plus variable/expression bindings cover most UIs and interactions with zero code; drop into JS scripting and algorithm graphs when you need deeper logic.
Which chips are supported? Can it be ported to my board?
D126 (RT-Thread), GS32F00137 (ThreadX), and BK32888 are supported. The framework is chip/RTOS agnostic — a new platform only needs the seam layer adapted, with zero core changes, plus an online chip-pack mechanism.
How is simulation/hardware parity guaranteed?
The desktop simulator and target firmware share one widget catalog and protocol source; MQTT/SIP/RTP/Opus are continuously guarded by automated cross-verification.
How big is the firmware? Can resource-limited MCUs run it?
Firmware is trimmed by tiny/small/medium/full macro tiers — the smallest is a display-free pure control project, covering from 8051-class resources up to APUs.
How does the product prevent cloning?
A 1-Wire chip license token anchors trust in the chip’s unique key; unauthorized boards fail-closed, with a factory programming tool included.
Does it support customization / scripting?
Yes — three extension layers to choose from: a JS engine (gx.uart/can/spi/i2c bus APIs), a rule engine, and algorithm graphs.
How do I choose between a module and a display board?
Modules suit embedded products with serial connectivity (RS485/TTL) — design the UI free, then download. Display boards target volume products with richer WiFi/CAN/Ethernet and optional enclosure mounting. Dev kits are best for first evaluation.
Leave us a message
For purchase inquiries, chip adaptation, or solution matching, please describe your needs.