Log4OM

n5tm

Just added MSK144 mode to the rst.xml file... this one was also over written by update.

I've saved the entire Log4OM2 appdata folder to a cloud drive so I can easily get all this back after next update.

also trying to set permissions on those files so they will not be overwritten. We will see....

n5tm

So, I'm complaining... you bring out a new release, and I must yet again go fix the bandplan to add 630 and 2200 meters. Also I must add CAS-4A and CAS-4B back to the satellite list

Isn't there some way your update can avoid over writing these files???

Off to make the changes again...

n5tm

If working a "rover" station in a VHF contest you log the callsign/R the software is logging the station as being in Russian, not the US. Is there a work around?

n5tm

Ok, here's an observation and a work-around.
If you set the Omnirig poll = 100 and also time out = 100ms it works most of the time. You will get frequency change and mode change on the first double click.

So the work-around for the Digital mode:
1) Modify the K3.ini file in the Omnirig Rigs folder ...

n5tm

I've been using the antique Logger32 software which is written in VB6. It works very well with the K3, however I've been hoping to find a program written in this century.

I'm experiencing the same issue with clicking the spots. It will change the freq the first time, then the mode the second time ...

Search found 5 matches

Re: updates break what I change for 630m and satellite llist

updates break what I change for 630m and satellite llist

Rovers using callsign/R are logging as Russia #54

Re: Inconsistant mode selection from cluster spot

Re: Inconsistant mode selection from cluster spot