Re: [wsjt-devel] RC4 Unexpected Behavior of RR73

[James Shaver]

The other person needs to check to see if NA Contest Mode is selected in the 
menu.  

 

From: m...@handgunrepairshop.com [mailto:m...@handgunrepairshop.com] 
Sent: Sunday, November 18, 2018 7:30 PM
To: 'WSJT software development'
Subject: [wsjt-devel] RC4 Unexpected Behavior of RR73

 

As requested in 2.0 Quick Start Guide, a report of unexpected behavior in rc4.

 

214715 Tx 2617 ~ CQ KV4ZY EN91 

214730 -4 0.3 2401 ~ KV4ZY W5PF EM20

214745 Tx 2617 ~ W5PF KV4ZY -04 

214800 -2 0.3 2401 ~ KV4ZY W5PF R EM20

214815 Tx 2617 ~ W5PF KV4ZY RR73 

214845 Tx 2617 ~ CQ KV4ZY EN91 

214830 -2 0.3 2401 ~ KV4ZY W5PF 73

 

Auto seq sent RR73 prior to receiving a signal report in the above QSO, the 
wsjtx.log entry with empty rcvd field;

 

2018-11-18,21:47:30,2018-11-18,21:48:15,W5PF,EM20,14.076617,FT8,-04,,20,TS-2000 
& H-6BTV,

 

Additional observation, the move to 2.0 is slowly gaining users, I had to use 
JTAlert text message to help 2 QSO attempts with me, one was still using rc3 
and the other his very first rc4 QSO today.

 

73 de Doug KV4ZY

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] RC4 Unexpected Behavior of RR73

[mail]

As requested in 2.0 Quick Start Guide, a report of unexpected behavior in rc4.214715  Tx  2617 ~  CQ KV4ZY EN91
214730  -4  0.3 2401 ~  KV4ZY W5PF EM20
214745  Tx  2617 ~  W5PF KV4ZY -04   
214800  -2  0.3 2401 ~  KV4ZY W5PF R EM20
214815  Tx  2617 ~  W5PF KV4ZY RR73  
214845  Tx  2617 ~  CQ KV4ZY EN91
214830  -2  0.3 2401 ~  KV4ZY W5PF 73Auto seq sent RR73 prior to receiving a signal report in the above QSO, the wsjtx.log entry with empty rcvd field;2018-11-18,21:47:30,2018-11-18,21:48:15,W5PF,EM20,14.076617,FT8,-04,,20,TS-2000 & H-6BTV,Additional observation, the move to 2.0 is slowly gaining users, I had to use JTAlert text message to help 2 QSO attempts with me, one was still using rc3 and the other his very first rc4 QSO today.73 de Doug KV4ZY

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Greg Beam]

Hi Stephen,

 

re: (post #435): After JTSDK 3.0.2 is released, I’ll be separating the non-WSJT 
frameworks into their own projects to make installation/updates a bit easier 
for everyone. At that point, a User Guide will be added which will explain each 
of the scripts/applications (possibly its own project). A jtsdk-dotnet-core 
repository “rename” will also be made to better align with its purpose. 
Currently, the Windows Build Script (JTBuild-cm.cmd) is for testing only and 
will be converted to a CSharp application so it works cross-platform. The whole 
point of moving to CSharp/Java/Python was to allow any one app/script to work 
on multiple platforms without much hassle.

 

Regarding which version of Qt to use, that is entirely up to the WSJT Dev team. 
Qt 5.9 was an LTS release (3yr support I believe) which is why I added it to 
JTSDK v3. If 5.9.x doesn’t work for Mac OS they may need to bump it to 5.10 or 
whatever is deemed appropriate. Either way, it’s a simple change to JTSDK v3 to 
accommodate the need.

73’s

Greg, KI7MT

 

 

From: Stephen Ireland  
Sent: Saturday, November 17, 2018 11:41 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJT-X & JTSDK future?

 

Hi Bill and Greg,

 

I am just a little surprised, after some ongoing comms, that the JTSDK 3.0.1 is 
not the prime, standard Windows Development platform  So that everyone is 
on the same page.

 

Greg, the JTSDK 3.0.1 works a treat... as long as you follow the instructions 
in your main post (#435) at https://groups.io/g/JTSDK/topic/23847651 .

 

[ It even works with “forks” that use subversion s long as the 32-bit SlikSVN 
client found at  https://sliksvn.com/download/ overwrites the deployed version 
].

 

Greg, can you please perhaps put these instructions found in #435 somewhere 
clearly and cleanly and in a prominent place for all for guidance? From you it 
gains validity. 


Bill, I am of the opinion, with considerable evidential backing, that Qt 5.5 is 
lacking for our needs (as some comms has conveyed); migration and 
standardisation to more contemporary Qt versions are mandated. Note – not 
“bleeding edge” versions, but contemporary versions. We then need to stick 
SOLELY with this version for a while.

 

Greg, I think that the AR community significantly missed your attention to us. 
Yet it is always a reminder to us all that personal interests must ALWAYS come 
first and that we in the AR community must be patient. Patience is a virtue – 
but not a virtue shared by many in the AR community ☹ 

If you need a hand, there are many of us here that can and are willing to help 
and contribute. Some of us (including me) may be “pains in the posterior” on 
occasion, but most in our community have their hearts in the right place.

 

Advancement.

 

73

 

Steve I

VK3VM / Vk3SIR

 

Sent from Mail   for Windows 10

 

From: Greg Beam  
Sent: Sunday, 18 November 2018 4:40 PM
To: 'WSJT software development'  
Subject: Re: [wsjt-devel] WSJT-X & JTSDK future?

 

Hi Bill,

 

Understand all re: points in 1 and 2 below.

 

As for item 3, JTSDK-Tools (JTSDK v3) uses the Qt Installer for updates / 
adding GCC tool-chains and prebuilt-components. At present, version JTSDK-Tools 
v3.0.1 supports both Qt 5.5 and Qt 5.9. As most would agree, using the Qt 
Maintenance Tool is the preferred method of installing/updating Qt Components. 
Adding Qt 5.10 would require a minimal change to the environment script(s) and 
I may add that to version 3.0.2 to cover future needs. It appears that Qt 5.5 
thru 5.10 all use the 5.3.x GCC tool-chain which simplifies things a good bit.

Most of the JTSDK-Tools installation is manually performed by the user, as this 
allows greater flexibility with installation and updates. The addition of MSYS2 
is a major improvement over the original MSYS as it provides a powerful package 
manager (pacman, from Arch Linux) to keep utilities up to date.

 

JTSDK-Tools is, for the most part, geared more toward developers rather than 
casual users. The basics are there for anyone wanting to work on whatever 
project they wish. However, it is not a turn-key solution as it was in the past.

 

73’s

Greg, KI7MT

 

From: Bill Somerville mailto:g4...@classdesign.com> > 
Sent: Saturday, November 17, 2018 2:21 PM
To: wsjt-devel@lists.sourceforge.net  
Subject: Re: [wsjt-devel] WSJT-X & JTSDK future?

 

On 17/11/2018 05:24, Greg Beam wrote:

At this point, I’ve no idea how things are working with WSJT-X builds (Win32 or 
Linux) other than what’s being formally published by the WSJT Dev team. 

Hi Greg,

welcome back!

The relevant changes can be summarized as:

1) we are now using git DVCS. I think you are up to speed on this already and 
are aware of the new git repos on the WSJT SourceForge project page. The old 
svn repo is still there but for 

[wsjt-devel] Reminder: FT8 mock contest tomorrow

[Joe Taylor]

A one-hour "practice contest" will be held tomorrow using the FT8 mode 
and the ARRL RTTY Roundup rules.


Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time)

Dial frequency 7.078 MHz (and higher, in 2 kHz increments, if too much 
QRM).  Secondary dial frequency, especially for those in other parts of 
the world: 14.078 MHz.


Everyone works everyone.

To participate you must use WSJT-X 2.0.0-rc4.  Installation packages for 
Windows, Linux, and macOS can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Note that this Release Candidate 4 ("RC4") is a beta-test version.  A 
full release of WSJT-X 2.0 is targeted for release on December 10, 2018.


A revised Quick-Start Guide to WSJT-X 2.0 for RC4 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

Be sure to read this entire document before using WSJT-X 2.0.  There 
have been many changes since RC3.


IMPORTANT FOR THE MOCK CONTEST:

1. On the *Settings | Advanced* tab, be sure to check the
*Special operating activity* and *ARRL RTTY Roundup* options.  In the 
field labeled "Exch" enter the 2- or 3-letter abbreviation for your 
state or province (US/Canadian stations) or DX if you are not in the US 
or Canada.


2. Be sure that 7.078 and 14.078 appear in your drop-down frequency list 
for FT8 mode.  You might need to do a *Reset* on the *Settings | 
Frequencies* tab.  If the sub-band starting at 7.078 becomes 
over-crowded we suggest moving to higher dial frequencies in 2 kHz 
increments: 7.080, 7.082, etc.  Type Ctrl+Shift+F12 to move up by 2 kHz, 
Ctrl+Shift+F11 to move down by 2 kHz.  You might want to change 
Bins/Pixel or adjust the width of the Wide Graph so as to limit the 
range of frequencies displayed to 0 - 2000 Hz.


3. Do not use a compound or nonstandard callsign in this event.

Note that planning is underway for other FT8 contests to be held in the 
next few months.


FT8 Roundup: December 1-2, 2018, see
https://www.rttycontesting.com/ft8-roundup/rules/ for detsils.

The ARRL RTTY Roundup, January 5-6 2018: FT8 is encouraged, as well as RTTY

Post results and comments here so we can all learn from an actual FT8 
contest-like experience.  If you are not already subscribed, you may 
wish to join the email list wsjt-devel:

https://sourceforge.net/p/wsjt/mailman/?source=navbar
That list is the best way to communicate directly with the WSJT 
Development Group.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Font size vs dialog box sizes.

[Leo]

Use siri to speak the frequenc

Sent from my iPad

> On 18 Nov 2018, at 15:13, WB5JJJ  wrote:
> 
> I have set my font to a larger size for easy readability without my reader 
> glasses.  This causes all text boxes to lose a lot of their information as 
> the font is larger but the text box is not dynamic and does not change size.  
> 
> The one area that does bug me is the dropdown for frequency selection, it 
> cuts off critical numbers after the decimal point, but does show the band.  
> So it will be displaying all choices like "14.07...(20m)" which is helpful, 
> but somewhat useless as I have to figure out which one of several identical 
> listings is the one I want.  Yes, they are in order, but it's still trial and 
> error to see which one the radio displays.  This is especially confusing when 
> I've loaded the saved and updated DXPedition setup configuration with 
> multiple frequencies in each band and I don't remember what they are. 
> However, sometimes this dropdown box is wide enough to see the full 
> information which is really nice, but mostly it's smaller. 
> 
> -- 
> George Cotton, WB5JJJ
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Font size vs dialog box sizes.

[Jim Shorney]

I found that I can make the fonts more readable to my eyes without actually
making them larger by setting the main font to DejaVu Sans bold and decoded
text font to Courier 10 Pitch bold. YMMV of course.

73

-Jim
NU0C


On Sun, 18 Nov 2018 08:13:26 -0600, WB5JJJ wrote:

> I have set my font to a larger size for easy readability without my reader
>glasses.  This causes all text boxes to lose a lot of their information as
>the font is larger but the text box is not dynamic and does not change
>size.
>
>The one area that does bug me is the dropdown for frequency selection, it
>cuts off critical numbers after the decimal point, but does show the band.
>So it will be displaying all choices like "14.07...(20m)" which is helpful,
>but somewhat useless as I have to figure out which one of several identical
>listings is the one I want.  Yes, they are in order, but it's still trial
>and error to see which one the radio displays.  This is especially
>confusing when I've loaded the saved and updated DXPedition setup
>configuration with multiple frequencies in each band and I don't remember
>what they are. However, sometimes this dropdown box is wide enough to see
>the full information which is really nice, but mostly it's smaller.
>
>-- 
>George Cotton, WB5JJJ
>

--
Hold tight and pretend it's a plan. - The Doctor, "The Doctor, the Widow and 
the Wardrobe"




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Font size vs dialog box sizes.

[WB5JJJ]

 I have set my font to a larger size for easy readability without my reader
glasses.  This causes all text boxes to lose a lot of their information as
the font is larger but the text box is not dynamic and does not change
size.

The one area that does bug me is the dropdown for frequency selection, it
cuts off critical numbers after the decimal point, but does show the band.
So it will be displaying all choices like "14.07...(20m)" which is helpful,
but somewhat useless as I have to figure out which one of several identical
listings is the one I want.  Yes, they are in order, but it's still trial
and error to see which one the radio displays.  This is especially
confusing when I've loaded the saved and updated DXPedition setup
configuration with multiple frequencies in each band and I don't remember
what they are. However, sometimes this dropdown box is wide enough to see
the full information which is really nice, but mostly it's smaller.

-- 
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Resolved bugs wsjt-x v2.0.0-rc4 a891ad

[VE3FBZ]

Thanks. Like everything else, what works.

I use a powered hub because my HP laptop USB power is an issue. Too much load I 
suspect. Anyway it works for me.

Apologize that I did not include in last msg.
V2-rc3
Win 10 1803 
IC-7300
Long wire antenna. 43 ft vertical then runs 63 feet horizontal - west to east.
MJF auto-tuner external - at base of vertical Antenna .


 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 




> On Nov 17, 2018, at 11:38 PM, Art Witmans  wrote:
> 
> Thank you VE3FBZ!
> 
> You mentioned the hub and it triggered a memory of past issues with hubs.
> The reason I used a hub is because the computer-end of the CAT cable for the 
> FT897 has the interface circuit moulded in and is therefore wider than normal 
> which in turn prevents the usb audio converter cable to be plugged into the 
> next usb port of the laptop.
> 
> I carefully ground off enough plastic from one side of the wide plug so both 
> fit in the laptop. 
> 
> Result: No hub - problem gone! 
> 
> Thanks again!
> Best Regards,
> VE7WAE, 
> 
> Sent from ProtonMail Mobile
> 
> 
>> On Sat, Nov 17, 2018 at 17:36, VE3FBZ  wrote:
>> Try putting a powered USB hub between.
>> 
>> 
>>  Regards and 73s
>> VE3FBZ
>> London Amateur Radio Club
>> www.larc.ca 
>> 
>> 
>> 
>> 
>>> On Nov 17, 2018, at 6:06 PM, Art Witmans via wsjt-devel 
>>>  wrote:
>>> 
>>> 
>>> 
>>> 
>>> Sent with ProtonMail Secure Email.
>>> 
>>> ‐‐‐ Original Message ‐‐‐
 On Saturday, November 17, 2018 2:55 PM, Yahoo Groups 
  wrote:
 
 Hello
 
 wsjt-x and js8call are really great fun to use!
 
 The problems I find is there is a frequent loss of audio link from laptop 
 to transceiver. It goes ok for a while and than the modulation comes out 
 the laptop speaker instead of going to the transceiver. Once this happends 
 it will ignore the settings in the preferences.
 The only way to restore function is by quitting and restarting the 
 software.
 FT991a has additional problem having 2 codecs and you never know which one 
 it wants to use. If it is the "wrong" one, you have to force quitting the 
 software because it does not quit normally.
 Flrig does not have this problem
 
 Same problem found in the js8call software.
 
 Laptop used:
 macOS Mojave 10.14.1
 tranceivers used:
 FT-897D and FT-991A
 
 
 Sent with ProtonMail Secure Email.
 
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Almost like back in the "Good Old Days"

[Michael]

Hi Guy's

Have been active today on wsjt-x rc4. Worked a few stations. Had the 
hook in k1jt but lost Joe in qrm. It just like the good old days in 2012 
when I started working on JT9 and JT65 - I callede CQ for many hours and 
nobody was alive out there. Sometimes I got an answer with - Hi Michael 
"You are the only one on the band - nice to work someone". That was how 
I made the WAS in only 3 month. After 6 years and + 50.000 qso's on the 
Digi modes I still love those modes and that includes "take the mode to 
the edge" like in the middle of the night sending with 5w on 60m or 160m 
and the waterfall is totally "clean" - in comes DP0POL on 60m with -22dB 
and send me a -24dB rpt - and on 160m VP8LP send me a -21dB - "I Love it 
- I love it" like another wellknown Danish guy "Ole Henrinksen" would 
have said,. Keep up the good work and I'll still be there to test it


73 de Michael 5p1kzx/oz1kzx




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rig control error on 40 meters

[Marco Calistri via wsjt-devel]

Ciao Marco,




This is a clear RF feedback which is disturbing your PC signal.




I'm quite sure it is this for two reasons:




1) it happens on a specific band


2) it disappears if you reduce the output power




First of all 100 watts on FT8 are exceeding the suggested power level, so the 
first suggested action is: keep power down!




Second, if you like/need QRO, you should verify the antenna on 40 meters and 
the coax line. May be by putting some ferrites as rf chokes along the cable 
and/or by adjusting the SWR you could eliminate the issue.




73 and Good luck de PY1ZRJ (FORMER) IK5BCU




Ottieni Outlook per Android







On Sun, Nov 18, 2018 at 7:14 AM -0200, "Marco Morelli via wsjt-devel" 
 wrote:















 
Get this message after 1 or  more succesful trasmissions.
If I chose retry  + enable TX I can continue for 1 or  more 
cycles then it happens again.
 
This happens only on 40 meter, on all the others bands WSJT works 
normally.
 
If I reduce power to about 100 w it seems to works almost normally.
 
I replaced interface cables, put ferrite beads, but nothing changed.
Checked CI-V interface transceive was OFF.
CI-V speed set to 1200 baud.  
 
WSJT-X is 1.9.1  but tested also 1.8 with same results.
PC op.sys is windows 10
TRX is IC-7800
 
 
Any suggestion ?
 
73 de I0MOM Marco





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel