Date   

locked Re: Clowns ( LIDS )

Phil Irons <ve1bvd@...>
 

Rudy, I believe that the polite, Canadian way of saying that is "I might not always be right, but I'm NEVER wrong"!

73,

Phil/VE1BVD


On Thu, Sep 19, 2013 at 8:55 AM, Rudy Benner <rudy@...> wrote:


I am always right.
 
r
 
 
Sent: Thursday, September 19, 2013 7:46 AM
Subject: Re: [HamApps] Clowns ( LIDS )
 
 

Thanks Rudy and David. Checked my clock and seems good. But perhaps the sending station has the problem.  Since his calls never seem to result in a QSO I'll bet you are right. 
 
73
 
Ross
K3HR


On Thu, Sep 19, 2013 at 12:50 AM, Rudy Benner <rudy@...> wrote:
 
Either their clock or you clock is off. Check yours.
 
ve3bdr
 
Sent: Wednesday, September 18, 2013 11:47 PM
Subject: [HamApps] Clowns ( LIDS )
 
 
Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls.  None of them come up in the call book. :-)
 
Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88  no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.
 
No matter where you go the LIDS appear and ruin it for the rest of us.  OY!
 
Gee ........... maybe I'm missing the greatest band conditions of the century!  :-)
 
Ross
K3HR
 


On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:
 

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

 
I have a couple of questions concerning changing bands and see if it’s my
setup or this is the ways it works
 
1.       I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.       When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
 
Now the only reasons I ask is first, it’s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
 
So is this normal or is something need to be changed?
 
John Hudson
KO4XJ
 

 
 






--
Phil & Anne Irons
Sydney, Nova Scotia


locked Re: No grid and no RRR

Mike Anderson
 

Im also Guilty as charged. Especially if I see a -10 or a good sig. I just say 73s. The DXers usually dont RRR me but just send 73 and I return the same.


locked Re: No grid and no RRR

WB4CIW@...
 

Hi Again Bill,
I do, however, always send my grid.  I just short cut the last two minutes of a contact.
Frank
 
 

In a message dated 19-Sep-13 11:57:53 Mountain Daylight Time, WB4CIW@... writes:


Hi Bill
I may be one of those guys.  Instead of taking the time and sending a 1 minute transmission saying
only RRR and then another saying 73, I took a cue from a couple of DX stns and combined the two
sending RR TU LOOT 73.  The ham at the other end usually sends 73 back and I resume calling CQ
or the next station inline.
 
73, Frank
WB4CIW
 
In a message dated 19-Sep-13 9:15:44 Mountain Daylight Time, billw81@... writes:
What does it mean when the other station does not designate his grid and instead puts in a number like -3, -10,etc.?

Also, some stations skip RRR and append 73 instead. Is it proper procedure to send your 73 in this situation? Or is this interfering with his desire to speed things up?

73

Bill, Ai4PF





------------------------------------

Yahoo!7 Groups Links

<*> To visit your group on the web, go to:
    http://au.groups.yahoo.com/group/HamApps/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://au.groups.yahoo.com/group/HamApps/join
    (Yahoo! ID required)

<*> To change settings via email:
    HamApps-digest@...
    HamApps-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    HamApps-unsubscribe@...

<*> Your use of Yahoo!7 Groups is subject to:
    http://au.docs.yahoo.com/info/terms/


locked Re: No grid and no RRR

WB4CIW@...
 

Hi Bill
I may be one of those guys.  Instead of taking the time and sending a 1 minute transmission saying
only RRR and then another saying 73, I took a cue from a couple of DX stns and combined the two
sending RR TU LOOT 73.  The ham at the other end usually sends 73 back and I resume calling CQ
or the next station inline.
 
73, Frank
WB4CIW
 

In a message dated 19-Sep-13 9:15:44 Mountain Daylight Time, billw81@... writes:
What does it mean when the other station does not designate his grid and instead puts in a number like -3, -10,etc.?

Also, some stations skip RRR and append 73 instead. Is it proper procedure to send your 73 in this situation? Or is this interfering with his desire to speed things up?

73

Bill, Ai4PF





------------------------------------

Yahoo!7 Groups Links

<*> To visit your group on the web, go to:
    http://au.groups.yahoo.com/group/HamApps/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://au.groups.yahoo.com/group/HamApps/join
    (Yahoo! ID required)

<*> To change settings via email:
    HamApps-digest@...
    HamApps-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    HamApps-unsubscribe@...

<*> Your use of Yahoo!7 Groups is subject to:
    http://au.docs.yahoo.com/info/terms/


locked Re: No grid and no RRR

Mike Anderson
 

This I borrowed from one of the  files that I keep around.   Source available if needed.  ( Have to look up his call)

The standard for a QSO to be officially acknowledged usually is as follows:
(1) Both callsigns have to be transferred over the radio path in both directions without error.
(2) A report – of which kind whatsoever – has to be transferred in both directions.
(3) Both stations must get a confirmation from the other end that (1) and (2) have been successful.
My personal reading of this rule is that it claims for two types of basic requirements:
(a) The transfer of a considerable non-trivial message in either direction for mutual
identification (requirement 1)
(b) The successful realization of a dialog exclusively via the radio path with at least four very
simple transmissions in sequence (requirements 1...3)
Depending on the radio channel in use and depending on the conditions, (a) or (b) may be the
crucial part. On VHF and above bands, and propagation modes such as meteor scatter it often is (b)
while at very low signal levels (EME, LF, 160m) it is (a). (a) and (b) in combination guarantee that
the radio contact at least in principle could be used to exchange further non-trivial information.
It is obvious that there is no common sense on what constitutes a valid QSO. Some of us believe
that the simple physical detection of signals that represent the callsigns, the report, and the
acknowledgements should be sufficient. Others, as myself, demand for the transfer of the complete
amount of information, and for a dialog with a causal sequence of messages. The causality must
purely be based on information received via the radio path.
Let AAAAA and BBBBB be the callsigns of two stations. A typical minimal EME-contact has the
following principal schedule:
s tate message state message 
(A1) CQ AAAAA
(B1) AAAAA BBBBB
(A2) BBBBB AAAAA OOO OOO OOO
(B2) AAAAA BBBBB RO RO RO
(A3) BBBBB AAAAA RRR RRR RRR
(B3) AAAAA BBBBB 73 73 73
One of the requirements is to get the callsigns at both ends correct (a). Here, we will concentrate on
the second requirement (b), i.e. on the dialog between the stations until they are confident that the
other end got the required qso-information.


locked Re: Clowns ( LIDS )

Jim - N4ST
 

Not sure about WSJT-X, but JT65-HF seemed to be more tolerant at decoding
someone who was late, than someone who was early. So, in that case if his
timing is off by more than 2 seconds or so and you can decode him, he
probably can ‘t decode you. BUT, if you can’t decode a signal that you see
transmitting early on the waterfall, take a crack ant sending CHK UR CLOCK.

73,
Jim – N4ST

Despite my attempt to be humorous at 4 am this morning. (life's too short
not to have some fun).        I have seen the same decodes.    Were I to
answer  that  stream  and send  a   Check Your Clock message would that 
person (in this case in China)   been able to see that message?

Just curious.


Mike
K5NAN


locked Re: is jtalert working

fly_ul
 

Norton decided to block access to the internet. I have used this program over a year and yesterday my firewall blocked it.

I fixed it. Thanks

Great program and great support.

Jeff WO4R


locked Re: Error with ADIF SQLite on logging

George Siede
 

Laurie,

I am having this same problem here as of yesterday and again just now today when I logged a contact. Also it seems that all my previous logged contacts are not being seen - for instance it now says I need all 50 states on 20 meters JT65 when in fact I have worked just about all of them with many confirmed on LoTW.

Worked B4 does not work anymore either. I assume because it can't find the database to compare to? I am running the newest version 2.4.9 and WSJT-X v1.1, r3496. This seems to have started to happen right after I downloaded the latest callsigns database and version 2.4.9 - was all fine before that at any rate.

I tired the Scan Log and Update command but that did nothing to fix things.

George
KD0PMW

--- In HamApps@yahoogroups.com.au, "cbtimmins" <clark_timmins@...> wrote:

With 2.4.8 no issues.
Immediately after upgrade to 2.4.9 error.

Error:
JTAlert : QSO log to ADIF
FAILURE: QSO Not logged!
ERROR Message : ADIF SQLite File not found
NOTE: The QSO is still saved to the JT65-HF Log File
[OK]

Also, recognizing B4 is spotty.

My setup -
Windows 7 x64
JT65-HF Version 1.0.9.3
JT Alert 2.4.9
HRD Logbook v5 (but I don't log to that)

Settings:
Logging / Standard ADIF File
Enabled - only option used Log prop data, SFI, A-index, K-index

Log file <<user>>&#92;AppData&#92;Local&#92;Ham-Apps&#92;JTAlert&#92;AE7KL&#92;Logs&#92;AE7KL.ADI

I have downloaded the "most recent" 2.4.9 and I have tried an uninstall, re-install of 2.4.9.


locked Re: Clowns ( LIDS )

chas cartmel
 

Mike – probably not – thought that myself at one point.

 

73

Charlie

www.G4EST.me.uk

 

From: HamApps@... [mailto:HamApps@...] On Behalf Of Mike Anderson
Sent: 19 September 2013 13:57
To: HamApps@...
Subject: Re: [HamApps] Clowns ( LIDS )

 

 

Despite my attempt to be humorous at 4 am this morning. (life's too short not to have some fun).        I have seen the same decodes.    Were I to answer  that  stream  and send  a   Check Your Clock message would that  person (in this case in China)   been able to see that message?

Just curious.


Mike
K5NAN


locked Ads on Hamspots

afa1yy
 

At this time on Hamspots, "Auto refresh" has turned blue and is double underlined. When I hover over it with my mouse, an advertisement pops up. Over the past 2 days, this has happened several times with different words turning blue and being underlined.

Art K0AY


locked Re: Clowns ( LIDS )

Mike Anderson
 

Despite my attempt to be humorous at 4 am this morning. (life's too short not to have some fun).        I have seen the same decodes.    Were I to answer  that  stream  and send  a   Check Your Clock message would that  person (in this case in China)   been able to see that message?

Just curious.


Mike
K5NAN


locked Re: Clowns ( LIDS )

Thomas F Giella W4HM <w4hm@...>
 

DOH, open mouth insert foot {:<))

Yes it's a timing problem and I see that issue on occasion myself. I personally use the free "Dimension 4" software to keep my computer clock in sync.

What really stinks is when a real DX call sign get's falsely produced and printed in the software window by a timing issue and everyone goes crazy calling the non existent DX station.

73,
Thomas W4HM


Just getting a kick out of some of the clowns on JT65 on 40 meters with the
fake calls. None of them come up in the call book. :-)

Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88 no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.

No matter where you go the LIDS appear and ruin it for the rest of us. OY!

Gee ........... maybe I'm missing the greatest band conditions of the
century! :-)

Ross
K3HR


locked Re: Clowns ( LIDS )

chas cartmel
 

Ross

This was happening to a Chinese station a couple of weeks ago. He was decoding OK but his clock showed 2.4 DT so relatively stations were calling him @ -2,4, hence he was not able to decode the replies heading his way. I have found that JT65-HF can decode those stations with bigger DT values better than wspr-x although not so sensitive at below -22db

 

This guy did have a QRZ page however with an email address so I contacted him and the next day his clock was corrected and has seemed to be stable since as I hear (see) him regularly.

 

73

Charlie

www.G4EST.me.uk

 

From: HamApps@... [mailto:HamApps@...] On Behalf Of Ross Lambert
Sent: 19 September 2013 12:46
To: HamApps@...
Subject: Re: [HamApps] Clowns ( LIDS )

 

 

Thanks Rudy and David. Checked my clock and seems good. But perhaps the sending station has the problem.  Since his calls never seem to result in a QSO I'll bet you are right. 

 

73 

 

Ross

K3HR

 

On Thu, Sep 19, 2013 at 12:50 AM, Rudy Benner <rudy@...> wrote:

 

Either their clock or you clock is off. Check yours.

 

ve3bdr

 

Sent: Wednesday, September 18, 2013 11:47 PM

Subject: [HamApps] Clowns ( LIDS )

 

 

Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls.  None of them come up in the call book. :-)

 

Seeing Calls like XW9JTH purporting to be calling calls like V36VI.

4L6PQS calling X71CHT

XO4ZQQ calling W88  no suffix

6I5HEH working V35 no suffix

Other assorted gibberish.

 

No matter where you go the LIDS appear and ruin it for the rest of us.  OY!

 

Gee ........... maybe I'm missing the greatest band conditions of the century!  :-)

 

Ross

K3HR

 

 

On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:

 

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

 
I have a couple of questions concerning changing bands and see if it’s my
setup or this is the ways it works
 
1.       I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.       When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
 
Now the only reasons I ask is first, it’s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
 
So is this normal or is something need to be changed?
 
John Hudson
KO4XJ
 

 

 


locked Re: Clowns ( LIDS )

Rudy Benner <rudy@...>
 

I am always right.
 
r
 
 

Sent: Thursday, September 19, 2013 7:46 AM
Subject: Re: [HamApps] Clowns ( LIDS )
 
 

Thanks Rudy and David. Checked my clock and seems good. But perhaps the sending station has the problem.  Since his calls never seem to result in a QSO I'll bet you are right. 
 
73
 
Ross
K3HR


On Thu, Sep 19, 2013 at 12:50 AM, Rudy Benner <rudy@...> wrote:
 
Either their clock or you clock is off. Check yours.
 
ve3bdr
 
Sent: Wednesday, September 18, 2013 11:47 PM
Subject: [HamApps] Clowns ( LIDS )
 
 
Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls.  None of them come up in the call book. :-)
 
Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88  no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.
 
No matter where you go the LIDS appear and ruin it for the rest of us.  OY!
 
Gee ........... maybe I'm missing the greatest band conditions of the century!  :-)
 
Ross
K3HR
 


On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:
 

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

 
I have a couple of questions concerning changing bands and see if it’s my
setup or this is the ways it works
 
1.       I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.       When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
 
Now the only reasons I ask is first, it’s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
 
So is this normal or is something need to be changed?
 
John Hudson
KO4XJ
 

 
 


locked Re: Clowns ( LIDS )

Dr. Ross
 

Thanks Rudy and David. Checked my clock and seems good. But perhaps the sending station has the problem.  Since his calls never seem to result in a QSO I'll bet you are right. 

73 

Ross
K3HR


On Thu, Sep 19, 2013 at 12:50 AM, Rudy Benner <rudy@...> wrote:
 

Either their clock or you clock is off. Check yours.
 
ve3bdr
 
Sent: Wednesday, September 18, 2013 11:47 PM
Subject: [HamApps] Clowns ( LIDS )
 
 

Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls.  None of them come up in the call book. :-)
 
Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88  no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.
 
No matter where you go the LIDS appear and ruin it for the rest of us.  OY!
 
Gee ........... maybe I'm missing the greatest band conditions of the century!  :-)
 
Ross
K3HR
 


On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:
 

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

 
I have a couple of questions concerning changing bands and see if it’s my
setup or this is the ways it works
 
1.       I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.       When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
 
Now the only reasons I ask is first, it’s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
 
So is this normal or is something need to be changed?
 
John Hudson
KO4XJ
 

 



locked Re: Clowns ( LIDS )

Mike Anderson
 

Ross,

Those are interstellar communications coming from the Planet Niburu.�� I hope you have captured those historic communications for posterity? Perhaps you were able to record the transmissions attempting to contact the Hams of earth?� What a rare moment as� I too have� seen some of those call signs and it was only after Googling them did I find out their origin.� [Google knows everything] � You can even see videos of Niburu on YouTube.

Perhaps Laurie will add them to the database next week.


�Great� Job.


Mike
K5NAN


locked Re: Clowns ( LIDS )

Rudy Benner <rudy@...>
 

Either their clock or you clock is off. Check yours.
 
ve3bdr
 

Sent: Wednesday, September 18, 2013 11:47 PM
Subject: [HamApps] Clowns ( LIDS )
 
 

Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls.  None of them come up in the call book. :-)
 
Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88  no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.
 
No matter where you go the LIDS appear and ruin it for the rest of us.  OY!
 
Gee ........... maybe I'm missing the greatest band conditions of the century!  :-)
 
Ross
K3HR
 


On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:
 

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

 
I have a couple of questions concerning changing bands and see if it’s my
setup or this is the ways it works
 
1.       I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.       When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
 
Now the only reasons I ask is first, it’s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
 
So is this normal or is something need to be changed?
 
John Hudson
KO4XJ
 

 


locked Re: Clowns ( LIDS )

BuDJie
 

Hi Ross.....I quite often see this kind of thing happening with odd calls and also wrong grids..
after doing some searching i have noticed that the DT on the the decode line will be either 1.5 plus or -1.0 and below
this means that the calling station has a clock sequence problem
he is either starting too early hence the -1.0 or starting too late and shows 1.5
plus
on 20m a good example is FK8HG ..he will start off at approx 0.6 and within a few minutes his sig start to show the DT climbing a few minutes ago he was showing 2.1
as he is close to my QTH he starts throwing up spurious decodes as he is showing sig strength -02 and getting towards +05 at times

EU stations often show bad DT readings also....i have e-mailed a couple of my local friends when their clocks have shown bad DT and the have changed their clock programs and fixed it

i am using WSJT-X by K1JT which is very sensitive to those problems

i'll bet those "clowns" dont have good clock software as it is a big problem wth Windows......im using Linux where most modern distros auto install and setup
NTP time software....very accurate too

asi said these are my observations there may be some other things going on too

73 David VK4BDJ


On 19/09/13 13:47, Ross Lambert wrote:
�
Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls. �None of them come up in the call book. :-)

Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88 �no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.

No matter where you go the LIDS appear and ruin it for the rest of us. �OY!

Gee ........... maybe I'm missing the greatest band conditions of the century! �:-)

Ross
K3HR



On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:
�

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

�
I have a couple of questions concerning changing bands and see if it�s my
setup or this is the ways it works
�
1.������ I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.������ When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
�
Now the only reasons I ask is first, it�s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
�
So is this normal or is something need to be changed?
�
John Hudson
KO4XJ
�




locked Clowns ( LIDS )

Dr. Ross
 

Just getting a kick out of some of the clowns on JT65 on 40 meters with the fake calls.  None of them come up in the call book. :-)

Seeing Calls like XW9JTH purporting to be calling calls like V36VI.
4L6PQS calling X71CHT
XO4ZQQ calling W88  no suffix
6I5HEH working V35 no suffix
Other assorted gibberish.

No matter where you go the LIDS appear and ruin it for the rest of us.  OY!

Gee ........... maybe I'm missing the greatest band conditions of the century!  :-)

Ross
K3HR



On Wed, Sep 18, 2013 at 7:29 PM, Jim - N4ST <newsgroup@...> wrote:
 

John,

WSJT-X is not very forgiving on the CAT connection.
If the connection fails one time, there is no retry, it simply disables the
connection.
So, if you turn your rig off first or break the connection with HRD (and I'm
guessing DXLAB works the same), WSJT-X will turn its CAT interface.
I found this out the hard way by logging/spotting a couple dozen QSOs on the
wrong frequency.

73,
Jim - N4ST

From: HamApps@... [mailto:HamApps@...] On
Behalf Of John Hudson
Sent: Wednesday, September 18, 2013 08:59
To: HamApps@...
Subject: [HamApps] changing bands

 
I have a couple of questions concerning changing bands and see if it’s my
setup or this is the ways it works
 
1.       I cannot keep ENABLE CAT checked.. Almost every time I load WSJT-X
1.1 r3496 I have to go into CONFIG and check ENABLE CAT (rig = 9998
Commander for DXLab) Is this normal or is it suppose to stay checked all
times?
2.       When I do check ENABLE CAT, I can select bands from WSJT drop down
menu for bands and the rig changes fine and WSJT changes fine, all is ok.
BUT if I change bands using COMMANDER ( I have JT freqs saved in the memory
slots) the rig changes, WSJT-X changes the frequency readout but the drop
down menu showing band does not AND the freq readout is red until I select
the correct band from drop down menu
 
Now the only reasons I ask is first, it’s pain to remember to change and my
log has entered the wrong band a few times plus I got an email form someone
that need KY for contact and they seen me reporting spots on the wrong
bands..
 
So is this normal or is something need to be changed?
 
John Hudson
KO4XJ
 



locked Re: is jtalert working

Laurie, VK3AMA <groups05@...>
 

If your getting an error message when checking for updates, that is usually caused by JTAlert being unable to access the HamApps.com server to check the latest updates file. Band Activity data comes from the HamSpots.net server.

Is you internet working?
Can you access HamApps.com and HamSpots.net using your web browser?

de Laurie VK3AMA


On 19/09/2013 1:14 PM, fly_ul wrote:
My jtalert 2.4.9 was working fine till this morning.  The callsign spotting per band just stopped updating.  It still updates the decoded data.  I ran repair and it still doesnt work. When I go to program updates it states in latest version "Error".

Is this a widespread problem or an I just one of the lucky few that have a problem?