Sending UDP commands to device - not received by device

[TomM]

As discussed in another post I use a Weeder Tech WTDIO 14 I/O RS232 device to extend the number of inputs on my miniserver.  This is coupled to an IP -> RS232 adapter (USR-TCP232-24) to make the WTDIO IP enabled.  Communication over RS232 between the 2 devices is correct and working (from now on I'll just refer to this combo of devices as 'the device').  Data connection from the device to the miniserver is fine, when sensors are triggered, the miniserver reliably receives the data from the device and acts accordingly.

The problem I'm facing is sending UDP commands to the device from the miniserver, in that the device never seems to receive the commands the miniserver sends.  This is required to setup the device in the event of a power cut or other anomaly with the device.  I have a small program installed on my pc that was supplied with the IP->RS232 adapter and 2 way comms over UDP works fine.  I have replicated this with PacketSender on my PC too.  Essentially, a command is sent and the device responds with confirmation or an error - so even if the syntax of my command that i sent is not correct, it will still respond.

Using the miniserver monitor in Loxone config, I can see the stream is created correctly over UDP to the correct socket and the command is sent.  But the device never responds and I know for a fact the device has never received the command.  Loxone Support have assessed my config and say there is nothing wrong with it at all and the miniserver is sending the command correctly.

Has anyone any experience with sending commands via UDP and therefore any ideas on how to resolve this issue?  Any ideas on how to troubleshoot at all?

Thanks 

Tom

[Michael]

Hi Tom,

Perhaps you could inspect the packages, with something like WireShark, from the miniserver to the IP>RS232 device, and compare them to the config program for the device. Maybe this could give you an idea of what is amiss.

You would probably need a switch with port mirroring, or put the miniserver directly to eg. your laptop and then bridge the ethernet with wifi.

I haven't actually tried something like this, but it seems the next step is to compare the traffic, to get an idea of the differences.

Sincerely

Michael

[TomM]

Hi Michael,

Yep, wireshark is a good idea.  From experience I think the easiest way to do this is set up my PC as a proxy and then the miniserver gateway address is my computer.  I'll give it a crack at the weekend i think.

I'll report back any findings.

Tom