Please check out this thread from a month or so ago
indilib.org/forum/general/10604-kstars-m...driver.html?start=12
Read More...
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...
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.
Read More...
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)
Read More...
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.
Read More...
Rob, yes, you are correct, the .cu is the one to connect to!!!
Ron, attached is mac screen shot of nstep running
Note the selected port
Read More...
Hi Rob,
Ok, I can confirm that ekos on MAC for nStep is broken.
A port scan returns either (depending on the type of nStep)
/dev/cu.usbmodemXXX
or
/dev/cu.SLAB_USBtoUARTXXX
The first issue is there are two enumerations in /dev
/dev/tty.* and /dev/cu.*
The /dev/tty.* is the connection point
But even when I force set the port to /dev/tty type I get a yellow when pressing Connect but no errors display
I have tried the above with both enumerations (tty.USBMODEM and tty.SLAB_USBtoUART)
Now I believe the port scan is deep inside indi and not the particular nStep driver, how does INDI for other devices enumerate USB 'serial' tty ports on MAC? How is the CU scanned versus the TTY?
Also, how can the baud rate be selected for these types of devices?
For the nStep, the tty.usbmodem type takes just about anything but the SLAB enumeration requires 9600 baud.
Read More...
Hi Ron,
Be advised I am not a normal MAC user but I am an nStep'er they are my device, circuitboard/firmware and working with Jasem to get the INDI driver running a few years ago.
MAC should need nothing added to be able to see and be able to talk to the device as long as you version OSX supports USB CDC devices. It is not special like FTDI needing a low level driver.
Which version of the nStep? Small in a sleeve or box with buttons? With Wifi?
Does it show with an assigned port under port selector?
Do you see a /dev/tty.usbmodem* and /dev/cu.usbmodem* (on High Siera anyway).
Does it show up in 'About This Mac'->SystemReport->usb ?
You can try talking to it with something like Zterm (or other terminal app that can connect to a usb serial device).
Open ZTerm, select the device, hit a few ctrl-F's, should get an 'S' back for each hit.
Read More...
Hi Ron,
Which version of the nStep? Small in a sleeve or box with buttons? With Wifi?
Does it show with an assigned port under port selector?
Do you see a /dev/tty.usbmodem* and /dev/cu.usbmodem* (on High Siera anyway).
Does it show up in 'About This Mac'->SystemReport->usb ?
You can try talking to it with something like Zterm (or other terminal app that can connect to a usb serial device).
Open ZTerm, select the device, hit a few ctrl-F's, should get an 'S' back for each hit.
Read More...
Hi John,
The manual shows the option, now if removed for ARM Debian ???
www.openastroproject.org/documentation/o...e-1-5-0-user-manual/
Search for 'General' in the doc, the lowest radar button available in the page, right above the 'Display FPS' slider.
The text below the Settings description shows:
"Finally another option that may help on small displays, to split the controls off into a separate window that can be hidden behind the main preview window or minimised to get it out of the way."
Read More...
Hi John,
Does Settings->General->"Use separate window for controls"
Help any?
There are also these env variables used by QT
doc.qt.io/qt-5/highdpi.html
But me playing on Ubuntu, none of them made any differences on a high-dpi ubuntu laptop by changing the screen resolution to various values.
Read More...
The official PI 7 inch screen is not limited to its resolution.
In /boot/config.txt
add whatever frame buffer size you want to try
I use the following primarily because ccdciel has the same issues, cannot see all the screen.
framebuffer_width=1280
framebuffer_height=768
I do admit to having to use a handheld magnifier to enlarge some of the text in Skychart but 95%+ of all screen info is legible to be.
Read More...