Date   

Re: CW Keying for IC-7300 using USB

K8TS
 

Guys;

I have the same problem.

COM 5 and COM 10 only though.

One runs rig control, and the other dx spotting.

I can set up cw transmit, it will display, but will not key rig.

COM10 Only shows if the radio is on.

I do not use WinKeyer.  (I do not understand it, consider me uneducated if you will, is it a separate piece of hardware?)

Dale K8TS

 

Sent from Mail for Windows 10

 

From: AI3KS
Sent: Monday, November 4, 2019 10:11 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] CW Keying for IC-7300 using USB

 

Ken,

To my knowledge, you cannot share the USB connection with rig control and keying. I use the C-IV port for rig control and the USB port for keying for RTTY. It works the same for CW, but I find the Winkeyer a better option. If your USB to serial adapter is connected to the C-IV port, try that for rig control. If not, you will need to add that cable.

Steve, AI3KS

On 19/11/04 21:49, Ken Gunther wrote:

    I'm unsuccessfully trying to use N3FJP software (November SS) to do my CW keying via a USB cable. I am trying to use a USB cable to control frequency/mode as well as key the radio so that I can use the function keys to send predefined messages.

    Looking at device manager I have the following COM ports:
     COM3 - USB Serial port
     COM4 - Silicon Labs CP210x USB to UART
     COM5 - Prolific USB to serial

    N3FJP software can successfully read/set frequency and mode on COM4

    In the rig my settings in Menu->Set->Connections->USB Send/Keying
             USB Keying (CW) is set to DTR

    In the N3FJP software in Settings->Transmit->CW I have tried both COM3 and COM5 and the transmit to DTR but I cannot get N3FJP to key the radio.


                                        Thank you,
                                        Ken WB2KWC





 

 


Re: CW Keying for IC-7300 using USB

Ed W2LCQ <w2lcq@...>
 

I have an ICOM 756 Pro III rig. Rig control is on COM3 via a West Mountain Rigtalk USB CI-V cable and rig keying on COM4 through a Winkeyer USB and USB printer cable. This allows me to send N3FJP ACL CW via the function keys. 

73, Ed Jones W2LCQ

            —- Frankford Radio Club —-
CWops 701 - SKCC 5474C - FISTS 12294

"
            






On Nov 4, 2019, at 10:11 PM, AI3KS <AI3KS.01@...> wrote:

 Ken,

To my knowledge, you cannot share the USB connection with rig control and keying. I use the C-IV port for rig control and the USB port for keying for RTTY. It works the same for CW, but I find the Winkeyer a better option. If your USB to serial adapter is connected to the C-IV port, try that for rig control. If not, you will need to add that cable.

Steve, AI3KS

On 19/11/04 21:49, Ken Gunther wrote:
    I'm unsuccessfully trying to use N3FJP software (November SS) to do my CW keying via a USB cable. I am trying to use a USB cable to control frequency/mode as well as key the radio so that I can use the function keys to send predefined messages.

    Looking at device manager I have the following COM ports:
     COM3 - USB Serial port
     COM4 - Silicon Labs CP210x USB to UART
     COM5 - Prolific USB to serial

    N3FJP software can successfully read/set frequency and mode on COM4

    In the rig my settings in Menu->Set->Connections->USB Send/Keying
             USB Keying (CW) is set to DTR

    In the N3FJP software in Settings->Transmit->CW I have tried both COM3 and COM5 and the transmit to DTR but I cannot get N3FJP to key the radio.


                                        Thank you,
                                        Ken WB2KWC








Re: CW Keying for IC-7300 using USB

AI3KS
 

Ken,

To my knowledge, you cannot share the USB connection with rig control and keying. I use the C-IV port for rig control and the USB port for keying for RTTY. It works the same for CW, but I find the Winkeyer a better option. If your USB to serial adapter is connected to the C-IV port, try that for rig control. If not, you will need to add that cable.

Steve, AI3KS

On 19/11/04 21:49, Ken Gunther wrote:
    I'm unsuccessfully trying to use N3FJP software (November SS) to do my CW keying via a USB cable. I am trying to use a USB cable to control frequency/mode as well as key the radio so that I can use the function keys to send predefined messages.

    Looking at device manager I have the following COM ports:
     COM3 - USB Serial port
     COM4 - Silicon Labs CP210x USB to UART
     COM5 - Prolific USB to serial

    N3FJP software can successfully read/set frequency and mode on COM4

    In the rig my settings in Menu->Set->Connections->USB Send/Keying
             USB Keying (CW) is set to DTR

    In the N3FJP software in Settings->Transmit->CW I have tried both COM3 and COM5 and the transmit to DTR but I cannot get N3FJP to key the radio.


                                        Thank you,
                                        Ken WB2KWC








CW Keying for IC-7300 using USB

Ken Gunther
 

I'm unsuccessfully trying to use N3FJP software (November SS) to do my CW keying via a USB cable. I am trying to use a USB cable to control frequency/mode as well as key the radio so that I can use the function keys to send predefined messages.

    Looking at device manager I have the following COM ports:
     COM3 - USB Serial port
     COM4 - Silicon Labs CP210x USB to UART
     COM5 - Prolific USB to serial

    N3FJP software can successfully read/set frequency and mode on COM4

    In the rig my settings in Menu->Set->Connections->USB Send/Keying
             USB Keying (CW) is set to DTR

    In the N3FJP software in Settings->Transmit->CW I have tried both COM3 and COM5 and the transmit to DTR but I cannot get N3FJP to key the radio.


                                        Thank you,
                                        Ken WB2KWC


Re: Issue That is Probably My Fault

AE0JR
 

Under Settings you probably have  ”Carry Comments Data Forward”  checked.  Try unchecking it and see if that improves the problem.

 

From: N3FJPSoftwareUsers@groups.io [mailto:N3FJPSoftwareUsers@groups.io] On Behalf Of Jeff Grantham
Sent: Monday, November 04, 2019 11:18 AM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Issue That is Probably My Fault

 

I am experiencing something on a random basis that I can not figure out.  When I enter a new call, sometimes I get double data in the comments that has their address.  Has anyone else experienced that and if so, what was the fix?

 

 

Thanks,

Jeff

KB5WCK

DMR ID: 3158487

 


AC Log 6.5 Logging Differences, Two Installations

Kenneth W. Campbell
 

Good afternoon,

I've a couple of interesting problems here: I'm running two instances of AC Log 6.5, one on my main PC, a second on my laptop for portable use. Both are ver. 6.5, and TQSL on both is ver. 2.4.7. Here's the problems:
1. Both show differences in LoTW logging confirmation. One will show certain contacts as confirmed by LoTW, and the other shows it as still unconfirmed.
2. The portable log insists on showing FT4 contacts as MFSK. Main log is OK.

Any ideas as to what can bring abut consistency here? All suggestions are heartily appreciated! :-)
--
All the best,
Ken N6PCD


Re: Issue That is Probably My Fault

Dan Morris
 

Jeff - Check a little closer. I have had those and if I look closely enough the addresses are actually different.  One that I previously had for that callsign and then one from QRZ. I usually delete the one previously and go with QRZ which normally is the updated one.

Dan Morris  KZ3T

I live to live for Him!



On Nov 4, 2019, at 12:18 PM, Jeff Grantham <jeff@...> wrote:

I am experiencing something on a random basis that I can not figure out.  When I enter a new call, sometimes I get double data in the comments that has their address.  Has anyone else experienced that and if so, what was the fix?
 
 
Thanks,
Jeff
KB5WCK
DMR ID: 3158487
 


Re: Issue That is Probably My Fault

KB5WCK
 

Thanks.  That’s probably what it is.

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Scott Davis via Groups.Io
Sent: 04-Nov-19 13:02
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Issue That is Probably My Fault

 

Hi Jeff,

 

Thanks for your e-mail.  When AC Log looks up the address, it checks the string against what is currently in your Comments field and if it finds a match, it will not add it again.  If there is one character different though, it will be added.

 

If you prefer not to have the address added to the Comments field, click Calbook > Place Retrieved Address in Comments Field so that it is unchecked.

 

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: Jeff Grantham <jeff@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Mon, Nov 4, 2019 12:18 pm
Subject: [N3FJPSoftwareUsers] Issue That is Probably My Fault

I am experiencing something on a random basis that I can not figure out.  When I enter a new call, sometimes I get double data in the comments that has their address.  Has anyone else experienced that and if so, what was the fix?

 

 

Thanks,

Jeff

KB5WCK

DMR ID: 3158487

 


Re: Issue That is Probably My Fault

Scott Davis
 

Hi Jeff,

Thanks for your e-mail.  When AC Log looks up the address, it checks the string against what is currently in your Comments field and if it finds a match, it will not add it again.  If there is one character different though, it will be added.

If you prefer not to have the address added to the Comments field, click Calbook > Place Retrieved Address in Comments Field so that it is unchecked.

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: Jeff Grantham <jeff@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Mon, Nov 4, 2019 12:18 pm
Subject: [N3FJPSoftwareUsers] Issue That is Probably My Fault

I am experiencing something on a random basis that I can not figure out.  When I enter a new call, sometimes I get double data in the comments that has their address.  Has anyone else experienced that and if so, what was the fix?
 
 
Thanks,
Jeff
KB5WCK
DMR ID: 3158487
 


Issue That is Probably My Fault

KB5WCK
 

I am experiencing something on a random basis that I can not figure out.  When I enter a new call, sometimes I get double data in the comments that has their address.  Has anyone else experienced that and if so, what was the fix?

 

 

Thanks,

Jeff

KB5WCK

DMR ID: 3158487

 


Re: New user here with problems

Larry Banks
 

Hi Dave,
 
Dan is correct, you need to change the dates on those Qs that have the wrong date and resubmit.  Don’t worry about the Qs you have already submitted as they will never see a confirmation.  They will remain in the LoTW database as what are called zombies.
 
Just always log everything in UTC time/date from now on.

73 -- Larry -- W1DYJ

 

From: Dan Morris
Sent: Monday, November 04, 2019 8:50
Subject: Re: [N3FJPSoftwareUsers] New user here with problems
 
Well, unless someone else has a better idea right off hand I would say if you haven’t entered too many just to go back and correct only those where the actual date may be wrong due to the UTC time.  I would think that most of them if the UTC time is not far off or in middle of the day that the date would be just fine.  I guess the main problem would be somewhere around the end of UTC data and you may have put the local instead of UTC date.
 
Just change those and resubmit to LoTW and see what happens.

Dan Morris  KZ3T

I live to live for Him!



On Nov 4, 2019, at 8:41 AM, Dave via Groups.Io <kc3am@...> wrote:
 

Dan,

Another thing I just thought about that has me concerned.

My paper logging has always been local date / time not UTC date / time.

I have been inputting the local date but converting the local time to UTC time since that is what the program is asking for. This brain fart just occurred this morning. As I started to look at the log I have found several entries that have one entry in Green and one in Blue. The Green has the local date and the Blue has the UTC date. I am very puzzled here and not sure how to fix this mess I have created.

Any thoughts anyone?

Dave KC3AM

On 11/02/2019 07:48, Dan Morris wrote:
Dave - What I believe is the different colors represent the following:
Black - That record has not been uploaded to LoTW or eQSL, etc
Blue - That record has been uploaded to LoTW or eQSL, etc
Green - That record has received a QSL from LoTW or eQSL, etc
 
Possibly those records with errors are not  being uploaded because of the “PH” in the mode field. The mode should be “SSB"

Dan Morris  KZ3T

I live to live for Him!



On Nov 1, 2019, at 11:57 PM, Dave via Groups.Io <kc3am@...> wrote:
 
Hello all, I am just new at using this software for logging and am using version 6.5.
I am having a couple of problems.
I am entering data from my paper log book and have 181 entries so far, some are blue, some are green, some are black. I see no description for the what the black line color indicates. My problem is that only 117 records are being uploaded to LOTW when I ask for the entire log to be uploaded. I have 'removed duplicates' and still have 181 entries. Why are only 117 entries being uploaded?

Also when uploading I get an error message saying invalid mode(PH) on line 707. This error appears with different call sign entries each time I try to upload the log.

Any idea what is happening?

Dave KC3AM
 
--
73, Dave KC3AM
 


Re: Minor Bearing issue

Poul K
 

Settings > Appearance > Display Bearing as Compass Point is unchecked.

Thank you Scott - that did it!
73


Re: New user here with problems

Dan Morris
 

Well, unless someone else has a better idea right off hand I would say if you haven’t entered too many just to go back and correct only those where the actual date may be wrong due to the UTC time.  I would think that most of them if the UTC time is not far off or in middle of the day that the date would be just fine.  I guess the main problem would be somewhere around the end of UTC data and you may have put the local instead of UTC date.

Just change those and resubmit to LoTW and see what happens.

Dan Morris  KZ3T

I live to live for Him!



On Nov 4, 2019, at 8:41 AM, Dave via Groups.Io <kc3am@...> wrote:

Dan,

Another thing I just thought about that has me concerned.

My paper logging has always been local date / time not UTC date / time.

I have been inputting the local date but converting the local time to UTC time since that is what the program is asking for. This brain fart just occurred this morning. As I started to look at the log I have found several entries that have one entry in Green and one in Blue. The Green has the local date and the Blue has the UTC date. I am very puzzled here and not sure how to fix this mess I have created.

Any thoughts anyone?

Dave KC3AM

On 11/02/2019 07:48, Dan Morris wrote:
Dave - What I believe is the different colors represent the following:
Black - That record has not been uploaded to LoTW or eQSL, etc
Blue - That record has been uploaded to LoTW or eQSL, etc
Green - That record has received a QSL from LoTW or eQSL, etc

Possibly those records with errors are not  being uploaded because of the “PH” in the mode field. The mode should be “SSB"

Dan Morris  KZ3T

I live to live for Him!



On Nov 1, 2019, at 11:57 PM, Dave via Groups.Io <kc3am@...> wrote:

Hello all, I am just new at using this software for logging and am using version 6.5.
I am having a couple of problems.
I am entering data from my paper log book and have 181 entries so far, some are blue, some are green, some are black. I see no description for the what the black line color indicates. My problem is that only 117 records are being uploaded to LOTW when I ask for the entire log to be uploaded. I have 'removed duplicates' and still have 181 entries. Why are only 117 entries being uploaded?

Also when uploading I get an error message saying invalid mode(PH) on line 707. This error appears with different call sign entries each time I try to upload the log. 

Any idea what is happening?

Dave KC3AM

--
73, Dave KC3AM


Re: New user here with problems

Dave
 

Dan,

Another thing I just thought about that has me concerned.

My paper logging has always been local date / time not UTC date / time.

I have been inputting the local date but converting the local time to UTC time since that is what the program is asking for. This brain fart just occurred this morning. As I started to look at the log I have found several entries that have one entry in Green and one in Blue. The Green has the local date and the Blue has the UTC date. I am very puzzled here and not sure how to fix this mess I have created.

Any thoughts anyone?

Dave KC3AM

On 11/02/2019 07:48, Dan Morris wrote:
Dave - What I believe is the different colors represent the following:
Black - That record has not been uploaded to LoTW or eQSL, etc
Blue - That record has been uploaded to LoTW or eQSL, etc
Green - That record has received a QSL from LoTW or eQSL, etc

Possibly those records with errors are not  being uploaded because of the “PH” in the mode field. The mode should be “SSB"

Dan Morris  KZ3T

I live to live for Him!



On Nov 1, 2019, at 11:57 PM, Dave via Groups.Io <kc3am@...> wrote:

Hello all, I am just new at using this software for logging and am using version 6.5.
I am having a couple of problems.
I am entering data from my paper log book and have 181 entries so far, some are blue, some are green, some are black. I see no description for the what the black line color indicates. My problem is that only 117 records are being uploaded to LOTW when I ask for the entire log to be uploaded. I have 'removed duplicates' and still have 181 entries. Why are only 117 entries being uploaded?

Also when uploading I get an error message saying invalid mode(PH) on line 707. This error appears with different call sign entries each time I try to upload the log. 

Any idea what is happening?

Dave KC3AM

--
73, Dave KC3AM


Re: Minor Bearing issue

Scott Davis
 

Hi Poul,

Thanks for your e-mail.  I'm not sure why your long path value isn't correct.  It is working properly here.  What are the values that you have entered for Lat and Long on setup?

To return from compass point, click Settings > Appearance > Display Bearing as Compass Point so that it is unchecked.

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: Poul K <sa7cnd@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Sun, Nov 3, 2019 10:38 am
Subject: [N3FJPSoftwareUsers] Minor Bearing issue

Clicking "Bearing:" down left in AClog 6.5, displays "Long path:", always value 180 here.
Clicking there again returns "Bearing:" but now always N. And so on, 180, N, ...
Is this a bug?


Re: Minor Bearing issue

Mike Olbrisch
 

Sorry sir, I am out of ideas.

 

Mike – KD5KC.

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Poul K
Sent: Sunday, November 3, 2019 13:15 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Minor Bearing issue

 

Hi Mike
I checked Setup, was ok. So issue remains...
73


Re: New user here with problems

Dave
 

Yes Dan,

All the Black lines are gone and I have about 70% Green lines and the rest are Blue.

I will do a better job when I continue to enter data from my paper log book which dates back to 1992.

Sadly 90% of my contacts are from a WAS net. I have noticed that in 2015 I only have one contact logged.

I am trying to devote more time to HF but it is a chore to get away from the work bench and the projects that I have saved for retirement time.

Dave KC3AM

On 11/02/2019 22:25, Dan Morris wrote:
Dave - glad you got them fixed. Now try doing a download from LoTW and see what happens. Hopefully a bunch of those will turn color.

Dan Morris

On Nov 2, 2019, at 9:29 PM, Dave via Groups.Io <kc3am@...> wrote:



Dan,

I did find several problems with my entries, PH vs SSB to start with. Band?? / freq errors... band = 80 & freq = 7.268.

I did a "all contacts not uploaded' and corrected the errors that appeared there. When that was done I did an 'entire log' upload which went ok without an error.

This was 3 hours ago and LOTW does not show the 181 contacts that were uploaded. Maybe it will take a longer time due to the duplicate records.

There are still many black lines in the AC log at this time but that may change the next time I do an upload.

I will see what happens tomorrow.

Thanks much,

Dave KC3AM

On 11/02/2019 07:48, Dan Morris wrote:
Dave - What I believe is the different colors represent the following:
Black - That record has not been uploaded to LoTW or eQSL, etc
Blue - That record has been uploaded to LoTW or eQSL, etc
Green - That record has received a QSL from LoTW or eQSL, etc

Possibly those records with errors are not ??being uploaded because of the ???PH??? in the mode field. The mode should be ???SSB"

Dan Morris ??KZ3T

I live to live for Him!



On Nov 1, 2019, at 11:57 PM, Dave via Groups.Io <kc3am@...> wrote:

Hello all, I am just new at using this software for logging and am using version 6.5.
I am having a couple of problems.
I am entering data from my paper log book and have 181 entries so far, some are blue, some are green, some are black. I see no description for the what the black line color indicates. My problem is that only 117 records are being uploaded to LOTW when I ask for the entire log to be uploaded. I have 'removed duplicates' and still have 181 entries. Why are only 117 entries being uploaded?

Also when uploading I get an error message saying invalid mode(PH) on line 707. This error appears with different call sign entries each time I try to upload the log.??

Any idea what is happening?

Dave KC3AM

--
73, Dave KC3AM
--
73, Dave KC3AM


Re: Minor Bearing issue

Poul K
 

Hi Mike
I checked Setup, was ok. So issue remains...
73


Re: Minor Bearing issue

Mike Olbrisch
 

Make certain you have your own Lat-Lon entered correctly.

 

Western Hemisphere is NEGATIVE  (- 106.12345°)

 

Northern Hemisphere is POSITIVE (31.12345°)

 

You get there by: SETTINGS à  SETUP  on the upper menu bar.

 

BTW – OPERATOR is your call sign, not your name.  That can cause issues with some reports.

 

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...

 

Big Bend JEEP Rear

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Poul K
Sent: Sunday, November 3, 2019 8:39 AM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Minor Bearing issue

 

Clicking "Bearing:" down left in AClog 6.5, displays "Long path:", always value 180 here.
Clicking there again returns "Bearing:" but now always N. And so on, 180, N, ...
Is this a bug?


Minor Bearing issue

Poul K
 

Clicking "Bearing:" down left in AClog 6.5, displays "Long path:", always value 180 here.
Clicking there again returns "Bearing:" but now always N. And so on, 180, N, ...
Is this a bug?