I am using a SBL2e-100IR module.
I have the module working. It is receiving serial data and transmitting UDP packets when the “Connect/send to this address” is configured as a specific IP address on my network: 192.168.0.39. The “Learn UDP reply address” is disabled.
But what I need to do is transmit the UDP packets as broadcasts, either 192.168.0.255 or 255.255.255.255.
When the “Connect/send to this address” is changed to either of these IP (and the NetBurner module power-cycled after saving the setting), no UDP datagrams are subsequently transmitted.
Can the Serial-to-Ethernet software transmit a broadcast IP address with UDP?
Question about Serial-to-Ethernet UDP broadcast
-
- Posts: 2
- Joined: Fri Jan 23, 2015 3:49 pm
Re: Question about Serial-to-Ethernet UDP broadcast
How are you determining they are not being sent? Can you do a wireshark capture and see if the packets show up?
-
- Posts: 2
- Joined: Fri Jan 23, 2015 3:49 pm
Re: Question about Serial-to-Ethernet UDP broadcast
Thanks for the quick reply.
Yes, I have a network monitor and can observe the UDP packets. I have set the “Connect/send to this address” to several different but specific (non-broadcast) IP addresses and can see the UDP datagrams being transmitted to any of those IP. But when the address is changed to the local network broadcast IP of 192.168.0.255 there are no UDP datagrams being transmitted. Same for 255.255.255.255.
Yes, I have a network monitor and can observe the UDP packets. I have set the “Connect/send to this address” to several different but specific (non-broadcast) IP addresses and can see the UDP datagrams being transmitted to any of those IP. But when the address is changed to the local network broadcast IP of 192.168.0.255 there are no UDP datagrams being transmitted. Same for 255.255.255.255.
Re: Question about Serial-to-Ethernet UDP broadcast
This was an issue with SBL2E factory app/library code.
It has been corrected.
I'm putting this note here to tell anyone that has a similar issue to contact support and get a new code image.
Paul
It has been corrected.
I'm putting this note here to tell anyone that has a similar issue to contact support and get a new code image.
Paul