Date   

locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

Joe Subich, W4TV
 

Laurie,

** - Support for DXLab LoTW, eQSL & US databases abandoned.**
Do you have better data for US stations (county, grid, etc.) than the
DXLab domestic database? It would be a shame to lose that data.

73,

... Joe, W4TV


On 9/5/2012 9:43 PM, Laurie, VK3AMA wrote:


I have had several requests for information on what is in the upcoming 2.0.0
release.

From the Release notes of 2.0.0, not complete, but does cover all the changes
currently implemented and tested.

*2.0.0**
** Important: This version compatible with JT-Macros 2.0.0 or later ONLY.**
** Important: This version compatible with HamApps-Sounds 2.0.0 or later ONLY.**
** Important: This version compatible with HamApps-Databases 12.09.01 or
later ONLY.**
****
** New Features:**
** - Interface Language Support. This release, English and Spanish only.**
** (new languages can be added without the need to upgrade JT-Alert)**
** - Previous QSOs summary popup for current QSO partner via mouse hover over**
** callsign with "New Band" or "First QSO" display below callsign.**
** - Previous QSOs summary via right-click menu on any of the decoded
callsigns.**
** - Current QSO partner data sent to JT-Macros for use in macro
substitution,**
** Bands worked count, Name and Callsign.**
** - Updater program to check and install updated files.**
** - Detect and process new decodes at any time in the minute. **
** - Log scan for ADIF & MixW Logs to update Wanted (State, DXCC, etc) Lists.**
** - Band Activity popup shows change in band spotters count since last
check.**
** - Option to display "Halt TX" Symbol to Left or Right of decoded
callsigns.**
** - Option to display DXCC Country names below decoded callsigns.**
** - "Disable Alert if Station worked B4" option for Own Call Alert.**
** - "Generate Alerts ONLY if Station is calling CQ or QRZ" option.**
** - "Generate Alerts ONLY if Station is eQSL(AG) member" option.**
** - "Generate Alerts ONLY if Station is LoTW member" option.**
** - DXKeeper log file now automatically detected.**
** - Button to open your browser to QRZ.com page of your current QSO
Callsign.**
** (visible if "Show Log Fields" is enabled)**
** - EQSL & LoTW QSL Request defaults for ADIF format log.**
** - Auto-Start Apps delay, after start before next application start.**
** - Auto-start Apps selection more file extensions, .bat, .cmd, .lnk & .com.**
** - Add 2M to Bands for Wanted alerts (DXCC, WAS, WAC, Grids & CQZones).**
** - Sound Card selection now includes Windows Default.**
** - Test Sound Card menu entry (under "Settings" menu).**
** - Test Sound Card button under Sound Card section of configuration
window. **
** - Progress display when sending Config & Session files email to support.**
** - Un-installer has option to completely remove all user settings.**
** Changes:**
** - Settings moved from ini file to an SQLite database.**
** - Support for Swisslog and VQlog logging abandoned.**
** - Support for DXLab LoTW, eQSL & US databases abandoned.**
** - Ham-Apps US State, LoTW & eQSL databases now distributed as a single
file.**
** - HRD V5 MS Access File method abandoned, use the HRD V5 ODBC DSN instead.**
** - Own Call alerts will not generate other alerts even if they apply.**
** - Calls, displayed left-to-right, follow the decodes low-to-high DF order.**
** - 95% decrease in log scan time when updating Worked Grids Lists.**
** - Improved CQ & ITU Zone determination accuracy for China.**
** - Country name of US calls for HRDLog saved as "United States".**
** - When docked, JT-Alert window can only be moved by moving JT65-HF window.**
** - Halt after TX symbol changed to "filled square" symbol.**
** Fixes:**
** - Own call alert generated for other callsigns that start with own call.**
** - DXKeeper QSL request incorrectly set to "N" rather than "".**
** - HRD QSL/eQSL/LoTW Received incorrectly set to "" rather than "N".**
** - Log scan DXCC count not matching DXKeeper progress counts.**
** - Part of hidden log fields visible on displays with 125% font scaling.**
** - Text cropped on Band Activity popup on displays with 125% font scaling.**
** - Not logging US State where State was "DC".**
** - WAS Log scans not using State "DC" as State "MD".**
** - Titlebar menus & Band Activity displays delayed on Win7 & Vista Aero
themes.**
** - Un-managed Error when Config encounters invalid database file path.**
** - Error message when Wanted Call Alert triggers the JT65-HF ToTop event.**
***
de Laurie, VK3AMA



locked Re: overriding info from Callsign Database

n0rq
 

Thank you, Laurie, and others, for comments!

I did indeed flip the CQ/ITU zones in LOTW (oops!), so I've corrected it and re-uploaded.

As for changing the official FCC entry, I can't really do that. As noted, it is a remote station. I don't live in SD, don't get mail in SD, and therefore can't effectively (or I think even legally) change to a SD address. Not all NT5HS operations are from SD -- all JT65 is, but not everything.

It is, I think, a near-unique situation. I know there are few other guys that operate JT65 remotely, some of them from another state/province. As such, it's probably going to just be a minor problem. I think that if guys download updates from eQSL and/or LOTW, it may (??) correct the log if the wrong state was entered. And of course if they look at the QRZ bio, it spells it out.

Anyway, I appreciate the ideas!

73, Dave N0RQ
http://www.powerlinenoise.com/n0rq/jt65-hf/


locked Re: What's coming in the new 2.0.0 release.

n0rq
 

Wow! Great list. Should make a really good tool even better! Glad to hear 60m will work, too.

Looking forward to it...
73, Dave N0RQ


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

signal <signalhz@...>
 

Laurie that's great. Now I can't wait for the 2.0 release


Eddy N4ABN

On 9/5/2012 11:02 PM, Laurie, VK3AMA wrote:
 

Regardless of how the 60M frequency is set in JT65-HF manually, via macro or Cat, the jt65hf_log.adi file still doesn't record the frequency. When you use the "Log QSO" button of JT65-HF, you will notice that the resulting "Log Contact" window has the frequency set as 0. Manually altering that zero frequency doesn't fix the problem either, no frequency is logged so JT-Alert wont log the QSO.

As mentioned in my other email, I have a workaround for the JT-Alert 2.0.0 release. JT-Alert will no longer read the frequncy from the jt65hf_log.adi file but will read directly from the QRG field of the JT65-HF window

de Laurie, VK3AMA

On 6/09/2012 12:43 PM, signal wrote:
Hi Laurie, What about if in JT65-HF the frequency is added like a macro? I'm on 60m 5.346.500 trying it out now.

Eddy N4ABN


On 9/5/2012 10:33 PM, Laurie, VK3AMA wrote:
 

Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN


--


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

Laurie, VK3AMA <groups04@...>
 

Regardless of how the 60M frequency is set in JT65-HF manually, via macro or Cat, the jt65hf_log.adi file still doesn't record the frequency. When you use the "Log QSO" button of JT65-HF, you will notice that the resulting "Log Contact" window has the frequency set as 0. Manually altering that zero frequency doesn't fix the problem either, no frequency is logged so JT-Alert wont log the QSO.

As mentioned in my other email, I have a workaround for the JT-Alert 2.0.0 release. JT-Alert will no longer read the frequncy from the jt65hf_log.adi file but will read directly from the QRG field of the JT65-HF window

de Laurie, VK3AMA

On 6/09/2012 12:43 PM, signal wrote:
Hi Laurie, What about if in JT65-HF the frequency is added like a macro? I'm on 60m 5.346.500 trying it out now.

Eddy N4ABN


On 9/5/2012 10:33 PM, Laurie, VK3AMA wrote:
 

Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN


--


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

signal <signalhz@...>
 

had to switch to 5.366.500


On 9/5/2012 10:43 PM, signal wrote:
Hi Laurie, What about if in JT65-HF the frequency is added like a macro? I'm on 60m 5.346.500 trying it out now.

Eddy N4ABN


On 9/5/2012 10:33 PM, Laurie, VK3AMA wrote:
 

Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

signal <signalhz@...>
 

You got the work around already Laurie?

Eddy N4ABN


On 9/5/2012 10:42 PM, Laurie, VK3AMA wrote:
 

Already fixed for the 2.0.0 release.

de Laurie, VK3AMA

On 6/09/2012 12:33 PM, Laurie, VK3AMA wrote:
Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN



-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

signal <signalhz@...>
 

Hi Laurie, What about if in JT65-HF the frequency is added like a macro? I'm on 60m 5.346.500 trying it out now.

Eddy N4ABN


On 9/5/2012 10:33 PM, Laurie, VK3AMA wrote:
 

Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

Laurie, VK3AMA <groups04@...>
 

Already fixed for the 2.0.0 release.

de Laurie, VK3AMA

On 6/09/2012 12:33 PM, Laurie, VK3AMA wrote:
Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN



locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

Laurie, VK3AMA <groups04@...>
 

Hi Eddy,

Not logging 60M QSOs is due to a bug in JT65-HF NOT logging the 60M frequency(or band) in the jt65hf_log.adi file.
It is this file that JT-Alert reads to determine if a new QSO has been logged. If JT-ALert cant determine the frequency of the new contact, then JT-Alert logging is aborted.

I will investigate a possible workaround.

de Laurie, VK3AMA

On 6/09/2012 11:53 AM, signal wrote:
That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN


locked Re: [Ham-Apps] What's coming in the new 2.0.0 release.

signal <signalhz@...>
 

That's a nice long list. How about for 60m band? I noticed yesterday JTAlert wouldn't upload a qso to HRD if I made a contact on 60m.

73 Eddy N4ABN


On 9/5/2012 9:43 PM, Laurie, VK3AMA wrote:
 

I have had several requests for information on what is in the upcoming 2.0.0 release.

From the Release notes of 2.0.0, not complete, but does cover all the changes currently implemented and tested.

2.0.0
  Important: This version compatible with JT-Macros 2.0.0 or later ONLY.
  Important: This version compatible with HamApps-Sounds 2.0.0 or later ONLY.
  Important: This version compatible with HamApps-Databases 12.09.01 or later ONLY.
 
  New Features:
    - Interface Language Support. This release, English and Spanish only.
       (new languages can be added without the need to upgrade JT-Alert)
    - Previous QSOs summary popup for current QSO partner via mouse hover over
       callsign with "New Band" or "First QSO" display below callsign.
    - Previous QSOs summary via right-click menu on any of the decoded callsigns.
    - Current QSO partner data sent to JT-Macros for use in macro substitution,
       Bands worked count, Name and Callsign.
    - Updater program to check and install updated files.
    - Detect and process new decodes at any time in the minute.
    - Log scan for ADIF & MixW Logs to update Wanted (State, DXCC, etc) Lists.
    - Band Activity popup shows change in band spotters count since last check.
    - Option to display "Halt TX" Symbol to Left or Right of decoded callsigns.
    - Option to display DXCC Country names below decoded callsigns.
    - "Disable Alert if Station worked B4" option for Own Call Alert.
    - "Generate Alerts ONLY if Station is calling CQ or QRZ" option.
    - "Generate Alerts ONLY if Station is eQSL(AG) member" option.
    - "Generate Alerts ONLY if Station is LoTW member" option.
    - DXKeeper log file now automatically detected.
    - Button to open your browser to QRZ.com page of your current QSO Callsign.
       (visible if "Show Log Fields" is enabled)
    - EQSL & LoTW QSL Request defaults for ADIF format log.
    - Auto-Start Apps delay, after start before next application start.
    - Auto-start Apps selection more file extensions, .bat, .cmd, .lnk & .com.
    - Add 2M to Bands for Wanted alerts (DXCC, WAS, WAC, Grids & CQZones).
    - Sound Card selection now includes Windows Default.
    - Test Sound Card menu entry (under "Settings" menu).
    - Test Sound Card button under Sound Card section of configuration window.
    - Progress display when sending Config & Session files email to support.
    - Un-installer has option to completely remove all user settings.
  Changes:
    - Settings moved from ini file to an SQLite database.
    - Support for Swisslog and VQlog logging abandoned.
    - Support for DXLab LoTW, eQSL & US databases abandoned.
    - Ham-Apps US State, LoTW & eQSL databases now distributed as a single file.
    - HRD V5 MS Access File method abandoned, use the HRD V5 ODBC DSN instead.
    - Own Call alerts will not generate other alerts even if they apply.
    - Calls, displayed left-to-right, follow the decodes low-to-high DF order.
    - 95% decrease in log scan time when updating Worked Grids Lists.
    - Improved CQ & ITU Zone determination accuracy for China.
    - Country name of US calls for HRDLog saved as "United States".
    - When docked, JT-Alert window can only be moved by moving JT65-HF window.
    - Halt after TX symbol changed to "filled square" symbol.
  Fixes:
    - Own call alert generated for other callsigns that start with own call.
    - DXKeeper QSL request incorrectly set to "N" rather than "".
    - HRD QSL/eQSL/LoTW Received incorrectly set to "" rather than "N".
    - Log scan DXCC count not matching DXKeeper progress counts.
    - Part of hidden log fields visible on displays with 125% font scaling.
    - Text cropped on Band Activity popup on displays with 125% font scaling.
    - Not logging US State where State was "DC".
    - WAS Log scans not using State "DC" as State "MD".
    - Titlebar menus & Band Activity displays delayed on Win7 & Vista Aero themes.
    - Un-managed Error when Config encounters invalid database file path.
    - Error message when Wanted Call Alert triggers the JT65-HF ToTop event.
 

de Laurie, VK3AMA

-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked What's coming in the new 2.0.0 release.

Laurie, VK3AMA <groups04@...>
 

I have had several requests for information on what is in the upcoming 2.0.0 release.

From the Release notes of 2.0.0, not complete, but does cover all the changes currently implemented and tested.

2.0.0
  Important: This version compatible with JT-Macros 2.0.0 or later ONLY.
  Important: This version compatible with HamApps-Sounds 2.0.0 or later ONLY.
  Important: This version compatible with HamApps-Databases 12.09.01 or later ONLY.
 
  New Features:
    - Interface Language Support. This release, English and Spanish only.
       (new languages can be added without the need to upgrade JT-Alert)
    - Previous QSOs summary popup for current QSO partner via mouse hover over
       callsign with "New Band" or "First QSO" display below callsign.
    - Previous QSOs summary via right-click menu on any of the decoded callsigns.
    - Current QSO partner data sent to JT-Macros for use in macro substitution,
       Bands worked count, Name and Callsign.
    - Updater program to check and install updated files.
    - Detect and process new decodes at any time in the minute.
    - Log scan for ADIF & MixW Logs to update Wanted (State, DXCC, etc) Lists.
    - Band Activity popup shows change in band spotters count since last check.
    - Option to display "Halt TX" Symbol to Left or Right of decoded callsigns.
    - Option to display DXCC Country names below decoded callsigns.
    - "Disable Alert if Station worked B4" option for Own Call Alert.
    - "Generate Alerts ONLY if Station is calling CQ or QRZ" option.
    - "Generate Alerts ONLY if Station is eQSL(AG) member" option.
    - "Generate Alerts ONLY if Station is LoTW member" option.
    - DXKeeper log file now automatically detected.
    - Button to open your browser to QRZ.com page of your current QSO Callsign.
       (visible if "Show Log Fields" is enabled)
    - EQSL & LoTW QSL Request defaults for ADIF format log.
    - Auto-Start Apps delay, after start before next application start.
    - Auto-start Apps selection more file extensions, .bat, .cmd, .lnk & .com.
    - Add 2M to Bands for Wanted alerts (DXCC, WAS, WAC, Grids & CQZones).
    - Sound Card selection now includes Windows Default.
    - Test Sound Card menu entry (under "Settings" menu).
    - Test Sound Card button under Sound Card section of configuration window.
    - Progress display when sending Config & Session files email to support.
    - Un-installer has option to completely remove all user settings.
  Changes:
    - Settings moved from ini file to an SQLite database.
    - Support for Swisslog and VQlog logging abandoned.
    - Support for DXLab LoTW, eQSL & US databases abandoned.
    - Ham-Apps US State, LoTW & eQSL databases now distributed as a single file.
    - HRD V5 MS Access File method abandoned, use the HRD V5 ODBC DSN instead.
    - Own Call alerts will not generate other alerts even if they apply.
    - Calls, displayed left-to-right, follow the decodes low-to-high DF order.
    - 95% decrease in log scan time when updating Worked Grids Lists.
    - Improved CQ & ITU Zone determination accuracy for China.
    - Country name of US calls for HRDLog saved as "United States".
    - When docked, JT-Alert window can only be moved by moving JT65-HF window.
    - Halt after TX symbol changed to "filled square" symbol.
  Fixes:
    - Own call alert generated for other callsigns that start with own call.
    - DXKeeper QSL request incorrectly set to "N" rather than "".
    - HRD QSL/eQSL/LoTW Received incorrectly set to "" rather than "N".
    - Log scan DXCC count not matching DXKeeper progress counts.
    - Part of hidden log fields visible on displays with 125% font scaling.
    - Text cropped on Band Activity popup on displays with 125% font scaling.
    - Not logging US State where State was "DC".
    - WAS Log scans not using State "DC" as State "MD".
    - Titlebar menus & Band Activity displays delayed on Win7 & Vista Aero themes.
    - Un-managed Error when Config encounters invalid database file path.
    - Error message when Wanted Call Alert triggers the JT65-HF ToTop event.
 

de Laurie, VK3AMA


locked Re: [Ham-Apps] JT-Alert Callsign Databases - New version, 12.09.06 (2012-Sep-06), available

signal <signalhz@...>
 

Hi Laurie, that's a good upgrade.  Do you have a list of future upgrades?

Eddy N4ABN

On 9/5/2012 8:55 PM, Laurie, VK3AMA wrote:
 

Hi Eddy,

The next release of JT-Alert will allow for download and install of the Database updates via a button click within the JT-Alert Configuration window.

de Laurie, VK3AMA


On 6/09/2012 10:42 AM, signal wrote:
Thanks Laurie....73 Eddy N4ABN


On 9/5/2012 8:37 PM, Laurie, VK3AMA wrote:
 

Latest Callsign Databases (12.09.06) file available for download from
http://ham-apps.com/dnl/JT-Alert/JT-Alert_Databases_12.09.06_Setup.exe

Download Size: 4.4 MB

Simply run the executable to install or update existing files.

The version number reflects the creation and release UTC date.
12 = year, 09 = month, 06 = day. So this file created and released 2012-Sep-06

de Laurie, VK3AMA


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/



-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked Re: [Ham-Apps] JT-Alert Callsign Databases - New version, 12.09.06 (2012-Sep-06), available

Laurie, VK3AMA <groups04@...>
 

Hi Eddy,

The next release of JT-Alert will allow for download and install of the Database updates via a button click within the JT-Alert Configuration window.

de Laurie, VK3AMA


On 6/09/2012 10:42 AM, signal wrote:
Thanks Laurie....73 Eddy N4ABN


On 9/5/2012 8:37 PM, Laurie, VK3AMA wrote:
 

Latest Callsign Databases (12.09.06) file available for download from
http://ham-apps.com/dnl/JT-Alert/JT-Alert_Databases_12.09.06_Setup.exe

Download Size: 4.4 MB

Simply run the executable to install or update existing files.

The version number reflects the creation and release UTC date.
12 = year, 09 = month, 06 = day. So this file created and released 2012-Sep-06

de Laurie, VK3AMA


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/



locked Re: [Ham-Apps] JT-Alert Callsign Databases - New version, 12.09.06 (2012-Sep-06), available

signal <signalhz@...>
 

Thanks Laurie....73 Eddy N4ABN


On 9/5/2012 8:37 PM, Laurie, VK3AMA wrote:
 

Latest Callsign Databases (12.09.06) file available for download from
http://ham-apps.com/dnl/JT-Alert/JT-Alert_Databases_12.09.06_Setup.exe

Download Size: 4.4 MB

Simply run the executable to install or update existing files.

The version number reflects the creation and release UTC date.
12 = year, 09 = month, 06 = day. So this file created and released 2012-Sep-06

de Laurie, VK3AMA


-- 
If you do not feel comfortable with firearms, maybe you will be more comfortable as a victim.

https://sites.google.com/site/n4abnradio/


locked JT-Alert Callsign Databases - New version, 12.09.06 (2012-Sep-06), available

Laurie, VK3AMA <groups04@...>
 

Latest Callsign Databases (12.09.06) file available for download from
http://ham-apps.com/dnl/JT-Alert/JT-Alert_Databases_12.09.06_Setup.exe

Download Size: 4.4 MB

Simply run the executable to install or update existing files.

The version number reflects the creation and release UTC date.
12 = year, 09 = month, 06 = day. So this file created and released 2012-Sep-06

de Laurie, VK3AMA


locked Re: [Ham-Apps] Re: overriding info from Callsign Database

Laurie, VK3AMA <groups04@...>
 

Hi James,A

On rereading the original email, you are correct.

This remote station operation and the resulting logging of incorrect State/Grid data is not limited to JT-Alert. I ran some quick tests against Logger32, DXKeeper, HRD and a couple of other minor loggers and they all logged a NT5HS QSO as TX, not SD.

From my perspective, the callbook data for NT5HS needs to be corrected at the source and not at the Logger. JT-Alert, however, will use the correct data if there is a previous QSO (same for DXKeeper, I didn't try this for the other loggers), otherwise the QSO partner should be making attempts to correct the data when logging a NT5HS QSO for the first time.

My thoughts... I imagine that the majority of ops use QRZ for data lookup. The lookup data provided by QRZ XML of browser lookup needs to be corrected. A couple of lines in a lengthy Bio (which I rarely read) while the lookup data remains incorrect, is not sufficient. With the limits of what can be exchanged in a JT65A QSO, it is even more important that the source of the lookup data be correct especially when the correct data may be lost during the QSO exchanges.

de Laurie, VK3AMA

On 1/09/2012 12:05 PM, james_nf8i wrote:
Laurie,

I think, if I've understood correctly, that the concern is that NT5HS is currently operating Mobile/Portable away from his home QTH.  QRZ and FCC are showing the correct, permanent, mailing address, but the OP is looking for a way to have temporary location info propagated through JT-Alert.

(I have no idea how this would work, but I think that's the concern, not the accuracy of the various databases.)

73 de NF8I,

~James



locked Re: overriding info from Callsign Database

cessnaflyer42
 

Laurie,

I think, if I've understood correctly, that the concern is that NT5HS is currently operating Mobile/Portable away from his home QTH. QRZ and FCC are showing the correct, permanent, mailing address, but the OP is looking for a way to have temporary location info propagated through JT-Alert.

(I have no idea how this would work, but I think that's the concern, not the accuracy of the various databases.)

73 de NF8I,

~James


locked Re: [Ham-Apps] overriding info from Callsign Database

Laurie, VK3AMA <groups04@...>
 

Dave,

Some additional information...

I note that on LoTW, NT5HS is setup as CQZone=7 and ITUZone =4. This is wrong, the correct data should be CQZone=4 and ITUZone=7
On QRZ.com, no zones are recorded and incorrect State (TX).
On eQSL, zones, State and Grid are correctly recorded.
On HamQTH, State and Zone are incorrect.

You have data inconsistencies between eQSL, LoTW, QRZ.com and the FCC database, any of which can be used by your QSO partner during the several minutes of a typical JT65A QSO to lookup your Zone, Grid and State data.

I respectfully suggest that if these data errors were corrected, then most of you problems with incorrectly logged data by your QSO partner would be eliminated.


de Laurie, VK3AMA


locked Re: [Ham-Apps] overriding info from Callsign Database

Laurie, VK3AMA <groups04@...>
 

Dave,

I assume it is NT5HS that is generating incorrect State alerts and wrongly logged grid. Is that correct?

I note on QRZ.com and the FCC database that both calls are listed as in TX. If your QSO partners are looking up your info during a QSO then they will see that the TX State matches that already filled in by JT-Alert and are most likely not changing it. If your QSO partner is not reading your QRZ bio, then they will most likely miss the State and Grid corrections.

I note that NT5HS is using SD and EN04 on LoTW. Why is it correct on LoTW but not in the FCC database
?

The callsign database of JT-Alert is only used to determine LoTW/eQSL(AG) membership and US State, NO Grid data.

If the US State is being reported as incorrect it is because the State is incorrectly recorded in the official FCC Database from which the State info is derived.

Are you sending your Grid as part of the Standard CQ message or in your 73 message? If the latter, then it is operator error (your QSO partner) not making the correction before logging the contact. If you are sending the Grid in the CQ message, then that is what will be logged (unless they have altered it in JT-Alert, then that is what will be logged)

JT-Alert does examine the log for previous QSOs and will use the most recent QSO data to populate the log fields of JT-Alert, so if the most recent logged QSO has incorrectly logged Grid or State data then that incorrect data will be used.

Due to the rigid (and 13 char limit) structure of JT65A exchanges, it is difficult to make your QSO partner aware of the State and Grid corrections, especially if the are performing online lookups during the QSO and not paying attention to the actual data sent. Easily accomplished with other digital modes (PSK, RTTY, etc) however.

If I was to have a QSO today with NT5HS (unlikely since I'm off air for a few weeks), then on first double-click of your callsign in JT65-HF, the log fields of JT-ALert will be populated with SD and EN04 since we have had a previous QSO and the log data is correct. However for a first contact, the JT-Alert State would be entered as TX (from the fcc file) and the Grid left empty and if not changed will be logged as EN04 (if sent as part of your CQ exchange).

Partially coded here is a QRZ XML lookup for JT-Alert, but even if working, it will also report NT5HS as being in TX.

I am hesitant to develop an override system. I suggest that you need to get QRZ, FCC database and LoTW in sync and all reporting the correct data, SD and EN04.

Sorry for the rambling nature of this email, battling an ongoing Migraine here (2 weeks and counting), so I shouldn't even be on the computer.

de Laurie, VK3AMA


On 29/08/2012 6:59 AM, n0rq wrote:
Hi.

This may be uncommon enough to make it not worth while, I don't know.

The alerts from JT-Alert, and I think any logging by JT-Alert, uses the state and/or grid from the installed Callsign Datbases.  This normally makes sense.

However, for someone that is /P, /M, /MM, or like me, a remote station in another state, the alerts are wrong.  The same is true of the hamspots.net site.

It would be nice (I think) to have some way to force an override to the Callsign Databases.  Maybe I'm the only one, I don't know, and I'm sure not asking for something special for just one person.  I always xmit my correct grid (EN04), which is in SD, but I get repeated emails from guys that are confused about where I am (or telling me I sent the wrong grid), and I'm sure there are lots of incorrect log entries as me in TX instead of SD.  My standard "73" msg is something like 5W 73 FROM SD, but even then, logging, alerting, and reporting is often wrong.

I don't know the answer.  Or maybe there isn't really one.  But I mention it, in case Laurie or someone else has ideas...

Tnx & 73!
Dave N0RQ (op. for NT5HS in SD)
remote station info: http://www.powerlinenoise.com/n0rq/remote-hf-station/




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

Yahoo!7 Groups Links

<*> To visit your group on the web, go to:
    http://au.groups.yahoo.com/group/Ham-Apps/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://au.groups.yahoo.com/group/Ham-Apps/join
    (Yahoo! ID required)

<*> To change settings via email:
    Ham-Apps-digest@... 
    Ham-Apps-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    Ham-Apps-unsubscribe@...

<*> Your use of Yahoo!7 Groups is subject to:
    http://au.docs.yahoo.com/info/terms/