Replies: 10 comments 1 reply
|
Hi Jim, thanks for giving it a go on the FTDX5000. The FTDX5000 isn't a formally supported model yet, so picking another Yaesu profile is exactly the right approach - and I think I know why band changes fail. A quick technical note: YWC changes band by sending the radio a frequency command, not a dedicated "band" command. The FTDX5000 uses 8-digit frequency values (00030000-60000000 Hz), the same as the FTDX3000, whereas most other Yaesu models use 9 digits. Older YWC builds always sent 9 digits, which an 8-digit radio silently rejects - so band changes (and direct frequency entry) just don't take. I fixed exactly this for the FTDX3000 recently. The catch is the fix is currently only in the test (pre-release) builds, not the latest normal release. Two quick questions so I can point you the right way:
If you're willing to test: grab the latest pre-release v2.4.2-pre21 from https://github.com/mm5agm/Yaesu_Web_Control/releases/tag/v2.4.2-pre21 (my in-app updater won't offer pre-releases automatically, so that direct link is the only way). Install it, select FTDX3000 in Settings as the closest match, and see whether band changes and direct frequency entry work now. One heads-up: the FTDX5000 is a dual-receiver radio, so the second VFO/sub-receiver may behave oddly under the FTDX3000 profile - we can sort that out as part of proper FTDX5000 support. If the band/frequency side works for you, I'd be glad to add a proper FTDX5000 profile with you as the tester. And when you get a chance, could you list the "few other issues" specifically (a log file helps a lot - Diagnostics > Download test log)? 73, Colin |
|
Colin thanks for the quick response. I am currently running V2.2.0 and have
tried the FTDX3000 and the FTDX101MP with the same results which makes
sense after reading your explanation. I will download your pre-release
version v2.4.2-pre21 and let you know my results. Might be a little bit
before I get back to you as I am about ready to leave for the day. I'd be
glad to help you out in any way with the FTDX5000 test.
As soon as I get a chance I'll test the new version and get back to you.
Thanks...Jim K2QB
…On Mon, Jul 27, 2026 at 8:22 AM Colin Campbell ***@***.***> wrote:
Hi Jim, thanks for giving it a go on the FTDX5000.
The FTDX5000 isn't a formally supported model yet, so picking another
Yaesu profile is exactly the right approach - and I think I know why band
changes fail. A quick technical note: YWC changes band by sending the radio
a frequency command, not a dedicated "band" command. The FTDX5000 uses
8-digit frequency values (00030000-60000000 Hz), the same as the FTDX3000,
whereas most other Yaesu models use 9 digits. Older YWC builds always sent
9 digits, which an 8-digit radio silently rejects - so band changes (and
direct frequency entry) just don't take.
I fixed exactly this for the FTDX3000 recently. The catch is the fix is
currently only in the test (pre-release) builds, not the latest normal
release.
Two quick questions so I can point you the right way:
1. Which version of YWC did you download? (Help > About, or the
installer filename.)
2. Which Yaesu model did you select in Settings?
If you're willing to test: grab the latest pre-release v2.4.2-pre21 from
https://github.com/mm5agm/Yaesu_Web_Control/releases/tag/v2.4.2-pre21 (my
in-app updater won't offer pre-releases automatically, so that direct link
is the only way). Install it, select FTDX3000 in Settings as the closest
match, and see whether band changes and direct frequency entry work now.
One heads-up: the FTDX5000 is a dual-receiver radio, so the second
VFO/sub-receiver may behave oddly under the FTDX3000 profile - we can sort
that out as part of proper FTDX5000 support. If the band/frequency side
works for you, I'd be glad to add a proper FTDX5000 profile with you as the
tester. And when you get a chance, could you list the "few other issues"
specifically (a log file helps a lot - Diagnostics > Download test log)?
73, Colin
—
Reply to this email directly, view it on GitHub
<#85?email_source=notifications&email_token=CJ3DZ5S7IW5YRIZXR7SLQ6L5G5CSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHE3TCNRUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17797164>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CJ3DZ5RRFGSIKNLLJDKS2MT5G5CSDAVCNFSNUABJKJSXA33TNF2G64TZHMYTENBVGUYDANJYHA5UI2LTMN2XG43JN5XDWMJQGUYDGNRTGWQXMAQ>
.
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/CJ3DZ5VBQSCMH37GNJAZWJL5G5CSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHE3TCNRUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CJ3DZ5TUTPOSAMKZHHMZTED5G5CSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHE3TCNRUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
So Colin here is what I found so far with v2.4.2-pre21 using my FTDX5000MP.
- Selecting FTDX3000 as the radio I am now able to switch bands by
clicking on the band buttons.
- I can switch modes and key the xmtr.
- I can select different antennas.
- AGC, NB, Man Notch all work as they should.
- Roofing, RF Gain and AF Gain works as they should.
- Monitor and ATU work as they should.
- Power Out meter is very slow to respond.
- Unable to get VFO B selected.
- No window display of spectrum.
So far this is what i have found. Now a really dumb question. I assume I
should be able to run the app on my laptop and have access to my radio at
home which is connected to my home PC, but I haven't been able to figure
out how to change the IP address in the setup to direct it to my home
network.
Thanks and let me know what I can do for you.
Jim K2QB
…On Mon, Jul 27, 2026 at 8:22 AM Colin Campbell ***@***.***> wrote:
Hi Jim, thanks for giving it a go on the FTDX5000.
The FTDX5000 isn't a formally supported model yet, so picking another
Yaesu profile is exactly the right approach - and I think I know why band
changes fail. A quick technical note: YWC changes band by sending the radio
a frequency command, not a dedicated "band" command. The FTDX5000 uses
8-digit frequency values (00030000-60000000 Hz), the same as the FTDX3000,
whereas most other Yaesu models use 9 digits. Older YWC builds always sent
9 digits, which an 8-digit radio silently rejects - so band changes (and
direct frequency entry) just don't take.
I fixed exactly this for the FTDX3000 recently. The catch is the fix is
currently only in the test (pre-release) builds, not the latest normal
release.
Two quick questions so I can point you the right way:
1. Which version of YWC did you download? (Help > About, or the
installer filename.)
2. Which Yaesu model did you select in Settings?
If you're willing to test: grab the latest pre-release v2.4.2-pre21 from
https://github.com/mm5agm/Yaesu_Web_Control/releases/tag/v2.4.2-pre21 (my
in-app updater won't offer pre-releases automatically, so that direct link
is the only way). Install it, select FTDX3000 in Settings as the closest
match, and see whether band changes and direct frequency entry work now.
One heads-up: the FTDX5000 is a dual-receiver radio, so the second
VFO/sub-receiver may behave oddly under the FTDX3000 profile - we can sort
that out as part of proper FTDX5000 support. If the band/frequency side
works for you, I'd be glad to add a proper FTDX5000 profile with you as the
tester. And when you get a chance, could you list the "few other issues"
specifically (a log file helps a lot - Diagnostics > Download test log)?
73, Colin
—
Reply to this email directly, view it on GitHub
<#85?email_source=notifications&email_token=CJ3DZ5S7IW5YRIZXR7SLQ6L5G5CSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHE3TCNRUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17797164>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CJ3DZ5RRFGSIKNLLJDKS2MT5G5CSDAVCNFSNUABJKJSXA33TNF2G64TZHMYTENBVGUYDANJYHA5UI2LTMN2XG43JN5XDWMJQGUYDGNRTGWQXMAQ>
.
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/CJ3DZ5VBQSCMH37GNJAZWJL5G5CSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHE3TCNRUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CJ3DZ5TUTPOSAMKZHHMZTED5G5CSDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXHE3TCNRUUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
That is great news, Jim - thank you for the thorough test. The important bit is confirmed: band switching and direct frequency entry now work on a real FTDX5000, which proves the 8-digit frequency fix. Everything you listed as working (modes, TX, antennas, AGC/NB/notch, roofing, RF/AF gain, monitor, ATU) is exactly what I'd hope to see. Even better - I've now added proper FTDX5000MP and FTDX5000D profiles, and they're in a fresh pre-release you can try right now: https://github.com/mm5agm/Yaesu_Web_Control/releases/tag/v2.4.2-pre22 Install that, then go to Settings > Radio Model and select FTDX5000MP (instead of FTDX3000). The FTDX5000 is a true dual-receiver radio, so you should now see VFO A and VFO B side by side, each with its own controls and S-meter. I'd really appreciate it if you could test it and let me know how the sub-receiver behaves - that's the main thing I can't check myself without the radio. On the three issues from your last test:
On running it from your laptop remotely - good question, and not a dumb one. There isn't an IP setting to change, because YWC is itself the little web server. It runs on the PC that's cabled to the radio and listens on port 8080; you don't install a second copy on the laptop, you just point a browser at the home PC. There are two cases: Same home network (laptop and PC on the same Wi-Fi/LAN): just open a browser on the laptop and go to your home PC's local address, e.g. http://192.168.1.50:8080 (find the PC's IPv4 address with "ipconfig" on the home PC). You may get a one-time Windows Firewall prompt to allow YWC. Away from home (laptop out on the internet, radio still at home): this works, but please don't just open/forward port 8080 on your router to the internet. YWC has no username or password - it assumes it's on your trusted home network - so exposing it directly would let anyone who finds it control your radio. The safe way is to make your laptop part of your home network remotely, using a VPN, and then use the same http://192.168.1.50:8080 address as if you were at home. Easiest options:
Either way YWC itself needs no changes - the VPN just makes "away" look like "at home". If you tell me what router you have I can point you at the specific setting; but Tailscale is usually the quickest win. One important caveat before you go too far down this road: YWC gives you control, meters and (with an SDR) spectrum, but it does not carry the radio's audio - there's no receive audio or microphone path wired into it. So over a remote link you'd be able to tune, change bands and drive the rig, but you wouldn't hear anything through YWC. For genuine remote operating you'd need a separate audio path as well - the simplest being a remote-desktop session into the home PC (which can carry the PC's sound back to your laptop), or a dedicated audio-over-IP setup alongside YWC. I just don't want you to build the VPN and find it silent. Audio is on my longer-term wish list, but it isn't there today. That said, I do have a few users who are already operating remotely with YWC and handling the audio separately - I'm waiting to hear back on exactly how they've set it up. A Mumble server rings a bell as one approach they use for the audio side. Once I have the details I'll be glad to pass them on, and if you get something working I'd love to hear how you did it too. Thanks again - your report moved this forward a long way, and I'd be glad to have you as the FTDX5000 tester. 73, Colin |
|
1.
VFO B / sub-receiver not selectable. That was expected under the
FTDX3000 profile (the FTDX3000 is single-receiver, so YWC had no concept of
a second receiver). The new FTDX5000MP profile is exactly the fix - select
it and VFO B should come to life. VFO B is now tracking frequency but
remains greyed out and I am unable to select nads, input frequency, etc.
2.
Power Out meter very slow to respond. Worth chasing. Could you send me a
diagnostics log while you key up and watch the meter? In YWC: Diagnostics >
Download test log, transmit into a dummy load for a few seconds, then grab
the log and attach it here. That'll show me how the radio is reporting the
reading and why it's lagging. (Note: the power/S-meter calibration in this
build is still a placeholder cloned from the FTdx101MP - we'll refine it
with your real numbers.) Log is attached.
3.
No spectrum display. Expected, not a fault. The spectrum/panadapter
needs a separate SDR receiver (e.g. an SDRplay RSP) fed from the radio's IF
output - it doesn't come from the CAT link. Without an SDR connected the
spectrum area stays blank. It's optional; everything else works
without it. I
have an SDR play connected to the IF out of the FTDX5000 and have selected
it under settings but still no display.
…On Tue, Jul 28, 2026 at 6:12 PM Colin Campbell ***@***.***> wrote:
That is great news, Jim - thank you for the thorough test. The important
bit is confirmed: band switching and direct frequency entry now work on a
real FTDX5000, which proves the 8-digit frequency fix. Everything you
listed as working (modes, TX, antennas, AGC/NB/notch, roofing, RF/AF gain,
monitor, ATU) is exactly what I'd hope to see.
Even better - I've now added proper FTDX5000MP and FTDX5000D profiles, and
they're in a fresh pre-release you can try right now:
https://github.com/mm5agm/Yaesu_Web_Control/releases/tag/v2.4.2-pre22
Install that, then go to Settings > Radio Model and select FTDX5000MP
(instead of FTDX3000). The FTDX5000 is a true dual-receiver radio, so you
should now see VFO A and VFO B side by side, each with its own controls and
S-meter. I'd really appreciate it if you could test it and let me know how
the sub-receiver behaves - that's the main thing I can't check myself
without the radio.
On the three issues from your last test:
1.
VFO B / sub-receiver not selectable. That was expected under the
FTDX3000 profile (the FTDX3000 is single-receiver, so YWC had no concept of
a second receiver). The new FTDX5000MP profile is exactly the fix - select
it and VFO B should come to life.
2.
Power Out meter very slow to respond. Worth chasing. Could you send me
a diagnostics log while you key up and watch the meter? In YWC: Diagnostics
> Download test log, transmit into a dummy load for a few seconds, then
grab the log and attach it here. That'll show me how the radio is reporting
the reading and why it's lagging. (Note: the power/S-meter calibration in
this build is still a placeholder cloned from the FTdx101MP - we'll refine
it with your real numbers.)
3.
No spectrum display. Expected, not a fault. The spectrum/panadapter
needs a separate SDR receiver (e.g. an SDRplay RSP) fed from the radio's IF
output - it doesn't come from the CAT link. Without an SDR connected the
spectrum area stays blank. It's optional; everything else works without it.
On running it from your laptop remotely - good question, and not a dumb
one. There isn't an IP setting to change, because YWC is itself the little
web server. It runs on the PC that's cabled to the radio and listens on
port 8080; you don't install a second copy on the laptop, you just point a
browser at the home PC.
There are two cases:
Same home network (laptop and PC on the same Wi-Fi/LAN): just open a
browser on the laptop and go to your home PC's local address, e.g.
http://192.168.1.50:8080 (find the PC's IPv4 address with "ipconfig" on
the home PC). You may get a one-time Windows Firewall prompt to allow YWC.
Away from home (laptop out on the internet, radio still at home): this
works, but please don't just open/forward port 8080 on your router to the
internet. YWC has no username or password - it assumes it's on your trusted
home network - so exposing it directly would let anyone who finds it
control your radio. The safe way is to make your laptop part of your home
network remotely, using a VPN, and then use the same
http://192.168.1.50:8080 address as if you were at home. Easiest options:
- A "mesh VPN" like Tailscale or ZeroTier - install it on both the
home PC and the laptop, and they can talk to each other from anywhere with
no router changes. This is the simplest and what I'd suggest starting with.
- Or a VPN built into your home router, if it has one
(OpenVPN/WireGuard), which puts the laptop back on your home LAN when
connected.
Either way YWC itself needs no changes - the VPN just makes "away" look
like "at home". If you tell me what router you have I can point you at the
specific setting; but Tailscale is usually the quickest win.
One important caveat before you go too far down this road: YWC gives you
control, meters and (with an SDR) spectrum, but it does not carry the
radio's audio - there's no receive audio or microphone path wired into it.
So over a remote link you'd be able to tune, change bands and drive the
rig, but you wouldn't hear anything through YWC. For genuine remote
operating you'd need a separate audio path as well - the simplest being a
remote-desktop session into the home PC (which can carry the PC's sound
back to your laptop), or a dedicated audio-over-IP setup alongside YWC. I
just don't want you to build the VPN and find it silent. Audio is on my
longer-term wish list, but it isn't there today.
That said, I do have a few users who are already operating remotely with
YWC and handling the audio separately - I'm waiting to hear back on exactly
how they've set it up. A Mumble server rings a bell as one approach they
use for the audio side. Once I have the details I'll be glad to pass them
on, and if you get something working I'd love to hear how you did it too.
Thanks again - your report moved this forward a long way, and I'd be glad
to have you as the FTDX5000 tester.
73, Colin
—
Reply to this email directly, view it on GitHub
<#85?email_source=notifications&email_token=CJ3DZ5UUOLPLIOUA6JQSYID5HEQNJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGE4DKNZYUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17818578>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CJ3DZ5X43AIDJADGQYTYBUD5HEQNJAVCNFSNUABJKJSXA33TNF2G64TZHMYTENBVGUYDANJYHA5UI2LTMN2XG43JN5XDWMJQGUYDGNRTGWQXMAQ>
.
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/CJ3DZ5UVEY7EGBTNM6Z5HSL5HEQNJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGE4DKNZYUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CJ3DZ5UVG467Z7CS7OKQNET5HEQNJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGE4DKNZYUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
Thanks Jim, that's really useful - and good news that VFO B is now tracking the sub-receiver frequency, that tells me the FTDX5000MP profile is being applied. Let me take the three in turn. 1. VFO B greyed out / can't select bands or enter a frequency I think this one may just be a stale page in the browser rather than a real fault. Here's why: whether a VFO panel is "live" or "greyed and locked" is decided by a flag written into the page when it first loads. On pre21 you were running the FTDX3000 profile, which is single-receiver, so YWC deliberately greys VFO B and disables its controls. If your browser is still showing a cached copy of the page from that FTDX3000 session, VFO B stays greyed - while the live data feed (a separate connection) keeps updating the frequency underneath. That would match exactly what you're seeing: frequency moving, but everything else locked. Could you try a hard refresh after selecting FTDX5000MP:
Then check VFO B again - the band buttons, mode and frequency box should all be fully usable, and the panel should no longer look dimmed. Let me know if that brings it to life. If it's still greyed after a hard refresh, then it is a real bug and I'll dig in properly - if so, please open F12 (Developer Tools) and tell me if there are any red errors in the Console tab. 2. Power Out meter - the log didn't reach me I think your log got lost. It looks like you replied by email, and GitHub quietly drops file attachments that come in that way, so nothing arrived on my end. Could you attach it directly on the web page instead: open the discussion in a browser, and drag the .log file into the comment box (or use the paperclip / "attach files" link below it). Once I have it I can see exactly how the radio is reporting the power reading and why it lags. 3. Spectrum still blank with the SDRplay on the IF output This one is separate and worth chasing. A couple of quick questions to narrow it down:
And if you can grab a diagnostics log covering startup with the SDR selected (same Diagnostics > Download test log), that will show me whether YWC is managing to start the SDR worker at all. Thanks again Jim - the VFO B and power bits are close, and once I can see the two logs I'll get the rest sorted. 73, Colin |
|
Could you try a hard refresh after selecting FTDX5000MP:
- Click into the YWC page and press *Ctrl+F5* (hold Ctrl and press F5),
or
- Close the browser tab completely and open a fresh one to the YWC
address.
Then check VFO B again - the band buttons, mode and frequency box should
all be fully usable, and the panel should no longer look dimmed. Let me
know if that brings it to life. If it's still greyed after a hard refresh,
then it is a real bug and I'll dig in properly - if so, please open F12
(Developer Tools) and tell me if there are any red errors in the Console
tab.
VFO B activated briefly then goes to grayed out again. I am not seeing any
red errors in the console tab. The hard refresh did bring my Spectrum Scope
to life.
*2. Power Out meter - the log didn't reach me - *Log file attached under
Support on web site.
*Jim K2QB*
…On Thu, Jul 30, 2026 at 2:37 PM Colin Campbell ***@***.***> wrote:
Thanks Jim, that's really useful - and good news that VFO B is now
tracking the sub-receiver frequency, that tells me the FTDX5000MP profile
is being applied. Let me take the three in turn.
*1. VFO B greyed out / can't select bands or enter a frequency*
I think this one may just be a stale page in the browser rather than a
real fault. Here's why: whether a VFO panel is "live" or "greyed and
locked" is decided by a flag written into the page when it first loads. On
pre21 you were running the FTDX3000 profile, which is single-receiver, so
YWC deliberately greys VFO B and disables its controls. If your browser is
still showing a cached copy of the page from that FTDX3000 session, VFO B
stays greyed - while the live data feed (a separate connection) keeps
updating the frequency underneath. That would match exactly what you're
seeing: frequency moving, but everything else locked.
Could you try a hard refresh after selecting FTDX5000MP:
- Click into the YWC page and press *Ctrl+F5* (hold Ctrl and press
F5), or
- Close the browser tab completely and open a fresh one to the YWC
address.
Then check VFO B again - the band buttons, mode and frequency box should
all be fully usable, and the panel should no longer look dimmed. Let me
know if that brings it to life. If it's still greyed after a hard refresh,
then it is a real bug and I'll dig in properly - if so, please open F12
(Developer Tools) and tell me if there are any red errors in the Console
tab.
*2. Power Out meter - the log didn't reach me*
I think your log got lost. It looks like you replied by email, and GitHub
quietly drops file attachments that come in that way, so nothing arrived on
my end. Could you attach it directly on the web page instead: open the
discussion in a browser, and drag the .log file into the comment box (or
use the paperclip / "attach files" link below it). Once I have it I can see
exactly how the radio is reporting the power reading and why it lags.
*3. Spectrum still blank with the SDRplay on the IF output*
This one is separate and worth chasing. A couple of quick questions to
narrow it down:
- In YWC, go to *Diagnostics* and run the device scan - does your
SDRplay show up in the list there?
- On the main screen, does the spectrum area show a small status label
(e.g. "connecting", "streaming", "disconnected", or "No DLL")? What does it
say?
- Which SDRplay model is it (RSP1A, RSPdx, etc.)?
And if you can grab a diagnostics log covering startup with the SDR
selected (same Diagnostics > Download test log), that will show me whether
YWC is managing to start the SDR worker at all.
Thanks again Jim - the VFO B and power bits are close, and once I can see
the two logs I'll get the rest sorted.
73, Colin
—
Reply to this email directly, view it on GitHub
<#85?email_source=notifications&email_token=CJ3DZ5QNGNYLF3BK244Q7ZD5HOIVHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGQ2DAOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17844091>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CJ3DZ5XYZUU2BVEGBTHAY7D5HOIVHAVCNFSNUABJKJSXA33TNF2G64TZHMYTENBVGUYDANJYHA5UI2LTMN2XG43JN5XDWMJQGUYDGNRTGWQXMAQ>
.
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/CJ3DZ5SFBMPUTRPWAXPPLPL5HOIVHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGQ2DAOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CJ3DZ5Q7L4XHDWBAECWZUDL5HOIVHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGQ2DAOJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
Thanks Jim - and good to hear the Spectrum Scope came to life after the hard refresh, that one's sorted. On VFO B: the fact that it lights up briefly and then goes grey tells me the page is probably being drawn as if the radio were single-receiver, and then the first data update greys the "inactive" side. On a proper dual-receiver setup that greying can't happen at all, so I want to confirm what your page is actually being told the radio is. Could you do a quick check for me:
That single line tells me whether the server is handing the page the wrong receiver type (a bug I can fix) or whether the radio model didn't quite save. If 73, Colin |
|
Collin when I do a search for vfoRow...it finds nothing.
Jim
…On Sat, Aug 1, 2026 at 7:38 AM Colin Campbell ***@***.***> wrote:
Thanks Jim - and good to hear the Spectrum Scope came to life after the
hard refresh, that one's sorted.
On VFO B: the fact that it lights up briefly and then goes grey tells me
the page is probably being drawn as if the radio were single-receiver, and
then the first data update greys the "inactive" side. On a proper
dual-receiver setup that greying can't happen at all, so I want to confirm
what your page is actually being told the radio is.
Could you do a quick check for me:
- With YWC open, press *F12* to open Developer Tools and click the
*Elements* (or *Inspector*) tab.
- Press *Ctrl+F* inside that panel and search for vfoRow.
- You'll land on a line like <div id="vfoRow" data-radio-model="..."
data-single-receiver="...">.
- Tell me the two values: *data-radio-model* and *data-single-receiver*
.
That single line tells me whether the server is handing the page the wrong
receiver type (a bug I can fix) or whether the radio model didn't quite
save. If data-radio-model shows anything other than FTDX5000MP, go back
to *Settings > Radio Model*, re-select *FTDX5000MP*, save, then fully
restart YWC (close it completely and relaunch, not just the browser) so the
backend picks up the change - then Ctrl+F5 the page.
73, Colin
—
Reply to this email directly, view it on GitHub
<#85?email_source=notifications&email_token=CJ3DZ5UEMPDWJTNNY7FWC6T5HXJENA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGYZDKNZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17862579>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CJ3DZ5RY4KDHQYS7ZFABQOL5HXJENAVCNFSNUABJKJSXA33TNF2G64TZHMYTENBVGUYDANJYHA5UI2LTMN2XG43JN5XDWMJQGUYDGNRTGWQXMAQ>
.
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/CJ3DZ5RUVH63ZQ4VYJZTN235HXJENA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGYZDKNZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CJ3DZ5XMKHF57X5XACHVV5T5HXJENA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGYZDKNZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
|
Thanks Jim. I'll get back to you later this week. My A.I. account ran out of funds and I'll need to wait till I get my pocket money to top it up. |
|
Thanks Jim -- since the spectrum came right after the hard refresh but VFO B still greys out, that rules out a stale page, so I want to check exactly how the server is rendering your radio. Could you do this on the YWC tab:
var r=document.getElementById('vfoRow');console.log('model=',r&&r.dataset.radioModel,'single=',r&&r.dataset.singleReceiver)It'll print something like If it shows 73 Colin |
Uh oh!
There was an error while loading. Please reload this page.
Anyone have success using this with a FTDX5000? I can get it to connect and almost work using other Yaesu radio protocols but unable to change bands and a few other issues.
Jim K2QB
All reactions