Date   

locked Re: Thanks

Michael Black
 

Yes...that's why his email said "next version".

de Mike W9MDB



From: YO2NAA <yo2naa@...>
To: Support@HamApps.groups.io
Sent: Sunday, July 16, 2017 8:33 AM
Subject: Re: [HamApps] Thanks

Dear Laurie,
 
My band activity only displays JT65 and JT9 but not FT8.
I use JTAlert 2.9.10
Your image is from a future version?
 
TNX, 73
Ady YO2NAA
 

From: Support@HamApps.groups.io [mailto: Support@HamApps.groups.io ] On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, July 15, 2017 2:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Thanks
 
Mike,

Thanks for the THANKS. I think it is somewhat misplaced as I didn't have any direct involvement in the development of FT8.

Regarding the FT8 activity on the bands, in the next release of JTAlert the BandActivity window includes tr/rx band counts of FT8 (taken from HamSpots.net).

This image was taken just now, not at the usage peak (yesterday I saw 20m activity peak at over 300 unique callsigns spotting FT8)



Note the FT8 spotters on 6m double that of JT65.

de Laurie, VK3AMA



locked Re: Thanks

Ady, YO2NAA
 

Dear Laurie,

 

My band activity only displays JT65 and JT9 but not FT8.

I use JTAlert 2.9.10

Your image is from a future version?

 

TNX, 73

Ady YO2NAA

 


From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, July 15, 2017 2:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Thanks

 

Mike,

Thanks for the THANKS. I think it is somewhat misplaced as I didn't have any direct involvement in the development of FT8.

Regarding the FT8 activity on the bands, in the next release of JTAlert the BandActivity window includes tr/rx band counts of FT8 (taken from HamSpots.net).

This image was taken just now, not at the usage peak (yesterday I saw 20m activity peak at over 300 unique callsigns spotting FT8)



Note the FT8 spotters on 6m double that of JT65.

de Laurie, VK3AMA


locked Re: POLL : Do you run JTAlert against multiple copies of WSJT-X and JTDX concurrently on the same PC? #POLL

Jay
 

Just another example of another feature that this software had that I didn't even know existed.
THANKS Laurie!

- Jay N1RWY

----

My only wish is that with FT8- the previously decoded list of stations stays visible longer- I like checking stations qrz pages and or sending direct message to kill time during my digital work. When using FT8 - they populate and display for a much shorter period than when in JT65 (I understand why) I only wish it could be tweaked a bit to display them longer. Besides that- amazing software as always! Jay N1RWY
Jay,

Activate the JTAlert Decodes History window. Be aware however, it will be somewhat polluted due to the current JTAlert one minute period and the incorrect handling of the 15sec period. The next release of JTAlert handles the new 15 sec period for this display as well.

The Decodes History window (use view menu or F9 hotkey), typically opens in a narrow vertical window or the last viewed width, it can be expanded/collapsed by using the two overlapping squares icon. The expanded and collapsed widths are fixed, but the vertical height is adjustable using the mouse.

de Laurie VK3AMA


locked Re: Logging FT8 QSO's

Art Roberts
 

Good point, thanks Mike. I guess that I am just in a 'logging rut' and feel that I have to do this immediately.

Art


On 7/16/2017 8:59 AM, Michael Black via Groups.Io wrote:
Isn't the only way to fix a mode on an eQSL entry is to edit each one on eQSL?  And then you won't match the prior entries that the others fixed.

Seems best to just wait a few weeks until things catch up.  Nobody is in that big a hurry to get an eQSL confirmation are they?

de Mike W9MDB



From: Art Roberts <w1aer@...>
To: Support@HamApps.groups.io
Sent: Sunday, July 16, 2017 7:55 AM
Subject: Re: [HamApps] Logging FT8 QSO's

I have been uploading my FT8 QSO's to eQSL by marking them as JT9 and then a comment about FT8. I have had 3 or 4 responses with their card marked the same. I am sure it doesn't count in their system, but as a 'QSL card....'  that is up for debate. I figure that once the adif situation gets worked out, I'll go back and correct things. I have changed FT8 to DATA in LOTW.
Art
W1AER

On 7/15/2017 12:07 PM, Michael Black via Groups.Io wrote:
Not that I know of....eQSL won't support FT8 until it's in the ADIF spec....several weeks away probably.

Right now uploading an FT8 to eQSL gets a warning message returned of invalid mode.  I'm not sure what they do with it.  I can't find my QSL's on eQSL for FT8 anywhere.
I think the warning may actually be saying it's rejected.
So will just have to re-upload the FT8's when eQSL catches up.

de Mike W9MDB





-- 
Art Roberts W1AER
Tariffville, CT  FN31ov
FT8, JT9, T10 and JT65





-- 
Art Roberts W1AER
Tariffville, CT  FN31ov
FT8, JT9, T10 and JT65



locked Re: Logging FT8 QSO's

Michael Black
 

Isn't the only way to fix a mode on an eQSL entry is to edit each one on eQSL?  And then you won't match the prior entries that the others fixed.

Seems best to just wait a few weeks until things catch up.  Nobody is in that big a hurry to get an eQSL confirmation are they?

de Mike W9MDB



From: Art Roberts <w1aer@...>
To: Support@HamApps.groups.io
Sent: Sunday, July 16, 2017 7:55 AM
Subject: Re: [HamApps] Logging FT8 QSO's

I have been uploading my FT8 QSO's to eQSL by marking them as JT9 and then a comment about FT8. I have had 3 or 4 responses with their card marked the same. I am sure it doesn't count in their system, but as a 'QSL card....'  that is up for debate. I figure that once the adif situation gets worked out, I'll go back and correct things. I have changed FT8 to DATA in LOTW.
Art
W1AER

On 7/15/2017 12:07 PM, Michael Black via Groups.Io wrote:
Not that I know of....eQSL won't support FT8 until it's in the ADIF spec....several weeks away probably.

Right now uploading an FT8 to eQSL gets a warning message returned of invalid mode.  I'm not sure what they do with it.  I can't find my QSL's on eQSL for FT8 anywhere.
I think the warning may actually be saying it's rejected.
So will just have to re-upload the FT8's when eQSL catches up.

de Mike W9MDB



From: Bill Barrett <billbarrett174@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 10:54 AM
Subject: Re: [HamApps] Logging FT8 QSO's

Any workaround for eQSL?
Thanks;
Bill W2PKY

On Sat, Jul 15, 2017 at 11:41 AM, Michael Black via Groups.Io <mdblack98@...> wrote:
Depends on your logging program.

Log4OM can map FT8 to Data and is uploading as FT8 to QRZ for me after the change to ModeList_user.csv adding an entry "FT8;FT8;DATA;FT8"
TQSL can map FT8 to Data

If you're doing QRZ through JTAlert I don't believe it supports remapping.  But it will probably be fixed in 2.9.11

de Mike W9MDB



From: Warren Greenberg via Groups.Io <warren.greenberg=yahoo.com@ groups.io>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 10:29 AM
Subject: [HamApps] Logging FT8 QSO's

 I loaded tge beta version, and I made several Q'S using FT8.
 The question I have, how do you log a FT8 QSO in QRZ, eQSL & LOTW (in LOTW I log as 'Data').

Warren - AE4WG





--
Bill Barrett
352-437-4758



-- 
Art Roberts W1AER
Tariffville, CT  FN31ov
FT8, JT9, T10 and JT65





locked Re: Logging FT8 QSO's

Art Roberts
 

I have been uploading my FT8 QSO's to eQSL by marking them as JT9 and then a comment about FT8. I have had 3 or 4 responses with their card marked the same. I am sure it doesn't count in their system, but as a 'QSL card....'  that is up for debate. I figure that once the adif situation gets worked out, I'll go back and correct things. I have changed FT8 to DATA in LOTW.

Art
W1AER


On 7/15/2017 12:07 PM, Michael Black via Groups.Io wrote:
Not that I know of....eQSL won't support FT8 until it's in the ADIF spec....several weeks away probably.

Right now uploading an FT8 to eQSL gets a warning message returned of invalid mode.  I'm not sure what they do with it.  I can't find my QSL's on eQSL for FT8 anywhere.
I think the warning may actually be saying it's rejected.
So will just have to re-upload the FT8's when eQSL catches up.

de Mike W9MDB



From: Bill Barrett <billbarrett174@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 10:54 AM
Subject: Re: [HamApps] Logging FT8 QSO's

Any workaround for eQSL?
Thanks;
Bill W2PKY

On Sat, Jul 15, 2017 at 11:41 AM, Michael Black via Groups.Io <mdblack98@...> wrote:
Depends on your logging program.

Log4OM can map FT8 to Data and is uploading as FT8 to QRZ for me after the change to ModeList_user.csv adding an entry "FT8;FT8;DATA;FT8"
TQSL can map FT8 to Data

If you're doing QRZ through JTAlert I don't believe it supports remapping.  But it will probably be fixed in 2.9.11

de Mike W9MDB



From: Warren Greenberg via Groups.Io <warren.greenberg=yahoo.com@ groups.io>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 10:29 AM
Subject: [HamApps] Logging FT8 QSO's

 I loaded tge beta version, and I made several Q'S using FT8.
 The question I have, how do you log a FT8 QSO in QRZ, eQSL & LOTW (in LOTW I log as 'Data').

Warren - AE4WG





--
Bill Barrett
352-437-4758



-- 
Art Roberts W1AER
Tariffville, CT  FN31ov
FT8, JT9, T10 and JT65



locked Re: Log40m

Michael Black
 

Looks like the RST file is just for setting defaul RST numbers when the field is blank.

As for eQSL I see no solution.  I'm just going to wait until FT8 is one of their modes and upload my QSLs.

eQSL does not have a DATA or DIGITAL mode like LOTW does (or PHONE either) so the same mapping that works in LOTW does not work for eQSL.


de Mike W9MDB



From: Dan Malcolm <pilotcfii@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 6:30 PM
Subject: Re: [HamApps] Log40m

I don’t know Mike.  The RSTmode.csv mod is supposed to allow Log4OM to keep the JT style RST reports instead of standard SSB style reports.  I don’t think the RSTmode.csv has anything to do with mapping data for confirmation matching.  That function belongs to modelist.csv.  Here is a quote from Terry (G4POP) on the Log4OM forum:
 
“Try juggling with the mode list entry order like JT65;FT8;JT65;FT8 combinations to see if a certain combination enables the download and also maintains the RST list correctly.”
 
Terry doesn’t mention DATA at all.  Since he doesn’t ust FT8 I think this is the limit of his help.  Seems more designed to get Log4OM to initially accept FT8.  I don’t think he (nor I at this point) is worried about weblog confirmations.  Once FT8 is accepted by ADIF, the collective weblogs will start handling all this correctly.  In the meantime I did TQSL mapping mod, and entered “FT8;FT8;DATA;FT8;” into ModeList_user.csv.  My Log4OM accepts FT8, eQSL does not, LotW does.  Looking back as far as June 30, I only have 2 FT8 confirmations from LoTW, although I still get the other digimodes and SSB.  Once the ADIF spec is changed and accepted by eQSL and LoTW, those site will be flooded by a backlog of uploads.
 
What is your take on all this?
 
Dan – K4SHQ
 
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, July 15, 2017 2:26 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Log40m
 
I understand the modelist_user.csv maps outgoing.  
 
I'm a bit fuzzy on the rstmode.csv -- If we download a DATA confirmatino from LOTW how is this mapping DATA back to FT8 for the match?
 
de Mike W9MDB 
 
 

From: Dan Malcolm <pilotcfii@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 1:36 PM
Subject: Re: [HamApps] Log40m
 
Mike,
Both the RSTmode.csv file and modelist.csv (Mode List button)file need to be changed.
RSTmode.csv 3rd line needs to be: “JT>JT|ROS|FSQ|MSK|FT8”.  I needed to do this to retain standard JT RST notation.
I think you can also edit RSTMode.csv via expert mode and the “RST JTxx mode” button.  That brings up a blank RSTmode.csv file, but it is the user version of the file.  I’m told that will also be loaded once it’s edited.  I edited the RSTmode.csv main file before I was told I shouldn’t do that, but mine is working.
 
Dan – K4SHQ
 
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, July 15, 2017 11:20 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Log40m
 
Settings/Options -- click "Enable Expert mode".  Then "Mode List".
 
Add this to the CSV file
 
FT8;FT8;DATA;FT8
 
Restart Log4OM
 
de Mike W9MDB
 
 

From: Chris Steele via Groups.Io <Kg4lqz@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 11:14 AM
Subject: [HamApps] Log40m
 
What is the way you change the mode file on log40m. I have not really used this logging program but do know where to find the expert part. I just don't know what to do or how to save a new mode file. De N4LHY
 
 



locked Re: Worked before SOLVED !

Rudolf Schaffer
 

RR Laurie, email running...

Le 16.07.2017 à 07:59, HamApps Support (VK3AMA) a écrit :
On 16/07/2017 3:22 PM, Rudolf Schaffer wrote:
Laurie,

You're 100% correct !

Just received EK1KE, present in log.adi with <APP_DXKeeper...> records and seen with B4 attribute.
"
<Band:3>20M <Call:5>EK1KE <APP_DXKEEPER_DXCCPREFIX:2>EK <DXCC:2>14 <Fr.....
"
I don't understand what was the "false" problem.

Very sorry for inconvenience and false "conclusion" !

My best 73,
Rudi, HB9ARI

Rudi,

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. I have a suspicion as to what might be happening, but I wont speculate openly as it is rather complicated and will likely add more to the confusion. ;-)

de Laurie VK3AMA
   


locked Re: Worked before SOLVED !

HamApps Support (VK3AMA)
 

On 16/07/2017 3:22 PM, Rudolf Schaffer wrote:
Laurie,

You're 100% correct !

Just received EK1KE, present in log.adi with <APP_DXKeeper...> records and seen with B4 attribute.
"
<Band:3>20M <Call:5>EK1KE <APP_DXKEEPER_DXCCPREFIX:2>EK <DXCC:2>14 <Fr.....
"
I don't understand what was the "false" problem.

Very sorry for inconvenience and false "conclusion" !

My best 73,
Rudi, HB9ARI

Rudi,

Please use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your Configuration and Session files for analysis. I have a suspicion as to what might be happening, but I wont speculate openly as it is rather complicated and will likely add more to the confusion. ;-)

de Laurie VK3AMA
   


locked Re: Worked before SOLVED !

Rudolf Schaffer
 

Laurie,

You're 100% correct !

Just received EK1KE, present in log.adi with <APP_DXKeeper...> records and seen with B4 attribute.
"
<Band:3>20M <Call:5>EK1KE <APP_DXKEEPER_DXCCPREFIX:2>EK <DXCC:2>14 <Fr.....
"
I don't understand what was the "false" problem.

Very sorry for inconvenience and false "conclusion" !

My best 73,
Rudi, HB9ARI

Le 15.07.2017 à 23:10, HamApps Support (VK3AMA) a écrit :
On 16/07/2017 4:57 AM, Rudolf Schaffer wrote:
...as i've imported into DXKeeper an adif file without the DXKeeper parameters some time ago withh success,
may be some parameters will be missing in the DXK's log, but they are not important for my own use.

73,
Rudi
Rudi,

Removing the DXKeeper adif "APP_DXKeeper" fields should not have corrected your problem. Those fields are perfectly valid and JTAlert will automatically ignore them as they are unneeded.

I routinely take a 20,000 QSO adif export from my DXKeeper log to test the ADIF functionality in JTAlert. There is never any need to strip out log specific fields like the
"APP_DXKeeper" fields.

I know you think this is resolved by removing the fields, but I believe the problem will reappear again. When it does, send me a support email (with a note of the Callsign and UTC time)  and a copy of your adif file.

de Laurie VK3AMA
   


locked Re: Worked before SOLVED !

Rudolf Schaffer
 

Laurie,

Thank you for your reply , explanations and help.

I will look for B4 call(s) active and verify all. Yesterday, 2 active and B4 calls were QRV (4O4A and RA9KT)
I hope to get an other call B4 today.

I will reactivate the "Worked B4" visual alert as i've done yesterday.

My best 73,
Rudi, HB9ARI

Le 15.07.2017 à 23:10, HamApps Support (VK3AMA) a écrit :
On 16/07/2017 4:57 AM, Rudolf Schaffer wrote:
...as i've imported into DXKeeper an adif file without the DXKeeper parameters some time ago withh success,
may be some parameters will be missing in the DXK's log, but they are not important for my own use.

73,
Rudi
Rudi,

Removing the DXKeeper adif "APP_DXKeeper" fields should not have corrected your problem. Those fields are perfectly valid and JTAlert will automatically ignore them as they are unneeded.

I routinely take a 20,000 QSO adif export from my DXKeeper log to test the ADIF functionality in JTAlert. There is never any need to strip out log specific fields like the
"APP_DXKeeper" fields.

I know you think this is resolved by removing the fields, but I believe the problem will reappear again. When it does, send me a support email (with a note of the Callsign and UTC time)  and a copy of your adif file.

de Laurie VK3AMA
   


locked Re: Log40m

Dan Malcolm <pilotcfii@...>
 

I don’t know Mike.  The RSTmode.csv mod is supposed to allow Log4OM to keep the JT style RST reports instead of standard SSB style reports.  I don’t think the RSTmode.csv has anything to do with mapping data for confirmation matching.  That function belongs to modelist.csv.  Here is a quote from Terry (G4POP) on the Log4OM forum:

 

“Try juggling with the mode list entry order like JT65;FT8;JT65;FT8 combinations to see if a certain combination enables the download and also maintains the RST list correctly.”

 

Terry doesn’t mention DATA at all.  Since he doesn’t ust FT8 I think this is the limit of his help.  Seems more designed to get Log4OM to initially accept FT8.  I don’t think he (nor I at this point) is worried about weblog confirmations.  Once FT8 is accepted by ADIF, the collective weblogs will start handling all this correctly.  In the meantime I did TQSL mapping mod, and entered “FT8;FT8;DATA;FT8;” into ModeList_user.csv.  My Log4OM accepts FT8, eQSL does not, LotW does.  Looking back as far as June 30, I only have 2 FT8 confirmations from LoTW, although I still get the other digimodes and SSB.  Once the ADIF spec is changed and accepted by eQSL and LoTW, those site will be flooded by a backlog of uploads.

 

What is your take on all this?

 

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, July 15, 2017 2:26 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Log40m

 

I understand the modelist_user.csv maps outgoing.  

 

I'm a bit fuzzy on the rstmode.csv -- If we download a DATA confirmatino from LOTW how is this mapping DATA back to FT8 for the match?

 

de Mike W9MDB 

 

 


From: Dan Malcolm <pilotcfii@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 1:36 PM
Subject: Re: [HamApps] Log40m

 

Mike,

Both the RSTmode.csv file and modelist.csv (Mode List button)file need to be changed.

RSTmode.csv 3rd line needs to be: “JT>JT|ROS|FSQ|MSK|FT8”.  I needed to do this to retain standard JT RST notation.

I think you can also edit RSTMode.csv via expert mode and the “RST JTxx mode” button.  That brings up a blank RSTmode.csv file, but it is the user version of the file.  I’m told that will also be loaded once it’s edited.  I edited the RSTmode.csv main file before I was told I shouldn’t do that, but mine is working.

 

Dan – K4SHQ

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Michael Black via Groups.Io
Sent: Saturday, July 15, 2017 11:20 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Log40m

 

Settings/Options -- click "Enable Expert mode".  Then "Mode List".

 

Add this to the CSV file

 

FT8;FT8;DATA;FT8

 

Restart Log4OM

 

de Mike W9MDB

 

 


From: Chris Steele via Groups.Io <Kg4lqz@...>
To: Support@HamApps.groups.io
Sent: Saturday, July 15, 2017 11:14 AM
Subject: [HamApps] Log40m

 

What is the way you change the mode file on log40m. I have not really used this logging program but do know where to find the expert part. I just don't know what to do or how to save a new mode file. De N4LHY

 

 


locked Re: Do you run JTAlert against multiple copies of WSJT-X and JTDX concurrently on the same PC?

Guy G4DWV 4X1LT
 

Hi,

 

It is very easy already to run multiple instances of WSJT-X and JTDX concurrently already. It is so unobtrusive you did not even notice, hi hi.

 

73 de Guy G4DWV 4X1LT


locked Re: Logging FT8 QSO's

John Etling
 

… OR simply be patient a few weeks or so, hold the QSOs and waiting until the ADIF council puts it in as a recognized mode. Once they do that eQSL, LotW and other online logging services will then recognize it.

 

I’m Just Sayin’

73 de K3JAE

 

John

 

 

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, July 15, 2017 15:56
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Logging FT8 QSO's

 

On 16/07/2017 1:41 AM, Michael Black via Groups.Io wrote:

If you're doing QRZ through JTAlert I don't believe it supports remapping.  But it will probably be fixed in 2.9.11

 

Mike,

No it wont.
JTAlert will only ever log the mode used, no will not be any remapping to get around the online log services that don't support the mode. That is something the end user will need to take care of by utilising the facilities in their primary logger if it supports remapping and the online log in question.

de Laurie VK3AMA
   


locked Re: FT8 JTAlert Not In Sync?

John Etling
 

I would also support and encourage this option.. when you finally are able to slow down and work it in!

 

I’m Just Sayin’

73 de K3JAE

 

John

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of HamApps Support (VK3AMA)
Sent: Saturday, July 15, 2017 15:52
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FT8 JTAlert Not In Sync?

 

On 16/07/2017 1:34 AM, kkinderen@... wrote:

I wonder if an additional filter could be put onto JTAlert to only display CQs from needed/wanted calls and ignore all other transmissions?


Kev,

That option has been on my todo list for awhile. It wont be in the next release however.

de Laurie VK3AMA
   


locked Re: Testing Messages : Please post to this message thread

Howard Grams
 

testing 1 2 3 4


locked Re: POLL : Do you run JTAlert against multiple copies of WSJT-X and JTDX concurrently on the same PC? #POLL

HamApps Support (VK3AMA)
 

On 16/07/2017 1:45 AM, Guy G4DWV/4X1LT wrote:
I tried FT8 and find it too hectic, which is probably why WSJT-X has introduced some automation for QSOs. I have got too used to doing other stuff when working T10 and JT65/9, like watching YouTube videos and checking QRZ pages.

One copy of JTDX is enough for me. I agree with Jay about finding features in JTAlert. I have found so much new stuff too, so much that I need to work my way though all the options and reconfigure most of them. Thanks Laurie, could not work JT modes without JTAlert.

73 de Guy G4DWV 4X1LT

Thanks Guy,

I am not on-air at the moment (have been for just over 12 months), so am unable to test FT8 live. BUT, during my testing with FT8 I quickly realised, it wont be a mode for me to use regularly. I will likely only ever use it to try and work a much needed DXCC or State that is only on FT8, otherwise I will be using JT65/JT9. I like my leisure time at the end of a TX period. the 2 secs for FT8 is too short for me. Now if a new 30sec t/r period mode was introduced with say 5 or more secs of decision time, that would get me interested.

de Laurie VK3AMA
   


locked Re: POLL : Do you run JTAlert against multiple copies of WSJT-X and JTDX concurrently on the same PC? #POLL

HamApps Support (VK3AMA)
 

On 16/07/2017 1:30 AM, Jay wrote:
My only wish is that with FT8- the previously decoded list of stations stays visible longer- I like checking stations qrz pages and or sending direct message to kill time during my digital work.  When using FT8 - they populate and display for a much shorter period than when in JT65 (I understand why) I only wish it could be tweaked a bit to display them longer.

Besides that- amazing software as always!

Jay N1RWY
Jay,

Activate the JTAlert Decodes History window. Be aware however, it will be somewhat polluted due to the current JTAlert one minute period and the incorrect handling of the 15sec period. The next release of JTAlert handles the new 15 sec period for this display as well.

The Decodes History window (use view menu or F9 hotkey), typically opens in a narrow vertical window or the last viewed width, it can be expanded/collapsed by using the two overlapping squares icon. The expanded and collapsed widths are fixed, but the vertical height is adjustable using the mouse.

de Laurie VK3AMA
   


locked Re: Worked before SOLVED !

HamApps Support (VK3AMA)
 

On 16/07/2017 4:57 AM, Rudolf Schaffer wrote:
...as i've imported into DXKeeper an adif file without the DXKeeper parameters some time ago withh success,
may be some parameters will be missing in the DXK's log, but they are not important for my own use.

73,
Rudi
Rudi,

Removing the DXKeeper adif "APP_DXKeeper" fields should not have corrected your problem. Those fields are perfectly valid and JTAlert will automatically ignore them as they are unneeded.

I routinely take a 20,000 QSO adif export from my DXKeeper log to test the ADIF functionality in JTAlert. There is never any need to strip out log specific fields like the
"APP_DXKeeper" fields.

I know you think this is resolved by removing the fields, but I believe the problem will reappear again. When it does, send me a support email (with a note of the Callsign and UTC time)  and a copy of your adif file.

de Laurie VK3AMA
   


locked Re: Do you run JTAlert against multiple copies of WSJT-X and JTDX concurrently on the same PC?

HamApps Support (VK3AMA)
 

On 16/07/2017 3:26 AM, Mike Horn wrote:
I would hate to see WSJT-X or JTAlert  suffer to satisfy the minority of individuals who need to run several instances of the software.  The same should be promulgated for the majority.
Mike,

JTAlert functionality wont be compromised. Multi-instance support will remain. The poll was created to see who runs multiple WSJT-X and JTDX instances simultaneously and if they would be affected by any decision to no longer support that scenario with JTAlert.

de Laurie VK3AMA