|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Jack. I have set JTAlert to auto start wsjt and gridtracker when I click on JTAlert’s shortcut. This means I can’t forget to start JTAlert which I sometimes did! 73, Antony G4CUS
Jack. I have set JTAlert to auto start wsjt and gridtracker when I click on JTAlert’s shortcut. This means I can’t forget to start JTAlert which I sometimes did! 73, Antony G4CUS
|
By
Antony
· #33042
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Hey Ron! I always let JTALERT handle everything and have never had an issue except when I forget to start it Just have it send to HRD and turn off sending from wsjtx Hope to catch you in the VHF conte
Hey Ron! I always let JTALERT handle everything and have never had an issue except when I forget to start it Just have it send to HRD and turn off sending from wsjtx Hope to catch you in the VHF conte
|
By
Jack Plum
· #33037
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Mike, Not sure if you have visibility into the JTAlert forum. In the event you don't attached is the response I posted. The reference to Chris (VK2BYI) is regarding his post stating this was a known H
Mike, Not sure if you have visibility into the JTAlert forum. In the event you don't attached is the response I posted. The reference to Chris (VK2BYI) is regarding his post stating this was a known H
|
By
Ronald Panetta
· #33034
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Chris is 100% correct. The issue is an HRD defect and will be fixed in the next release. I received the following directly from Mike VK4EIE (WA9PIE): ----Begin Quote---- Ron, Ferry is absolutely incor
Chris is 100% correct. The issue is an HRD defect and will be fixed in the next release. I received the following directly from Mike VK4EIE (WA9PIE): ----Begin Quote---- Ron, Ferry is absolutely incor
|
By
Ronald Panetta
· #33032
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Another benefit of Logging direct to HRDLogbook from JTAlert, any QSOs that are logged when JTAlert/WSJT-X is not being used, say your RTTY, PSK, SSB & CW QSOs, will still be available to JTAlert when
Another benefit of Logging direct to HRDLogbook from JTAlert, any QSOs that are logged when JTAlert/WSJT-X is not being used, say your RTTY, PSK, SSB & CW QSOs, will still be available to JTAlert when
|
By
HamApps Support (VK3AMA)
· #33026
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Ron, Your best option is to enable HRD logging in JTAlert. This avoids the QSO forwarding mechanism and has several benefits. You get full access to the alerting facilities and B4 reporting of JTAlert
Ron, Your best option is to enable HRD logging in JTAlert. This avoids the QSO forwarding mechanism and has several benefits. You get full access to the alerting facilities and B4 reporting of JTAlert
|
By
HamApps Support (VK3AMA)
· #33023
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Tnx Chris. An ADIF parser that depends on field order (when the adif spec has no such requirement) is crazy. What did they get a first year student programmer to write the code? Treating an adif recor
Tnx Chris. An ADIF parser that depends on field order (when the adif spec has no such requirement) is crazy. What did they get a first year student programmer to write the code? Treating an adif recor
|
By
HamApps Support (VK3AMA)
· #33022
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
+ AA6YQ comments below We only Support UDP Logging from N1MM and WSJTX not JTAlert, it has its own defects. Since QSO Forward works perfect for the 1st 2 there is an issue in JTALert. + Whoever wrote
+ AA6YQ comments below We only Support UDP Logging from N1MM and WSJTX not JTAlert, it has its own defects. Since QSO Forward works perfect for the 1st 2 there is an issue in JTALert. + Whoever wrote
|
By
Dave AA6YQ
· #33010
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
And below is another response from HRD support. Neither message touches on a HRD defect. Wish they would admit to it as it is causing a lot of effort on others trying to fault isolate. Ronald, You nee
And below is another response from HRD support. Neither message touches on a HRD defect. Wish they would admit to it as it is causing a lot of effort on others trying to fault isolate. Ronald, You nee
|
By
Ronald Panetta
· #33008
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Thanks for that insight. I just last week opened up a ticket with HRD and here is their response. Ronald, We only Support UDP Logging from N1MM and WSJTX not JTAlert, it has its own defects. Since QSO
Thanks for that insight. I just last week opened up a ticket with HRD and here is their response. Ronald, We only Support UDP Logging from N1MM and WSJTX not JTAlert, it has its own defects. Since QSO
|
By
Ronald Panetta
· #33007
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
There is a known defect in HRD Logbook where UDP broadcasts received on the QSO Forwarding for WSJT-X port may not log correctly depending upon the ADIF field order. Of course, the field order in ADIF
There is a known defect in HRD Logbook where UDP broadcasts received on the QSO Forwarding for WSJT-X port may not log correctly depending upon the ADIF field order. Of course, the field order in ADIF
|
By
Chris VK2BYI
· #33006
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Bill: First let me start out by saying I just installed a new PC in the shack. Prior to this I did not do much digital as they old machine was way too slow. So with the new machine, I installed the la
Bill: First let me start out by saying I just installed a new PC in the shack. Prior to this I did not do much digital as they old machine was way too slow. So with the new machine, I installed the la
|
By
Ronald Panetta
· #33005
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
I use the latest versions of WSJT, JTALERT, GRIDTRACKER and HRD without any problems. They work well together. I echo Roger’s plea for HRD support to continue despite the underlying problems! Carry on
I use the latest versions of WSJT, JTALERT, GRIDTRACKER and HRD without any problems. They work well together. I echo Roger’s plea for HRD support to continue despite the underlying problems! Carry on
|
By
Antony
· #33003
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Hi Laurie. I agree with Roger, as you know I been around for some time. I have not had an issue with logging to HRD for years now. I was there for the dust up a few years ago with HRD, and you have do
Hi Laurie. I agree with Roger, as you know I been around for some time. I have not had an issue with logging to HRD for years now. I was there for the dust up a few years ago with HRD, and you have do
|
By
kk7h@...
· #33002
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Laurie, Please do not discontinue logging to HRD 6.x. It works perfectly fine for most of us, and we appreciate all of your efforts.
Laurie, Please do not discontinue logging to HRD 6.x. It works perfectly fine for most of us, and we appreciate all of your efforts.
|
By
Roger M
· #33001
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Ron-- I have no issues with logging date/time in HRD. Setup is HRD 6.7.0.277; WSJT 2.2.2; JT Alert 2.16.8 Please note that in WSJT, Secondary UDP 2333 box is not checked off in the Reporting Tab I fou
Ron-- I have no issues with logging date/time in HRD. Setup is HRD 6.7.0.277; WSJT 2.2.2; JT Alert 2.16.8 Please note that in WSJT, Secondary UDP 2333 box is not checked off in the Reporting Tab I fou
|
By
William W1WAB
· #33000
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Here’s my chime FWIW. I used HRD for a long time; started with it many years ago and stayed stuck with it. I finally gave up and was able to wean myself off the last piece of it and complete the move
Here’s my chime FWIW. I used HRD for a long time; started with it many years ago and stayed stuck with it. I finally gave up and was able to wean myself off the last piece of it and complete the move
|
By
Russ Ravella
· #32998
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
Ron, I see nothing wrong with that ADIF record you captured. The QSO_DATE is set and is of the correct format. I can't explain why HRD is not accepting the <QSO_DATE> field. Is all other data being lo
Ron, I see nothing wrong with that ADIF record you captured. The QSO_DATE is set and is of the correct format. I can't explain why HRD is not accepting the <QSO_DATE> field. Is all other data being lo
|
By
HamApps Support (VK3AMA)
· #32995
·
|
|
QSO dates missing in HRD from JTAlert UDP/2333
#HRD
I encountered the same issue recently posted by David over a year ago here: https://hamapps.groups.io/g/Support/message/26679?p=,,,20,0,0,0::relevance,,hrd+udp+2333,20,2,0,67711266. Reference his scre
I encountered the same issue recently posted by David over a year ago here: https://hamapps.groups.io/g/Support/message/26679?p=,,,20,0,0,0::relevance,,hrd+udp+2333,20,2,0,67711266. Reference his scre
|
By
Ronald Panetta
· #32994
·
|
|
SOLVED*** HRD Radio control causes JT Alert/JTDX to fail. #JTDX #HRD SOLVED***
#JTDX
#HRD
Thanks to all that responded; All were all helpful. I did not think the problem was in the JTDX settings as de Laurie VK3AMA suggested. However, he was correct. Based on his comments I held everything
Thanks to all that responded; All were all helpful. I did not think the problem was in the JTDX settings as de Laurie VK3AMA suggested. However, he was correct. Based on his comments I held everything
|
By
Ken
· #32878
·
|