How-to
How Geo SCADA publishes values to MQTT
Short answer
Geo SCADA Expert publishes outbound values as control writes to MQTT Text driver points: the topic lives in each point's Control settings and the control value becomes the payload, while the point's readback is irrelevant. Sparkplug payloads need the Sparkplug B driver. Data arriving from Node-RED proves only the inbound path.
On this page
- What Geo SCADA can publish today
- How a control write becomes a publish
- Configure an outgoing MQTT Text point
- Worked example: one pump state from Geo SCADA to a Node-RED debug node
- When the write does not arrive
- Several signals: one topic per value, or one JSON message
- Deciding the route for your case
- Questions asked
Geo SCADA Expert publishes values to MQTT as control writes, not as a value scan. For a few signals in text or JSON form, the documented path is the MQTT Text driver: create points in that driver, configure each point's Control settings so a write goes to a topic, then have your logic or an operator action write the payload itself as the control value. What the point reads back does not matter. There is no general-purpose embedded publisher that streams arbitrary points on change; Sparkplug payloads belong to the dedicated Sparkplug B driver. And the Node-RED data already arriving in Geo SCADA proves only the inbound subscription path — the outbound publish needs its own points, its own permissions, and one controlled test.
What Geo SCADA can publish today #
The outbound capability splits on payload, and no general-purpose embedded publisher streams arbitrary database points as they change.
For a handful of text or JSON signals, the path is the MQTT Text driver: points whose Control settings write to topics, driven by control values that carry the data. This is the method Schneider Electric gives for exactly this case — a few signals in text or JSON form, ideal for a Node-RED consumer.
For Sparkplug payloads, the Sparkplug B driver in current releases is the route; the driver help presents it as MQTT publish/subscribe through a broker carrying real-time and historic data, and exporting Sparkplug B out of Geo SCADA to a historian covers it. For a payload format of your own, the basic MQTT driver code published for Geo SCADA Expert servers is documented as modifiable, so you can shape its data and control messages to a format of your choice.
How a control write becomes a publish #
The Geo SCADA MQTT driver guide defines an MQTT client as the party that sends PUBLISH and SUBSCRIBE messages to an online broker; clients never reach each other directly. Both Geo SCADA and Node-RED are clients, so a third device — or one of their hosts — runs the broker that every message crosses.
In the MQTT Text driver, publishing is a control action with three fixed parts. The destination topic lives in the point's Control settings. The control value supplied with the write becomes the payload delivered to that topic, byte for byte. And the write itself is the trigger: a value changing elsewhere in the database publishes nothing until a logic program, a method, or an operator action transfers it into the control.
Being connected to the broker proves transport and session, not permission. The broker must separately authorize that connection's identity to publish the topic you configured.
Configure an outgoing MQTT Text point #
- Create the point in the MQTT Text driver, on the connection that reaches your broker. If the inbound exchange already works, read that connection's endpoint — address, listener port (1883 unless configured otherwise), TLS, credentials — and match it, or verify the outgoing connection's own settings against the broker.
- Open the point's Control settings and enter the destination topic exactly as the consumer subscribes to it. MQTT topics are case-sensitive:
plant/Cooling/pump/stateandplant/cooling/pump/stateare different topics. - Confirm authorization in both directions on the broker: the Geo SCADA connection identity needs publish rights on that topic, and the receiving client needs subscribe rights. Grant only the topics the outbound path actually uses — plant data published under a permissive wildcard authorization is plant data leaked.
- Choose the payload representation before wiring anything: a plain text token for a scalar state, or the exact JSON string the receiving flow expects. The driver transmits the control value as-is; nothing converts an analog value into a JSON object for you.
- Issue the first write deliberately — from an operator action or a manual control — so you know the moment it happens. Check the server's control diagnostics: a rejected control points at permissions or configuration; no control action at all means your trigger never ran.
- When one write publishes cleanly, connect the real source logic to the same control path, one signal at a time, and record each mapping of source point, outgoing point, and topic.
Worked example: one pump state from Geo SCADA to a Node-RED debug node #
The case is the one this setup comes from: Geo SCADA and Node-RED on one broker, inbound data already flowing, one outbound signal to prove. Every string below is a test input chosen for this example; replace each with yours.
| Input | Test value | Where it comes from |
|---|---|---|
| Outgoing point | one point in the MQTT Text driver | step 1 above |
| Destination topic in Control settings | plant/cooling/pump/state | chosen for the test; the subscriber matches it |
| Control value | RUNNING | chosen payload, unlike any value already on the broker |
| Receiver | Node-RED mqtt in node on plant/cooling/pump/state, debug node attached | the environment in the question |
| Broker | the broker the working inbound exchange uses | the already-working inbound path |
The rule in words: the control value written to the point is the payload published, byte for byte, on the topic in that point's Control settings, at the moment of the write and at no other time.
The check, written out:
- Topic entered in Control settings:
plant/cooling/pump/state - Topic in the mqtt in node's subscription:
plant/cooling/pump/state— the two strings are identical, character by character. - Control value written:
RUNNING - Payload in the debug sidebar when the write completes:
RUNNING— the same seven characters: R, U, N, N, I, N, G.
Result: msg.payload shows RUNNING with topic plant/cooling/pump/state, appearing when the control executes and not before.
Decision: an exact match on both strings, arriving at the instant of the write, proves the outbound path end to end — point, connection, broker authorization, and subscription. A value that appears on deploy before any write is a retained message, not proof; no message at all goes to the table below. Once proven, wire the pump's real state logic to the same control so each state change writes RUNNING or STOPPED.
When the write does not arrive #
| What you observe | Where it stopped | What to do |
|---|---|---|
| No connection from the Geo SCADA server to the broker | Transport or session: address, port, TLS, credentials | Fix the connection; compare with the working inbound endpoint |
| Connected, but the broker refuses the publish | Topic authorization | Grant that connection identity publish rights on that topic |
| Publish accepted, nothing in Node-RED | Subscription filter, or a different broker | Match the topic exactly; confirm both clients use the same broker |
| Message arrives, the flow errors on it | Payload representation | Inspect the raw payload before any conversion; fix the string your logic writes |
| A value appears on deploy, before any write | A retained message from an earlier test | Clear it with a zero-length retained publish, then retest |
| No control action in the diagnostics | The trigger logic never ran | Fix the logic or operator action before touching the broker |
Work the rows in that order. Confirm the write was issued before blaming the broker, and confirm broker delivery before blaming the receiver's parsing.
Several signals: one topic per value, or one JSON message #
For a handful of scalars, give each outgoing point its own topic. Debugging in Node-RED is then one debug node per topic, and a wrong value is immediately a wrong mapping. The same one-topic-per-tag layout is the approach taken when publishing eWON MQTT tags as separate topics, and it is the right default here too.
When the consumer needs several values together — a dashboard card, a single JSON function — publish one JSON object on one topic instead: the writing logic builds the complete string and writes it as one control value, so each write carries the whole snapshot. Fewer messages, values that stay together, one permission to grant.
As a working rule: separate topics up to about a dozen independent scalars; a single JSON topic the moment the receiver treats the values as one record.
Do not confuse this with the MQTT JSON Schema A driver in the Geo SCADA help: its quick-start tutorial has the remote client publishing messages that Geo SCADA subscribes to, which is the inbound direction. Outbound JSON is just a text control value.
Deciding the route for your case #
- A few text or JSON signals to Node-RED or a similar consumer: MQTT Text driver control writes, configured as above.
- A Sparkplug consumer or a historian speaking Sparkplug: the Sparkplug B driver, documented for real-time and historic transfer over MQTT.
- A bespoke payload contract: the modifiable basic MQTT driver code.
- Hundreds of tags, store-and-forward buffering, or publishing from outside the SCADA server: an edge box doing the publishing, the approach in pushing ClearSCADA values to MQTT through an edge gateway.
Whichever route you take, prove it the same way: one deliberate write, one distinguishable payload, one exact match at the receiver — before any production logic depends on it.
Questions asked
Does Geo SCADA act as the MQTT broker in this setup?
No. The MQTT driver's own terminology describes a client as the party sending PUBLISH and SUBSCRIBE messages to an online broker; both Geo SCADA and Node-RED are clients. Some other device runs the broker. Confirm which one it is before comparing settings, because two clients connected to two different brokers will never exchange traffic.
How do I publish every change of an analog value?
Put the trigger in logic, not in the point. A logic program or method that executes on the source value's change formats the value and writes it as a control value to the outgoing point; each write publishes once. The point has no scan that republishes its current value, so a source value that changes without a write sends nothing at all.
Node-RED showed a value before I issued any write. Why?
That is a retained message. The broker stores the last payload published with the retained flag and resends it to every new subscriber, so it proves nothing about your outbound path. Publish a zero-length payload with the retained flag set to that same topic to clear it, redeploy the flow, and only then take your proof write.
Can I publish Sparkplug B payloads with the MQTT Text driver?
No. Sparkplug is more than a payload string: it defines a strict topic namespace, state management, and message types that a plain text publish cannot satisfy. The Sparkplug B driver in current Geo SCADA releases carries real-time and historic data over MQTT publish/subscribe through a broker, and that is the tool for a Sparkplug consumer.