One protocol, every model
All c-power controllers share one external call protocol.
You do not rewrite the integration when the screen or the model changes.
Custom development
Built for integration
Every c-power controller answers the same external call protocol.
Integrate once and the same code drives a text card or a video controller.
SDK and protocol documentation
An SDK and the protocol specification cover the whole series.
Your developers work against a documented interface, not a black box.
Serpentine wiring and screen.map files let one port drive several module rows.
Reads data from your equipment
Controllers take data over serial, Ethernet, Wi-Fi and cellular links.
Screen content can follow a live reading instead of a fixed schedule.
View accessoriesRuns without the network
Programs, real-time clock and brightness control run on the card itself.
The screen keeps playing when the link drops.
What gets built on it
Content that follows a sensor value
temperature, humidity, wind direction, PM2.5, PM10, CO2
Screens driven by an operations system
flight information, motorway messages, car park occupancy
Integration with your own CMS or ERP
Custom playback logic and protocol wrappers for your development team