====== Drive the OnAirScreen ON AIR LED from ProppFrexx ======

[[https://www.radio42.com/|ProppFrexx ONAIR]] can turn OnAirScreen **LED1** (factory label **ON AIR**) from a **mixer-channel** event (fader start / channel ON) via ''EXEC_SEND_HTTP_GET''.

This is **not** the current-title howto. Titles: [[onairscreen:proppfrexx-en|Show the current ProppFrexx title on OnAirScreen]].

API reference: [[oas:api|OnAirScreen API / UDP / HTTP / MQTT]]\\
Mixer GPI on a Raspberry Pi (no playout in between): [[onairscreen:manual-en|User Manual]] (GPIO)\\
ProppFrexx: [[https://www.radio42.com/proppfrexx/forum/viewtopic.php?t=12|Control-Commands]] (mixer events, ''EXEC_SEND_HTTP_GET''), [[https://www.radio42.com/proppfrexx/forum/viewtopic.php?t=2191|HTTP GET from a fader]]

===== Two different “on air” signals =====

^ Signal ^ What it is ^ Use for LED1? ^
| Mixer channel ON / ''OnFaderStart'' | Mic or channel live on the desk (or ProppFrexx mixer strip) | **Yes** — this is the studio lamp |
| Playlist playing / OnTrackPlay | A file started | No — that is the [[onairscreen:proppfrexx-en|title]] path |

===== 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''. Commands are **GET** only.

On **Windows** test with ''oas_send.exe'' from the OnAirScreen license:

<code>
oas_send.exe --ip 192.168.23.5 "LED1:ON"
oas_send.exe --ip 192.168.23.5 "LED1:OFF"
</code>

If OnAirScreen runs on **the same PC**, use ''127.0.0.1''. Firewall: TCP **8010**.

===== Recommended path: mixer event to HTTP GET =====

**General settings → Events/Commands** (GPIO/Remoting). On the **mixer channel** that is the mic / on-air source, assign:

  * Channel ON or **OnFaderStart** (pressed / fader open):

<code>
EXEC_SEND_HTTP_GET http://OAS-IP:8010/?cmd=LED1:ON
</code>

  * Channel OFF or fader closed / **OnFaderStart** released:

<code>
EXEC_SEND_HTTP_GET http://OAS-IP:8010/?cmd=LED1:OFF
</code>

Omit username/password in ''EXEC_SEND_HTTP_GET'' — OnAirScreen does not use HTTP auth. [[https://www.radio42.com/proppfrexx/forum/viewtopic.php?t=2191|Forum: EXEC_SEND_HTTP_GET]]

Event names match the Control-Commands list (mixer-channel events such as ''OnFaderStart''). Use the event that tracks **desk live**, not ''OnTrackPlay''.

===== Option B — GPIO / GamePort / Livewire =====

A hardware fader-start (GamePort, Velleman, IO-Warrior, Livewire+, Ember+) maps the same way: **GPIO message mapping** to the two ''EXEC_SEND_HTTP_GET'' commands above (pressed = ON, released = OFF). Test the mapping in the GPIO monitor first so ON is the closed contact, not the open one.

===== Other commands =====

  * ''EXEC_SEND_HTTP_POST'' — OnAirScreen commands are **GET** only.
  * ''EXEC_SEND_TCP'' — OnAirScreen has **no** TCP command port.

===== Notes =====

  * Raspberry Pi with a desk contact: GPIO in the [[onairscreen:manual-en|User Manual]] is shorter than going through ProppFrexx.
  * Questions: [[https://www.astrastudio.de/kontakt/|Contact]]

===== Other LED howtos =====

[[onairscreen:mairlist-led-en|mAirList]] · [[onairscreen:proppfrexx-led-en|ProppFrexx]] · [[onairscreen:myriad-led-en|Myriad Playout]] · [[onairscreen:playoutone-led-en|PlayoutONE]] · [[onairscreen:rodecaster-pro-ii-led-en|RØDECaster Pro II (MIDI)]]

Titles: [[onairscreen:mairlist-en|mAirList]] · [[onairscreen:radioboss-en|RadioBOSS]] · [[onairscreen:radiodj-en|RadioDJ]] · [[onairscreen:playoutone-en|PlayoutONE]] · [[onairscreen:stationplaylist-en|StationPlaylist]] · [[onairscreen:proppfrexx-en|ProppFrexx]] · [[onairscreen:myriad-en|Myriad Playout]] · [[onairscreen:zetta-en|RCS Zetta]]