|
locked
Re: B4 information Lost
WarrenG KC0GU
Jeff, Do you use JTAlert with that setup you described? I have never used JTAlert while contesting. I import the contest log into my main logging program after the contest is finished. Warren KC0GU
On Mon, Jan 10, 2022 at 5:40 AM Jeff Young <kb3hf@...> wrote:
|
|
|
|
locked
Re: B4 information Lost
Jeff Young
Mike: I am using an N3FJP RU contest log not ACLog. The instructions are clear that I have to use the manual settings because the database is different for the contest and not the ACLog database that I use normally. When not contesting, the auto setup works fine. This is specific to RTTY Roundup.
Jeff KB3HF
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Michael Black via groups.io
Sent: Sunday, January 9, 2022 10:28 PM To: Support@HamApps.groups.io Subject: Re: [HamApps] B4 information Lost
Why are you not using the Automatic configuration? That ensures you use the same database. What I don't know (and Laurie can clarify) is if you change logs in ACLog will JTAlert automatically follow?
Also...check JTAlert's Help/WSJT-X UDP Setup and use 224.0.0.1 for the UDP Server. You can then turn on "Listen for WSJT-X" too.
Mike W9MDB
On Sunday, January 9, 2022, 06:47:03 PM CST, Jeff Young <kb3hf@...> wrote:
Laurie
Here are the in my N3FJP RU, WSJT-x & JTAlert settings:
I am at a loss as to why the B43 doesn’t work.
Jeff
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jeff Young
I get a message from WSJT-X to log a contact after RR73. I guess that means l am logging from WSJT-X My comment about bands is if I go from 20m to 40m and go back to 20m, B4 info from earlier 20m contacts are gone. Jeff
-------- Original message -------- From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> Date: 1/9/22 5:06 PM (GMT-06:00) Subject: Re: [HamApps] B4 information Lost
On 10/01/2022 7:57 am, Jeff Young wrote:
|
|
|
|
locked
Lookup (Not responding)
Mike Steiner
I have been having issues ever since I install everything on a new computer.
I have been able to figure out that something is going wrong when JTAlert when looks up are made….
I’m monitoring a band, the callsigns window fills up of decoded callsigns, ever thing is good. However when I select a call to answer is when the problem starts, JTAlert stops responding. Nothing in the main or callsigns window for a few minutes (3-4 minutes). JTDX continues to work normally and the qso is made. After the 2-3 minutes JTAlert catches up and the QSO is logged into HRD.
I;m using QRZ.com and there is no last error message. Also the last lookup date, is current. And my subscription is not expired.
Thanks Mike K7QDX
|
|
|
|
locked
Re: B4 information Lost
Michael Black
Why are you not using the Automatic configuration? That ensures you use the same database. What I don't know (and Laurie can clarify) is if you change logs in ACLog will JTAlert automatically follow? Also...check JTAlert's Help/WSJT-X UDP Setup and use 224.0.0.1 for the UDP Server. You can then turn on "Listen for WSJT-X" too. Mike W9MDB
On Sunday, January 9, 2022, 06:47:03 PM CST, Jeff Young <kb3hf@...> wrote:
Laurie
Here are the in my N3FJP RU, WSJT-x & JTAlert settings:
I am at a loss as to why the B43 doesn’t work.
Jeff
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jeff Young
I get a message from WSJT-X to log a contact after RR73. I guess that means l am logging from WSJT-X My comment about bands is if I go from 20m to 40m and go back to 20m, B4 info from earlier 20m contacts are gone. Jeff
-------- Original message -------- From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> Date: 1/9/22 5:06 PM (GMT-06:00) Subject: Re: [HamApps] B4 information Lost
On 10/01/2022 7:57 am, Jeff Young wrote:
|
|
|
|
locked
MariaDB SQL Decode Issue
I successfully converted my v6,5,0.207 HRD Acess DB to MariaDB, running windows 10 WSJTX v2.5.4 and JTAlert v2.5.0.9. That is running perfectly on my Windows 10 HP Envy.
I installed the same software versions on my Windows 10 HP Spectre and the Maria DB will not decode. As a workaround I am running JTAlerts with no log and QSO forwarding WSJTX to HRD MariaDB log. The settings on both machined mirror each other. I turned of the firewall on the Spectre with no improvement. What could be causing one installation to work and the other not to? I verified JT Alert crashes when the HRD Access DB is chosen. The MariaDB does cause JTAlert to close aka Crash. Thanks in advance for your help.
|
|
|
|
locked
Re: B4 information Lost
Jeff Young
Laurie
Here are the in my N3FJP RU, WSJT-x & JTAlert settings:
I am at a loss as to why the B43 doesn’t work.
Jeff
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jeff Young
Sent: Sunday, January 9, 2022 17:29 To: Support@HamApps.groups.io Subject: Re: [HamApps] B4 information Lost
I get a message from WSJT-X to log a contact after RR73. I guess that means l am logging from WSJT-X My comment about bands is if I go from 20m to 40m and go back to 20m, B4 info from earlier 20m contacts are gone. Jeff
-------- Original message -------- From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> Date: 1/9/22 5:06 PM (GMT-06:00) Subject: Re: [HamApps] B4 information Lost
On 10/01/2022 7:57 am, Jeff Young wrote:
|
|
|
|
locked
Re: B4 information Lost
Jeff Young
I get a message from WSJT-X to log a contact after RR73. I guess that means l am logging from WSJT-X
toggle quoted messageShow quoted text
My comment about bands is if I go from 20m to 40m and go back to 20m, B4 info from earlier 20m contacts are gone. Jeff
-------- Original message -------- From: "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> Date: 1/9/22 5:06 PM (GMT-06:00) To: Support@HamApps.groups.io Subject: Re: [HamApps] B4 information Lost On 10/01/2022 7:57 am, Jeff Young
wrote:
I am running N3FJP RTTY Roundup V3.9, WSJT-X Ver 2.3.1, JTAlert Ver 2.50.9 and found that when I switched bands during the contest, I lost the B4 information in JTALart call signs screen. It seems that the only B4 contacts indicated were the one's that I worked during that current session on the band. Previous contacts on the same band before were lost. All logging to the N3FJP RU software and rig controls worked fine but I can't figure out what I set up incorrectly for the RU. When I run ACLog normally, I have not noticed the loss of B4 data. Need to find out why this happened during RU because it caused me to run a lot of dupes. Thanks. JTAlert B4 checks are done against your log and by default are band dependent. Changing band to a previously unworked band will not show the B4 for callsigns previously worked on another band. Are you using JTAlert to log the QSOs?\ de Laurie VK3AMA
|
|
|
|
locked
Re: B4 information Lost
JTAlert Support (VK3AMA)
On 10/01/2022 7:57 am, Jeff Young
wrote:
I am running N3FJP RTTY Roundup V3.9, WSJT-X Ver 2.3.1, JTAlert Ver 2.50.9 and found that when I switched bands during the contest, I lost the B4 information in JTALart call signs screen. It seems that the only B4 contacts indicated were the one's that I worked during that current session on the band. Previous contacts on the same band before were lost. All logging to the N3FJP RU software and rig controls worked fine but I can't figure out what I set up incorrectly for the RU. When I run ACLog normally, I have not noticed the loss of B4 data. Need to find out why this happened during RU because it caused me to run a lot of dupes. Thanks. JTAlert B4 checks are done against your log and by default are band dependent. Changing band to a previously unworked band will not show the B4 for callsigns previously worked on another band. Are you using JTAlert to log the QSOs?\ de Laurie VK3AMA
|
|
|
|
locked
B4 information Lost
Jeff Young
I am running N3FJP RTTY Roundup V3.9, WSJT-X Ver 2.3.1, JTAlert Ver 2.50.9 and found that when I switched bands during the contest, I lost the B4 information in JTALart call signs screen. It seems that the only B4 contacts indicated were the one's that I worked during that current session on the band. Previous contacts on the same band before were lost. All logging to the N3FJP RU software and rig controls worked fine but I can't figure out what I set up incorrectly for the RU. When I run ACLog normally, I have not noticed the loss of B4 data. Need to find out why this happened during RU because it caused me to run a lot of dupes. Thanks.
|
|
|
|
locked
JTDX io.groups
Jim Smith
It seems the JTDX io.groups mailing list has been suspended or deleted.
An announcement yesterday afternoon said: "HI all I hope things are good there The group will be suspended, closed shortly UTC" No other information regarding the sudden closure has been forthcoming. There is another support group for this software on Facebook. I'm not aware of any others.
|
|
|
|
locked
Re: Double Click on Call Does Not TX
Michael Black
In JTAlert Help/WSJT-X UDP Setup Mike W9MDB
On Saturday, January 8, 2022, 04:52:28 PM CST, John Kludt K7SYS <johnnykludt@...> wrote:
Folks, Running WSTX-2.5.3 and JT Alerts 2.50.9 on current release Win 10. All works as expected on my IC-7300. On my Flex 6700 double clicking on the callsign in WSJT-X sets the TX but double clicking on the callsign in JT Alerts does not. John
|
|
|
|
locked
Double Click on Call Does Not TX
John Kludt K7SYS
Folks,
Running WSTX-2.5.3 and JT Alerts 2.50.9 on current release Win 10. All works as expected on my IC-7300. On my Flex 6700 double clicking on the callsign in WSJT-X sets the TX but double clicking on the callsign in JT Alerts does not. John
|
|
|
|
locked
Re: JTAlert Speed
neil_zampella
Seth, since you haven't been on here long, then you haven't seen the numerous threads that were concerned with the HRD and Access issue. No debate here, but you can get the support group's back topics via a browser; you'll find them easily.
Neil, KN3ILZ
On Sat, Jan 8, 2022 at 03:56 AM, Captain Fantastic wrote:
I'm not trying to start a debate. I haven't been on here long, but I see a bit of unfounded bashing here that doesn't seem to be consistent with the spirit of helpfulness for which I got into this hobby.
|
|
|
|
locked
Re: JTAlert Speed
JTAlert Support (VK3AMA)
On 8/01/2022 5:54 pm, Captain Fantastic
wrote:
All I'm saying is... That statement I made was not a criticism of HRD 6. It was an observation based on my experiences and participants in this group over recent months trying to diagnose HRD MSAccess logs causing slowdowns in JTAlert. Up until I wrote that statement, it was only ever HRD V6 logs that were at the root of the problem. That is a fact. FWIW, NOT all HRD V6 MSAccess logs were affected. There are 3 other MSAccess log types supported by JTAlert, all using the same base code to read the MSAccess log files, that have never experienced this issue. They are DXLab DXKeeper, ACLog and its variants and the JTAlert internal B4 database. Again, this is not a criticism of HRD V6, it is an observation based on experience. de Laurie VK3AMA
|
|
|
|
locked
Re: DX Decode Country direction SP Many Missing
Jim Cooper
On 8 Jan 2022 at 9:42, Bud Governale wrote:
No. The grid is also missing.as Mike also noted, without the grid there is no calculation of azimuth or distance ... no input, no output ... math works that way !! what I do is have the 'lookup' working in the JTalert main window, which gets the grid from QRZ ... which is generally accurate ... I then type in the grid on WSJY-X and it calculates the azimuth (under the DX Call window). Sometimes the log popup window appears before I get the grid into WSJT-X, so I type in the grid in the log window as well ... hey, a little manual work keeps us alert. :)) w2jc
|
|
|
|
locked
Re: DX Decode Country direction SP Many Missing
Michael Black
If there's no grid received you won't get an azimuth. Many ops like to skip the TX2 message and you'll never see their grid unless they call CQ. Mike W9MDB
On Saturday, January 8, 2022, 08:19:27 AM CST, Bud Governale <w3ll@...> wrote:
Direction - az - for stateside decodes in the list are there but many from Countries are missing. Missing or outdated file? 73, Bud W3LL W3LL@...
|
|
|
|
locked
DX Decode Country direction SP Many Missing
Bud Governale
Direction - az - for stateside decodes in the list are there but many from Countries are missing.
Missing or outdated file? 73, Bud W3LL W3LL@...
|
|
|
|
locked
Re: JTAlert Speed
Captain Fantastic
All I'm saying is...
The statement I was objecting to is that "problems in recent months that have been due to HRD MSAccess logs, but they were all modern installs of HRD, never on the old HRD V5" is not accurate. KN3ILZ - how recent is your experience with HRD? I'm not trying to start a debate. I haven't been on here long, but I see a bit of unfounded bashing here that doesn't seem to be consistent with the spirit of helpfulness for which I got into this hobby. I'm quite happy with HRD. No problems here. Seth, KC9TLG
|
|
|
|
locked
Re: accented international characters
JTAlert Support (VK3AMA)
On 8/01/2022 6:18 am, Barry VA7GEM via groups.io wrote:
Mike from HRD picked this up and has a developer working on fixing it.Tnx for the update Barry. de Laurie VK3AMA
|
|
|
|
locked
Re: accented international characters
Barry VA7GEM
On Tue, Jan 4, 2022 at 02:02 PM, Barry VA7GEM wrote:
JTAleret is handling these characters well.Mike from HRD picked this up and has a developer working on fixing it. TVM Mike de Barry
|
|
|
