Issues with CAT (Cluster CW/CW-R) QSO manual entries (dates)

[TY2CD]

Log4OM Version 1.19.0.0
RIG ICOM IC-9100 (USB CAT and Audio)
Windows 8 PRO

1. When clicking in the main screen cluster window on a station in CW mode, the CAT interface always change the IC-9100 to CW-R (Reverse) instead of CW.

2. When adding manually i.e. older QSO's not software logged, the start of QSO date can be logged as a date other than the current date but when going to the update screen to log the end of QSO date the date is not tracking the changed start of QSO date but always showing the current date. Is there a way that the end of QSO date can track the start of QSO date if manually entered as a older date than the current date.

3.Is it possible to add an option to detach the global/grayline screen as to display on its own on another monitor?

Thank You, Log4OM is different to other LOG software in that it actually integrates into my DX activities without being a distraction. I have changed from many years of using HRD to Log4OM.

With TY I am usually at the receiving side of the pile-up frenzy, so I have some ideas for a DX-expedition option/configuration that could change the logging screen to make it easier to run pile-ups i.e. to log the TX and split RX frequencies.

73
Wynand
de TY2CD

[G4POP]

Log4OM Version 1.19.0.0
RIG ICOM IC-9100 (USB CAT and Audio)
Windows 8 PRO

1. When clicking in the main screen cluster window on a station in CW mode, the CAT interface always change the IC-9100 to CW-R (Reverse) instead of CW.

This is an error in the ini file, please confirm that you are using Omnirig and which rig ini and I will supply a modified rig.ini

2. When adding manually i.e. older QSO's not software logged, the start of QSO date can be logged as a date other than the current date but when going to the update screen to log the end of QSO date the date is not tracking the changed start of QSO date but always showing the current date. Is there a way that the end of QSO date can track the start of QSO date if manually entered as a older date than the current date.

The date shown in the edit window is not saved unless you check the box - Go look at the data recorded and you will see that the QSO end date is empty which signifies that the QSO ended on the same day as it started - See screen shot below

3.Is it possible to add an option to detach the global/grayline screen as to display on its own on another monitor?

Sorry but no

With TY I am usually at the receiving side of the pile-up frenzy, so I have some ideas for a DX-expedition option/configuration that could change the logging screen to make it easier to run pile-ups i.e. to log the TX and split RX frequencies.

Please let us have your ideas for consideration by the team

[TY2CD]

Thank you for the reply and pointers.

I have swopped the CW_U and CW_L listing (decimal code) in the IC_9100.adi file of OMNIRIG and now the correct change to CW instead of CW-R is taking place when clicked in the cluster.

I will make my suggestions for a DX-Expedition log option as soon as I applied some more thought to it. The aim would be to only have to enter the call and a different RST only if needed (usually default is 59 or 599) while the date, QSO time, frequency (including split RX) and Country is automatically entered. Minimum keyboard typing / mouse movement needed to log a valid contact. Possibly it could be part of a future listing under contests.

Once again thank you for a great package of coding and at the best price.

73

de TY2CD

[NN7D]

Terry, I have the same issue with OmniRig's IC-7600 ini file. I had to manually edit it to correct the CW-R CAT mode. They are reversed from what they should be.

Doug - W7DRM

[G4POP]

Doug
This has occurred with several Omnirig ini files which are written by collaborators of Omnirig, not by us

I believe that the originators are not CW operators and just conform to band upper and lower modes in their ignorance.

Nothing we can do about it apart from be aware of the issue and help the users when it occurs