Pete,

I should also mention that this future version of D-STAR Hot Spot will
only send slow speed (DPRS) data received from the attached RF
receiver to D-PRS Interface.  Slow speed data embedded in a DV stream
received from a connected gateway or reflector will NOT be sent out
the TCP port to D-PRS Interface.

I've added this functionality because mobile D-STAR Hot Spot users who
transmit DPRS data do not show up on the APRS-IS network, even when
Hot Spot is connected to a repeater with a G2 gateway running D-STAR
Monitor.  This is because data forwarded to DPlus from a connected
D-STAR Hot Spot is not passed to D-STAR Monitor.  Thus D-STAR Hot Spot
must have it's own means of passing DPRS data to the APRS-IS network,
rather then relying on the connected gateway.

Rather than build my own APRS-IS client inside of D-STAR Hot Spot, I
figured your D-PRS Interface software would fit the bill perfectly. 
Initial testing shows that the TCP connection between D-STAR Hot Spot
and D-PRS Interface works great!

Mark (KB9KHM)


--- In [email protected], "kb9khm" <kb9...@...> wrote:
>
> Pete,
> 
> It seems like if I specify a TCP Port for D-PRS Interface to connect
> to (I'm talking TCP "serial port" here - as in connecting to DVTool),
> that D-PRS Interface will only try once to connect to the TCP port
> when the application is first launched.
> 
> Is there anyway I can talk to you into a new version of DPRS-Interface
> that will retry the TCP "serial port" connection if the TCP server is
> not available, or if the connection is lost?  A retry of once per
> minute or so would be great.
> 
> I've added code to D-STAR Hot Spot to make a TCP server available that
> will stream out the slow speed (DPRS) data to your D-PRS Interface
> application.  My concern arises in a situation where D-STAR Hot Spot
> and D-PRS Interface are launched automatically on Windows boot-up.  If
> D-PRS Interface happens to launch before D-STAR Hot Spot, and Hot
> Spot's TCP server is not ready yet, that D-PRS will never make a
> connection.  A TCP connect retry from D-PRS Interface would cure this
> issue.
> 
> Thanks!
> 
> Mark (KB9KHM)


Reply via email to