Joe Taylor kirjoitti 11.6.2020 klo 22.18:
Hi Saku,
OG55W is not a standard callsign. Not a good idea to use that with
FT4/FT8/MSK144 in a contest.
-- Joe, K1JT
Thanks Joe !
After night sleep I remember seeing this before. Was it even in user
manual at the time special callsigns
Can we change the rig selection where it varies between Serial/Network to just
be a single "Device" ?
Then use the same tooltip for Network but add com port info too.
All devices are now capable of supporting network-based serial devices so the
"old" way is obsolete. Some are network-only but
With the release of the enhanced wsprd decoder, I have published version
2.9g of my 'wsprdaemon' system (http://wsprdaemon.org/) and upgraded some
of the 25+ WD sites to run it.
In addition to running wsprd 2.2.1, wsprdaemon can run both that new wsprd
and old wsprd 2.1.x and compare the number
Hi Saku,
OG55W is not a standard callsign. Not a good idea to use that with
FT4/FT8/MSK144 in a contest.
-- Joe, K1JT
On 6/11/2020 2:13 PM, Saku wrote:
Hi!
This may be reported but just found out in NAC 50MHz contest:
EU VHF mode set.
Station calling cq: CQ TEST OG55W
Qso
Tom, are you starting WSJT-X from N1MM or are you starting from WSJT-X
first before you open N1MM? Once N1MM is set up, you can start WSJT-X
by this sequence: Open N1MM+ Logger > Window > Load WSTX-X/JTDX. My
guess is you have missed something in the Set-up of N1MM+ Logger. It
took me
On 11/06/2020 20:06, Mark Spencer wrote:
Hi.
Thanks for all the efforts that the dev team has put into the latest
version of WSJT-X. I have started doing my pre June VHF contest
preparations and noted some odd behaviour at times when using CAT
control with one of my Icom 706MkiiG's. When
It’s been fixed.
Mike w9mdb
Sent from my iPhone
> On Jun 11, 2020, at 2:11 PM, Mark Spencer wrote:
>
>
> Hi.
>
> Thanks for all the efforts that the dev team has put into the latest version
> of WSJT-X. I have started doing my pre June VHF contest preparations and
> noted some odd
Hi.
Thanks for all the efforts that the dev team has put into the latest
version of WSJT-X. I have started doing my pre June VHF contest
preparations and noted some odd behaviour at times when using CAT control
with one of my Icom 706MkiiG's.When switching between 50 Mhz and 144
and 432 Mhz,
Hi Tim
I have made a shotcut and it's looking this way:
C:\WSJT\wsjtx\bin\wsjtx.exe -stylesheet :/qdarkstyle/style.qss
73 de Michael 5p1kzx
Den 11-06-2020 kl. 12:19 skrev Timothy Nichols via wsjt-devel:
-Original Message-
From: Timothy Nichols
To: wsjt-devel@lists.sourceforge.net
Hi!
This may be reported but just found out in NAC 50MHz contest:
EU VHF mode set.
Station calling cq: CQ TEST OG55W
Qso does not initiate with double click in Band activity window line.
Neither with double click in companion program (UDP initiate).
Only way is to enter OG55W to DX call,
Timothy,
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.1.html#DARK_STYLE
If the lines wrap, enlarge the web browser window.
73
Bill
G4WJS.
On 11/06/2020 11:19, Timothy Nichols via wsjt-devel wrote:
-Original Message-
From: Timothy Nichols
To:
-Original Message-
From: Timothy Nichols
To: wsjt-devel@lists.sourceforge.net
Sent: Wed, Jun 10, 2020 1:37 pm
Subject: Fwd: Can't get Darkstyle to function
I did not have a space there (in the manual there is a carriage return between
"stylesheet" and : , so it's hard to tell there ia
I have done this before for a long time with a FT-1000MP, and I have never had
any problems. At this particular club we also have a station no. 2, with a
Yaesu FT-1000 Mark V, and the combo WSJT-X in one of the CAT ports from
Microham router and N1MM+ on the other works, even the Mark V is not
I would think the problem will creep in with non-addressable VFOs.
So if one is trying to read VFOA and the other VFOB (like in split mode) then
VFOs can get confused...
This sequence is not guaranteed to be atomic
S VFOAfS VFOBf
The other app could come in between the S/f commands and switch
Mike,
the microHAM uRouter application provides two sets of virtual serial
ports per rig. I have been using this facility with issues for many
Years. Proper arbitration of CAT commands is provided. Obviously
conflicting commands cannot be reconciled, but control from two
applications is
Title: Re: [wsjt-devel] WSJT-X 2.2.1 GA, Hamlib error with FTdx3000 and Microham II router
Mike,
MicroKEYER III here (uses the same Router Software as MK II)
works perfect, by using:
COM14: JTDX
COM15: WSJT-X
or
COM14: WSJT-X or JTDX
COM15: Flrig
or, a little bit strange, but
COM14:
Reading the documentation it's implied and refers to a "control channel". The
thing just does a passthru so I don't know how it could possibly share the rig
with CAT control. That's likely why he got a bus collision error. I also
can't find a single youtube video of anybody doing CAT control
On 11/06/2020 12:36, Black Michael via wsjt-devel wrote:
You can't have two programs doing CAT control to the MKII at the same
time.
Mike,
that's not correct. The microHAM uRouter provides two sets of COM ports
per radio.
73
Bill
G4WJS.
___
You can't have two programs doing CAT control to the MKII at the same time.
If you're interested I can post a video of how to configure N1MM and WSJT-X to
work together. But it requires three more programs. #1 FLRig#2 rigctlcom
(comes with WSJT-X)#3 Virtual serial port software like com0com or
Portmon from Sysinternals (part of Microsoft) may tell you what's going on
with the com ports, assuming Windows OS, and that it picks up the virtual ones.
Alan G0TLK, sent from my mobile device
On 11 June 2020 07:59:53 Tom Ramberg via wsjt-devel
wrote:
That is: The radio is connected to the
That is: The radio is connected to the computer via the MKII. The COM ports I
refer to are all virtual ports created in Microham's router. As I stated in my
other response, the aim is to keep it as simple as possible for the new hams in
my club. They use N1MM+ for genaral logging, and that is
No. That's it.
73
Tom OH6VDA
Sendt fra min iPad Air 2
> 10. jun. 2020 kl. 16:20 skrev Bill Somerville :
>
>
> On 10/06/2020 14:11, Bill Somerville wrote:
>> On 10/06/2020 14:01, Tom Ramberg wrote:
>>> First it happens when I set the Com port In the radio tab WSJT-X settings
>>> (in this
The rig is Yaesu FTdx3000 connected with a Microham II keyer. I suppose that is
what I am trying, yes. And when I disconnect N1MM+, WSJT-X works fine with both
COM4 and COM5.
The problem is that I am trying to set this up in a club, where most of the
users are new licencees, and I want to make
23 matches
Mail list logo
