Hi Ken,

?

Thanks for your e-mail.? The rig interface code in all our software is identical.? Since rig interface is working in CQ WW, from CQ WW's rig interface form, click the Save Settings button while you are polling your rig (make sure your frequency updates and you turn your VFO).? Then start AC Log and click the Load settings button (at the left below the rig list).

?

Enjoy!

?

73, Scott

N3FJP

Hello and thanks for reading my message… I am trying to load and run the Meshsense App on a 64 bit AMD processor machine running a fully updated versions of Linux and an OS of Ubuntu Jammy Jellyfish. Using Firefox, on the N3FJP website, I click on the app download button and can successfully download (near as I can tell) the application installation package. The package downloads a file named “Meshsense-X86_64.AppImage” into a file folder named “library” When I double click on the appropriate icon within a couple of seconds I get an error message saying “failed to install file:not supported”. I am by no means even a competent Linux / Ubuntu user but to date have managed to get by because apps either worked well right away or I could search / ask for help.

When I search on the internet phrase “failed to install file:not supported” the hits and tips are many. Some such as … insufficient user levels (I have root user permission) and range to many rabbit holes which I have struggled to climb out of! I have tried many suggested command line uses to start and run the installation (apt, etc) but nadda.

I run all my other N3FJP programs on the Windows machine and they are great, just wanted to run Meshsense on my Linux machine. A search on the N3FJP website and here on Groups IO shows very little queries and banter re “Meshsense” so maybe I am totally in the wrong place? Can anyone please kindly assist me?

Thanks for the bandwidth use!

Tom L K3TWL

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

开云体育 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

开云体育 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

开云体育 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

开云体育 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

开云体育 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?

?

Perhaps not to your specific question ....

I often check LoTW's queue time after doing an upload.? Previously (months ago) the minimum queue delay would usually be just less than 60 seconds - unless it was right after a popular contest weekend which could introduce additional processing delays.? Over the past few months, the "typical" queue delay is now often only 30 seconds, or so.? I assume ARRL has added some computer processing muscle to the system for better response time.

?

But once in a while - in spite of showing a short queue time - the system for some reason takes longer to process my upload of new contacts.? When that happens, my subsequent "download" from LoTW will still not contain acknowledgement of the recent newly uploaded contacts.? At that point I've learned to simply ignore the delay and initiate another "download" later - usually the next day - when the system has completed processing my log.? So you may just want to try again at a later time.

?

Also remember, TQSL certificates must be renewed every 3 years.? Check to insure yours is still active:

?? Log into LoTW ; Click "Your Account" ; Click "Your Certificates" to see the valid date range at bottom of page.

After working flawlessly for years, today when I hit "All since 2024/11/22" in AClog's LoTW window, everything processed as usual, but the QSOs just processed weren't marked as "QSL Sent" nor were the ones already confirmed marked as "QSL received." I tried several times, and TQSL appears to be doing its thing, but the log isn't updated.

Yesterday I just passed 10,000 QSOs in my log, in case that makes a difference.

I know that LoTW has been discussed a lot here, but I couldn't find this particular issue in a quick archive search.
--

Mark D. Johns, K?JM
Minneapolis, MN EN35hd
-----------------------------------------------
"Heaven goes by favor; if it went by merit,
? ?you would stay out and your dog would go in."
? ? ?---Mark Twain