1. Topics
  2. Setup FT1000mp

Setup FT1000mp

Jeff Wilson <jjw5257@...>
 

All the CAT failures with my FT1000mp and Logger32 have come down the the selected COM port not being available.  Usually this was because it was also assigned to N1MM or WSJTX even though they were not even open. I connect my rig to the Win7 COM1 for CAT.  If I removed COM 1 from the N1MM config, problem solved.  I have suffered this inconvenience for years.  Maybe OMNI-Rig or the new slave port function in L32 will help.  I use OMNI-Rig to run Logger32 and WSJTX with the FT1000mp with no problem.
I hope this helps.
73
Jeff VE3CV
ka5hetradio@...
 

Thanks for your help. I will try this, but leaning towards N1MM program. 
Thanks 
ka5het 

On Fri, Feb 22, 2019 at 6:38 AM Jeff Wilson via Groups.Io <jjw5257=yahoo.ca@groups.io> wrote:
All the CAT failures with my FT1000mp and Logger32 have come down the the selected COM port not being available.  Usually this was because it was also assigned to N1MM or WSJTX even though they were not even open. I connect my rig to the Win7 COM1 for CAT.  If I removed COM 1 from the N1MM config, problem solved.  I have suffered this inconvenience for years.  Maybe OMNI-Rig or the new slave port function in L32 will help.  I use OMNI-Rig to run Logger32 and WSJTX with the FT1000mp with no problem.
I hope this helps.
73
Jeff VE3CV


--
Steve McDonald
Bob
 

I have a great deal of difficulty believing that Logger32 is smart enough to know that COM1 is assigned to CAT control in N1MM or WSJT when N1MM and WSJT are not running. I suspect there's something else involved that you haven't mentioned.  I can assure you the Logger32 does not read the N1MM or WSJT configuration files to figure out if there is potential port conflict. Exactly what is the Logger32 error message?  SeventyThree(s).

On February 22, 2019 at 7:37 AM "Jeff Wilson via Groups.Io" <jjw5257@...> wrote:

All the CAT failures with my FT1000mp and Logger32 have come down the the selected COM port not being available.  Usually this was because it was also assigned to N1MM or WSJTX even though they were not even open. I connect my rig to the Win7 COM1 for CAT.  If I removed COM 1 from the N1MM config, problem solved.  I have suffered this inconvenience for years.  Maybe OMNI-Rig or the new slave port function in L32 will help.  I use OMNI-Rig to run Logger32 and WSJTX with the FT1000mp with no problem.
I hope this helps.
73
Jeff VE3CV


 


 
n5kd
 

Did I miss something? L32 supports OMNI-Rig now? I’ve been wanting this feature for ages. I’ll have a “play” later today.

73’ Pete, N5KD.



On Feb 22, 2019, at 12:37, Jeff Wilson via Groups.Io <jjw5257@...> wrote:

All the CAT failures with my FT1000mp and Logger32 have come down the the selected COM port not being available.  Usually this was because it was also assigned to N1MM or WSJTX even though they were not even open. I connect my rig to the Win7 COM1 for CAT.  If I removed COM 1 from the N1MM config, problem solved.  I have suffered this inconvenience for years.  Maybe OMNI-Rig or the new slave port function in L32 will help.  I use OMNI-Rig to run Logger32 and WSJTX with the FT1000mp with no problem.
I hope this helps.
73
Jeff VE3CV
1 - 4 of 4