Connectivity - Remote to Server

1

Server: Raspberry Pi - Bullseye
wfview: v2.03
Remote: Windows 10 Pro
wfview: v2.03

Radio: IC7300 - USB

Used to have connection from remote to server and things worked fine - a hiccup occurred with the audio, and in an attempt to fix it, upgraded both server and remote to wfview v2.03
Server IP address is unchanged. Port settings are correct. Can connect to Server using Remote Desktop and can control radio from wfview.
Log files : Remote: https://termbin.com/tbzi Server: https://termbin.com/eeek

Probably something easy that I am overlooking.

TIA
Michael - KG5UMH

2

Michael,

What is the issue with the setup? Tell us what isn’t working.

Thanks for the log files and other details. We will help figure it out.

—E
de W6EL

3

Sorry Elliott, cannot connect the remote to the server. Have rebooted both remote and server computers and power cycled the radio.

KG5UMH
Michael

4

Please verify that you DO NOT have the following items checked in your Client-side settings:

  1. Manual Radio CI-V Address
  2. Use CI-V address as Model ID too

Please verify that, on the Icom IC-7300, you DO have CI-V Transceive ENABLED.

Thanks,

–E
de W6EL

5

Elliott,

Manual Radio CI-V Address - NOT CHECKED
Use CI-V address as Model ID - NOT CHECKED

Since this was working a week or so ago, the CI-V Transceive must be enabled. I have not been to the Server location for two months - don’t think it would change.

Port forwarding is setup on the Server end to route the ports to the Raspberry Pi. Again that has been functional within the last week.

Thanks

Michael

6

I believe you are connecting, but the radio is not seen.

Double-check CI-V Transceive. Some legacy software turn this feature off, which is quite annoying.

–E
de W6EL

7

Ok, I will get some one to go to the server location and check that. Thanks Elliott

KG5UMH
Michael

8

Hi Michael!

You say you can control the radio with wfview. I guess you mean with wfview on the remote side over remote desktop? If do your radio must be correctly set up as Ci-V obviously work.

You can re-install an older version of Wfview if you give it another path when installing. I always do that when upgrading my remote to be sure I have a fallback if it does not work.

Then you can check if your remote connection still work with the previous versions of Wfview.

Good luck!

9

Hi!

I recently had this problem and I thought that my port forwarding settings were correct, which they were if you just looked at the port forwarding. However, the thing was that both my client’s PC and the Server PC actually changed their IPv4 adresses! After changning these in both of the router’s settings it worked for me!

10

Elliott… thanks for the response

Just to confirm I’m using an IC7610. I can confirm that “Manual Radio CI-V Address” and "Use CI-V address

as Model ID too" are not in use (not checked). I also checked the Radio menu and “CI-V Transceive” is turned ON.

Also in the WFView app under Radio Access I’m unsure about the use of User Name: I use my call sign W0SP and

in the radio Menu>SET>Network>Network User 1>Network User ID: W0SP and under "Network Radio

Name: IC7610". Also in the app I use for the Hostname: 192.168.0.10 and 50001 for the Control port.

When I try to Connect to Radio (with the radio ON or OFF) the bottom part the the main WFView page says

“Searching CI-V bus for connected radios”

Again thanks for your response…Fred

11

Hi Fred,

Good that the CI-V Transceive is ON, thank you for checking that one.

Can you please send us your log file, that will probably be the quickest way for us to see what is going on.

https://wfview.org/wfview-user-manual/how-to-send-a-logfile/

Thanks,

–E

12

Elliot… here’s the log file thanx… F

https://termbin.com/lofb

13

Hi Fred,

Please don’t “piggy-back” on somebody else’s topic, click the “New Topic” button at the top of the window.

Having said that, your radio isn’t responding to the connection request:

2025-02-09 13:45:45.944 INF udp: UDP Stream bound to local port: 48992  remote port: 50001
2025-02-09 13:46:46.285 WRN system: No response received to connection request
2025-02-09 13:46:46.285 INF udp: Closing UDP stream : "192.168.0.10" : 50001

Check that the server is actually enabled in your radio.

1 Like
14

Sorry Phil…
I’m new here. I thought I was responding to Elliot…

Fred Hollendorfer, W0SP
Wheat Ridge, CO