Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Publisher Data Point Not Publishing
-
One of the data points is not publishing. I don't know to how many this is happening but if we can figure this one out, I know how to rectify the rest:
This is coming from a ModbusRTU source into a MangoES, which is published to an Enterprise Mango install
I cannot seem to be able to post images on here due to Imgur limits, but here's what I confirmed.
-
MangoES is pulling data via Modbus
-
MangoES has the data in the Publisher
-
MangoEnterprise is not receiving this data point
Many other data points are being sent correctly.
I tried to REMOVE, SAVE and then ADD the data point again, and it did not resolve the situation.
-
-
Hello @mihairosu, Single data point not publishing from MangoES to MangoEnterprise, steps to try:
If other points on the same publisher are working but one specific point is not arriving on the Enterprise side, the most common cause is an XID mismatch introduced when the point was removed and re-added to the publisher. Work through these steps in order:
On MangoES:
- Go to Publishers and open the publisher sending to MangoEnterprise
- Find the entry for the affected data point and note its Published Point XID (this is separate from the data point XID, it typically looks like PP_xxxxxxxx)
- Confirm the data point itself is healthy: add it to a Watch List and verify it is receiving fresh values from the Modbus source
- Confirm the data point's Logging Type is not set to Do Not Log, some publisher configurations will not forward a point that has no logged values
On MangoEnterprise:
- Go to the Data Source that receives published data from MangoES
- Find the data point that is supposed to receive this value and open its configuration
- Look at the Point Locator, it will contain the Published Point XID it is listening for
- Compare this XID to the one you noted on MangoES, if they do not match, this is the cause
To fix:
- Update the Point Locator on the MangoEnterprise data point to match the current Published Point XID from MangoES
- Save the data point, then disable and re-enable the data source on MangoEnterprise to force it to reconnect
If the XIDs already match, also check:
- The data point and its data source are both enabled on MangoEnterprise
- The data type on the Enterprise point matches what MangoES is sending (e.g., both NUMERIC)
- The publisher on MangoES shows a healthy connection status with no errors
The remove/re-add step almost always generates a new Published Point XID on MangoES while the Enterprise side still holds the old one, updating the Point Locator on Enterprise is usually all that is needed
