This is an old revision of the document!
Drive the OnAirScreen ON AIR LED from PlayoutONE
Aiir PlayoutONE can turn OnAirScreen LED1 (factory label ON AIR) when Data Controller sees a mixer GPI (Axia, Wheatstone, serial) and runs RUNAPP with oas_send.
This is not the current-title howto. Titles: Show the current PlayoutONE title on OnAirScreen.
API reference: OnAirScreen API / UDP / HTTP / MQTT
Mixer GPI on a Raspberry Pi (no playout in between): User Manual (GPIO)
Aiir: Data Controller, Axia GPI, Commands (RUNAPP, IPCOMMAND)
Two different “on air” signals
| Signal | What it is | Use for LED1? |
|---|---|---|
| Data Controller GPI (Axia pin, Wheatstone LIO, COM closure) | Desk tally into PlayoutONE | Yes — this is the studio lamp |
ONAIR / OFFAIR / ONAIR CHANGE | Which PC is the on-air machine | No — studio take-over, not mic live |
ONAIR CHANGE is the wrong event for a lamp.
What OnAirScreen expects
| Channel | Target (default) | Example |
|---|---|---|
| HTTP | Port 8010 | http://OAS-IP:8010/?cmd=LED1:ON |
| UDP | Port 3310 | LED1:ON |
Same pattern for off: LED1:OFF. OnAirScreen has no TCP command port — do not point IPCOMMAND at UDP 3310.
On Windows test with oas_send.exe from the OnAirScreen licence:
oas_send.exe --ip 192.168.23.5 "LED1:ON" oas_send.exe --ip 192.168.23.5 "LED1:OFF"
Use oas_send-noconsole.exe from the same licence in RUNAPP so no console flashes on air. If OnAirScreen runs on the same PC, use 127.0.0.1.
Recommended path: Data Controller GPI to RUNAPP
1. Data Controller running; mixer integration on (e.g. Settings → Integrations → Axia node). What is Data Controller?
2. Two PlayoutONE Commands (Command Manager):
LED1 on (RUNAPP path, then > then arguments — RUNAPP):
RUNAPP C:\Path\To\oas_send-noconsole.exe>--ip 192.168.23.5 "LED1:ON"
LED1 off: same with LED1:OFF. Adjust the path to where the OnAirScreen tools sit.
3. Data Controller command matrix: incoming GPI (Axia pin ON/OFF, Wheatstone SLIO, serial string) to those two commands. Pin ON / high → LED1 on; pin OFF / low → LED1 off. You can keep an existing “Play Next” mapping and add a second command for the lamp.
Axia GPIO capture: Connecting to Axia nodes.
Firewall: the PlayoutONE PC must reach OnAirScreen TCP 8010 (oas_send uses HTTP) or UDP 3310.
Option B — HTTP without oas_send
If you would rather hit the API from a one-liner:
RUNAPP C:\Windows\System32\curl.exe>-s "http://192.168.23.5:8010/?cmd=LED1:ON"
OnAirScreen still needs GET. There is no PlayoutONE “HTTP GET metadata output” for GPI — Monitor metadata is titles only (title howto).
Notes
IPCOMMAND host:port TEXTopens a TCP socket and writes a string. That does not match OnAirScreen’s UDP command port. PreferRUNAPP+oas_send.- Raspberry Pi with a desk contact: GPIO in the User Manual is shorter than Data Controller.
- Questions: Contact
Other LED howtos
mAirList · ProppFrexx · Myriad Playout · PlayoutONE
Titles: mAirList · RadioBOSS · RadioDJ · PlayoutONE · StationPlaylist · ProppFrexx · Myriad Playout · RCS Zetta