CAT is changing the bandwidth filter - why?

V2 error reports
Post Reply
4L4FN
New user
Posts: 1
Joined: 15 Nov 2024, 19:08

CAT is changing the bandwidth filter - why?

Post by 4L4FN »

have IC-756 PRO2 connected to Log4Om (latest version) on my PC.
CAT/Omnirig forks fine with one small exception:
- every time changing frequency/call sign to a new one from PC, it changes bandwidth filter FIL1 or FIL3 onto *FIL2* regardless of band/frequency position, kind of... some extra command is coming out from the logger.
So, after every click bandwidth filter is set to - FIL2

I doubt it should have any effect at all on a bandwidth filter "position", any!
Appreciate any help on this!

73!
User avatar
KI5IO
Moderator
Posts: 1935
Joined: 16 Aug 2015, 16:30
Location: Plano, TX

Re: CAT is changing the bandwidth filter - why?

Post by KI5IO »

Ed,

Make sure your IC-756 has the latest/official drivers installed on your PC from the ICOM folks.

Then (or maybe first ... your choice) you could possibly try different "ini" files that are available in the OmniRig 'rigini' zip file.

Clip below is from a zip file I d/l'd today from the OmniRig website (DX Atlas).

At least a couple of options to consider.

Take a look at the IC-756 Pro ini comments.txt file that is included with the 'rig.ini' zip file. There might be a hint there as well.

.
Attachments
icon-756.png
icon-756.png (5.29 KiB) Viewed 2043 times
73 - Nolan Kienitz - KI5IO
Plano, TX
sm0ikc
Novice Class
Posts: 3
Joined: 23 Nov 2024, 23:03

Re: CAT is changing the bandwidth filter - why?

Post by sm0ikc »

Hi guys,

I experience *exactly* the same issue with my IC7300.
I don´t have the skill to determine what messages are sent to the tranceiver via CAT but I am speculating that it includes a filter command, where it should not.

I am using the latest official USB serial driver from ICOMs website. The driver is from 2018.

This issue was quite frustrating since it made FT8 ops difficult by constantly swithing to FIL2 during USB-D, which by default is too narrow for FT8. My current workaround is that I modified FIL2 to 3.2kHz bandwith.

Edit: I don´t know if the assumed FIL2 CAT message comes from Log4OM2 or from wstjx. Maybe the latter?

Cheers / Tomas, SM0IKC
Post Reply