|
locked
Re: When did District of Columbia become a state?
Crazy conversation. No hallowing here. I also use CC User where all the Canadian Provinces are included under the State tab, and AK and HI are not. You can Alarm all of the above however. It's not a political statement. It's just a tool to help Alert what you might be interested in. I'm glad there are states listed at all. How about all the other Countries with their states or subdivisions that don't have their Alerts available. We should consider ourselves lucky. 73, Herb WB8ASI
On March 13, 2020 at 9:04 PM Carey Fisher <careyfisher@...> wrote:
|
|
|
|
locked
Re: When did District of Columbia become a state?
HamApps Support (VK3AMA)
On 14/03/2020 4:57 am, Carey Fisher
wrote:
I disagree! JTAlert owes its existence to providing users with an early heads up that something was decoded that will meet their personal tracking goals without the need to do manual log lookups or Browser lookups to see if a decoded Callsign should be worked. Gone are the days when I would see a new VE pop up on JT65 and scurrying off to perform a QRZ browser lookup to see if they are in zone 2, or quickly checking if a CQing station was an Lotw user before I replied. All the Alerts are generic in nature, in that they are not tied to the specific requirements of a specific Award Sponsor. Many users have personal goals that go way beyond the requirements of an ARRL Award (as an example), which is why each Alert type allows for individual or any Band/Mode tracking. Many users will try and work a Station or entity on each digital mode on each band, despite the ARRL DXCC Award not providing individual mode endorsements. Not to mention no Awards for 60m contacts. So should 60m be removed and leave it to the user to manually check their log if a Callsign decoded on 60m is needed? There are many personal goals and Awards with differing requirements. The generic nature of the Alerts with the flexible Band and Mode tracking options tries to cater to those goals and Award requirements without restriction. de Laurie VK3AMA
|
|
|
|
locked
Re: When did District of Columbia become a state?
Carey Fisher
If you use "US Primary Administrative Subdivision" then wouldn't you have to include territories like Puerto Rico, Guam, American Samoa, Northern Mariana...? There are only 50 States and there is no Worked All US Primary Administrative Subdivisions (WAUPAS) awards. It's tradition and a hallowed one at that. 73, Carey, WB4HXE
On Fri, Mar 13, 2020 at 8:57 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
--
Carey Fisher
|
|
|
|
locked
Re: When did District of Columbia become a state?
HamApps Support (VK3AMA)
On 14/03/2020 11:24 am, Ron W3RJW via
Groups.Io wrote:
OK, I'll change the name of the Alert from "Wanted US State" to " Wanted US Primary Administrative Subdivision" in line with the ADIF standard, which BTW lists "DC" as one of the valid values in the STATE enumeration. Will that make the complainers happy? Instead of the "x or 51 States wanted" status, I could change it to "x of 51 subdivisions wanted" If not "Wanted US Primary Administrative Subdivision" perhaps "Wanted US PAS" for short. FWIW, I know DC is technically not a State, but if people are going to "loose their shit" over something as trivial as this, perhaps they should also target eQSL where DC is valid for their 51 State award ,or all the different Loggers that record "DC" rather than "MD" in the Sate field (I have seen enough logs to know this is not uncommon), or QRZ,com where there XML data allows for "DC" as a State, perhaps they need to change as well, then I wouldn't have to have code in the XML parser to map DC to MD. While your at it complain to the different Contest organizers that count DC and MD as 2 separate entities. de Laurie VK3AMA
|
|
|
|
locked
Audio & Visual Alert activated for a particular called station, not for the calling station.
Mark W2OR
In the following example, the JTA DXCC alert is activated even though the needed DXCC entity (EX) is a called station. The following example is taken from WSJT-x screen :
233615 -19 0.2 1001 ~ <EX0QR> PB75A The alert occurs using using either JTA v.2.16 or v2.15. I am hoping a work-around is available to shut off the JTAlert in similar cases. Please see below. The alert is activated, apparently, because in the above example, the DXCC prefix 'EX' is needed for DXCC, and also, in the above example, the needed DXCC entity callsign appears between the unique symbols < >. In sum, the alert is activated even though the needed entity (EX) is a called station. The Netherlands DXCC entity (entity 'PA', which in this case is PB75A) is not needed and it is not part of any other alert.
|
|
|
|
locked
Re: Worked B4: Yes: Unknown Date
HamApps Support (VK3AMA)
On 14/03/2020 10:57 am, Bob Felton
wrote:
When I hover the mouse over a decoded callsign being shown as worked B4, the message "Worked B4: Yes: Unknown Date" is shown in the popup message. This happens with all Worked B4 flagged decodes. I looked at my B4logv2.mdb and there are dates listed for every entry. An example follows: Bob, What logger are you using with JTAlert? de Laurie VK3AMA
|
|
|
|
locked
Re: When did District of Columbia become a state?
Laurie,
There are 50 states in the USA not 51. DC is in the state of MD. We all hunt 50 states for WAS. Showing DC as the 51st state is just plain wrong. -- 73 Ron, W3RJW
|
|
|
|
locked
Worked B4: Yes: Unknown Date
Bob Felton
When I hover the mouse over a decoded callsign being shown as worked B4, the message "Worked B4: Yes: Unknown Date" is shown in the popup message. This happens with all Worked B4 flagged decodes. I looked at my B4logv2.mdb and there are dates listed for every entry. An example follows:
_call _band _mode _grid _date _time 9Z4Y 17 FT8 FK90 20171127 221745 Do I have a setting wrong? I note that the date and time have no formatting characters. Could that be the issue? If so, what is the correct format? Thanks in advance. -- Bob K7WLX
|
|
|
|
locked
Re: TNX73 is not a New DXCC.
Mike Anderson
Could you please remove tnx73 from the list might have been a better response. Guess I am old fashioned for courtesy.
Mike K5NAN
|
|
|
|
locked
Re: TNX73 is not a New DXCC.
HamApps Support (VK3AMA)
On 14/03/2020 8:28 am,
asobel@... wrote:
Already fixed for the next release. de Laurie VK3AMA
|
|
|
|
locked
TNX73 is not a New DXCC.
asobel@...
Dear Larry
JTalert does respond to the greeting "TNX73" as a New DXCC alert. I had a few such cases and it is quite irritating. Please remove TNX73 from JTalert DXCC list.
Amos Sobel 4X4MF.
|
|
|
|
locked
Re: JTAlert is closing (crashing) after logging or settings change
Dave Garber
my understanding is that sound card, in jtalert, is only for the alerts, not decoding anything, so if you are still hearing alerts, perhaps you have the wrong sound card selected. decoding is only via wsjt or jtdx, and their sound cards should be a different sound device Dave Garber VE3WEJ / VE3IE
On Fri, Mar 13, 2020 at 9:12 AM Rich McCabe <r.mccabe@...> wrote: That shuts sound off. Does not disable or alleviate need for sound card.
|
|
|
|
locked
Re: JTAlert loses "connection" to WSJT-X and HRD Logbook
HamApps Support (VK3AMA)
On 14/03/2020 12:05 am,
stuartliss@... wrote:
Most of the time, JTAlert displays the alerts, but sometimes it does not. Stuart, Looking at your spot data sent to HamSpots, I see you running a rather old version of WSJT-X. As a first step you should update WSJT-X. A couple of other users had a similar problem and updating their old WSJT-X versions was the fix. If the problems persist after a WSJT-X update let me know. de Laurie VK3AMA
|
|
|
|
locked
Re: When did District of Columbia become a state?
Easy folks. It's just an Alert. I like it. Just don't use it. 73, Herb WB8ASI
On March 13, 2020 at 1:57 PM Carey Fisher <careyfisher@...> wrote:
|
|
|
|
locked
Re: When did District of Columbia become a state?
Carey Fisher
Yeah, listing a 51st State is problematic. It should be removed. Maybe replace MD with MDC since DC can count for MD in some contexts. 73, Carey, WB4HXE
On Fri, Mar 13, 2020 at 1:19 PM Carl - WC4H via Groups.Io <wc4h.dx=yahoo.com@groups.io> wrote:
--
Carey Fisher
|
|
|
|
locked
Re: When did District of Columbia become a state?
Tom Melvin
If you don’t want to use it then don’t - the default is ‘as normal’ - it’s there if needed as an option.
If you do want to chase "DC" then un-tick the "Consider DC as MD" Tom -- 73’s
Tom GM8MJV (IO85) On 13 Mar 2020, at 17:19, Carl - WC4H via Groups.Io <wc4h.dx@...> wrote:
|
|
|
|
locked
Re: When did District of Columbia become a state?
Carl - WC4H
There will always be hams tracking all kinds of stuff for personal reasons. That does not mean that DC should be made into a 51st state. DC counts as MD and should not be listed as a state. It could conceivably be a multiplier for some contest (although it's MD or MDC not DC), but definitely not a state.
|
|
|
|
locked
Re: JTAlert is closing (crashing) after logging or settings change
Rich McCabe
That shuts sound off. Does not disable or alleviate need for sound card.
|
|
|
|
locked
JTAlert loses "connection" to WSJT-X and HRD Logbook
Stuart, K2YYY
Most of the time, JTAlert displays the alerts, but sometimes it does not.
It stops displaying alerts and doesn't log a QSO to HRD Logbook. I exit JTAlert and restart it and it works until the next time it fails. I'm using 2.16.1, but this problem has happened with the last few releases. Stuart, K2YYY
|
|
|
|
locked
Re: Defender Virus detected??
radio_00 <m0zeh@...>
Don't download that it has a virus in it. Download it from the proper source.
https://hamapps.com/ Thanks Steve m0zeh
|
|
|
