Is Log4OM V2 compatible with OmniRig V2?
Thanks,
Brad, N4PYI
Search found 38 matches
- 24 Apr 2020, 20:45
- Forum: General discussions
- Topic: OmniRig V2
- Replies: 2
- Views: 1980
- 24 Apr 2020, 00:11
- Forum: General discussions
- Topic: Frequency Display
- Replies: 6
- Views: 5138
Frequency Display
How do you get the second frequency display to come alive? Is this for SO2R or am I missing something? Using Flex 6300.
- 11 Feb 2020, 01:56
- Forum: General discussions
- Topic: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
- Replies: 5
- Views: 3167
Re: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
Terry,
I did go back and check the date on the manual that I used to set up WSJT-X and JT Alert the first time. It was dated in January. I downloaded the latest and did the configuration as instructed in that one and it works perfectly.
Thanks
I did go back and check the date on the manual that I used to set up WSJT-X and JT Alert the first time. It was dated in January. I downloaded the latest and did the configuration as instructed in that one and it works perfectly.
Thanks
- 10 Feb 2020, 15:04
- Forum: General discussions
- Topic: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
- Replies: 5
- Views: 3167
Re: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
And yes, it did work prior to my intergating FLDigi to the best of my knowledge. At least I only noticed it after I integrated FLDigi.
Thanks for your help and for Log4OM. I really like the software.
Thanks for your help and for Log4OM. I really like the software.
- 10 Feb 2020, 15:01
- Forum: General discussions
- Topic: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
- Replies: 5
- Views: 3167
Re: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
Terry, After running debug and looking at the logs I found that JT Alert was closing port 2241. I went back and reconfigured Log4OM and WSJT-X to send the callsign information and the logging information directly to Log4OM from WSJT-X and everything started working again. I am not sure why JT Alert ...
- 09 Feb 2020, 12:43
- Forum: General discussions
- Topic: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
- Replies: 5
- Views: 3167
Re: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
After posting this, I ran debug in Log4OMV2 and then saved the log. It looks like the searches after the QSO are putting the callsign in the country field. I have attached the log here. If you search the log for the callsign K1CP you will see that search worked. All others after that fail. Thanks Te...
- 09 Feb 2020, 12:29
- Forum: General discussions
- Topic: Callsign Lookup Breaks after WSJT-X or FLDigi QSO
- Replies: 5
- Views: 3167
Callsign Lookup Breaks after WSJT-X or FLDigi QSO
I am noticing since update to 2.3 that when I work a QSO using WSJT-X or FL Digi, when the callsign is populated into Log4OM V2 it breaks the call sign lookup. So, you don't get all the info from the lookup as it is not going out to QRZ etc to pull in the information. All lookups after the QSO fail....
- 01 Feb 2020, 15:57
- Forum: General discussions
- Topic: LOTW Sent & Received Date Fields
- Replies: 6
- Views: 3942
Re: LOTW Sent & Received Date Fields
Also to add to this post, would like to be able to do the same with ClubLog sent and received fields as well as sent and received date fields.
- 01 Feb 2020, 15:48
- Forum: General discussions
- Topic: LOTW Sent & Received Date Fields
- Replies: 6
- Views: 3942
LOTW Sent & Received Date Fields
Is there a way to add the LOTW sent date and received date fields to the Recent QSO's view? LOTW " sent" and "received" are available but not the corresponding date fields. These are available in the QSL Manager, but not in the Recent QSO's view. This was something that I found v...
- 31 Jan 2020, 00:08
- Forum: General discussions
- Topic: Log4OM V2 with Version 1
- Replies: 6
- Views: 3438
Re: Log4OM V2 with Version 1
Got it Doug.
Thanks
Thanks