Date   

Re: Roll back to an earlier version of Logger32

Damian M0BKV
 

The rollback after the attempt to upload version 410 and deletion of Logger32.exe occurring unfortunately contains V410 so you need to obtain an earlier version (V409) elsewhere.


Re: Logger32 will not read frequency

Jim Hargrave
 

Ken,

The FT-920 has a built in Level converter for Radio  control. All you need is a true RS-232 serial cable.

If your computer does not have   serial ports, I highly recommend a USB to RS232 serial adapter with FTDI chip set.

The problem with Prolific is a company is making fake knock offs.

Be sure what you buy states W10 compatible.

 

I have a couple Prolific adapters which work on XP, but not any later. I purchased a FTDI adapter when I upgraded to W8. (now W10).

I have since installed 2 serial boards in the computer.

 

My FT920   has been in use for Beta testing since the development of Logger32 (2003)

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: Monday, March 30, 2020 3:39 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Julian

 

I use a FT920 for RTTY using MMTTY in L32 and that has never been a problem. I use an Edgeport USB Convertor which gives me multiple serial ports and the Edgeport connects to the W10 PC by a USB cable. This way I can use the FT2000 and the FT920 on the same PC.

 

So do I look for a USB to serial cable which specifically states compatible with W10?

 

I don’t think the cable I bought states it is compatible with W10 although I can’t seem to find the instructions.

 

Thanks again Julian.

 

Ken

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:26
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken,

 

 It was just an eBay purchase for about £4:99 but at the time there were very few that said windows-10 compatible, it’s a bit different now, I was connecting up the FT-920 and had a similar experience as you but came to the lead when the FT-817 did the same. Device Manager didn’t show any errors but the cat on the radio display didn’t show so I knew it was the connection. I have a few spare so if you get desperate you can have one of my spare ones.

 

    Julian

 


On 30 Mar 2020, at 09:10, "kenfilmer@..." <kenfilmer@...> wrote:

Morning Julian

 

That sounds familiar!

 

Can you please tell me where you bought the W10 compatible adaptor?

 

I have a desktop PC with my main radio with W10. I loaded L32 with no problem and apart from one time when I had a problem synchronising with LoTW its been great for around 15 years and a truly wonderful and versatile logging programme.

 

Its this **@@””** laptop that is the problem that clearly does not want to connect to my radio so if you can point me where to buy a W10 compatible cable I will be eternally grateful

 

73

 

Ken

G3XPO

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:00
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.

Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 

 


Re: Logger32 will not read frequency

Stephen Tompsett
 

Especially if it came with a driver disk or instructions to download drivers it's probably a fake or sold as 'FTDI compatible'!

To ensure that I get real devices I usually purchase FTDI based cables and devices from :

https://ftdi-uk.shop/

or

https://shop.technofix.uk/

I'm happy to pay a bit more for real FTDI devices because they are reliable, perform well and are supported on all the operating systems I use.


On 30/03/2020 10:52, G4RRM Pete wrote:

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

-- 
Stephen Tompsett (G8LYB)
Tel: 01788 578940
Mob: 07956 855816


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Thanks John

 

You show cables specifically for the radio which is good.

 

I shall have a close look through these and get one which seems most likely to do the job.

 

That’s great, thanks John.

 

73

 

Ken

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 30 March 2020 11:42
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

 

on ebay too;

 

 

One last thing you could try is to uninstall the driver for the cable you have and try downloading & installing a driver from here;

 

 

GL & 73

 

John - G7SSE

 

------ Original Message ------

Sent: 30/03/2020 11:31:34

Subject: Re: [hamlogger] Logger32 will not read frequency

 

Pete thanks for that.

 

If that one worked for you I’m happy to get a cable that has been tried and tested!

 

The help from everybody (thank you all) seems to indicate it is in fact a cable problem and that must be the way to go.

 

73 Stay safe everybody!

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: G4RRM Pete
Sent: 30 March 2020 10:52
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 


--
73, John - G7SSE

 


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Ah. The cable you mentioned didn’t say it was compatible with W10, but the reviews seemed to indicate it was.

 

Thanks Pete!

 

73

 

Ken

 

Sent from Mail for Windows 10

 

From: G4RRM Pete
Sent: 30 March 2020 11:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

One thing just dawned on me. I wasn’t working with win 10!! Our systems were win7.

 

 

 

73

Pete

G4RRM



On 30 Mar 2020, at 11:31, "kenfilmer@..." <kenfilmer@...> wrote:



Pete thanks for that.

 

If that one worked for you I’m happy to get a cable that has been tried and tested!

 

The help from everybody (thank you all) seems to indicate it is in fact a cable problem and that must be the way to go.

 

73 Stay safe everybody!

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: G4RRM Pete
Sent: 30 March 2020 10:52
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 

 


Re: Logger32 will not read frequency

G4RRM Pete
 

One thing just dawned on me. I wasn’t working with win 10!! Our systems were win7.



73
Pete
G4RRM

On 30 Mar 2020, at 11:31, "kenfilmer@..." <kenfilmer@...> wrote:



Pete thanks for that.

 

If that one worked for you I’m happy to get a cable that has been tried and tested!

 

The help from everybody (thank you all) seems to indicate it is in fact a cable problem and that must be the way to go.

 

73 Stay safe everybody!

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: G4RRM Pete
Sent: 30 March 2020 10:52
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 


Re: Logger32 will not read frequency

John Munton - G7SSE
 

------ Original Message ------
Sent: 30/03/2020 11:31:34
Subject: Re: [hamlogger] Logger32 will not read frequency

Pete thanks for that.

 

If that one worked for you I’m happy to get a cable that has been tried and tested!

 

The help from everybody (thank you all) seems to indicate it is in fact a cable problem and that must be the way to go.

 

73 Stay safe everybody!

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: G4RRM Pete
Sent: 30 March 2020 10:52
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 


--
73, John - G7SSE


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Pete thanks for that.

 

If that one worked for you I’m happy to get a cable that has been tried and tested!

 

The help from everybody (thank you all) seems to indicate it is in fact a cable problem and that must be the way to go.

 

73 Stay safe everybody!

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: G4RRM Pete
Sent: 30 March 2020 10:52
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

I shall look for  W10 compatible cable Julian, thanks.

 

I did find the instructions for the cable I have and it says suitable for various windows programmes but I does not mention W10.

 

Thanks again for your help!

 

73

 

Ken

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 10:01
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Basically Ken the answer is yes, I had the Belkin multi port usb for win7 but that wouldn’t work with 10 so had to buy a new one, all it said was windows compatible so there was a bit of head scratching but bought another one which was win10 compatible and it came up straight away. I now have the 920 via db9 on the main pc and the usb compatible on the laptop. Like you L32 & mmtty for rtty and N1MM for contest. All works well.

 

 


On 30 Mar 2020, at 09:39, "kenfilmer@..." <kenfilmer@...> wrote:

Hi Julian

 

I use a FT920 for RTTY using MMTTY in L32 and that has never been a problem. I use an Edgeport USB Convertor which gives me multiple serial ports and the Edgeport connects to the W10 PC by a USB cable. This way I can use the FT2000 and the FT920 on the same PC.

 

So do I look for a USB to serial cable which specifically states compatible with W10?

 

I don’t think the cable I bought states it is compatible with W10 although I can’t seem to find the instructions.

 

Thanks again Julian.

 

Ken

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:26
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken,

 

 It was just an eBay purchase for about £4:99 but at the time there were very few that said windows-10 compatible, it’s a bit different now, I was connecting up the FT-920 and had a similar experience as you but came to the lead when the FT-817 did the same. Device Manager didn’t show any errors but the cat on the radio display didn’t show so I knew it was the connection. I have a few spare so if you get desperate you can have one of my spare ones.

 

    Julian

 


On 30 Mar 2020, at 09:10, "kenfilmer@..." <kenfilmer@...> wrote:

Morning Julian

 

That sounds familiar!

 

Can you please tell me where you bought the W10 compatible adaptor?

 

I have a desktop PC with my main radio with W10. I loaded L32 with no problem and apart from one time when I had a problem synchronising with LoTW its been great for around 15 years and a truly wonderful and versatile logging programme.

 

Its this **@@””** laptop that is the problem that clearly does not want to connect to my radio so if you can point me where to buy a W10 compatible cable I will be eternally grateful

 

73

 

Ken

G3XPO

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:00
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.

Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 

 

 


Re: Logger32 will not read frequency

G4RRM Pete
 

Hi Ken

 

I’m not PC savy enough to know why your FTDI says Prolific, or if that’s just a legacy setting from something else.

 

For info this is what I bought, afraid its gone up since 2015 when I purchased, but it worked ok ( did have to buy a Male female changer too)

 

https://www.amazon.co.uk/gp/product/B004ZMYTYC/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

GL

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 30 March 2020 09:03
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 


Re: Logger32 will not read frequency

Julian GW4JBQ
 

Basically Ken the answer is yes, I had the Belkin multi port usb for win7 but that wouldn’t work with 10 so had to buy a new one, all it said was windows compatible so there was a bit of head scratching but bought another one which was win10 compatible and it came up straight away. I now have the 920 via db9 on the main pc and the usb compatible on the laptop. Like you L32 & mmtty for rtty and N1MM for contest. All works well.




On 30 Mar 2020, at 09:39, "kenfilmer@..." <kenfilmer@...> wrote:

Hi Julian

 

I use a FT920 for RTTY using MMTTY in L32 and that has never been a problem. I use an Edgeport USB Convertor which gives me multiple serial ports and the Edgeport connects to the W10 PC by a USB cable. This way I can use the FT2000 and the FT920 on the same PC.

 

So do I look for a USB to serial cable which specifically states compatible with W10?

 

I don’t think the cable I bought states it is compatible with W10 although I can’t seem to find the instructions.

 

Thanks again Julian.

 

Ken

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:26
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken,

 

 It was just an eBay purchase for about £4:99 but at the time there were very few that said windows-10 compatible, it’s a bit different now, I was connecting up the FT-920 and had a similar experience as you but came to the lead when the FT-817 did the same. Device Manager didn’t show any errors but the cat on the radio display didn’t show so I knew it was the connection. I have a few spare so if you get desperate you can have one of my spare ones.

 

    Julian

 


On 30 Mar 2020, at 09:10, "kenfilmer@..." <kenfilmer@...> wrote:

Morning Julian

 

That sounds familiar!

 

Can you please tell me where you bought the W10 compatible adaptor?

 

I have a desktop PC with my main radio with W10. I loaded L32 with no problem and apart from one time when I had a problem synchronising with LoTW its been great for around 15 years and a truly wonderful and versatile logging programme.

 

Its this **@@””** laptop that is the problem that clearly does not want to connect to my radio so if you can point me where to buy a W10 compatible cable I will be eternally grateful

 

73

 

Ken

G3XPO

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:00
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.

Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 

 


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Hi Jacek

 

That’s very interesting, thank you.

 

I had a look at aliexpress.com – it looks like they sell everything!

 

Thank you, I will try and find a suitable cable, which is now where it is apparent my problem is!

 

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: SP6ABO
Sent: 30 March 2020 09:46
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken,
for long time I've been using CI-V interface cable to connect my Icom trx. First trx was 736, current is 7410. Both work flawless. I tried also to connect ic-7800 but failed. The logics assy is suspected to be out of order in this trx.
The interface cable is around $3.50 on aliexpress.com. For safety reason I added also USB opto isolator module.

73 Jacek
SP6ABO

 


Re: Logger32 will not read frequency

SP6ABO
 

Hi Ken,
for long time I've been using CI-V interface cable to connect my Icom trx. First trx was 736, current is 7410. Both work flawless. I tried also to connect ic-7800 but failed. The logics assy is suspected to be out of order in this trx.
The interface cable is around $3.50 on aliexpress.com. For safety reason I added also USB opto isolator module.

73 Jacek
SP6ABO


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Hi Julian

 

I use a FT920 for RTTY using MMTTY in L32 and that has never been a problem. I use an Edgeport USB Convertor which gives me multiple serial ports and the Edgeport connects to the W10 PC by a USB cable. This way I can use the FT2000 and the FT920 on the same PC.

 

So do I look for a USB to serial cable which specifically states compatible with W10?

 

I don’t think the cable I bought states it is compatible with W10 although I can’t seem to find the instructions.

 

Thanks again Julian.

 

Ken

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:26
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken,

 

 It was just an eBay purchase for about £4:99 but at the time there were very few that said windows-10 compatible, it’s a bit different now, I was connecting up the FT-920 and had a similar experience as you but came to the lead when the FT-817 did the same. Device Manager didn’t show any errors but the cat on the radio display didn’t show so I knew it was the connection. I have a few spare so if you get desperate you can have one of my spare ones.

 

    Julian

 


On 30 Mar 2020, at 09:10, "kenfilmer@..." <kenfilmer@...> wrote:

Morning Julian

 

That sounds familiar!

 

Can you please tell me where you bought the W10 compatible adaptor?

 

I have a desktop PC with my main radio with W10. I loaded L32 with no problem and apart from one time when I had a problem synchronising with LoTW its been great for around 15 years and a truly wonderful and versatile logging programme.

 

Its this **@@””** laptop that is the problem that clearly does not want to connect to my radio so if you can point me where to buy a W10 compatible cable I will be eternally grateful

 

73

 

Ken

G3XPO

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:00
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.

Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 

 


Re: Logger32 will not read frequency

Julian GW4JBQ
 

Hi Ken,

 It was just an eBay purchase for about £4:99 but at the time there were very few that said windows-10 compatible, it’s a bit different now, I was connecting up the FT-920 and had a similar experience as you but came to the lead when the FT-817 did the same. Device Manager didn’t show any errors but the cat on the radio display didn’t show so I knew it was the connection. I have a few spare so if you get desperate you can have one of my spare ones.

    Julian



On 30 Mar 2020, at 09:10, "kenfilmer@..." <kenfilmer@...> wrote:

Morning Julian

 

That sounds familiar!

 

Can you please tell me where you bought the W10 compatible adaptor?

 

I have a desktop PC with my main radio with W10. I loaded L32 with no problem and apart from one time when I had a problem synchronising with LoTW its been great for around 15 years and a truly wonderful and versatile logging programme.

 

Its this **@@””** laptop that is the problem that clearly does not want to connect to my radio so if you can point me where to buy a W10 compatible cable I will be eternally grateful

 

73

 

Ken

G3XPO

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:00
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.

Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Morning Julian

 

That sounds familiar!

 

Can you please tell me where you bought the W10 compatible adaptor?

 

I have a desktop PC with my main radio with W10. I loaded L32 with no problem and apart from one time when I had a problem synchronising with LoTW its been great for around 15 years and a truly wonderful and versatile logging programme.

 

Its this **@@””** laptop that is the problem that clearly does not want to connect to my radio so if you can point me where to buy a W10 compatible cable I will be eternally grateful

 

73

 

Ken

G3XPO

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Julian GW4JBQ
Sent: 30 March 2020 09:00
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi Ken

 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.

Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

 


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Dave, Pete

 

I was just looking for FTDI chip cables ..... and the cable I bought and which I am using is the attached.

 

It is a FTDI chip cable, which raises the question why does the ports in device manager say Prolific?

 

Does this mean the cable I bought if NOT FTDI? This is it!


https://www.amazon.co.uk/COOSO-Serial-Female-Adapter-Chipset/dp/B075VR429G/ref=sr_1_14?dchild=1&keywords=ftdi+serial+to+usb+cable&qid=1585554956&sr=8-14

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 


Re: LOGGER 32

Julian GW4JBQ
 

Hi Gary,

 Really good to hear you again

      Julian



On 30 Mar 2020, at 01:25, Gary Hinson <Gary@...> wrote:

Not so weird, Darl.

 

Antivirus programs tread a fine line on sensitivity: if too sensitive (with the preamp set to TURBO!), they can sound the alert on totally innocuous programs.  Everything seems scary. 

 

If too lax/laid-back, they can fail to sound the alert on nasty programs.  They are as deaf to trouble as certain Eastern European operators with huge power amplifiers and vestigial ears.

 

We’ve seen a slew of postings here in the past week or so about both McAfee and Windows Defender alerting on (and, it seems, quarantining) Logger32.exe.  Maybe everyone is a bit on edge with COVID-19.

 

I’m virtually certain it is a false alarm.  If you’re worried, check it out by uploading Logger32.exe to VirusTotal.org and make what you will of the results.  It is not uncommon to see a handful of antivirus programs sound the alert on relatively rare executables such as this: “a handful” means “a few” as in “a minority” or “a small minority”, often just obscure antivirus packages but sometimes (as now) one or two of the main players too.  Do ya feel lucky, punk?

 

The preferred solution is to report this a false alarm to the relevant antivirus supplier, and they’ll put their best egg-heads on the case.  They have high isolation labs for testing suspect programs.  Maybe they even have radios and dummy loads.  I don’t think they wear face masks though.  If they agree that this is a false alarm, they will normally code and push out an update to their antivirus signatures as soon as practicable (sometimes within hours, more often within days since we Logger32ites are so rare and ‘special’).

 

Meanwhile*, you may be able to manually configure your antivirus program to ignore (“exclude”) Logger32.exe, perhaps even the whole Logger32 directory.  You may need to restore Logger32.exe from the quarantine area, if it wasn’t deleted.  If it was deleted, you’ll need to download, reinstall and re-update Logger32 from Logger32.net … but if you haven’t updated or reconfigured the antivirus program, it will spring lithely into action once more, quarantining or deleting the latest update once again.

 

You could also replace your antivirus program with a “better” one”.  Good luck figuring out which ones are “better”.  There’s plenty of choice out there.  The big brand commercial suppliers with big marketing budgets generally battle it out at the top of all the comparative rankings (funny, that) but even the obscure providers (including freeware ones) generally do OK.  The main advantage of the commercial products is more timely customer support, in theory, for incidents just like this.  In practice, the suppliers are always working under pressure, especially now I guess with COVID-19.

 

As a last resort, you can turn off your antivirus programs completely and live dangerously, doing the IT equivalent of sharing personal space and bodily fluids with large crowds of people right now.  It’s definitely not to be recommended. 

 

Hinson tip: whatever else you do, make sure you have recent offline backups of anything important, such as your log (preferably a full ADIF export).  That way, if it all goes horribly wrong, you haven’t lost everything, except perhaps a few hours, maybe a few QSOs and some dignity.  Chalk it up to experience.  [And don’t ask me how I know this.]

 

73,

Gary   ZL2iFB

 

* Don’t forget to remove the exclusion once the antivirus program is updated to stop false-alarming.  It is unlikely but possible that a future update to Logger32 or the associated utilities and documentation might be infected with something nasty, in which case you’ll be glad of the alert.

 

 

Logo

Gary Hinson

Gary@...

IsecT Limited

My blog

Information security

ISO/IEC 27001 standards

Security metrics

Security policies

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Darl DEEDS
Sent: 30 March 2020 10:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOGGER 32

 

I woke up this morning and turned on my monitor, computer was already on, and found Logger gone, no shortcut nor in my program directory, although it was still in the hard drive minus the exe. program. Same as you Tom.

 

I haven’t changed anything for weeks except updating to the newest version automatically.

 

I do not use MacAfee. I only have Microsoft Defender installed.

 

It took a while but I finally got it to reinstall and nothing was lost.

 

Very weird that an overnight virus scan would remove it. Defender did show several items quarantined including Logger.exe

 

Darl  NA8W

 

From: Tom Wylie
Sent: Sunday, March 29, 2020 15:49
To: hamlogger@groups.io
Subject: [hamlogger] LOGGER 32

 

After quitting the contest tonight It was my intention to import my contest logs into Logger 32 as normal,  however, I noticed that my shortcut no longer works and says that the EXE file it refers to has been removed.    I went into the Logger 32 folder and sure enough there is no EXE file.

 

I ran a virus check and found that yesterday morning I seemed to have picked up a trojan    Occamy.C   which has latched onto my Logger32 EXE file and it has been quarantined in my computer.   I cant remember when I last updated Logger 32 but feel it was in the past couple of days via an auto update.      Can anybody throw any light on this?  Can I merely dump the .exe file and download a fresh on from the main site.   I have backed up my logs.

 

Tom

GM4FDM

 

 

 

 

 

Sent from Mail for Windows 10

 

 


Re: Logger32 will not read frequency

Julian GW4JBQ
 

Hi Ken
 I found that when I bought my new laptop last year without a serial port I had to buy new windows-10 compatible adapters as none of the others would work even with the prolific software drivers. I had to do the same when windows-7 came out. I have found that L32 is one of the easiest to interface with the correct cable.
Best of luck 👍


On 30 Mar 2020, at 08:47, "kenfilmer@..." <kenfilmer@...> wrote:

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 


Re: Logger32 will not read frequency

kenfilmer@outlook.com
 

Dave, Pete

 

Many thanks for the reply.

 

OK, I shall look for a FTDI serial to USB cable.

 

I have come to the conclusion that there is something fundamentally wrong with my hardware!

 

I have a couple of other serial to USB cables to try, neither worked before, but I’ll see if they are Prolific as well.

 

Thanks chaps, much appreciated.

 

73

 

Ken

G3XPO

 

Sent from Mail for Windows 10

 

From: Dave Colliau
Sent: 29 March 2020 22:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Prolific drivers are touchy and if your not computer/Prolific savvy you can tear your hair out getting them to work. That said once the right driver is loaded they should just keep working.

I use the FTDI cables and win10 finds them and loads the drivers.

I did have one instance where windows did an update on my laptop and I had to find the FTDI driver and load it ?

Stranger things have happened .

73

Dave N8DC

On March 29, 2020 at 4:42 PM G4RRM Pete <pete@...> wrote:

Hi Ken / John

 

Just a thought, I know two people that have had issues with Prolific USB to Serial adaptors ( I was setting them up).

Radios wouldn’t talk to PC, they swapped to FTDI chips and it worked first time.

I think they are known for issues and documented on the net.

 

Of course if it’s a not a new piece of kit and you have used it before just ignore my mail.

 

Hope you get sorted.

 

73

Pete

G4RRM

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of kenfilmer@...
Sent: 29 March 2020 20:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Hi John

 

Thanks for the reply! Apologies for the late reply. Answers follow -

 

On the lower status bar is the word "Radio" in blue text?

Yes it is.


If you hover your mouse over it does it say "com3 open"?

Well, funny thing. Whereas yesterday the only port I had available was port 3, today I got the message INVALID SERIAL PORT COMM 3 on opening port 3 and on radio 1 settings I now have the choice of ports 3 or 4. Port 4 was not shown yesterday. I set port 4 in SET UP RADIO 1, no adverse messages but still no frequency but it does say when I hover the mouse over the radio - RADO 1 COMM 4 OPEN.


Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

There is a green light by COMM 4, all other lights on RASIO 1 row are red. I can see what I assume is the radio polling and replies but I have no idea whether all those mean. They repeat these two lines –

USING #1 POLL 00 00 00 03 10

USING #1 SHORT POLL 00 00 00 01 FA.

 

. There is nothing shown adjacent to frequency or mode.

 

I have checked frequency in SET UP.

 

I have the correct baud, databits etc all set in accordance with the MK5 manual, all as your figures. I’ve tried using different values but as expected, no difference.

 

Yes, the cable driver has been installed correctly as far as I know.

 

Going to DEVICE MANAGER under ports it says PROLIFIC USB TO SERIAL COMM PORT 4. Which seems to show the cable is there and working.

 

I will try DTR and RTS. Neither of these are ticked now, which is the same as on my other (working correctly) radio.

 

I have reloaded L32 in case originally I had a duff download but that made no difference.

 

Right, i’m going to try the DTR and RTS, see if that makes a difference.

 

John, thanks again, I appreciate your taking the time to rerply.

 

73

 

Ken

 

 

 

 

Sent from Mail for Windows 10

 

From: John Munton - G7SSE
Sent: 29 March 2020 17:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 will not read frequency

 

Ken

 

On the lower status bar is the word "Radio" in blue text?
If you hover your mouse over it does it say "com3 open"?
Right click on it and select "Show radio debug window"
You should (if all working correctly) see in the window Logger32 polling the radio and the replies coming back.

If all looks OK try;
On the top menu bar in Logger32 click "Setup" then "Frequency" and make sure the top item on the menu is ticked.

 

If not;

I assume you are using the following settings in the Logger32 radio set up; baud 4800, 8 databits, 2 stopbits and parity to none.

If so, could be you might also need to change either the DTR or RTS settings.

 

I assume also you have correctly installed the drivers for your USB - serial cable?

You can check in Windows / Control Panel / Device Manager, under Ports that you have COM3 showing up.

 

73, GL

 

John - G7SSE

 

------ Original Message ------

Sent: 29/03/2020 16:27:40

Subject: [hamlogger] Logger32 will not read frequency

 

Can any body help a computer skill challenged G3?

I've been trying to set up L32 on a back up Yaesu MK5. using a laptop with W10. I've tried 3 different laptops, all with the same result so its probably not the laptop at fault.

Nothing I do will make L32 read the radio's frequency.

I've got the correct settings for the radio set up, even tried changing them about but no difference. One thing I can't adjust is the serial port number. The laptop gives me the choice of port 3 .... or port 3. I get no messages of incorrect port number. I can't change the port number and unlike my other set up i don't get a choice of serial ports.

I am using a serial to USB cable between the radio CAT socket and laptop. I have tried different cables which presumably rules out an incorrect cable.

I have L32 working perfectly on my main radio and as far as i can see i'm doing everything the same on the MK5. 

Any ideas  anybody?

73

Ken G3XPO


--
73, John - G7SSE

 

 

 


 

 

5921 - 5940 of 85227