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!

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

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

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:

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:

Hopefully that helps someone else out there!

Cheers,
Will.

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

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!

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

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

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.

Every time I try to connect, kstars crash with my previous reported log, so I'm unable to use the sesto senso 2 focuser with kstars. Anyone else with this issue?

If KStars is crashing in Linux, then please install ekosdebugger and post the logs from it.

I have most of it working except the RPI3 with Stellarmate , I tried the following which someone posted here earlier,

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

Shows it is there but doesn't connect

I tried my Ascom IntelNUC worked first go so the Seno 2 was ok.

Tried my RPI4 Stellarmate and it already had the Senso 2 driver I thought the 3 and 4 had the same version ?

Could connect using ccdciel but not Kstars on my Mac, until I renamed the device from Sesto Senso to Sesto Senso 2 in the EKOS profile editor.

Now it works with Kstars . Now if Kstars only didn't crash while capturing images, I use Ccdciel instead for capture.

Now to figure out the RPI3 issue.

Hope this is of some help
Cliff