install of 2.28.0.0 success except

[G4POP]

Is this symptom only confined to Yaesu radios and if so which particular models?

[N7QJP]

I can't say if it applies to other radios as the only radio I use is my Yaesu FTdx-10.

I can say that FT8 works properly while FT4 causes the blinking. Given that both FT8 and FT4 use the same mode in the radio (DATA-U), I want to think that it is not mode dependent on the radio itself....but that is just an assumption on my part.

An additional piece of information.....at the same time the signal fields are blinking, the Mode field on Log4OM switches back and forth between FT4 and FT8, in sync with the blinking of the signal fields. All of this occurs regardless of the Yaesu being in TX or RX.

I am using WSJT-X v2.6.1, GridTracker v1.23.0402, Log4OM v2.28.0.0, and Omni-Rig 1.20.

Thank you for your attention to this matter.
73....Stu N7QJP

[G4POP]

What happens if you run just Log4OM on its own

No data programs running

Tune to same frequency and select same modes on radio and in Log4OM?

[KI5IO]

Similar observations noted in this thread.

Seems to be 'rig related'. Some "work-a-rounds" noted by a couple OMs until a solution is found.

https://forum.log4om.com/viewtopic.php?t=8560&start=10

[G4POP]

What frequency are you operating FT4 on?

[N7QJP]

Hello Terry,
I shutdown and restarted the PC to make sure there were no residual apps running.

I started Log4OM. I manually switched the Yaesu to 17 meters (18.100 Mhz) and selected a radio mode of VFO A, DATA-U.

Turning my attention to Log4OM, it is showing FT8 in the Mode field. I did not select that.

When I try to select FT4 in the Mode field on Log4OM, it won't let me do it. The drop-down listbox appears, and as I move the mouse down the list to select one of the modes, it repositions my mouse back to FT8 and the S and R fields blink one time. If I try to select another mode in Log4OM, the same behavior continues to happen. I assume Log4OM is reading the Yaesu's mode via the CAT interface.

I then selected mode USB on the Yaesu, the Mode on Log4OM changed to USB as expected. I cannot select a different mode on the drop-down listbox on Log4OM. It simply defaults back to USB. This makes sense to me since the CAT interface is reporting USB to Log4OM.

I operate FT4 from 30 to 10 meters.

[G4POP]

Perhaps I should have been more specific, I needed to know what actual frequencies you operate FT4 on, not the bands.

Log4OM uses its bandpalns to derive the mode according to the frequency you are tuned to and includes specific frequencies for FT8 and FT4, look at the band plan in the config folder

C:\Users\YOUR USER NAME\AppData\Roaming\Log4OM2\bandplan

These frequencies are those demanded by the users and JT - See listed extract from your local bandplan below.

<Dxcc>291</Dxcc>
<SpecialFrequencies>
<string>1840000|FT8</string>
<string>3573000|FT8</string>
<string>5357000|FT8</string>
<string>7074000|FT8</string>
<string>10136000|FT8</string>
<string>14074000|FT8</string>
<string>18100000|FT8</string>
<string>21074000|FT8</string>
<string>24915000|FT8</string>
<string>28074000|FT8</string>
<string>50313000|FT8</string>
<string>3575000|FT4</string>
<string>7047500|FT4</string>
<string>10140000|FT4</string>
<string>14080000|FT4</string>
<string>18104000|FT4</string>
<string>21140000|FT4</string>
<string>24919000|FT4</string>
<string>28180000|FT4</string>
<string>50318000|FT4</string>
</SpecialFrequencies>

When Log4OM is sent one of those frequencies, because you or the JT program tuned to it, it does two things!

1. Changes logging mode to FT8 or FT4
2. Changes the RST format to the format for the selected mode like +05 or -21 for the JT modes

If the JT software sends Log4OM a mode FT4 but a frequency allocated to FT8 confusion reigns - e.g. your tuned to 21074000 but the JT software sends FT4 as the mode - "Hey man your giving me the wrong mode for the frequency your tuned to, give me a break"

When you tune away from the JT allocated frequencies listed in your band plan the normal mode and RST structure for that section of the band is reselected, e.g.Data, CW or Phone

If the frequency is not one of the FT spots listed above the mode and RST is derived from the normal section of the bandplan as shown below.

<BandPlanRange>
<Band>15m</Band>
<Start>21000</Start>
<End>21070</End>
<EmissionType>CW</EmissionType>
<ModulationType>USB</ModulationType>
</BandPlanRange>
<BandPlanRange>
<Band>15m</Band>
<Start>21070</Start>
<End>21200</End>
<EmissionType>DIGITAL</EmissionType>
<ModulationType>USB</ModulationType>
</BandPlanRange>
<BandPlanRange>
<Band>15m</Band>
<Start>21200</Start>
<End>21450</End>
<EmissionType>PHONE</EmissionType>
<ModulationType>USB</ModulationType>
</BandPlanRange>
<BandPlanRange>

Now perhaps you can see why not only the mode flickers but also the RST fields its because Log4OM is receiving conflicting information.

Just why this seems to be more prevelent on specific radios I can only assume to be related to that manufacturers CAT command structure because I cannot replicate this on any of my Icom, Elecraft or SDR radios and I dont have Yaesu or Kenwood radios to test.

One other thought occurs to me is that perhaps the graticular data for frequency is not fine enough so check what your tuning dial on the radio shows and if its just showing 100hz divisions change it to 1 hz

Example: If the radio displays 14.074.0 or 14.074.00 try changing the frequenct staps to display 14.074.000

[N7QJP]

Hello Terry,
I use the default FT4 frequencies as provided by WSTJ-X when selecting the FT4 mode. They show on the Yaesu's display as follows:

50.318.000
28.180.000
24.919.000
21.140.000
18.104.000
14.080.000
10.140.000
7.047.500
3.575.000

The tuning on my VFO is 10 Hz steps. I'd have to look in the manual to see if I can reduce that to 1 Hz.

I checked the ....\Log4OM\bandplan\bandplan_dxcc291.xml file for the FT4 frequencies and they agree with what you indicated in your last post and also with what I just posted above. In other words, the bandplan XML file and the FT4 frequencies coming from WSJT-X are in agreement with each other.

For what it is worth, I've been running Log4OM along with WSJT-X and GridTracker since early last summer. I stay current on the release of all three of these software apps. It has only been the last Log4OM release where this blinking issue started. Last week, I did a firmware update on the Yaesu FTdx-10. However, the blinking fields were occurring right after I installed Log4OM v2.28.0.0 (early June if memory serves me correctly) so I don't think the CAT command structure has changed here in the shack.

Is there anything else I can check and forward to you? I think I answered your questions from your last post.

Thank you very much for taking the time to look into this issue.

73,
Stu -- N7QJP

[G4POP]

Checking code and Lele has a Yaesu so we will get back to you soon

[G4POP]

See viewtopic.php?p=44768#p44768

What happens if you run Log4OM stand alone without any of your JT programs running just Log4OM, Omnirig and your radio connected. WSJT, JTALERT, Gridtracker etc all shut down