Date   

locked Re: activity window

HamApps Support (VK3AMA)
 

On 15/04/2021 2:28 am, f8nhf wrote:
I can't find the activity window 
even with the help I can't find it 
in the setup JTAlert section <windows/Activity is activated

thank you for your help

73 Denis F8NHF

"View -> Activity window" menu of the main JTAlert window. Or press F11 when the main JTAlert window is active (has focus).

de Laurie VK3AMA


locked Re: CQ Marathon Alert in v2.5.0 - Defect confirmed

HamApps Support (VK3AMA)
 

On 15/04/2021 2:40 am, W6XK wrote:
I frequently hover the cursor over a call sign to quickly obtain basic info about the received station, including the type of alert (if any) generated for that station.  This is helpful when more than one alert is generated for a specific station, because only the highest priority alert is color-coded.  In the former version, one or more alerts were listed in the pop-up window under the list of station info.  In v2.5.0, a needed alert is now text-highlighted, rather than listed below the station info.  How can I get a CQ Marathon alert to be shown in the pop-up window in the latest version?

Vy 73, Chet W6XK

Chet,

Tnx for the report. I can confirm this is a defect.

The Callsign tooltip does have Marathon alerted entries, but they do not display if there is no Marathon triggered status set in the data feed from the old JTAlert (where all the alerting logic still resides) and the new Callsigns window. The Marathon triggered data is not being received because it is not being sent, this is the defect. I am investigating. I should have it fixed for the next release.

de Laurie VK3AMA
 


locked Re: icon messaging #FT8

HamApps Support (VK3AMA)
 

On 14/04/2021 4:45 pm, f8nhf wrote:
you are right, for the message alert to be visible I have to increase the size of the flag to 10 at this size the window is not fluid anymore 
your idea to add a control if it is feasible or put a badge instead
 greetings

73 Denis F8NHF

FYI, the next JTAlert has a dedicated size selector for the Online (Star) icon. The size of the icon no longer uses the QSL flag size. This has already been coded and tested.

de Laurie VK3AMA


locked Re: 2.50.0 not logging propagation data

HamApps Support (VK3AMA)
 

On 14/04/2021 9:21 pm, Ron W3RJW via groups.io wrote:
2.50.0 not logging propagation data ... Item is ticked in "Logging" options.  Has been working in previous versions.

TNX
--
73
Ron, W3RJW

This is a defect. See my response at https://hamapps.groups.io/g/Support/message/34175

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

HamApps Support (VK3AMA)
 

On 15/04/2021 1:45 am, David - AK2L wrote:
Follow up to #34151
Here is an example of logging two calls with myself:

The first and third entries are from JTAlert.  The second and fourth are from WSJT-X.
The date, grid and submode are all missing.

That looks like a previously reported HRD Logbook bug.

HRD in their infinite wisdom chose to implement an ADIF parser that requires the fields in a QSO record to be in a specific order and it breaks when it receives the ADIF data from JTAlert. The ADIF files, per the official ADIF specs, do not need the data to be in a specific order, it is not a CSV file where order is mandatory. HRD eventually acknowledged this defect rather than continually blaming JTAlert, and promised a fix. Either the fix has not been forthcoming or your running an old HRD version.

I tried matching the adif field order of the WSJT-X adif data, to work around this bug, but that failed because JTAlert includes additional data, like name, QTH, Solar data, State, Zones, etc that WSJT-X does not provide, and I was flying blind not knowing what the expected order was, it is not documented.

I suggest you make sure your HRD version is the latest and if the problem persists, contact HRD support end inquire about when the adif field order defect will be corrected.

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

Bob Frostholm
 

Whoops... I apologize,,,,sorry to waste your time.

73

Bob

Ko6Lu
On 4/14/2021 11:18 AM, Laurie, VK3AMA via groups.io wrote:



On 15/04/2021 4:07 am, Bob Frostholm wrote:
Why does my Logging Options page look different than yours?

Do you really want an answer?

The difference is that my screen-capture shows the checkbox display scrolled down to reveal the settings that were not in view. Note my image had a red rectangle around the scrollbar and part of my message read "(you will need to scroll the window down to find the setting)".

de Laurie VK3AMA


--
Bob
KO6LU


locked Re: Call Sign Display Grid Disappeared

Thomas Webb
 

Problem solved!!!   In the 'View' menu, I clicked 'Call Sign Window' and it came back.

Tom, WA9AFM


locked Re: Callsign window

Paul Nicholson
 

I upgraded JTAlert yesterday, and found that double-clicking on callsigns in the Callsign window and Decodes window does not flow back to WSJT-X (v2.3.1) on my Win10 computer, which has all the current patches and has been rebooted.  Is this what you're seeing?
To test this, I just downgraded to JTAlert 2.16.17 and saw the same thing. I wonder if this isn't caused by a Windows update.
In both cases, WSJT-X seems to work as expected and JTAlert windows are populating properly but I'm unable to cause action in WSJT-X from mouse clicks in JTAlert.


locked Re: Solar Data Not Logged? - Defect Confirmed.

HamApps Support (VK3AMA)
 

On 15/04/2021 1:15 am, Jim - N4ST wrote:

Ver 2.50.0 does not seem to be logging solar data to HRD Logbook.

And I do have the box checked to do so in the JTAlert Settings.

 

Also, in the options for the Activity Window, the “Solar in the Title Bar” check box works just the opposite of what is implied.

A clear box posts the data, a checked box removes the data.

 

_________

73,

Jim – N4ST


Jim,

Tnx for the report. This is a defect.

It has been corrected for the next release.

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

Laurie, VK3AMA
 



On 15/04/2021 4:07 am, Bob Frostholm wrote:
Why does my Logging Options page look different than yours?

Do you really want an answer?

The difference is that my screen-capture shows the checkbox display scrolled down to reveal the settings that were not in view. Note my image had a red rectangle around the scrollbar and part of my message read "(you will need to scroll the window down to find the setting)".

de Laurie VK3AMA


locked Re: 2.5.0 -- AutoIt Error

Bob Frostholm
 

Laurie

Why does my Logging Options page look different than yours?

73

Bob

Ko6Lu
On 4/13/2021 4:45 PM, HamApps Support (VK3AMA) via groups.io wrote:

On 14/04/2021 6:51 am, David - AK2L wrote:
Note: I did try to have JTAlert send (UDP) the QSO to HRD, but HRD was not picking up the submode from a MFSK/FT4 QSO whereas it picked it up from WSJT-X just fine.

Likely you haven't set the "Log FT4 as ADIF 3.1.0 ..." setting under the Logging Options (you will need to scroll the window down to find the setting).



de Laurie VK3AMA


--
Bob
KO6LU


locked Call Sign Display Grid Disappeared

Thomas Webb
 

While experimenting with some of the settings in 2.5, I unclicked 'On Top' for the Call Sign Display Grid thinking this would get rid of the tool bar display.  However, the Call Sign Display Grid is gone and I can't find how to get it back.

Tom, WA9AFM


locked Re: Can't find call sign window

Brad@...
 

Well I thought I’d give you an update. When I went to delete the “callsign” file there was nothing there, I discovered that if I changed the “main” monitor though it suddenly appeared, so I’m not sure why but seems to be working.


locked CQ Marathon Alert in v2.5.0

W6XK
 

I frequently hover the cursor over a call sign to quickly obtain basic info about the received station, including the type of alert (if any) generated for that station.  This is helpful when more than one alert is generated for a specific station, because only the highest priority alert is color-coded.  In the former version, one or more alerts were listed in the pop-up window under the list of station info.  In v2.5.0, a needed alert is now text-highlighted, rather than listed below the station info.  How can I get a CQ Marathon alert to be shown in the pop-up window in the latest version?

Vy 73, Chet W6XK


locked activity window

f8nhf
 

Hello

I can't find the activity window 
even with the help I can't find it 
in the setup JTAlert section <windows/Activity is activated

thank you for your help

73 Denis F8NHF


locked Re: .NET 5 and W7 home premium

John
 

Dave,

Easiest way to find out is to install .NET5.
It'll let you know.

John
VE7KKQ


On Wed, Apr 14, 2021 at 9:10 AM David Gould <dave@...> wrote:
I have seen some postings that .NET 5 has installed OK with W7 Pro, but I have not seen anything regarding W7 Home premium (64 bit)

I am a computer user not a technician, I would appreciate any guidance on whether I can upgrade and if so how?  or am I stuck with the current version of JT Alert.

I know I can go back to previous versions of JT Alert, but can I go back to my current version of .NET (4.8) if I encounter any problems with the upgrade?

73,
Dave  G3UEG


locked Re: Getting fed up..... #FT8

Paul
 

Excellent point, the View/Show Hidden devices. That really messed me up until I found out about the need to do that and I deleted the "hidden" devices so I could reassign them as needed.

For those that haven't found this command group yet:

1. start by going to the windows Control Panel
2. select Device Manager
3. select View
4. select Show Hidden Devices
5. select Ports (COM & LPT}
6. you will see a list of the USB and LPT ports, those ports that are not available for reassignment will be greyed out. You can then select it and chose to delete it or delete it AND the driver that is needed to reinstall it.

Why would you need to do all this? Suppose you were running fine before a windows update, and one of your critical USB's was assigned to com port 8. After the windows update, windows has reassigned your USB device to com port 12 and your system no longer works because it expects to find that device on port 8. Your choices are to change all your software to com port 12 or to reassign your device back to com port 8. Trouble is, windows has locked com port 8 to the USB it was originally assigned to even though the update has also reassigned it to com port 12. You need to first remove the locked/hidden (non-existent) port to make it available for reassignment. The same thing happens with audio ports and other devices. Thank windows for not leaving things the way they were before they forced the update on us.

W2EC Paul


locked .NET 5 and W7 home premium

David Gould
 

I have seen some postings that .NET 5 has installed OK with W7 Pro, but I have not seen anything regarding W7 Home premium (64 bit)

I am a computer user not a technician, I would appreciate any guidance on whether I can upgrade and if so how?  or am I stuck with the current version of JT Alert.

I know I can go back to previous versions of JT Alert, but can I go back to my current version of .NET (4.8) if I encounter any problems with the upgrade?

73,
Dave  G3UEG


locked Re: Getting fed up..... #FT8

Ron / W4MMP
 

Hi,

I never have this problem with any Windows update.  This I believe is due to the fact that I give a name to the sound devices I care about.  It appears that Windows updates don't mess with named sound devices.  Do a similar naming operation for any USB/Serial adapters you care about.  That is performed in the device manager.  Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.  


73,
Ron / W4MMP
On 4/14/2021 11:25, Michael Black via groups.io wrote:

Yeah...I had the same problem and so did a friend of mine with the latest update.

Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...

Mike W9MDB




On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <w2ec@...> wrote:


Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us. 

W2EC Paul

On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mdblack98@...> wrote:


What "same messages" ??

Mike W9MDB




On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <ve3npi@...> wrote:


Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi


locked Re: 2.5.0 -- AutoIt Error

David - AK2L
 

Denis,
Thank you.  You have convinced me to try Maria DB.
AK2L

921 - 940 of 34867