Hi Yukio-san,
Thanks for alerting us to the omission of a mode-label color definition
for FT4, and the typo. They will be corrected in the next release!
-- Joe, K1JT
On 5/22/2020 8:52 PM, Yukio JG1APX wrote:
Hello all
I have noticed minor things in mainwindow.cpp source code. If
Hi, I'm concentrating on the UI rather than program function, hopefully
not too pernickety! Some of these may not be specific to RC1 but are
just things I've noticed on specifically looking for anomalies etc:
1. The RC opens in 7 seconds on this machine, 5 seconds for 2.1.2 - a
noticeable
Hi Alan,
thanks for your considered comments and observations. Some comments in
line below from me.
On 23/05/2020 16:50, Alan Groups wrote:
Hi, I'm concentrating on the UI rather than program function,
hopefully not too pernickety! Some of these may not be specific to
RC1 but are just
Hi Joe
Thank you.
I am glad to hear that.
73
Yukio JG1APX
On Sat, 23 May 2020 09:11:20 -0400
Joe Taylor wrote:
> Hi Yukio-san,
>
> Thanks for alerting us to the omission of a mode-label color definition for
> FT4, and the typo. They will be corrected in the next release!
>
> --
Hi Bill, hi developers,
thank you for your answer.
I've tried to check the specification of BLE beacons:
They use only 3 Channels for 'connection-less' beacons, e.g.
https://github.com/AltBeacon/spec
(channels 37, 38 and 39, spread over the Bluetooth/WiFi frequencies).
Further they send the
On 23/05/2020 19:51, Dave K1SX wrote:
I did not see any over/underruns in VAC, but warnings in the VAC log did prompt
me to change an interrupt timing setting, and I have not see the problem since.
Although, it was not easy to catch in any event.
Hi Dave,
adusting the VAC interrupt
Hi Bill,
thanks...
I did not see any over/underruns in VAC, but warnings in the VAC log did prompt
me to change an interrupt timing setting, and I have not see the problem since.
Although, it was not easy to catch in any event.
Since I could work around my PTT issue, I have been able to use
I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m
able to get the receive Audio Codec to work properly and I can see decodes
but I get a “Rig Failure - Hamlib Error - Invalid configuration while
opening connection to rig” whenever I do a Test CAT. I am unable to get
WSJT-X
On 23/05/2020 23:16, Bill wrote:
I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac.
I’m able to get the receive Audio Codec to work properly and I can see
decodes but I get a “Rig Failure - Hamlib Error - Invalid
configuration while opening connection to rig” whenever I
Hi,
Thanks for the quick response. I just tried HandShake = NONE and I
have the same result - Rig Failure - HamLib Error.
Any other suggestions?
Thanks!
Bill - AK6A
On Sat, May 23, 2020 at 3:32 PM Bill Somerville
wrote:
> On 23/05/2020 23:16, Bill wrote:
>
> I am having an issue
Hi John,
I'm using a Mac so whatever problems there might be are doubled. I've
tried accessing the radio through the MacLoggerDX program but that didn't
work either. I'm using USB2 direct - no hubs. There is some talk about the
new Silicon Labs drivers not working properly and an older
Bill,
Many new 101MP owners in the PNW have been experiencing some setup issues,
resulting in lots of phone calls.
Have you been able to talk to the rig with any other S/W via USB and with what
virtual settings?
Is the PC using USB 2.0 or 3.x ? The 101MP is unfortunately persnickety in
I had issues to but on window 10 platform.
I used the FT5000 rig, everything burst into life when I switched over from
FTdx101D
Ken.. G0ORH
Sent from my iPad
> On 24 May 2020, at 01:02, John Zantek wrote:
>
> Bill,
> Many new 101MP owners in the PNW have been experiencing some setup
On 23/05/2020 23:59, Bill wrote:
Hi,
Thanks for the quick response. I just tried HandShake = NONE and I
have the same result - Rig Failure - HamLib Error.
Any other suggestions?
Thanks!
Bill - AK6A
Hi Bill,
please include the message shown by pressing the "Show Details ..."
Using /dev/cu.SLAB_USBtoUART the handshake is set to NONE
When I tried the Handshake = Hardware I received the same error.
Thanks for helping me with this. I know you are very busy with the RC.
Since the FTDX101MP is a new radio there doesn't seem to be much info out
there.
- Bill
On Sat, May
I've seen this a couple of times before on RC1, Windows 10-64.
I responded to a CQ from VE3VN (Hold TX set, also auto seq & call 1st). Just
after my transmission began I halted tx because I noticed he had called CQ
WC, which I guess isn't me. Then I saw, in red in the band activity window,
VE3VN
Hi Bill,
When using /dev/cu.SLAB_USBtoUART1 The error details shows: HamLib Error:
Invalid configuration while opening connection to rig.
When using /dev/cu.SLAB_USBtoUART The error details shows: HamLib Error:
Communication timed out while getting current frequency.
Both selections end up
On 24/05/2020 00:18, Bill wrote:
When using /dev/cu.SLAB_USBtoUART The error details shows: HamLib
Error: Communication timed out while getting current frequency.
Hi Bill,
was that with "Settings->Radio->Handshake->Hardware" or
"Settings->Radio->Handshake->None"?
73
Bill
G4WJS.
18 matches
Mail list logo
