Enable, Dispatch and Sending
Four controls answer different questions. Keeping them separate is essential when a Layout contains both dynamic sources and instruments you intend to transmit.
| Control | What it governs |
|---|---|
| Generator Enable | The source's local operating lifecycle |
| Generator Dispatch | Whether eligible genuine samples are delivered to compatible bound instrument properties |
| Instrument Enable / interval | Whether this instrument is included in the authorized output schedule and how often |
| Enable Sending | Explicit global authorization for ordinary external instrument output, subject to mode, readiness and adapter policy |
Keep manual or captured values
- Stop external Sending while constructing the workspace.
- Disable unnecessary sources or turn Dispatch off before editing instrument values.
- Edit/restore the instrument snapshot and inspect widget, Property Editor and Object Tree.
- When ready for dynamic delivery, enable the source/Dispatch. Delivery resumes on a genuine eligible sample, not an invented initialization write.
With Dispatch off, generator activity does not replace your saved or manually edited values. Turning Dispatch on allows the next source update, including valid zero, to replace the corresponding value.
Start once, then stop deliberately
When the output is stopped and ready, Enable Sending is available. While Sending is active, Enable Sending is disabled and Stop is available. During connection or retry, read the status and use Stop to cancel rather than repeatedly clicking Start.
Stop Sending and F12 revoke ordinary output and pending bounded discovery/route requests. They do not promise to retract frames already accepted by an OS/adapter queue. Local simulation can continue after external output stops; disable the relevant source/movement mode when you also want local motion to stop.
Interpret disabled controls
- Viewer disables ordinary instrument Sending.
- No selected/ready supported output may leave Start disabled.
- Actisense Release is RX-only; Debug TX remains experimental.
- An enabled generator or checked instrument does not bypass these restrictions.
- Chartplotter requests use separate bounded authorization; neither authorization silently grants the other.
Saved Enable/Dispatch states are restored configuration. Loading, startup, route selection and mode changes never automatically authorize global Sending.
Illustrated controls
Reading guide: Compare the toolbar states: ready permits Start; active permits Stop; stopped after Stop permits Start only when the transport is ready.
Figure 36. Both authorization and transport readiness matter. This no-interface workspace remains stopped. Click to enlarge.
Figure 37. When the connection is ready and Sending is stopped, Enable Sending is available. Click to enlarge.
Figure 38. While Sending is active, use Stop Sending or F12 to stop external output. Click to enlarge.
Figure 39. Stop returns the sender to stopped state; F12 invokes the same safety lifecycle. Click to enlarge.
Related topics
Generating NMEA Data · Manual Vessel Movement · Autopilot and Route Following · Game Controller Mode · Engine and Transmission Simulation · Weather and Environmental Simulation · AIS Simulation · Windlass Simulation · Connection Troubleshooting · Route Overview · Engineering Units