Hey Chris, I've had something similar happen... Basically all stations fail to
decode.
Check your clock. Make sure NTP is synced. I have a Dell laptop that
continuously slips so I force it to resync before I start pulling my hair out.
73's Tim
ae5tc
> On Jul 1, 2018, at 1:22 PM, Chris Getman
To unsubscribe, copy and paste the URL that's listed at the bottom of
this message thread. You'll get a page that you will have to enter your
email address in, then click on the UNSUBSCRIBE button.
Neil, KN3ILZ
On 7/2/2018 7:09 PM, John wrote:
On Tue, 03 Jul 2018 09:04:04 +1000, Ed Stokes
Grant,
I am thinking that it is reasonable interpretation to consider CQ message, i.e.
“CQ, CQ EU, CQ NA, CQ AS…..” is our “paging message” or “congestion control
message” to allow certain group to send their access message such as “KH1/KH7Z
JA5AEA PM95” at access channel i.e. above 1,000Hz~4,0
I'm not sure what good this would do. I exchanged reports with the
operation twice on 17M and once on 20M. One of the 17M contacts did not
result in the RR73, just an exchange of signal reports. Of course, that
exchange did not end up in the Club Log, which means it was not a valid
QSO. So, I
List Members,
I have done extensive internet searches for
my station to make it operational with the
following hardware/software, but no search
has found an answer. Hopefully this list can
help.
I am using the WSJT-X v1.9.1, a Yeasu FT-857D,
a Navigator modem, Navigator cable set, Dell
laptop 3.0
On the Main screen, the Tx<---Rx and Rx<---Tx arrows seem backwards. Set
Tx=1810 and Rx=1409, press Rx<---Tx and you get both Tx and Rx at 1810.
I'm reading Rx<---Tx as change the Tx frequency to the Rx frequency, move 1810
to 1409 in this example.
WSJT-X 1.9.1 r8747 the GA release. Normal set u
On 03/07/2018 00:18, kb...@neo.rr.com wrote:
---
WSJT-X
---
Rig failure
---
Hamlib error: Invalid configuration while opening connection to rig
---
OK
---
Hi OM,
there is som
On Tue, 03 Jul 2018 09:04:04 +1000, Ed Stokes wrote:
Thanks, Joe, I’ll try that next time.
73 Ed
On Jul 2, 2018, at 11:10 AM, Joe Taylor wrote:
On 7/2/2018 10:13 AM, Ed Stokes wrote:
running 1.9.1 on a Mac Mini
generally double clicking on DX station works as expected: call sign
chan
here it is
Bill Somerville wrote:
> On 02/07/2018 23:26, kb...@neo.rr.com wrote:
> > the error I get is hamlib error.
>
> OM,
>
> that is not the full error message. You can grab the full message by
> hitting CTRL+C while the error message box has focus, the message text
> is copied to
To the fellow trying to use the FTDX3000 download the software Omnirig it has
the FTDX3000 as a rig choice then in the setup of wsjtx select Omnirig. I used
similar setup with a Flex 3000 and it worked with it. Hope your able to get
things going. 73 Morris WA4MIT
On Monday, July 2, 2018,
Thanks, Joe, I’ll try that next time.
73 Ed
> On Jul 2, 2018, at 11:10 AM, Joe Taylor wrote:
>
> On 7/2/2018 10:13 AM, Ed Stokes wrote:
>> running 1.9.1 on a Mac Mini
>> generally double clicking on DX station works as expected: call sign
>> changes and transmit is enabled.
>> sometimes, th
On 02/07/2018 23:26, kb...@neo.rr.com wrote:
the error I get is hamlib error.
OM,
that is not the full error message. You can grab the full message by
hitting CTRL+C while the error message box has focus, the message text
is copied to the clipboard so you can easily paste it into a reply to
sorry I was short with you my mail came back undeliverable probably because I
sent it the same time i tried to join the group the yahoo group referred me
here. the error I get is hamlib error. I even belong to yaesu 3000 users group
no help there that I could find. someone must be using the s
Everyone,
The thread hi-jacking has been interesting but time to bring it back to my
original question perhaps please?
Take,
Yes - the problem with varying power is I might hear him CQ when he
transmits with only one channel but when -14dB of power reduction results
from 5 responses I c
In hound mode, would it be a good idea to use another watchdog timer to
trigger on received messages from the DX call, perhaps started with a 5 min
period (after first call) and reset to a longer timeout (15min?) on decoded
messages from the DX ? Additional reset by a longer idle period (say
30-60m
At least with this current dxpedition, I suggest you at least tentatively log
contacts as soon as you have received a report from the fox and have sent yours.
I had been trying to contact KH1/KH7Z on 20m but the only success I had were 2
'busted' sequences. I never saw a RR73 for either of them
I let it run six attempts then I stop it. Since the RR73 is incoming from
the Fox and I have all the details I need for entry into my log, I log it,
then wait for the Club Log verification. If I am in the fox log on the
that band I will upload my log.
On Mon, Jul 2, 2018 at 3:07 AM, Charles Suck
I've been watching them (KH1/KH7Z) work various stations on 14 Mhz for the
last 30 Minutes or so. I have yet to see a single CQ from them.
73
Mark S
VE7AFZ
On Mon, Jul 2, 2018 at 7:38 AM, Bill Turner via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> I have seen kh7z answering stations
In the case you give as long as you have the prior decode of them you would
just double-click it and that solves the problem as you have actually received
them before.
I assume you would still have them in your Band Activity window.
de Mike W9MDB
On Monday, July 2, 2018, 8:24:55 AM CDT, R
Hi OM
It was not a wise crack answer - WHAT ERROR ARE YOU GETTING ?
Have scanned the mail for 6 months for your call - it is not there - so since I
can’t find your earlier mail perhaps others as may have missed your mail.
There is some info on the general wsjt mailing list at:
https://groups
On 7/2/2018 10:13 AM, Ed Stokes wrote:
running 1.9.1 on a Mac Mini
generally double clicking on DX station works as expected: call sign changes
and transmit is enabled.
sometimes, the software just keeps transmitting to the previous station.
It doesn’t matter if you turn off enable or halt
well my mail must have gotten lost. and wisecrack answers like can't read my
mind turn me off. I have the latest version 1.9.1 as far as I know run windows
10 on a hp I-5 and run AC log with CAT control mmty direct fsk and a multitude
of other digital modes. as I said I need some parameters for
I have seen kh7z answering stations on 20m last night at -7 to -20 strength.
Only saw one CQ at 11pm local in NC.
Sent from Yahoo Mail on Android
On Mon, Jul 2, 2018 at 9:24 AM, Russ wrote:
--
Check out the vibra
See the details at the bottom of every mail
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
It allows you to manage your subscriptions yourself - no-one else can do it.
It may be worthwhile (have checked and you have never posted with that call
running 1.9.1 on a Mac Mini
generally double clicking on DX station works as expected: call sign changes
and transmit is enabled.
sometimes, the software just keeps transmitting to the previous station.
It doesn’t matter if you turn off enable or halt tx, the software just won’t
change calls
I originally joined this group to get the exact parameters for my yaesu 3000.
first of all it isn't listed in the drop down menu, I tried using the 5000
instead and set everything I could find and it came back error so since I can't
seem to get this information and all the mails I see are not of
Hello all. Maybe I am sticking my nose where it does not belong, because I
have not used or studied this fox/hound business. But when I see many stations
advocating to forcefully block calling a station “blind”, I have to think that
some care is needed. I have a lot of experience with FT8 on
One question maybe some could answer is if they saw a Fox CQ and the Hound
responses but never saw the Fox secondary messages. You'd likely see several
repeats from the hounds that don't see the reduced power signal.
de Mike W9MDB
On Monday, July 2, 2018, 12:43:01 AM CDT, Tsutsumi Takeh
Hi All
20m conditions were a bit better today and I finally managed to work Baker
with 100W, lots of feeder loss and a sloping dipole.
The problem I had was, after receiving my report from KH7Z, I failed to
receive RR73. Thanks to Bill's advice to start over again (TX1 message), on
the 4th
29 matches
Mail list logo
