×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Sesto Senso 2 connect issue

3 months 3 weeks ago
Mel
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
Sesto Senso 2 connect issue #52141
Hi all

I just purchased a Sesto Senso 2 autofocuser. I reviewed a lengthy thread detailing the development process of the driver and to my knowledge version 1.4 (which I have) should support it - although it was not mentioned in the original thread if this was for the first or second gen of the SS focuser.

Upon connecting to the Pi I saw in dmesg that some other process (pps) was picking up the port:
[   11.052246] pps pps0: new PPS source usbserial1
[   11.052377] pps pps0: source "/dev/ttyUSB1" added

In INDI, seemed as though the port was not available and reported that some other process was using the port - I assumed this was due to the above message and did some searching. I found a couple of threads suggesting that gpsd could be grabbing the port (seems pps is a timing service). I tried killing gpsd with:
sudo killall gpsd

dmesg reports:
[ 1106.059726] pps pps0: removed

Thinking I was onto a winner I then go ahead and test the connection using a profile with CCD simulator, Guide Simulator, Telescope Simulator and the Sesto.
indiserver -p 7624 -m 100 -l .indi/logs -vv -f /tmp/indiFIFO indi_sestosenso_focus indi_simulator_ccd indi_simulator_guide indi_simulator_telescope

I am still getting the same error - actually I just checked and the error is slightly different with gpsd disabled: Previously the error stated the port was in use, now it says:
2020-04-18T20:45:29: [WARNING] Communication with /dev/ttyUSB1 @ 9600 failed. Starting Auto Search... 
2020-04-18T20:45:29: [INFO] Error retrieving data from SestoSenso, please ensure SestoSenso controller is powered and the port is correct. 
2020-04-18T20:45:29: [ERROR] Serial read error: Timeout error.

I went further and fully disabled gpsd by editing /etc/default/gpsd as below:
# Default settings for the gpsd init script and the hotplug wrapper.

# Start the gpsd daemon automatically at boot time
START_DAEMON="false"

# Use USB hotplugging to add new USB devices automatically to the daemon
USBAUTO="false"

# Devices gpsd should collect to at boot time.
# They need to be read/writeable, either by user gpsd or the group dialout.
DEVICES=""

# Other options you want to pass to gpsd
GPSD_OPTIONS="-n"

Reboot, check dmesg - pps is still not grabbing the port - retest - same result. I don't know how to find out which process, if any, might be holding the port, or whether the hardware is just not answering as is suggested in the logs attached. What about the name of the hardware - could it be reporting itself differently (being 2nd gen) and being ignored? I'm sure there might be others using 2nd Gen Sesto Senso and I'd like to hear from you please?

Also is there a better way to test the drivers standalone? I thought I read somewhere of a way to start the drivers up in a standalone configuration for testing but I could not find the resource. I am connecting from a Mac client and set the logging up to the highest (bearable) level both on the server (-vv) and the client. Both logs are attached showing the commands being sent and no response. For this test the device was connected to ttyUSB1 and that's the setting that I started the connection with although EKOS hunts the other available ports.
[    4.735511] usb 1-1.3.1.2: cp210x converter now attached to ttyUSB1

I did connect to a windows machine and ran through the calibration (and updated the firmware) - the hardware is functioning as expected on Windoze.

Sorry for the long post - there's alot of information here - I do hope someone can help!

Cheers
Iain
Attachments:
The following user(s) said Thank You lantictac

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

3 months 3 weeks ago 3 months 3 weeks ago by ouioui01.
ouioui01
Junior Boarder
Junior Boarder
Posts: 29
More
Sesto Senso 2 connect issue #52142
Hi Mel,
are you using this new driver ?

github.com/indilib/indi/pull/1111

Cheers

----
ES ED 127mm FCD100, AZEQ6 GT, FocusLynx ESX25, Nikon D800 full modded / D5300, ASI120mm-s for guiding, Polemaster
-- RPi4 8Gb Stellarmate 1.5.3, Windows 10 Pro, Kstars/Ekos/Indi/PHD2/VNC

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

3 months 3 weeks ago 3 months 3 weeks ago by Mel.
Mel
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
Sesto Senso 2 connect issue #52143
Hi

No, not yet - I see it was added very recently - now do I have to pull the whole indi distribution for nightly builds to get this or can I selectively pull just the driver and edit the INDI driver XML config file? I'll have a look around for some instructions on this as well.

Thanks for the quick reply! That looks like the issue.

Cheers
Iain

EDIT - I'm running INDI on a Pi4 - is there a nightly build for Raspbian?

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

3 months 3 weeks ago
Mel
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
Sesto Senso 2 connect issue #52144
Thanks - I got a working version of the SestoSenso2 driver now. The limiting factor for me at the moment appears to be my knowledge of the Linux build/distro system. I tried to pull master for the git repo indilib:

git clone github.com/indilib/indi.git --depth=1

I was getting wierd curl errors without the --depth=1 param - probably because I am running the pi on a sketchy wifi link. Once I got the source I could compile/install fine but indiserver would just die on launch.

astroberry@astroberry:~/Projects/master/build/indi $ indiserver -p 7624 -l .indi/logs -vvv -f /tmp/indiFIFO
2020-04-18T22:53:20: startup: indiserver -p 7624 -l .indi/logs -vvv -f /tmp/indiFIFO
2020-04-18T22:53:20: listening to port 7624 on fd 3
Killed

Eventually I resorted to updating the astroberry distribution via apt-get:

sudo apt update
sudo apt install libindi1 indi-bin
ls -latr /usr/bin/indi_sestosenso2_focus
-rwxr-xr-x 1 root root 42504 Mar 7 16:00 /usr/bin/indi_sestosenso2_focus

Obviously this is quite an old version and I think I probably lost the fixes that Jasem applied for the trutech wheel recently. I would really have liked to have just installed the sestosenso2 driver.

Why couldn't I build / install from the git sources I wonder? There was no log for the crashed indiserver.

Anyway at least now I know there is a driver for my focuser that works - I confirmed by running the calibration just now. Will see how it performs once fitted to the scope - I noticed it seemed to home itself on disconnect.

Thanks!

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

3 months 3 weeks ago 3 months 3 weeks ago by ouioui01.
ouioui01
Junior Boarder
Junior Boarder
Posts: 29
More
Sesto Senso 2 connect issue #52148
Hi,

I didn't install it for the moment, cause I'm waiting the focuser...delayed due the situation.
Maybe Piotr (who made the driver) could help you !
Maybe there are commands to update indi-core and indi drivers directly without building it from git...

Stay safe and clear skies

ouioui01

----
ES ED 127mm FCD100, AZEQ6 GT, FocusLynx ESX25, Nikon D800 full modded / D5300, ASI120mm-s for guiding, Polemaster
-- RPi4 8Gb Stellarmate 1.5.3, Windows 10 Pro, Kstars/Ekos/Indi/PHD2/VNC
The following user(s) said Thank You Mel

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

3 months 3 weeks ago
Mel
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
Sesto Senso 2 connect issue #52151
Thanks OuiOui!

If it’s any help First Light Optics have them in stock and got mine to me in 2 days via DHL. I paid £6 for UK shipping which is their base charge.

Cheers
Iain

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

3 months 2 weeks ago
lantictac
Fresh Boarder
Fresh Boarder
Posts: 1
More
Sesto Senso 2 connect issue #52571
Firstly, thanks to Iain for providing some valuable clues with the Sesto Senso 2 driver configuration. I was testing on a Pi 3 with an Astroberry install and the latest build of KStars & INDI.

After a lot of hours I've finally got the Sesto Senso 2 connecting reliably and setup a persistent serial port mapping. This is what I found:

1. gpsd was determined to own the Sesto Senso 2 /dev/ttyUSB# device. I initially tried to prevent gpsd from intercepting the port by editing /lib/udev/rules.d/60-gpsd.rules but the attempt was unsuccessful. In the end I just disabled gpsd by editing /etc/default/gpsd (as per Iain's suggestion). I'm sure there's a better solution but for now it works for my needs.

2. I wanted to map the Sesto Senso 2 /dev/ttyUSB# device to /dev/sestosenso2 but INDI would fail to connect when I tried:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="insert_your_serial_here", MODE="0666", SYMLINK+="sestosenso2"

It turns out /dev/sestosenso2 would end up pointing at a /dev/gpiochip# rather than the desired /dev/ttyUSB#...

After a lot of different approaches I discovered I could get it to point at the correct Sesto Senso 2 /dev/ttyUSB# using:
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="insert_your_serial_here", MODE="0666", SYMLINK+="sestosenso2"

Hopefully that helps someone else out there!

Cheers,
Will.

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

3 months 2 weeks ago
Mel
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
Sesto Senso 2 connect issue #52601
Glad to be of service! I haven’t tried naming my port connections but it’s on my list so that will definitely be helpful. For the moment I am still having to ‘dmesg | grep ttyUSB’ after every reboot!

Cheers
Iain

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

3 months 5 days ago
toticdqs
Fresh Boarder
Fresh Boarder
Posts: 8
More
Sesto Senso 2 connect issue #53428
Hi all! just received the sesto senso 2, but is not connecting on kstars 3.4.3 on an osX computer.

2020-05-08T16:36:50: [INFO] Debug is enabled.
2020-05-08T16:36:49: [ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.
2020-05-08T16:36:49: [INFO] Trying connecting to /dev/cu.Bluetooth-Incoming-Port @ 115200 ...
2020-05-08T16:36:48: [WARNING] Communication with /dev/cu.usbserial @ 115200 failed. Starting Auto Search...
2020-05-08T16:36:48: [ERROR] Failed to connect to port (/dev/cu.usbserial). Error: Port failure Error: Resource busy. Check if device is connected to this port.

any ideas?

thanks!

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

2 months 2 days ago 2 months 2 days ago by toticdqs.
toticdqs
Fresh Boarder
Fresh Boarder
Posts: 8
More
Sesto Senso 2 connect issue #55368
For any others have this issue, I can connect to the sesto senso 2 after install this driver, on osx 10.14.6:

www.silabs.com/products/development-tool...t-bridge-vcp-drivers

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

2 months 1 day ago
toticdqs
Fresh Boarder
Fresh Boarder
Posts: 8
More
Sesto Senso 2 connect issue #55461
on osx high sierra 10.13.6, kstars crashes when trying to connect to senso 2:

Process: kstars [1594]
Path: /Applications/KStars.app/Contents/MacOS/kstars
Identifier: ???
Version: 3.4.2 (3.4.2)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: kstars [1594]
User ID: 501

Date/Time: 2020-06-12 19:06:08.025 +0200
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Anonymous UUID: 78AA750A-47EC-FF60-7CDC-E9AF4F34CF4D


Time Awake Since Boot: 1600 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000001
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x1:
-->
__TEXT 00000001025de000-0000000103110000 [ 11.2M] r-x/r-x SM=COW /Applications/KStars.app/Contents/MacOS/kstars

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 0x0000000102eec420 INDI::BaseDevice::getRawProperty(char const*, INDI_PROPERTY_TYPE) + 64
1 0x000000010272cbe3 0x1025de000 + 1371107
2 org.qt-project.QtCore 0x00000001058c0552 0x1056a0000 + 2229586
3 0x000000010269bc6f 0x1025de000 + 777327
4 0x00000001026a86cd 0x1025de000 + 829133
5 org.qt-project.QtCore 0x00000001058b8c4d QObject::event(QEvent*) + 957
6 org.qt-project.QtWidgets 0x00000001049c0b5d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
7 org.qt-project.QtWidgets 0x00000001049c1f95 QApplication::notify(QObject*, QEvent*) + 581
8 org.qt-project.QtCore 0x000000010588e804 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
9 org.qt-project.QtCore 0x000000010588f8b3 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 691
10 libqcocoa.dylib 0x0000000108a30052 QCocoaEventDispatcherPrivate::processPostedEvents() + 322 (qcocoaeventdispatcher.mm:888)
11 libqcocoa.dylib 0x0000000108a30758 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 40
12 com.apple.CoreFoundation 0x00007fff2f421d31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
13 com.apple.CoreFoundation 0x00007fff2f4d960c __CFRunLoopDoSource0 + 108
14 com.apple.CoreFoundation 0x00007fff2f404d3c __CFRunLoopDoSources0 + 300
15 com.apple.CoreFoundation 0x00007fff2f40415d __CFRunLoopRun + 1293
16 com.apple.CoreFoundation 0x00007fff2f4039b7 CFRunLoopRunSpecific + 487
17 com.apple.HIToolbox 0x00007fff2e6e3d96 RunCurrentEventLoopInMode + 286
18 com.apple.HIToolbox 0x00007fff2e6e3a0f ReceiveNextEventCommon + 366
19 com.apple.HIToolbox 0x00007fff2e6e3884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
20 com.apple.AppKit 0x00007fff2c994a73 _DPSNextEvent + 2085
21 com.apple.AppKit 0x00007fff2d12ae34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
22 com.apple.AppKit 0x00007fff2c989885 -[NSApplication run] + 764
23 libqcocoa.dylib 0x0000000108a2f5c8 QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2648 (qcocoaeventdispatcher.mm:430)
24 org.qt-project.QtCore 0x000000010588a97f QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 431
25 org.qt-project.QtCore 0x000000010588ee52 QCoreApplication::exec() + 130
26 0x00000001025f2a63 0x1025de000 + 84579
27 libdyld.dylib 0x00007fff5731a015 start + 1

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

1 month 1 week ago
Cliff
Fresh Boarder
Fresh Boarder
Posts: 6
More
Sesto Senso 2 connect issue #56487
I just found this information thanks for sharing , I am also having issues getting my Sesto Senso 2 working with either my Stellarmate or my Mac my mac is on the latest 10.15.5 though

The driver installed successfully but the focuser is still not connecting in kstars.

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

Time to create page: 0.632 seconds