You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
First of all, fantastic work on this project!
I have a bit of a question/issue with a particular machine on our network and I'm not sure where to start with debugging it.
The machine has an agent running already so I am using the http-adaptor client module to retrieve from it.
I am using this method on our other machines successfully (this is so I can aggregate all the data together and push to an MQTT broker using the mqtt-relay module).
All works well for all of our other machines just not this one Sodick Wire-EDM.
I can go to <machine_ip>/probe and see the device details (same for current and sample).
The logs in Docker show this: 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_26c483b645 : Client Started : http://<Sodick_IP>:50113 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_f0693379c2 : Client Started : http://<machine_2>:8082 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_bd26fc051a : Client Started : http://<machine_3>:8082 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_99c70cc2d7 : Client Started : http://<machine_4>:50013
I get a "DEBUG|modules.http-adapter|Client ID = adapter_http_99c70cc2d7 : MTConnectDevices Received" from all the machines (with different Client IDs) except the Sodick.
I don't get anything back from it at all.
I did notice on the Probe call in my browser that they have additional information in the namespace line, relating to some custom attributes they have added. <MTConnectDevices xmlns:m="urn:mtconnect.org:MTConnectDevices:1.3" xmlns="urn:mtconnect.org:MTConnectDevices:1.3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:x="urn:sodick.com:SodickDevices:1.3" xsi:schemaLocation="urn:sodick.com:SodickDevices:1.3 /schemas/sodick_devices_1.3.xsd">
I am wondering if this is causing problems?
Or am I missing anything?
The http-adaptor section in agent.config.yaml looks this: - http-adapter: address: <ip_address> port: 50113 deviceKey: Sodick_VN600Q interval: 5000 heartbeat: 10000 useSSL: false currentOnly: true useStreaming: false devices: Sodick_VN600Q: name: Sodick_VN600Q_1 uuid: Sodick_VN600Q_1 id: Sodick_VN600Q_1
Any help or advice would be greatly appreciated.
Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
First of all, fantastic work on this project!
I have a bit of a question/issue with a particular machine on our network and I'm not sure where to start with debugging it.
The machine has an agent running already so I am using the http-adaptor client module to retrieve from it.
I am using this method on our other machines successfully (this is so I can aggregate all the data together and push to an MQTT broker using the mqtt-relay module).
All works well for all of our other machines just not this one Sodick Wire-EDM.
I can go to <machine_ip>/probe and see the device details (same for current and sample).
The logs in Docker show this:
2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_26c483b645 : Client Started : http://<Sodick_IP>:50113 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_f0693379c2 : Client Started : http://<machine_2>:8082 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_bd26fc051a : Client Started : http://<machine_3>:8082 2024-10-10 22:20:15.3511|INFO|modules.http-adapter|Client ID = adapter_http_99c70cc2d7 : Client Started : http://<machine_4>:50013
I get a "DEBUG|modules.http-adapter|Client ID = adapter_http_99c70cc2d7 : MTConnectDevices Received" from all the machines (with different Client IDs) except the Sodick.
I don't get anything back from it at all.
I did notice on the Probe call in my browser that they have additional information in the namespace line, relating to some custom attributes they have added.
<MTConnectDevices xmlns:m="urn:mtconnect.org:MTConnectDevices:1.3" xmlns="urn:mtconnect.org:MTConnectDevices:1.3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:x="urn:sodick.com:SodickDevices:1.3" xsi:schemaLocation="urn:sodick.com:SodickDevices:1.3 /schemas/sodick_devices_1.3.xsd">
I am wondering if this is causing problems?
Or am I missing anything?
The http-adaptor section in agent.config.yaml looks this:
- http-adapter: address: <ip_address> port: 50113 deviceKey: Sodick_VN600Q interval: 5000 heartbeat: 10000 useSSL: false currentOnly: true useStreaming: false devices: Sodick_VN600Q: name: Sodick_VN600Q_1 uuid: Sodick_VN600Q_1 id: Sodick_VN600Q_1
Any help or advice would be greatly appreciated.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions