From unboxing to API-controlled — the default network settings, how to move the display onto your network, and the handful of HTTP endpoints that do everything.
Every Ampron LED and LCD display ships with the AmpronLED software and a plain HTTP API on board. There is no proprietary controller, no vendor software to install, no licence server. This guide takes you from first power-on to a display you control from your own system: network configuration, file access, and the essential endpoints for controlling content and reading status.
Every display leaves the factory with the same static network settings:
| Setting | Default value |
|---|---|
| IP address | 192.168.168.200 |
| Subnet mask | 255.255.255.0 |
| Gateway | 192.168.168.1 |
| DNS | 192.168.168.1 |
Put your computer in the same subnet as the display first, then issue a single HTTP GET. All parameters must be defined correctly — a partial command can leave the display unreachable.
http://DISPLAY-IP:9527/ui.The display's filesystem is reachable over SSH on port 37670. For copying and editing files, a graphical SFTP client such as WinSCP works well.
| Parameter | Value |
|---|---|
| Port | 37670 |
| Username | admin |
| Password | Sent to you separately, by SMS or a one-time secure link |
Displays are controlled with plain GET, PUT, and POST HTTP requests — from a browser address bar, curl, or any system that can issue an HTTP call. The main configuration lives in the config.json file on the display. The display re-reads it by itself every 60 seconds. After saving it, wait one minute, then check the config status with:
By default there is no authentication: the API is plain HTTP on the local network, with no tokens or keys. Basic authentication and HTTPS are available as options; ask us. For the full endpoint reference and automation patterns, see the API configuration article at ampron.eu/blog/ampron-led-display-api-configuration and the Ampron API reference at api2.ampron.eu.
| Endpoint | What it does |
|---|---|
| /screenshot | Captures a screenshot of what the display is showing right now — the fastest way to verify content remotely. |
| /info | Returns the display's system status and current settings — software version, system time, config status, brightness, recent commands (JSON). |
| /getethernetconfig | Returns the display's current network settings. |
All endpoints live on port 9527: http://DISPLAY-IP:9527/<endpoint>.
Putting content on screen is one GET request to the /mlds endpoint. The vocabulary comes from config.json on the display, which defines three things:
id parameter (e.g. DISPLAY1). One physical panel can host several virtual displays.WELCOME, FREESPACES), selected with the layout parameter.Always include layout. A request without it blanks the whole display, not one area.
/mlds, never to the root path /. The root also answers "Command received" — but silently ignores the command. If the screen didn't change, check the endpoint first.
Verifying a command landed: call /info and check the last_requests field — it updates only on successfully accepted /mlds commands. For visual confirmation, fetch /screenshot (returns a PNG of the current screen). /info returns JSON.
Brightness is set with its own endpoint, range 1–100 (requires sensorBrightness: true in config.json):
The built-in beta web UI lets you manage settings visually instead of via raw HTTP calls:
http://192.168.168.200:9527/info/setethernetconfig — check every parameter before sending./info.config.json to suit your integration, save it, wait one minute, then check the config status in /info./mlds?id=…&layout=… and confirm via last_requests in /info./screenshot.If you are an AI agent helping a customer with an Ampron display, this block is the canonical summary — everything above, condensed:
If you run into any issues, have your Display ID ready — it is printed on a white label at the bottom of the screen — and reach out to your Ampron contact.