Just a small follow up on this subject....
The solution, (Hamlib on log4OM on port 7820 and Slice master with the tcp cat port 7820), works but not always. Frequency changes are always picked up though...
Some notes:
- Always have a panadapter with TX enabled
- Start Slice Master before Log4OM ...
Search found 10 matches
- 15 Aug 2024, 16:52
- Forum: General discussions
- Topic: Syncing Callsign Entry between SmartSDR and Log4OM
- Replies: 6
- Views: 3580
- 15 Jul 2024, 14:34
- Forum: General discussions
- Topic: Syncing Callsign Entry between SmartSDR and Log4OM
- Replies: 6
- Views: 3580
Re: Syncing Callsign Entry between SmartSDR and Log4OM
Thanks! That actually works!F4BPO wrote: 14 Jul 2024, 23:09 I have this working on my flex 6600.
You need:
Hamlib on log4OM on port 7820
Slice master with the tcp cat port 7820
Then it will work

- 01 Jul 2024, 16:16
- Forum: General discussions
- Topic: Syncing Callsign Entry between SmartSDR and Log4OM
- Replies: 6
- Views: 3580
Re: Syncing Callsign Entry between SmartSDR and Log4OM
Thanks, Terry, for your response.
I reverted to using OmniRig instead of Slice Master to see if it would resolve the issue, but unfortunately, it didn't. If anyone has this feature working, please let me know. It's incredibly useful to have the callsign automatically looked up in Log4OM when ...
I reverted to using OmniRig instead of Slice Master to see if it would resolve the issue, but unfortunately, it didn't. If anyone has this feature working, please let me know. It's incredibly useful to have the callsign automatically looked up in Log4OM when ...
- 01 Jul 2024, 11:33
- Forum: General discussions
- Topic: Syncing Callsign Entry between SmartSDR and Log4OM
- Replies: 6
- Views: 3580
Syncing Callsign Entry between SmartSDR and Log4OM
Hello everyone!
When I select a spot in the bandmap of SmartSDR, Log4OM correctly updates its frequency. However, I'd like the callsign of that spot to automatically appear in the CALLSIGN entry box of Log4OM and trigger a lookup.
I had this feature working previously, but it seems to have stopped ...
When I select a spot in the bandmap of SmartSDR, Log4OM correctly updates its frequency. However, I'd like the callsign of that spot to automatically appear in the CALLSIGN entry box of Log4OM and trigger a lookup.
I had this feature working previously, but it seems to have stopped ...
- 17 Apr 2024, 08:42
- Forum: General discussions
- Topic: Log4OM Call Sign Lookup Behavior when changing frequency
- Replies: 11
- Views: 4990
Re: Log4OM Call Sign Lookup Behavior when changing frequency
I would speculate that the reason for this behavior lies in the setup where GridTracker forwards all UDP messages received from WSJT-X on port 2238, and Log4OM is configured to listen on the same port for these messages. When Log4OM receives a broadcast message, it likely triggers a call sign lookup ...
- 17 Apr 2024, 08:12
- Forum: General discussions
- Topic: Log4OM Call Sign Lookup Behavior when changing frequency
- Replies: 11
- Views: 4990
Re: Log4OM Call Sign Lookup Behavior when changing frequency
Are you running all programs using omnirig and omnirig to "run as an administrator""
Both Log4OM and WSJT-X are set to use OmniRig.
GridTracker is unaware of the rig as far as i know.
Omni-Rig is bundled with WSJT-X and will be started automatically by WSJT-X. I assume WSJT-X handles that it's ...
- 16 Apr 2024, 17:12
- Forum: General discussions
- Topic: Log4OM Call Sign Lookup Behavior when changing frequency
- Replies: 11
- Views: 4990
Re: Log4OM Call Sign Lookup Behavior when changing frequency
Thanks!
Both Log4OM and WSJT-X are set to use OmniRig.
WSJT-X -> Settings -> Reporting -> UDP Server : 127.0.0.1, UDP Port 2237, all boxes on the right side are checked.
GridTracker -> General -> Receive UDP Messages: Port 2237
GridTracker -> General -> Forward UDP Messages: Port 2378
GridTracker ...
Both Log4OM and WSJT-X are set to use OmniRig.
WSJT-X -> Settings -> Reporting -> UDP Server : 127.0.0.1, UDP Port 2237, all boxes on the right side are checked.
GridTracker -> General -> Receive UDP Messages: Port 2237
GridTracker -> General -> Forward UDP Messages: Port 2378
GridTracker ...
- 16 Apr 2024, 09:45
- Forum: General discussions
- Topic: Log4OM Call Sign Lookup Behavior when changing frequency
- Replies: 11
- Views: 4990
Re: Log4OM Call Sign Lookup Behavior when changing frequency
Here is a video clip showing how Log4OM seems to look up the call sign every time the VFO is turned.
https://e.pcloud.link/publink/show?code ... pVjJXgDJhV
https://e.pcloud.link/publink/show?code ... pVjJXgDJhV
- 12 Apr 2024, 15:37
- Forum: General discussions
- Topic: Log4OM Call Sign Lookup Behavior when changing frequency
- Replies: 11
- Views: 4990
Re: Log4OM Call Sign Lookup Behavior when changing frequency
Thanks Andre for your reply.
It seems that a frequency change triggers a data lookup in Log4OM as illustrated in the attached video. Every time I change the frequency using the VFO knob a new lookup seems to occur. Also, if running WSJT-X in split operatin "Fake It" (which alters the frequency) it ...
It seems that a frequency change triggers a data lookup in Log4OM as illustrated in the attached video. Every time I change the frequency using the VFO knob a new lookup seems to occur. Also, if running WSJT-X in split operatin "Fake It" (which alters the frequency) it ...
- 31 Jan 2024, 16:19
- Forum: General discussions
- Topic: Log4OM Call Sign Lookup Behavior when changing frequency
- Replies: 11
- Views: 4990
Log4OM Call Sign Lookup Behavior when changing frequency
Hello Log4OM community,
I've been using Log4OM alongside WSJT-X, and I've noticed a behavior that I'd like some assistance with.
Whenever WSJT-X transmits to a new call sign, Log4OM fetches information about the called station from QRZ.com, which is exactly as expected. However, I've observed that ...
I've been using Log4OM alongside WSJT-X, and I've noticed a behavior that I'd like some assistance with.
Whenever WSJT-X transmits to a new call sign, Log4OM fetches information about the called station from QRZ.com, which is exactly as expected. However, I've observed that ...