Quality inspection data not syncing from SCADA to MES quality module after PLC firmware update

MES Honeywell MES
, , , , , , , ,
1

We’re experiencing a critical issue after our Allen-Bradley PLC firmware was upgraded from v21 to v24 last week. Quality inspection data from our automated testing stations is no longer syncing to the Honeywell MES quality management module.

The OPC UA connection shows as active in the SCADA interface, but the MES data collector logs indicate tag read failures. Our quality inspections are being recorded locally on the SCADA system but aren’t flowing into MES for compliance reporting.


OPC UA Read Error: BadNodeIdUnknown
Tag: ns=2;s=QualityStation_01.InspectionResult
Timestamp: 2025-03-14 14:32:18

I suspect the PLC firmware update changed the OPC UA namespace structure, but I’m not sure how to verify the current tag mappings or reconfigure the MES data collector. Has anyone dealt with similar tag mapping issues after a PLC firmware update? This is blocking our quality compliance workflow.

2

Check your quality data type mappings in the MES quality module configuration. The AB firmware v24 changed some default data types - what was previously Int16 might now be Int32, and string lengths may have changed.

Also verify the timestamp handling. The new firmware uses UTC timestamps by default, while v21 used local time. If your MES quality module expects local timestamps, you’ll need to add a timezone conversion in the data collector transformation rules.

3

Let me provide a comprehensive solution based on your situation. After PLC firmware updates that change OPC UA address space structure, you need to address three key areas: PLC firmware compatibility, OPC UA tag mapping, and MES data collector configuration.

Step 1: Update OPC UA Tag Mappings

Edit <MES_HOME>/config/datacollector/opcua_mappings.xml to reflect the new namespace and node structure:

<TagMapping>
  <Source>ns=3;s=QualityControl.Station_01.InspectionResult</Source>
  <Destination>QC_STATION_01_RESULT</Destination>
  <DataType>Int32</DataType>
</TagMapping>

Note the namespace change from ns=2 to ns=3 and the hierarchical path structure. Use UaExpert to verify exact node IDs for all your quality inspection points.

Step 2: Configure Data Type Compatibility

AB firmware v24 changed default data types. Update your data collector transformation rules in <MES_HOME>/config/datacollector/transformations.xml:

<Transform tag="QC_STATION_01_RESULT">
  <TypeConversion from="Int32" to="Int16"/>
  <TimestampConversion from="UTC" to="Local"/>
</Transform>

This handles the data type changes and timestamp format differences between firmware versions.

Step 3: Update MES Quality Module Data Source Mappings

In Honeywell MES:

  1. Navigate to Quality Management > Configuration > Data Sources
  2. Edit your SCADA data source connection
  3. Update the OPC UA server endpoint if the PLC IP or port changed
  4. Test the connection to verify the MES can reach the PLC

Then update inspection attribute mappings:

  1. Go to Quality Management > Inspection Templates
  2. For each template using SCADA data, select Data Source Mapping
  3. Remap each quality attribute to its new OPC UA tag path
  4. Verify data types match between PLC tags and MES quality attributes

Step 4: Configure Data Collector Service

Update polling and error handling in <MES_HOME>/config/datacollector/service.properties:


opcua.polling.interval=5000
opcua.reconnect.attempts=3
opcua.read.timeout=10000

Restart the MES Data Collector service:


service mes-datacollector restart

Step 5: Validation and Monitoring

Monitor the data collector logs at <MES_HOME>/logs/datacollector.log for successful tag reads. You should see entries like:


INFO: Tag read successful - ns=3;s=QualityControl.Station_01.InspectionResult = 1
INFO: Data mapped to MES attribute QC_STATION_01_RESULT

In the MES quality module, trigger a test inspection from your SCADA system and verify the data appears in the quality record within your configured polling interval.

Additional Considerations:

  • If you have multiple PLCs or quality stations, repeat the tag mapping updates for each
  • Document your new OPC UA tag structure for future reference
  • Consider creating a tag mapping validation script to catch mismatches after future firmware updates
  • Update your disaster recovery documentation with the new configuration

This systematic approach addresses the PLC firmware compatibility issues, corrects OPC UA tag mappings, and properly configures the MES data collector for the new tag structure. Your quality inspection data should now sync correctly from SCADA to MES.

4

One thing to watch out for - if your quality inspection workflow has custom attributes mapped to specific OPC tags, those may also need remapping. We had a similar issue where dimensional measurements were tied to specific tag positions in the old flat structure.

In our case, we had to update not just the data collector config but also the quality attribute definitions in the MES quality module. Navigate to Quality Management > Inspection Templates > Data Source Mapping to verify those connections are still valid after your tag structure changes.

5

I’ve seen this exact scenario with AB PLC firmware updates. The v24 firmware reorganized the OPC UA address space structure. Your tag namespace probably shifted from ns=2 to ns=3, and the node identifiers may have changed format.

First step: use an OPC UA client tool like UaExpert to browse your PLC’s current address space and document the new tag paths. Compare them against your MES data collector configuration to identify the mismatches.

6

You need to update the OPC UA tag mappings in the MES Data Collector configuration file, typically located at <MES_HOME>/config/datacollector/opcua_mappings.xml. Each quality inspection point needs its node ID corrected to match the new PLC address space structure.

After updating the XML, restart the MES Data Collector service. Monitor the collector logs to verify successful tag reads before the quality data starts flowing again. Also check if your data transformation rules need adjustment for the new hierarchical structure.