Date   
Astron Power Supplies For Sale #Power Supplies For Sale #power

Tony
 

All:

I have 3 like-new Astron power supplies for sale: SS-18 / SS-25 and SS-30M. All were purchased new for $400.0 in 2019.

Best offer takes all three. Pictures on request.

Paypal / CONUS only.

Tony -K2MO

k3ukpage #facebook

main@digitalradio.groups.io Integration <main@...>
 

By digitalradio

FT* mode activity on 20M tonight

New release of MULTIPSK (4.39.1) - New package due to missing files #Multipsk

Patrick Lindecker
 

Hello to all,

 

As I realized that it was missing files (about SDRplay), I have just updated the Multipsk V.4.39.1 package. Sorry.

 

73

Patrick




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


New release of MULTIPSK (4.39.1) #Multipsk

Patrick Lindecker
 

New release of MULTIPSK (4.39.1)

 

Pour les francophones: la version en français de ce message se trouve sur mon site (http://f6cte.free.fr). Il suffit de cliquer sur le lien "Principales modifications (courriel avertissant de la sortie de la nouvelle version)".


Hello to all Ham and SWL,

 

* The new release of MultiPSK (4.39.1) is on my Web site (http://f6cte.free.fr/index_anglais.htm).
* The mirror site is Earl's, N8KBR: https://www.paazig.net/f6cte/MULTIPSK_setup.exe

* The MD5 signature of the downloaded MULTIPSK_setup.exe file to, possibly, check (with WinMD5 for example), that the downloading works without error, is equal to: 7cd16b8616ec0883bdd11962a37edcbd

* Multipsk associated to Clock are freeware programs but with functions submitted to a licence (by user key).

 

The main improvements of MULTIPSK 4.39.1 are the following:

 

Addition of TCP/IP interfaces: "SRDplay" and "rtl_tcp.exe"

 

Pushing on the "SDRplay" or "rtl_tcp.exe" button of the "Configuration" screen permits to interface:

·                     either a SDRplay receiver, thanks to the TCP/IP server "rsp_tcp.exe",

·                     either a TNT receiver or compatible, thanks to the TCP/IP server "rtl_tcp.exe".

The frequency and the gain are adjustable through this interface.

The I/Q signal is taken from the receiver (TNT or SDRplay) through the TCP/IP server, at a sampling frequency 250 KHz, in the local loop adress: 127.0.0.1, port 1234. The TCP/IP adress and the port are configurable.

 

 

Improvement of the EGC decoding

The EGC (Enhanced Group Calls) service of Inmarsat C satellites uses the PSK modulation at 1200 bauds to send broadcast messages either to all ships or to ships located on a given area, from a NCSC (Network Control Station Channel). The geostationary Inmarsat satellites 4-F3, 3-F5, 4-F1 and 4A-F4 use frequencies around 1540 MHz for these transmissions

Necessary hardware: for these UHF frequencies, a stable receiver and without not too much shift is advised (RTL/SDR key as "RTL-SDR.COM V3", for example). A LNA ("Low Noise Amplifier") is necessary. It must be placed at the antenna output. A LNA specific to band L is advised. The antenna can be a Patch one or a helical one (right-hand circular polarization).

 

 

Note about translation of Multipsk.exe and Clock .exe:  the 4.39 version of Multipsk has been translated to Spanish by Joachin (EA4ZB), from French.

See: http://f6cte.free.fr/Translation_files.htm.

 

73

Patrick

 

 




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Re: VARA working under Wine!

Graham
 

Q  Is this process  automated now,  batch file ect  ? or  still  in the above, step by step  format ? 

Tnx-Graham

g0nbd 

Re: IS this Pactor 3 I have decoded ? #Pactor

Jeremy Allen
 

I know I'm late, but that's P3, specifically Speed level 1 and a few SL2's in there.  You can see it's SL1 with the 2 tones. 

As far as compression, the modems have built in PMC or Huffman compression that can be applied to the data stream in K-K or BBS QSO's.  In Winlink these are suppressed and the software uses B2F compression and the modem just transmits the 8-bit data without additional compression.

Most K-K is on 40 or 20M, but I guess some folks are on 80M as well.
--
73 DE N1ZZZ

Stand alone digital TX #FT8 #jt9 #pi4 #wspr

Bo, OZ2M
 

Hello group

If you are looking for a stand alone solution to transmit digital signals like FT8, JT9, PI4 or WSPR from kHz to GHz then the RFzero www.rfzero.net might be just what you have been looking for. The RFzero is an "extended" Arduino Zero, with GPS and more, so you can modify the software yourself if you like.

Bo

Re: Call AA0AAA ? Opera over Es'hail-2 / QO-100 #opera

Graham
 

Tnx Ev, 

I thought as much , 

The  identical  time  stamp is indicative  of a  simultaneous   'off air'  decode
one station, one  call , then that's open to  random  noise  , note the rx   time stamp is from
the  decode  pc  clock 

73-Graham

2019-05-24 22:13:18 IK1WVQ AA R3D-262 KO94KS 0 1.296.600 -12 Op05_||||||||||||||_~13dB
2019-05-24 22:13:18 IK1WVQ AA SP5XSB KO02LD 0 1.296.600 -10 Op05_||||||||||||||||||_~11dB
2019-05-24 22:13:17 IK1WVQ AA PA1SDB JO33KH 0 1.296.600 -15 Op05_||||||||_~16dB
2019-05-24 22:13:17 IK1WVQ AA SV8RV KM07KS 0 1.296.600 -12 Op05_||||||||||||||||_~12dB

Looking back over the  last 24 Hrs  spots ,  there is  only  one  false  decode  listed , 

2019-05-24 07:47:12 PA3GYK JO21QQ R3D-262 KO94KS 2.234 1.296.600 2 Op05_||||||||||||||||||||||||||||||||||||||||||||||_3dB
2019-05-24 07:46:59 O0PQ AA PA3GYK JO21QQ 0 1.296.600 -18 Op05_||||_~18dB
2019-05-24 05:19:50 IK1WVQ JN44CB SP5XSB KO02LD 1.302 1.296.600 -13 Op05_||||||||||||_~14d

Re: Call AA0AAA ? Opera over Es'hail-2 / QO-100 #opera

Ev Tupis
 

The AA block is assigned to the USA.

The AA 2x3 callsign format is not being assigned by the FCC to Amateur radio licensees.

It's a pirate, if decoded correctly.

Ev, W2EV


On Thursday, May 23, 2019, 6:09:50 PM EDT, Graham <g0nbd@...> wrote:


Usually ,  Opera  has its  share of  ' odd  calls  on 136 KHz  and  occasionally 477 

However,  one  decode  of the  call  AA0AAA  , occurred  at  0801 , all  Rx
stations ,  monitoring  off  air  10GHz down link  

I can  find  no  trace of the  call  on the  web ..but  qra locator JN44CB appears to  of been uploaded to the  system , by the  Opera  app 

2019-05-22 08:01:41 AA0AAA JN44CB PA1SDB JO33KH 1.033 1.296.600 -17 Op05_||||||_~17dB
2019-05-22 08:01:41 AA0AAA JN44CB SV8RV-8 KM07KS 1.271 10.368.000 -16 Op05_||||||||_~16dB
2019-05-22 08:01:41 AA0AAA JN44CB PA3GYK JO21QQ 874          10.368.000 -14 Op05_||||||||||||_~14dB
obvious conclusion I guess  -)

73-Graham
g0nbd

Call AA0AAA ? Opera over Es'hail-2 / QO-100 #opera

Graham
 

Usually ,  Opera  has its  share of  ' odd  calls  on 136 KHz  and  occasionally 477 

However,  one  decode  of the  call  AA0AAA  , occurred  at  0801 , all  Rx
stations ,  monitoring  off  air  10GHz down link  

I can  find  no  trace of the  call  on the  web ..but  qra locator JN44CB appears to  of been uploaded to the  system , by the  Opera  app 

2019-05-22 08:01:41 AA0AAA JN44CB PA1SDB JO33KH 1.033 1.296.600 -17 Op05_||||||_~17dB
2019-05-22 08:01:41 AA0AAA JN44CB SV8RV-8 KM07KS 1.271 10.368.000 -16 Op05_||||||||_~16dB
2019-05-22 08:01:41 AA0AAA JN44CB PA3GYK JO21QQ 874          10.368.000 -14 Op05_||||||||||||_~14dB
obvious conclusion I guess  -)

73-Graham
g0nbd

Re: Extended message and RS ID #Multipsk

Sholto Fisher
 

Hi Patrick,

 

> Note: QNI worth for what?

 

I was thinking of a little program which could automatically capture all the call signs heard from RS/CALL-ID when ncs asks for station check in (QNI).

 

73

Sholto

K7TMG

 

Sent from Mail for Windows 10

 


From: main@digitalradio.groups.io <main@digitalradio.groups.io> on behalf of Patrick Lindecker <f6cte@...>
Sent: Friday, May 3, 2019 1:48:02 AM
To: main@digitalradio.groups.io
Subject: [digitalradio] Extended message and RS ID #MULTIPSK
 

Hello Sholto,

 

>MultiPSK has a tcp/ip interface. It might be possible to use a custom application for RS-ID QNI?

Yes, the reception of a RS/ID (in a 44 KHz bandwidth maximum) is sent to the TCP/IP link (as the form of a comment) .

Note: QNI worth for what?

 

>I wonder if simultaneously received RS-ID symbols (separated by frequency) would be decoded? This would help a lot to overcome any doubling which is a common problem.

For RSID, strictly simultaneous no (it would be a very rare event).

However for EM, it can be received any number of extended messages (EM) strictly simultaneously, as it is programmed for.

 

73

Patrick

 

 

De : main@digitalradio.groups.io [mailto:main@digitalradio.groups.io] De la part de Sholto Fisher
Envoyé : vendredi 3 mai 2019 02:45
À : main@digitalradio.groups.io
Objet : Re: [digitalradio] #WSJTX FT4 for NBEMS nets ?

 

MultiPSK has a tcp/ip interface. It might be possible to use a custom application for RS-ID QNI?

 

I wonder if simultaneously received RS-ID symbols (separated by frequency) would be decoded? This would help a lot to overcome any doubling which is a common problem.

 

73

Sholto

K7TMG

 


From: main@digitalradio.groups.io <main@digitalradio.groups.io> on behalf of Tony <DXDX@...>
Sent: Thursday, May 2, 2019 5:10:35 PM
To: main@digitalradio.groups.io
Subject: Re: [digitalradio] #WSJTX FT4 for NBEMS nets ?

 

Andy:

 

The Extended Messaging feature in Multipsk would certainly speed-up the check-in process. It takes a few seconds to pass along ones status and call sign. The RS-ID protocol has plenty of sensitivity for the weaker check-ins as well.   


Check-ins would pop-up in both the waterfall and EM Window which is pretty convenient for the net control operator. 

 

Tony -K2MO

 

 

 

On 4/30/2019 10:45 AM, Andrew OBrien wrote:

Me , again. On my old topic of faster/easier net call-up methods.  As you may remember I think many NBEMS Olivia nets take FAR too long checking in stations (20 minutes of checking in, two minutes for net content ) . I did consider FSQcall and JS8Call as offering a better way to start an NBEMS net before switching to Olivia and FLAMP methods for traffic sending. Now I'm wondering if FT4 , or even FT8, offer something more efficient?  Both FT4 and FT8 offer the ability for Net Control to simultaneously detect stations checking in  over a 3 Khz range. Plenty of bandwidth for 20-30 NBEMS stations to check in and be "spread out" .  With FT4 , checking in could be done via a couple of 4.5 second cycles , with FT8 , 12 seconds. I'm also wondering about the "Fox and Hound" setting in FT8 (not implemented in FT4 at the  moment) and whether this could be used by a NCS to quickly acknowledge, en masse, the stations checking in. With WSJT-X and Fldigi open at same time. WSJT FT modes could be used to check in all stations within a minute and then use TX RSID in Fldigi (or Multipsk) to send traffic in the more  traditional, speedier, robust, digital modes.

 

Andy K3UK 

 




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Extended message and RS ID #Multipsk

Patrick Lindecker
 

Hello Sholto,

 

>MultiPSK has a tcp/ip interface. It might be possible to use a custom application for RS-ID QNI?

Yes, the reception of a RS/ID (in a 44 KHz bandwidth maximum) is sent to the TCP/IP link (as the form of a comment) .

Note: QNI worth for what?

 

>I wonder if simultaneously received RS-ID symbols (separated by frequency) would be decoded? This would help a lot to overcome any doubling which is a common problem.

For RSID, strictly simultaneous no (it would be a very rare event).

However for EM, it can be received any number of extended messages (EM) strictly simultaneously, as it is programmed for.

 

73

Patrick

 

 

De : main@digitalradio.groups.io [mailto:main@digitalradio.groups.io] De la part de Sholto Fisher
Envoyé : vendredi 3 mai 2019 02:45
À : main@digitalradio.groups.io
Objet : Re: [digitalradio] #WSJTX FT4 for NBEMS nets ?

 

MultiPSK has a tcp/ip interface. It might be possible to use a custom application for RS-ID QNI?

 

I wonder if simultaneously received RS-ID symbols (separated by frequency) would be decoded? This would help a lot to overcome any doubling which is a common problem.

 

73

Sholto

K7TMG

 


From: main@digitalradio.groups.io <main@digitalradio.groups.io> on behalf of Tony <DXDX@...>
Sent: Thursday, May 2, 2019 5:10:35 PM
To: main@digitalradio.groups.io
Subject: Re: [digitalradio] #WSJTX FT4 for NBEMS nets ?

 

Andy:

 

The Extended Messaging feature in Multipsk would certainly speed-up the check-in process. It takes a few seconds to pass along ones status and call sign. The RS-ID protocol has plenty of sensitivity for the weaker check-ins as well.   


Check-ins would pop-up in both the waterfall and EM Window which is pretty convenient for the net control operator. 

 

Tony -K2MO

 

 

 

On 4/30/2019 10:45 AM, Andrew OBrien wrote:

Me , again. On my old topic of faster/easier net call-up methods.  As you may remember I think many NBEMS Olivia nets take FAR too long checking in stations (20 minutes of checking in, two minutes for net content ) . I did consider FSQcall and JS8Call as offering a better way to start an NBEMS net before switching to Olivia and FLAMP methods for traffic sending. Now I'm wondering if FT4 , or even FT8, offer something more efficient?  Both FT4 and FT8 offer the ability for Net Control to simultaneously detect stations checking in  over a 3 Khz range. Plenty of bandwidth for 20-30 NBEMS stations to check in and be "spread out" .  With FT4 , checking in could be done via a couple of 4.5 second cycles , with FT8 , 12 seconds. I'm also wondering about the "Fox and Hound" setting in FT8 (not implemented in FT4 at the  moment) and whether this could be used by a NCS to quickly acknowledge, en masse, the stations checking in. With WSJT-X and Fldigi open at same time. WSJT FT modes could be used to check in all stations within a minute and then use TX RSID in Fldigi (or Multipsk) to send traffic in the more  traditional, speedier, robust, digital modes.

 

Andy K3UK 

 




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Re: #WSJTX FT4 for NBEMS nets ? #WSJTX

Andrew OBrien
 

I’ll have to take a closer look in Multipsk .
Andy . 


On May 2, 2019, at 8:45 PM, Sholto Fisher <sholto.fisher@...> wrote:

MultiPSK has a tcp/ip interface. It might be possible to use a custom application for RS-ID QNI?

 

I wonder if simultaneously received RS-ID symbols (separated by frequency) would be decoded? This would help a lot to overcome any doubling which is a common problem.

 

73

Sholto

K7TMG

 


From: main@digitalradio.groups.io <main@digitalradio.groups.io> on behalf of Tony <DXDX@...>
Sent: Thursday, May 2, 2019 5:10:35 PM
To: main@digitalradio.groups.io
Subject: Re: [digitalradio] #WSJTX FT4 for NBEMS nets ?
 
Andy:

The Extended Messaging feature in Multipsk would certainly speed-up the check-in process. It takes a few seconds to pass along ones status and call sign. The RS-ID protocol has plenty of sensitivity for the weaker check-ins as well.   

Check-ins would pop-up in both the waterfall and EM Window which is pretty convenient for the net control operator. 

Tony -K2MO



On 4/30/2019 10:45 AM, Andrew OBrien wrote:
Me , again. On my old topic of faster/easier net call-up methods.  As you may remember I think many NBEMS Olivia nets take FAR too long checking in stations (20 minutes of checking in, two minutes for net content ) . I did consider FSQcall and JS8Call as offering a better way to start an NBEMS net before switching to Olivia and FLAMP methods for traffic sending. Now I'm wondering if FT4 , or even FT8, offer something more efficient?  Both FT4 and FT8 offer the ability for Net Control to simultaneously detect stations checking in  over a 3 Khz range. Plenty of bandwidth for 20-30 NBEMS stations to check in and be "spread out" .  With FT4 , checking in could be done via a couple of 4.5 second cycles , with FT8 , 12 seconds. I'm also wondering about the "Fox and Hound" setting in FT8 (not implemented in FT4 at the  moment) and whether this could be used by a NCS to quickly acknowledge, en masse, the stations checking in. With WSJT-X and Fldigi open at same time. WSJT FT modes could be used to check in all stations within a minute and then use TX RSID in Fldigi (or Multipsk) to send traffic in the more  traditional, speedier, robust, digital modes.
 
Andy K3UK 


Re: #WSJTX FT4 for NBEMS nets ? #WSJTX

Sholto Fisher
 

MultiPSK has a tcp/ip interface. It might be possible to use a custom application for RS-ID QNI?

 

I wonder if simultaneously received RS-ID symbols (separated by frequency) would be decoded? This would help a lot to overcome any doubling which is a common problem.

 

73

Sholto

K7TMG

 


From: main@digitalradio.groups.io <main@digitalradio.groups.io> on behalf of Tony <DXDX@...>
Sent: Thursday, May 2, 2019 5:10:35 PM
To: main@digitalradio.groups.io
Subject: Re: [digitalradio] #WSJTX FT4 for NBEMS nets ?
 
Andy:

The Extended Messaging feature in Multipsk would certainly speed-up the check-in process. It takes a few seconds to pass along ones status and call sign. The RS-ID protocol has plenty of sensitivity for the weaker check-ins as well.   

Check-ins would pop-up in both the waterfall and EM Window which is pretty convenient for the net control operator. 

Tony -K2MO



On 4/30/2019 10:45 AM, Andrew OBrien wrote:
Me , again. On my old topic of faster/easier net call-up methods.  As you may remember I think many NBEMS Olivia nets take FAR too long checking in stations (20 minutes of checking in, two minutes for net content ) . I did consider FSQcall and JS8Call as offering a better way to start an NBEMS net before switching to Olivia and FLAMP methods for traffic sending. Now I'm wondering if FT4 , or even FT8, offer something more efficient?  Both FT4 and FT8 offer the ability for Net Control to simultaneously detect stations checking in  over a 3 Khz range. Plenty of bandwidth for 20-30 NBEMS stations to check in and be "spread out" .  With FT4 , checking in could be done via a couple of 4.5 second cycles , with FT8 , 12 seconds. I'm also wondering about the "Fox and Hound" setting in FT8 (not implemented in FT4 at the  moment) and whether this could be used by a NCS to quickly acknowledge, en masse, the stations checking in. With WSJT-X and Fldigi open at same time. WSJT FT modes could be used to check in all stations within a minute and then use TX RSID in Fldigi (or Multipsk) to send traffic in the more  traditional, speedier, robust, digital modes.
 
Andy K3UK 


Re: #WSJTX FT4 for NBEMS nets ? #WSJTX

Tony
 

Andy:

The Extended Messaging feature in Multipsk would certainly speed-up the check-in process. It takes a few seconds to pass along ones status and call sign. The RS-ID protocol has plenty of sensitivity for the weaker check-ins as well.   

Check-ins would pop-up in both the waterfall and EM Window which is pretty convenient for the net control operator. 

Tony -K2MO



On 4/30/2019 10:45 AM, Andrew OBrien wrote:
Me , again. On my old topic of faster/easier net call-up methods.  As you may remember I think many NBEMS Olivia nets take FAR too long checking in stations (20 minutes of checking in, two minutes for net content ) . I did consider FSQcall and JS8Call as offering a better way to start an NBEMS net before switching to Olivia and FLAMP methods for traffic sending. Now I'm wondering if FT4 , or even FT8, offer something more efficient?  Both FT4 and FT8 offer the ability for Net Control to simultaneously detect stations checking in  over a 3 Khz range. Plenty of bandwidth for 20-30 NBEMS stations to check in and be "spread out" .  With FT4 , checking in could be done via a couple of 4.5 second cycles , with FT8 , 12 seconds. I'm also wondering about the "Fox and Hound" setting in FT8 (not implemented in FT4 at the  moment) and whether this could be used by a NCS to quickly acknowledge, en masse, the stations checking in. With WSJT-X and Fldigi open at same time. WSJT FT modes could be used to check in all stations within a minute and then use TX RSID in Fldigi (or Multipsk) to send traffic in the more  traditional, speedier, robust, digital modes.
 
Andy K3UK 


#WSJTX FT4 for NBEMS nets ? #WSJTX

Andrew OBrien
 

Me , again. On my old topic of faster/easier net call-up methods.  As you may remember I think many NBEMS Olivia nets take FAR too long checking in stations (20 minutes of checking in, two minutes for net content ) . I did consider FSQcall and JS8Call as offering a better way to start an NBEMS net before switching to Olivia and FLAMP methods for traffic sending. Now I'm wondering if FT4 , or even FT8, offer something more efficient?  Both FT4 and FT8 offer the ability for Net Control to simultaneously detect stations checking in  over a 3 Khz range. Plenty of bandwidth for 20-30 NBEMS stations to check in and be "spread out" .  With FT4 , checking in could be done via a couple of 4.5 second cycles , with FT8 , 12 seconds. I'm also wondering about the "Fox and Hound" setting in FT8 (not implemented in FT4 at the  moment) and whether this could be used by a NCS to quickly acknowledge, en masse, the stations checking in. With WSJT-X and Fldigi open at same time. WSJT FT modes could be used to check in all stations within a minute and then use TX RSID in Fldigi (or Multipsk) to send traffic in the more  traditional, speedier, robust, digital modes.
 
Andy K3UK 

Re: FT4 public rlease now avaiable #WSJTX

Andrew OBrien
 

I assume JTalert will eventually be updated   . I use DXLab to get alerts for DXCC entities when using WSJT. 
Andy K3UK


On Apr 30, 2019, at 5:19 AM, John Netro via Groups.Io <n9wvm@...> wrote:

JT Alert Doesn't work with FT4, Any plans to have that working with it?

N9WVM, John

On Monday, April 29, 2019, 10:51:59 PM EDT, Tom W7SUA <tom@...> wrote:


Thanks!


On 4/29/2019 5:40 PM, Andrew OBrien wrote:
> I simply followed the instructions and “reset” and frequencies were there . I worked stations on 20, 30, and 17.
>> On Apr 29, 2019, at 7:40 PM, Tom W7SUA <tom@...> wrote:
>>
>> Thanks. Downloaded to copy the FT4 crowd.
>>
>> However the FT4 freqs not in there so had to add the recommended ones from the PDF. But folks are not up where the PDF intro document suggested. No not only being stomped on by FT8 when I an trying to use Olivia but by FT4 now when I am trying to use JS8. Grrr...
>>
>> 73, tom w7sua
>>
>>> On 4/29/2019 11:18 AM, Andrew OBrien wrote:
>>> RC5 of WSJTX is now available at the usual site.  This is the release that includes FT4 for testing
>>> Andy K3UK
>>
>>
>>
>
>
>


Re: FT4 public rlease now avaiable #WSJTX

John Netro
 

JT Alert Doesn't work with FT4, Any plans to have that working with it?

N9WVM, John

On Monday, April 29, 2019, 10:51:59 PM EDT, Tom W7SUA <tom@...> wrote:


Thanks!


On 4/29/2019 5:40 PM, Andrew OBrien wrote:
> I simply followed the instructions and “reset” and frequencies were there . I worked stations on 20, 30, and 17.
>> On Apr 29, 2019, at 7:40 PM, Tom W7SUA <tom@...> wrote:
>>
>> Thanks. Downloaded to copy the FT4 crowd.
>>
>> However the FT4 freqs not in there so had to add the recommended ones from the PDF. But folks are not up where the PDF intro document suggested. No not only being stomped on by FT8 when I an trying to use Olivia but by FT4 now when I am trying to use JS8. Grrr...
>>
>> 73, tom w7sua
>>
>>> On 4/29/2019 11:18 AM, Andrew OBrien wrote:
>>> RC5 of WSJTX is now available at the usual site.  This is the release that includes FT4 for testing
>>> Andy K3UK
>>
>>
>>
>
>
>


Re: FT4 public rlease now avaiable #WSJTX

 

Thanks!

On 4/29/2019 5:40 PM, Andrew OBrien wrote:
I simply followed the instructions and “reset” and frequencies were there . I worked stations on 20, 30, and 17.
On Apr 29, 2019, at 7:40 PM, Tom W7SUA <@w7sua> wrote:

Thanks. Downloaded to copy the FT4 crowd.

However the FT4 freqs not in there so had to add the recommended ones from the PDF. But folks are not up where the PDF intro document suggested. No not only being stomped on by FT8 when I an trying to use Olivia but by FT4 now when I am trying to use JS8. Grrr...

73, tom w7sua

On 4/29/2019 11:18 AM, Andrew OBrien wrote:
RC5 of WSJTX is now available at the usual site. This is the release that includes FT4 for testing
Andy K3UK

Re: FT4 public rlease now avaiable #WSJTX

Andrew OBrien
 

I simply followed the instructions and “reset” and frequencies were there . I worked stations on 20, 30, and 17.

On Apr 29, 2019, at 7:40 PM, Tom W7SUA <@w7sua> wrote:

Thanks. Downloaded to copy the FT4 crowd.

However the FT4 freqs not in there so had to add the recommended ones from the PDF. But folks are not up where the PDF intro document suggested. No not only being stomped on by FT8 when I an trying to use Olivia but by FT4 now when I am trying to use JS8. Grrr...

73, tom w7sua

On 4/29/2019 11:18 AM, Andrew OBrien wrote:
RC5 of WSJTX is now available at the usual site. This is the release that includes FT4 for testing
Andy K3UK