Replies: 11 comments 2 replies
|
Found it, and it isn't the same thing as your 6000 Hz issue report — that one was the width being re-sent on every QSY, and it's fixed. This is the width becoming wrong, which is a different path. Nexus sends the mode and a 3 kHz width together, so a rig that recalls a narrow DATA filter can't clip FT8. When a mode-set gets refused, it retries — and after ten straight refusals it stops naming a width and tells the rig "use your own default for this mode". On a Flex that default is wide, and that's your 6000. So the filter isn't being set to 6000 on purpose. It's the rig picking its own width because Nexus gave up asking for a specific one. Which means the thing I actually want to know: ten consecutive refusals is not a healthy CAT link. Something is rejecting the mode set over and over on your 6400. Are you going through Hamlib, or SmartSDR's own CAT? And does it happen on every band change or only some? Tracked now as #82 so it doesn't get lost in here. Leaving this open. 73 |
|
CONNECTING TO RADIO VIA SMARTSDR CAT. USING PORT 5002, VIA IP, NOT A COM
PORT.
where is this default 6000 hz in smart sdr, is it changable as not to be
default
. I have never seen thaton wsjt, n1mm or mixw4 or hrd, so never seen
before.
I Have not seen any error pop to say cat lost
Dave Garber
VE3WEJ / VE3IE
…On Fri, Aug 14, 2026 at 11:30 PM HamRadioTools ***@***.***> wrote:
Found it, and it isn't the same thing as your 6000 Hz issue report — that
one was the width being re-sent on every QSY, and it's fixed. This is the
width becoming wrong, which is a different path.
Nexus sends the mode and a 3 kHz width together, so a rig that recalls a
narrow DATA filter can't clip FT8. When a mode-set gets refused, it retries
— and after ten straight refusals it stops naming a width and tells the rig
"use your own default for this mode". On a Flex that default is wide, and
that's your 6000.
So the filter isn't being set to 6000 on purpose. It's the rig picking its
own width because Nexus gave up asking for a specific one.
Which means the thing I actually want to know: *ten consecutive refusals
is not a healthy CAT link.* Something is rejecting the mode set over and
over on your 6400. Are you going through Hamlib, or SmartSDR's own CAT? And
does it happen on every band change or only some?
Tracked now as #82 <#82> so it
doesn't get lost in here. Leaving this open. 73
—
Reply to this email directly, view it on GitHub
<#66?email_source=notifications&email_token=AT62B6TMDKU3MUSNJGPPAWL5J7KOTA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGI2DOOJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18024790>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT62B6WKSL7DXGE735WA6YD5J7KOTAVCNFSNUABJKJSXA33TNF2G64TZHMYTGMBUGU2TANJWGE5UI2LTMN2XG43JN5XDWMJQGYYDEOBWG2QXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AT62B6WCOGZKGLRPDPBJGMT5J7KOTA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGI2DOOJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/AT62B6U5J5CM4H2ICRSYES35J7KOTA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGI2DOOJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Which means the thing I actually want to know: *ten consecutive refusals is
not a healthy CAT link.* Something is rejecting the mode set over and over
on your 6400. Are you going through Hamlib, or SmartSDR's own CAT? And does
it happen on every band change or only some?
This morning I clicked on a call, with cat control working, the radio
qsy's, as it should to the tx mode, and the radio goes to 6k hz. no
delay. so where is it losing cat??
VE3WEJ / VE3IE
…On Sat, Aug 15, 2026 at 7:02 AM Dave ve3wej ***@***.***> wrote:
CONNECTING TO RADIO VIA SMARTSDR CAT. USING PORT 5002, VIA IP, NOT A COM
PORT.
where is this default 6000 hz in smart sdr, is it changable as not to be
default
. I have never seen thaton wsjt, n1mm or mixw4 or hrd, so never seen
before.
I Have not seen any error pop to say cat lost
Dave Garber
VE3WEJ / VE3IE
On Fri, Aug 14, 2026 at 11:30 PM HamRadioTools ***@***.***>
wrote:
> Found it, and it isn't the same thing as your 6000 Hz issue report — that
> one was the width being re-sent on every QSY, and it's fixed. This is the
> width becoming wrong, which is a different path.
>
> Nexus sends the mode and a 3 kHz width together, so a rig that recalls a
> narrow DATA filter can't clip FT8. When a mode-set gets refused, it retries
> — and after ten straight refusals it stops naming a width and tells the rig
> "use your own default for this mode". On a Flex that default is wide, and
> that's your 6000.
>
> So the filter isn't being set to 6000 on purpose. It's the rig picking
> its own width because Nexus gave up asking for a specific one.
>
> Which means the thing I actually want to know: *ten consecutive refusals
> is not a healthy CAT link.* Something is rejecting the mode set over and
> over on your 6400. Are you going through Hamlib, or SmartSDR's own CAT? And
> does it happen on every band change or only some?
>
> Tracked now as #82 <#82> so it
> doesn't get lost in here. Leaving this open. 73
>
> —
> Reply to this email directly, view it on GitHub
> <#66?email_source=notifications&email_token=AT62B6TMDKU3MUSNJGPPAWL5J7KOTA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGI2DOOJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18024790>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AT62B6WKSL7DXGE735WA6YD5J7KOTAVCNFSNUABJKJSXA33TNF2G64TZHMYTGMBUGU2TANJWGE5UI2LTMN2XG43JN5XDWMJQGYYDEOBWG2QXMAQ>
> .
> Triage notifications, keep track of coding agent tasks and review pull
> requests on the go with GitHub Mobile for iOS
> <https://github.com/notifications/mobile/ios/AT62B6WCOGZKGLRPDPBJGMT5J7KOTA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGI2DOOJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
> and Android
> <https://github.com/notifications/mobile/android/AT62B6U5J5CM4H2ICRSYES35J7KOTA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGI2DOOJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
> Download it today!
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Following up, because what you have said since does not fit the explanation I gave you and I would rather correct that than leave it standing. I told you the width goes wide after ten consecutive refused mode sets, with the rig falling back to its own default. That path is real and it is fixed. But you are on SmartSDR CAT over IP, not Hamlib, and you say it happens immediately with no delay — and ten refusals in a row would not be instant. So that is probably not your path, and I do not yet know what is. There is a second fix coming that is more likely to be yours: Nexus was re-commanding the DATA filter width on every retune, even when neither the mode nor the band had changed. That one is immediate, it happens on exactly the action you describe — clicking a call and watching the radio QSY — and it is fixed on the way to the next release. What would settle it: turn on the CAT diagnostics and click a call, then send me the few lines around the retune. I am looking for whether a width of 0 goes out on the wire. If it does, it is the fallback after all. If it does not, it is the re-command and the next build fixes it. 73 |
|
How do I turn on diagnosis
sent by ve3wej on samsung s21+ while not driving
…On Sat, Aug 15, 2026, 12:54 p.m. HamRadioTools ***@***.***> wrote:
Following up, because what you have said since does not fit the
explanation I gave you and I would rather correct that than leave it
standing.
I told you the width goes wide after ten consecutive refused mode sets,
with the rig falling back to its own default. That path is real and it is
fixed. But you are on SmartSDR CAT over IP, not Hamlib, and you say it
happens immediately with no delay — and ten refusals in a row would not be
instant. So that is probably not your path, and I do not yet know what is.
There is a second fix coming that is more likely to be yours: Nexus was
re-commanding the DATA filter width on every retune, even when neither the
mode nor the band had changed. That one is immediate, it happens on exactly
the action you describe — clicking a call and watching the radio QSY — and
it is fixed on the way to the next release.
What would settle it: turn on the CAT diagnostics and click a call, then
send me the few lines around the retune. I am looking for whether a width
of 0 goes out on the wire. If it does, it is the fallback after all. If it
does not, it is the re-command and the next build fixes it.
73
—
Reply to this email directly, view it on GitHub
<#66?email_source=notifications&email_token=AT62B6RZIUEZNTXVGXSWPD35KCIWBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGMZDGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18032391>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT62B6R5X7ZAVOQXCI6NKMT5KCIWBAVCNFSNUABJKJSXA33TNF2G64TZHMYTGMBUGU2TANJWGE5UI2LTMN2XG43JN5XDWMJQGYYDEOBWG2QXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AT62B6WBA5UDVQTNNHHQWDT5KCIWBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGMZDGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/AT62B6T7YZOZWWRPGHGAV2L5KCIWBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGMZDGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Not found yet but I noticed cat in pktusb mode. Not digiu as needed for
flex
sent by ve3wej on samsung s21+ while not driving
…On Sat, Aug 15, 2026, 12:57 p.m. Dave ve3wej ***@***.***> wrote:
How do I turn on diagnosis
sent by ve3wej on samsung s21+ while not driving
On Sat, Aug 15, 2026, 12:54 p.m. HamRadioTools ***@***.***>
wrote:
> Following up, because what you have said since does not fit the
> explanation I gave you and I would rather correct that than leave it
> standing.
>
> I told you the width goes wide after ten consecutive refused mode sets,
> with the rig falling back to its own default. That path is real and it is
> fixed. But you are on SmartSDR CAT over IP, not Hamlib, and you say it
> happens immediately with no delay — and ten refusals in a row would not be
> instant. So that is probably not your path, and I do not yet know what is.
>
> There is a second fix coming that is more likely to be yours: Nexus was
> re-commanding the DATA filter width on every retune, even when neither the
> mode nor the band had changed. That one is immediate, it happens on exactly
> the action you describe — clicking a call and watching the radio QSY — and
> it is fixed on the way to the next release.
>
> What would settle it: turn on the CAT diagnostics and click a call, then
> send me the few lines around the retune. I am looking for whether a width
> of 0 goes out on the wire. If it does, it is the fallback after all. If it
> does not, it is the re-command and the next build fixes it.
>
> 73
>
> —
> Reply to this email directly, view it on GitHub
> <#66?email_source=notifications&email_token=AT62B6RZIUEZNTXVGXSWPD35KCIWBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGMZDGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18032391>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AT62B6R5X7ZAVOQXCI6NKMT5KCIWBAVCNFSNUABJKJSXA33TNF2G64TZHMYTGMBUGU2TANJWGE5UI2LTMN2XG43JN5XDWMJQGYYDEOBWG2QXMAQ>
> .
> Triage notifications, keep track of coding agent tasks and review pull
> requests on the go with GitHub Mobile for iOS
> <https://github.com/notifications/mobile/ios/AT62B6WBA5UDVQTNNHHQWDT5KCIWBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGMZDGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
> and Android
> <https://github.com/notifications/mobile/android/AT62B6T7YZOZWWRPGHGAV2L5KCIWBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGMZDGOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
> Download it today!
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Two answers, and your PKTUSB observation may be the whole story. Which rig model is selected in Settings -> Radio? For a Flex over SmartSDR CAT on port 5002 it needs to be FlexRadio FLEX-6xxx (SmartSDR CAT) — that profile is what translates the mode Nexus commands into the DIGU your radio wants. If it is set to a Kenwood TS-2000 or a PowerSDR entry instead, the translation never happens, SmartSDR sees a mode it handles differently, and the filter lands wherever SmartSDR decides — which would explain the instant 6 kHz with no delay, and the PKTUSB you spotted. One honest caveat: I have verified the shipped library carries the DIGU spelling for that profile, but I could not read the Flex mode table itself from here. On turning on diagnosis: for a Flex there is no toggle — the CAT status line under the dial IS the diagnosis. It prints every mode command and every refusal as they happen ("rig set to ..." / "rig refused ..."). The separate diagnostic log switch you may have seen mentioned is Icom-only and cannot appear for your radio. So: tell me what the model dropdown says, and what the CAT status line reads right after you click a call and the width goes wide. Those two answers settle it. 73 |
|
set for flex, see attached.
Dave Garber
VE3WEJ / VE3IE
…On Sun, Aug 16, 2026 at 1:23 AM HamRadioTools ***@***.***> wrote:
Two answers, and your PKTUSB observation may be the whole story.
Which rig model is selected in Settings -> Radio? For a Flex over SmartSDR
CAT on port 5002 it needs to be *FlexRadio FLEX-6xxx (SmartSDR CAT)* —
that profile is what translates the mode Nexus commands into the DIGU your
radio wants. If it is set to a Kenwood TS-2000 or a PowerSDR entry instead,
the translation never happens, SmartSDR sees a mode it handles differently,
and the filter lands wherever SmartSDR decides — which would explain the
instant 6 kHz with no delay, and the PKTUSB you spotted. One honest caveat:
I have verified the shipped library carries the DIGU spelling for that
profile, but I could not read the Flex mode table itself from here.
On turning on diagnosis: for a Flex there is no toggle — the CAT status
line under the dial IS the diagnosis. It prints every mode command and
every refusal as they happen ("rig set to ..." / "rig refused ..."). The
separate diagnostic log switch you may have seen mentioned is Icom-only and
cannot appear for your radio.
So: tell me what the model dropdown says, and what the CAT status line
reads right after you click a call and the width goes wide. Those two
answers settle it.
73
—
Reply to this email directly, view it on GitHub
<#66?email_source=notifications&email_token=AT62B6QNHKE3YFQG6Y4AYQL5KFAL5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGM3TKOJXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18037597>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT62B6UINJEZU7I4LBXEYN35KFAL5AVCNFSNUABJKJSXA33TNF2G64TZHMYTGMBUGU2TANJWGE5UI2LTMN2XG43JN5XDWMJQGYYDEOBWG2QXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AT62B6RO74T2JHP2ZJZ6RHL5KFAL5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGM3TKOJXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/AT62B6QZ6Y4SGJIZSYGYWGT5KFAL5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGM3TKOJXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Dave — the attachment didn't make it through: replying by email drops images, so open this page in a browser and drag the screenshot in there. While you're at it, two things settle this: the exact CAT status line under the dial right after you click a call, and which Nexus version you're on — both width fixes shipped in 1.4.0, so if you're earlier than that, update first and this may simply be gone. 73 |
|
I have since downloaded 1.6.2, but 6000hz issue still exists, and going
from cw ( and cw frequency), then clicking on FT, does not qsy to ft8 or
ft4 frequency, it stays on cw freq, and 6000 hz wide. I am still not
understanding the "default" of 6000 hz. I have never, except and only seen
it used in AM mode
Dave Garber
VE3WEJ / VE3IE
…On Mon, Aug 17, 2026 at 6:10 PM HamRadioTools ***@***.***> wrote:
Dave — the attachment didn't make it through: replying by email drops
images, so open this page in a browser and drag the screenshot in there.
While you're at it, two things settle this: the exact CAT status line under
the dial right after you click a call, and which Nexus version you're on —
both width fixes shipped in 1.4.0, so if you're earlier than that, update
first and this may simply be gone. 73
—
Reply to this email directly, view it on GitHub
<#66?email_source=notifications&email_token=AT62B6TD7RBYQ4VRYMWDA535KN7E7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGU3TCNBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18057144>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT62B6S6REOG675RVFEWREL5KN7E7AVCNFSNUABJKJSXA33TNF2G64TZHMYTGMBUGU2TANJWGE5UI2LTMN2XG43JN5XDWMJQGYYDEOBWG2QXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AT62B6UVDHXYZGYAGXYIUFL5KN7E7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGU3TCNBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/AT62B6RSFHDDMBEHFTMP5VL5KN7E7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGU3TCNBUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Dave — found it, and your AM instinct was right. Nexus never asks for 6000: on that path it sends the mode change with no filter width at all, and SmartSDR's CAT emulation applies its own default filter when it gets a bare mode set — which looks to be that 6-kHz AM-ish width. Nexus also re-sends the mode more often than it needs to, which is why you see it constantly; that's getting fixed, but I want to confirm the radio-side behavior on a real Flex first, and you can nail it in two minutes. With SmartSDR's filter display visible and the slice in DIGU, run Separately: you're right that clicking over to FT should QSY you to an FT8 frequency and doesn't — that one's a straight bug on my end, already fixed for the next release. I've reopened #82 to track the filter half properly. 73 |
|
do I have to download rigctl ??? |
|
sorry, found it within nexus, but comes up errors so I am starting it wrong i think |
Uh oh!
There was an error while loading. Please reload this page.
COuld someone tell me my Flex 6400 is sudenly setting filter on any mode change/band change to 6000hz, instead of leaving ait where I set the radio. ft8 does not use 6000, that I have ever seen
All reactions