Re: [wsjt-devel] FT8 Testing

> On Jul 7, 2017, at 9:19 PM, David wrote: > > Hi All...been on 20m 17.074 calling CQ..Gary AG0N called me decode was -19 > but the band here is up and down at the moment .tnx Gary hope we can do > it sometime > > 73 David VK4BDJ I got all but the 73, David. It is

[wsjt-devel] FT8

Hi good sigs from USA..tnx guys for QSO David VK4BDJ -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [wsjt-devel] FT8 Testing

David, I just swung the beam your way. If you're still around, I'm monitoring 14074 FT8. Eric NC6K -Original Message- From: David [mailto:djm...@bigpond.com] Sent: Friday, July 7, 2017 8:19 PM To: 'WSJT software development' Subject: [wsjt-devel] FT8

[wsjt-devel] FT8 on test

Hi ...made a couple of contacts VK4QG and N7XR..found out that once you double click on the callsign it has an Auto Seq feature.real neat helps with the Qso as the mode is so fast.. Love the mode and will continue to test it 73 David VK4BDJ

[wsjt-devel] FT8 Testing

Hi All...been on 20m 17.074 calling CQ..Gary AG0N called me decode was -19 but the band here is up and down at the moment .tnx Gary hope we can do it sometime 73 David VK4BDJ -- Check out the vibrant tech

Re: [wsjt-devel] Compiling issues...

Hi Ryan, I think the package your looking for is: https://packages.ubuntu.com/xenial/libusb-1.0-0-dev https://packages.ubuntu.com/xenial/i386/libusb-1.0-0-dev/filelist .. so that would be: sudo apt-get install libusb-1.0-0-dev That is the package for 16.04 (Xenial). I

[wsjt-devel] WSJT-X 1.7.1 r7812

Hi Joe and Bill.compiled r7812 with JTSDK and it works 100% .FT8 RX/TX working well with FT-450D rig.thanks guys maybe we will get a contact...usually on 20m 14074.00 for FT8 73 David VK4BDJ -- Check

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Hi Bob, Bill may have gone to bed… He was on 20m, 14.074. Steve, k9an > On Jul 8, 2017, at 2:05 AM, Robert Nobis wrote: > > Hi Bill, > > Fantastic. Just wondering, what band were you on? > > > Bob Nobis > n7...@nobis.net > > >> On Jul 7, 2017,

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Thank you Joe and team. looking forward to it. Dave NZ3M On 7/7/2017 9:10 PM, Bill Somerville wrote: On 08/07/2017 00:53, Joe Taylor wrote: To: Users of FT8 From:WSJT Development Team Subject: IMPORTANT NOTICE ABOUT FT8 HI Joe, working UFB here, my first FT8 long path QSO using 50W my

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

On 08/07/2017 02:10, Bill Somerville wrote: working UFB here 12 US states, 1 VE province, 4 DXCC (K, VE, EI, VK) in less than 90 minutes on 20m. And we haven't even beta released FT8 yet. Thanks folks: US Counties confirmed: 0 worked : 16 Count State

Re: [wsjt-devel] Compiling issues...

You need libusb-1.0.0 and the -devel package I suspect. Had a similar issue with this on my old centos 6 box and had to compile that from source.. Lloyd Kirk WB5HUP On 2017-07-07 19:31, G8DQX (WSJT developers on SF) wrote: Ryan, one suspects that, for Ubuntu, the command should be: SUDO

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

On 08/07/2017 00:53, Joe Taylor wrote: To: Users of FT8 From:WSJT Development Team Subject: IMPORTANT NOTICE ABOUT FT8 HI Joe, working UFB here, my first FT8 long path QSO using 50W my end: 010245 Tx 1212 ~ VK6KXW G4WJS IO91 010230 -14 0.7 1189 ~ CQ VK6KXW OF87 010246 Tx

Re: [wsjt-devel] Double Display in Rx window

Same version, same thing here. This is a new config (I had accidentally "cloned" my development config into default, and the program wouldn't open, so I erased it and started from scratch). https://www.dropbox.com/s/dxom5s5t8f2n7d6/Screenshot%202017-07-07%2020.58.24.png?dl=0 On Fri, Jul 7, 2017

[wsjt-devel] Fwd: Double Decodes on Received Transmissions - FT8

​ Why am I getting double decodes on transmissions I receive m my QSO partner in the Rx Frequency. I have attempted to attach a screenshot. If not here is a copy and paste. 003945 -6 0.5 784 ~ KQ5S G4WJS +00 003945 -6 0.5 784 ~ KQ5S G4WJS +00 004002 Tx 785 ~ G4WJS KQ5S R-06

[wsjt-devel] Double Display in Rx window

Hi all .. Seeing double entries for the replying station in the RX window, r7812.See attached pic. Neil, KN3ILZ -- Check out the vibrant tech community on one of the world's most engaging tech sites,

Re: [wsjt-devel] Compiling issues...

Ryan, one suspects that, for Ubuntu, the command should be: *sudo apt install libusb-1.0-0-dev* HTH, Robin, G8DQX On 08/07/17 00:50, Bill Somerville wrote: Hi Ryan, sorry you are having trouble building WSJT-X. Try this: $ sudo apt install libusb-devel 73 Bill G4WJS.

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Joe and the dev team, Excellent work! The new-and-improved FT8 is working well. I'm using 7812 on a Mac. One thing I'm seeing, however: I'm getting double decodes when I'm in a QSO. For instance: [cid:25421FA7-3F32-40AC-9BD3-18D564FDDAC7] Is it just me? -- David Tiller Sr. Architect/Lead

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

My thanks also to Joe and the team. Two QSOs completed so far, and one with signal levels around -18. No repeats needed, and seems like all working so far. NC6K -Original Message- From: Dan Malcolm [mailto:dan.malcol...@gmail.com] Sent: Friday, July 7, 2017 5:42 PM To: 'WSJT software

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Thanks Joe. I know you and your fellow developers have been hard at it, and we appreciate the effort, and the great results. One issue I am seeing that during a QSO, my QSO partners replies show up in Band Activity fine, but get doubled in Rx Frequency. I have screen shots, and will provide

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To: Users of FT8 From:WSJT Development Team Subject: IMPORTANT NOTICE ABOUT FT8 If you are building WSJT-X for yourself from source code, you may now upgrade to r7812 and recompile. You will then have access to the latest version of FT8 plus some new features for setting default

Re: [wsjt-devel] Compiling issues...

On 08/07/2017 00:41, Ryan Tourge wrote: I'm having trouble compiling WSJT-X. I've installed the SDK and I believe all the dependencies that it has yelled at me about. It appears to have built hamlib-3 fine but when I try to build the latest development branch it gives me the following: This

[wsjt-devel] Compiling issues...

I'm having trouble compiling WSJT-X. I've installed the SDK and I believe all the dependencies that it has yelled at me about. It appears to have built hamlib-3 fine but when I try to build the latest development branch it gives me the following: This is on an Ubuntu 16.04 32 Bit system:

Re: [wsjt-devel] Frequency List in r7805

On 07/07/2017 23:55, Neil Zampella wrote: quick question, should frequencies that should be labeled at FT8 in the frequency list have the Mode blank when looking at the list, or is this something that will change at midnight, like Cinderella's coach ?? :) The reason I ask, is that they're

[wsjt-devel] Frequency List in r7805

Hi all, quick question, should frequencies that should be labeled at FT8 in the frequency list have the Mode blank when looking at the list, or is this something that will change at midnight, like Cinderella's coach ?? :) The reason I ask, is that they're turning up in the list when I'm in

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Thanks, Joe > Correct. It's not yet UTC on July 8. > > On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote: >> Hi Joe >> >> I think the code in mainwindow.cpp still has the restriction on mycall, >> in >> two places. >> >> Program does not run unless mycall set to one of the

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Correct. It's not yet UTC on July 8. On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote: Hi Joe I think the code in mainwindow.cpp still has the restriction on mycall, in two places. Program does not run unless mycall set to one of the test calls. Charlie To:

Re: [wsjt-devel] Suggestions for three extra bits in FT8

I'd like to see a message type that consisted of a callsign in the current format, and the rest of the bits are in a callsign specific message format. It should be displayed as HEX. There should be a website somewhere where the message format is defined based on the sending callsign. For

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Hi Joe I think the code in mainwindow.cpp still has the restriction on mycall, in two places. Program does not run unless mycall set to one of the test calls. Charlie > To: Users of FT8 > From:WSJT Development Team > Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8 > > The

Re: [wsjt-devel] Suggestions for three extra bits in FT8

Consideration may be given to using the 3 bits as an index rather than binary bits.That would give 7 options based on a 3-bit index with 000 meaning no options. de Mike W9MDB From: Alexandre Moleiro via wsjt-devel To: WSJT software development

Re: [wsjt-devel] Suggestions for three extra bits in FT8

Hi! 3 extra bits can potentially create 5 new FT8 "submodes" with just these constraints: -15 second T/R period-72 bits of payload each period This can open a whole new world of qso sequences, multi-pass decoding, TX power adjustment, beaconing, etc. We can look at "most requested" features

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To: Users of FT8 From:WSJT Development Team Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8 The planned protocol change in FT8 is now complete and tested. Effective at UTC on July 8, 2017, you should stop using FT8 with any WSJT-X code revision earlier than r7805. If you

Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

For Bill The easy way to test functionality is to remove set_vfo from dummy.c in hamlib and test with that and rigctld. WSJT-X will fail.  So it's just changing the set_vfo capability logic to match get the get_vfo logic. Bill's hamlib has been updated for the rigctld side to fix that side

Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

Mike -- Thanks for submitting the patches! I have installed "menu.patch" and "qsotime.patch". They appear to be OK, but please double-check to be sure their functions are what's wanted. I have left rigctld_setvfo.patch for Bill; I have no easy way to test its functionality here.

Re: [wsjt-devel] Suggestions for three extra bits in FT8

I think this might have been might missed in the fury of activity yesterday. Is there a write-up of the protocol anywhere for deeper understanding? Best, Jordan KN4CRD On Jul 6, 2017, 12:22 PM -0400, Jordan Sherer , wrote: > Thanks for the insight, Bill. Is there a

Re: [wsjt-devel] FT8 audio spacing - waterfall graticule

On 07/07/2017 11:23, Richard Lamont wrote: FT8 doesn't have a two-pass decoder. Even it it did, a signal that doesn't have another one overlapping it stands a better chance of being decoded. A regular spacing of (say) 60 Hz would help to keep things apart. I'm not suggesting that this should

[wsjt-devel] FT8 audio spacing - waterfall graticule

FT8 doesn't have a two-pass decoder. Even it it did, a signal that doesn't have another one overlapping it stands a better chance of being decoded. A regular spacing of (say) 60 Hz would help to keep things apart. I'm not suggesting that this should be forced on users by WSJT-X, but there is a

Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

On 07/07/2017 07:58, Adrian Fabry wrote: 2. For the saved wav files, mode and submode should be included in the file name Hi Ady, more information is included in the catalogue of the WAV files. It can be examined using a tool like Audacity to look at the metadata. It is unfortunate that the

Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

Hi Joe, thank you and all the development team for the work. I'd suggest two features: 1. QRA64: Different color (or using bold chars) for the AP part of the decoded message, when AP was used in the decode. 2. For the saved wav files, mode and submode should be included in the file name 73

Re: [wsjt-devel] WSJT-X: Working frequency suggestions

Hi Bill, Under CPU AMD A8-5500, i.e. poorman's i3, WSJT-X v1.7.0 r7405 works flawlessly even at blue separator down to zero. It stays at zero after restart the program and I could not see Gary's issue about the position change of blue separator. I believe JT9.exe is well designed for multiple