Hi Jasem,

To be honest, nothing seems to be broken or need extra explanation beyond INDI port scan and choosing the correct port (/dev/cu.DEVICE) the device (for any driver that is a usb serial CDC type device) has enumerated on.

I can not explain what issues I had when I first DL'ed Kstars for MAC
I tried recreating them by moving Kstars.app to trash then deleting all vestiges I could find of preferences
/Users/USERNAME/Library/Application support/ anything with kstars
and
~/Library/Application Support/knotifications5/kstars.notifyrc
~/Library/Preferences/kstarsrc
~/Library/Preferences/kstars
~/Library/Caches/kstars

Then re-install Kstars
All looked clean, no vestiges of previous profiles and wizard was first thing offered

Chose CCD Sim and rigel nStep

The port was filled in correctly (i had only one type of USB CDC device attached) as expected and the 'Connect' just worked.

Now what I do see is if the device is entered manually (and wrong) and a 'Connect' is hit, I had reported seeing a 'Yellow' on the Connect.

Each and every time this happens seems to leave a hung process for the indi driver, e.g. I have all these hung processes (e.g. entering /dev/tty.DEVICE)

502 16962 1 0 Sat07AM ?? 0:00.02 indi_nstep_focus
502 17048 1 0 Sat08AM ?? 0:00.02 indi_nstep_focus
502 17100 1 0 Sat08AM ?? 0:00.02 indi_nstep_focus
502 17141 1 0 Sat08AM ?? 0:00.03 indi_nstep_focus
502 17157 1 0 Sat08AM ?? 0:00.03 indi_nstep_focus
502 17249 1 0 10:13AM ?? 0:00.03 indi_nstep_focus
502 17551 1 0 11:22AM ?? 0:00.03 indi_nstep_focus
502 17615 1 0 11:29AM ?? 0:00.03 indi_nstep_focus
502 17655 1 0 11:35AM ?? 0:00.03 indi_nstep_focus
502 17687 1 0 11:39AM ?? 0:00.03 indi_nstep_focus
502 17733 1 0 12:15PM ?? 0:00.03 indi_nstep_focus
502 17747 1 0 12:16PM ?? 0:00.03 indi_nstep_focus
502 18663 1 0 8:58AM ?? 0:00.03 indi_nstep_focus

Read More...