Call Search
     

New to Ham Radio?
My Profile

Community
Articles
Forums
News
Reviews
Friends Remembered
Strays
Survey Question

Operating
Contesting
DX Cluster Spots
Propagation

Resources
Calendar
Classifieds
Ham Exams
Ham Links
List Archives
News Articles
Product Reviews
QSL Managers

Site Info
eHam Help (FAQ)
Support the site
The eHam Team
Advertising Info
Vision Statement
About eHam.net

donate to eham
   Home   Help Search  
Pages: Prev 1 [2] 3 4 5 6 7 Next   Go Down
  Print  
Author Topic: 9LY1JM Sierra Leone DXpedition  (Read 5835 times)
N5VYS
Member

Posts: 1395




Ignore
« Reply #15 on: January 11, 2019, 11:59:38 AM »

I never heard them on 80M last night in STX. They did have a good signal 30M.

Obie N5VYS
Logged
N5MOA
Member

Posts: 1709




Ignore
« Reply #16 on: January 11, 2019, 08:07:09 PM »

Still a bit of QSB, but signal coming up nicely on 160m.
Logged
N3QE
Member

Posts: 5567




Ignore
« Reply #17 on: January 11, 2019, 08:15:31 PM »

Heard them peak up a couple times on 160M CW tonight. Very loud on 75M phone.

And HUGE kudos for them spending so much time on RTTY on so many bands. With very good operators and huge rate too. I want to sharply contrast with a couple DXpeditions last year that had great signals on RTTY but didn't make any effort at all before switching entirely to FT8.
Logged
WB9LUR
Member

Posts: 494


WWW

Ignore
« Reply #18 on: January 12, 2019, 09:14:57 PM »

Check your QSO with 9LY1JM on Clublog:

https://secure.clublog.org/charts/?c=9ly1jm

Logged

. .

73, Randy / WB9LUR - http://www.CallingDX.com

. .
LA7DFA
Member

Posts: 99




Ignore
« Reply #19 on: January 12, 2019, 10:15:27 PM »

The FT8 problem is due to their weird callsign.
If you enter 9LY1JM, then WSJT-X cannot work properly in DXmode.
If you try 9L1YJM, then all is ok...  But ofcourse wrong callsign.
Logged
DK7OB
Member

Posts: 16




Ignore
« Reply #20 on: January 13, 2019, 06:15:41 AM »

The FT8 problem is due to their weird callsign.
If you enter 9LY1JM, then WSJT-X cannot work properly in DXmode.
If you try 9L1YJM, then all is ok...  But ofcourse wrong callsign.
I was able to work around this by entering the call sign in the DX Call field manually.
Looks like a software bug.

Logged
KJ4Z
Member

Posts: 1449




Ignore
« Reply #21 on: January 13, 2019, 09:09:17 AM »

The FT8 problem is due to their weird callsign.
If you enter 9LY1JM, then WSJT-X cannot work properly in DXmode.
If you try 9L1YJM, then all is ok...  But ofcourse wrong callsign.
I was able to work around this by entering the call sign in the DX Call field manually.
Looks like a software bug.

Thanks for the tip.  I needed it to work them on 15 this morning.  The usual double-clicking didn't work.  They were sending weird reports out.  Some people got no report at all, e.g. "W1XYZ 9LY1JM".  My report was literally "-".  Weird.
Logged
MM0NDX
Member

Posts: 623




Ignore
« Reply #22 on: January 13, 2019, 09:17:01 AM »

Operations at 9LY1JM. Picture by F1ULQ for DX-World readers, without copyright..



Logged

WB8VLC
Member

Posts: 617




Ignore
« Reply #23 on: January 13, 2019, 12:37:27 PM »

They had a Nice signal into Oregon on 18.140 ssb for 2 hours this morning.

It was very easy breaking thru the east coast with only a simple 24 foot high moxon and 300 watts.
Logged
N5CM
Member

Posts: 246




Ignore
« Reply #24 on: January 13, 2019, 12:54:44 PM »

I tried them on 80m several times to no avail.  Huge pileups.  Then, I got them on 30.  I tried again last night, taking a break from hunting states during the North American QSO Party (NE, WY, OR, and AK) on 80m, and got them Grin  I'm guessing the contest may have decreased the magnitude of the pileup to some extent such that my signal could be heard (100W + wire).  Just prior to lunch today, they had a great signal on 20m CW, and I was able to get through after a couple of calls.
Logged
WO7R
Member

Posts: 3891




Ignore
« Reply #25 on: January 13, 2019, 12:57:43 PM »

Just worked them (I think) on 17m F&H.  I suspect this is all about the "funny" call sign and the limitations of encoding a 77 bit message.

My messages were "clipped".  I got a signal report of "-" and an RR73 that just read "R".  And, I have a 2x1 call.  If you have a 1x3 or 2x3, you are not going to see much, I think.

Good luck everyone.
Logged
VK3HJ
Member

Posts: 2071




Ignore
« Reply #26 on: January 13, 2019, 01:58:39 PM »

I've not heard them yet.
Logged
VK3HJ
Member

Posts: 2071




Ignore
« Reply #27 on: January 14, 2019, 04:29:54 AM »

Worked on 40 m CW this afternoon, despite the best efforts of a German station to QRM me. Thanks to the op for sticking with me until the QSO completed.
Logged
N2SR
Member

Posts: 1134




Ignore
« Reply #28 on: January 14, 2019, 05:38:52 AM »

They were on 40 ssb last night.   7.120 QSX 7125.   

I did not call them, as 7.125 would put any USA station out of the band.   

Logged

If no one is doing it that way, there is a probably a very good reason.
WA2VUY
Member

Posts: 458




Ignore
« Reply #29 on: January 14, 2019, 06:35:26 AM »

They switched to listening on 7135 after this.
Quote from: N2SR l Smiley :)ink=topic=123545.msg1109375#msg1109375 date=1547473132
They were on 40 ssb last night.   7.120 QSX 7125.   

I did not call them, as 7.125 would put any USA station out of the band.   


Logged
Pages: Prev 1 [2] 3 4 5 6 7 Next   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!