Re: [wsjt-devel] Are you building WSJT-X ?

2022-04-25 Thread Ken Chandler via wsjt-devel
Hi chaps
I’ve built WSJT - X on Raspberry pi platform a while ago, runs very well, 
finding my notes is the issue, will post when I retrieve then…

Ken.. G0ORH

Like it’s owner, this email is covid free!

Sent from my iPad


On 25 Apr 2022, at 18:55, William Smith via wsjt-devel 
 wrote:

I've built WSJT-X from source on a Raspberry Pi.  Here are my notes  (yeah, I 
know this isn't the _right_ way, but I couldn't understand the instructions, so 
i found a tutorial and modified it:

/*
The instructions in the source tarall are much easier to parse if you already 
know what you are doing.  路‍♂️

I got some hints from http://www.kk5jy.net/wsjtx-build/

Here's what I did:

From a clean Bullseye install (11.1) via Raspberry Pi Imager

sudo apt-get install cmake

export CXXFLAGS='-O2 -march=native -mtune=native'
export CFLAGS='-O2 -march=native -mtune=native'

sudo apt-get install emacs-nox (or your favorite editor to build the script 
below)
build a script from the webpage above and execute it (takes a long time)

wget 
https://github.com/Hamlib/Hamlib/releases/download/4.3.1/hamlib-4.3.1.tar.gz
tar xvzf 
cd 
/configure --prefix=/usr/local --enable-static
make
sudo make install
sudo ldconfig
rigctl --version shows: rigctl Hamlib 4.3.1 Mon Sep 13
which rigctl returns: /usr/local/bin/rigctl
reboot to confirm somehting doesn't break
Success!

--  Now for wsjt-x

export CXXFLAGS='-O2 -march=native -mtune=native'
export CFLAGS='-O2 -march=native -mtune=native'

wget https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.5.2.tgz
tar xvzf 
cd 
cd src
[Aha!  This is where hamlib 4.4 comes from!]
tar -zxvf wsjtx.tgz
mkdir build
cd build
cmake ../wsjtx
make
sudo make install

*/

I'm a hardware guy, but I've programmed in Basic, Pascal, Fortran, a lot of 
Z-80 assembly, C, a little C++, Perl, and lately mostly Python under Debian 
(mostly on Raspberry Pi).

I don't really have the skills to parse the code and make changes, and there 
are no particular missing features I feel are critical.  I started to look at 
what it would take to run through the audio initialization and connection steps 
on {USB port renumbering} so as to avoid restarting WSJT-X (or deselecting and 
reselecting the proper audio ports), but it's a rare enough occurrance that I 
stopped when I got bogged down.  路‍♂️

I've written some Python code to parse ALL.TXT and determine where the gaps in 
the waterfall are, and get histograms of audio frequency, SNR, and dT, so 
that's kinda fun.

Gotta say, this is a spectacular program, and the ability to run it on multiple 
platforms really makes it shine.  While I've done Windows, macOS, and Linux, I 
settled on the latter for ease of use.

Thanks for making this for all of us to enjoy!

73, Willie N1JBJ
73, Willie VP5WS



> On Apr 25, 2022, at 11:29 AM, Joe Taylor via wsjt-devel 
>  wrote:
> 
> When I started work on WSJT some 21 years ago, my principal goal was to help 
> bring amateur weak-signal communication techniques into the twenty-first 
> century -- and in doing so, to help spread knowledge of modern communication 
> theory into the amateur radio community.
> 
> By 2005 WSJT was well established but mostly used for special purposes like 
> meteor scatter and EME ("moonbounce").  A stable development path had been 
> established: the program was fully Open Source, licensed under the GNU 
> General Public License, and it could be built by anyone from source code 
> using freely available compilers and development tools.  At this time WSJT 
> was coded in a combination of Python, Fortran, and C.  A re-write in 2012 
> created the present program, WSJT-X, using the Qt platform and C++ language 
> in addition to Fortran and C.
> 
> To help gauge the extent to which my original educational goals are being 
> met, we in the core development team are interested to know how many WSJT-X 
> users are currently building the program for themselves, from source code.  
> If you are doing so, we would appreciate an email response -- either 
> publicly, to this list, or in a private email to me. All responses will be 
> appreciated, but particular things you might want to mention in your message 
> include these:
> 
> - Building on what platform?  Windows, Linux, macOS, or other?
> 
> - What are your particular programming skills and interests?
> 
> - Are you making changes to the code?  If so, toward what end?
> 
> - What portions of the code have you studied well enough to understand?
> 
> Many thanks -- I look forward to hearing from you!
> 
>   -- 73, Joe, K1JT
> 
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT-X 2.5.0 GA Release

2021-09-28 Thread Ken Chandler via wsjt-devel
I tried uploading 2.5.0 and got a big error message.
I had to abort.

Ken.. G0ORH

Like it’s owner, this email is covid free!

Sent from my iPad


On 28 Sep 2021, at 16:30, Bill Somerville via wsjt-devel 
 wrote:


On 28/09/2021 16:25, Richard Shaw wrote:
> On Tue, Sep 28, 2021 at 9:45 AM Bill Somerville via wsjt-devel 
>  wrote:
>> Your build has many compiler options we have not tested with, do you really 
>> need to use them all?
>> -grecord-gcc-switches
>> -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
>> -Wp,-D_GLIBCXX_ASSERTIONS
>> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
>> -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1
>> -fasynchronous-unwind-tables
>> -fstack-clash-protection -fcf-protection
>> -Werror -Wall -Wextra
>> -Wno-pragmas -Wl,-z,relro
>> -Wl,--as-needed -Wl,-z,now
>> -specs=/usr/lib/rpm/redhat/redhat-hardened-ld
> 
> Those build flags are enforced by Fedora packaging guidelines and are 
> automatically applied with the %cmake RPM macros, however, I have already 
> built test packages of 2.5.0 without issue for Rawhide and Fedora 34. I plan 
> to do the official builds after I have a little time to test it locally first.
> 
> Thanks,
> Richard 
Hi Richard,

thanks for that confirmation. It would seem that either the Qt5 libraries in 
the RedHat repo are broken or Tomasz's system has some issues.

73
Bill
G4WJS.

___
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] (no subject)

2020-05-23 Thread Ken Chandler via wsjt-devel
I had issues to but on window 10 platform.
I used the FT5000 rig, everything burst into life when I switched over from 
FTdx101D 

Ken.. G0ORH

Sent from my iPad


> On 24 May 2020, at 01:02, John Zantek  wrote:
> 
> Bill,
> Many new 101MP owners in the PNW have been experiencing some setup issues, 
> resulting in lots of phone calls. 
> Have you been able to talk to the rig with any other S/W via USB and with 
> what virtual settings?
> Is the PC using USB 2.0 or 3.x ?  The 101MP is unfortunately persnickety in 
> that regard.
> No hubs, right?
> 73 John W7CD
>  
> From: Bill [mailto:brightl...@gmail.com] 
> Sent: Saturday, May 23, 2020 3:59 PM
> To: WSJT software development
> Subject: Re: [wsjt-devel] (no subject)
>  
> Hi,
>  
> Thanks for the quick response. I just tried HandShake = NONE and I have 
> the same result - Rig Failure - HamLib Error.
>  
>Any other suggestions?
>  
> Thanks!
>  
> Bill - AK6A
>  
> On Sat, May 23, 2020 at 3:32 PM Bill Somerville  wrote:
> On 23/05/2020 23:16, Bill wrote:
> I am having an issue connecting a Yaesu FTDX-101MP to WSJT-X on a Mac. I’m 
> able to get the receive Audio Codec to work properly and I can see decodes 
> but I get a “Rig Failure - Hamlib Error - Invalid configuration while opening 
> connection to rig” whenever I do a Test CAT. I am unable to get WSJT-X to 
> establish control communications with the radio. I’ve seen online suggestions 
> that say use the HamLib FT-991 selection. I am using the regular WSJT-X 
> version 2.1.2. I am also just using a USB cable from the radio to the Mac 
> which is running High Sierra. I am using the following settings:
> 
>  
> 
> WSJT-X
> 
>  
> 
> RADIO TAB
> 
>  
> 
> Rig: Yaesu FT-991
> 
>  
> 
> Serial Port: /dev/cu.SLAB_USBtoUART1 
> 
> Note: Installed latest Silicon Labs Drivers - Also Available selections:
> 
> /dev/tty.SLAB_USBtoUART1
> 
> /dev/cu.SLAB_USBtoUART
> 
> /dev/tty.SLAB_USBtoUART
> 
>  
> 
> Baud Rate: 38400
> 
> Polling Interval: 1S
> 
> Data Bits: Eight
> 
> Stop Bits: Two
> 
> Handshake: Hardware
> 
> Force Control Lines: Both Empty
> 
>  
> 
> PTT Method: CAT
> 
> Mode: None
> 
> Split: Rig
> 
>  
> 
> AUDIO Tab
> 
>  
> 
> Input - USB AUDIO CODEC
> Output - USB AUDIO CODEC
> 
> FTDX101MP Menu
> 
>  
> 
> FUNC --> Operation Settings
> General
> 232C RATE - 38400
> CAT RATE - 38400
> 
> FUNC --> RADIO SETTINGS
> MODE SSB
> SSB MOD SOURCE - REAR
> REAR SELECT - USB
> RPORT GAIN - 10
> DATA MODE SOURCE - REAR (This is the default)
> REAR SELECT - USB
> DATA OUT LEVEL - 10
> RPORT GAIN - 10
> 
> RADIO MAIN PANEL & DISPLAY
> 
>  
> 
>  
> 
> R.FIL - 3kHz
> WIDTH - 4000Hz
> 
> 
> APPLE COMPUTER
> 
>  
> 
> USB AUDIO CODEC 1 Format: 2 ch 16-bit Integer 48 kHz
> USB AUDIO CODEC 2 Format: 2 ch 16-bit Integer 48 kHz
> 
>  
> 
>  
> 
>  
> 
> Any ideas what might be the issue in getting this going? Has anyone else been 
> able to get a FTDX-101MP working with WSJT-X? Do I need to install a newer 
> version of HamLib for this new radio?
> 
>  
> 
> Thanks!
> 
>  
> 
> Bill - AK6A
> 
> Hi Bill,
> 
> try with "Settings->Radio->Handshake->None".
> 
> 73
> Bill
> G4WJS.
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1

2020-05-08 Thread Ken Chandler via wsjt-devel
Joe
Does the switch stay active or is this for casual ops who only want to work a 
few QSO's so your asked each time whether to switch or decline!!

Regards
Ken.. G0ORH

Sent from my iPad


> On 8 May 2020, at 20:05, Joe Taylor  wrote:
> 
>> On 5/7/2020 02:35, Roeland Jansen wrote:
>> regarding the EU VHF contest mode:
>> it appears that even if it's unchecked the software does switch to contest 
>> mode. when you happen to
>> get a reply (?) or klick on someone who uses that mode. I think that is fine 
>> and fair enough.
>> However, it stays in that mode even when it was initially directed not to.
>> During ft8 activity contests, people use also other software that does not 
>> even have the EU VHF contest mode.
>> This means that if the switch has been made, you need to recognize it, reset 
>> it in the menu and call again.
>> That's the thought on this?
> 
> Your name and call??
> 
> Starting with WSJT-X v2.2.0, reception of one of the specialized EU VHF 
> Contest messages will cause trigger a message asking whether you should 
> switch to using EU VHF Contest messages.  The switch will not be automatic.
> 
> Obviously, to send or receive the specialized EU VHF Contest messages you 
> must use WSJT-X or some other software that supports these messages.
> 
>-- 73, Joe, K1JT
> 
> 
> ___
> 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