DGLux does not directly expose the active state of a Mango schedule in the available implementation. Use the schedule event to toggle a virtual point, then bind the DGLux display to that point. This creates an explicit status signal without requiring direct schedule integration.
Active-schedule status path
The supported workaround separates schedule execution from visualization. The event writes the schedule state to a Mango virtual point, and DGLux reads that virtual point as the display source.
| Component | Function |
|---|---|
| Schedule event | Toggles the status value when the schedule changes state. |
| Virtual point | Stores the active or inactive state for external use. |
| DGLux display | Uses the virtual point to indicate schedule status. |
Configure the workaround
- Create or select a virtual point that will represent whether the schedule is active.
- Configure the schedule event to toggle that virtual point as the schedule enters or leaves its active state.
- Use the virtual point as the data source for the required DGLux status indicator.
The evidence does not specify a point identifier, value encoding, event configuration fields, or DGLux widget type. Select those details within the existing project conventions rather than assuming product-specific settings.
Verify the displayed state
Activate and deactivate the schedule while observing both the virtual point and the DGLux indicator. Confirm that the event changes the point in each direction and that DGLux follows the point. If the display does not change, isolate the fault by first checking the event-to-point update and then the point-to-DGLux binding.
FAQ
Can DGLux directly show whether a Mango schedule is active?
Direct schedule-state access is not available in the described implementation. Expose the state through a virtual point instead.
How do I display an active schedule in DGLux?
Configure the schedule event to toggle a virtual point, then bind the DGLux status display to that point.
How do I troubleshoot a DGLux schedule indicator that does not change?
First verify that the schedule event updates the virtual point. If it does, check whether the DGLux display is bound to that point and follows its state.