Date   

locked mixw

David Pykett
 

Hi Laurie
 
I may have missed it but is there any thoughts on JT-Alert being able to access the mixw log? I am using Mixw 3.01.
 
73
Dave
G0IIQ
 
 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Don Leitch <don@...>
 

Tnx checking it out now

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Dave Wright
Sent: Thursday, 20 October 2011 8:01 a.m.
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

A program developed by WD5EAE that supported LoTW and EQSL uploads/downloads, as well as mass-updates by QRZ..and a few other things as well…all before HRD supported it directly.  I still use it only when I need to do mass updates, but it works well and quickly.

 

www.wd5eae.org/Software.html

 

It hasn't been updated in awhile, but it doesn't need to be. 

 

73

 

Dave


-- 
Dave Wright

K3DCW

 

"Real radio bounces off the sky"

 

On Wednesday, October 19, 2011 at 2:54 PM, Don Leitch wrote:

 

Dave now you have me again whats HRD utitilites

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Dave Wright
Sent: Thursday, 20 October 2011 1:00 a.m.
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Jeff,

 

You can either open the window and click the button as you said, or I use HRD Utilities.  It can do group updates…1, 2, 5, 10, all QSOs at once.  And you can select the fields you want to update…for example, I don't have it update the Grid as I want to use what is listed in JT65, but I do like to get names and other info.  

 

It is still a lot easier than typing them in one by one.  


-- 
Dave Wright

K3DCW

 

"Real radio bounces off the sky"

 

On Wednesday, October 19, 2011 at 7:56 AM, K2AK - Jeff wrote:

 

KD,

 

Thanks for the response. The only way I know how to get HRD V5 to update the QRZ information (name, QTH, grid cords, etc) is to open (modify) the contact after it was logged and then click the QRZ button in the ALE window. Are you able to get HRD to update the record automatically without opening the record?

 

Thanks again and 73,

Jeff – K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of K. D. Sarchet
Sent: Wednesday, October 19, 2011 4:27 AM
To: Ham-Apps@...
Subject: RE: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41

 

 


locked Re: [Ham-Apps] Lost Logbook

Laurie, VK3AMA <groups03@...>
 

Hi Scott,

If you are uncomfortable with manually editing your log file, email it
to me direct and I will correct it
The problem is that the DXCC code field,which is a number, in your HRDV5
log has no data and HRD chokes.

The only way I have been able to reproduce that happening is to log a
callsign using the JT65-HF "Log Contact" window and entering the
Callsign there while there is no callsign entered on the main JT65-HF
window in the "TX to Call Sign" field. JT-Alert uses the callsign on the
main window to determine the DXCC, CQ, ITU, etc. Since that data is
missing, because of the no callsign, no DXCC is Sent to the HRD log.

I am working on the fix. I had never anticipated people would log
without first having the QSO entered on the main screen.

de Laurie, VK3AMA

On 19-October-2011 23:39, Scott wrote:
Laurie,

I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.

Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!

73 Scott
KN3A


08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
08:29:46 Database Open status 1
08:29:46 Database Opening 'HRD My Logbook - Access'
08:29:46 Database Open status 1
08:29:46 Database Timeout ..: 120 seconds
08:29:46 Database Open status 1

08:29:47 Reload Error: Getting 24011 records -
08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,COL_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,COL_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC
08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second

08:29:47 General Loading class CLogfileFrame



locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Dave Wright <hfradiopro@...>
 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Dave Wright <hfradiopro@...>
 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Don Leitch <don@...>
 

Dave now you have me again whats HRD utitilites

Don zl1atb

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Dave Wright
Sent: Thursday, 20 October 2011 1:00 a.m.
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Jeff,

 

You can either open the window and click the button as you said, or I use HRD Utilities.  It can do group updates…1, 2, 5, 10, all QSOs at once.  And you can select the fields you want to update…for example, I don't have it update the Grid as I want to use what is listed in JT65, but I do like to get names and other info.  

 

It is still a lot easier than typing them in one by one.  


-- 
Dave Wright

K3DCW

 

"Real radio bounces off the sky"

 

On Wednesday, October 19, 2011 at 7:56 AM, K2AK - Jeff wrote:

 

KD,

 

Thanks for the response. The only way I know how to get HRD V5 to update the QRZ information (name, QTH, grid cords, etc) is to open (modify) the contact after it was logged and then click the QRZ button in the ALE window. Are you able to get HRD to update the record automatically without opening the record?

 

Thanks again and 73,

Jeff – K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of K. D. Sarchet
Sent: Wednesday, October 19, 2011 4:27 AM
To: Ham-Apps@...
Subject: RE: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41

 


locked Lost Logbook

Scott
 

Laurie,

I have had no problem logging from the JT Alert since I downloaded it on Sunday, and have probably logged over 100 QSO's successfully. This morning I worked two JT65 QSO's on 10 meters and logged them. When I did a refresh on the logbook, I got an error (see logfile). I tried to do a repair of the database and got a message Driver's ConfigDSN, ConfigDriver, or COnfigTranslator failed.

Can you help me out here? I have Win7 64 bit, the latest V5.2893, and 1.0.7. Any ideas please? Until this morning it's been completely trouble free and I love the JT Alert update!

73 Scott
KN3A


08:29:46 Database Opening 'DSN=HRD My Logbook - Access'
08:29:46 Database Open status 1
08:29:46 Database Opening 'HRD My Logbook - Access'
08:29:46 Database Open status 1
08:29:46 Database Timeout ..: 120 seconds
08:29:46 Database Open status 1

08:29:47 Reload Error: Getting 24011 records -
08:29:47 Reload Error: SELECT COL_PRIMARY_KEY,COL_ADDRESS,COL_AGE,COL_A_INDEX,COL_ANT_AZ,COL_ANT_EL,COL_ANT_PATH,COL_ARRL_SECT,COL_BAND,COL_BAND_RX,COL_BIOGRAPHY,COL_CALL,COL_CHECK,COL_CLASS,COL_CNTY,COL_COMMENT,COL_CONT,COL_CONTACTED_OP,COL_CONTEST_ID,COL_COUNTRY,COL_CQZ,COL_DISTANCE,COL_DXCC,COL_EMAIL,COL_EQ_CALL,COL_EQSL_QSLRDATE,COL_EQSL_QSLSDATE,COL_EQSL_QSL_RCVD,COL_EQSL_QSL_SENT,COL_EQSL_STATUS,COL_FORCE_INIT,COL_FREQ,COL_FREQ_RX,COL_GRIDSQUARE,COL_HEADING,COL_IOTA,COL_ITUZ,COL_K_INDEX,COL_LAT,COL_LON,COL_LOTW_QSLRDATE,COL_LOTW_QSLSDATE,COL_LOTW_QSL_RCVD,COL_LOTW_QSL_SENT,COL_LOTW_STATUS,COL_MAX_BURSTS,COL_MODE,COL_MS_SHOWER,COL_MY_CITY,COL_MY_CNTY,COL_MY_COUNTRY,COL_MY_CQ_ZONE,COL_MY_GRIDSQUARE,COL_MY_IOTA,COL_MY_ITU_ZONE,COL_MY_LAT,COL_MY_LON,COL_MY_NAME,COL_MY_POSTAL_CODE,COL_MY_RIG,COL_MY_SIG,COL_MY_SIG_INFO,COL_MY_STATE,COL_MY_STREET,COL_NAME,COL_NOTES,COL_NR_BURSTS,COL_NR_PINGS,COL_OPERATOR,COL_OWNER_CALLSIGN,COL_PFX,COL_PRECEDENCE,COL_PROP_MODE,COL_PUBLIC_KEY,COL_QSLMSG,COL_QSLRDATE,COL_QSLSDATE,COL_QSL_RCVD,COL_QSL_RCVD_VIA,COL_QSL_SENT,COL_QSL_SENT_VIA,COL_QSL_VIA,COL_QSO_COMPLETE,COL_QSO_RANDOM,COL_QTH,COL_RIG,COL_RST_RCVD,COL_RST_SENT,COL_RX_PWR,COL_SAT_MODE,COL_SAT_NAME,COL_SFI,COL_SIG,COL_SIG_INFO,COL_SRX,COL_SRX_STRING,COL_STATE,COL_STATION_CALLSIGN,COL_STX,COL_STX_STRING,COL_SWL,COL_TEN_TEN,COL_TIME_OFF,COL_TIME_ON,COL_TX_PWR,COL_WEB,COL_USER_DEFINED_0,COL_USER_DEFINED_1,COL_USER_DEFINED_2,COL_USER_DEFINED_3,COL_USER_DEFINED_4,COL_USER_DEFINED_5,COL_USER_DEFINED_6,COL_USER_DEFINED_7,COL_USER_DEFINED_8,COL_USER_DEFINED_9,COL_CREDIT_GRANTED,COL_CREDIT_SUBMITTED FROM [TABLE_HRD_CONTACTS_V01] ORDER BY COL_TIME_ON DESC, COL_CALL DESC
08:29:47 Reload Error: Invalid character value for cast specification on column number 23 (COL_DXCC)
08:29:47 Reload Loaded 0/24011 records in 1125 miliseconds, 0.0 records per second

08:29:47 General Loading class CLogfileFrame


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

K2AK - Jeff <k2ak@...>
 

Thank you Laurie,

Very much appreciated.

73 de Jeff K2AK

-----Original Message-----
From: Ham-Apps@yahoogroups.com.au [mailto:Ham-Apps@yahoogroups.com.au] On
Behalf Of Laurie, VK3AMA
Sent: Wednesday, October 19, 2011 5:11 AM
To: Ham-Apps@yahoogroups.com.au
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert
after each contact

Hi Jeff,

That is a defect in JT-Alert 1.5.0 that is corrected in the upcoming
1.5.1 release (2 days time).

de Laurie, VK3AMA

On 19-October-2011 22:10, sitedev wrote:
Everything seems to be working fine with the nicely updated JT-Alert 1.5
except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE
window to capture all of the user information from QRZ or Buckmaster
(Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the
call sign and band to the B4log.mdb file just fine. The next time the call
sign that was previously logged is decoded is doesn't display as worked B4.
If I restart JT65-HF and JT-Alert it will then display that same call sign
as worked B4.

I do have the Display worked B4 checked in the configuration and created
the B4log.mdb file in the default directory and then imported all of my JT65
contacts from HRD. I tried using the log to ADI file but that didn't work at
all unless the callsign was in the ADI file (didn't care what was in B4 mdb
file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff - K2AK
DM41

------------------------------------

Yahoo!7 Groups Links


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

K2AK - Jeff <k2ak@...>
 

Dave,

 

I guess there is no real solution to automating (being lazy) even more. I stopped using HRD Utilities when HRD included LoTW updating. I think the easiest way for me was to try and get the B4Log.mdb working without restarting but I am sure these little tweaks will happen (don’t want to pester the developer as there are more important issues at hand). JT65 is much better with JT-Alert than without, hands down.

 

Laurie… Thanks for your awesome contributions to the Amateur Radio community.

 

73, Jeff

K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of Dave Wright
Sent: Wednesday, October 19, 2011 5:00 AM
To: Ham-Apps@...
Subject: Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Jeff,

 

You can either open the window and click the button as you said, or I use HRD Utilities.  It can do group updates…1, 2, 5, 10, all QSOs at once.  And you can select the fields you want to update…for example, I don't have it update the Grid as I want to use what is listed in JT65, but I do like to get names and other info.  

 

It is still a lot easier than typing them in one by one.  


-- 
Dave Wright

K3DCW

 

"Real radio bounces off the sky"

 

On Wednesday, October 19, 2011 at 7:56 AM, K2AK - Jeff wrote:

 

KD,

 

Thanks for the response. The only way I know how to get HRD V5 to update the QRZ information (name, QTH, grid cords, etc) is to open (modify) the contact after it was logged and then click the QRZ button in the ALE window. Are you able to get HRD to update the record automatically without opening the record?

 

Thanks again and 73,

Jeff – K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of K. D. Sarchet
Sent: Wednesday, October 19, 2011 4:27 AM
To: Ham-Apps@...
Subject: RE: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41

 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Laurie, VK3AMA <groups03@...>
 

Hi Jeff,

That is a defect in JT-Alert 1.5.0 that is corrected in the upcoming 1.5.1 release (2 days time).

de Laurie, VK3AMA

On 19-October-2011 22:10, sitedev wrote:
Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff � K2AK
DM41


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

Dave Wright <hfradiopro@...>
 


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

K2AK - Jeff <k2ak@...>
 

KD,

 

Thanks for the response. The only way I know how to get HRD V5 to update the QRZ information (name, QTH, grid cords, etc) is to open (modify) the contact after it was logged and then click the QRZ button in the ALE window. Are you able to get HRD to update the record automatically without opening the record?

 

Thanks again and 73,

Jeff – K2AK

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of K. D. Sarchet
Sent: Wednesday, October 19, 2011 4:27 AM
To: Ham-Apps@...
Subject: RE: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41


locked Re: [Ham-Apps] Thanks, Laurie

W5ADD@arrl.net
 

Laurie, hi.

The latest e-mail regarding removal of the blank space in the JT65 log pathname totally did the trick for me.

Congratulations on an update that is scary because it is so good!

--
Parker, W5ADD


locked Re: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

K. D. Sarchet <wy5r@...>
 

Sorry, I don’t have an answer to your issue, but wanted to make you aware of this:

 

>> I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

 

I use HRD V5 too, and it updates the user information from QRZ.  Maybe you are unaware that it does?

 

73 de WY5R - KD

 

JT65A Power Calculator

 

From: Ham-Apps@... [mailto:Ham-Apps@...] On Behalf Of sitedev
Sent: Wednesday, October 19, 2011 6:10 AM
To: Ham-Apps@...
Subject: [Ham-Apps] Problems Reading B4log.mdb unless restart JT-Alert after each contact

 

 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41


locked Problems Reading B4log.mdb unless restart JT-Alert after each contact

sitedev <k2ak@...>
 

Everything seems to be working fine with the nicely updated JT-Alert 1.5 except I am having one issue.

I am not using logging because I am using HRD V5 and I like to use the ALE window to capture all of the user information from QRZ or Buckmaster (Hamcall), like Name, Address, coordinates, QTH etc.

When I log a contact using the "LOG QSO" button in JT65-HF it writes the call sign and band to the B4log.mdb file just fine. The next time the call sign that was previously logged is decoded is doesn't display as worked B4. If I restart JT65-HF and JT-Alert it will then display that same call sign as worked B4.

I do have the Display worked B4 checked in the configuration and created the B4log.mdb file in the default directory and then imported all of my JT65 contacts from HRD. I tried using the log to ADI file but that didn't work at all unless the callsign was in the ADI file (didn't care what was in B4 mdb file).

Not sure why it is not refreshing or what should take place.

Any ideas?

Thanks,
Jeff – K2AK
DM41


locked Re: [Ham-Apps] HRD 5.0->eqsl logging request

Laurie, VK3AMA <groups03@...>
 

HRDV5 QSOs being marked as SWL is corrected and will be the 1.5.1 release.

de Laurie, VK3AMA

On 19-October-2011 11:35, kb0asq wrote:
It appears that HRD 5.0 will not automatically upload new entries to eqsl record is marked in a certain way. I haven't quite figured out if it has to be marked as "sent" or queued for sure.

Also, I just noticed the record is marked as a swl record instead of a contact.

KB0ASQ


locked Re: [Ham-Apps] HRD 5.0->eqsl logging request

Laurie, VK3AMA <groups03@...>
 

Hi KB0ASQ,

Flagging QSOs with eQSL and or LoTW "Requested" is already coded into the next release which should be out in 2 or 3 days.

Please provide more detail about how a HRD QSO is marked as SWL. (I don't regularly use HRD)



de Laurie, VK3AMA

On 19-October-2011 11:35, kb0asq wrote:
It appears that HRD 5.0 will not automatically upload new entries to eqsl record is marked in a certain way.  I haven't quite figured out if it has to be marked as "sent" or queued for sure.

Also, I just noticed the record is marked as a swl record instead of a contact.

KB0ASQ




locked HRD 5.0->eqsl logging request

wd0dxd
 

It appears that HRD 5.0 will not automatically upload new entries to eqsl record is marked in a certain way. I haven't quite figured out if it has to be marked as "sent" or queued for sure.

Also, I just noticed the record is marked as a swl record instead of a contact.

KB0ASQ


locked Re: [Ham-Apps] ## IMPORTANT ## - New Fix for NOT LOGGING errors.

Laurie, VK3AMA <groups03@...>
 

Additional information.

After performing the fix, log 2 QSOs to confirm that fix has worked, the first logging may not work, but the second should be logged.

Sorry for all this run-around.

New release, 1.5.1 in 2 or 3 days.

Laurie, VK3AMA

On 19-October-2011 08:29, Laurie, VK3AMA wrote:
You will need to have the jt65hf_log.adi file located in a directory path that does not contain a space.

The Fix.
  1. Stop JT-Alert.
  2. Start JT65-HF if not running.
  3. Click "Log QSO" button in JT65-HF.
  4. Use the browse button (right side of edit field) to browse to a NEW location (without a space in the path)
  5. Ensure that this new path has a Backslash "\" at the end of the path, type that character in manually.
  6. Click the "Cancel" button.
  7. Stop JT65-HF (this is important for the new change to be saved to the JT65-HF config file)
  8. Start JT65-HF
  9. Start JT-Alert
Logging should now work and a popup should appear after logging.

This fix will not be necessary once JT-Alert 1.5.1 is released (in 2 or 3 days time).


locked JT-Alert 1.5.0 under Wine

BuDJie
 

Hi Laurie
I know your having a hard time with all the problems but
I thought i would give you a good report and i hope it makes you smile and feel better

Im really amazed at what the program can do when just used on its own with
JT65-HF.....I love the Alert tones when you get a answer to your call
I have 2 comps running all the time....this one has e-mail and net working
the other one about 3 meters away has all the Ham apps
go from one to the other on the office chair...if im busy at this comp i now dont miss any contacts on the Ham comp

Most of the crashes happened when using Ubuntu 11.10 with the Unity desktop
(dont like it) have been able to get it to work with Gnome 3 and it looks and works a lot better...

love the CQ voice..when i hear it i can then check with a turn of the head as to who is calling

Laurie you have designed and coded a very top quality piece of software

Hey..dont tear your hair out with any problems...if we didnt make mistakes we wouldnt learn anything :-)

have a great day

73 David VK4BDJ