Date   

locked Re: JTAlert and N3FJP ARRL RTTY Log

Bernd - KB7AK
 

When I had the situation earlier when no states were transferred, at that time I hadn't set WSJT into contest mode, I was just having regular QSO's and tried to log them, each one failed with an error of "invalid abbreviation" in N3FJP. Once I put WSJT into contest mode, and simulated a successful QSO, by first selecting a station, then clicking Log QSO in WSJT, then filling in the blanks for the 4 fields I described before, then I was able to log a QSO and data was transferred properly. I even created a Cabrillo log file and it looked perfectly Ok.

What still puzzles me is the fact when I click a station, the following happens: The call sign is properly populated, RST R is populated with 599, ST/PR/# is empty, RST S is populated with 599, and Country is populated with the proper country name. I suspect that once the first real exchange happens, all fields will be properly updated. I wish we had a test run like they did before the contest in December to see how it works under real life conditions. I trust you that you tested everything and that it will work on Saturday.

I hope that clears up any confusion I might have caused. 


locked Re: Sound card problem.

Michael Black
 

Have you set up the audio alerts for the alerts you want?  Selected the default sound for each?

de Mike W9MDB




On Thursday, January 3, 2019, 1:03:07 PM CST, Dermot Flanagan <dermotflanagan@...> wrote:


Have installed FT v22 & JT Alertv 2.12.10 All is working except the sound card which is fine on test but no audio when FT8 running. I have reinstalled both FT and JT but still no audio. Can you help please? Thanks


locked Re: JTAlert and N3FJP ARRL RTTY Log

JTAlert Support (VK3AMA)
 

Responses inline...

On 4/01/2019 1:20 pm, Bernd - KB7AK wrote:
I followed the setup instructions in the help file and I still have the problem that the State/Province field is blank. If I simulate logging a QSO by clicking on Log QSO in WSJT and fill in the blanks, Rpt S, Rpt R, Exch S, and Exch R, then the QSO gets logged correctly with the state filled in. I will wait until Saturday to check how this works in the real world.
Please describe the steps your performing that result in no State transfer. Are the Log QSO window exchanges fields correctly populated, I suspect they aren't.

If your manually entering the exchanges in the WSJT-X Log QSO window and they are correctly logged. This indicates that the non-manual method your using is likely not filling in those exchanges. How are you performing your tests?

In the setup instructions, the title bar is described as having two additional codes set based on the contest. Based on the description I would expect those two codes to state "[RRL]" and "[RU]", mine are "[RCL]" and "[RU]", so only a match on the second code but not on the first.
"RCL" is correct. There were several iterations of the naming convention before I settled. The help file got out of sync with what JTAlert displays. "RRL" in the help file is incorrect, it should have read "RCL".

de Laurie VK3AMA


locked Re: JTAlert and N3FJP ARRL RTTY Log

Bernd - KB7AK
 

I followed the setup instructions in the help file and I still have the problem that the State/Province field is blank. If I simulate logging a QSO by clicking on Log QSO in WSJT and fill in the blanks, Rpt S, Rpt R, Exch S, and Exch R, then the QSO gets logged correctly with the state filled in. I will wait until Saturday to check how this works in the real world.

In the setup instructions, the title bar is described as having two additional codes set based on the contest. Based on the description I would expect those two codes to state "[RRL]" and "[RU]", mine are "[RCL]" and "[RU]", so only a match on the second code but not on the first.


locked Re: Sound card problem.

Dermot Flanagan <dermotflanagan@...>
 

Yes the JT alerts are not playing , I do have a number of them ticked  to sound. I did have the Ham Apps Sounds downloaded, but will check as i reinstalled the JT Alert.
Thanks for the help, will get back when I check the status of the Sound app.
De Dermot EI6FZ


locked Re: Sound card problem.

neil_zampella
 

If you're having problems with WSJT-X and audio, you should go to the YAHOO WSJT support group.  

 

Neil, KN3ILZ


locked Re: Special OP Mode Tag in title bar

JTAlert Support (VK3AMA)
 

On 4/01/2019 8:16 am, Ron W3RJW wrote:
Tnx Laurie ...  I didn't know that "Fix" would work on Win 8.1, but it does
Ron,

The Alternate Layout build is not a fix. It is simply a build that uses the traditional method for presenting a menu in a Windows form. While it was coded in response to recent Win10 issues, it is not Win10 specific and can be easily used with all the Windows versions supported by JTAlert.

de Laurie VK3AMA


locked Re: Re KI4GE

JTAlert Support (VK3AMA)
 

On 4/01/2019 9:26 am, Phil Cooper wrote:

I guess you get data from the FCC database as does DXKeeper, (and also DXView), but this is clearly wrong.

I am not sure what – if anything – you can do about this, but I thought it would be useful to know, if anyone is chasing specific States.

73 de Phil GU0SUP

Phil,

There is something that can be done, and I am working on it at the moment.

Rather than relying on a database of Callsigns versus States created with regular updates from the FCC, which for the vast majority is accurate, a database that determines the State based on the on-air grid is being coded. This will allow for those operators who change the State from which they are operating while their Callsign doesn't reflect the change.

This Grid based State database lookup will still not be 100% accurate as there are many grids that can be in 2,3,4 States. When that occurs, the lookup will default to using the State that encompasses the largest area of the 4 character Grid used on air.

This is still a WIP that has taken a bit of a holiday in recent weeks with the Holiday activities taking up a lot of my time, so I don't know when it will go live within JTAlert.

de Laurie VK3AMA
 


locked Re KI4GE

Phil Cooper
 

Laurie and the group,

 

Just before Christmas, I had a contact with KI4GE in FT8, and yesterday, I had an LoTW confirmation from him.

However, DXKeeper reported that there was a mis-match between logged data and LoTW data, informing me that I had logged FL as a State, and LoTW reported SC as the State.

 

Looking at his QRZ page shows that although he actually lives in Florida, he runs a remote station in South Carolina.

 

I guess you get data from the FCC database as does DXKeeper, (and also DXView), but this is clearly wrong.

 

I am not sure what – if anything – you can do about this, but I thought it would be useful to know, if anyone is chasing specific States.

 

73 de Phil GU0SUP


locked Re: Reporting and oddity ...

Frank Kirschner
 

That makes sense. I didn't even know the setting existed.

Thanks.

73,
Frank
KF6E


On Thu, Jan 3, 2019 at 11:46 AM Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io> wrote:

Settings/Miscellaneous/Performance
Increase the Check QSO Log Record delay time

de Mike W9MDB



On Thursday, January 3, 2019, 10:27:09 AM CST, Mike Flowers <mike.flowers@...> wrote:


Hi Gang,

 

I run JTA and DXKeeper and I sometimes receive an error message when logging that the QSO wasn’t logged.   However, the QSO has never failed to be logged in DXKeeper.

 

I think that I am getting this error message in error.

 

Does anyone on the list have the same occurrence?    And if so, is there a solution?

 

It’s not really a functional error, just one of an error message.

 

Thanks!

 

- 73 and good DX de Mike, K6MKF, Past President - NCDXC

 


locked Re: Reporting and oddity ...

Anthony
 

Mike,

Yes it started happening to me today.  If you just wait it out, it eventually logs to DX Keeper, CL and EQSL.
--

Anthony N2KI


locked Re: Special OP Mode Tag in title bar

Ron W3RJW
 

Tnx Laurie ...  I didn't know that "Fix" would work on Win 8.1, but it does ...  It just adds a line to an already crowded layout ...

I will say I have never knowingly changed the scaling of the fonts on this computer ...  That being said, how would one change the scaling to a number that will works with JTA?  ...  Does that have to be done globally?  ... Is that a known for sure good fix ??
--
73
Ron, W3RJW


locked Re: No Response to Double-Click

Frank Kirschner
 

Laurie, 

Thanks. That explains the behavior. 

73,
Frank 
KF6E 

On Thu, Jan 3, 2019, 15:26 HamApps Support (VK3AMA) <vk3ama.ham.apps@... wrote:
On 3/01/2019 9:25 am, Frank Kirschner wrote:
At one time, when I double clicked on a call displayed in JT Alert, it would set the active call in WSJT-X to be that call and enable transmit. Now sometimes it does, and sometimes it doesn't.

Is there a setting that has changed, or is there something else I need to do? It doesn't have anything to do with whether the station is calling CQ or not.

73,
Frank 
KF6E 

Frank,

You only need to perform a single-click. The double-click was less reliable and was retired a while back. A double-click should still work, as JTAlert will see it a 2 single clicks.

Keep in mind, that setup of WSJT-X in response to a Callsign click in JTAlert will only happen for CQ Decodes. While JTAlert sends the necessary command to WSJT-X regardless of the decode type, WSJT-X limits the automation to CQs only.

de Laurie VK3AMA


locked Re: No Response to Double-Click

JTAlert Support (VK3AMA)
 

On 3/01/2019 9:25 am, Frank Kirschner wrote:
At one time, when I double clicked on a call displayed in JT Alert, it would set the active call in WSJT-X to be that call and enable transmit. Now sometimes it does, and sometimes it doesn't.

Is there a setting that has changed, or is there something else I need to do? It doesn't have anything to do with whether the station is calling CQ or not.

73,
Frank 
KF6E 

Frank,

You only need to perform a single-click. The double-click was less reliable and was retired a while back. A double-click should still work, as JTAlert will see it a 2 single clicks.

Keep in mind, that setup of WSJT-X in response to a Callsign click in JTAlert will only happen for CQ Decodes. While JTAlert sends the necessary command to WSJT-X regardless of the decode type, WSJT-X limits the automation to CQs only.

de Laurie VK3AMA


locked Re: Windows 10 October Update (1809) is Back

JTAlert Support (VK3AMA)
 

On 3/01/2019 10:55 am, Dave Corio via Groups.Io wrote:
 Microsoft has been re-releasing their October Windows 10 update that had been recalled shortly after the original release. I upgraded to it today.

The main problem for JTAlert is the loss of part of the menu bar as had been reported when this update was first presented. This is easily solved by installing the "AL" version of JTAlert. There were several minor issues as well:

"Onedrive" is defaulted to "On". Uninstalled it as I use a different off-site storage.
All my custom fonts for Windows were returned to default system fonts.
My custom scrollbar widths were also returned to default system settings.
There are a couple of "new" items taking up resources, such as "Microsoft Text Entry" showing up in Task Manager. Have to track them down.
The Windows Defender antivirus appears to have some cosmetic changes although seems to operate the same.

All my drives, internal & remote, were intact. COM ports haven't changed, and audio paths (IC-7200 USB) and RealTek onboard were also intact.

The sky didn't fall and the earth is still rotating! The update took about  3 hours on 1M cable modem, and another hour to track down the listed issues.

73 es Happy New Year to all!
Dave - KB3MOW

Dave,

Thanks for that.

FWIW, I have been running Windows 1809 release since it was first published, before it was removed, and was never able to get the missing title-bar menus that many reported.

de Laurie VK3AMA


locked Re: Question on the upcoming contest

JTAlert Support (VK3AMA)
 

On 3/01/2019 11:21 pm, Tom N2XW wrote:
Can someone give me an example of the remote pc configuration for N3FJP RTTY software. I think it was posted before. But I can’t find it. 

Thanks 
Tom
N2XW
In the JTAlert help file.

From the 2.12.10 release notes...
Logging WSJT-X 2.0.0 Special Operation Mode Contest QSOs (RTTY Roundup,
 Field Day & NA VHF) to N3FJP Contest Logs (ARRL RTTY Roundup, ARRL Field
 Day & VHF respectively). Important: See JTAlert Help File for setup & usage.
 ("Tutorials -> N3FJP Contest Logs Logging" topic)

de Laurie VK3AMA


locked Re: Speaking of Title Bars

@Daveq
 

Thanks, Ron.

I’ve always had the “Updates” before. Just noticed the (!) yesterday. Haven’t changed font size in years but all is good.

Thanks for the answer.

Dave W3DLQ


locked Re: Speaking of Title Bars

JTAlert Support (VK3AMA)
 

On 3/01/2019 1:29 pm, quickskys@... wrote:
I just noticed that I now have a (!) in my title bar along with the normal info I’ve always had.  I always read the release notes but could not find anything describing it in the last few notes. 

Just wondering. 

73,
Dave  W3DLQ
"(!)" = Updates available

Sorry I missed documenting the change from "(Updates!)" to "(!)" as I tried to free up space in the titlebar.

de Laurie VK3AMA


locked Re: JTAlert and N3FJP ARRL RTTY Log

JTAlert Support (VK3AMA)
 

On 4/01/2019 2:22 am, Steve Kennick wrote:
I am posting this both in the HamApps and N3FJP Forums, so please excuse the extra bandwidth.
I must be missing something simple but I can't get JTAlert to properly log to N3FJP RTTY Log.

Running:
N3FJP RTTY Roundup Log 3.6
JTAlert 2.12.10
WSJT-X 2.0.0
Windows 10

JTAlert says I am connected to RCL and RU.

When I log a simulated QSO, JTAlert puts the State in the RST Rcvd field and the qso doesn't log. In the WSJT-X contest log, all is well. I have checked the remote PC settings and they look ok. I even tried checking the boxes to have the exchanges logged in the "other"fields and they remain blank.

I uninstalled and reinstalled RTTY Log.

I also tried the Field Day log and that works OK.

If I remember correctly, I even had a misconfiguration where I was running Roundup on WSJT-X with  RTTY Log but had the Field Day Log and Field Day File settings on JTAlert and it then did log the "Other" Fields but still didn't log the fill in the state in RTTY Log.

What am I missing?

Thanks,

Steve, AI3KS

Steve,

Did you follow the Setup instructions in the JTAlert help file?

You mention logging of Other fields, The Other fields only apply to ACLog, none of the N3FJP Contest loggers. If your seeing successful logging of Other fields, that indicates your using ACLog, not a Contest Logger. See the help file ("Tutorials -> N3FJP Contest Logs Logging" topic) for correct N3FJP Contest Loggers setup.

de Laurie VK3AMA


locked Re: Sound card problem.

JTAlert Support (VK3AMA)
 

On 4/01/2019 5:59 am:
Have installed FT v22 & JT Alertv 2.12.10 All is working except the sound card which is fine on test but no audio when FT8 running. I have reinstalled both FT and JT but still no audio. Can you help please? Thanks
OM,

Are you saying the the JTAlert alert sounds are not playing?

If so, than the likely cause is that you don't have Sound files set for the affected Alerts.
Visit each of the Alert types in the Settings Window and check if a sound file is set. You can reset to default (if you have the HamApps Sounds installed) or manually set your own files. You can test each alert sound within the Settings window.

de Laurie VK3AMA

17001 - 17020 of 39821