×

INDI Library v1.9.4 Released (17 Jan 2022)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

Kstars Mac - Rigel systems N-Step focus motor driver ??

  • Posts: 2578
  • Thank you received: 684
As for the other question about ports and port scanning, as I recall Jasem wrote that code a few years ago when we were working on getting a bunch of drivers to be easier to use so that it would find and list all the available ports and make them clickable buttons or drop down boxes, rather than the user having to type in the port’s path directly which was hard for most users.  I do not remember though exactly where that code was
The following user(s) said Thank You: Gene N
2 months 3 weeks ago #77084

Please Log in or Create an account to join the conversation.

  • Posts: 97
  • Thank you received: 16
Rob, yes, you are correct, the .cu is the one to connect to!!! Thank you!

Ron, attached is mac screen shot of nstep runningNote the selected port  

 
Last edit: 2 months 3 weeks ago by Gene N.
2 months 3 weeks ago #77087
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 1
I tried reply to your previous questions about the device, but am not seeing it posted... Anyway, The Mac system report shows it when connected to a USB 3 port: USB 3.0 Bus:

Host Controller Driver: AppleUSBXHCIPPT
PCI Device ID: 0x1e31
PCI Revision ID: 0x0004
PCI Vendor ID: 0x8086

USB Stepper Focus v0.1s :

Product ID: 0xfbb2
Vendor ID: 0x04d8 (Microchip Technology Inc.)
Version: 0.01
Serial Number: 00000000P3
Speed: Up to 12 Mb/sec
Manufacturer: Astrogene1000_stuff
Location ID: 0x14100000 / 31
Current Available (mA): 500
Current Required (mA): 240
Extra Operating Current (mA): 0






However, EKOS shows a failed to connect message.

2021-10-30T18:59:09: [ERROR] Failed to connect to port (/dev/cu.usbserial). Error: Port failure Error: No such file or directory. Check if device is connected to this port.
2 months 3 weeks ago #77097

Please Log in or Create an account to join the conversation.

  • Posts: 97
  • Thank you received: 16
Ron,

See the message "Could not connect to /dev/cu.usbserial"

In the INDI control panel for the nStep you need to select the correct port or force set it
In a terminal window, do a
ls -ltr /dev/*usb*

You shoudl see something like
/dev/cu.usbmodemXXX
/dev/tty.usbmodemXXX

See the image of my control panel above, notice the row with the Ports on it

Copy the text of the file name (e.g. /dev/cu.usbmodem621) shown for the cu device and open your control panel, paste the device name into the right field of the Ports and do a 'Set'
Then on the Option tab of the control panel, do a Save
Then try your connect.
2 months 3 weeks ago #77098

Please Log in or Create an account to join the conversation.

  • Posts: 2578
  • Thank you received: 684
Maybe we could get some of this good information onto this page

indilib.org/focusers/rigel-systems-nstep.html

to help other users in the future and to avoid confusion.  If you know how we could change the text to more clearly help beginners to this driver, please let us know
2 months 3 weeks ago #77099

Please Log in or Create an account to join the conversation.

  • Posts: 97
  • Thank you received: 16
Hi Rob,

This, to me, is just INDI configuration and not nStep related.

I assume all devices use the underlying INDI port/device selector when dealing with 'serial' interfaces.

I have the same issue on a PI for the Celestron Nexstar device selection.. If I have the Celestron connected at power on or not previously connected after power on I see a
/dev/usbmodem0
If I unplug/replug the Celestron I then see it enumerate on /dev/usbmodem1 (a different /dev entry)
2 months 3 weeks ago #77100

Please Log in or Create an account to join the conversation.

  • Posts: 2578
  • Thank you received: 684
Yes, you are correct that this issue could affect users of multiple drivers, but if both of you were confused as to which ports to connect to for the devices tty vs cu, you can be sure others might be as well.  So perhaps a paragraph can be written for all drivers that might have this port issue and maybe copy it to all the driver explanation pages?  or maybe make one page with the information for all of those drivers explaining it?
2 months 3 weeks ago #77102

Please Log in or Create an account to join the conversation.

  • Posts: 97
  • Thank you received: 16
Hi Rob,

Agreed! It is a longer learning curve!

I had to dust off my MAC, last time used was year+ ago and never for INDI.
I had been involved with Craig S back in the PHD0 MAC days with the nStep, but that was back in 2012 or so when I did MAC work for the nStep.

It was two choices to try, cu or tty and a web search cleared up MAC use of each.
2 months 3 weeks ago #77103

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 1
Got it connected! Its not quite the steps in your post, as it gave me a yellow 'light' and then no connection. I tried scan ports and I think that did it but when fiddling with the settings I'm not exactly sure. Attached is a screen-shot of the settings and messages when it worked. thanks for your work. HTH some others per your discussions with Rob. Clear skies, and maybe a big aurora tonite! -although I have lots of clouds.
/Users/ursamajor_1/Desktop/Screen Shot 2021-10-30 at 9.21.46 PM.png
2 months 3 weeks ago #77108

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 1
trying jpeg for the screen shot of INDI window:

/Users/ursamajor_1/Desktop/Screen Shot 2021-10-30 at 9.21.46 PM.jpg
2 months 3 weeks ago #77109

Please Log in or Create an account to join the conversation.

Thanks folks! What information do we need to add to the documentation to make this easier for future users? can someone summarize this in a paragraph or two so we can add it to the documentation?
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
2 months 3 weeks ago #77111

Please Log in or Create an account to join the conversation.

  • Posts: 97
  • Thank you received: 16
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
2 months 3 weeks ago #77128

Please Log in or Create an account to join the conversation.

Time to create page: 0.932 seconds