Date   

locked Re: JT Alert periodically crashes.

Larry Banks
 

Including any HDMI ports.

Larry / W1DYJ


On 11/18/2021 12:42, K1DJE - Dave Corio via groups.io wrote:
On 11/18/2021 12:12 PM, Jim Cooper wrote:
On 18 Nov 2021 at 3:21, vk3xl via groups.io wrote:

  now about every 30 minutes JT Alert
stops receiving the decodes from WSJT-X again.
sure seems like something timing out ...

maybe someone on the list who is more familiar
with the internals of Windows can suggest where
to find an EVENT LOG that would say just what
happened at those specific times.

w2jc







Have you checked the power-saving features of all USB ports in use by your system? If those are on it could cause loss of connectivity resulting in crashes.


73

Dave - K1DJE









locked Re: JT Alert periodically crashes.

JTAlert Support (VK3AMA)
 

On 18/11/2021 10:21 pm, vk3xl via groups.io wrote:
Well it worked up to yesterday and now about every 30 minutes JT Alert stops receiving the decodes from WSJT-X again.
I checked all the power management settings in the device manager as well as the power settings in the control panel. and nothing has changed there.

I am confused to what has changed to cause this to come back after a week or so of trouble free 24 hour operation.

Any clues on what to check next greatly appreciated.

In a previous message https://hamapps.groups.io/g/Support/message/37778 you claim to be running WSJT-X 2.5.2.

PSKReporter shows you're running WSJT-X 2.5.0 NOT 2.5.2 as claimed.


There should not be a problem with 2.5.0 but it may be the cause.

Is this an official WSJT-X release you're running or one of the hacked clones masquerading as WSJT-X?

Please try the latest 2.5.2 release.

de Laurie VK3AMA


locked Re: JT Alert periodically crashes.

K1DJE - Dave Corio
 

On 11/18/2021 12:12 PM, Jim Cooper wrote:
On 18 Nov 2021 at 3:21, vk3xl via groups.io wrote:

now about every 30 minutes JT Alert
stops receiving the decodes from WSJT-X again.
sure seems like something timing out ...

maybe someone on the list who is more familiar
with the internals of Windows can suggest where
to find an EVENT LOG that would say just what
happened at those specific times.

w2jc





Have you checked the power-saving features of all USB ports in use by your system? If those are on it could cause loss of connectivity resulting in crashes.


73

Dave - K1DJE


locked Re: JT Alert periodically crashes.

Jim Cooper
 

On 18 Nov 2021 at 3:21, vk3xl via groups.io wrote:

now about every 30 minutes JT Alert
stops receiving the decodes from WSJT-X again.
sure seems like something timing out ...

maybe someone on the list who is more familiar
with the internals of Windows can suggest where
to find an EVENT LOG that would say just what
happened at those specific times.

w2jc


locked Re: Grid not passed correctly from WSJTX-> JTA > DXK #FT8

Rich - K1HTV
 

Thanks Jim,
Laurie found the cause of the problem and sent me a beta test version of JTA 2.50.7 which I have tested. It corrected the problem of passing the correct grid from JTA to DXK.

73,
Rich - K1HTV

On Tue, Nov 16, 2021 at 9:54 PM Jim Cooper <jim.w2jc@...> wrote:
On 16 Nov 2021 at 18:22, Rich - K1HTV wrote:

> If I understand it correctly, the QSO data is passed from WSJT-X
> through JT Alert to the DX Keeper log. If that is the case, is the
> incorrect grid being introduced by JTAlert?

Do you have the JTalert DECODES window open?
If so, what grid does it show there for the /MM ?

That is most likely what JTalert will send for the log ...
if it is EMPTY, then that might explain why an old
grid is being found and used.

From what I have seen operating, most /MM FT8 stations
do not send their current grid square very often, if at all.

Just some thoughts ...

w2jc



locked Re: JT Alert periodically crashes.

vk3xl@...
 

Well it worked up to yesterday and now about every 30 minutes JT Alert stops receiving the decodes from WSJT-X again.
I checked all the power management settings in the device manager as well as the power settings in the control panel. and nothing has changed there.

I am confused to what has changed to cause this to come back after a week or so of trouble free 24 hour operation.

Any clues on what to check next greatly appreciated.


locked Re: IOTA box ?

EDMUNDO CAMPUSANO
 

Thanks for your answer Lauren, I hope that in the future some small window will be shown for IOTA.-

My respects and thanks for JTalert.-

73 Edmundo CE2EC

El mié, 17 de nov. de 2021 a la(s) 16:44, HamApps Support (VK3AMA) (vk3ama.ham.apps@...) escribió:
On 17/11/2021 11:38 pm, EDMUNDO CAMPUSANO wrote:
I would like to know if it is possible to put a box indicating the island? or IOTA number.-?

I have a membership of xlm data in qrz and it allows me to collect this type of data.-
Greetings

--
Edmundo 73, CE2EC
La Serena

Edmundo,

Adding a dedicated IOTA input filed is on my todo list, but due to size restrictions of the current window it is not possible to add an additional field without a lot of re-coding. It is unlikely that the field will be added until the old log fields area of JTAlert is moved to the new 2.50.x series code base

While there is no IOTA input filed, JTAlert still logs any IOTA values that are returned from an XML lookup.

de Laurie VK3AMA



--
Edmundo 73, CE2EC
La Serena


locked Re: IOTA box ?

JTAlert Support (VK3AMA)
 

On 17/11/2021 11:38 pm, EDMUNDO CAMPUSANO wrote:
I would like to know if it is possible to put a box indicating the island? or IOTA number.-?

I have a membership of xlm data in qrz and it allows me to collect this type of data.-
Greetings

--
Edmundo 73, CE2EC
La Serena

Edmundo,

Adding a dedicated IOTA input filed is on my todo list, but due to size restrictions of the current window it is not possible to add an additional field without a lot of re-coding. It is unlikely that the field will be added until the old log fields area of JTAlert is moved to the new 2.50.x series code base

While there is no IOTA input filed, JTAlert still logs any IOTA values that are returned from an XML lookup.

de Laurie VK3AMA


locked Re: Grid not passed correctly from WSJTX-> JTA > DXK #FT8 - DEFECT Confirmed #FT8

JTAlert Support (VK3AMA)
 

On 17/11/2021 1:22 pm, Rich - K1HTV wrote:
In the past, when I completed an FT8 QSO with a /MM maritime mobile station in a new water grid, the grid in the WSJT-X "DX Grid" field was entered in the llog box which opened after the 73 message was received. The grid along with the rest of the QSO data was passed through JTAlert to DX Keeper and logged. However, I have noticed that after a QSO is logged, the Grid logged in DX Keeper for that QSO is a grid from an older QSO. I can't seem to find any option or checkbox in either WSJT-X, JT Alert or DX Keeper which might be related to correcting this problem.

73,
Rich - K1HTV

Rich,

I can confirm this defect. Under some circumstances the grid recorded in the WSJTX "Log QSO" window was being ignored during the logging operation. This was due to a logic error in the code. It has been corrected for the next public release.

Check your email, I have sent a link to a JTAlert pre-release build for you to test.

de Laurie VK3AMA


locked Re: jt alert window to Standard message window

JTAlert Support (VK3AMA)
 

On 18/11/2021 2:32 am, David McLennon wrote:
when I click on a call sign in the jt alert window, the callsign does not transfer to the standard message window.
Thx for any help you can provide.
73
Dave VO1LM
Just installed 2.50.7

Use the "Help -> Troubleshooting" menu and review the "WSJT-X not responding to JTAlert Callsign clicks" topic (2nd bullet point).

de Laurie VK3AMA


locked Re: JT ALERT stopped communicating with wsjt-x

JTAlert Support (VK3AMA)
 

On 18/11/2021 4:11 am, afa1yy wrote:
Another symptom,the band is unknown  (???)   I am using only 1 logging program - log4om v2. This is a recent error, it started about a week ago.  It  could be related to an upgrade in the OS? I have downloaded and reinstalled both WSJT-X and JTalert. any clues?
--
Art  K0AY


The "???m" indicates that JTAlert is not receiving receiving UDP messages from WSJTX. Something is blocking JTAlert. See my previous message regarding setting up UDP multicast

de Laurie VK3AMA


locked Re: JT ALERT stopped communicating with wsjt-x

afa1yy
 

Another symptom,the band is unknown  (???)   I am using only 1 logging program - log4om v2. This is a recent error, it started about a week ago.  It  could be related to an upgrade in the OS? I have downloaded and reinstalled both WSJT-X and JTalert. any clues?
--
Art  K0AY


locked jt alert window to Standard message window

David McLennon
 

when I click on a call sign in the jt alert window, the callsign does not transfer to the standard message window.
Thx for any help you can provide.
73
Dave VO1LM
Just installed 2.50.7


locked IOTA box ?

EDMUNDO CAMPUSANO
 

Hi Laurie

I would like to know if it is possible to put a box indicating the island? or IOTA number.-?

I have a membership of xlm data in qrz and it allows me to collect this type of data.-
Greetings

--
Edmundo 73, CE2EC
La Serena


locked Re: Grid not passed correctly from WSJTX-> JTA > DXK #FT8

Jim Cooper
 

On 16 Nov 2021 at 18:22, Rich - K1HTV wrote:

If I understand it correctly, the QSO data is passed from WSJT-X
through JT Alert to the DX Keeper log. If that is the case, is the
incorrect grid being introduced by JTAlert?
Do you have the JTalert DECODES window open?
If so, what grid does it show there for the /MM ?

That is most likely what JTalert will send for the log ...
if it is EMPTY, then that might explain why an old
grid is being found and used.

From what I have seen operating, most /MM FT8 stations
do not send their current grid square very often, if at all.

Just some thoughts ...

w2jc


locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

Jim Cooper
 

On 16 Nov 2021 at 16:11, A. Mark Gillespie (VK3BU) wrote:

1. I've only just returned to the
hobby and I am still in the process of
setting things up so the only
logging that I'm doing is in WSJT-X
and then up loading that .ADI file
to QRZ.COM.
Mark ... you're doing that the HARD WAY!!

I also use the QRZ logbook and LotW ... but
I use JTalert to upload my QSOs as they are
made DIRECTLY to QRZ.com (you do need to
have the QRZ XML subscription). It is super
simple and super easy.

Then at the end of the day, three mouse clicks
in QRZ logbook and all my new entries are sent
up to LotW magically !!

Jim w2jc


locked Grid not passed correctly from WSJTX-> JTA > DXK #FT8

Rich - K1HTV
 

In the past, when I completed an FT8 QSO with a /MM maritime mobile station in a new water grid, the grid in the WSJT-X "DX Grid" field was entered in the llog box which opened after the 73 message was received. The grid along with the rest of the QSO data was passed through JTAlert to DX Keeper and logged. However, I have noticed that after a QSO is logged, the Grid logged in DX Keeper for that QSO is a grid from an older QSO. I can't seem to find any option or checkbox in either WSJT-X, JT Alert or DX Keeper which might be related to correcting this problem.
 
I wrote to DX Lab Suite and Dave, AA6YQ suggested doing some diagnostics. I sent him the error log file with the results. It indicated that the incorrect grid was being sent to DX Keeper and not the grid that was in the WSJT-X log box. I checked the wsjtx.log file and it had the correct grid that was in the WSJT-X log box which came up after the QSO.
 
If I understand it correctly, the QSO data is passed from WSJT-X through JT Alert to the DX Keeper log. If that is the case, is the incorrect grid being introduced by JTAlert?
 
73,
Rich - K1HTV


locked Re: JTAlert - Worked B4 Working But Not Quite 100% #FT8

A. Mark Gillespie (VK3BU)
 

Hi Laurie,
1. I've only just returned to the hobby and I am still in the process of setting things up so the only logging that I'm doing is in WSJT-X and then up loading that .ADI file to QRZ.COM.
I followed the procedure in JTAlert for the initial once only import of the WSJT-X .ADI file into JTAlert. JTAlert seems to know about all my worked B4 contacts as I make them, they just aren't identified ONLY in the "Show QSO's History Popup". All my worked B4 stations have a grey background in WSJT-X and a grey box in JTAlert as I make them. The worked B4 identification is working perfectly to identify all stations as worked before, it's just the details of the previous conversations aren't included in the "Show QSO's History Popup".
2.With the setup described above, do I need to set up an additional log file somewhere?
3. I turned off Malwarebytes and Norton and it made no difference.
4. I can confirm that there are two 3D2USU entries in the WSJT-X .ADI log. The logging of new contacts into JTAlet seems to be working fine since the do get a grey background. This problem is happening with all my worked B4 contacts.
Thanks for your comments.
Cheers, Mark VK3BU



locked Re: Text in DX window

Jim Cooper
 

On 16 Nov 2021 at 14:15, Bob wrote:

now here is the dilemma my call isnTMt showing in
the window no text¦????
what window? always good idea to include a
screen shot of what you are talking about so
folks here don't have to guess, or ask a bunch
of questions to get the details.


locked Re: Text in DX window

Dave Garber
 

rx window?  in wsjt?     what version jtalert and wsjtx ( or jtdx) are you using

Dave Garber
VE3WEJ / VE3IE


On Tue, Nov 16, 2021 at 9:15 AM Bob <bobl4655@...> wrote:

 

First let me say I love JT alert . That being said. I have problem in RX frequency window. I call cq all meters say I’m putting signal out. Even get response , now here is the dilemma my call isn’t showing in the window no text…???? If you need more info please contact me I have audio that signal is going out but no text in window I read and read and didn’t find any info, one said needed to allow dx activity ticked that box nuffin, I am at a loss  kb1yxn thanking you in advance

Sent from Mail for Windows

 

2401 - 2420 of 39945