I just downloaded ver 3.0.22 of sdr console. My first attempt to use SDR Console. Started SDR console and it operates for around 30 seconds and stops. I know I'm missing something on my end, I have the 8000DLE selected I stop the SDR console and restart and the same thing happens. Any help would be appreciated. Thanks.
John N2XD
8000dle and sdr console ver 3.0.022
Re: 8000dle and sdr console ver 3.0.022
Hi John, do you have updated the 8k with Protocol 2? SDRC doesn't work with Prot.1.
If you have P2 than it's proberbly a bad network connection or your router is to slow. P2 needs a 1Gb connection.
If you have P2 than it's proberbly a bad network connection or your router is to slow. P2 needs a 1Gb connection.
73 PD3LK Leon
- Tony EI7BMB
- Posts: 653
- Joined: Sun Apr 09, 2017 2:31 pm
- Location: Dublin
- Contact:
Re: 8000dle and sdr console ver 3.0.022
I had this problem and it turned out to be the firewall . https://www.sdr-radio.com/ANAN-Apache-Labs
Re: 8000dle and sdr console ver 3.0.022
Thanks for the suggestions. I am running the Ver 2 of the firmware as I am running the latest ver of Thetis and running on the same same router connection. I did check the firewall and all is fine there. I will have to keep looking.
John
John
Re: 8000dle and sdr console ver 3.0.022
Hi John,
I'm not sure how closely you looked at the firewall but Tony is correct that this is an acknowledged issue with the Windows firewall making duplicate rules that will block the "ack" confirmation handshake with SDR Console shortly after the program is started. When I encountered this problem with SDR Console I found a rule that was blocking TCP and UDP communication and set the rule to "Allow" and thought that was the end of it. Well... that didn't fix it because as it turns out, the firewall had made numerous duplicate rules blocking the connection for SDR Console. I cleaned all the "Not Allow" rules out (there were more than a dozen of them) and before starting SDR Console again I created an allow rule for TCP/UDP to allow communication for SDR Console. That seems to have ended the problem for me. At any rate, you might want to take a second look at all the rules that are up and down the list in the firewall, you may find that the firewall has been busy creating them without displaying a prompt to ask you.
73, Rob W1AEX
I'm not sure how closely you looked at the firewall but Tony is correct that this is an acknowledged issue with the Windows firewall making duplicate rules that will block the "ack" confirmation handshake with SDR Console shortly after the program is started. When I encountered this problem with SDR Console I found a rule that was blocking TCP and UDP communication and set the rule to "Allow" and thought that was the end of it. Well... that didn't fix it because as it turns out, the firewall had made numerous duplicate rules blocking the connection for SDR Console. I cleaned all the "Not Allow" rules out (there were more than a dozen of them) and before starting SDR Console again I created an allow rule for TCP/UDP to allow communication for SDR Console. That seems to have ended the problem for me. At any rate, you might want to take a second look at all the rules that are up and down the list in the firewall, you may find that the firewall has been busy creating them without displaying a prompt to ask you.
73, Rob W1AEX
"One thing I am certain of is that there is too much certainty in the world."
Re: 8000dle and sdr console ver 3.0.022
Hi Rob,
I will check this again. This might be beyond my pay grade. However it should be an adventure. Thanks.
John N2XD
I will check this again. This might be beyond my pay grade. However it should be an adventure. Thanks.
John N2XD