then, like always -- use the right tool for the right job?
On Wed, Sep 15, 2021 at 11:12 AM Jim Brown via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> On 9/14/2021 11:43 PM, Laurie, VK3AMA via wsjt-devel wrote:
> > That has been my experience as well. On the surface JTDX offers a
> > g
ICOM does call their VFOs like this:
If there is a single RX in the rig, like the 7300, you have VFO A/B so you
have two VFO slots.
if you have two receivers, Main and Sub are used. And Both Main and Sub
have VFO A and B (like the 9700) so you have four VFO slots.
On Sun, Apr 4, 2021 at 6:35 PM
mine is still available if you need it. Be sure to mail me before so that
the USB connection is available since we only use ether here
On Wed, 3 Mar 2021, 23:36 Black Michael via wsjt-devel, <
wsjt-devel@lists.sourceforge.net> wrote:
> Anybody with an IC-9700 that wants to volunteer for some test
I have read the whole story. In defense for what Dave stated -- note that I
am not a native speaker --
I just was reading lack of. missing, imperfection.
Not FAULT FAILURE SHORTCOMING etc.
Below is a definition of deficiency. I don't think that Dave has *any*
reason to state that wsjtx is a failu
wholeheartedly agree Tom
On Tue, 9 Feb 2021, 13:31 tom, wrote:
> Against it.
>
> There are too many callsigns being issued for numerous reasons -
> anniversaries / covid / 1st etc. Having the software check (and keep
> having to get internal lists updates from other sites) is not really
> pract
I back Rud on this: the issue though is that if something else (for
whatever reason) calls wsprd, imho it should be better to handle this
to be on the safe side?
R.
On Wed, Dec 2, 2020 at 11:05 PM Bill Somerville
wrote:
> On 02/12/2020 21:55, Rud Merriam wrote:
>
> Hi Bill,
>
> I realize that
sudo remove tab2
On Wed, 29 Jul 2020, 09:36 Neil Zampella, wrote:
> I have no problem with removing that for the next version. Would save a
> lot of time by you and the other developers during contests answering
> questions about why something was not logged properly. Tab 1 gives
> the
Not sure if the 785x works the same but if so... all is online here
Mike.
On Sun, Jun 14, 2020 at 5:36 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hi Jon,
> Would you be willing to let me connect up to your computer and do some
> debugging?
> I think we may al
>Your name and call??
the name would be in the from line and I was not aware of the need for a
call sign but hey..
Roeland Jansen, PA3MET
>Starting with WSJT-X v2.2.0, reception of one of the specialized EU VHF
>Contest messages will cause trigger a message asking whether you should
&
regarding the EU VHF contest mode:
it appears that even if it's unchecked the software does switch to contest
mode. when you happen to
get a reply (?) or klick on someone who uses that mode. I think that is
fine and fair enough.
However, it stays in that mode even when it was initially directed no
>
> What is *CI-V Transceive*?
>
> All Icom rigs equipped with CI-V offers the option of enabling/disabling *CI-V
> transceive*. What is this?
>
> With CI-V Transceive set to *on*, two things happen:
>
>- the rigs transmits data over the bus when frequency or mode changes;
>- the rig reacts
g and
linu/unlink settings.
above works for apple stuff, linux and windows.
On Sat, Apr 11, 2020 at 3:21 PM Roeland Jansen
wrote:
>
> first of all -- update to v1.30 which is the latest f/w that I know of.
>
>
> Secondly,
>
> CIV:
>
> CIV baud rate
>
>
first of all -- update to v1.30 which is the latest f/w that I know of.
Secondly,
CIV:
CIV baud rate
On Sat, 11 Apr 2020, 14:34 Frank Birch, wrote:
> Ensure the Baud rates are the same. I’m able to run at highest.
> Are you connecting direct to the USB port - no hub.
> Stay safe, be well
> 7
for the shits and giggles
just took the liberty to config a windows laptop downstairs, connected via
rsba1 to one of my rigs, the 7851.
The 7851 is available over te lan and is also controlled over it's USB port
with rigctld.
wsjtx is configured to talk to net rigcontrol.
At the rig's end a linu
what rig type did
On Mon, Nov 25, 2019 at 9:45 PM Jon Anhold wrote:
> I'm not sure why yet, but when I upgrade to 2.1.1, I get the following
> error on startup:
>
> [image: image.png]
>
> 73 de KM8V
>
> On Mon, Nov 25, 2019 at 1:43 PM Joe Taylor wrote:
>
>> The WSJT Development Group is pleased
as said, it is is in the logging directory. be sure you don't hide file
extensions under Windows
On Wed, 30 Oct 2019, 15:49 Carl Buehler, wrote:
> WSJT-X 2.1.0 logging still a concern. The wsjtx text log continues to
> save contacts. I downloaded and installed the program but no .adi or
> simil
I am with Mike on this, been there, done that. Really annoying.
On Mon, 5 Aug 2019, 18:13 Black Michael via wsjt-devel, <
wsjt-devel@lists.sourceforge.net> wrote:
> If you install 2.1.0 over 2.0.0 for example you end up with two listings
> in the App manager.
> If you try to uninstall 2.0.0 it fa
hi,
the following is something I have seen since 2016 or so and while I always
fix it by hand, it makes me wonder if it's a bug, feature or otherwise.
- I have wsjt-x started and both rx and tx point to the pcm2901 codec of
the icom transceiver(s). I decode just fine etc. However, at first
transmis
I sometimes just used to forget. I have made a habit to keep the TX freq
now.
On Sun, Jul 28, 2019 at 6:20 PM Claude Frantz
wrote:
> On 7/28/19 6:00 PM, Ron WV4P wrote:
>
> Hi Ron, Andy & all,
>
> > Way to much credit has been given to the ability of Operators. Hold TX
> > should be checked by
I have thee configs with different codec/civ/etc (9700, 7300, 7851) myself
and all three required a restart of wsjtx. If that is the same as with
this... I would not thing the option would be too good to use.
On Tue, 23 Jul 2019, 05:22 Rich Zwirko - K1HTV, wrote:
> Your idea of switching from t
that certainly does. a contest is in cw easier than ragchewining, esp at
high speed as most of the things to exchange are 'known values'.
On Mon, Jul 22, 2019 at 11:18 PM Larry B. via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> However, 59 or 599 serves the human brain as a very good
> John
>
> On Mon, Jul 22, 2019 at 10:07 AM Roeland Jansen <
> roeland.janse...@gmail.com> wrote:
>
>>
>> contest stations generally only want valid contacts (according to the
>> contest rules) to prevent
>> a penalty. That also is a thing.
>>
>
contest stations generally only want valid contacts (according to the
contest rules) to prevent
a penalty. That also is a thing.
On Mon, Jul 22, 2019 at 2:31 PM Ryan Tourge wrote:
> A bit prissy to exclude a station that lacks a signal report. You both
> ack'd each other. obviously the call took
stical analysis. See the attached graphic.
>
> Not perfect, but way better and way cheaper than most other alternatives,
> especially if stuck away from home. 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 9:16 AM Roeland Jansen
> wrote:
>
>> the issue is not the device b
>
>>
>> Cheers,
>>
>>
>>
>> Neal
>>
>> N6YFM
>>
>>
>>
>> On Wed, Jun 26, 2019, 3:16 AM
>> wrote:
>>
>> Send wsjt-devel mailing list submissions to
>> wsjt-devel@lists.sourceforge.net
>>
&
the tracks. this group is NOK
I know it's a bastard operator from hell solution but sometimes forcing
people helps.
and it's just an idea... just an idea
On Wed, Jun 26, 2019 at 12:20 PM Bill Somerville
wrote:
> On 26/06/2019 10:55, Roeland Jansen wrote:
> > I did not look at
I did not look at the patches Mike sent but:
https://time.is/
gives you how good/bad the time is. If you start up: do check like this
and refuse to go on if the timeskew is too large.
Add a link how to fix in the message and you force people to fix it.
(not that people read notices)
just my b
set rig TX power to 100%, connect a
> dummy load, then reduce audio drive level so power meter reads less than
> 100% in the middle of the passband?
>
> Tom M0LTE
>
> On Fri, 14 Jun 2019 at 07:39, Roeland Jansen
> wrote:
>
>> "However, the action of AL
"However, the action of ALC meter depends on balance between the modulation
level setting of your transceiver and the audio output level of your PC.
Please adjust them with seeing the ALC meter.
As you already know, if the ALC meter indicates within the ALC zone, there
is no problem.
Best Regard
so we agree that we should follow the manuals of the manufacturers?
On Wed, Jun 12, 2019 at 4:56 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> I finally got a reply from Kenwood for the TS-990S -- this quite likely
> applies to all the Kenwood's with the red ALC zon
few exceptions on some rigs with old
> audio setups) coming from computer->soundcard. You adjust the gain in the
> receiver and external soundcard if you have one (Signalink, RigBlaster,
> etc) to limit the power.
> As I recall I've only had one rig where we couldn&
In the *Icom manual* it states, “When operating in the SSB data mode,
adjust the device's output level to be within the *ALC* zone.” So contrary
to the old rule that *ALC*fluctuation is bad, that is not the case with
these new SDR transceivers. (from someone else's view)
The ALC zone is in this c
I own a 7300, 7851 and 9700. The ALC just deflects a small bit to have 100%
power -- just tried.
When it comes to side skirts and double decodes -- if you are too
enthousiastic and the ALC is way up, you will indeed see these issues.
The manually states on all the TRX (different wording)
Transm
hi all,
I did mention this briefly a few days ago.
- The build platform is suse leap 15
- issue is active with wsjtx-2.01/linux (someone else built it for suse)
- issue is active with wsjtx-2.1.0rc5/linux (built myself)
- no issue with both versions in windows 10 pro
I believe it might be a
hi Bill,
thanks about the runaway timer... and I'll see if I can find the project
page. Like Chris, I must then have overlooked it Bill.
I built 2.01 myself so I assume that this won't be an issue either.
RFI is not the issue I suppose -- the windows port works fine, under linux
it goes wrong; e
someone built 2.01 for opensuse and a few things happen there
a) after transmit most of the time, if not all the time, the RX device is
lost and is set to internal mic
b) I see runaway tx timer (or something along that text).
I built the stuff myself with the same issues. So it would be apprecia
MDB
>
>
>
> On Tuesday, April 23, 2019, 8:34:12 AM CDT, Roeland Jansen <
> roeland.janse...@gmail.com> wrote:
>
>
> hi Mike,
>
> sort of. I know I can put the branch I have at the same place but the
> build instructions of wsjt-x talk a bout specific patches tha
vel@lists.sourceforge.net> wrote:
> If you mean the IC-9700 specifically that has been incorporated in the 4.0
> branch of hamlib and should appear in the next release of WSJT-X.
>
> de Mike W9MDB
>
>
>
> On Tuesday, April 23, 2019, 7:50:14 AM CDT, Roeland Jansen <
> roeland
In the build instructions there have been notes about hamlib not having the
patches
merged into their code yet.
Now, we're seeing hamlib v4.x ; Is that still the case that patches are not
merged?
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.n
On Wed, Jun 1, 2016 at 3:15 PM, Walter Fey wrote:
> OpenSUSE Leap 42.1 with Gnome does not show this behavior.
> So it seems to be a KDE (Phonon) problem.
>
>
if we can get a finger on what happens with phonon we could see if we can
getr rid of the work-arounds.
I may have a few strings to pull
On Tue, May 31, 2016 at 10:24 PM, Walter Fey wrote:
> Hallo,
>
> The same issue comes up on a Fedora 23 installation with KDE.
> After the first transmission pulseaudio is switching the input to the
> first audio device instead of the one selected by WSJT-X. This can
> easily be corrected with pa
On Mon, May 30, 2016 at 12:09 PM, Walter Fey wrote:
> Hallo Roeland,
>
> The problem comes up when you have more than one audio device connected
> to your openSUSE system.
> The RX of WSJTX is switched to the first audio device after the first
> transmission. You can switch the input back to the
On Tue, May 31, 2016 at 1:49 AM, Bill Somerville
wrote:
> On 30/05/2016 15:00, Roeland Jansen wrote:
>
> I will build a SUSE VM and see if I can reproduce the issue, if I can I
>> will try and track down what is happening and if we can work around it.
>>
>
> that w
Bill,
On Mon, May 30, 2016 at 1:14 PM, Bill Somerville
wrote:
> On 30/05/2016 11:56, Roeland Jansen wrote:
> > To me it sounds like it's a bug, athough I am not sure how it happens.
>
> Hi Roeland,
>
> it is surely a defect but in which software?
>
>
I don&#
On Mon, May 30, 2016 at 12:09 PM, Walter Fey wrote:
> Hallo Roeland,
>
> The problem comes up when you have more than one audio device connected
> to your openSUSE system.
> The RX of WSJTX is switched to the first audio device after the first
> transmission. You can switch the input back to the
hi Bill,
>
> how is your rig connected to your laptop? Does the rig go to Tx mode and
> return to Rx mode when it should? Is this only with WSPR Tx or are other
> modes causing the same issues?
>
it's connected via USB. Both CAT and SOUND. They are an IC7100 and/or 7600.
Both show the same.
The
all,
in a recent chat with Michael Black, about wsjt and linux I decided to ask
the question here.
I am running opensuse leap 42.1 on a moderately slow laptop.
The version taken is wsjtx-1.6.0.r6263-1.21.x86_64
but the 'official builds' on the website also exhibits the
same issue.
If I start ws
47 matches
Mail list logo
