Date   

locked Re: 60 METERS #band

 

Thanks for the reply. Appreciate it. 73's Dave

On 6/17/2022 4:42 PM, K4NDN wrote:
On WSJT-X
Click FILES, SETTINGS then click the FREQUENCIES Tab, in the body of the
frequency modes regions box RIGHT CLICK and select INSERT then enter the
appropriate information. 60 is 5.357 in USA.
K4NDN

On Fri, Jun 17, 2022 at 5:32 PM Dave Garber<ve3wej@...> wrote:

Did it not save when you upgraded. Or did you uninstall it? Then reinstall.

I am not home right now so i cant look it up but maybe frequency reset
might bring them in or wait for the knowledgeable to answer

sent via LG hand held device

On Fri., Jun. 17, 2022, 5:11 p.m. Dave Tucker Nu4N, <
dwtucker19@...>
wrote:

I HAVE THE FREQ''S FREQ'S FOR 60 METRS. I FORGOT HOW TO SET UP 60 IN
WSJT?
THANKS
--
*73'S DAVE NU4N*








--
Eric J Evans
Amateur Radio Operator: K4NDN
Elkton, VA. USA, 22827
Grid: FM08qj
540.335.6178
e.evans1369@...

--
*73'S DAVE NU4N*


locked Re: 60 METERS #band

K4NDN
 

On WSJT-X
Click FILES, SETTINGS then click the FREQUENCIES Tab, in the body of the
frequency modes regions box RIGHT CLICK and select INSERT then enter the
appropriate information. 60 is 5.357 in USA.
K4NDN

On Fri, Jun 17, 2022 at 5:32 PM Dave Garber <ve3wej@...> wrote:

Did it not save when you upgraded. Or did you uninstall it? Then reinstall.

I am not home right now so i cant look it up but maybe frequency reset
might bring them in or wait for the knowledgeable to answer

sent via LG hand held device

On Fri., Jun. 17, 2022, 5:11 p.m. Dave Tucker Nu4N, <
dwtucker19@...>
wrote:

I HAVE THE FREQ''S FREQ'S FOR 60 METRS. I FORGOT HOW TO SET UP 60 IN
WSJT?
THANKS
--
*73'S DAVE NU4N*









--
Eric J Evans
Amateur Radio Operator: K4NDN
Elkton, VA. USA, 22827
Grid: FM08qj
540.335.6178
e.evans1369@...


--
K4NDN


locked Re: 60 METERS #band

Dave Garber
 

Did it not save when you upgraded. Or did you uninstall it? Then reinstall.

I am not home right now so i cant look it up but maybe frequency reset
might bring them in or wait for the knowledgeable to answer

sent via LG hand held device

On Fri., Jun. 17, 2022, 5:11 p.m. Dave Tucker Nu4N, <dwtucker19@...>
wrote:

I HAVE THE FREQ''S FREQ'S FOR 60 METRS. I FORGOT HOW TO SET UP 60 IN WSJT?
THANKS
--
*73'S DAVE NU4N*






locked Re: 2.6.0 video oddity (bug?) #IssueReport

K4NDN
 

Try the ‘high contrast’ option in Windoze 10…works for me..takes some
fiddling but I like it

On Fri, Jun 17, 2022 at 14:40 Dave Corio via groups.io <k1dje=
yahoo.com@groups.io> wrote:

That was it here. Changing from dark mode eliminated the problem.

Still not a major issue, but I hope it might be addressed somewhere down
the road.

2.6.0 still performing well!

Tnx es 73
Dave - K1DJE





--
Eric J Evans
Amateur Radio Operator: K4NDN
Elkton, VA. USA, 22827
Grid: FM08qj
540.335.6178
e.evans1369@...


--
K4NDN


locked 60 METERS #band

 

I HAVE THE FREQ''S FREQ'S FOR 60 METRS. I FORGOT HOW TO SET UP 60 IN WSJT?
THANKS
--
*73'S DAVE NU4N*


locked All is going well here with 2.6.0-rc1 #mainscreen - contest mode #mainscreen

Reino Talarmo
 

If additional buttons are to be added, Contest Mode should be a priority. Lot of quick switching between normal and CM
It would be better if WSJT could switch automatically to contest mode and back again. That is WSJT should always send the >exchange wanted by the other QSO partner and then after the QSO go back to the mode you you prefer. As WSJT can display a >window "Change to xx contestmode" it might as well just switch to that contestmode.
Hi Palle,
There is no bits for a contest "name" in the messages as such and contest specific messages a recognized only by the message construction as some stage of the QSO message exchange. Some of those are very specific e.g. EU VHF contest, but some others have exactly the same message structure. So to find a specific contest by the message is not fool proof.

The second issue is that a non-contester may not want to participate to the contest at all and the contester will assume his participation and will lose points or at least get a NIL.

There can be ongoing various contests at the same time and the automatic "participation" to all of those will disturb contest database.

My vote to the automatic switch to contest mode is NO.

A button for a contester to switch to normal mode and back gets my YES.

73, Reino OH3mA


locked WSJT to ACLOG for FD #logging

KT7AZ
 

I have noticed when manually trying to enter a contact in WSJT-X in FD mode while using N3FJP link, that entering the exchange in small letters gets a bad entry when sending to N3FJP.
N3FJP requires Exchange to be in caps.

I was wondering if you could set the Exchange fields in WSJT-X to convert to caps.

Thanks,
Gary
--
KT7AZ


locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

Carl - WC4H
 

Hello all.

Built it 2.6.0 on my Raspberry Pi 4B without any issues. I like the changes and hope to see a few more. So far everything that I use is working.

73.
Carl - WC4h


locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

Jim Brown
 

Thanks to the team for ongoing work. One comment. Those of us active on 6M have long found the need for a VHF Contest Mode more important than Fox/Hound. It's needed not only during contests, but also when grid expeditions are using it, conditions are highly variable, and stations are in and out in a few minutes. Losing a cycle can mean losing a QSO with a rare grid.

73, Jim K9YC

On 6/16/2022 8:22 AM, Joe wrote:
Dear WSJT-X and MAP65 Users,
We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc1 is ready for download by beta testers.


locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

Pietro Molina
 

Yeah, I think the ghost is for this. Buto old WSJT-X does not list the
ghosts, only the most powerful signal.

Pietro (via Tablet)

Il ven 17 giu 2022, 20:29 Al Groff via groups.io <al.k0vm=
yahoo.com@groups.io> ha scritto:

It could also be caused a power line ( 50 hz in EU) induced AM
modulation. It could be power supply ripple on the RF PA, AC modulating
the TX audio tones and even RF coupled to the AC lines with a rusty
joint and re radiated..

AL, K0VM



On 6/17/2022 6:46 AM, Michael Black via groups.io wrote:
That could be aircraft reflection. Just a touch of Doppler.
Mike W9MDB



On Friday, June 17, 2022, 06:39:07 AM CDT, Pietro Molina <
pietro@...> wrote:

I never saw this effect: link
https://www.dropbox.com/s/5csq20ase8h9xqs/Screenshot%202022-06-17%2012.00.54.png?dl=0
I have often seen a ghost signal with lower intensity, in previous
versions, especially off 50Hz. In the decoding panel, however, there was
only one line, the ghost images were not reported. This has never happened
with such close signals, I think due to noise in my receiver or transmitter.
Not a big deal, but in case of congested band it can be disturbing.

Pietro I2OIM
















locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

Jim Brown
 

On 6/17/2022 4:46 AM, Michael Black via groups.io wrote:
That could be aircraft reflection.  Just a touch of Doppler.
Those of us around San Francisco and San Jose see this pretty often, thanks to multiple airports with lots of traffic. I'm 20 miles from the nearest airport and see it often.

73, Jim K9YC


locked Re: 2.6.0 video oddity (bug?) #IssueReport

John Nelson
 

That's interesting -- same here.

I much prefer dark mode and it'd be great if this albeit very minor glitch could be fixed.


locked Re: All is going well here with 2.6.0-rc1 #mainscreen

Palle Preben-Hansen, OZ1RH
 

If additional buttons are to be added, Contest Mode should be a priority. Lot of quick switching between normal and CM
It would be better if WSJT could switch automatically to contest mode and back again. That is WSJT should always send the exchange wanted by the other QSO partner and then after the QSO go back to the mode you you prefer. As WSJT can display a window "Change to xx contestmode" it might as well just switch to that contestmode.

73, Palle, OZ1RH.


locked Re: 2.6.0 video oddity (bug?) #IssueReport

Dave Corio
 

That was it here. Changing from dark mode eliminated the problem.

Still not a major issue, but I hope it might be addressed somewhere down the road.

2.6.0 still performing well!

Tnx es 73
Dave - K1DJE


locked Re: logging #logging

Roger
 

This is not a WSJTX problem so I am locking this thread. Please continue discussions on a JTALERT forum.

73
Roger
GW4HZA
Moderator


locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

JP Tucson, AZ
 

Hi Joe & wsjtx team,

Interesting...

Could you folks please elaborate on the following...

- Correct the handling of messages starting with "CQ xxxx ..."

What was 'wrong' with it, how is supposed to work now?


- Correct a flaw that could cause Windows to drop audio samples

Thanks, I've been noticing this more recently! Haven't changed computer stuff, or radio setup, and couldn't figure out why I appeared to have no-decodes (clock is gps), etc. Hopefully, these issues will go away for good.


- Correct the auto-sequencing logic in several specific circumstances

What exactly did you correct; i.e. what symptoms? What specific circumstances... so that we can look and make sure on our end it is corrected.
(I have long suspected & known that there were several 'bugs' in the auto sequence.



I don't know if you have touched this: but I will make this suggestion.

PLEASE ! Change the Fox/Hound watchdog! Meaning - please give us an actual countdown to when it is going to shut off our transmitter! That the FH watchdog is not even the same time as the std watchdog is confusing... further, the FH watchdog tends to shut off at the most inopportune times! Like during a QSO (the other station will reply, but your computer won't respond - - - in other words, the program needs to DETECT that the other station has called and automatically turn the TX BACK ON please! )


Next: Please make a section for SOTA/POTA/IOTA... heck, all the '....OTA/s... haha
Also for the State QSO parties.

Mean allow for the extended exchanges.

I have thought about this, understand that each line is limited by bits, etc.

My proposed solution is to create a 'special op mode' where you add a TX7 line where a person can STORE the SOTA/POTA number and the auto-sequencer in that mode will jump from Tx5 (..73), to TX 7 and list the stored #.

Further, this scheme could also work for QSO parties by allowing them to add/store their State/County....

Ultimately, this could carry forth to a TX8, 9 and 10 for short emergency messages and other such long exchanges. Hopefully to the point where even the Winter Field Day folks get on board with FT8.



Thank you


locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

Paul
 

Hi all this might be of help.Running here Windows 10 Dell.I tried several times and this error occurred.C:\WSJT\wsjtx\bin\qt5core.dll. Retry and ignore never worked.Check for file in WSJTX and it was there.DID A RESTART and all downloaded fine.Always worth a restart and retry.I am glad to see JT9 Is still accessible in the mode drop down.Need more users !!!Thanks Joe and the team for all your hard work.Kindest Regards as always.Paul G4YKQ.

On Friday, 17 June 2022, 14:17:37 BST, Gary Rogers <cgaryrogers190@...> wrote:

I set the configuration with the cmake GUI. The config.h that worked has:

/* Define to 1 if you have the <linux/parport.h> header file. */
/* #undef HAVE_LINUX_PARPORT_H */


In the file that didn’t work the second line was:

#undef HAVE_LINUX_PARPORT_H */

There were several commands in this file with that problem. Of the three config.h files in my build directory, two started with # so I just overwrote the two bad files with the good one and it built.


On Jun 16, 2022, at 3:13 PM, Michael Black via groups.io <mdblack98@...> wrote:

In Hamlib/src/parallel.h there is this:

#ifdef HAVE_LINUX_PARPORT_H
#  include <linux/parport.h>
#endif

Then in config.h
/* Define to 1 if you have the <linux/parport.h> header file. */
#define HAVE_LINUX_PARPORT_H 1

config.h is generated by "configure" -- do you use "configure" ??

Mike W9MDB







On Thursday, June 16, 2022, 01:54:49 PM CDT, Gary Rogers <cgaryrogers190@... <mailto:cgaryrogers190@...>> wrote:





I’ve installed on Windows 10, MacOS 12.4 and Raspberry Pi using the provided installers. All seem to functioning as intended.

When I try to build from source for MacOS, I get the following fatal error during the Hamlib build portion:

/Users/charlesrogers/Build/hamlib-prefix/src/hamlib/src/parallel.h:30:12: fatal error: 'linux/parport.h' file not found
#  include <linux/parport.h>
^~~~~~~~~~~~~~~~~
1 error generated.
make[5]: *** [dummy.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [all-recursive] Error 1
make[3]: *** [hamlib-prefix/src/hamlib-stamp/hamlib-build] Error 2
make[2]: *** [CMakeFiles/hamlib-install.dir/all] Error 2
make[1]: *** [CMakeFiles/package.dir/rule] Error 2
make: *** [package] Error 2

Any thoughts on how to resolve?








locked Re: Release Candidate WSJT-X 2.6.0-rc1 #general

Al Groff
 

It could also be caused a power line ( 50 hz in EU) induced AM modulation. It could be power supply ripple on the RF PA, AC modulating the TX audio tones and even RF coupled to the AC lines with a rusty joint and re radiated..

AL, K0VM

On 6/17/2022 6:46 AM, Michael Black via groups.io wrote:
That could be aircraft reflection.  Just a touch of Doppler.
Mike W9MDB


On Friday, June 17, 2022, 06:39:07 AM CDT, Pietro Molina <pietro@...> wrote:
I never saw this effect: link  https://www.dropbox.com/s/5csq20ase8h9xqs/Screenshot%202022-06-17%2012.00.54.png?dl=0
I have often seen a ghost signal with lower intensity, in previous versions, especially off 50Hz. In the decoding panel, however, there was only one line, the ghost images were not reported. This has never happened with such close signals, I think due to noise in my receiver or transmitter.
Not a big deal, but in case of congested band it can be disturbing.

Pietro I2OIM









locked Re: Contesting Decode Window #TechnicalHelpQuestion #ContestMode

Robert T
 

OK sorry guys, I didn't realize that window was generated by N1MM and not WSJT-X. Problem is being looked into.

Bob, K2RET

<pre>1</pre>

On 06/14/2022 4:42 PM Robert T <k2ret@...> wrote:


Awhile back changes were made to the Decode List window so that it could be expanded to widen the columns so that during a contest, the message field could be made wider to accommodate the wider messages from stations received. During the ARRL Digi & ARRL VHF contests, I widened the window and adjusted the width of the message field. After some time, the window defaulted back to the original size when I first opened it. I had to keep adjusting the window and message column width throughout the contest.

Is there a setting I'm missing or is there something that can be done on your end, programming wise, to repair this?

Thanks,

Bob, K2RET



locked Re: logging #logging

richard clare
 

Dave, the issue seems to be the newest update release (2.51.5) of jtAlerts. When I reverted back to the last version I didn't get the error about not logging to dxlab when making a new qso. When I reinstalled the newest update to jtAlerts I got the error alert again. I then went back to the previous version (2.51.4) and it was working correctly. The error seems to be the latest update of jtAlerts. Thanks Dave for the quick response. Richard wb6ewm

2921 - 2940 of 38026