I used vspe to make a port for ac log. It didn¡¯t work. Transfered that port to wsjtx where it¡¯s working perfectly. Was going to use the yaesu actual port and it will not work either. Anytime you try you get all of these different messages. Any one want to advise what¡¯s going on ?
Randy K5UF

On Nov 21, 2024, at 8:23?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

I don't understand what you mean by "make a port for ac log."

?

I use VSPE to share the radio USB port (Kenwood TS-890) with applications.? In my case in VSPE, I created a "splitter" with the virtual port = Com 15 and the Data source port = Com 9.? The radio port is set to Com 9, all applications, including ACL "connect" to COM 15.? Understand that to me ACL is a logging program, not a radio control program, so it listens for frequency and mode only.

?

I use (reluctantly) WSJT- Improved in whatever flavor du jour.? It too uses Com 15 and has frequency control of the radio.

?

I also use at various times, or concurrently, DXBase, SpectraVue, MMTTY, N1MM, etc. all connected to Com 15.

?

Wes? N7WS

?

?

On Wed, Nov 20, 2024 at 06:55 PM, Randy Cornelison wrote:

I used vspe to make a port for ac log. It didn¡¯t work. Transfered that port to wsjtx where it¡¯s working perfectly. Was going to use the yaesu actual port and it will not work either. Anytime you try you get all of these different messages. Any one want to advise what¡¯s going on ?
Randy K5UF

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?

On Nov 21, 2024, at 11:33?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

Hi Randy,

?

If I understand correctly, always a dubious proposition at my age, you need to connect all of your applications via Com 13 and only the radio to Com 4.

?

My VSPE interface looks like this:

?

<vspe.PNG>

?

My ACL interface looks like this:

?

<ACL.PNG>

?

My WSJT interface looks like this:

?

<WSJT.PNG>

?

Hope this helps.

?

?

On Thu, Nov 21, 2024 at 07:58 AM, Randy Cornelison wrote:

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?

On Nov 21, 2024, at 11:33?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

Hi Randy,

?

If I understand correctly, always a dubious proposition at my age, you need to connect all of your applications via Com 13 and only the radio to Com 4.

?

My VSPE interface looks like this:

?

<vspe.PNG>

?

My ACL interface looks like this:

?

<ACL.PNG>

?

My WSJT interface looks like this:

?

<WSJT.PNG>

?

Hope this helps.

?

?

On Thu, Nov 21, 2024 at 07:58 AM, Randy Cornelison wrote:

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?

?>>>>>>>>>>>>>>>>>>>>
Everything You Need to Know About USB and Serial Interfaces <https://

N6TV_Dayton_2019_Everything_USB.pdf>
?>>>>>>>>>>>>>>

Thanks!

Brian Warner
WB0NWZ

On Nov 22, 2024, at 5:21?AM, Scott Davis via groups.io <SNKDavis@...> wrote:

?

Hi Randy,

Thanks for your follow up.? Your error message indicate that our software isn't able to access your selected port.? First, your port must be installed properly, with the correct drivers, etc.

Second, Windows will not share ports with other programs, or different functions within the same program. For example, if you are using com port four for rig interface, you'll need to select another com port for CW sending in the software (and of course connect your CW interface to the com port selected for CW). Your CW sending interface and your rig interface are two different devices and each will have to be connected to a different port.

Likewise, if you are using a digital program such as WSJT, you will either need to first disable rig interface in WSJT before connecting to N3FJP Software, or disable rig interface in N3FJP Software (select None from the rig list) before connecting with WSJT.

Com port sharing errors occurs when the port is already in use by another program or another function in N3FJP Software. Whichever program or function you open first takes control of the com port. No other program or function will be able to access it until the resource is released by the program that controls it.

Most folks (including us) use USB to serial adapters for each port function, but we've also had good reports from folks using a single port and com port virtualization software, which will split a physical COM port into multiple virtual ones, like you are attempting with VSPE.? Hopefully others with more experience using com port splitters will have additional insights for you there.

Enjoy!

73, Scott

N3FJP

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

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

On Thursday, November 21, 2024 at 05:10:42 PM EST, Randy Cornelison via groups.io <corn4247@...> wrote:

Age I¡¯m thinking may be a factor here too. I had it running perfectly when win4yaesu hit the scene and things got changed around. Trying to put it back like it was and no success so far. My settings are different from yours as I use one of the yaesu settings. Scott, if you happen to read this could you decipher the error type messages I¡¯m getting? When I close ac log I get a msg that says object reference not set to an instance of an object. Start up program you get access to the port com 4 denied. Com 4 is the one coming out of the radio. Totally lost on this one

On Nov 21, 2024, at 11:33?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

Hi Randy,

?

If I understand correctly, always a dubious proposition at my age, you need to connect all of your applications via Com 13 and only the radio to Com 4.

?

My VSPE interface looks like this:

?

<vspe.PNG>

?

My ACL interface looks like this:

?

<ACL.PNG>

?

My WSJT interface looks like this:

?

<WSJT.PNG>

?

Hope this helps.

?

?

On Thu, Nov 21, 2024 at 07:58 AM, Randy Cornelison wrote:

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?

On Nov 24, 2024, at 1:30?PM, Randy Cornelison via groups.io <corn4247@...> wrote:

?I pulled the cable that comes out of the yaesu ftdx101mp (com4) from the computer. I then put it back in and was able to get rig interface to accept the com port and it is now working on the rig interface page. You can change the rig¡¯s frequency and it displays it when you hit test. Here is the conundrum. The actual ac log page is not showing the frequency although the rig interface is working I think correctly. Any ideas out there?

Randy K5UF?

On Nov 22, 2024, at 5:21?AM, Scott Davis via groups.io <SNKDavis@...> wrote:

?

Hi Randy,

Thanks for your follow up.? Your error message indicate that our software isn't able to access your selected port.? First, your port must be installed properly, with the correct drivers, etc.

Second, Windows will not share ports with other programs, or different functions within the same program. For example, if you are using com port four for rig interface, you'll need to select another com port for CW sending in the software (and of course connect your CW interface to the com port selected for CW). Your CW sending interface and your rig interface are two different devices and each will have to be connected to a different port.

Likewise, if you are using a digital program such as WSJT, you will either need to first disable rig interface in WSJT before connecting to N3FJP Software, or disable rig interface in N3FJP Software (select None from the rig list) before connecting with WSJT.

Com port sharing errors occurs when the port is already in use by another program or another function in N3FJP Software. Whichever program or function you open first takes control of the com port. No other program or function will be able to access it until the resource is released by the program that controls it.

Most folks (including us) use USB to serial adapters for each port function, but we've also had good reports from folks using a single port and com port virtualization software, which will split a physical COM port into multiple virtual ones, like you are attempting with VSPE.? Hopefully others with more experience using com port splitters will have additional insights for you there.

Enjoy!

73, Scott

N3FJP

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

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

On Thursday, November 21, 2024 at 05:10:42 PM EST, Randy Cornelison via groups.io <corn4247@...> wrote:

Age I¡¯m thinking may be a factor here too. I had it running perfectly when win4yaesu hit the scene and things got changed around. Trying to put it back like it was and no success so far. My settings are different from yours as I use one of the yaesu settings. Scott, if you happen to read this could you decipher the error type messages I¡¯m getting? When I close ac log I get a msg that says object reference not set to an instance of an object. Start up program you get access to the port com 4 denied. Com 4 is the one coming out of the radio. Totally lost on this one

On Nov 21, 2024, at 11:33?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

Hi Randy,

?

If I understand correctly, always a dubious proposition at my age, you need to connect all of your applications via Com 13 and only the radio to Com 4.

?

My VSPE interface looks like this:

?

<vspe.PNG>

?

My ACL interface looks like this:

?

<ACL.PNG>

?

My WSJT interface looks like this:

?

<WSJT.PNG>

?

Hope this helps.

?

?

On Thu, Nov 21, 2024 at 07:58 AM, Randy Cornelison wrote:

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?

On Nov 22, 2024, at 5:21?AM, Scott Davis via groups.io <SNKDavis@...> wrote:

?

Hi Randy,

Thanks for your follow up.? Your error message indicate that our software isn't able to access your selected port.? First, your port must be installed properly, with the correct drivers, etc.

Second, Windows will not share ports with other programs, or different functions within the same program. For example, if you are using com port four for rig interface, you'll need to select another com port for CW sending in the software (and of course connect your CW interface to the com port selected for CW). Your CW sending interface and your rig interface are two different devices and each will have to be connected to a different port.

Likewise, if you are using a digital program such as WSJT, you will either need to first disable rig interface in WSJT before connecting to N3FJP Software, or disable rig interface in N3FJP Software (select None from the rig list) before connecting with WSJT.

Com port sharing errors occurs when the port is already in use by another program or another function in N3FJP Software. Whichever program or function you open first takes control of the com port. No other program or function will be able to access it until the resource is released by the program that controls it.

Most folks (including us) use USB to serial adapters for each port function, but we've also had good reports from folks using a single port and com port virtualization software, which will split a physical COM port into multiple virtual ones, like you are attempting with VSPE.? Hopefully others with more experience using com port splitters will have additional insights for you there.

Enjoy!

73, Scott

N3FJP

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

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

On Thursday, November 21, 2024 at 05:10:42 PM EST, Randy Cornelison via groups.io <corn4247@...> wrote:

Age I¡¯m thinking may be a factor here too. I had it running perfectly when win4yaesu hit the scene and things got changed around. Trying to put it back like it was and no success so far. My settings are different from yours as I use one of the yaesu settings. Scott, if you happen to read this could you decipher the error type messages I¡¯m getting? When I close ac log I get a msg that says object reference not set to an instance of an object. Start up program you get access to the port com 4 denied. Com 4 is the one coming out of the radio. Totally lost on this one

On Nov 21, 2024, at 11:33?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

Hi Randy,

?

If I understand correctly, always a dubious proposition at my age, you need to connect all of your applications via Com 13 and only the radio to Com 4.

?

My VSPE interface looks like this:

?

<vspe.PNG>

?

My ACL interface looks like this:

?

<ACL.PNG>

?

My WSJT interface looks like this:

?

<WSJT.PNG>

?

Hope this helps.

?

?

On Thu, Nov 21, 2024 at 07:58 AM, Randy Cornelison wrote:

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?

On Nov 25, 2024, at 5:54?AM, Scott Davis via groups.io <SNKDavis@...> wrote:

?

Hi Randy,

Thanks for your follow up.? I'm sorry that you are still having trouble.? Once configured properly, the frequency will update as you turn your VFO.? Make sure you use the Yaesu Newer 2 selection for your Yaesu 101 MP.? More details on the successful settings other Yaesu 101 MP users have sent along are here:

Enjoy!

73, Scott

N3FJP

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

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

On Sunday, November 24, 2024 at 02:30:05 PM EST, Randy Cornelison via groups.io <corn4247@...> wrote:

I pulled the cable that comes out of the yaesu ftdx101mp (com4) from the computer. I then put it back in and was able to get rig interface to accept the com port and it is now working on the rig interface page. You can change the rig¡¯s frequency and it displays it when you hit test. Here is the conundrum. The actual ac log page is not showing the frequency although the rig interface is working I think correctly. Any ideas out there?

Randy K5UF?

On Nov 22, 2024, at 5:21?AM, Scott Davis via groups.io <SNKDavis@...> wrote:

?

Hi Randy,

Thanks for your follow up.? Your error message indicate that our software isn't able to access your selected port.? First, your port must be installed properly, with the correct drivers, etc.

Second, Windows will not share ports with other programs, or different functions within the same program. For example, if you are using com port four for rig interface, you'll need to select another com port for CW sending in the software (and of course connect your CW interface to the com port selected for CW). Your CW sending interface and your rig interface are two different devices and each will have to be connected to a different port.

Likewise, if you are using a digital program such as WSJT, you will either need to first disable rig interface in WSJT before connecting to N3FJP Software, or disable rig interface in N3FJP Software (select None from the rig list) before connecting with WSJT.

Com port sharing errors occurs when the port is already in use by another program or another function in N3FJP Software. Whichever program or function you open first takes control of the com port. No other program or function will be able to access it until the resource is released by the program that controls it.

Most folks (including us) use USB to serial adapters for each port function, but we've also had good reports from folks using a single port and com port virtualization software, which will split a physical COM port into multiple virtual ones, like you are attempting with VSPE.? Hopefully others with more experience using com port splitters will have additional insights for you there.

Enjoy!

73, Scott

N3FJP

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

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

On Thursday, November 21, 2024 at 05:10:42 PM EST, Randy Cornelison via groups.io <corn4247@...> wrote:

Age I¡¯m thinking may be a factor here too. I had it running perfectly when win4yaesu hit the scene and things got changed around. Trying to put it back like it was and no success so far. My settings are different from yours as I use one of the yaesu settings. Scott, if you happen to read this could you decipher the error type messages I¡¯m getting? When I close ac log I get a msg that says object reference not set to an instance of an object. Start up program you get access to the port com 4 denied. Com 4 is the one coming out of the radio. Totally lost on this one

On Nov 21, 2024, at 11:33?AM, Wes Stewart via groups.io <n7ws@...> wrote:

?

Hi Randy,

?

If I understand correctly, always a dubious proposition at my age, you need to connect all of your applications via Com 13 and only the radio to Com 4.

?

My VSPE interface looks like this:

?

<vspe.PNG>

?

My ACL interface looks like this:

?

<ACL.PNG>

?

My WSJT interface looks like this:

?

<WSJT.PNG>

?

Hope this helps.

?

?

On Thu, Nov 21, 2024 at 07:58 AM, Randy Cornelison wrote:

Good morning Wes and thanks for your reply. What I meant by ¡°make a port for ac log¡± was to put a port on rig interface page that would work properly so ac log will show frequency and mode because currently it¡¯s not. The actual port (data source) on the yaesu is com4. I used vspe to use com4 as data source and com 13. I was using com4 on wsjtx . Tried to activate com 13 on ac log and had no success . Switched com 13 to wsjtx and it works perfectly. Tried com 4 on ac log which had worked fine on wsjtx and had no success. I¡¯m sure it¡¯s a simple fix but almost a computer illiterate here. Again thanks for your reply and maybe you can figure this out?

Randy K5UF?

?