Date   

locked Re: JTalerts #DXLAB

Mike Cooper
 

Once I got access to the JTAlerts(ALT) program I undocked it from WSJT-X  and so far is working, Evidently when it is installed docking to WSJT-X is enabled and that is what causes the issue with not being able to find it. 


locked I need SQLite log

afa1yy
 

In upgrading to LOG4OM V2, My logs in SQLite  are no longer there.  Besides the new format, I do have my complete log saved as an ADIF.  In setting up LoG4om2 in  JTalert, I am required to provide my log in SQLite format.  How can I convert ADIF into SQLite?
--
Art  K0AY


locked Re: JTalerts #DXLAB

Mike Cooper
 

Turns out it is a screen sizing issue if I drop the display setting to 100% I can just barely see it the alt mode but cannot drag it out onto the full screen. And if I try
it the dragging process disrupts the rest of the screen. 


locked Re: FAILURE : QSO Not logged! ERROR Message : HRD : Unsupported ODBC DSN Callsign :

HamApps Support (VK3AMA)
 

On 29/01/2020 12:41 am, John Peck wrote:
OK, fixed it. Found where I did not have it configured properly. Sorry to bother you. 
John,

What did was the fix? If its embarrassing, email me direct. I am curious as to the cause.

de Laurie VK3AMA


locked Re: JTalerts #DXLAB

HamApps Support (VK3AMA)
 

On 29/01/2020 6:12 am, w7osg2@... wrote:
Just installed JTalerts and it appears to be working but there is no menu for either version ALT or otherwise???

Is there some trick to accessing it?
OM,

Sounds like you didn't use the correct JTAlert shortcut. The Alt Layout is automatically used when starting JTAlert using either the Green or Purple colored shortcut icon, it will have "(AL)" in the shortcut title.

de Laurie VK3AMA


locked JTalerts #DXLAB

Mike Cooper
 

Just installed JTalerts and it appears to be working but there is no menu for either version ALT or otherwise???

Is there some trick to accessing it?


locked Re: SCAN LOG NO HIGHLIGHTER

Bob Elliot
 

Fixed. Clean install and now all OK.
--
73 Bob K1RI
Sent from my Rotary Phone


locked Re: FAILURE : QSO Not logged! ERROR Message : HRD : Unsupported ODBC DSN Callsign :

John Peck
 

OK, fixed it. Found where I did not have it configured properly. Sorry to bother you. 


locked Re: FAILURE : QSO Not logged! ERROR Message : HRD : Unsupported ODBC DSN Callsign :

John Peck
 

Thank you Laurie. Debug recording just sent. John


locked Re: JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.

Laurie, VK3AMA
 

Matt,

Sqlite or MySQL log?

If sqlite, please zip up you log file and email it to me. Thanks

de Laurie VK3AMA


On 28/01/2020 5:52 pm, Matthew Payne wrote:
Same issue here Laurie.

If I select "No QSL Confirmation" then the scan works fine and removed any that I have worked from needed. If I unselect "No QSL Confirmation" and select "Card, eQSL and LoTW" the scan runs and seems to ignore the confirmations that I have, resetting needed back to all (340 DXCC for example).

I have downloaded eQSL and LoTW confirmations and they are show as confirmed is Log4OM V2

Matt
M0LMK / KI5GXV


locked Re: JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.

Matt M0LMK
 

Same issue here Laurie.

If I select "No QSL Confirmation" then the scan works fine and removed any that I have worked from needed. If I unselect "No QSL Confirmation" and select "Card, eQSL and LoTW" the scan runs and seems to ignore the confirmations that I have, resetting needed back to all (340 DXCC for example).

I have downloaded eQSL and LoTW confirmations and they are show as confirmed is Log4OM V2

Matt
M0LMK / KI5GXV


locked Re: JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.

HamApps Support (VK3AMA)
 

On 28/01/2020 1:41 pm, Doug Munday wrote:
JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.  The MySQL Test Connection shows Pass, pass. JTAlert is logging new QSO's into the MySQL db fine.  The scan process appears to work - the scan process reports the scan (image below), however it shows 340 needed in each category.  .I guess that is the first clue that something is amiss.   End result is that every decode appears as a ATNO!      If I change back to SQLite db, the scan works as it should.

Hope this helps.

Doug - W7DRM
Doug,

I have just received a similar report form another user. This occurred for them after they did an LoTW update of their log.
Is that what happened for you?

I suspect that there is an issue with "qsoconfirmations" json data in the log, either the format has changed or JTAlert is not handling the json field extraction correctly when it is running the SQL query against the log.

Please can you do an adif export of your MySQL log, zip it up and send it to me  for analysis. Don't send it to this Group.

de Laurie VK3AMA


locked Re: Text Message App Crashes

HamApps Support (VK3AMA)
 

On 27/01/2020 4:39 pm, ve7gtc wrote:
I have for the last several months, through all releases, had a text message issue. Someone sends me a text. It pops up and I answer. As soon as I type the first letter of the answer, the app closes. It doesn't matter if I am answering a text or initiating a new one. It crashes about 50% of the time. I get a lot of text messages, and don't know if that causes the problem. If I close JTAlert and open it again, that may or may not solve the problem. Any thoughts?
Thans,
Gus K2GT
Gus,

Yours is the first report of this behavior.

If it has been happening through many releases over several months, and with no other user reports, I am inclined to suspect something specific to your PC environment. PC specific defects are notoriously difficult to diagnose, often impossible.

Perhaps its a resources issue, how much Memory is available, how high is the CPU usage, what Windows version? What PC protection software are you running?

I might see something in your JTAlert sessions files, use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA



locked Re: JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.

HamApps Support (VK3AMA)
 

On 28/01/2020 2:03 pm, HamApps Support (VK3AMA) via Groups.Io wrote:

Typically when the DXCC counts (or any of the other alert types) returned by the Scan reset back to all are needed, the usual cause is that the scan was run against an empty or invalid log. Are you sure you have JTAlert set to use the correct MySQL database?

Another possibility is that you have set a QSL requirement, like LoTW, and your log has not been updated with any LoTW confirmations.

de Laurie VK3AMA


locked Re: JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.

HamApps Support (VK3AMA)
 

On 28/01/2020 1:41 pm, Doug Munday wrote:
JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.  The MySQL Test Connection shows Pass, pass. JTAlert is logging new QSO's into the MySQL db fine.  The scan process appears to work - the scan process reports the scan (image below), however it shows 340 needed in each category.  .I guess that is the first clue that something is amiss.   End result is that every decode appears as a ATNO!      If I change back to SQLite db, the scan works as it should.

Doug - W7DRM
Doug,

I can't fault it here is my tests.

When you run the MySQL Test connection is it reporting correctly the number of QSOs in the database and the last QSO?

Typically when the DXCC counts (or any of the other alert types) returned by the Scan reset back to all are needed, the usual cause is that the scan was run against an empty or invalid log. Are you sure you have JTAlert set to use the correct MySQL database?

de Laurie VK3AMA


locked JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.

Doug Munday
 

JTAlert 2.15.8 - Scan log of Log4OM V2 (2.2.0.0) not working with MySQL database.  The MySQL Test Connection shows Pass, pass. JTAlert is logging new QSO's into the MySQL db fine.  The scan process appears to work - the scan process reports the scan (image below), however it shows 340 needed in each category.  .I guess that is the first clue that something is amiss.   End result is that every decode appears as a ATNO!      If I change back to SQLite db, the scan works as it should. 



Hope this helps. 

Doug - W7DRM

Setup:
Log4OM V2.2.0.0
MySQL db
JTDX v2.1.0-rc147
JTAlert for JTDX v2.15.8
Win 10


locked Re: FAILURE : QSO Not logged! ERROR Message : HRD : Unsupported ODBC DSN Callsign :

HamApps Support (VK3AMA)
 

On 28/01/2020 10:21 am, John Peck wrote:
I am running HRD and WSJT-X on a Win 10 machine. All programs are at current levels. I recently installed JTAlert. It seems to have a lot of cool features and it is fun getting to know it.

However when I get the popup message at the end of a FT8 QSO and I hit the button to log the contact I get a popup error message, as follows:

FAILURE : QSO Not logged!
ERROR Message : HRD : Unsupported ODBC DSN
Callsign :  K4NYX
Frequency :  7.074862 MHz
Logged Mode :  FT8
This message has been placed in the Windows clipboard.
HRD TCP Logging command result returned =>

More than likely I just don't have something set up correctly. Can you give me some ideas as to whatis wrong?

John
John,

Rather than going through a protracted back-and-forth question & answer exercise, it would be easiest for you to send a support request.
Please do the following...

  • Enable debug recording via the "Settings -> Enable Debug Recording" JTAlert title-bar menu.
  • Restart JTAlert, that is close JTAlert and then start JTAlert.
  • Operate as normal and log a QSO to HRD.
  • Then use the "? -> Contact Support" menu, on the JTAlert title-bar, to send me your JTAlert files for analysis. Include a note of the Callsign and UTC time of the logging that failed with the ODBC error.
  • Turn off debug recording.

de Laurie VK3AMA


locked FAILURE : QSO Not logged! ERROR Message : HRD : Unsupported ODBC DSN Callsign :

John Peck
 

I am running HRD and WSJT-X on a Win 10 machine. All programs are at current levels. I recently installed JTAlert. It seems to have a lot of cool features and it is fun getting to know it.

However when I get the popup message at the end of a FT8 QSO and I hit the button to log the contact I get a popup error message, as follows:

FAILURE : QSO Not logged!
ERROR Message : HRD : Unsupported ODBC DSN
Callsign :  K4NYX
Frequency :  7.074862 MHz
Logged Mode :  FT8
This message has been placed in the Windows clipboard.
HRD TCP Logging command result returned =>

More than likely I just don't have something set up correctly. Can you give me some ideas as to whatis wrong?

John


locked Re: SCAN LOG NO HIGHLIGHTER

Bob Elliot
 

The DXCC Scan & Rebuild.  See attached.  It normally highlighted new ones like the highlight asking “OK to update your configuration?

 

It updates OK but no highlight to display what it updating.


--
73 Bob K1RI
Sent from my Rotary Phone


locked Re: Can't get to JTALER "Manage Setting'

Ed Fuller
 

Laurie, I was getting both errors. The VC RUNTIME which i would clear twice then the MySQL which I would clear once.  Installing the 32 bit version of the latest VCRUNTIME140.dll would fix all.  Running Win7 Home Premium.

Ed