Date   

locked Re: : Missing contacts?

ve9dx@...
 


Good morning Laurie et All,
More on contacts that are not showing up on JT Alert.  Let me just refresh all on what is going on:
The other day I happened to hear KG3BOZ on 20 JT65.  When the call appeared CQing in the latest
WSJTx window..  Down in the JT alert window.  It appeared that BOZ was an alltime new contact.  I knew differrent so I did some investigating. 
My master log that I use and happen to like is LOGGER32. 
There I typed in KG3BOZ and found 12 contacts on both JT9 and JT65.  So what I did next was create a new .adi file.  Once completed, I did a search on KG3BOZ and found all contacts were in the .adi file and all data was indeed correct.  Nothing missing. I should note also that Logger told me exactly how many contacts were exported into that new .adi file.
This completed - It was time to import my digital log into JT alert.
How I did this is as follows:
(should say I have JT alert set up with the callsign box active rather than DXCC or US State and it does appear to be working as other stations appear fine with check marks appearing in the boxes under the bands with both JT65 and JT9)
Settings - Manage Settings - Logging (Card and LOTW both checked)
Worked B4 Database File - Create new - which I did and imported and matched exactly the number of
contacts exported by Logger32.
Standard ADIF file - enable Standard ADIF box checked.
Scan Log and update:  Did that as well and saved.
Still KG3BOZ does not appear to ever have been worked. Now have 13 band / mode contacts (added one) and none appear to have been worked.
Have to wonder if there are others as well.
Using the latest version of WSJTx and JT alert (2.5.6)
Any thoughts Laurie?
73 Andy (VE9DX)


locked Telnet Acces to HamSpots.net

f5rrs@...
 

Hello,


I use a Skimmer to follow several bands with WSJT-X (multi-instances) for both JT65 & JT9 mode on a dedicated computer in my network.


All my spots are outgoing to HamSpots.net

I use another computer with DXLab suite (so SpotCollector) and my outgoing spots from Skimmer computer are not going through my network.


1. Is it possible to have a Telnet acces to my network computer (with its TCP/IP adress and port number)

or

2. Is it possible to have a Telnet access to HamSpot.net with required mode filtering (JT65/JT9) ?


If everything is running on same computer, no issues, SpotCollector has my spots but with different computer that's an issue.

The need is : Host adress (with right filtering) / Port / Username / Password.


Any idea of implementation ?


73 - Damien F5RRS



locked Re: : Re: RE: "Chatty pane"

Laurie, VK3AMA <groups06@...>
 

On 22/01/2015 5:41 PM, f5rrs@... [HamApps] wrote:

Hello,

same request for me...
Should be very nice...

73 - Damien F5RRS

Damien,

Not sure what your requesting as the original message was not included in your post. What are you wanting?

de Laurie VK3AMA
   


locked Re: : Re: RE: "Chatty pane"

f5rrs@...
 

Hello,

same request for me...
Should be very nice...

73 - Damien F5RRS


locked Re: Missing contacts?

Laurie, VK3AMA <groups06@...>
 

On 22/01/2015 3:32 AM, ve9dx@... [HamApps] wrote:

Good afternoon all -
Over the last few days I have come upon a problem which I have done some studying into with no results.
It all started with a possibility of a new band / mode contact with KG3BOZ.  JT alert indicated I had never worked BOZ before when in fact I knew I had many times over.  Checking my master log I indeed had 12 previous contacts on various bands and modes both JT9 and JT65 and where I was hearing him was indeed a new band / mode.
Thus I did a complete download of all my JT9 and 65 contacts in .adi format.  Then I did an install into JT alert creating B4log.mdb
Doing a check - the number of contacts copied from the .adi file matches exactly the number imported into the .mdb file.  Further checked the .adi I used - all 12 contacts with BOZ appeared and the .adi file was totally normal.
Had I not heard BOZ - its not likely I would have noticed this.  This leads me to wonder if 1/ I am doing something wrong or 2/ are there other contacts not being recognized by JT alert.
Using the latest version  of WSJTx and 2.5.6 JT alert.
Any thoughts?
73 Andy VE9DX

Andy,

Are you using one of the the JTAlert supported loggers? If so, the B4log.mdb file is ignored and your log is queried for the B4 status.

de Laurie VK3AMA
   


locked Re: Spot Config

Jeff Stillinger <kb6ibb@...>
 

Excellent, I will give that a try.  Problem happens when 4 or 5 CQ’s are decoded, then a wanted State alert.  Takes a minute to figure out that none of the CQ stations are the ones you are looking for.


On Jan 20, 2015, at 23:49, 'Laurie, VK3AMA' groups06@... [HamApps] <HamApps@...> wrote:


On 21/01/2015 3:27 PM, Jeff Stillinger kb6ibb@... [HamApps] wrote:
Greetings group,


I have a configuration question.  I am working on a WAS on JT9.   I am currently being alerted to any wanted state/s, even if they are involved in a QSO.   What I would like is the configuration options for the “wanted state” alert, when the state is only calling CQ.


Thanks


DE KB6IBB
JTAlert does offer a primative Filter system for the Alerts. It is long-overdue for an overhaul. Visit the "Alerts" menu and about half-way up, enable the "Generate Alerts if ONLY CQ or QRZ". The Filters, as they are currently coded, use "OR" logic, rather than the preferred "AND" logic, so if you enable any of the other filters, say "LoTW", then you will get alerts if the decode is a CQ "OR" an LoTW user not an LoTW user calling CQ. 

FWIW, I have found getting alerted to a wanted State, even when they are in QSO with someone else a great way to get a "Heads up" that a needed State is active on the band. Especially useful when your down to the last couple of States on a Band. I didn't want to miss a rare one just because he was not calling CQ. This got me to 7Bands JT65 WAS :)

de Laurie VK3AMA
    



locked Missing contacts?

ve9dx@...
 

Good afternoon all -
Over the last few days I have come upon a problem which I have done some studying into with no results.
It all started with a possibility of a new band / mode contact with KG3BOZ.  JT alert indicated I had never worked BOZ before when in fact I knew I had many times over.  Checking my master log I indeed had 12 previous contacts on various bands and modes both JT9 and JT65 and where I was hearing him was indeed a new band / mode.
Thus I did a complete download of all my JT9 and 65 contacts in .adi format.  Then I did an install into JT alert creating B4log.mdb
Doing a check - the number of contacts copied from the .adi file matches exactly the number imported into the .mdb file.  Further checked the .adi I used - all 12 contacts with BOZ appeared and the .adi file was totally normal.
Had I not heard BOZ - its not likely I would have noticed this.  This leads me to wonder if 1/ I am doing something wrong or 2/ are there other contacts not being recognized by JT alert.
Using the latest version  of WSJTx and 2.5.6 JT alert.
Any thoughts?
73 Andy VE9DX


locked Re: Spot Config

Laurie, VK3AMA <groups06@...>
 

On 21/01/2015 3:27 PM, Jeff Stillinger kb6ibb@... [HamApps] wrote:
Greetings group,


I have a configuration question.  I am working on a WAS on JT9.   I am currently being alerted to any wanted state/s, even if they are involved in a QSO.   What I would like is the configuration options for the “wanted state” alert, when the state is only calling CQ.  


Thanks


DE KB6IBB 
JTAlert does offer a primative Filter system for the Alerts. It is long-overdue for an overhaul. Visit the "Alerts" menu and about half-way up, enable the "Generate Alerts if ONLY CQ or QRZ". The Filters, as they are currently coded, use "OR" logic, rather than the preferred "AND" logic, so if you enable any of the other filters, say "LoTW", then you will get alerts if the decode is a CQ "OR" an LoTW user not an LoTW user calling CQ.

FWIW, I have found getting alerted to a wanted State, even when they are in QSO with someone else a great way to get a "Heads up" that a needed State is active on the band. Especially useful when your down to the last couple of States on a Band. I didn't want to miss a rare one just because he was not calling CQ. This got me to 7Bands JT65 WAS :)

de Laurie VK3AMA
   


locked Spot Config

Jeff Stillinger <kb6ibb@...>
 

Greetings group,


I have a configuration question. I am working on a WAS on JT9. I am currently being alerted to any wanted state/s, even if they are involved in a QSO. What I would like is the configuration options for the “wanted state” alert, when the state is only calling CQ.


Thanks


DE KB6IBB


locked Re: : JTmacros 2.5.6 error

vk7cej@y7mail.com
 

Laurie, re "Were you interacting with JTMacros at the time?"....    the answer is no.  I was just sitting here contemplating file in general.

John


locked Re: : JTmacros 2.5.6 error

Laurie, VK3AMA <groups06@...>
 

On 18/01/2015 4:02 PM, vk7cej@... [HamApps] wrote:
Laurie, the error message popped up again today..  here is a screen shot... (attached)

73
John

Tnx John,
Important question, Where you interacting with JTMacros at the time?

Unfortunately, the line number being reported is incorrect and I am certain there are no undefined variables in the code. The true cause eludes me at the moment. I have made some code structure changes so, hopefully, the offending code will be at a different line number and if the error occurs in the next release the different line number will help me isolate the offending code. Good in theory, time will tell.

de Laurie VK3AMA
   


locked Re: : JTmacros 2.5.6 error

vk7cej@y7mail.com
 

Laurie, the error message popped up again today..  here is a screen shot... (attached)

73
John


locked Re: : RE: Click to enable halt button - location setting

Laurie, VK3AMA <groups06@...>
 

On 18/01/2015 5:27 AM, dburmester@... [HamApps] wrote:
Yes, the button exists in 2.5.6 for me too and I use it frequently.  Back (a few versions ago, I think), there was a setting that allowed us to move the location of that button to somewhere else (left) so that it wasn't so close to the "X".  Many of us would accidentally "X" and close the program when we "missed".  Not a big deal, but it was nice to have the flexibility to move it.    

73,
dale
That option was removed in version 2.5.0  (13-Nov-2014). Its mentioned in the release notes.

de Laurie VK3AMA
   


locked Re: callsigns per band broken

Laurie, VK3AMA <groups06@...>
 

On 18/01/2015 2:37 AM, fly_ul@... [HamApps] wrote:

Is the callsigns per band broken.  It was not working last night and not again this morning.  

jeff

WO4R

No its not broken. Its working fine.

In your last message  in this thread, you said that Win8.1 is now requiring a login. Sounds like some settings may have changed on your PC if that is new behaviour. Perhaps your firewall settings have changed and are now blocking the port JTAlert uses to talk to the HamSpots server for the Band data.

You can test/change the port used. Visit the Settings window, Web Services -> TCPIP Network Ports section.

de Laurie VK3AMA
   


locked Re: DK2SC CW on 3576

cosimo
 

Subject: Re: DK2SC deliberate QRM
From: "DK2OM - Wolf" <merope@t-online.de>
To: "IW5ELL" <cosimo.iw5ell@gmail.com>
Date: 11 Jan 2014 19:33 GMT

Dear Cosimo,

our Monitoring System is no band police!!! But I forwarded your message to =
our HF-Department.
73 de Wolf - DK2OM - IARUMS Region 1

"IW5ELL" schrieb:

Hello, I advise for the disruptive activities of DK2SC over JT65 signals
in 3576-3578 everynight. In attach few minutes received a 3576 USB.

TU&73 de Cosimo IW5ELL


locked DK2SC CW on 3576

ROLAND B
 

Have others noticed this station calling CQ on 3576 day after day.

Is he trying to jam JT65?

Maybe some of our German friends can make a comment.


Roley G3VIR


locked Re: : RE: Click to enable halt button - location setting

Dale Burmester
 

Yes, the button exists in 2.5.6 for me too and I use it frequently.  Back (a few versions ago, I think), there was a setting that allowed us to move the location of that button to somewhere else (left) so that it wasn't so close to the "X".  Many of us would accidentally "X" and close the program when we "missed".  Not a big deal, but it was nice to have the flexibility to move it.    

73,
dale
KA9SWE


locked Re: : RE: callsigns per band broken

fly_ul
 

After reboot out of the blue Win 8.1 requires a login password.  After I fix that it works.  I hate microsoft!!!!!!! Now I have to log on to my computer.  That will be fixed later
Jeff
wo4r


locked Re: Click to enable halt button - location setting

Dan Malcolm <dmalcolm24@...>
 

I too am using 2.5.6 and that button is still located just below the ‘X’ on my display

 

 

____________________________

Dan Malcolm CFI/II

K4SHQ

 

From: HamApps@... [mailto:HamApps@...]
Sent: Saturday, January 17, 2015 10:17 AM
To: HamApps@...
Subject: [HamApps] Click to enable halt button - location setting

 

 

Something has changed (I'm using 2.5.6 at the moment) and I can't seem to find the setting to change the location of the "Click to ENABLE WSJT-X halt after current TX" from the right to the left?   I recall that some of us requested the ability to change the location of that button because it was too close to the "X" close ... and the feature was implemented a while ago.  Is this feature still available somewhere? 

 

73,

dale

KA9SWE

 


locked Re: Click to enable halt button - location setting

Rudy Benner <rudy@...>
 

 
There are two of them.
 
ve3bdr
 

Sent: Saturday, January 17, 2015 11:17 AM
Subject: [HamApps] Click to enable halt button - location setting
 
 

Something has changed (I'm using 2.5.6 at the moment) and I can't seem to find the setting to change the location of the "Click to ENABLE WSJT-X halt after current TX" from the right to the left?   I recall that some of us requested the ability to change the location of that button because it was too close to the "X" close ... and the feature was implemented a while ago.  Is this feature still available somewhere?

 

73,

dale

KA9SWE