Log4OM

Hi,
I've been using Log4OM for a few weeks now and decided I would try to connect the rig to the computer.
I'm using "Hamlib" + Log4OM v1.18.0.0 + Win7.

Using the Hamlib program by itself I can use commands such as rigctl + PARAM and everything works well and gets data from the rig (a Yaesu FT767GX).
BUT log4OM won't seem to recognize the Hamlib software.
I have set the PATH parameter to the hamlib \bin directory.
The indicators for "CAT status" and "HRDlog on air" flash green briefly but nothing happens on the rig and the band/mode info in Log4OM don't change.
I have NOT installed the Hamlib software in the default directory - is this the problem?
I HAVE set the rig type, COM port, speed, stop bits correctly.

Anyone know what I should do to make this all work?

UPDATE....The rigctl command works from my newly downloaded version of Hamlib but NOT with the Log4OM's default installation with produces an error message "Unable to open COM24".
Do I need to update the original "Hamlib" files that Log4OM installed?


Best regards, Peter, G3ZPB, GB1BM.

You should not have any other instances of Hamlib running or there will be a conflict

Have you tried Omnirig, it's much simpler and less prone to issues?

Log4OM is provided with a copy of hamlib, and will start RIGCTLD.EXE network daemon.
No other instances or cat software should be active our they will conflict with hamlib.
You can run rigctld.EXE standalone, and connect to an instance of the Hamlib software already running

Daniele

Thank you both for your helpful replies.
I have now disabled the 2nd installation of Hamlib which has made a difference.
Also I have changed a few things and can now use COM4; that also helps.
But Hamlib won't stay connected - it sends a command to the rig and then seems to stop.
I'll try OmniRig and see how that goes - one problem is Omnirig doesn't support my FT767GX but I can probably write a file to do that.
CUL
Peter, G3ZPB.

Hi Peter,

have you tried the .ini for the FT-757 ?? Some of the old radios from one and the same manufacturer using the same code for CAT...

Hi Juergen,
Yes, I've tried the "757" code and it doesn't work.

Having reloaded a few things, I now have COMport 4 operational but still no joy.

Anyway, now back to Hamlib where I now have a more general question...
Does anyone have some more detailed instructions about making "Radio Connection" work?
Using "Hamlib", I can't make the "CAT Status" stay green.
I have set the rig model, port, Baud rate, stop bits, Force ICOM (no), data carrier, and RTS and DTR are blank.
Now what???
Do I click on "Load parameter" or "Save parameter"?
I presume I click on "Open" ? (at which point the CAT light on the rig flashes twice)
"Hamlib launched" goes green but "CAT status" stays red.
BUT I can open "rigctl" in a command window and can control the rig!!!! so I know the Hamlib system itself all works, it is just the way I am calling it from Log4OM that I have got wrong somewhere.

It should be pretty easy...
open the CAT screen in Log4OM, select correct parameters (AND COM PORT!!!) then press the connection button.
If you want to test it independently, when you have created all parameters a parameter string will appear on the screen in a textbox for your convenience.

Log4OM uses rigctlD.exe, not rigctl.exe, that is the TCP daemon.
If you increase the log level you can see a very fast scroll in the daemon screen (that is a DOS screen that opens minimized)

let me know

Peter
Omnirig?

Hi Both,
Thank you for your comments and help.
I am nearly there now
As a newcomer to computer logging and control, it would seem there is a bit more to it than intuition suggests!
In order to make my old Yaesu rig work, having selected the "Rig Model", I have had to set up the parameters (COM 4 and speed etc), then click on "Connect to Active Daemon" and then click on "Connect".
Now it works
However, after a period of time (perhaps 5 to 10 minutes) until I change band; then I get a message "RADIO doesn't answer to calls. Retry?" Clicking on "YES" and clicking on "Connect" does NOT make it all work.
I presume it must be a setting somewhere so I'll some other options.
Two other observations...
1> I have had no luck with Omnirig (no file for the FT767) and the FT757 file doesn't seem to work and I haven't written a specific file to try that.
2> another logging program (Winlog32) works perfectly in terms of reading data back from the FT767 for a long period of time with frequent band changes!!!!! (which tends to suggest my USB interface to the Rig and Driver Software is OK).
When I have finished and have got Log40M working OK with my rig, I'm quite prepared to write an extended section for the Log4OM-enu.pdf User Guide about Rig Control.
73s Peter.

Hi Peter, connect to an existing daemon means you are connecting to an instance of rigctld.exe already running.
This is typically the case of a remote rig (not connected to the current PC), where you have another PC connected via CAT.

You can connect to this remote daemon via network, and use the rig from remote.

In normal cases you should only use the "open connection" button placed in the bottom right part of the hamlib screen, after having set all parameters, without taking care of starting daemon separately.
Log4OM will start everything for you