Date   
Re: Spot display 6600M

Bob
 

I put the file, into the two directories with the name 3dff00MSComm.Ocx, renamed the original file 3D1000MSComm.Ocx and dropped the 3dff00 on the new file in BOTH locations where I found the file.

I read this twice, and I'm still confused ... The modified file must be named MSComm32.ocx, that is what Logger32 is looking for. Also, a reboot of the PC is probably in order so that the modified file is loaded. 73.

On December 1, 2019 at 12:03 PM rodman@... wrote:

Bob, I am pretty sure I did what you suggested, but Logger 32 will not run at all unless I put the original .Ocx file back in the two directories.

Summary:  I used HxD to modify MSComm32.Ocx with that exact name with the 3D FF 00 modification.  I put the file, into the two directories with the name 3dff00MSComm.Ocx, renamed the original file 3D1000MSComm.Ocx and dropped the 3dff00 on the new file in BOTH locations where I found the file.  Both directories then had the modified .Ocx file (I checked) but Logger32 would NOT run unless I renamed the original files.  An error message came up, listing MSCOMM.OCX (IN CAPITALS) as the source of the error.  I then put the original files with original names back in.  I am operating the computer by remote control.  I did not restart and did not initiate a restore point either.

Logger 32 is running as before with the COM19 warning on start up.

??  Thanks

 

Re: Spot display 6600M

@sy308
 

Bob, I am pretty sure I did what you suggested, but Logger 32 will not run at all unless I put the original .Ocx file back in the two directories.

Summary:  I used HxD to modify MSComm32.Ocx with that exact name with the 3D FF 00 modification.  I put the file, into the two directories with the name 3dff00MSComm.Ocx, renamed the original file 3D1000MSComm.Ocx and dropped the 3dff00 on the new file in BOTH locations where I found the file.  Both directories then had the modified .Ocx file (I checked) but Logger32 would NOT run unless I renamed the original files.  An error message came up, listing MSCOMM.OCX (IN CAPITALS) as the source of the error.  I then put the original files with original names back in.  I am operating the computer by remote control.  I did not restart and did not initiate a restore point either.

Logger 32 is running as before with the COM19 warning on start up.

??  Thanks

Re: trouble with dx spots window

Bob
 

1, When operating FT8, Logger32 does not send/receive audio. Check you PC Sound cards configuration and you WSJT-X configuration.
2. What radio are you using? There has just been a very long thread on the reflector about CW keying on a Yaesu USB port not working.
3. What is the caption of the DX Spots Window? 

SeventyThree(s).

On December 1, 2019 at 11:16 AM Matthias Bellmann <Dk4wd@...> wrote:

Hi
i am using a new computer win 10 prof. as administrator.
Now i am trying to make logger32 3.50.402 work as it was before. 
There are several problems:
 
1. FT8 / WSJT
The trcvr does not respond to the sound card out signal. PTT works, wsjt is reveiving.
 
 
2. CW machine similar problem. PTT works, cw machine is keying,but cw signal is ignored by trcvr. Use COM1 (real serial) und com4 (USB). Always same result. Did test every possible combination in the cw machine keyer setup. There muzst be something i did not realize.
 
3. I am connected with telnet dx-cluster. It works fine. dx spots are displayed in the telnet window but dx spots windows remains empty. Only WWV announcement and ann messages are displayed. All blocking filter in are disabled. 
 
PLEASE NO ANSWER "read help file". I did read help for many hours and did try many settings, now i gave up.
 
Any answer well be appreciated.
 
 
 

 

Re: ODP: ODP: [hamlogger] CW machine

Dave Colliau
 

I never got any of the enhanced ports Icom or Yaesu to work cw . I just used my old trusty home brew cw cable and a standard port and all is good. Since I had the cable from previous rigs and knew it worked i never really went too far with the cw machine and the keying.
Dave N8DC

On December 1, 2019 at 11:17 AM Andy VA3PL <va3pl@...> wrote:

 
Hi Bob
I am not computer wiz, just the computer user.
These are com ports created by YAESU provided driver. It is Silicon Labs driver.

Silicon Labs Dual CT2105 USB UART Bridge Enhanced COM Port (in my case COM5 used for CAT)
Silicon Labs Dual CT2105 USB UART Bridge Standard COM Port (in my case COM6 used for CW, Audio, RTTY)

Andy SP9KR




Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Bob <k4cy@...>
Wysłane: niedziela, 1 grudnia 2019 16:28
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: ODP: [hamlogger] CW machine
 
What is an enhanced virtual port, and how/why is it necessary for your PC to CAT connection? 73.
On November 30, 2019 at 3:20 AM Andy VA3PL <va3pl@...> wrote:

 
Vince
Go to page 94 and read it and understand.

As a test just loaded N1MM set it up using ENHANCED virtual port for CAT and configured REGULAR virtual port for CW and it work nicely.

Also on 101D go to CW SETTING and change there to PC KEYING using DTR.

CW work nicely in N1MM but not using Logger32 CW MACHINE.

Andy SP9KR

Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Vince Shirley <vince.g0orc@...>
Wysłane: sobota, 30 listopada 2019 00:29
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] CW machine
 
Hi Bob,

I still standby what I say in that there is nothing in the manual to suggest that CW may be sent down the USB port and I have never managed to make it work. I use an external interface should I wish to use electronic keying of CW

RTTY is supported as shown on P66 of the manual.  There is no such entry for CW.

The one thing that enables us to sleep soundly in our beds is that we don't have guns available to buy from our local supermarkets.  Oh, and our politicians may be the least respected members of our society but at least we haven't got Mr. Trump.  For that we are eternally grateful.

Vince 

On Fri, 29 Nov 2019 at 23:07, Bob < k4cy@...> wrote:
Vince, before you drift off into the arms of Morpheus (then wake up screaming from your nightmare of being on London Bridge at the wrong time) ... remember this message from the originator of the thread ...

Yes, there are two USB ports. One is enhanced for CAT and second USB is for other thinks, I have tried many combinations using one or the other and still no CW trough USB cable.
I been trying to avoid hurting somebody saying that other well known contest software provide capability of configuring CW trough USB cable and it works.
I was told by someone that "driver for Logger32 CW machine need to be updated".

SeventyThree(s).
On November 29, 2019 at 5:47 PM Vince Shirley < vince.g0orc@...> wrote:

At last - the voice of sanity.

Thanks Darren.  I said in the early days of this thread that the menu item relates to the keying of the radio and not sending CW which was something I worked out when I briefly owned an FTdx3000 which was very similar.in this respect. 

I gave up because no-one was listening.

There is nothing in the manual to say that CW may be sent down the radio's USB port.  If some operators have got it work then you are better than me and I'd love to know how you have done it using CW machine in Logger32.

I failed to get it to work with the FTdx3000 which had essentially the same menu item at the FTdx101.   If I remember correctly the FTdx5000 had PC keying in the menu but it had not been activated and was waiting for a software update.

I'll go and have lie down now...

Regards

Vince G0ORC





On Fri, 29 Nov 2019 at 14:10, Darren Collins (G0TSM) < daz@...> wrote:

I don't own an FTDX101 (I have the FTDX5K) but looking at the user manual it suggests that PC KEYING relates to the PTT and not to the CW Keying. If you look at the settings for the other modes it has the same options but for the other modes says its for RPTT SELECT. So it appears to be badly worded.

[RTTY] RPTT SELECT - DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 90))

[CW] PC KEYING -  DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 94))

I would imagine that Yaesu would be able to implement CW Keying via a software update, so its just down to the FTDX101 owners to request the feature. I recall that someone at Yaesu USA ran a 'wish list' for the FTDX5000 when it came out, so they are probably doing the same for the 101.

73 Darren G0TSM



On 28/11/19 21:10, Andy None via Groups.Io wrote:
Vince
Same here. radio keys and unkeys but no CW is send.
I give up also and went by using WinKeyer USB.
Been trying to use enhanced or regular USB port (they have different COM number) without success.

Andy SP9KR

On Thursday, November 28, 2019, 5:25:01 p.m. GMT+1, Vince Shirley <vince.g0orc@...> wrote:



I give up with this - there is nothing in the manual save for an entry in the CW MENU section which describes how to key the radio via its own USP port.

The radio keys and unkeys OK - but no CW is sent

My last word on the subject.

Vince G0ORC


On Thu, 28 Nov 2019 at 16:04, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Yes Mike, quite so.

But it doesn't work! 

Did you not read the rest of the message?

Vince

On Thu, 28 Nov 2019 at 15:29, Mike < ch25@...> wrote:
On Thu, Nov 28, 2019 at 03:59 PM, Vince Shirley wrote:
Thank you - I'm quite prepared to eat a large portion of humble pie and admit that I was wrong, but I just can't get it this to work. 
As written in the manual.
Mike

 

 


 

 

 


 

 

ODP: ODP: [hamlogger] CW machine

Andy VA3PL
 

Hi Bob
I am not computer wiz, just the computer user.
These are com ports created by YAESU provided driver. It is Silicon Labs driver.

Silicon Labs Dual CT2105 USB UART Bridge Enhanced COM Port (in my case COM5 used for CAT)
Silicon Labs Dual CT2105 USB UART Bridge Standard COM Port (in my case COM6 used for CW, Audio, RTTY)

Andy SP9KR




Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Bob <k4cy@...>
Wysłane: niedziela, 1 grudnia 2019 16:28
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: ODP: [hamlogger] CW machine
 
What is an enhanced virtual port, and how/why is it necessary for your PC to CAT connection? 73.

On November 30, 2019 at 3:20 AM Andy VA3PL <va3pl@...> wrote:

 
Vince
Go to page 94 and read it and understand.

As a test just loaded N1MM set it up using ENHANCED virtual port for CAT and configured REGULAR virtual port for CW and it work nicely.

Also on 101D go to CW SETTING and change there to PC KEYING using DTR.

CW work nicely in N1MM but not using Logger32 CW MACHINE.

Andy SP9KR

Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Vince Shirley <vince.g0orc@...>
Wysłane: sobota, 30 listopada 2019 00:29
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] CW machine
 
Hi Bob,

I still standby what I say in that there is nothing in the manual to suggest that CW may be sent down the USB port and I have never managed to make it work. I use an external interface should I wish to use electronic keying of CW

RTTY is supported as shown on P66 of the manual.  There is no such entry for CW.

The one thing that enables us to sleep soundly in our beds is that we don't have guns available to buy from our local supermarkets.  Oh, and our politicians may be the least respected members of our society but at least we haven't got Mr. Trump.  For that we are eternally grateful.

Vince 

On Fri, 29 Nov 2019 at 23:07, Bob < k4cy@...> wrote:
Vince, before you drift off into the arms of Morpheus (then wake up screaming from your nightmare of being on London Bridge at the wrong time) ... remember this message from the originator of the thread ...

Yes, there are two USB ports. One is enhanced for CAT and second USB is for other thinks, I have tried many combinations using one or the other and still no CW trough USB cable.
I been trying to avoid hurting somebody saying that other well known contest software provide capability of configuring CW trough USB cable and it works.
I was told by someone that "driver for Logger32 CW machine need to be updated".

SeventyThree(s).
On November 29, 2019 at 5:47 PM Vince Shirley < vince.g0orc@...> wrote:

At last - the voice of sanity.

Thanks Darren.  I said in the early days of this thread that the menu item relates to the keying of the radio and not sending CW which was something I worked out when I briefly owned an FTdx3000 which was very similar.in this respect. 

I gave up because no-one was listening.

There is nothing in the manual to say that CW may be sent down the radio's USB port.  If some operators have got it work then you are better than me and I'd love to know how you have done it using CW machine in Logger32.

I failed to get it to work with the FTdx3000 which had essentially the same menu item at the FTdx101.   If I remember correctly the FTdx5000 had PC keying in the menu but it had not been activated and was waiting for a software update.

I'll go and have lie down now...

Regards

Vince G0ORC





On Fri, 29 Nov 2019 at 14:10, Darren Collins (G0TSM) < daz@...> wrote:

I don't own an FTDX101 (I have the FTDX5K) but looking at the user manual it suggests that PC KEYING relates to the PTT and not to the CW Keying. If you look at the settings for the other modes it has the same options but for the other modes says its for RPTT SELECT. So it appears to be badly worded.

[RTTY] RPTT SELECT - DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 90))

[CW] PC KEYING -  DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 94))

I would imagine that Yaesu would be able to implement CW Keying via a software update, so its just down to the FTDX101 owners to request the feature. I recall that someone at Yaesu USA ran a 'wish list' for the FTDX5000 when it came out, so they are probably doing the same for the 101.

73 Darren G0TSM



On 28/11/19 21:10, Andy None via Groups.Io wrote:
Vince
Same here. radio keys and unkeys but no CW is send.
I give up also and went by using WinKeyer USB.
Been trying to use enhanced or regular USB port (they have different COM number) without success.

Andy SP9KR

On Thursday, November 28, 2019, 5:25:01 p.m. GMT+1, Vince Shirley <vince.g0orc@...> wrote:



I give up with this - there is nothing in the manual save for an entry in the CW MENU section which describes how to key the radio via its own USP port.

The radio keys and unkeys OK - but no CW is sent

My last word on the subject.

Vince G0ORC


On Thu, 28 Nov 2019 at 16:04, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Yes Mike, quite so.

But it doesn't work! 

Did you not read the rest of the message?

Vince

On Thu, 28 Nov 2019 at 15:29, Mike < ch25@...> wrote:
On Thu, Nov 28, 2019 at 03:59 PM, Vince Shirley wrote:
Thank you - I'm quite prepared to eat a large portion of humble pie and admit that I was wrong, but I just can't get it this to work. 
As written in the manual.
Mike

 

 


 

 

 


 

trouble with dx spots window

Matthias Bellmann
 

Hi
i am using a new computer win 10 prof. as administrator.
Now i am trying to make logger32 3.50.402 work as it was before. 
There are several problems:
 
1. FT8 / WSJT
The trcvr does not respond to the sound card out signal. PTT works, wsjt is reveiving.
 
 
2. CW machine similar problem. PTT works, cw machine is keying,but cw signal is ignored by trcvr. Use COM1 (real serial) und com4 (USB). Always same result. Did test every possible combination in the cw machine keyer setup. There muzst be something i did not realize.
 
3. I am connected with telnet dx-cluster. It works fine. dx spots are displayed in the telnet window but dx spots windows remains empty. Only WWV announcement and ann messages are displayed. All blocking filter in are disabled. 
 
PLEASE NO ANSWER "read help file". I did read help for many hours and did try many settings, now i gave up.
 
Any answer well be appreciated.
 
 
 

Re: ODP: [hamlogger] CW machine

Bob
 

What is an enhanced virtual port, and how/why is it necessary for your PC to CAT connection? 73.

On November 30, 2019 at 3:20 AM Andy VA3PL <va3pl@...> wrote:

 
Vince
Go to page 94 and read it and understand.

As a test just loaded N1MM set it up using ENHANCED virtual port for CAT and configured REGULAR virtual port for CW and it work nicely.

Also on 101D go to CW SETTING and change there to PC KEYING using DTR.

CW work nicely in N1MM but not using Logger32 CW MACHINE.

Andy SP9KR

Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Vince Shirley <vince.g0orc@...>
Wysłane: sobota, 30 listopada 2019 00:29
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] CW machine
 
Hi Bob,

I still standby what I say in that there is nothing in the manual to suggest that CW may be sent down the USB port and I have never managed to make it work. I use an external interface should I wish to use electronic keying of CW

RTTY is supported as shown on P66 of the manual.  There is no such entry for CW.

The one thing that enables us to sleep soundly in our beds is that we don't have guns available to buy from our local supermarkets.  Oh, and our politicians may be the least respected members of our society but at least we haven't got Mr. Trump.  For that we are eternally grateful.

Vince 

On Fri, 29 Nov 2019 at 23:07, Bob < k4cy@...> wrote:
Vince, before you drift off into the arms of Morpheus (then wake up screaming from your nightmare of being on London Bridge at the wrong time) ... remember this message from the originator of the thread ...

Yes, there are two USB ports. One is enhanced for CAT and second USB is for other thinks, I have tried many combinations using one or the other and still no CW trough USB cable.
I been trying to avoid hurting somebody saying that other well known contest software provide capability of configuring CW trough USB cable and it works.
I was told by someone that "driver for Logger32 CW machine need to be updated".

SeventyThree(s).
On November 29, 2019 at 5:47 PM Vince Shirley < vince.g0orc@...> wrote:

At last - the voice of sanity.

Thanks Darren.  I said in the early days of this thread that the menu item relates to the keying of the radio and not sending CW which was something I worked out when I briefly owned an FTdx3000 which was very similar.in this respect. 

I gave up because no-one was listening.

There is nothing in the manual to say that CW may be sent down the radio's USB port.  If some operators have got it work then you are better than me and I'd love to know how you have done it using CW machine in Logger32.

I failed to get it to work with the FTdx3000 which had essentially the same menu item at the FTdx101.   If I remember correctly the FTdx5000 had PC keying in the menu but it had not been activated and was waiting for a software update.

I'll go and have lie down now...

Regards

Vince G0ORC





On Fri, 29 Nov 2019 at 14:10, Darren Collins (G0TSM) < daz@...> wrote:

I don't own an FTDX101 (I have the FTDX5K) but looking at the user manual it suggests that PC KEYING relates to the PTT and not to the CW Keying. If you look at the settings for the other modes it has the same options but for the other modes says its for RPTT SELECT. So it appears to be badly worded.

[RTTY] RPTT SELECT - DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 90))

[CW] PC KEYING -  DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 94))

I would imagine that Yaesu would be able to implement CW Keying via a software update, so its just down to the FTDX101 owners to request the feature. I recall that someone at Yaesu USA ran a 'wish list' for the FTDX5000 when it came out, so they are probably doing the same for the 101.

73 Darren G0TSM



On 28/11/19 21:10, Andy None via Groups.Io wrote:
Vince
Same here. radio keys and unkeys but no CW is send.
I give up also and went by using WinKeyer USB.
Been trying to use enhanced or regular USB port (they have different COM number) without success.

Andy SP9KR

On Thursday, November 28, 2019, 5:25:01 p.m. GMT+1, Vince Shirley <vince.g0orc@...> wrote:



I give up with this - there is nothing in the manual save for an entry in the CW MENU section which describes how to key the radio via its own USP port.

The radio keys and unkeys OK - but no CW is sent

My last word on the subject.

Vince G0ORC


On Thu, 28 Nov 2019 at 16:04, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Yes Mike, quite so.

But it doesn't work! 

Did you not read the rest of the message?

Vince

On Thu, 28 Nov 2019 at 15:29, Mike < ch25@...> wrote:
On Thu, Nov 28, 2019 at 03:59 PM, Vince Shirley wrote:
Thank you - I'm quite prepared to eat a large portion of humble pie and admit that I was wrong, but I just can't get it this to work. 
As written in the manual.
Mike

 

 


 

 

 


 

Re: Spot display 6600M

Bob
 

Does it matter? Zap both of them (just to cover your ass) ... SeventyThree(s).

On November 30, 2019 at 9:25 PM rodman@... wrote:

I found mscomm32.ocx in two locations in my computer.  First is C:$WINDOWS.~BT\NewOS\Windows\SysWOW64 and the second is C:\Windows\SysWOW64.  My bet is the second location.  Am I correct??

 

Re: Spot display 6600M

@sy308
 

I found mscomm32.ocx in two locations in my computer.  First is C:$WINDOWS.~BT\NewOS\Windows\SysWOW64 and the second is C:\Windows\SysWOW64.  My bet is the second location.  Am I correct??

Re: Clicking on spots always SSB

Ignacy Misztal
 

Now it is working.
Getting Flex to work fully is a full-time job!
Ignacy, NO9E

Re: Clicking on spots always SSB

Bob
 

Yes,  Set RX1 Mode: ZZMD00; will set the radio to LSB as expected. Flex Radio has no CW mode. Try CWL and/or CWU in the 6th column. SeventyThree(s). 

On November 30, 2019 at 6:24 PM Ignacy Misztal <no9e@...> wrote:

MODE from BandPlan still retruns SSB. 6th column in Bandplan says CW. The debug windows shows:
QSY Market Set: Radio Freq. 7019.9 QSY Marker 7019.900
Set RX1 Mode: ZZMD00;
Set VFO-A Freq: ZZFA00007019900

 

Re: Clicking on spots always SSB

Ignacy Misztal
 

MODE from BandPlan still retruns SSB. 6th column in Bandplan says CW. The debug windows shows:
QSY Market Set: Radio Freq. 7019.9 QSY Marker 7019.900
Set RX1 Mode: ZZMD00;
Set VFO-A Freq: ZZFA00007019900

Re: Clicking on spots always SSB

Bob
 

Try setting Mode from BandPlan with the other two mode from options unchecked. Then, when you click on a CW DX Spot. if the radio does not switch to CW, then look at your personalized band plan (click TOOLS the SETUP BANDS & MODES) match the frequency in the 3rd/4th columns to the DX Spot frequency ... Does the 6th column say CW? If it does say CW, then the radio should have been commanded to switch to CW. Now you'll need to open the Radio debug Window (right click on the radio pane - at the middle of the lower status bar - then click SHOW RADIO DEBUG WINDOW) and examine the commands sent to the radio. 73.

On November 30, 2019 at 9:46 AM Ignacy Misztal <no9e@...> wrote:

Clicking on spots always reverts to  SSB mode. 
BandMode selection is set to "Mode from radio or DX spots". Setting to "Mode from BandPlan" does not change anything.
Radio is Flex 6600 running 3.1.18.
Ignacy, NO9E

 

Re: Clicking on spots always SSB

Ignacy Misztal
 

3.1.18 is Flex version. Running the newest version of L32.
This setup is for a remote station. At home with K3, L32 is working perfectly.
Ignacy, NO9E

Re: Clicking on spots always SSB

Bob
 

Does 3.1.18 refer to some version of Flex Radio software, or Logger32 version? 73.

On November 30, 2019 at 9:46 AM Ignacy Misztal <no9e@...> wrote:

Clicking on spots always reverts to  SSB mode. 
BandMode selection is set to "Mode from radio or DX spots". Setting to "Mode from BandPlan" does not change anything.
Radio is Flex 6600 running 3.1.18.
Ignacy, NO9E

 

Clicking on spots always SSB

Ignacy Misztal
 

Clicking on spots always reverts to  SSB mode. 
BandMode selection is set to "Mode from radio or DX spots". Setting to "Mode from BandPlan" does not change anything.
Radio is Flex 6600 running 3.1.18.
Ignacy, NO9E

ODP: [hamlogger] CW machine

Andy VA3PL
 

Vince
Go to page 94 and read it and understand.

As a test just loaded N1MM set it up using ENHANCED virtual port for CAT and configured REGULAR virtual port for CW and it work nicely.

Also on 101D go to CW SETTING and change there to PC KEYING using DTR.

CW work nicely in N1MM but not using Logger32 CW MACHINE.

Andy SP9KR

Od: hamlogger@groups.io <hamlogger@groups.io> w imieniu użytkownika Vince Shirley <vince.g0orc@...>
Wysłane: sobota, 30 listopada 2019 00:29
Do: hamlogger@groups.io <hamlogger@groups.io>
Temat: Re: [hamlogger] CW machine
 
Hi Bob,

I still standby what I say in that there is nothing in the manual to suggest that CW may be sent down the USB port and I have never managed to make it work. I use an external interface should I wish to use electronic keying of CW

RTTY is supported as shown on P66 of the manual.  There is no such entry for CW.

The one thing that enables us to sleep soundly in our beds is that we don't have guns available to buy from our local supermarkets.  Oh, and our politicians may be the least respected members of our society but at least we haven't got Mr. Trump.  For that we are eternally grateful.

Vince 

On Fri, 29 Nov 2019 at 23:07, Bob <k4cy@...> wrote:
Vince, before you drift off into the arms of Morpheus (then wake up screaming from your nightmare of being on London Bridge at the wrong time) ... remember this message from the originator of the thread ...

Yes, there are two USB ports. One is enhanced for CAT and second USB is for other thinks, I have tried many combinations using one or the other and still no CW trough USB cable.
I been trying to avoid hurting somebody saying that other well known contest software provide capability of configuring CW trough USB cable and it works.
I was told by someone that "driver for Logger32 CW machine need to be updated".

SeventyThree(s).
On November 29, 2019 at 5:47 PM Vince Shirley <vince.g0orc@...> wrote:

At last - the voice of sanity.

Thanks Darren.  I said in the early days of this thread that the menu item relates to the keying of the radio and not sending CW which was something I worked out when I briefly owned an FTdx3000 which was very similar.in this respect. 

I gave up because no-one was listening.

There is nothing in the manual to say that CW may be sent down the radio's USB port.  If some operators have got it work then you are better than me and I'd love to know how you have done it using CW machine in Logger32.

I failed to get it to work with the FTdx3000 which had essentially the same menu item at the FTdx101.   If I remember correctly the FTdx5000 had PC keying in the menu but it had not been activated and was waiting for a software update.

I'll go and have lie down now...

Regards

Vince G0ORC





On Fri, 29 Nov 2019 at 14:10, Darren Collins (G0TSM) < daz@...> wrote:

I don't own an FTDX101 (I have the FTDX5K) but looking at the user manual it suggests that PC KEYING relates to the PTT and not to the CW Keying. If you look at the settings for the other modes it has the same options but for the other modes says its for RPTT SELECT. So it appears to be badly worded.

[RTTY] RPTT SELECT - DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 90))

[CW] PC KEYING -  DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 94))

I would imagine that Yaesu would be able to implement CW Keying via a software update, so its just down to the FTDX101 owners to request the feature. I recall that someone at Yaesu USA ran a 'wish list' for the FTDX5000 when it came out, so they are probably doing the same for the 101.

73 Darren G0TSM



On 28/11/19 21:10, Andy None via Groups.Io wrote:
Vince
Same here. radio keys and unkeys but no CW is send.
I give up also and went by using WinKeyer USB.
Been trying to use enhanced or regular USB port (they have different COM number) without success.

Andy SP9KR

On Thursday, November 28, 2019, 5:25:01 p.m. GMT+1, Vince Shirley <vince.g0orc@...> wrote:



I give up with this - there is nothing in the manual save for an entry in the CW MENU section which describes how to key the radio via its own USP port.

The radio keys and unkeys OK - but no CW is sent

My last word on the subject.

Vince G0ORC


On Thu, 28 Nov 2019 at 16:04, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Yes Mike, quite so.

But it doesn't work! 

Did you not read the rest of the message?

Vince

On Thu, 28 Nov 2019 at 15:29, Mike < ch25@...> wrote:
On Thu, Nov 28, 2019 at 03:59 PM, Vince Shirley wrote:
Thank you - I'm quite prepared to eat a large portion of humble pie and admit that I was wrong, but I just can't get it this to work. 
As written in the manual.
Mike

 

 


 

Re: Spot display 6600M

Rick Ellison
 

I think Bob needs to build a new version of Logger32 on VB.NET. This way you can have up to 256 com ports to use. J

 

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Friday, November 29, 2019 7:44 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Spot display 6600M

 

Logger outputs N1MM+ formatted DX Spot data (and a whole bunch more - tooltip test, background color, and text color to match the DX Spot window settings) on localhost address 127.0.0.1 on port 12061. Software called Slice-Master listens on this port (in the same PC as Logger32) and overlays the DX Spot info onto the Flex Radio eye candy. How you configure the various components for your remote configuration is of no concern to Logger32. Now to your question about 16 serial ports limit in Logger32 ... Yes, Microsoft have restricted the number of serial ports supported by the MSCOMM32.OCX to 16. However, if you Google MSCOMM32 16 PORTS, you'll find a gazillion ways to hack your way around this limitation. Simplified, you need to do the following:

 

a) Make a backup copy of the MSCOMM32.OCX

b) With a HEX editor find the byte sequence 3D 10 00 in the file and change it to 3D FF 00

c) Save the change

 

Or, ask here for anyone who has made the hack to share the file with you. SeventyThree(s).

On November 29, 2019 at 6:09 PM rodman@... wrote:

I am going to post this same exact information to hamlogger too.  I have the Maestro/6600M pair.  At the remote location, I normally use Hamlogger32, but can use N1MM.  I am hoping to show spots on the Maestro, but I have no conception of how to organize the two locations to accomplish this.  I read the brief posting on how to get N1MM to connect to the system and shows information about an ip address of 127.x.x.x and I have no understanding on how that number will be useful.  All my computers are 192.x.x.x and this whole situation leads me to several questions.  Some are simple like, how do I begin to set up the computer at either end to do this?  What steps does one follow?  What is ideal or best program for this operation?  Is this worthwhile?  Do I feed the spots to the remote station end or the Maestro?  Which computer end is best for logging operations, the remote or the station?  Where is the best source of help showing how to setup and implement this selection?  What are the limitations on showing the spots?  How does COM numbering affect or allow this?  The computer at the remote end has over 15 COM ports and addressing them has been an issue with hamlogger because there appears to be a limit, numerically, what the program is capable or looking at.  It appears that when the 6600M was installed, it is paired with COM 19, but hamlogger will not recognize and provides an error message on start up.  COM 19 shows in device manager.   I know nothing about the overview on what needs to be provided or available in to get spots from hamlogger32 to the Flex.  A flow chart or  video, might be helpful for me to conceptually understand the requirements of the software better.  Thank you.


 

Re: Spot display 6600M

Bob
 

Logger outputs N1MM+ formatted DX Spot data (and a whole bunch more - tooltip test, background color, and text color to match the DX Spot window settings) on localhost address 127.0.0.1 on port 12061. Software called Slice-Master listens on this port (in the same PC as Logger32) and overlays the DX Spot info onto the Flex Radio eye candy. How you configure the various components for your remote configuration is of no concern to Logger32. Now to your question about 16 serial ports limit in Logger32 ... Yes, Microsoft have restricted the number of serial ports supported by the MSCOMM32.OCX to 16. However, if you Google MSCOMM32 16 PORTS, you'll find a gazillion ways to hack your way around this limitation. Simplified, you need to do the following:

a) Make a backup copy of the MSCOMM32.OCX
b) With a HEX editor find the byte sequence 3D 10 00 in the file and change it to 3D FF 00
c) Save the change

Or, ask here for anyone who has made the hack to share the file with you. SeventyThree(s).

On November 29, 2019 at 6:09 PM rodman@... wrote:

I am going to post this same exact information to hamlogger too.  I have the Maestro/6600M pair.  At the remote location, I normally use Hamlogger32, but can use N1MM.  I am hoping to show spots on the Maestro, but I have no conception of how to organize the two locations to accomplish this.  I read the brief posting on how to get N1MM to connect to the system and shows information about an ip address of 127.x.x.x and I have no understanding on how that number will be useful.  All my computers are 192.x.x.x and this whole situation leads me to several questions.  Some are simple like, how do I begin to set up the computer at either end to do this?  What steps does one follow?  What is ideal or best program for this operation?  Is this worthwhile?  Do I feed the spots to the remote station end or the Maestro?  Which computer end is best for logging operations, the remote or the station?  Where is the best source of help showing how to setup and implement this selection?  What are the limitations on showing the spots?  How does COM numbering affect or allow this?  The computer at the remote end has over 15 COM ports and addressing them has been an issue with hamlogger because there appears to be a limit, numerically, what the program is capable or looking at.  It appears that when the 6600M was installed, it is paired with COM 19, but hamlogger will not recognize and provides an error message on start up.  COM 19 shows in device manager.   I know nothing about the overview on what needs to be provided or available in to get spots from hamlogger32 to the Flex.  A flow chart or  video, might be helpful for me to conceptually understand the requirements of the software better.  Thank you.

 

Re: CW machine

Bob
 

Vince, you'll be pleased to hear POTUS will be there on Tuesday (even attending a soiree with HRH). BTW, it's rumored that the Met have applied for permission to erect these signs at each end of the bridge ... 



SeventyThree(s).

On November 29, 2019 at 6:29 PM Vince Shirley <vince.g0orc@...> wrote:

Hi Bob,

I still standby what I say in that there is nothing in the manual to suggest that CW may be sent down the USB port and I have never managed to make it work. I use an external interface should I wish to use electronic keying of CW

RTTY is supported as shown on P66 of the manual.  There is no such entry for CW.

The one thing that enables us to sleep soundly in our beds is that we don't have guns available to buy from our local supermarkets.  Oh, and our politicians may be the least respected members of our society but at least we haven't got Mr. Trump.  For that we are eternally grateful.

Vince 

On Fri, 29 Nov 2019 at 23:07, Bob < k4cy@...> wrote:
Vince, before you drift off into the arms of Morpheus (then wake up screaming from your nightmare of being on London Bridge at the wrong time) ... remember this message from the originator of the thread ...

Yes, there are two USB ports. One is enhanced for CAT and second USB is for other thinks, I have tried many combinations using one or the other and still no CW trough USB cable.
I been trying to avoid hurting somebody saying that other well known contest software provide capability of configuring CW trough USB cable and it works.
I was told by someone that "driver for Logger32 CW machine need to be updated".

SeventyThree(s).
On November 29, 2019 at 5:47 PM Vince Shirley < vince.g0orc@...> wrote:

At last - the voice of sanity.

Thanks Darren.  I said in the early days of this thread that the menu item relates to the keying of the radio and not sending CW which was something I worked out when I briefly owned an FTdx3000 which was very similar.in this respect. 

I gave up because no-one was listening.

There is nothing in the manual to say that CW may be sent down the radio's USB port.  If some operators have got it work then you are better than me and I'd love to know how you have done it using CW machine in Logger32.

I failed to get it to work with the FTdx3000 which had essentially the same menu item at the FTdx101.   If I remember correctly the FTdx5000 had PC keying in the menu but it had not been activated and was waiting for a software update.

I'll go and have lie down now...

Regards

Vince G0ORC





On Fri, 29 Nov 2019 at 14:10, Darren Collins (G0TSM) < daz@...> wrote:

I don't own an FTDX101 (I have the FTDX5K) but looking at the user manual it suggests that PC KEYING relates to the PTT and not to the CW Keying. If you look at the settings for the other modes it has the same options but for the other modes says its for RPTT SELECT. So it appears to be badly worded.

[RTTY] RPTT SELECT - DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 90))

[CW] PC KEYING -  DAKY (Pin 3 on data jack - (which is PTT) / DTR / RTS (Page 94))

I would imagine that Yaesu would be able to implement CW Keying via a software update, so its just down to the FTDX101 owners to request the feature. I recall that someone at Yaesu USA ran a 'wish list' for the FTDX5000 when it came out, so they are probably doing the same for the 101.

73 Darren G0TSM



On 28/11/19 21:10, Andy None via Groups.Io wrote:
Vince
Same here. radio keys and unkeys but no CW is send.
I give up also and went by using WinKeyer USB.
Been trying to use enhanced or regular USB port (they have different COM number) without success.

Andy SP9KR

On Thursday, November 28, 2019, 5:25:01 p.m. GMT+1, Vince Shirley <vince.g0orc@...> wrote:



I give up with this - there is nothing in the manual save for an entry in the CW MENU section which describes how to key the radio via its own USP port.

The radio keys and unkeys OK - but no CW is sent

My last word on the subject.

Vince G0ORC


On Thu, 28 Nov 2019 at 16:04, Vince Shirley via Groups.Io <vince.g0orc= gmail.com@groups.io> wrote:
Yes Mike, quite so.

But it doesn't work! 

Did you not read the rest of the message?

Vince

On Thu, 28 Nov 2019 at 15:29, Mike < ch25@...> wrote:
On Thu, Nov 28, 2019 at 03:59 PM, Vince Shirley wrote:
Thank you - I'm quite prepared to eat a large portion of humble pie and admit that I was wrong, but I just can't get it this to work. 
As written in the manual.
Mike