Large 'From' number, Out of Range Error - Agent-Agent

[nickamenda]

We have a DMG running with IoTConnector and Agent 1.3. We configured Agent-Agent connection in our 2.x Agent. It looks like our Agent is getting some bogus from query string.... Any suggestions on how to troubleshoot this?
Agent Adapter Target: /DMG_MORI_12280008713/sample?count=1000&from=366929686800&heartbeat=10000&interval=500

[wsobel]

What is the 1.3 agent current nextSequence?

It could be a header parsing issue or an upstream agent issue. Can you check the response doc from the upstream agent. Btw the image did not load.

[nickamenda]

The nextSequence on the 1.3 agent is 20090. Does the image load for you now? That is our 2.x Agent. I have attached a snippet of the 1.3 Agent

<MTConnectStreams xmlns:m="urn:mtconnect.org:MTConnectStreams:1.3"
    xmlns="urn:mtconnect.org:MTConnectStreams:1.3"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:mtconnect.org:MTConnectStreams:1.3 http://www.mtconnect.org/schemas/MTConnectStreams_1.3.xsd">
    <Header creationTime="2024-12-06T18:49:24Z" sender="DM208756B9B421" instanceId="1733490942" version="1.3.0.17" bufferSize="262144" nextSequence="20090" firstSequence="1" lastSequence="20089"/>
    <Streams>
        <DeviceStream name="DMG_MORI_x" uuid="001">
            <ComponentStream component="Device" name="DMG_MORI_x" componentId="DMG_MORI_x_0">
                <Events>
                    <AssetChanged dataItemId="DMG_MORI_x_0_asset_chg" timestamp="2024-12-06T13:15:42.834430Z" sequence="1" assetType="">UNAVAILABLE</AssetChanged>
                    <AssetRemoved dataItemId="DMG_MORI_x_0_asset_rem" timestamp="2024-12-06T13:15:42.834430Z" sequence="2" assetType="">UNAVAILABLE</AssetRemoved>
                    <EmergencyStop dataItemId="DMG_MORI_x_1" timestamp="2024-12-06T13:19:13.743362Z" name="estop" sequence="115">ARMED</EmergencyStop>
                    <Availability dataItemId="DMG_MORI_x_2" timestamp="2024-12-06T13:18:17.818864Z" name="avail" sequence="75">AVAILABLE</Availability>
                </Events>
                <Condition>

[wsobel]

I wonder if this is a version issue. I tested with a 2.0 agent. The 1.3 agent is ancient, around 10 years old. I need to set up a test and see if I can reproduce the issue.

[nickamenda]

Okay, let me know what you find! Thanks Will!

[MRIIOT]

Agreed 1.3 is ancient, yet I am surprised how many people and DMG, Cisco, etc use it.

[wsobel]

I'll need to look into this. The response documents haven't changed a lot since 1.3. There are extra attributes, but it should work.

[wsobel]

I'm going to see if I can reconstruct a 1.3 that matches the version you're running on Windows and try to reproduce the error.

Do you have the Device.xml and agent.cfg from the 1.3 machine (DMG Mori)?

[wsobel]

Also, please upload agent.log file with log level set to debug:

logger_config
{
    logging_level = debug
    output = file agent.log
}

[wsobel]

After reviewing the log output, I need to see the old DMG Device XML file to check if there aren't some errors that are causing this. The Events:AssetChanged:DOUBLE indicates that the original configuration had units for the asset changed event. This would be rather odd. I need to check of there are other issues that may be causing things to trip up the validation code in the new agent.