[hpsdr] Command delays with Hermes on dedicated PC ethernet port

[Ken N9VV (Win-8/64)]

Hi Ron,John,
I have a Dell with the Motherboard NIC (Gigabit) and have added a USB3 
--> Gigabit LAN adapter (has an RJ45 socket for a LAN cable) as my 
second net interface. They both work very well at the rated speeds 
(Gigabit) now that I changed the "METRIC" value.

I found that in my circumstance, the Windoze operating system would 
schedule communications on the LAN's at different priorities.

I think it was Phil VK6PH who suggested that I try to increase the 
"METRIC" value shown in the ADVANCED settings for the USB3 to Gigabit 
adapter. I changed it from the "Automatic" value to "200" and that 
certainly cured my problem.

GL de Ken N9VV

On 9/21/2014 3:31 PM, Ron McCurdy wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
> Hi John,
>
> Just unplug  the home network from the new card and plug it back into
> the old card.  Then, you'll have the new card to speed up the processing
> between your computer and rig.
>
> Ron
> P.S.  I've recently done the very same thing with my Dell PC.  The 1GB
> ethernet card is connected to the Metis card of the transceiver.
> ----- Original Message ----- From: "John Ackermann N8UR" <jra at febo.com>
> To: <hpsdr at lists.openhpsdr.org>
> Sent: Sunday, September 21, 2014 1:38 PM
> Subject: [hpsdr] Command delays with Hermes on dedicated PC ethernet port
>
>
>> ***** High Performance Software Defined Radio Discussion List *****
>>
>> I put another NIC in my PowerSDR computer so that it could talk directly
>> to Hermes without going through the house network.
>>
>> The original NIC (on-board RealTek) is hooked to Hermes, while the new
>> Intel PRO/1000PT is connected to the house network.  I'm using PowerSDR
>> 3.2.19 and Hermes firmware v2.9 on a Windows 7 machine.
>>
>> I am using APIPA address assignment, and have the expected 10-20 second
>> startup delay.  Once the address negotiation is finished, data flows
>> smoothly with no issues.
>>
>> However, any command that requires communication with the radio, such as
>> changing bands or going in/out of CW mode, has a long delay before
>> successful completion -- long enough for the Windows "waiting" icon to
>> show up for a few seconds.  Commands performed entirely within PowerSDR
>> are not affected, only those that need to communicate with the radio.
>>
>> It is almost as if the APIPA negotiation is happening each time PowerSDR
>> needs to communicate with the radio.
>>
>> When I have have Hermes sitting on the house network with DHCP address
>> assignment, there are no delays, so this problem is related to the
>> dedicated connection.  And the data packets flow smoothly, so the basic
>> connectivity between the radio and the PC is there.
>>
>> I wonder if there is a Windows networking setting that I should be
>> tweaking to prevent this delay.  Any ideas?
>>
>> Thanks,
>>
>> John
>> _______________________________________________
>> HPSDR Discussion List
>> To post msg: hpsdr at openhpsdr.org
>> Subscription help:
>> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>> HPSDR web page: http://openhpsdr.org
>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>

 1411332457.0