Every pixel,
on signal.

Controllers, receiving cards and software carry content from your system to full-colour and seven-colour LED screens.

§01Product lines

Choose by the screen you build.

Full-colour controllers use greyscale for images. Seven-colour controllers switch each colour on or off for text and graphics.

§02Custom integration · our core strength

Your protocol. Our controller.

Share a protocol document or describe the screen behaviour. We assess the firmware integration with your system, device or platform.

RS-232RS-485TCPUDP4GMQTTWebSocketHTTPNTCIPModbus RTUModbus TCPNMEA 0183CAN busExpressway signsToll lanesBus platformsBaggage systemsRadarAlarm panels+ your protocol

Project-dependent integration paths; confirm the required hardware and firmware.

Have a protocol?
We make the controller speak it.

Serial, TCP, 4G or your own platform. A new protocol is a firmware project, not new hardware.

Start a custom project

§03Built to integrate

One protocol. Connected systems.

Use the shared c-power SDK and external-call protocol across the controller range. Check command support against the model and firmware.

SDK · direct protocol · remote server

Choose your connection path and explore illustrative screen responses.

Read integration manuals

Packet inspector

Every byte explained.

Choose a command and frame format. Select a byte to inspect its field and the calculated checksum.

Read time · show text · set brightness

Local examples include checksum and frame escaping.

Open the full playground →

Native integration

Windows & Linux

Windows 32-bit and 64-bit libraries; Linux x86 library. Confirm platform and protocol support.

Java integration

JVM & ARM

Java integration for discovery, display windows and programme files.

Sample languages

Your application stack

C / C++ · C# · VB.NET · Delphi · Java

Open protocol

TCP & serial

Documented frames, checksums and byte escaping.

§04In the field

Where screens go to work.

§05Operations

Look after the whole screen.

Remote programme updates

Update screen programmes remotely on supported models.

Scheduled on/off

Set the times when screens switch on and off.

Connection status

Check the connection status of supported controllers.

Brightness and temperature

Manage brightness and view temperature information.

Batch publishing

Publish programmes to multiple supported screens.

Group management

Organise supported screens into groups.

Confirm the model and required sensors. Wi-Fi variants do not support cloud management.

Explore cloud management

§06Signal path

From content to module, one chain.

Step 1 · Your system

  1. Your system

    PC / platform / field device

    Send content from your PC, platform or field device.

    Explore details
  2. C-Power 50A

    Works with a KB hub board

    It works with a hub board matched to the module interface: KB21 for HUB75; KB20, KB04 or KB02 for others.

    Explore details
  3. LED modules

    Check interface and chip

    Confirm the module interface, scan type and driver chip before specifying the system.

    Explore details

§07Refresh, on camera

See the refresh difference.

High refresh: 5 and 7 Series with a listed PWM driver chip. X5A-4G requires a custom programme.

Check driver chips

§08Selection tools

Find your controller.

Enter the screen dimensions and pixel pitch. Match catalogue resolution limits, then carry the result into your RFQ.

Choose by screen size, colour and connection requirements.

Open full Finder

Tell us the screen.
We specify the system.

Screen size · pixel pitch · module interface · driver chip · quantity

Start an RFQ[email protected]