Re: Richard Shaw
> I figured it out... x10.
>
> I had the inputs and outputs reversed. Apparently there was enough
> bleedover to even make a contact which is why I thought it was hooked up
> correctly.
>
> Sorry for the noise.
Literally :)
Thanks for cheering me up,
Christoph
___
Thanks!
How do I find the development branch? I found the errant code in the
"master" branch.
From: Bill Somerville
Sent: Friday, July 17, 2020 09:12
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Introduction and merge request
On 17/07/2020 15:55, Mike Blaszczak wrote
On 17/07/2020 19:47, Richard Shaw wrote:
I figured it out... x10.
I had the inputs and outputs reversed. Apparently there was enough
bleedover to even make a contact which is why I thought it was hooked
up correctly.
Sorry for the noise.
Thanks,
Richard
Hi Richard,
ha ha, it can be a pro
I figured it out... x10.
I had the inputs and outputs reversed. Apparently there was enough
bleedover to even make a contact which is why I thought it was hooked up
correctly.
Sorry for the noise.
Thanks,
Richard
>
___
wsjt-devel mailing list
wsjt-dev
On Fri, Jul 17, 2020 at 12:02 PM Bill Somerville
wrote:
> maybe it's a problem with the driver for the sound card chip, it could be
> setting the gain stage before the ADC incorrectly. Are there a master
> device level sliders on the pavucontrol devices tabs?
>
Also set to 100%. I don't want to
I think I need to add some imaginary punctuation :)
> DX Lab Suite Commander: Failed to send command
> "CmdGetFreq": The remote host closed the connection”
I read it as DX Lab Suite Commander failed to send command…
Thanks,
Tom
Tom Schaefer, NY4I
Blog: www.ny4i.com
Madeira Beach, FL (Grid: EL8
On 17/07/2020 17:45, Richard Shaw wrote:
On Fri, Jul 17, 2020 at 11:28 AM Bill Somerville
mailto:g4...@classdesign.com>> wrote:
>
> At home I have to set the volume levels to ~50% and adjust the
audio
> slider in WSJT-X down quite a bit to keep output around 35W. While
> con
On Fri, Jul 17, 2020 at 11:28 AM Bill Somerville
wrote:
> >
> > At home I have to set the volume levels to ~50% and adjust the audio
> > slider in WSJT-X down quite a bit to keep output around 35W. While
> > connected to my laptop, both the input and output audio signals are
> > very low. I have
On 17/07/2020 17:20, Richard Shaw wrote:
I've setup at Fall Creek Falls State Park in Tennessee to teach the
Radio Merit Badge to scouts in my troop.
With the exception of the computer I'm using (a laptop) the setup is
exactly the same as my setup at home. I have a 4-port USB hub with two
USB
I've setup at Fall Creek Falls State Park in Tennessee to teach the Radio
Merit Badge to scouts in my troop.
With the exception of the computer I'm using (a laptop) the setup is
exactly the same as my setup at home. I have a 4-port USB hub with two
USB->Serial adapters (one CAT, on PTT) and a USB
On 7/16/20 at 12:11 AM, wsjt-devel@lists.sourceforge.net (Black
Michael via wsjt-devel) wrote:
If anybody has a rig out there that's in this list and you have
it working with WSJT-X...or if you have any bugs to report
working with WSJT-X please let me know.
Would like to promote as many of the
On 17/07/2020 17:09, Bill Somerville wrote:
On 17/07/2020 16:27, Thomas Schaefer wrote:
I am working on a server implementation that mimics DX Lab’s
Commander so WSJT-X can use TR4W for rig control.
I occasional;ly see a message from WSJT-X where it states,
DX Lab Suite Commander failed t
On 17/07/2020 15:55, Mike Blaszczak wrote:
Hello!
I'm Mike (K7ZCZ). I've been writing software for a long time, but I'm
mostly retired now.
After updating to WSJTX 2.2.2, I noticed a problem with the ADIF
files. I've submitted a merge request to correct it. Hopefully, I'm
not stepping on m
On 17/07/2020 16:27, Thomas Schaefer wrote:
I am working on a server implementation that mimics DX Lab’s Commander
so WSJT-X can use TR4W for rig control.
I occasional;ly see a message from WSJT-X where it states,
DX Lab Suite Commander failed to send command
"CmdGetFreq": The remote h
I am working on a server implementation that mimics DX Lab’s Commander so
WSJT-X can use TR4W for rig control.
I occasional;ly see a message from WSJT-X where it states,
DX Lab Suite Commander failed to send command
"CmdGetFreq": The remote host closed the connection”
I think what is means is
Hello!
I'm Mike (K7ZCZ). I've been writing software for a long time, but I'm mostly
retired now.
After updating to WSJTX 2.2.2, I noticed a problem with the ADIF files. I've
submitted a merge request to correct it. Hopefully, I'm not stepping on my
toes; it's been about a decade since I've
On 17/07/2020 15:11, Martin Davies G0HDB wrote:
On 17 Jul 2020 at 14:38, Bill Somerville wrote:
Hi Martin,
is there an easy way to disconnect the hard wired PTT from your
interface, for a test? I ask because it seems like the IC-7610 appears
to be doing something odd when keyed both via a CAT
On 17 Jul 2020 at 14:38, Bill Somerville wrote:
> Hi Martin,
>
> is there an easy way to disconnect the hard wired PTT from your
> interface, for a test? I ask because it seems like the IC-7610 appears
> to be doing something odd when keyed both via a CAT command and via the
> ACC socket.
Hi
Mike - snip below is exactly my point about GUI consistency.
I also agree with Bill though, in that radio amateurs should be encouraged
to experiment rather than become appliance operators, hence my "half way
house" suggestions!
Alan G0TLK, sent from my mobile device
On 17 July 2020 14:27:35
Re: Black Michael
> If you have a bug to report please do. The problem the flag would address is
> people saying "X doesn't work" when it's known that the rig can't do X.
All the patches in the Debian package are already in the hamlib git
except for the typo fix that I just submitted as PR.
Tha
On 17/07/2020 14:33, Martin Davies G0HDB wrote:
On 16 Jul 2020 at 4:11, Black Michael via wsjt-devel wrote:
If anybody has a rig out there that's in this list and you have it working with
WSJT-X...or if you have any bugs to report working with WSJT-X please let me
know.
Would like to promote
Mike,
the settings GUI is shared by all rigs and is built before the rig
connection is opened. Any information that can only be determined by
querying the rig will greatly complicate that. For example say there was
a rig emulation using a rig model that has a USB-DATA mode but that
emulation
As the user it's a matter of GUI consistency.
Selecting the Funcube radio rightly greyed out the serial settings, a
noticeable GUI change. That leads the user to expect all the other
settings are default for the radio selected, but they aren't.
I didn't get the error warning until the main w
On 16 Jul 2020 at 4:11, Black Michael via wsjt-devel wrote:
> If anybody has a rig out there that's in this list and you have it working
> with WSJT-X...or if you have any bugs to report working with WSJT-X please
> let me know.
> Would like to promote as many of these to stable as possible and
Self-training and 100% knowledge of how everything is supposed to work are two
completely different things. Far too many people just click on things until it
works without any understanding of why and won't even ask the question. I have
talked to and helped well over 1,000 hams now and many of
If you have a bug to report please do. The problem the flag would address is
people saying "X doesn't work" when it's known that the rig can't do X.
There are only 2 bugs outstanding right now in Hamlib -- both of which should
be fixed today.
https://github.com/Hamlib/Hamlib/issues
Mike W9MDB
Mike,
my Amateur Radio Licence clause 1(1)a says this:
"for the purpose of *self-training* in radio communications, including
conducting technical investigations"
My emphasis.
73
Bill
G4WJS.
On 17/07/2020 13:58, Black Michael via wsjt-devel wrote:
"Informed choices". I appreciate the humo
Re: Black Michael via wsjt-devel
> What I was referring to though was a flag that is "known" to be true. Perhaps
> for both for split and data/pkt. WSJT-X would default to enabled unless the
> the flag is present in either TRUE or FALSE state. And perhaps the tooltip
> on Split and Data/pkt c
"Informed choices". I appreciate the humor.many ops have no idea what's
supposed to work
What I was referring to though was a flag that is "known" to be true. Perhaps
for both for split and data/pkt. WSJT-X would default to enabled unless the
the flag is present in either TRUE or FALS
Hi Mike,
although it sounds attractive I think it will not work. There are too
many partial rig emulations out there to be sure if all advertized
features really work. The whole point of settings is for the user to
make informed choices based on their knowledge of their equipment, and
how the
Bill..maybe WSJT-X could use the availability of the "rig_set_split" to
enable/disable the Rig split option?
And what do you think about adding a flag in hamlib for whether or not Data/Pkt
is supported for a rig so that could be enabled/disabled?
Mike W9MDB
On Friday, July 17, 2020, 0
25018 AMSAT-UK FUNcube Dongle Pro+ 20200112.0
Beta RIG_MODEL_FUNCUBEDONGLEPLUS
WSJT-X 2.2.2 works fine in FT8 mode, including changing bands, but with
some notes:
* I altered the main settings rather than create a new configuration,
by selecting the Funcube in t
Hello Mike,
I work since some years only with YAESU FT-920, FT-857 and FT-817
without any probloems.
Many Thanks for your and yours team work.
73, gl de Hans, DL8ARJ
-Ursprüngliche Nachricht-
Von: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Gesendet: Donnersta
33 matches
Mail list logo
