ProgramObject writing to NumericWritable causes “ControlPoint.out set explicitly” warnings

Tridium Niagara
1

When running a custom ProgramObject (for GL36 VAV Box Request Counter), Niagara logs repeated warnings like:

WARNING [08:02:56][control] ControlPoint.out set explicitly: control:NumericWritable: /GL36_VAV_AHU/VAV_Box_5/VavCoolRequests
java.lang.Exception
...

The ProgramObject writes to StatusNumeric outputs, which are linked to NumericWritable points. Everything functions correctly, but these warnings appear every cycle.

Expected Behavior:
ProgramObject output updates to linked NumericWritable points should propagate cleanly without verbose control warnings if this is normal/expected behavior.

Actual Behavior:
Niagara logs a full stack trace every time the ProgramObject sets a linked NumericWritable, cluttering logs even though logic executes properly.

Question:
Is this normal Niagara behavior when linking ProgramObject StatusNumeric outputs to control:NumericWritable points? Or is there a cleaner way to output values without triggering these warnings (e.g., using intermediary StatusNumeric slots or suppressing “ControlPoint.out set explicitly” messages)?

2

Would need to see the whole code but I usually don’t see logs like that unless you’ve put them in the program object.

3

In modules you can use @suppresswarnings but I don’t know if that works in a module. But again, without seeing the code I can’t really answer. I’ve never had an issue writing a statusnumeric output to a numeric writable.

1 Like
4

Gosh somehow I accidently wired into an “out” to a NumericWriteable from a ProgObject … whoopsies nooby mistake

1 Like