Log4OM

I think this has been brought up before, but I could not find the thread.

Since finding the new IC-7600v2.ini file and being able to see both VFO freq displays of my IC-7600 within Log4OM, I've noticed that in split operations, the TX freq is logged, as well as spotted, rather than the Rx freq, which in my book would be desired. Has this issue been addressed?

There might be those who desire the tx freq to be logged, but I can never see a need to spot the tx freq. Maybe a configuration setting to log either TX or RX freq in Split might be helpful - the default being set to log the RX freq? And always spot the RX freq.

Thanks!

Doug - W7DRM

Hi Doug, the actual CAT management from Omnirig is a bit "complex" because every rig reports things in a different way.
Some rigs with 2 VFO reports only a generic "frequency", while other rigs reports both without TX indication and so on.
I'm working on some optimizations, but i prefere to avoid saving anything without having the 100% confidence that the data is correct.

Anyway i'm on it.

IW3HMH wrote:Hi Doug, the actual CAT management from Omnirig is a bit "complex" because every rig reports things in a different way.
Some rigs with 2 VFO reports only a generic "frequency", while other rigs reports both without TX indication and so on.
I'm working on some optimizations, but i prefere to avoid saving anything without having the 100% confidence that the data is correct.

Anyway i'm on it.

Thanks Daniele!

I know what you mean about the complexity of it. I had to work through it to get the IC-7600.ini file to work with OmniRig. At least with Icom rigs which can reply the status of both VFO's, there is a generic freq (pmFreq), then there is a pmFreqA, and a pmFreqB. My guess is you are using the generic pmFreq for the VFO A Display, and the pmFreqB for VFO B display. Might need some logic that says if there is a pmFreqA and pmFreqB freq response, use them, else use pmFreq.

This would also help with another issue I have noticed with the dual display in Log4OM. When you use the Sub/Main button on my 7600 to change focus to VFOb, the Log4OM dual displays show correctly, but when you change the freq of VFOb both Freq Displays on Log4OM change, then when you stop tuning, the VFO A display returns to the correct freq. The same thing happens when you are in Split mode.

Another issue, not related directly, but dealing with OmniRig and the pmSplit method, when the 7600 is in Split mode, both RX and TX follow the TX freq, rather than RX being on VFO A and TX being on VFOb.

Thanks for checking this out!

Doug - W7DRM

Daniele, I use Log4OM with an Elecraft K3 tranceiver and have the same issue and request as W7DRM. When I am operating in Split mode, I normally have the DX frequency in VFO-A and I am in the pile-up transmitting on VFO-B. When I log the QSO, Log4OM records my transmit frequency. For my records and for spotting on the DX cluster, it is customary (and I desire) to log the DX freq, NOT my pile-up split tx freq. If you decide to address this issue, I would request that Log4OM log the VFO-A frequency, or better yet, perhaps a user configuration option that allows the Log4OM user to configure which VFO is recorded in the Log4OM log. (And spotted.) Although I am confident that almost all Log4OM users would normally want VFO-A as the default freq logged. Thank you for your time and consideration. Bob N2NS

Bob,
One thing to bear in mind is that all national and international radio regulation departments are only interested in if you were transmitting within the allocated bands and require the transmit frequency to be recorded!

This way in any dispute regarding interference or illegal out of band transmission you have the evidence to prove your case.

I do however agree that the frequency used for dx spotting should be the receive frequency

There are many other reasons for recording the transmit frequency and we have the ability to save both frequencies if the information is provided by the command structure of the radio and therefore Omnirig/Hamlib