Need help to configure Local Network with IC9700

[f1ssf]

Morning alls,

I try to use TCPIP port to control LOG40 with IC9700.

TCI is configured by : 192.168.1.10 : 50001
IC9700 IP: 192.168.1.3
UDP control port:50001
UDP serial port : 50002
UDP audio port : 50003
Network control is ON
My local gateway (box): 192.168.1.254
Subnet mask: 255.255.255.0

I can ping my IC9700, no problem, but impossible for LOG40 to connect it.
I have try with TCI directly, and via Hamlib networt, it is same. (for hamlib, port 50001 is not accepted, I have try 36000)
Peharps ports problems ?
Can you help me please ?

73 Franck F1SSF

TCI direct.png (23.35 KiB) Viewed 2656 times

hamlib connect.png (58.9 KiB) Viewed 2656 times

[G4POP]

Think your confusing the Sunsdr TCI control with a TCP connection - Not the same thing

[f1ssf]

Hi Terry,
Ha OK for me it TCI= TCPIP, I thank it was the same thing. In French doc only tested with Omniring, I don't have thius information.
Also, I have installed Hamlib (4.5.5), configured 4532 port in my 9700, because 50001 defaut port is not accepted by Log40.
Same problem, no TCPIP communication. The CAT lamp flash only few seconds.
73 Franck

IC9700- TCP.png (66.43 KiB) Viewed 2626 times

icon CAT.png (48.14 KiB) Viewed 2626 times

[G4POP]

Two UDP ports cannot be the same

I believe we already us 50001 for TCI and the SunSDR because that's the default so it's in use

Therefore Hamlib can't use it

Try changing the TCI port to 40001 even though you won't use TCI because that will release the port 50001 for Hmlib to use.

Better still use the more reliable and simpler Omnirig CAT control but be sure to install the genuine Icom USB drivers first

[f1ssf]

that will release the port 50001 for Hmlib to use.

I have tryed, but TCP Radio in Hamlib do not accept my defaut port 50001, max 36000.
I have input 36000 in IC9700, same, no connexion.

Yes Omniring run very well, but that's shame to use it , when you have possibility to use LAN port.

I have tring the communication over LAN with WFVIEW icom software it is perfect.

I continue my investigations with LOG40, but I think the problem it refused IP50001 in hamlib, why ????
73 franck

[f1ssf]

Morning,
I turn around
I redid a lot of tests using the same port parameters that work under WFView.
However, I see new things, if I open the menu CONNECT / Interface CAT I can force communication with Hamlib, and in this case, the CAT is now permanently connected, but still OFFLine in the display.
If you have an idea, I think the solution is not far...
THANKS
franck

Hamlib connex2.png (232.55 KiB) Viewed 2581 times

[f1ssf]

Hello

I try to find difference between LOG40 (not running over local network) and WFVIEW (running very well) and I think I have found.
In WFview, I have decalred a network user in my radio IC9700 (ID and password) and I have full connexion over local network..
If I remove ID and password on radio or on WFView, I havn't connexion. (attached WFview functionnal config)

So I wonder, there may be somewhere in Log40 an ID and password for radio access? Could the connection be simply refused?

73 Franck

WSFview.png (45.3 KiB) Viewed 2578 times

[w7btm]

I'm also struggling with making reliable connections to my Icom 7610 from a variety of utilities:

• WFView
  Log4OM
  CatSync
  Grid Tracker
  Wsjtx

I am extremely frustrated by how difficult it is to establish reliable connections using either USB or Ethernet. As a new ham (February 2023) I'm stunned how far behind the ham radio hardware and software manufacturers are. USB seems to be the goto default, but the hardware is not "Plug and Play" compatible which means we must use all kinds of tools to share the USB serial ports. And Windows also gets in the way. And even with a radio like the 7610 that has an Ethernet port, support is minimal or non-existent other than a small number of programs.

Like you, I did get WFView to work via ethernet and yes, it requires the user name and password of the user defined in the radio. But Hamlib in Log4OM does not have an option to configure a user and password which is why Im sure those connections are being rejected.

So I'm left trying to make USB work simultaneously with Log4M and several other utilities.

I'm hoping that the current generation of hardware and software is the last before we have truly uniform compatibility with Ethernet enabled hardware.

Anyway, my rant is over, and now I'm gong back to figure out how to get all this to work on USB.....

[f1ssf]

Hello,
Yes it is extremely frustated, I confirm.It feels like we're still in the 80s.
Afterwards I think it's a question of software, because the ICOM have the LAN connection function, and run very well on WFView.
The commanders are not the developers , maybe that will come one day.
73'S