Because Niagara proxy points have no inputs, you cannot link into them from local station logic (even if the remote source component is a writable type). If you need this “inter-station link control,” you must make another Niagara proxy point (in the remote station) that proxies whatever local source component you need for the link.

Consider a Niagara proxy point for a BooleanWritable that controls a fan. You wish to provide link control from a local And object, controlling at priority level 7. Figure 98 shows these objects.

In the example above, you cannot link into the Niagara proxy point “BFanBO_1.”

So in the other (remote) station, you must make a Niagara proxy point for the And object, then link its output to the source point for “BFanBO_1.” Figure 99 shows the wire sheet views with these objects.

In a typical Supervisor station (serving primarily Px views), usually not much direct link control is needed, so this seldom applies. In addition, the schedule import/export mechanism allows for central scheduling control using local (imported) schedule components.

However, if you are engineering applications between JACE stations that require link control, or do have a use case where the Supervisor needs to globally write a value into the link logic in JACE stations, please understand you must always use Niagara proxy points in this fashion.

Avoid linking to action slots on Niagara proxy points, as such links can be lost. For more details, see the Best practices for Niagara proxy points section Avoid links to proxy point actions.