Date   

locked Re: Worked before

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Rudolf Schaffer
Sent: Saturday, July 15, 2017 4:47 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Worked before

Laurie,

It's in the other direction, to "initiate" the JTAlertX's log.adi, i've exported all my FT8 QSOs from DXKeeper as a standard adif
format into a transfert.adi file from PC1.
After, i've copied the content of this file into log.adi (PC2) just after the header :
"
<ADIF_VER:5>2.2.7
<ProgramID:8>JTAlertX
<ProgramVersion:6>2.9.10
<APP_JTAlertX_Created:23>2017/07/15 06:56:06 UTC <EOH> <Band:3>20M <Call:5>PY2MR <APP_DXKEEPER_DXCCPREFIX:2>PY <DXCC:3>108
<Freq:9>14.075767 <Mode:3>FT8 <Operator:6>HB9ARI <QSO_DATE:8>20170714 <TIME_OFF:6>182900 <TIME_ON:6>182900 <RST_Rcvd:3>-05
<RST_Sent:3>+00 <Comment:15>50W K3 HEX high <CONT:2>SA <ITUZ:2>15 <CQZ:2>11 <GRIDSQUARE:4>GG66 <PFX:3>PY2 <State:2>SP
<STATION_CALLSIGN:6>HB9ARI <OWNER_CALLSIGN:6>HB9ARI <LAT:11>S023 30.000 <LON:11>W047 00.000 <APP_DXKeeper_LotW_MEMBER:1>Y
<APP_DXKeeper_SELECT:1>Y <EQSL_QSL_SENT:1>R <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>R <LOTW_QSLSDATE:8>20170714
<APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR> .
.
.
.
<Band:3>20M <Call:5>RA9KT <APP_DXKEEPER_DXCCPREFIX:3>UA0 <DXCC:2>15 <Freq:9>14.076994 <Mode:3>FT8 <Operator:6>HB9ARI
<QSO_DATE:8>20170707 <TIME_OFF:6>145700 <TIME_ON:6>145700 <RST_Rcvd:3>-09 <RST_Sent:3>-13 <Comment:31>70W K3 HEXBEAM high 1st FT8
QSO <CONT:2>AS <CQZ:2>17 <GRIDSQUARE:4>MO27 <PFX:3>RA9 <State:2>YN <STATION_CALLSIGN:6>HB9ARI <OWNER_CALLSIGN:6>HB9ARI <LAT:11>N057
30.000 <LON:11>E065 00.000 <APP_DXKeeper_SELECT:1>Y <EQSL_QSL_SENT:1>R <LOTW_QSL_SENT:1>U <LOTW_QSL_RCVD:1>R
<LOTW_QSLSDATE:8>20170714 <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR>
<CALL:4>4O4A<QSO_DATE:8>20170715<TIME_ON:6>080400<TIME_OFF:6>080400<FREQ:9>14.075402<FREQ_RX:9>14.075402<BAND:3>20m<BAND_RX:3>20m<MO
DE:3>FT8<RST_SENT:3>+00<RST_RCVD:3>-01<GRIDSQUARE:4>JN92<DISTANCE:4>1066<A_INDEX:1>4<K_INDEX:1>1<SFI:2>94<COMMENT:15>50W K3 HEX
high<CQZ:2>15<ITUZ:2>28<PFX:3>4O4<CONT:2>EU<DXCC:3>514<COUNTRY:10>Montenegro<MY_GRIDSQUARE:6>JN37nc<MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<S
TATION_CALLSIGN:6>HB9ARI<QSO_COMPLETE:1>Y<EOR>
"
We can see that DXKeeper record format begin with: "<Band:3> 20M...."
and log.adi format begin with: "<CALL:4>4O4A<QSO_DATE:8>20..."

ADIF does not specify an order in which fields must appear.
The JTAlertX ADIF above describes a QSO with PY2MR.
The DXKeeper ADIF above describes two QSOs, one with RA9KT, and one with 404A.
73,

Dave, AA6YQ


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

Mike N8FRI
 

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.


locked Re: Log40m

Chris Steele <Kg4lqz@...>
 

Thanks Mike. I wasn't moving it to the CSV file. I will take care of that when I get back to the house.


locked Re: Logging FT8 QSO's

Bill Barrett
 

Thanks Mike for the reply.
Sad situation.

Bill W2PKY

On Sat, Jul 15, 2017 at 12:07 PM, Michael Black via Groups.Io <mdblack98@...> 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





--
Bill Barrett
352-437-4758


locked Re: Log40m

Michael Black
 

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 Log40m

Chris Steele <Kg4lqz@...>
 

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: Logging FT8 QSO's

Michael Black
 

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



locked Re: FT8 JTAlert Not In Sync?

neil_zampella
 

Kev,

you're not doing anything wrong.  JT-Alert in its current form just can't keep up.  Its still on a one minute JT65/JT9 cycle, whereas FT8 is 15 seconds.     For now what I've done is checked the "Show DXCC entiry and worked before status" checkbox.   What this does is show callsigns I've not worked before in Violet or DARK Purple.      This works quite well.

Neil, KN3ILZ


locked Re: JT Alert and FT8

Murf <n7uvh01@...>
 

having no troubles working the new mode.
like the auto mode.  been fun to play with and
something or mode to do WAS again.
Murf


locked Re: Logging FT8 QSO's

Bill Barrett
 

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


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

Guy G4DWV 4X1LT
 

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


locked Re: Logging FT8 QSO's

Michael Black
 

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@...>
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



locked Re: FT8 JTAlert Not In Sync?

kkinderen@...
 

After reading some more threads I realize this is a known issue that is being worked on. I also understand I need to work on hand-eye coordination in this new mode and be prepared to use it differently than I use JT9/JT65. 

I wonder if an additional filter could be put onto JTAlert to only display CQs from needed/wanted calls and ignore all other transmissions? This could reduce the manual scanning needed (eye part of the coordination) and make the user more efficient in the 2 seconds allotted for a response.

 --
73,
Kev K4VD


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

Jay
 

I would vote
1
Or
4

I keep finding new and supercool-I-can't-live-without features in your software every time I use it. :-)

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


locked Logging FT8 QSO's

Warren Greenberg
 

 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


locked Re: JT Alert and FT8

kkinderen@...
 

On Tue, Jul 11, 2017 at 08:05 pm, HamApps Support (VK3AMA) wrote:
Exactly!
With FT8, there is no longer a leisurely 10+ seconds to decide who to respond to based on a JTAlert alert.
Maybe to support the new workflow, when clicking an FT8 CQ in JTAlert it brings you to the proper frequency but doesn't initiate the reply. The operator has to initiate the reply when he or she is ready.

I can get my arms around JTAlert just letting me know what it has seen in the last minute but if it could also get me on the right frequency so that CQ shows up in the Rx Frequency list on the next call I'm in a better position to jump on it at the right time. I also think WSJT-X could be modified to prevent initiating transmit if more than a couple of seconds have passed to help avoid QRM.

Sheesh... FT8 has been harder to work than CW! (just kidding)
 
--
73,
Kev K4VD


locked FT8 JTAlert Not In Sync?

kkinderen@...
 

FT8 is so quick for this old man I keep messing up and responding to a CQ too late. Thanks, by the way, to the unidentified FT8 user for their help in pointing out how much of a LID I am. Real foul of you.

At any rate, this might just be a feature I don't understand yet. I created a little video that matches the timeline here. Is this a bug or is this how JTAlert should work? The YouTube video is here: 2017-07-15-10-07-06

This is what I'm seeing:

140700 N2ADV is calling CQ. When done, his call shows in JTAlert [ok]
140715 N2ADV is listening. When done, his call still shows in JTAlert [??]
140730 N2ADV is calling CQ. When done, his call flickers and then disappears in JTAlert [??]
140745 N2ADV is listening. When done, his call is not in JTAlert [ok]
140800 N2ADV is calling CQ. When done, his call shows in JTAlert [ok]

The timeline repeats.It seems to me after 140715 N2ADV's call should not show up in JTAlert because he didn't send anything. Then, when he does send another CQ at 140730 his call disappears (after a brief flicker).

Is it something I have setup incorrectly?


While I'm asking questions, how can I avoid starting my reply to a CQ seconds late? It seems to me the moment a decode is complete people are already sending replies. Do I just have to be that quick to play in this mode and cause problems for or incur the wrath of my fellow hobbyists?

And finally a suggestion... if you see someone like me goofing up and causing problems, send them a text message or look up the person's email and drop them a polite note with your thoughts. Seeing the following doesn't tell me anything other than you are probably a lonely person and I might have a technical problem but don't know what it is.

000630 -5 0.2 1266 ~ K4VD QRM LID
000645 -7 0.2 1266 ~ K4VD QRM LID

That was a rant. I couldn't help it. Mean people suck.

73,
Kev K4VD



--
73,
Kev K4VD


locked Re: Worked before

Rudolf Schaffer
 

Laurie,

It's in the other direction, to "initiate" the JTAlertX's log.adi, i've exported all my FT8 QSOs from DXKeeper as a standard adif format into a transfert.adi file from PC1.
After, i've copied the content of this file into log.adi (PC2) just after the header :
"
<ADIF_VER:5>2.2.7
<ProgramID:8>JTAlertX
<ProgramVersion:6>2.9.10
<APP_JTAlertX_Created:23>2017/07/15 06:56:06 UTC
<EOH>
<Band:3>20M <Call:5>PY2MR <APP_DXKEEPER_DXCCPREFIX:2>PY <DXCC:3>108 <Freq:9>14.075767 <Mode:3>FT8 <Operator:6>HB9ARI <QSO_DATE:8>20170714 <TIME_OFF:6>182900 <TIME_ON:6>182900 <RST_Rcvd:3>-05 <RST_Sent:3>+00 <Comment:15>50W K3 HEX high <CONT:2>SA <ITUZ:2>15 <CQZ:2>11 <GRIDSQUARE:4>GG66 <PFX:3>PY2 <State:2>SP <STATION_CALLSIGN:6>HB9ARI <OWNER_CALLSIGN:6>HB9ARI <LAT:11>S023 30.000 <LON:11>W047 00.000 <APP_DXKeeper_LotW_MEMBER:1>Y <APP_DXKeeper_SELECT:1>Y <EQSL_QSL_SENT:1>R <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>R <LOTW_QSLSDATE:8>20170714 <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR>
.
.
.
.
<Band:3>20M <Call:5>RA9KT <APP_DXKEEPER_DXCCPREFIX:3>UA0 <DXCC:2>15 <Freq:9>14.076994 <Mode:3>FT8 <Operator:6>HB9ARI <QSO_DATE:8>20170707 <TIME_OFF:6>145700 <TIME_ON:6>145700 <RST_Rcvd:3>-09 <RST_Sent:3>-13 <Comment:31>70W K3 HEXBEAM high 1st FT8 QSO <CONT:2>AS <CQZ:2>17 <GRIDSQUARE:4>MO27 <PFX:3>RA9 <State:2>YN <STATION_CALLSIGN:6>HB9ARI <OWNER_CALLSIGN:6>HB9ARI <LAT:11>N057 30.000 <LON:11>E065 00.000 <APP_DXKeeper_SELECT:1>Y <EQSL_QSL_SENT:1>R <LOTW_QSL_SENT:1>U <LOTW_QSL_RCVD:1>R <LOTW_QSLSDATE:8>20170714 <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR>
<CALL:4>4O4A<QSO_DATE:8>20170715<TIME_ON:6>080400<TIME_OFF:6>080400<FREQ:9>14.075402<FREQ_RX:9>14.075402<BAND:3>20m<BAND_RX:3>20m<MODE:3>FT8<RST_SENT:3>+00<RST_RCVD:3>-01<GRIDSQUARE:4>JN92<DISTANCE:4>1066<A_INDEX:1>4<K_INDEX:1>1<SFI:2>94<COMMENT:15>50W K3 HEX high<CQZ:2>15<ITUZ:2>28<PFX:3>4O4<CONT:2>EU<DXCC:3>514<COUNTRY:10>Montenegro<MY_GRIDSQUARE:6>JN37nc<MY_CQ_ZONE:1>0<MY_ITU_ZONE:1>0<STATION_CALLSIGN:6>HB9ARI<QSO_COMPLETE:1>Y<EOR>
"
We can see that DXKeeper record format begin with: "<Band:3> 20M...."
and log.adi format begin with: "<CALL:4>4O4A<QSO_DATE:8>20..."

For the moment, i've not done an import into DXKeeper to updates my log.

Not easy to explain that in English language...
73 QRO,
Rudi, HB9ARI


Le 15.07.2017 à 10:29, HamApps Support (VK3AMA) a écrit :
On 15/07/2017 6:20 PM, Rudolf Schaffer wrote:
Laurie,

Thank you for your quick reply and help !

I think that the "problem" is found.
I've just done a FT8 QSO and automatic logging into JTAlertX's log.adi is working perfectly !
BUT, i can see that adif format between imported QSOs fro DXKeeper is not the same as JTAlertXs log.adi.
I will search how to "adjust" the "DXK's format to the log.adi's format...
The last "test" QSO's call (4O4A) , written into log.adi is perfectly recognized as "B4" and not displayed.

Thank you for your work Laurie.

My best 73,
Rudi, HB9ARI

Rudi,

JTAlert uses standard ADIF tags and DXKeeper recognises the ADIF standard, it should be able to import the the JTAlert adi file without problem. I would be very surprised if there was an incompatibility.

Can you give an example of what DXKeeper doesn't like about the adi file, which part do you think is wrong?

de Laurie VK3AMA
   


locked Re: Worked before

HamApps Support (VK3AMA)
 

On 15/07/2017 6:20 PM, Rudolf Schaffer wrote:
Laurie,

Thank you for your quick reply and help !

I think that the "problem" is found.
I've just done a FT8 QSO and automatic logging into JTAlertX's log.adi is working perfectly !
BUT, i can see that adif format between imported QSOs fro DXKeeper is not the same as JTAlertXs log.adi.
I will search how to "adjust" the "DXK's format to the log.adi's format...
The last "test" QSO's call (4O4A) , written into log.adi is perfectly recognized as "B4" and not displayed.

Thank you for your work Laurie.

My best 73,
Rudi, HB9ARI

Rudi,

JTAlert uses standard ADIF tags and DXKeeper recognises the ADIF standard, it should be able to import the the JTAlert adi file without problem. I would be very surprised if there was an incompatibility.

Can you give an example of what DXKeeper doesn't like about the adi file, which part do you think is wrong?

de Laurie VK3AMA
   


locked Re: Worked before

Rudolf Schaffer
 

Laurie,

Thank you for your quick reply and help !

I think that the "problem" is found.
I've just done a FT8 QSO and automatic logging into JTAlertX's log.adi is working perfectly !
BUT, i can see that adif format between imported QSOs fro DXKeeper is not the same as JTAlertXs log.adi.
I will search how to "adjust" the "DXK's format to the log.adi's format...
The last "test" QSO's call (4O4A) , written into log.adi is perfectly recognized as "B4" and not displayed.

Thank you for your work Laurie.

My best 73,
Rudi, HB9ARI

Le 15.07.2017 à 10:04, HamApps Support (VK3AMA) a écrit :
On 15/07/2017 5:51 PM, Rudolf Schaffer wrote:
Hello,

I'm using JTAlertX 2.9.10 with WSJT-X only for FT8 mode.
I'm using the JTAlertX's log.adi only for FT8 and ave verified the content; all is ok.
I've done a scan for this log.
I choose to NOT display the worked before calls but they are still displayed.

What i'm missing ?

Thank you for your help.

73 QRO,
Rudi, HB9ARI
Rudi,

In addition to my last email, send me your adi file to VK3AMA.Ham.Apps [at] gmail.com

de Laurie VK3AMA