GlobalFusedPose UDP Output
Node ID: globalFusedPoseUdpOutput · Role: Sink · Realtime config: no
Description
Sends GlobalFusedPose as a fixed 24-byte little-endian UDP packet: latitude, longitude, heading.
Inputs / Outputs
- Inputs:
GlobalFusedPose - Outputs: (none)
Config aliases
GlobalFusedPoseUdpOutput, globalFusedPoseUdpOutput, globalFusedPoseUdpSink
Properties
The following fields are exposed in the node’s Properties panel in the UI. Types map to UI widgets (e.g. string → text input, number → numeric, boolean → toggle, select → dropdown, json → JSON editor).
| Key | Label | Type | Default | Description / Notes |
|---|---|---|---|---|
host | Destination IP | string | 127.0.0.1 | — |
port | Destination Port | number | 5005 | — |
maxRateHz | Max Rate (Hz) | number | 100 | — |
Example node definition
A full node definition in config.json looks like the block below. Paste it under the sinks key of your config, keyed by the node’s instance name (any identifier; it doesn’t have to match the node ID).
{
"sinks": {
"globalFusedPoseUdpOutput": {
"inputEndpoints": [
"inproc://globalFusedPose_data"
],
"inputDataFilter": [
"GlobalFusedPose"
],
"settings": {
"host": "127.0.0.1",
"maxRateHz": 100,
"port": 5005
}
}
}
}
Field reference
| Field | Purpose |
|---|---|
inputEndpoints | List of upstream endpoints this node connects to (outEndpoint / dataEndpoint values from upstream nodes). |
inputDataFilter | Optional whitelist of data types. Messages whose type isn’t in the list are dropped at the subscriber. |
settings | All user-configurable fields — see the Properties table above. |
Connections can also be declared at the top-level
connectionsarray whensettings.explicitConnectionsistrue, as an alternative to fillinginputEndpointson each node.