locked
Re: ACL, JTAlert, and Port 1100
Dave Garber
Are you trying to configure a log or the field day log sent by my LG phone
I'm sorry to bother everyone with this question, but after searching the archives I was unable to find a solution. I have been unable to connect to ACL through port 1100 via the local PC setting. I was able to do a work around by utilizing the remote PC function. However I would like to keep that set up for the Field Day and utilize the PC setting for the ACL. I am not trying to run ACL and the Contest Field Day log at the same time. I actually was not able to use the local PC option even before I loaded the Field Day log. For some reason JTAlert is just not able to find the ACL location without utilizing the remote PC function and me entering the location.
|
|
locked
Re: Grid Alerts ?
HamApps Support (VK3AMA)
On 28/06/2020 1:49 am, Al Bailey
(K8SIX) wrote:
Laurie I figured out the problem. I should have ANY MODE set instead of FT8. DUH. Thanks for the help though as I created the screenshot and saw my qso with the grid was on CW and it clicked. :) :) Al, Thanks for reporting back, sadly many don't bother. I suspected a mode mismatch. Good that it was easy to find. de Laurie VK3AMA
|
|
locked
Re: ACL, JTAlert, and Port 1100
HamApps Support (VK3AMA)
On 27/06/2020 11:00 pm, W5BT via
groups.io wrote:
Here is the screen shot. The port number will not populate or allow manual entry. I've checked the port number on ACL and it is checked and shows 1100. Bruce, The local configuration is automatic and doesn't allow for manual entry of values. The log file and port numbers are automatically populated (to avoid users selecting incorrect values) by JTAlert after reading the ACLog configuration file. With no data shown indicates that either JTAlert was unable to locate the ACLog config file in its fixed (ie not user changeable) location or JTAlert was prevented from reading it. I suggest a quick reinstall of ACLog to ensure that its config file is in the correct directory. If your running ACLog elevated (set to run as administrator) that will cause Windows to prevent JTAlert from reading the ACLog config. You need to restart JTAlert after any ACLog configuration changes. If the Local configuration option stills fails to populate, than switch JTAlert to using the Remote configuration which will allow you to populate the 1100 port and select teh ACLog file (make sure you get that correct). de Laurie VK3AMA
|
|
locked
Re: Logging to N3FPJ times out no matter the length set
HamApps Support (VK3AMA)
On 28/06/2020 11:37 am, WB5JJJ - George
wrote:
Restarted EVERYTHING and it still happens right on schedule. No huge problem, but since everything is logging as expected, I'm moving right on along with FD. Did that include a PC restart? That's the only suggestion I have, if all was working normally and now doesn't. de Laurie VK3AMA
|
|
locked
Re: JT Alerts Logging to HRD for Field day
#HRD
HamApps Support (VK3AMA)
On 28/06/2020 2:09 pm, Mike Cooper
wrote:
Any Idea why JT Alerts doesnt log the Class and ARRL Section to those field in HRD?? JTAlert has not control over how HRDLogbook interprets the standard adif exchange data sent (SRX_STRING & STX_STRING) in the logging instruction. The only requirement for JTAlert is that you enable the "Log WSJT-X Contest Exchanges..." option, under the Logging section of the Settings. In order for JTAlert to log exchanges, that data must be sent by WSJT-X and that requires WSJT-X to be running in Contest mode AND the use of Tab1, NOT Tab2. de Laurie VK3AMA
|
|
locked
JT Alerts Logging to HRD for Field day
#HRD
Mike Cooper
Any Idea why JT Alerts doesnt log the Class and ARRL Section to those field in HRD??
|
|
locked
Re: Not logging some QSOs to DXKeeper.
#DXLAB
HamApps Support (VK3AMA)
On 27/06/2020 11:35 pm, Carl - WC4H via
groups.io wrote:
Whenever you can do it. Carl,
I will need to get further debug data for another failed logging event. Please repeat the previous exercise and submit a new Support request. I don't think we need to include the DXK errorlog capture for this new test. I'll take the ongoing analysis of your problem off-list when I get your next set of files. de Laurie VK3AMA
|
|
locked
Logging to N3FPJ times out no matter the length set
About 7 hours into the FD contest, N3FPJ via JTA generates an error stating it could not confirm the contact was logged. When in fact, IT WAS LOGGED. Rechecked all the LOGGING settings and nothing has changed, but re-selected the log file and log type on AC Log sub topic just to be sure.
The error pops up exactly at the 11 second mark. This all started with about 120 contacts logged. Restarted EVERYTHING and it still happens right on schedule. No huge problem, but since everything is logging as expected, I'm moving right on along with FD. - 73's George - WB5JJJ
|
|
locked
Re: Sound file with the Kiwi accent?
HamApps Support (VK3AMA)
On 27/06/2020 9:44 pm, Timothy Brannon
wrote:
In preparation for Field Day I updated WSJT-X and JTAlert to the latest versions, including the sound files. Attached. Extract the .wav file and save it any where ever like, then use the sound Select button of the "Own Call" alert and navigate to and select this new file. de Laurie VK3AMA
|
|
locked
Re: Worked B4 list rebuild
HamApps Support (VK3AMA)
On 28/06/2020 7:00 am, Dan Osborne
wrote:
Hi Laurie - Dan, To be clear, there is no worked B4 list to rebuild, sort-of. JTAlert does maintain an in-memory cache of the Worked B4 statuses, but that is empty when JTAlert is started. This cache is dynamically updated with the B4 status of Callsigns when they are first decoded, with their B4 status determined by a one-time log lookup. de Laurie VK3AMA
|
|
locked
Worked B4 list rebuild
W5AFY Dan EM04id
Hi Laurie -
To be clear, does JTAlert rebuild the worked B4 list from the specified log file every time the application is started ???? Would not use WSJT-X without JTAlert - thanks for all your efforts ! W5AFY
|
|
locked
Re: JTAlert 2.16.8
I wholeheartedly agree with Larry W0OGH, digital wouldn't be near as much fun without your tireless efforts Laurie!
Joe N7IHB
|
|
locked
Re: ACL, JTAlert, and Port 1100
Art Olson
Bruce
toggle quoted messageShow quoted text
Uncheck the port number in acl. Manually type in a different port number. Doesn’t matter the number as I selected 2247. Recheck the box. Restart ACL. Verify the port number is what you set. Then start JTAlert it will read the ACL file and apply the port number you set in ACL Art N2AJO
On Jun 27, 2020, at 9:00 AM, W5BT via groups.io <bwtmlt@...> wrote:
|
|
locked
Re: JTAlert 2.16.8
Lawrence Godek
Your doing great. We wouldn't be having this much fun without your skills and time. Gl OM. Larry W0OGH
On 6/26/2020 7:42 PM, HamApps Support
(VK3AMA) wrote:
|
|
locked
Re: Grid Alerts ?
Laurie I figured out the problem. I should have ANY MODE set instead of FT8. DUH. Thanks for the help though as I created the screenshot and saw my qso with the grid was on CW and it clicked. :) :)
|
|
locked
Re: Not logging some QSOs to DXKeeper.
#DXLAB
Carl - WC4H
No problem Laurie.
Whenever you can do it. Many thanks. Carl - WC4H
|
|
locked
Re: ACL, JTAlert, and Port 1100
Michael Black
Click the "Remote Networked PC" -- which really means "Network Connection" "Local PC" really manes "Local File". Mike W9MDB
On Saturday, June 27, 2020, 08:00:55 AM CDT, W5BT via groups.io <bwtmlt@...> wrote:
Here is the screen shot. The port number will not populate or allow manual entry. I've checked the port number on ACL and it is checked and shows 1100. Bruce W5BT
|
|
locked
Re: ACL, JTAlert, and Port 1100
W5BT
Here is the screen shot. The port number will not populate or allow manual entry. I've checked the port number on ACL and it is checked and shows 1100.
Bruce W5BT
|
|
locked
Sound file with the Kiwi accent?
In preparation for Field Day I updated WSJT-X and JTAlert to the latest versions, including the sound files.
|
|
locked
Re: ACL, JTAlert, and Port 1100
HamApps Support (VK3AMA)
On 27/06/2020 2:43 pm, W5BT via
groups.io wrote:
I'm sorry to bother everyone with this question, but after searching the archives I was unable to find a solution. I have been unable to connect to ACL through port 1100 via the local PC setting. I was able to do a work around by utilizing the remote PC function. However I would like to keep that set up for the Field Day and utilize the PC setting for the ACL. I am not trying to run ACL and the Contest Field Day log at the same time. I actually was not able to use the local PC option even before I loaded the Field Day log. For some reason JTAlert is just not able to find the ACL location without utilizing the remote PC function and me entering the location. Bruce, If your able to connect to ACLog via the Remote Configuration than you should be able to when selecting the Local Configuration option. All the Local option does is that it reads the ACLog config file to determine the Log file path and the API port, removing you from the responsibility of manually setting the correct values. Does your local option show the correct values for those two properties, that is do they match what you set when using Remote? I suspect they may not match. Send a screen-capture of the Settings window (please not your entire desktop, just the window). This is mine with ACLog connectivity working in both Local & Remote config modes (note the Log and Port values are identical as they should be). de Laurie VK3AMA
|
|