Edge computing and IIoT
Earlier articles
Troubleshooting
Why Ignition MQTT shows tagid None and what to key on
tagid is None because the MQTT payload never carries it: tag IDs are indexes inside the Ignition tag history provider, assigned and retired as tag configuration changes. Key the lake on a site-scoped tag path with the site identity in the MQTT namespace, and trace duplicate sqlth_data_ table sets through their driver IDs in sqlth_drv before stopping the extra writer.
Troubleshooting
MQTT connect fails when TCP works: diagnose the handshake
A successful raw TCP open to the broker port proves only routing and an open port; MQTT error 28 at Connect means the gateway ended the call with no usable session. Read the broker log during the attempt: no logged attempt means the gateway sent no MQTT data, a logged refusal means authentication or broker configuration, and an accept followed by an immediate close means a duplicate client identifier.
Explainer
Where the Ignition Edge tag historian writes its data
Ignition Edge has no configurable path for its local tag historian: the store and its store-and-forward buffer both write to the volume Ignition is installed on. For a 7-day history on fewer than 100 tags, add 3 to 5 GB of headroom to the main partition; an external SQL database connection is the only supported way to choose the volume.
How-to
Seed a large Ignition historian database for replication
Stage the backup database by closed partition, not in one 88 GB dump. The measured 4.5 GB in 40 minutes gives 6.75 GB/h, so the whole history is about 13 hours of dumping, but a weekly 2 GB partition is an 18-minute unit you can restore and verify before starting MySQL replication from that aligned state.
Troubleshooting
Query tag history from a remote tag provider
Yes: Tag Historian is one module with two jobs — storage and retrieval — so the gateway where system.tag.queryTagHistory runs must license it too. Install and license the module on the querying gateway; from 8.1 a read-only license covers a gateway that only consumes history. Prove the fix by matching row counts between the two gateways.
Explainer
What Ignition historian failover leaves behind in the second database
When a database connection fails over, Ignition keeps collecting: it builds the historian tables in the secondary schema and commits samples there, and nothing merges back when the connection returns. Recovery is a manual reconciliation bounded by the failover window and guarded by a tag-mapping check. The supported design is database redundancy behind one logical endpoint, with History Mode matched to database availability.
Explainer
Why two Ignition historian connections share one pruning boundary
No. Two database connections pointed at the same SQL Server database give the tag historian two logical routes into one shared table set, and pruning deletes whole partition tables, so the 3-month policy can remove data marked never prune. Put each retention policy in its own database on the same instance.
Troubleshooting
Stale historian tag browse tree entries after a restore
A historical tag browse tree lists the identities the edge historian has stored samples under, and a gateway restore replaces live tag configuration without touching that store. On a disposable development machine, stop the gateway, move the local .idb file out with a copy kept, and restart to clear them; Root Node Path trims the visible hierarchy without deleting data.
Troubleshooting
Why historian backfill runs slow from Tier 1 to Tier 2
The 30-hour test moved 14 hours of history for 10 tags, under half real time, so the 2014-era backfill utility is the bottleneck, not the data. Verify the source history and current replication first, then fill gaps with bounded requests or a manufacturer-approved archive block copy. The SQL database export moves configuration, not samples: drop it.
Troubleshooting
Rebirth fails after switching Sparkplug MQTT brokers
After a broker switch, Sparkplug telemetry arriving on the new connection proves only the inbound path. A rebirth request must leave through the client session that is actually connected on the enabled MQTT Server; when the module mishandles multiple server connections, the NCMD publish fails as client offline and no births return. Verify the replacement connection once, re-establish the birth baseline, and run a module build with the documented multi-server rebirth correction.
Comparison
Getting Wonderware Historian data into Ignition Edge for MQTT
Yes — Ignition Edge can publish this data as MQTT Sparkplug, but through two separate routes. Live values come from the existing DAServer acquisition layer behind a DA-to-UA gateway, because Edge's OPC client is UA-only. History and aggregates come from SQL queries against the Historian Runtime database, using its documented stored procedures.
Troubleshooting
Why Ignition tag historian tables are not created
In Ignition tag history, periodic mode still stores nothing until the tag value changes once and fires the initial store. A connection that reads Valid and a login with full write rights are never exercised before that first store, so a static tag keeps zero rows even at a one-second sample rate. Force one controlled value change, count the rows, and only then look at provider or database permissions.