Date   

locked Re: Oddball Callsign R6H-212

Mike Olbrisch
 

Good morning N0GM.

 

I gave your reply some thought overnight.  At first the idea that it was a SWL made sense.  But then the original message says he has been logged several times in FT8.  Unless things are different in Russia, can an SWL license allow transmissions in FT8?   I have never been to Russia, and while I have a few Russian friends, none are hams.  So I have no real understanding of it, but I somehow don’t think a Russian SWL license confers the ability to transmit on FT8.

 

The mystery continues.  Y-all have a SUPER day.  I have one more night, then 8 days off.  This COVID-19 schedule is great!

 

Vy73 – Mike – KD5KC – El Paso – Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of George Merkle
Sent: Wednesday, May 27, 2020 16:38 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

That call is similar to the call signs SW listeners in the USSR used to have.  I have a couple of those cards from the olden days.  They had to have a license to listen to SW radio.  Tells you something right there.

Every DX contest there are some calls that are not in QRZ at the time.  Maybe eventually they show up.  Mostly, I figure they are special occasion call signs.

N0GM

 

On Wednesday, May 27, 2020, 05:14:25 PM CDT, Mike Olbrisch <mike-2020@...> wrote:

 

 

Exactly.  All of my licensed friends in Europe and in Germany, and in particular my in-laws, each had to make their own account in QRZ.  This is why you will find my brother-in-law and nephew DG7NFV and DO5AL with some detail on QRZ, my sister-in-law DL1NLG with a minimal presence (she doesn’t care that much), my good friend Karsten with a very detailed contesting presence as DD1JN and the Bavarian contest Club, and my friend Klaus with no QRZ presence at all.  He is not active on HF, so he didn’t bother with QRZ.

Just because a call sign is not listed in QRZ does not automatically make it an invalid call.  PERIOD.   The amateur radio world does not revolve around QRZ and the USA.  Far from it in fact.

Perhaps the QSL card I posted will help track down info.  Or contacting any Russian friends, information might be more localized or not widely available.  If R6H-212 is an invalid call, the perpetrator has gone to a lot of effort about it.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Archibald Delfish via groups.io
Sent: Wednesday, May 27, 2020 16:03 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I have a foreign callsign also, I had to manually enter my call sign in the QRZ database.

Callsign from most foreign countries are not automatically updated in QRZ.

XS Max

 

On May 27, 2020, at 5:46 PM, Mike Olbrisch <mike-2020@...> wrote:



Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted. 


locked Re: Oddball Callsign R6H-212

Christopher Scibelli
 

I must have missed something.  I have received those Russian SWL QSLs via the buro for decades, but it seems like you worked a station who gave you his SWL call. I don't understand why a Russian ham would be giving an SWL call out over the air unless you are simply logging received QSL cards.  Glad you got your answer about the meaning of the call.


73,

Chris  NU1O




-----Original Message-----
From: Bob740 <bob@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Wed, May 27, 2020 11:02 pm
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

Thanks for all the input. Now that I know what these kinds of contacts are for I may not log them anymore. Scott answered my original question, which is how to upload a batch of records to LOTW without having these oddballs flagged as errors.

Bob
KE0SDV 


Re: Most curious solution, but it worked......

Mike Olbrisch
 

Scott, in afterthought perhaps just the fact that I reset the column widths to default, then moved them one by one from left to right was all it needed and the mouse was unnecessary.  In any case, problem solved.

Back to work, load is over 800 MW and I have 580 MW of reserve gen.  I get off in 3 hours..... and sleep!

Thanks for all you do.

Mike.


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

From: "Scott Davis via groups.io"
To: "N3FJPSoftwareUsers@groups.io"
Cc:
Sent: Tuesday May 26 2020 10:58:46AM
Subject: Re: [N3FJPSoftwareUsers] Most curious solution, but it worked......

Thanks for the good, but bizarre report Mike (and I do remember the font debacle)!

I can't imagine why that would have any affect, but I am glad you found a remedy!

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Mike Olbrisch <mike-2020@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, May 26, 2020 9:11 am
Subject: [N3FJPSoftwareUsers] Most curious solution, but it worked......

Morning all.
 
I reported a couple of days ago that I was having issues keeping my column widths in place.  No one seemed to have any answer, Scott said the programming in that area had not changed in years.  I believe them all.  I used to live on Murphy St.  If it can go wrong, it happens to me.  Scott may remember the missing font debacle.  Without Scott’s intervention, I might still be out of luck!
 
My only guess about the column issue was that maybe the little wireless keyboard with a touch-pad instead of a mouse might be the problem.  So when I shut down my system in the control room this morning, I borrowed the spare wired mouse.  When I got home, I reset the column widths, then went one-by-one and used the mouse to set the column widths as I wanted them. 
 
AND IT WORKED!  Column widths stayed where I set them as I opened and closed the program 5 times.  The 5th restart, I downloaded the new country files before restarting.  Still fine!  I guess I better keep a wired mouse on hand just in case.  This one needs to go back to work with me tonight.  It won’t be missed today, due to COVID-19 we are operating out of two control rooms.  Day shift is in the primary control room.  I and my night crew will open up and run the back-up control center starting at 1730 MDT when the day shift will shut down the primary control room and go home for 12 hours.
 
I’m headed to bed.  But I’m happy!  It was a quiet night on the grid, but 12 hours is 12 hours and I’m beat.  Y-all have a SUPER day!  Stay safe, stay well.
 
 
Mike – KD5KC -- El Paso -- Texas.
 
The canyons are calling, colorful and deep.  But I have promises to keep.
And miles to go still in my Jeep...   And miles to go still in my Jeep...
 
 
ADVENTURE:  The respectful pursuit of trouble.
 
 


Re: N3FJP Server

Dale Yanz
 

Thanks Every Ones Input...

This is one for the books. With a phone call to Spectrum tech service and trouble shooting, the cable modem was working within specs!
I did place one of my old router back into service and guess what ...... That did fix the problem and I was able to down load the Call Data Lookup file!

73's Dale KJ6IX


locked Re: Oddball Callsign R6H-212

Bob740
 

Thanks for all the input. Now that I know what these kinds of contacts are for I may not log them anymore. Scott answered my original question, which is how to upload a batch of records to LOTW without having these oddballs flagged as errors.

Bob
KE0SDV 


locked Re: Oddball Callsign R6H-212

 

Joe KJ8O beat me to it! Yes, these are shortwave-listener "call signs." I do not log these but do try to QSL when I can. I'm not sure why anyone would want to log these but I see no reason at all to upload to LoTW. Don't think these would be accepted for awards, which is the primary purpose of LoTW.

Also, QRZ.com only downloads the amateur radio licensing databases for the USA and Canada. They do not download from any other country. Call signs for any stations other than USA and Canada are added by the licensees themselves with the the help of QRZ paid members. They do not accept entries from SWLs, CBers, or anything other than amateur radio. Some other suppliers of call sign info, such as Callbook, do have agreements with some DX licensing agencies and offer the info in their services, usually for a subscription fee.

Does that help?

73,

Don N4KC
www.n4kc.com
www.donkeith.com
   
   


locked Re: Oddball Callsign R6H-212

Joseph Miller
 

Hi everyone,

I hope I am not straying from the subject matter here, but I just went and looked at my Russian QSL cards, and I found: R3M-79, UA3-155-75 and R3E-229 in my collection. All three are SWLs who send reception reports to hams and requesting QSL cards. Since R6H-212 so closely matches the format of the third call sign above, I believe the gentleman is probably a Shortwave Listener. The U.S. does not have this requirement, but some countries require prospective hams to received so many SQL verifications before they get their ham radio license. At least this has been my experience.

vy 73 de Joe KJ8O Desert Hot Springs CA

On Wed, May 27, 2020 at 3:14 PM Mike Olbrisch <mike-2020@...> wrote:

Exactly.  All of my licensed friends in Europe and in Germany, and in particular my in-laws, each had to make their own account in QRZ.  This is why you will find my brother-in-law and nephew DG7NFV and DO5AL with some detail on QRZ, my sister-in-law DL1NLG with a minimal presence (she doesn’t care that much), my good friend Karsten with a very detailed contesting presence as DD1JN and the Bavarian contest Club, and my friend Klaus with no QRZ presence at all.  He is not active on HF, so he didn’t bother with QRZ.

Just because a call sign is not listed in QRZ does not automatically make it an invalid call.  PERIOD.   The amateur radio world does not revolve around QRZ and the USA.  Far from it in fact.

Perhaps the QSL card I posted will help track down info.  Or contacting any Russian friends, information might be more localized or not widely available.  If R6H-212 is an invalid call, the perpetrator has gone to a lot of effort about it.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Archibald Delfish via groups.io
Sent: Wednesday, May 27, 2020 16:03 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I have a foreign callsign also, I had to manually enter my call sign in the QRZ database.

Callsign from most foreign countries are not automatically updated in QRZ.

XS Max



On May 27, 2020, at 5:46 PM, Mike Olbrisch <mike-2020@...> wrote:



Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted. 



--
***  Avoid internet congestion, real radio uses airwaves.  ***

Joe Miller, KJ8O
Desert Hot Springs, CA
Locator DM13sw


locked Re: Oddball Callsign R6H-212

George Merkle
 

That call is similar to the call signs SW listeners in the USSR used to have.  I have a couple of those cards from the olden days.  They had to have a license to listen to SW radio.  Tells you something right there.
Every DX contest there are some calls that are not in QRZ at the time.  Maybe eventually they show up.  Mostly, I figure they are special occasion call signs.
N0GM

On Wednesday, May 27, 2020, 05:14:25 PM CDT, Mike Olbrisch <mike-2020@...> wrote:


Exactly.  All of my licensed friends in Europe and in Germany, and in particular my in-laws, each had to make their own account in QRZ.  This is why you will find my brother-in-law and nephew DG7NFV and DO5AL with some detail on QRZ, my sister-in-law DL1NLG with a minimal presence (she doesn’t care that much), my good friend Karsten with a very detailed contesting presence as DD1JN and the Bavarian contest Club, and my friend Klaus with no QRZ presence at all.  He is not active on HF, so he didn’t bother with QRZ.

Just because a call sign is not listed in QRZ does not automatically make it an invalid call.  PERIOD.   The amateur radio world does not revolve around QRZ and the USA.  Far from it in fact.

Perhaps the QSL card I posted will help track down info.  Or contacting any Russian friends, information might be more localized or not widely available.  If R6H-212 is an invalid call, the perpetrator has gone to a lot of effort about it.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Archibald Delfish via groups.io
Sent: Wednesday, May 27, 2020 16:03 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I have a foreign callsign also, I had to manually enter my call sign in the QRZ database.

Callsign from most foreign countries are not automatically updated in QRZ.

XS Max



On May 27, 2020, at 5:46 PM, Mike Olbrisch <mike-2020@...> wrote:



Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted. 


locked Re: Oddball Callsign R6H-212

Mike Olbrisch
 

Exactly.  All of my licensed friends in Europe and in Germany, and in particular my in-laws, each had to make their own account in QRZ.  This is why you will find my brother-in-law and nephew DG7NFV and DO5AL with some detail on QRZ, my sister-in-law DL1NLG with a minimal presence (she doesn’t care that much), my good friend Karsten with a very detailed contesting presence as DD1JN and the Bavarian contest Club, and my friend Klaus with no QRZ presence at all.  He is not active on HF, so he didn’t bother with QRZ.

Just because a call sign is not listed in QRZ does not automatically make it an invalid call.  PERIOD.   The amateur radio world does not revolve around QRZ and the USA.  Far from it in fact.

Perhaps the QSL card I posted will help track down info.  Or contacting any Russian friends, information might be more localized or not widely available.  If R6H-212 is an invalid call, the perpetrator has gone to a lot of effort about it.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Archibald Delfish via groups.io
Sent: Wednesday, May 27, 2020 16:03 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I have a foreign callsign also, I had to manually enter my call sign in the QRZ database.

Callsign from most foreign countries are not automatically updated in QRZ.

XS Max



On May 27, 2020, at 5:46 PM, Mike Olbrisch <mike-2020@...> wrote:



Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted. 


Re: fldigi logging for the upcoming 070 TDW PSK31 contest

Bo W4GHV
 

Help! I have read/skimmed the whole fldigi manual.
--
73, Bo W4GHV since '54


locked Re: Oddball Callsign R6H-212

Archibald Delfish
 

I have a foreign callsign also, I had to manually enter my call sign in the QRZ database.
Callsign from most foreign countries are not automatically updated in QRZ.

XS Max

On May 27, 2020, at 5:46 PM, Mike Olbrisch <mike-2020@...> wrote:



Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted.  _._,_._,_


locked Re: Oddball Callsign R6H-212

Lou Everett, Sr.
 

First!  I am not ignorant, neither is anyone else on here.  We are hams and have an explorational worldview.  I, and many others on here were with QRZ.COM Back in their beginning.  We know how hard the ownership works to ensure accurate data, which by the way is down loaded directly from the FCC and other foreign entities, and you can take that to the bank.  Plus, I did not say that QRZ.COM was perfect.  So before you accuse anyone of being ignorant get all your facts straight.

Lou WA5LOU



On Wed, May 27, 2020 at 4:46 PM Mike Olbrisch <mike-2020@...> wrote:

Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted.  And declaring that if a call sign doesn’t exist in QRZ it is not a valid call is just ignorant.

 

My good friend Klaus from near Schweinfurt Germany is DL9NAE.  Look him up on QRZ.

 

 

But look him up on the German license bureau and by golly he is there…..

 

 

 

Unless a foreign amateur deliberately makes the effort to place their data in QRZ, it may not be there.  One should never assume that just because QRZ does not show a call sign, that call sign is invalid.  If I have this wrong, somebody please notify Klaus his license is invalid according to QRZ…..  See what Klaus says.

 

You are probably looking at a special event station that isn’t well documented outside Russia.  If you know any Russian hams, perhaps a direct E-mail to them might gather more information.  That is where I would start.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Frank MacKenzie-Lamb
Sent: Wednesday, May 27, 2020 15:27 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

Try without the dash maybe?

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of nb7o
Sent: Wednesday, May 27, 2020 4:52 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I googled R6H-212 and got a few hits.  Looks like it is a club call with Victor as the operator.  Give it a try and see if you can find enough info to make LOTW happy.

 

Kevin/NB7O

--
Lou WA5LOU



locked Re: Oddball Callsign R6H-212

Mike Olbrisch
 

One of his on-line QSL cards has several club or award numbers…..  perhaps they can be tracked down for more info.  He also has an account on E-QSL, might be worth investigating.

 

 

 

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Mike Olbrisch
Sent: Wednesday, May 27, 2020 15:46 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted.  And declaring that if a call sign doesn’t exist in QRZ it is not a valid call is just ignorant.

 

My good friend Klaus from near Schweinfurt Germany is DL9NAE.  Look him up on QRZ.

 

 

But look him up on the German license bureau and by golly he is there…..

 

 

 

Unless a foreign amateur deliberately makes the effort to place their data in QRZ, it may not be there.  One should never assume that just because QRZ does not show a call sign, that call sign is invalid.  If I have this wrong, somebody please notify Klaus his license is invalid according to QRZ…..  See what Klaus says.

 

You are probably looking at a special event station that isn’t well documented outside Russia.  If you know any Russian hams, perhaps a direct E-mail to them might gather more information.  That is where I would start.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Frank MacKenzie-Lamb
Sent: Wednesday, May 27, 2020 15:27 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

Try without the dash maybe?

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of nb7o
Sent: Wednesday, May 27, 2020 4:52 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I googled R6H-212 and got a few hits.  Looks like it is a club call with Victor as the operator.  Give it a try and see if you can find enough info to make LOTW happy.

 

Kevin/NB7O


locked Re: Oddball Callsign R6H-212

Mike Olbrisch
 

Just sayin, but expecting QRZ.COM to have accurate data on every foreign amateur station is pretty short-sighted.  And declaring that if a call sign doesn’t exist in QRZ it is not a valid call is just ignorant.

 

My good friend Klaus from near Schweinfurt Germany is DL9NAE.  Look him up on QRZ.

 

 

But look him up on the German license bureau and by golly he is there…..

 

 

 

Unless a foreign amateur deliberately makes the effort to place their data in QRZ, it may not be there.  One should never assume that just because QRZ does not show a call sign, that call sign is invalid.  If I have this wrong, somebody please notify Klaus his license is invalid according to QRZ…..  See what Klaus says.

 

You are probably looking at a special event station that isn’t well documented outside Russia.  If you know any Russian hams, perhaps a direct E-mail to them might gather more information.  That is where I would start.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Frank MacKenzie-Lamb
Sent: Wednesday, May 27, 2020 15:27 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

Try without the dash maybe?

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of nb7o
Sent: Wednesday, May 27, 2020 4:52 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I googled R6H-212 and got a few hits.  Looks like it is a club call with Victor as the operator.  Give it a try and see if you can find enough info to make LOTW happy.

 

Kevin/NB7O


locked Re: Oddball Callsign R6H-212

Mel Marcus
 

But L would indicate confirmed by LOTW

-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212
From: "Scott Davis via groups.io" <SNKDavis@...>
Date: Wed, May 27, 2020 3:38 pm
To: "N3FJPSoftwareUsers@groups.io" <N3FJPSoftwareUsers@groups.io>

Hi Bob,

Thanks for your e-mail.  If you put an L in the Sent Confirmed By field, AC Log will no longer hand the QSO record to TQSL for upload.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Bob740 <bob@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, May 27, 2020 4:19 pm
Subject: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

I worked a guy in European Russia 3 times on FT8 with the callsign R6H-212. His real callsign must be different, but I have not been able to find it. He is listed with this callsign on the Russian QRZ.ru website (without an email address) but is not listed on QRZ.com. My problem: The records won't upload to LOTW, which is expected. That would be fine except I get an error each time I upload a batch of  records to LOTW. I would like to retain these records b/c I did work this station, but I want to avoid having upload errors for LOTW. The records did upload to eQSL so no problem there.

Thanks,
Bob
KE0SDV


locked Re: Oddball Callsign R6H-212

Frank MacKenzie-Lamb
 

Try without the dash maybe?

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of nb7o
Sent: Wednesday, May 27, 2020 4:52 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

I googled R6H-212 and got a few hits.  Looks like it is a club call with Victor as the operator.  Give it a try and see if you can find enough info to make LOTW happy.

 

Kevin/NB7O


locked Re: Oddball Callsign R6H-212

Frank MacKenzie-Lamb
 

I agree as QRZ is right on top of new or changed callsigns…

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Lou Everett, Sr.
Sent: Wednesday, May 27, 2020 4:38 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Oddball Callsign R6H-212

 

My rule of thumb is:  If I can’t find a particular call in QRZ.COM, then as far as I’m concerned, it is an invalid call.  

 

My two cents worth.

 

73 and be safe!

 

Lou WA5LOU

 

On Wed, May 27, 2020 at 3:19 PM Bob740 <bob@...> wrote:

I worked a guy in European Russia 3 times on FT8 with the callsign R6H-212. His real callsign must be different, but I have not been able to find it. He is listed with this callsign on the Russian QRZ.ru website (without an email address) but is not listed on QRZ.com. My problem: The records won't upload to LOTW, which is expected. That would be fine except I get an error each time I upload a batch of  records to LOTW. I would like to retain these records b/c I did work this station, but I want to avoid having upload errors for LOTW. The records did upload to eQSL so no problem there.

Thanks,
Bob
KE0SDV

--

Lou WA5LOU

 


Re: ACL does not play well with FLdigi

Dan Morris
 

I have run fldigi many times using the API with ACL and have had no problems.  I do not use radio control though so I don’t have to worry about COM conflicts.

Dan Morris  KZ3T

I live to live for Him!



On May 27, 2020, at 2:03 PM, Mark Gilligan <mark@...> wrote:

My goal is to have N3FJP Amateur Contact Log V6.6 work with FLdigi. 

 

The problem is that when I try to start the Contact logger while FLdigi is running I get a message that access to port COM 3 is denied.  This is apparently because COM 3 is already used by FLdigi to communicate with my IC-7000.  Device Manager does not show another port than COM3. I do not know how to create other COM ports.  Changing the COM port used by FLdigi opens a can of worms that I do not want to deal with.

 

My station consists of an ICOM IC-7000 connected to a Windows 10 laptop and a Signalink sound card. 

 

If I start the contact logger first the N3FJP Contact logger starts cleanly but when I start FLdigi, FLdigi does not appear to communicate with the radio and as a result the frequency displayed in FLdigi is not the frequency of the radio which suggests this is not a viable option.

 

When I configure the N3FJP software for my rig I am given the option of selecting ICOM or ICOM2 where I am only given the option of selecting COM3 for the port.  Thus I cannot avoid the conflict.

 

Both the N3FPJ Contact Log and FLdigi suggest that the programs can communicate using network addresses and port numbers but I have not been able to make this work.

 

I have checked the option to enable the TCP API port as 1100 which is the same value selected in FLdigi.

 

FLdigi Configuration information.

 

This information about FLdigi is provided in case the resolution impacts FLdigi.

 

I am using Hamlib in FLdigi to communicate with the ICOM IC-7000.  Does the method of rig control in FLdigi impact the problem.

 

In FLdigi the configuration menu for theN3FJP logger allows me to specify a network address of 127.0.0.1 and a Port number of 1100, which I understand to be the default.  My understanding is that with the network address and port number being specified the two programs should be able to communicate without needing COM3.

 

In addition I have listed Contact Log as one of the programs to be started when FLdigi is started.  This does not happen and I get no error message.  I am assuming that this is related to the conflict with COM3.



Mark  KD6MZC


Re: ACL does not play well with FLdigi

Richard Rohrer
 

Mark,

Go to the Configure tab in Fldigi and select the log option.  Select N3FJP logs and enable the data stream and that should take care of it.  Turn off the com port in ACL.  You can also set Fldigi to automatically start ACL from the autostart tab.  It does not matter what kind of rig control being used. 

If you need more help contract me directly and callsign at arrl.net. 

73
Dick - KC3EF


Re: ACL does not play well with FLdigi

Kevin Gray <notsome1else@...>
 

Mark,

Only one program can use a COM port at the same time.

If you have ACLog setup and connected to your radio correctly simply start it first.

In FLDigi “Don’t” select a rig control option. (set to none)

 

Instead, find the “logging” tab and “N3FJP Logs”. Check the box that says connect.

 

I also have the box checked for “Enable Data Stream”

 

 

 

This all seems to work flawlessly for me.

GUD Luck.

 

73 de Kevin N9VPV

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Mark Gilligan
Sent: Wednesday, May 27, 2020 1:03 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] ACL does not play well with FLdigi

 

My goal is to have N3FJP Amateur Contact Log V6.6 work with FLdigi. 

 

The problem is that when I try to start the Contact logger while FLdigi is running I get a message that access to port COM 3 is denied.  This is apparently because COM 3 is already used by FLdigi to communicate with my IC-7000.  Device Manager does not show another port than COM3. I do not know how to create other COM ports.  Changing the COM port used by FLdigi opens a can of worms that I do not want to deal with.

 

My station consists of an ICOM IC-7000 connected to a Windows 10 laptop and a Signalink sound card. 

 

If I start the contact logger first the N3FJP Contact logger starts cleanly but when I start FLdigi, FLdigi does not appear to communicate with the radio and as a result the frequency displayed in FLdigi is not the frequency of the radio which suggests this is not a viable option.

 

When I configure the N3FJP software for my rig I am given the option of selecting ICOM or ICOM2 where I am only given the option of selecting COM3 for the port.  Thus I cannot avoid the conflict.

 

Both the N3FPJ Contact Log and FLdigi suggest that the programs can communicate using network addresses and port numbers but I have not been able to make this work.

 

I have checked the option to enable the TCP API port as 1100 which is the same value selected in FLdigi.

 

FLdigi Configuration information.

 

This information about FLdigi is provided in case the resolution impacts FLdigi.

 

I am using Hamlib in FLdigi to communicate with the ICOM IC-7000.  Does the method of rig control in FLdigi impact the problem.

 

In FLdigi the configuration menu for theN3FJP logger allows me to specify a network address of 127.0.0.1 and a Port number of 1100, which I understand to be the default.  My understanding is that with the network address and port number being specified the two programs should be able to communicate without needing COM3.

 

In addition I have listed Contact Log as one of the programs to be started when FLdigi is started.  This does not happen and I get no error message.  I am assuming that this is related to the conflict with COM3.



Mark  KD6MZC