Date   

locked Unexpected "AutoHide" Behavior

Russ Ravella
 

DANG !! Sorry - wrong group !! Please disregard that last post !!


locked Unexpected "AutoHide" Behavior

Russ Ravella
 

Hi Dave,

I'm starting to play with SC's "AutoHide" feature.  When I use it while not using one of my SQL filters it works as described in the documentation.  When I use it with one of my SQL filters in play, it filters out spot entries with notes containing words from my list as expected but those filtered spots do not display when I check "Display only hidden spot database entries" in the "AutoHide" dialog as they do when I'm not using an SQL filter.  I have added the expression, "and (Hidden <> 'Y')" to the SQL filters as instructed in the documentation.  I probably misread something but I can't figure out what it is.  Any help would be appreciated!

Thanks,
Russ, KR6W


locked Re: Hello

J F
 

I have received and sent text messages with JtAlert. The feature that now lets you know if a ham is offline or online is nice.  Reasons for sending texts have been wide ranging from letting a ham know how their signal is or if they need to check their time. Sometimes its just a HI to a know ham. I think it is a nice feature.

On Saturday, January 11, 2020, 3:49:46 PM CST, Bry Carling AF4K <af4k@...> wrote:


I’m really looking forward to this and it sounds like the latest version of JtALERT has finally fixed my biggest pet peeve ever! Disappearing call signs in the boxes! I think over the last two or three years a lot of people probably gave up on using the app for messaging one another, sadly.

How many people on this list use the chat feature while they are running FT8 machine codes?

Best regards - Bry Carling, AF4K





locked Re: Hello

Bry Carling AF4K <af4k@...>
 

Also - The disappearing was still happening with whatever version I was using about six months ago.

Best regards - Bry Carling, AF4K





On Jan 11, 2020, at 4:57 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 12/01/2020 8:17 am, Bry Carling AF4K wrote:
I’m really looking forward to this and it sounds like the latest version of JtALERT has finally fixed my biggest pet peeve ever! Disappearing call signs in the boxes!

Not sure what your looking forward to. The next release doesn't introduce any major new features, it is primarily bug fixes or performance tweaks.

Callsigns don't just disappear, they get cleared and replaced with new Callsigns from the new decode period. If you want to see past callsigns your best to have the Decodes window open. If the Decodes window fails to show new entries after each period, than you need to go into the JTAlert Settings (not the Decodes Settings) and tick the "Enable Decodes" checkbox in the "Window -> Decodes" section.

de Laurie VK3AMA


locked Re: Hello

Bry Carling AF4K <af4k@...>
 

Perhaps you’re reading different release notes from me then, because I just downloaded the newest release and the ones I read said that you now have a timer that can extend the amount of time the callsigns appear in the boxes on JT Alert.

Perhaps my imagination is a lot more fertile than I thought it was today.

Best regards - Bry Carling, AF4K





On Jan 11, 2020, at 4:57 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 12/01/2020 8:17 am, Bry Carling AF4K wrote:
I’m really looking forward to this and it sounds like the latest version of JtALERT has finally fixed my biggest pet peeve ever! Disappearing call signs in the boxes!

Not sure what your looking forward to. The next release doesn't introduce any major new features, it is primarily bug fixes or performance tweaks.

Callsigns don't just disappear, they get cleared and replaced with new Callsigns from the new decode period. If you want to see past callsigns your best to have the Decodes window open. If the Decodes window fails to show new entries after each period, than you need to go into the JTAlert Settings (not the Decodes Settings) and tick the "Enable Decodes" checkbox in the "Window -> Decodes" section.

de Laurie VK3AMA


locked Re: Hello

HamApps Support (VK3AMA)
 

On 12/01/2020 8:17 am, Bry Carling AF4K wrote:
I’m really looking forward to this and it sounds like the latest version of JtALERT has finally fixed my biggest pet peeve ever! Disappearing call signs in the boxes!

Not sure what your looking forward to. The next release doesn't introduce any major new features, it is primarily bug fixes or performance tweaks.

Callsigns don't just disappear, they get cleared and replaced with new Callsigns from the new decode period. If you want to see past callsigns your best to have the Decodes window open. If the Decodes window fails to show new entries after each period, than you need to go into the JTAlert Settings (not the Decodes Settings) and tick the "Enable Decodes" checkbox in the "Window -> Decodes" section.

de Laurie VK3AMA


locked Hello

Bry Carling AF4K <af4k@...>
 

I’m really looking forward to this and it sounds like the latest version of JtALERT has finally fixed my biggest pet peeve ever! Disappearing call signs in the boxes! I think over the last two or three years a lot of people probably gave up on using the app for messaging one another, sadly.

How many people on this list use the chat feature while they are running FT8 machine codes?

Best regards - Bry Carling, AF4K





locked Re: No alert on North Macedonia

HamApps Support (VK3AMA)
 

On 9/01/2020 9:57 pm, marsip@... wrote:
Both in JTAlert and in WSJT-X. But several of these, are marked as "worked before". This is confusing. Where do JTAlert get the "worked before" information from, in this case? As I understand this, there should not be any historical information readable by JTAlert. Or do I misunderstand this?

JTAlert gets worked B4 data from the logger you have enabled for logging. If you running JTAlert without an enabled logger ("NO Log" will be shown in the titlebar status text) then JTAlert maintains a minimal B4 database and adds entries to that file whenever you log a QSO. If you want to clear that file open the Settings and use the "Create New" button on the "Logging -> Log B4 Database" section.

   

Restart JTAlert after creating a new B4 database.

de Laurie VK3AMA


locked Re: Missing Bearings

HamApps Support (VK3AMA)
 

On 10/01/2020 7:35 am, WB8ASI Herb wrote:
Thanks Laurie for your usual speedy response and service.  The new beta 0009 seems to be working fine now.  At first it didn't appear to show improvement so I restarted the computer.  It still didn't appear to fix the missing bearings, but as it ran for awhile it got better and better.  More bearings appeared in every cycle til I'm now near 100% which seems normal.  
Herb,

The initial absence of Bearing data (due to missing Grid data) is to be expected as only decodes with a Grid in the message will produce a Bearing. Once a Station has been decoded with a Grid, that Grid is cached so that subsequent decodes without a Grid will still produce a Bearing. This cached Grid data is remembered across JTAlert restarts. It was this caching that was broken.

de Laurie VK3AMA


locked Re: ACLog/JTalert help

Russ Ravella
 

Yeah, exactly.  Definitely hoping for the best for you and everybody in VK land Laurie!

On Jan 9, 2020, at 6:19 AM, Ron Ochu <ronochu.sky@...> wrote:

Hello Laurie,

Thank you for the very prompt and useful feedback.  I just knew there was something I was overlooking checking the WSJT log QSO button.  Once I did that, I now get the prompt log QSO box with your program and all the blanks in ACLog are filled.  Thank you for your assistance!  It is much appreciated.  

BTW, I wish everyone in VK all the best in coping with the fires.  I am praying for cooler weather with periodic rain (not flooding) to put out the fires.

73,  Ron KO0Z

On Wed, Jan 8, 2020 at 4:20 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 9/01/2020 8:33 am, Ron Ochu wrote:
I am running ACLog 6.4 and JTAlert 2.15.1.  JTalert is posting the call sign, name and QTH of a worked FT8 station on ACLog but nothing else such as report or mode.  There used to be a pop-up window informing me that the contact was logged, but now it doesn't exist.  JTAlert used to completely work, but now it only partially works with ACLog.  I've checked the settings on both programs and they appear to be fine.  Has anyone else experienced a similar issue? 

Thank you for viewing this post.

73,  Ron KO0Z

If JTAlert is not providing a Logging success/failure message and you haven't turned off those confirmation popups, than very likely your not clicking the "OK" button of the WSJT-X "Log QSO" window.  You need to log the QSO in WSJT-X for JTAlert to detect the logging event and send the QSO details to ACLog. The report and Mode will get sent to ACLog only as part of the logging process.

de Laurie VK3AMA





locked Re: Missing Bearings

WB8ASI Herb
 

Thanks Laurie for your usual speedy response and service.  The new beta 0009 seems to be working fine now.  At first it didn't appear to show improvement so I restarted the computer.  It still didn't appear to fix the missing bearings, but as it ran for awhile it got better and better.  More bearings appeared in every cycle til I'm now near 100% which seems normal.  

On January 9, 2020 at 2:40 PM "HamApps Support (VK3AMA)" <vk3ama.ham.apps@...> wrote:

On 10/01/2020 6:04 am, WB8ASI Herb wrote:
Since upgrading to 2.15.6, I seem to be missing over half the SP bearings both on the Decodes Window and hovering over the callsigns in the Call Display area.  I haven't seen any others mention this problem, so I must have something set wrong.  Any help pointing me in the right direction would be most appreciated.  Thanks, Herb WB8ASI
Herb,

This has already been corrected for the next release. The missing bearings are due to a failure to cache grids decoded. Check your email for a link to the latest Beta to test.

de Laurie VK3AMA


 


locked Re: Missing Bearings

HamApps Support (VK3AMA)
 

On 10/01/2020 6:04 am, WB8ASI Herb wrote:
Since upgrading to 2.15.6, I seem to be missing over half the SP bearings both on the Decodes Window and hovering over the callsigns in the Call Display area.  I haven't seen any others mention this problem, so I must have something set wrong.  Any help pointing me in the right direction would be most appreciated.  Thanks, Herb WB8ASI
Herb,

This has already been corrected for the next release. The missing bearings are due to a failure to cache grids decoded. Check your email for a link to the latest Beta to test.

de Laurie VK3AMA


locked Missing Bearings

WB8ASI Herb
 

Since upgrading to 2.15.6, I seem to be missing over half the SP bearings both on the Decodes Window and hovering over the callsigns in the Call Display area.  I haven't seen any others mention this problem, so I must have something set wrong.  Any help pointing me in the right direction would be most appreciated.  Thanks, Herb WB8ASI


locked Re: Wide Graph RED waterfall

J F
 

Thank you.  The problem was in the computer sound/recording/IC-7200 properties.  It was completely down.  Somehow I must have changed it.  As soon as I adjusted that level I started getting dB in the graph on the left of WSJT-X. 

When I was trying to get sounds for JtAlert I evidently changed this level.

Thanks to all that replied.  I am happy to be back on the air in FT8.

73

Jona
KK4HMQ

On Wednesday, January 8, 2020, 10:21:55 PM CST, Michael Black via Groups.Io <mdblack98@...> wrote:


Given that you don't even show 0dB on the dB graph on the left would indicate you have either the wrong audio device selected or the audio level between the rig and computer is wrong.

Audio device on the computer should be at 0dB (right click the level slider in the recording sound device to set dB) and adjust the rig's audio playback to get 30dB on a quiet spot.

Also need to check the mixer to ensure WSJT-X's level in there is correct too.

Plus there's the microphone privacy stuff to check.

de Mike W9MDB




On Wednesday, January 8, 2020, 07:49:58 PM CST, J F via Groups.Io <kk4hmq@...> wrote:


I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time. 


locked Re: Wide Graph RED waterfall

chas cartmel
 

Perhaps the volume is too high.

Charlie

G4EST

www.g4est.me.uk

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Joe Polcari
Sent: 09 January 2020 14:00
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Wide Graph RED waterfall

 

Possibly your soundcard is misconfigured if it’s USB. Check it.

 

From: <Support@HamApps.groups.io> on behalf of "J F via Groups.Io" <kk4hmq@...>
Reply-To: <Support@HamApps.groups.io>
Date: Wednesday, January 8, 2020 at 8:50 PM
To: <Support@HamApps.groups.io>
Subject: [HamApps] Wide Graph RED waterfall

 

I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time. 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked Re: Wide Graph RED waterfall

Joe Polcari
 

Possibly your soundcard is misconfigured if it’s USB. Check it.

 

From: <Support@HamApps.groups.io> on behalf of "J F via Groups.Io" <kk4hmq@...>
Reply-To: <Support@HamApps.groups.io>
Date: Wednesday, January 8, 2020 at 8:50 PM
To: <Support@HamApps.groups.io>
Subject: [HamApps] Wide Graph RED waterfall

 

I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time. 


locked Re: ACLog/JTalert help

Ron Ochu
 

Hello Laurie,

Thank you for the very prompt and useful feedback.  I just knew there was something I was overlooking checking the WSJT log QSO button.  Once I did that, I now get the prompt log QSO box with your program and all the blanks in ACLog are filled.  Thank you for your assistance!  It is much appreciated.  

BTW, I wish everyone in VK all the best in coping with the fires.  I am praying for cooler weather with periodic rain (not flooding) to put out the fires.

73,  Ron KO0Z


On Wed, Jan 8, 2020 at 4:20 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 9/01/2020 8:33 am, Ron Ochu wrote:
I am running ACLog 6.4 and JTAlert 2.15.1.  JTalert is posting the call sign, name and QTH of a worked FT8 station on ACLog but nothing else such as report or mode.  There used to be a pop-up window informing me that the contact was logged, but now it doesn't exist.  JTAlert used to completely work, but now it only partially works with ACLog.  I've checked the settings on both programs and they appear to be fine.  Has anyone else experienced a similar issue? 

Thank you for viewing this post.

73,  Ron KO0Z

If JTAlert is not providing a Logging success/failure message and you haven't turned off those confirmation popups, than very likely your not clicking the "OK" button of the WSJT-X "Log QSO" window.  You need to log the QSO in WSJT-X for JTAlert to detect the logging event and send the QSO details to ACLog. The report and Mode will get sent to ACLog only as part of the logging process.

de Laurie VK3AMA


locked Re: No alert on North Macedonia

marsip@...
 

I have set all dxcc-prefixes as wanted, with any mode and any band, and without doing any log scan.

I have unset/unticked "Filters/Do not show Worked (B4) Callsigns", I this case I get alerts on all callsigns. Both in JTAlert and in WSJT-X. But several of these, are marked as "worked before". This is confusing. Where do JTAlert get the "worked before" information from, in this case? As I understand this, there should not be any historical information readable by JTAlert. Or do I misunderstand this?


locked Re: Wide Graph RED waterfall

Michael Black
 

Given that you don't even show 0dB on the dB graph on the left would indicate you have either the wrong audio device selected or the audio level between the rig and computer is wrong.

Audio device on the computer should be at 0dB (right click the level slider in the recording sound device to set dB) and adjust the rig's audio playback to get 30dB on a quiet spot.

Also need to check the mixer to ensure WSJT-X's level in there is correct too.

Plus there's the microphone privacy stuff to check.

de Mike W9MDB




On Wednesday, January 8, 2020, 07:49:58 PM CST, J F via Groups.Io <kk4hmq@...> wrote:


I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time. 


locked Wide Graph RED waterfall

J F
 

I searched the group and found this discussed in 2015 however the person that figured it out himself did not sign his name with call and their is no email.  So I am now posting this in the hopes someone can help me.  Below I will attach a screen shot of what I have going on.  It happened once before as you can see by the date. However I don't remember how I managed to solve it.  Radio is Icom 7200, Ham Radio Deluxe v.6.60.237, WSJT-X v2.1.2, JTAlert v2.15.6
  
 All I can remember is that it was something so simple.  Now I feel stupid for not having written down what seemed so simple at the time.