|
locked
Re: JTAlert Not Showing All Calls
Dick KC9YRA
I have seen the same problem with JTAlert not showing all call signs decoded. This appears to be random. About 1 out of 10 decodes. The number of missing call signs I have seen missing is 1 and as many as 10, as in the picture attached. I believe this started with JTAlert v2.16.5. I am currently using 2.16.6 and wsjtx v 2.2.0-rc2. The call signs missing always appear to be the ones at the beginning of the current decode cycle on the wsjtx band activity window. The call signs missing can be from any standard decode type.
Thanks, 73 Dick KC9YRA
|
|
|
|
locked
Re: Worked B4 sometimes not working
Paul AC9O
Here's another example with XE2OR....
73 Paul, AC9O
|
|
|
|
locked
Re: Incorrectly Identifying DXCC Entities Worked
Jeff - G4IUA
Thanks for sharing your findings. I'm pretty sure it happened before my brand new installation too though. You're right John; they can always be worked again - it's just a bit wasteful! However it is vital to have new DXCCs showing up. I have really common ones (DL, EA, I, etc) show in in yellow sometimes and I get all excited about a new country to work, only to find I've worked hundreds of them before!
|
|
|
|
locked
Re: Incorrectly Identifying DXCC Entities Worked
John, DK9JC / AK9JC
I can confirm this behaviour too. Log4OM latest build here. It shows DXCC worked before as new, even after a rescan of the log. Not much of an issue here. I then work them agn, that increases the chance of a QSL. :-)
|
|
|
|
locked
Worked B4 sometimes not working
Paul AC9O
Not all Worked B4 are being picked up sometimes. In the screen capture, you will see K5RAV (which I just worked a few contacts ago) highlighted but shows up in the pop-up as worked b4 on 6m. Next to it is W0IZ which I also just worked but is showing up as B4. I tried clearing the cache but no change. I use ACLog as my logger. Until I upgraded WSJT-X to v2.2.0-rc2 it was fine as far as I can tell. Been on 2.16.6 for a few days.
Hope I am describing things ok. Thanks and 73 Paul, AC9O
|
|
|
|
locked
Incorrectly Identifying DXCC Entities Worked
Jeff - G4IUA
WSJT-X (v2.2.0-rc1), Log4OM v2 (2.6.1.0), JTAlert (2.16.6) – all latest releases.
I’m not sure what I have set up incorrectly. I want JTAlert to change colour to indicate a DXCC entity needed on the band on which I’m operating. ATM I’m seeing some (but not all) DXCC entities showing in yellow when I’ve definitely worked that entity before. Log4OM correctly confirms this. JTAlert is pointing to the SQLite file used by Log4OM so there shouldn’t be any discrepancy there, and I’ve manually scanned it as well.
In ‘Wanted DXCC/Individual Bands’ I have ‘Tracking: By Individual Band’, and ‘Any Mode’ selected. All bands in use are ticked. As I click on a band (20, 17, 15 etc) the right hand side box shows the countries needed and the ‘Wanted’ number changes. When I select ‘Applications/WSJT-X/JTDX’ and tick the box ‘Colour Band Activity Callsigns….alert colours’ the callsign is sometimes shown in yellow. It’s just somehow identifying SOME already worked entities as new ones. Note that many are correct ‘worked before’ DXCC entities and are highlighted green. Any suggestions?
Jeff – G4IUA
|
|
|
|
locked
JTAlert Not Showing All Calls
Jim N6VH
Laurie,
I know this has been reported before, for previous versions of JTAlert. However, I just noticed it with 2.16.6 Release version. Also using the latest beta version of WSJT-X , 2.2.0-rc2. Occasionally, JTAlert will not display all the decoded calls. In the example in the screen captures, both calls were "B4", but only one of them was displayed in JTAlert. Both calls did show in the Decodes Window for that time slot. In another incident, a needed call didn't show in the call grid, but I was still alerted for it. I am reasonably certain my filters aren't involved, since the calls in question do display at other times. 73, Jim N6VH
.jpg)
.jpg)
.jpg)
|
|
|
|
locked
Icom 7300 DVK Macro
Irwin Darack
I am trying to write a macro that keys the Icom 7300 Voice TX memories. I have written the command in the Macro Manager, placed a button on the HRD Rig Control Screen and it does not key the rig.The Icom 7300 CAT Command is FE FE 94 E0 28 00 04 FD. Any help would be appreciated. Thanks -- Irwin KD3TB
|
|
|
|
locked
Re: JTAlert 2.16.6 working with WSJT 2.2.0-rc1
Jim Denneny
Thanks Neil. Your instructions "whitelisted Hamapps for me. JTAlert is updated.
73, Jim K7EG
|
|
|
|
locked
Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns
Paul AC9O
Also just saw this. The XE is showing up with new zone, DXCC, etc in JTAlert, but the line above is not hightlighted.
|
|
|
|
locked
Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns
Paul AC9O
Not sure if this is the same issue, but may be related.
Running JTAlert 2.16.6 and just installed WSJT-X v2.2.0-rc2. Not every time, but it will sometimes clear prior calls between decode passes for the same cycle. I will usually see all the decodes in the last cycle, but sometimes it only displays the last few. Here's screen grab of this. Note that JTAlert display starts with KO9A but above you see 3 additional decodes prior to that call. Hope this helps Paul, AC9O
|
|
|
|
locked
Re: Regarding JTAlert 2.16.5 randomly stopping display of Callsigns
dj2va@...
Hi,
I was using JTAlert 2.16.5 with wsjt-x 2.1.2 64bit and wsjt-z 2.1.2.0 mod 32 64bit for several weeks. Alerts and logging to HRD 6.7.0.xxx worked perfectly. A few days ago I also realized, that JTAlert stopped sending alerts after running for several minutes. All QSOs during that period were not logged in Hamradio Deluxe Log. I upgraded JTAlert to 2.16.6, but it's still the same. As soon as the alerts work again, also logging to HRD works. I could get JTAlert to start sending Alert by closing and restarting it. Addtionally I realized, if I just leave everything on its own, it starts to send alerts again after a while by itself. 73 Michael, DJ2VA
|
|
|
|
locked
Re: More than 36 decodes
B. Smith
The WSJT-X Decodes Window is my preference for IDing callers. There are a lot of good features in JTAlert but using the 36 boxes to find targets isn't one of them. The use of the JTAlert color codes seems to interact usefully with the WSJT-X Decodes Window, but I don't understand exactly how that is supposed to work.
|
|
|
|
locked
Re: Windows Title Bar
VE3JI
Hi Dave ... thanks for the tip ... it is in the Manage Settings / Alerts / Filters .... if one is selected "F" is displayed
73 Ian, VE3JI
|
|
|
|
locked
Re: False Positive
Richard Rohrer
I could not get 2.16.5 to install at all, all the anti-virus programs tried to delete it. I downloaded 2.16.6 and it installed with no problems.
73 Dick - KC3EF
|
|
|
|
locked
Re: More than 36 decodes
Also, you could use the Decodes Window to see the entire list. 73 Herb WB8ASI
On May 25, 2020 at 9:38 AM neil_zampella <neilz@...> wrote:
|
|
|
|
locked
Re: More than 36 decodes
neil_zampella
Not sure if Laurie can do that in this version series (2.xx), You could check the CQ only box on WSJT-X, and only see those stations calling CQ. You'll still get anyone responding to you.
Neil, KN3ILZ
|
|
|
|
locked
Re: menu has disappeared
Hi Jim Thx for youe time and also for this info, now work fine, agn 73 Edmundo CE2EC
El sáb., 23 de may. de 2020 a la(s) 12:52, Jim N6VH (N6VH@...) escribió:
--
Edmundo 73, CE2EC La Serena
|
|
|
|
locked
Re: Windows Title Bar
Dave Garber
or one of your slices is in fox mode Dave Garber VE3WEJ / VE3IE
On Mon, May 25, 2020 at 5:49 AM Dave ve3wej <ve3wej@...> wrote:
|
|
|
|
locked
Re: Windows Title Bar
Dave Garber
I believe they are referring to filters in the jtalert program, not the radio. check to see if alerts are changed, in any heading Dave Garber VE3WEJ / VE3IE
On Sun, May 24, 2020 at 8:26 PM VE3JI <ve3ji@...> wrote: Hi All
|
|
|
