Server/ Client Connection Issue

I’m still unable to connect to my server located in my garag with my client in my house. The server is connected to WiFi extender in garage, I don’t know if that makes a difference or not? I sent pictures of my logs already so I’m at loss what to do now? Any help would be appreciated…

Hi Terry,

It might, depending on how you set it up. If our responses are delayed, it is simply due to our lives (yes, we do have them!) and also our push to get version 1.5 out soon.

—E
de W6EL

El, I do realize you have a life outside Wfview. I appreciate you help so far and when you can look at the thread on my issues. I will just be more patient. Sorry! Wfview is a great program and is working fine on server……

Terry,

it is hard to trouble shoot issues this way with screenshots.
It’s also hard if we don’t first split the issue. We first need to
be sure that you have your server part working.

In other ways. where the rig is located you can connect the
client directly and have control over it? the sound control will
be direct the speaker of the rig in this case.

If so, we will check and see if your server setup works locally (!)
on the server side itself.

After that we’re going to find out the IP address of that server and use
it to configure the client.

(And we may need to continue with more steps).

I’m married so I don’t have a life. (ok, well I do, like we all do ;-))

Thanks for information, the server radio works on all functions except audio doesn’t go to radio when I hit transmit button. Radio goes into tx mode. The computer doesn’t have any programs other than Wfview. It’s a clean windows pro install .

The computer is connected with network cable to Wi-Fi extender located in garage.

I fixed the transmit audio on server, changed setting in radio! Still can’t connect with client?

Thanks….

Terry,

what I understand from you is that it works locally on the server, right? That’s a good sign.

Now, we need to see if you have set up the server part with username, password etc.
You need to know the ip address of the server it’s running on. You also need to know the UDP ports you have assigned the wfview server so that you have all information available.

Here for instance, I use (user pass are not real)

ip address 192.168.1.110
user TEST
pass WELCOME
control port 50001

and you need to be sure that the server has (for the time being) has its firewall disabled

If you now put these (your saved) details in the client and you have the rig on and the server running…
you should be able to conect to the server. Note that theh client also should not run software that
uses one of the UDP ports that are defined in the server part. I know that some remote control software
may use a default port like 50001 which also will leave you out of a working client.

If that happens or if you are not sure, you could change the three ports in the server side.

Ayways. Before it’s getting complicated…

write down user/pass, ip address and control port and see if the client connects. Attach the log here. Remember – no screenshots, just plain logging text

Roeland,
I am a novice when comin to computer issues. The radio and computer I have as my server is located in my garage and it works with client or server. It is configured as server. the laptop is connected to a Wi-Fi extender with a network cable. I’m not running any other software that would interfere with the default ports 50001,50002,50003.

My next problem is I don’t know how to have log files saved to a file? I can get the log file displayed on computer monitor in power cell but can’t figure out how to save as a text file. PS C:\Users\baugh> PS C:\Users\baugh> Get-Content $env:TEMP\wfview.log -Wait -Tail 30
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.007 INF default: setState 1
2022-09-11 13:59:39.045 INF default: setState 1
2022-09-11 13:59:39.045 INF default: setState 0
2022-09-11 13:59:39.045 INF default: setState 1
2022-09-11 13:59:39.061 INF system: Loading settings from “\HKEY_CURRENT_USER\Software\wfview\wfview”
2022-09-11 13:59:39.145 INF gui: Got Audio Output from Settings: "Speakers / Headphones (Realtek "
2022-09-11 13:59:39.145 INF gui: Got Audio Input from Settings: “Microphone (Realtek Audio)”
2022-09-11 13:59:39.477 INF gui: Got Server Audio Input: “Microphone (Realtek Audio)”
2022-09-11 13:59:39.477 INF gui: Got Server Audio Output: "Speakers / Headphones (Realtek "
2022-09-11 13:59:39.524 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2022-09-11 13:59:39.524 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2022-09-11 13:59:39.546 INF rig: creating instance of rigCommander()
2022-09-11 13:59:39.546 INF udp: Starting udpHandler user: “TCB” rx latency: 150 tx latency: 150 rx sample
rate: 48000 rx codec: 4 tx sample rate: 48000 tx codec: 4
2022-09-11 13:59:39.578 INF udp: UDP Stream bound to local port: 60369 remote port: 50001
2022-09-11 13:59:39.662 INF system: Received CommReady!!
2022-09-11 13:59:39.662 INF default: Setting rig state for wfmain
2022-09-11 13:59:47.861 INF rig: closing instance of rigCommander()
2022-09-11 13:59:47.861 INF udp: Closing UDP stream : “192.168.10.112” : 50001

Roeland,
Here is my server log;
C:\Users\WK4B> Get-Content $env:TEMP\wfview.log -Wait -Tail 30

2022-09-12 09:08:26.666 INF default: setState 1

2022-09-12 09:08:26.667 INF default: setState 0

2022-09-12 09:08:26.667 INF default: setState 1

2022-09-12 09:08:26.685 INF system: Loading settings from “[\HKEY_CURRENT_USER\Software\wfview\wfview](file://HKEY_CURRENT_USER/Software/wfview/wfview)”

2022-09-12 09:08:26.749 INF gui: Got Audio Output from Settings: “Speakers (USB Audio CODEC )”

2022-09-12 09:08:26.749 INF gui: Got Audio Input from Settings: “Microphone (USB Audio CODEC )”

2022-09-12 09:08:27.035 INF gui: Got Server Audio Input: “Microphone (USB Audio CODEC )”

2022-09-12 09:08:27.035 INF gui: Got Server Audio Output: “Microphone (USB Audio CODEC )”

2022-09-12 09:08:27.291 INF system: Cannot prepare WF view without rigCaps. Waiting on this.

2022-09-12 09:08:27.299 INF rig: creating instance of rigCommander()

2022-09-12 09:08:27.302 INF system: Serial Port found: “COM3” Manufacturer: “Silicon Laboratories” Product ID “Silicon Labs CP210x USB to UART Bridge” S/N “IC-7300_02030031”

2022-09-12 09:08:27.303 INF udp.server: Starting udp server

2022-09-12 09:08:27.303 INF audio: Audio Input device “Microphone (USB Audio CODEC )”

2022-09-12 09:08:27.303 INF audio: Audio Output device “Microphone (USB Audio CODEC )”

2022-09-12 09:08:27.319 INF udp.server: My IP Address: “192.168.10.104”

2022-09-12 09:08:27.319 INF udp.server: Server Binding Control to: 50001

2022-09-12 09:08:27.330 INF udp.server: Server Binding CIV to: 50002

2022-09-12 09:08:27.331 INF udp.server: Server Binding Audio to: 50003

2022-09-12 09:08:27.362 INF serial: Opened port: “COM3”

2022-09-12 09:08:27.419 INF system: Received CommReady!!

2022-09-12 09:08:27.419 INF system: Delay command interval timing: 75 ms

2022-09-12 09:08:27.419 INF system: Skipping automatic CIV, using user-supplied value of 148

2022-09-12 09:08:27.419 INF default: Setting rig state for wfmain

the log is in a file as stated in the command:

Get-Content $env:TEMP\wfview.log -Wait -Tail 30

you see TEMP\wfview.log

there – if you cannot find it you could start notepad or something and copy/paste it in it and save as a file too. (I’m not a windows guy, just thinking of how you could…)

Rolland,

Are the files I sent earlier that are texts nor ok?

such small logs are OK yes. If it starts to become pages and pages… we’ll object.

Roeland,

I’m sorry that I’m causing so much grief, I have tried to answer request from me the best way I know how. I’ve sent both log files in recent correspondence, I’ve replied that server is working fine connected to radio. I jus can’t get client to connect to server. Again i apologize for being a pest. Thanks Terry WK4B

Hi Terry.

No not at all, what Roeland means is pages and pages of logs pasted into a message make things difficult to read. Unfortunately what you actually posted doesn’t include the important information we need to diagnose the issue!

By far the best way to post logs is to drag the log file into the new message window (or attach it to the email if you post that way).

To find the log (called wfview.log) open an Explorer window (folder icon) and in the address box type %TEMP% followed by Enter.

You can then drag the file called wfview.log into the message creation window and it will be attached to the post.

73 Phil M0VSE

client Log
wfview.log (3.7 KB)

Hi Terry.

It looks to me like you have multiple networks configured on your machines? Currently wfview will only communicate on the primary network interface.

According to your logs, this is 192.168.1.206 on your client and 192.168.10.104 on your server? These are different networks so likely can’t talk to each other unless you have a router which routes packets from the 192.168.1.x network to the 192.168.10.x network?

However, the client appears to be trying to connect to 192.168.10.111 which is not the address that is being detected for the server anyway?

If you use DHCP (quite likely) then your machines will often get assigned different addresses each time they are booted up, the easiest way around this is to set a DHCP reservation which ensures the same address is assigned each time, but the process is different for every DHCP server (likely your Internet router) and is a bit beyond the scope of a forum dedicated to wfview support!

73 Phil M0VSE

Server Log File.
2022-09-14 09:51:58.227 INF system: “wfview version: 1.42 (Git:7145de1 on Sep 5 2022 at 03:01:23 by build@wfview.org)\nOperating System: Windows 10 Version 2009 (i386)\nBuild Qt Version 5.15.2. Current Qt Version: 5.15.2\n”

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:19.882 INF default: setState 1

2022-09-14 09:52:20.288 INF default: setState 1

2022-09-14 09:52:20.288 INF default: setState 0

2022-09-14 09:52:20.288 INF default: setState 1

2022-09-14 09:52:20.351 INF system: Loading settings from “[\HKEY_CURRENT_USER\Software\wfview\wfview](file://HKEY_CURRENT_USER/Software/wfview/wfview)”

Phil, I did have two networks on Office laptop one “Private and one Public” I think I have recofig two just the “Public”

Office Laptop Wfview Client
SSID: ATT5WWV7dw
Protocol: Wi-Fi 5 (802.11ac)
Security type: WPA2-Personal
Network band: 5 GHz
Network channel: 157
Link speed (Receive/Transmit): 144/866 (Mbps)
IPv6 address: 2600:1700:7b91:2920::12
2600:1700:7b91:2920:b025:3ed4:8edc:25c4
Link-local IPv6 address: fe80::b025:3ed4:8edc:25c4%8
IPv6 DNS servers: 2600:1700:7b91:2920::1
IPv4 address: 192.168.1.206
IPv4 DNS servers: 192.168.1.254
DNS suffix search list: attlocal.net
Manufacturer: Broadcom
Description: Dell Wireless 1820A 802.11ac
Driver version: 1.566.0.2
Physical address (MAC): CC-B0-DA-BA-5F-35

Garage Laptop Server
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : cflogin
Link-local IPv6 Address . . . . . : fe80::4d48:7171:3eed:8beb%16
IPv4 Address. . . . . . . . . . . : 192.168.10.103
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1