AirBourn post=70347 wrote: Running latest nightly (2021-04-21T23:50:23Z) on Ubuntu 20.04.2. Immediately on starting Ekos I get a dialog that says "INDI Driver indi_asi_ccd crashed. Restart it?" and it will cycle a couple of time (probably once for each ASI CCD device), and then show the INDI Control Panel without my ASI devices. I also see a message about the driver crash in the log. Latest Stable (3.5.2 I think) works fine on the machine. Related?
Here the Indi Driver files for your SestoSenso compiled on AMD64.
Let me know if they work for you.
Darren665 post=70371 wrote: Yep, I have no idea where the middle is,
when using the focus routine it doesn't give you any numbers, so you have no idea how far its moved,
I used to be able to set the focus position above 200,000
I've definately manually entered 1,000,000 on a earlier version of kstars
I've been using my scopes with Kstars for over a year without this focus limit problem
this is a new problem after the last Kstars Update
I suppose I could try and downgrade Kstars.
I'll google how to do it.
Thanks for the help everyone,
I'll update if I find a fix that works.
Anyone know how to edit/build/install INDI Drivers pinch.pngsmile.png
This seems to be set in the firmware of the focuser, just as in the MyFocuserPro code. Fortunately, that is open source, so I could edit it and reload it into the Arduino.
You may be able solve your problem by changing the procedure somewhat:
1, Remove Sesto Senso
2, Hand wind it all the way in clockwise,
3, hit calibrate as That's now Zero
4. Now set the focuser position to 100,000 (i.e. the middle between 0 and max travel)
5, re-fit Sesto Senso focuser ONTO TELESCOPE THAT ALREADY IS NEAR PERFECT FOCUS,
That should give you enough room (+/- 100,000 steps).
I had a similar problem with MyFocuserPro, which uses the MoonLite Indi Driver. Although the Control Panel allowed me to change the maximum position to 100,000, the actual focuser would not move past 10,000. I had to modify the actual Arduino code to change the maximal allowed value there. The change in the control panel was not translated into the Arduino code.
I don't know how the Sesto Senso focuser works, but it is possible that the maximal focus position is similarly set in its microcontroller. If the driver cannot modify that value, changing the value in the Control Panel may similarly have no effect in that case.
I don't know whether that is related, but I had repeated crashes while trying to build (not install) a brand new Kstars from the most recent master yesterday on a mini-PC with a stable Kstars installation from March 1. The build repeatedly crashed at the same point, saying there was a problem with a darklibrary file.
I don't recall exactly the name of that file, and I did not explore further since I had the stable Kstars version on the machine and I wanted to image, but reading this thread I am now wondering whether the issues are related. I can try to reproduce later tonight, if that is useful, and post the exact error message.
Jasem, please advise if you want me to do that.
airscott post=70239 wrote: Not a Pi. No config.txt. No "boot section"
Agreed! Just what I wrote as well.
Both work just fine.
My mini-PC is now almost 3 years old and I find the Pi4 is performing better.
But Ubuntu and Kstars work perfectly fine on both systems.
The problems come in with the different flavors of virtual desktops. I still think x11VNC is the simplest solution by far.
Working flawlessly for me for 2 years +.
We are turning around in circles here. All these problems have been solved many times over here on this forum.
It is usually a simple matter of just editing the config.txt file in the boot section of the Pi4.
Also, x11VNC works just fine. Couldn't be more straightforward.
Set the framebuffer to the size of your monitor in the config.txt file
set the hdmi_hotplug and the hdmi_mode (82 in my case for 1920x1080)
set x11vnc -storepasswd
add x11vnc -usepw -shared -forever to the Ubuntu Startup Items
That should do it.
Concur with Wouter here.
I am also using both systems, mini-PC as well as the 8 GB version of the RPi4 and I prefer the RPi4 BY FAR.
I run Ubuntu 20.04 on both systems and I do not concur with the VNC being laggy. I am using 5GHz connection to the Pi4, image transmission is near instantaneous, and the Pi4 is considerably faster than the mini-PC. 867 Mbps vs 433 Mbps.
That being said, both work for me, and once set up for the night, I don't care much about the mini-PC being more laggy on VNC. I just let it run and collect my frames in the morning.
You must be doing something wrong with your setup.
I fixed my crashes by 1) purging libasi, then 2) recompiling indi using 'git checkout dc02153a571281f613321df0cad912d5ae09480a' instead of 'git checkout master', i.e. going back in time to March 10 when everything still worked for me.
Not the cleanest method, but fast and after doing that my filter wheel, Moonlight focuser and cameras were back in action again.
I assume that reverted the ZWO SDK also, but I did not check.
Did you go back to a larger picture size again and ascertain that the crash still occurred?
Maybe the first instance was not surprising, the sensor of the ASI1600 measures only 4656 x 3520 pixels, so you added an extra 9312 pixels that are not addressed.