Andrea,

well, no, it is just me closing it.
may be something in the sequence?
power up-connect usb-start APCC- start NINA-connect telescope in NINA
disconnect telescope NINA-close NINA-shutdown APCC- disconnect USB-power mount off

I don't have the mount with me now.
I've just opened APCC to check a few things and discovered the new COMs.
Now I reverted to COM21-22 .
Will check again with the mount

All I can say for sure is that on normal exit, APCC will close and destroy any virtual COM ports it created.

Some applications use brute-force methods to close applications by killing them and that will leave the virtual ports allocated.

-Ray

Hi Andrea,

APCC should close its virtual COM ports when it closes.

The only way this wouldn't happen is if something is "killing" the APCC task.

So, is it possible that APCC is getting "killed"?

-Ray

Hello, 
I am writing to check if what I see in my system is what is expected/correct:

-I create the virtual ports as specified, for example COM21, COM 22
-then configure the primary port to a physical COM3

Everything works as expected. closing/opening APCC doesn't change anything till I leave the mount attached to USB.

But, if I disconnect the mount and usb cable and launch APPC again (which happens if need to make some trials at home):

-new virtual ports are created (COM3, COM4) automatically
-virtual ports COM 21, COM22 are not anymore possible as virtual port in the drop down menu
-COM21, COM22 are listed under "device manager", "Ports", "Eltima drivers"
-deleting the COM21/22 from here does free them in APCC and they can be configured again

my questions:
-is this the correct behavior?
-shall I remove the flag "create virtual ports first" as soon as they are created the first time?

Thank you
Andrea