ot sufficient for this - there will be implementation-specific
> details that are important too.
>
> From what I understood the point here was that validation would not be
> locked down to just one 'supplier' of keys. Otherwise - what's the point of
> having that URL
One Time Passwords are something that many websites use now (with support
of authentication/password apps like Google Authenticator, Microsoft
Authenticator, 1password, etc.). They work by have a "Time Based One Type
Password" that follows the methods outlined in RFC6238 (and predecessor
RFCs).
Th
Hi Lance, your contacts should be showing up in your regular log file; in
addition, there's a file, FoxQSO.txt, that keeps a record of sent and
received communications while in Fox mode.
-Brian N9ADG
On Mon, Oct 7, 2024 at 2:16 PM Lance Collister, W7GJ via wsjt-devel <
wsjt-devel@lists.sourceforg
Hi Andy; can you please help me understand the circumstances better?
Under “normal” f/h operation, the hound calls with a grid. WSJT-X in fox mode
can queue a caller with a grid. WSJT-X in fox mode doesn’t queue
non-grid-supplying callers.
If the “fox” replied to a signal report message as the
Greetings; can you describe what mode you are using? If you left it going for a
few days without deciding any signals (e.g. with no antenna) same behavior?
What radio and interface to the radio? Any other information you could share
would be most appreciated.
Thanks!
-Brian N9ADG
Sent via iP
Or, pick words that don’t have a meaning yet. Like call it “TX Optimizan” with choices like “none” “active” and “emulate” . I am joking. -Brian N9ADGSent via iPhoneOn May 8, 2023, at 11:18 AM, John Kludt via wsjt-devel wrote:Michael,My vote is we have beat this issue to death several times over.
Greetings; if you've compiled the current software, you'll probably note
that doing so generates quite a few separate applications. Two of these
applications are wsjtx and jt9 -- wsjtx *is* the UI on top of the jt9
application.
-Brian N9ADG
On Wed, Apr 26, 2023 at 4:56 AM Daniel Uppström via wsj
Hi Alex and and Olof; I too have been building M1-specific binaries (for
2.6.0 rc-1).
There certainly are some caveats in building specifically for M1 chips at
this time, starting with specifying some of the CMake variables required:
CMAKE_OSX_ARCHITECTURES -> arm64 (this chooses M1-specific bina
Hi Derek:
Perhaps others will join in, however, the optimizations that you're talking
about doing might be best to accomplish after you have correct packet
parsing working?
Regarding the scanning-packet aspect, my recollection is that the C#
libraries are rich in their ability to scan byte buffer
Hi John -- congrats on your group's initiative and success with this
ambitious project. While it looks like you've mined the wsjt-x development
email alias for interest, there are at least a couple of other groups that
might also have an interest in coming up with a common way to do this:
1) The Q
I had something similar occur on a not-new Dell E6420 (I5 curiously enough)
laptop; what it turned out to be is the system clock was 'slipping' by
various random amounts, second to second. The error would accumulate, no
decodes, until it had slipped by 15 seconds, and then decodes would happen
agai
at 9:20 AM Bill Somerville
wrote:
> On 12/12/2018 17:00, Brian Moran wrote:
>
> Is there a way, once a new foreground / background color has been set for
> some text snippets via UDP Highlight Callsign packet for them ALL to be
> cleared?
>
> Hi Brian,
>
> yes, a
Is there a way, once a new foreground / background color has been set for
some text snippets via UDP Highlight Callsign packet for them ALL to be
cleared?
I'm thinking of the instance where perhaps a callsign is colored to reflect
a particular status during a contest or operation, but then the con
Is there a way, once a new foreground / background color has been set for
some text snippets via UDP Highlight Callsign packet for them ALL to be
cleared?
I'm thinking of the instance where perhaps a callsign is colored to reflect
a particular status during a contest or operation, but then the con
WSJT-X represents current state of the art for weak signals in Amateur
Radio communications, but using 'email as a bug database' to keep track of
issues decidedly does NOT represent the state of the art in anything.
Asking everyone to read all of the emails to see if their issue is
represented befo
ges to update your speedy internal table.
-Brian N9ADG
On Tue, Nov 20, 2018 at 11:40 AM Bill Somerville wrote:
>
> On 20/11/2018 19:25, Brian Moran wrote:
> > Hi Bill! You say time critical -- how many milliseconds are currently
> > available to look up the up-to-40-calls and re
Hi Bill! You say time critical -- how many milliseconds are currently
available to look up the up-to-40-calls and render a 'worked_before'
status for each of them?
On Tue, Nov 20, 2018 at 11:09 AM Bill Somerville wrote:
>
> On 20/11/2018 18:06, Brian Moran wrote:
> > In
In the ARRL RTTY Roundup, the rules say work stations once per band,
regardless of mode. This means those stations using both RTTY and FT8
modes in the same contest will have to check callsigns in BOTH MODES
to know what to work efficiently.
Will there be a means supported to do an 'outcall' to a
I'll try to carve out some time this summer to work on a means to
automatically check for the latest program version on the wsjt-x
website. I talked about it last fall, but got really busy. I'm really
not any less busy now, but it's time to get that 'feature' going.
-Brian N9ADG
On Tue, Jul 10,
Hi Michael; will this allow directed ‘fishing’ for contacts where a station can
send a message to another to prompt the completion dialog?
-Brian N9ADG
Sent via iPhone
> On Jun 9, 2018, at 11:51 AM, Black Michael via wsjt-devel
> wrote:
>
> Numerous times have had people response with sig r
Ted, here's what I do to use N1MM Logger+ with wsjt-x:
I created a second, different shortcut to the N1MM Logger+ program that
starts N1MM Logger+ with a different .ini file, one that does NOT talk to
the radio. N1MM is really only used for logging, and the frequency and mode
information is provid
Here's a link to a project that has Amateur Radio built into an autonomous
vehicle on the high seas.
http://www.jrfarc.org/hf-voyager/
It's possible to work the vehicle using FT8, as described in this note on
the Elecraft reflector by Jim, K9YC:
https://marc.info/?l=elecraft&m=152036765825717&w=
ication could be written
> to map between WSJT-X "Logging ADIF" messages and N1MM+ UDP log messages.
> Your Python script for NMEA geo-location could perhaps serve double duty?
>
> 73
> Bill
> G4WJS.
>
>
> On 04/02/2018 06:33, Brian Moran wrote:
>
> When clean-
The Minnesota QSO Party folks added FT8 for their event which occurred last
weekend. I asked Mark, WA0MHJ, how that turned out:
Hello Brian,
Well this is still an on-going experiment.
I have processed through 170 entrants so far. In those 170, we have 22 who
have also sent ADIF files for FT-8 c
is implemented
similarly to the free text entry -- when editing is deemed 'finished', the
message to change the grid is sent.
Attached is a diff.
On Sat, Feb 3, 2018 at 3:31 PM, Bill Somerville
wrote:
> Hi Brian,
>
> some comments in line below.
>
> On 03/02/2018 21:
be the case that the own-grid
squares of each station are used if provided (since they don't need to be
in a QSO as part of the IGC rules), but I've not tested that.
On Sat, Feb 3, 2018 at 10:00 AM, Bill Somerville
wrote:
> On 03/02/2018 17:48, Brian Moran wrote:
>
>> Hi Fo
Hi Folks, when we were on the boat on the way to Mellish Reef we operated
/MM. Adding the appropriate grid square was just something we had to
remember to do, and didn't require checking too often as we were only
proceeding at 8 kt.
In a vehicle, grid might need to be updated more frequenty, like
I'm finding that the following is NOT true in 1.8.x and development
branches:
"WSJT-X sends this status message when ..."
- When the DE call or grid changes (currently when the settings are exited)
It does *not *appear to emit a status message when the grid is changed in
the configuration dialog,
OK, but to me that seems slightly at (conceptual) odds to the
always-short-circuited pending DXpedition mode, which so far uses RR73
exclusively.
On Mon, Jan 29, 2018 at 12:22 PM, Bill Somerville
wrote:
> On 29/01/2018 20:10, Brian Moran wrote:
>
>> Is it envisioned that the RR73
Is it envisioned that the RR73 mode will be promoted into a setting that is
preserved as part of the configuration in the future (depending on the
preconditions of not having a type2 callsign)?
If it was a setting, would it move to the configuration tab, would it stay
a double-click option on tx4,
It seems like you could help yourself in this instance. ALL.TXT contains
information like this:
2017-12-20 21:29 14.074 MHz FT8
212915 -12 0.0 570 ~ N5YYF W2GW FN30
212915 -6 0.1 700 ~ K1PL NZ2X -14
212915 -19 0.1 800 ~ CQ KB8BIP EM88
212915 -7 0.3 1127 ~ PY6HD W4BCG EM65
212915 -2
So, back to the practical matter of getting the time right faced with lack
of WWV/WWVH, no GPS NMEA sentences to plunder, no superlative chronometer
to reference.
Here's something that you can try --- turn off time sync on your computer.
Stop any WSJTX app you have running. Go into control panel,
Or wwv/wwvh depending. on Mellish Reef we lost time timeserver sync for a
recalcitrant laptop, syncd it this way. We otherwise used an NTP server driven
from a cheap GPS on our reef network.
Sent via iPhone
> On Dec 7, 2017, at 12:23 PM, Ria Jairam wrote:
>
> I think this was discussed before
I haven't seen the callsign field change but HAVE seen the report field change
to the value for the next caller.
Not sure of a repro case, however I imagine a careful exam of all.txt could
yield examples.
Sent via iPhone
> On Nov 26, 2017, at 2:24 PM, Bill Somerville wrote:
>
>> On 26/11/
Hi everyone, I was one of the VK9MA team members. During one of four boat
days to Mellish Reef, I added into wsjt-x the ability to broadcast the ADIF
records via UDP to N1MM Logger+ as they were being logged to make it
easier for us; I can supply a context diff or I guess I could do an SVN
branch.
35 matches
Mail list logo
