[WT-support] Controlling custom hardware?

[Olof Lundberg]

Markku,

I believe the Windows default is that ports can't be shared but there is -
if I remember correctly - a setting in the properties for .NET's UDPlistener
(possibly called 'exclusiveaddress' or similar and/or in the registry that
can change that. I am away from my stuff right now so can't check.

73 Olof G0CKV

From: support-bounces at f5mzn.org [mailto:support-bounces at f5mzn.org] On Behalf
Of Markku Oksanen
Sent: 19 March 2014 17:39
To: support at win-test.com; sm5ajv at qrq.se; Markku Oksanen [private]
Subject: Re: [WT-support] Controlling custom hardware?

 

All

 

First, thank you for the helpful suggestions and hints.

 

For the past few days I have been trying to make a MS .NET 4.0 UDP listener
work under VB2010, using the System.Net.Sockets namespace, which gives you
essentially a 5 line UDP listener.

Now, this works but ONLY one time because I don't manage to release the
resources (the port) in a proper manner and after countless hours of
searching, I can't find the answer either.  And still there is plenty of UDP
listener SW that works.  What to do?

 

So, just because it was simple, I was doing the testing on a single laptop
with WT running as the UDP source (broadcasting what WT broadcasts) and it t
turns out that when I move WT to an other machine on the same network, all
work great!!!  My code was OK, it was the way XP TCP/IP stack and ports that
caused the errors. Now I have the code I need to go ahead.

 

So,  I only need to write the LUA script that checks what radio is active
and if "*" was already used etc. and I should be in business to send my
custom GAB messages as Ingo suggested.

 

 

Markku

OH2RA/OG2A/WW1C

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20140319/50db49eb/attachment.html>