B-Station2 - OSC task works individually but not when triggered by action

[fabian@glr]

Hi,

I have a B-Station2 (firmware 1.24) sending OSC to a Cuety LPU-2.

When I execute an OSC task individually (via the task execute button), it works perfectly; the LPU-2 receives and responds to the command. However, when the same OSC task is the only task inside an action and that action is triggered (via Network Connection trigger or the manual action execute button), the OSC task does not execute.

LED tasks inside actions do work correctly with the same triggers.

I have tried:
Multiple trigger types (Network Connection, Button)
Multiple trigger flanks (Change, Start, Stop)
Multiple OSC URIs (/pb09/bu, /pb09/go+)
Firmware is up to date (1.24)

Is this a known issue, does anyone know how to fix this, or am I missing something in the action/task configuration?

Thanks

[Jorge Solano]

Hello Fabian,

Thanks for the clear description 

The behaviour you describe is not what we would normally expect. Since the OSC task works from its individual Execute button, the B-Station2 is able to communicate with the LPU-2.

Could you try a fresh Action with only this task:

OSC → Send Bool → Set
URI: /pb09/go+
Value: true

Then open Monitor → OSC and compare what happens when you execute the task individually, execute the complete Action, and trigger the Action from a button.

For this test, please use /pb09/go+ rather than /pb09/bu, since /bu requires a true → false sequence to emulate the Cuety button press.

You can also try the built-in Buttons -> LPU-2 template as a comparison.

If the OSC message appears in the monitor when executing the task individually, but nothing is sent when executing the complete Action, please send us a screenshot of the Action and OSC task configuration, your Settings → OSC page, and if possible a backup of the B-Station2 configuration and the LPU-2 firmware version. We can then reproduce this here on firmware 1.24 and investigate further.

Hope this helps!