Date   

PLEASE ACTIVATE ACCOUNT

k5rcd
 

 


Virus-free. www.avast.com


Re: QSORelay and HRD will not log

Chris VK2BYI
 
Edited

Dave, I just noticed something in the screen capture of your settings posted above.

You have your JTAlert ADIF Log File setting in QSO Relay set to the JTAlert 'lastqso.adi' file.  That is not correct, that file in JTAlert is not used by QSO Relay.

Referring to the diagram in QSO Relay Settings and Data Flow topic as mentioned in my previous reply to Mike, check the "Log File" setting on the "Standard ADIF File" section under "Logging" in JTAlert:

And set the JTAlert ADIF Log File setiing in QSO Relay to the same value:

The examples shown here are from my system.  The actual filenames will be slightly different on your PC.  With the setting you have at the moment, QSO Relay will still relay contacts to HRD Logbook OK, but you will not be able to update your Wanted Alert requirements in JTAlert if that is important to you.


73 Chris VK2BYI


Re: QSORelay and HRD will not log

Chris VK2BYI
 

Thanks Dave!
Mike, if the Windows 8 PC is working, use it as the reference when checking the settings on the Windows 10 PCs and make sure all of the settings are identical.  QSORelay was developed on Windows 10 and tested on Windows 7, 8, 8.1 and 10.
You should also refer to the QSO Relay Settings and Data Flow topic pinned second from the top in the Messages area, which has another diagram showing all of the critical settings in JTAlert and QSORelay and their purpose.  You may have to zoom your browser to 150% or more to make the diagram easy to read.
73 Chris VK2BYI


Re: QSORelay and HRD will not log

Dave wo2x
 

2237 is the port for WSJT-X to JT Alert.

2233 is JT Alert to QSO Relay.

 

Here’s a screenshot of settings for WSJT-X and QSO Relay for my setup. I am NOT using Maria DB but everything works fine.

Make sure the TCP port is correct for QSO relay to talk to HRD Logbook. Should be 7826.

 

Dave wo2x

 

 

Sent from Mail for Windows 10

 

From: NA6MB Mike
Sent: Thursday, July 13, 2017 8:35 AM
To: vk2byi-qsorelay@groups.io
Subject: Re: [vk2byi-qsorelay] QSORelay and HRD will not log

 

 I'm using Microsoft access database not Maria but symtoms sounded the same .

 


Re: QSORelay and HRD will not log

NA6MB Mike <na6mb.mike@...>
 

 I'm using Microsoft access database not Maria but symtoms sounded the same .


Re: QSORelay and HRD will not log

Chris VK2BYI
 

Other users experiencing issues with MariaDB have found it helps to have another, empty Access Logbook database open in HRD Logbook at the same time as the MariaDB database.  It also worked for me on a couple of occasions and I use Microsoft SQL Server.
73 Chris VK2BYI


Re: QSORelay and HRD will not log

NA6MB Mike <na6mb.mike@...>
 

Was a solution found?
i have a similar problem.
Set up three PCS, win 8 worked fine two win 10 don't work.
Win 8 has HRD UDP set to 2333, as does jtalert and QSO relay.
Win 10 have UDP set to 2237 default.
i changed HRD JTAlert and WJST-X to all have 2333.
No good.

Ideass?

NA6MB
Mike


locked Re: QSO Relay version 1.5

Howard Sidorsky
 

Hi Chris,

 

Until Field Day and the prep prior to FD, WSJT with QSO Relay was working just fine.  All of a sudden as I went back to JT65 today, I realized that it is no longer working.  I’ve checked everything and everything seems to be okay. 

 

However, I do not seem to have the current QSO in the log.adi file.  I cannot figure out why contacts are not going there.  I have sync’d QSO Relay… but no luck. 

 

I realize that it is now Saturday for you but if you could let me know what it would be a good time to reach you, either today or during the week, I would greatly appreciate it.  If in the mean time I solve the problem I will let you know…

 

Thanking you in advance,

 

Howard – K6SID….

 

From: vk2byi-qsorelay@groups.io [mailto:vk2byi-qsorelay@groups.io] On Behalf Of Chris VK2BYI
Sent: Sunday, June 11, 2017 9:13 PM
To: vk2byi-qsorelay@groups.io
Subject: [vk2byi-qsorelay] QSO Relay version 1.5

 

Please be advised that a new release of QSO Relay (Version 1.5) is now available for download at http://www.vk2byi.com.au/qsorelay/, or by selecting the Check for Updates... item on the QSO Relay menu.

This version is a minor release only, that adds a new feature, and that corrects a minor issue.  Most users will notice very little change in functionality.

  • Added a new feature whereby the scope of rows to be extracted from HRD Logbook during a synchronise database operation, can be filtered to 'All contacts', 'JT Mode contacts only' or 'Digital mode contacts only';
  • Corrected the contents of the County field when a new QSO is being added to HRD Logbook, to provide the County value only, and not the State and County values for US contacts.  The State value is still provided in the State field.

Again, we wish to thank all users for their positive feedback and patience in working with us to resolve some of the issues experienced.


jtalert not updating

rdaiprai@...
 

can someone help me ? i am running windows 7 ultimate ,jtdx ver17.9,latest ver of qsorelay, and the latest ver of hrd.
qsorelay works perfectly with hrd , when i sync hrd lod to qsorelay it works perfectly but when i do a scan log in jtalert it dose not update .
i have to put jtdx on a freq that has no signals on it and restart jtalert and then do a scanlog and it seams to work but once jtdx receives a signal  to decode jtalert scanlog dose not work again.
any thoughts on this problem?
thanks rich n0umf
rdaiprai@...


Re: Possible small Bug?

Chris VK2BYI
 

Hi Morris,

Thank you for the feedback and your kind words.  We did work 2016-09-02 - and verified on LoTW and eQSL.

73 Chris VK2BYi


Re: Possible small Bug?

Morris WA4MIT
 

version 1.5 seems to work great no double state entries in the county part of ADIF. Thanks Chris you do a great job really enjoy using your software. Noticed we had worked 2/9/16 on JT mode. Thanks 73


locked QSO Relay version 1.5

Chris VK2BYI
 

Please be advised that a new release of QSO Relay (Version 1.5) is now available for download at http://www.vk2byi.com.au/qsorelay/, or by selecting the Check for Updates... item on the QSO Relay menu.

This version is a minor release only, that adds a new feature, and that corrects a minor issue.  Most users will notice very little change in functionality.

  • Added a new feature whereby the scope of rows to be extracted from HRD Logbook during a synchronise database operation, can be filtered to 'All contacts', 'JT Mode contacts only' or 'Digital mode contacts only';
  • Corrected the contents of the County field when a new QSO is being added to HRD Logbook, to provide the County value only, and not the State and County values for US contacts.  The State value is still provided in the State field.

Again, we wish to thank all users for their positive feedback and patience in working with us to resolve some of the issues experienced.


Re: Possible small Bug?

Morris WA4MIT
 

OK Chris again thanks for all your effort and sharing your fine software with all of us. 73 Morris


Re: Possible small Bug?

Chris VK2BYI
 

Hi Morris,
I have just read the posts in the HRD forum and have posted a couple of replies.  I will have a new version of QSO Relay ready ASAP.
73 Chris VK2BYI


Re: Possible small Bug?

Morris WA4MIT
 

Chris this subject has also been discussed on the HRD forum even Laurie VK3AMA commented on it and we all believe this is happening when QSO Relay sends data to HRD. Further I did a test to see if HRD somehow was causing this to happen. What I did was made a USA contact on JT65 using QSO Relay then did a ADIF export from HRD of this one qso and this contact showed the double state in the county field. I then deleted this one contact. JTAlert generates a file called "last qso" in ADI format so I imported this data (same qso same call) into HRD then again did a ADIF export and this time there was no double state in the county part of the ADI export. 
I believe this little experiment points to something happening when QSO Relay imports into HRD generating this anomaly.  What do you think?
73 Morris


Re: Possible small Bug?

Chris VK2BYI
 

Found the answer!
This is what happens when I logged your call on my system (some detail cropped for clarity)...
2017-06-03 13:09:01.2595 Processing received data
    <CALL:6>WA4MIT<QSO_DATE:8>20170603<TIME_ON:6>030800...<CONT:2>NA<CNTY:13>AL,Tuscaloosa<DXCC:3>291<COUNTRY:13> ... <EOR>
 
So, JTAlert is suppling 'AL,Tuscaloosa' for CNTY.

You might ask the question on the HamApps forum, as a better answer will be found there.

73 Chris VK2BYI


Re: Possible small Bug?

Chris VK2BYI
 

I assume that is the CNTY column on the left and the State column on the right you have circled.  Can I see what is in the County column for those contacts in HRD?

As I said in my previous post, what is exported in CNTY in the ADIF file, is actually State + County from HRD Logbook.  This is why you end up with 'DE' + , + 'DE,New Castle' in CNTY - it is HRD Logbook ADIF Export doing that.  I am guessing that either JTAlert and/or HRD Logbook is looking up details on a web service such as QRZ.com etc, and capturing those sorts of values.  But I do not know, I am only guessing.
 
But seeing as you asked... :-)

One way to help track it down is to Enable Tracing in the QSO Relay Options dialog, and work a few JT stations, then Disable Tracing so that the session file is closed and written.  Then examine the session file, or send it to me, and the details there will show what was sent by JTAlert and what was relayed to HRD Logbook.  For example, you will see this sort of thing:
 
A data packet from JTAlert is received - NOTE That there is no CNTY field in the following 'ADD' statement from JTAlert - but then County is not that relevant 'downunder', so I didn't expect it to be there. Your situation may be different:
    2017-05-07 20:02:15.9029 Processing received data
    ADD <CALL:6>VK2RTX<DXCC:3>150<COUNTRY:9>Australia<QSO_DATE:8>20170504<QSO_DATE_OFF:8>20170504<TIME_ON:6>070200<TIME_OFF:6>072000<FREQ:9>14.078902<FREQ_RX:9>14.078902<BAND:3>20m<BAND_RX:3>20m<MODE:4>JT65<DISTANCE:1>0<COMMENT:4>JT65<CQZ:2>30<ITUZ:2>59<PFX:3>VK2<CONT:2>OC<MY_GRIDSQUARE:6>QF55mx<MY_CQ_ZONE:2>30<MY_ITU_ZONE:2>59<STATION_CALLSIGN:6>VK2BYI<QSO_COMPLETE:1>Y <EOR>
 
The details are saved in the QSO Relay database (not relevant to this discussion):
    2017-05-07 20:02:15.9034 Logging contact in SQLite
    ...
    2017-05-07 20:02:16.1045 Contact successfully logged in SQLite
 
The contact details are relayed to HRD Logbook - NOTE: the detail layout is simply changed from the ADIF style provided by JTAlert, to the 'db add' syntax that HRD Logbook expects - but the values are not changed - so CNTY is not here either:
    2017-05-07 20:02:16.1055 Relaying contact via TCP to HRD
    ...
    db add "My Logbook" { CALL="VK2RTX" DXCC="150" COUNTRY="Australia" QSO_DATE="20170504" QSO_DATE_OFF="20170504" TIME_ON="070200" TIME_OFF="072000" FREQ="14078902" FREQ_RX="14078902" BAND="20m" BAND_RX="20m" MODE="JT65" DISTANCE="0" COMMENT="JT65" CQZ="30" ITUZ="59" PFX="VK2" CONT="OC" MY_GRIDSQUARE="QF55mx" MY_CQ_ZONE="30" MY_ITU_ZONE="59" STATION_CALLSIGN="VK2BYI" QSO_COMPLETE="Y " }
    Found 22 Valid Fields...
    Added 22 Fields to Access - W8RID...
    ...
 
The row is verified as written to the HRD Logbook database itself:
    Verify VK2RTX, 20170504, 070200, 20m, JT65
    2017-05-07 20:02:16.5600 Contact successfully relayed via TCP to HRD
 
Beyond all of this, it also depends upon what HRD Logbook does when it looks up details from web services, and how the details are formatted in those sources.
 
All I can say, is that QSO Relay does not change any of the details whatsoever - it just uses the formats required for accepting and relaying the details.  So, if it is not coming from JTAlert, then it is probably happening when HRD Logbook adds the record.  I suspect the later.

73 Chris VK2BYI
 


Re: Possible small Bug?

Morris WA4MIT
 
Edited

Hey Chris wonder where this is happening?. I looked in some recent log entries with county showing and this is not there in HRD on screen logbook but when I opened a adif save this is what I see in ADIF Master and if you notice there are a couple of PSK contacts in this and they are not double state??. Thanks for your reply 73 Morris


Re: Possible small Bug?

Chris VK2BYI
 

QSO Relay does not place any significance on individual fields, it simply relays the data received from JTAlertX to HRD Logbook.

However, it would appear that when you extract an ADIF file from HRD Logbook, it concatenates the State and County column values from the logbook and writes the result as the <CNTY> field in the ADIF file.

Here is a contact from my Logbook, where the County field is populated:



The same contact in the ADIF export file looks like this (with most of the detail cropped):
  ... <ant_el:3>0.0 <band:3>15m <band_rx:3>15m <call:5>K7VNE <cnty:11>AZ,Maricopa <comment:24>JT65 Sent: -10 Rcvd: -02 ...
And when opened in ADIF Master, it looks like this:



Check the contact back in HRD Logbook, and I think you will find that it has been logged correctly, with separate State and County values.  But in your case, I would guess you have 'AL.' in State and 'AL. Tuscaloosa.' in County.  And these values probably come that way from QRZ.com etc.

73 Chris VK2BYI


Possible small Bug?

Morris WA4MIT
 

Chris I was looking at my HRD.647 DB with ADIF Master and I noticed that in the County Column with each JT QSO insert that the State is being inserted twice. This only started on May the 6th 2017 and this would be about the time I started using QSO RELAY this is only occurring with JT QSO`s. It looks like this AL. AL. Tuscaloosa. Prior to 5/6/17 the state is listed only once such as Al. Tuscaloosa. Not sure if this is a relay or JTAlert issue but wanted to let you know. Everything has been working great no hiccups or problems thanks for a great piece of software. 73 thanks Morris wa4mit