154 replies to this topic

[drcbweaver]

And one more suggestion. How about an option to toss a frame taken during a dither based on feedback from the phones accelerometer?

 

I am using my phone mounted to a Sky Watcher Star Adventurer Mini and have dithering enabled. Since there is no communication between the phone and the SAM, I get quite a few frames in which it dithered during the exposure.

 

I believe this app already has access to the phones motions sensors for the "Non Tracking Dynamic" feature. How about a setting that would allow us to toss a frame that was being taken when it sensed a dither? I would envision this next to the "Save all frames" setting. Something like a "discard frames if motion exceeds x" option.

[artik]

And one more suggestion. How about an option to toss a frame taken during a dither based on feedback from the phones accelerometer?

 

I am using my phone mounted to a Sky Watcher Star Adventurer Mini and have dithering enabled. Since there is no communication between the phone and the SAM, I get quite a few frames in which it dithered during the exposure.

 

I believe this app already has access to the phones motions sensors for the "Non Tracking Dynamic" feature. How about a setting that would allow us to toss a frame that was being taken when it sensed a dither? I would envision this next to the "Save all frames" setting. Something like a "discard frames if motion exceeds x" option.

No I don't use phone sensors to detect movement - in fact the Android specific part is quite small most of the stuff runs on Linux as well. I observe the picture and if the image ins't going by straight line as suppose to do on non-tracking imaging - I restart stacking and wait for image movement to sattle.

 

Regarding dithering - since OLS communicates now with mount via built-in it is something possible to implement - just don't have spare time to do it right now.

[artik]

It refuses to use my calibration frames, 

What do you mean? What error message do you get?

[artik]

Version 40 of OpenLiveStacker was released to google play and on github:

 

TL;DR

 

Major fixes in dynamic-non-tracking mode, fixes in skywatcherAltAz driver so it works properly with az gti, workaround in use of SynScan Driver 

 

Full changelog

 

 

• Fixed major issue with dynamic-non tracking mode that created improper registration and failure to track (implemented in 39 but wasn't officially released)
• Fixed several issues with indi (all the fixed are already merged back into the official indi tree):
  • Fixed bug in timeout handling in core indi library
  • Major improvements in skywatcherAltAz driver
    • Fixed track rate update to make sure it never changes direction - that lead to a poor and unstable tracking and sometimes mount runaway
    • Fixed communication timeout to reasonable values of 300ms to prevent mount run away and potential equipment collision in case of UDP packet loss
    • Added approach to target from the same direction similar to what SynScan App does for improved goto/sync accuracy
• fixed issue with non-standard properties of synscan driver - now it is possible to use it together with SynScan App for controlling mounts
• Encoders are now disabled by default with skywatcherAltAz drvier

 

For AZ GTi and SynScan Pro app users

 

1st of all if you use az gti in alt-az mode the driver is vastly improved.

And additional option is now to use SynScan Pro app together with OpenLiveStacker - you can connect to the synscan app on address via tcp/127.0.0.1:11882 and talk to SynScan app rather than the mount itself.

Advantage: official app and drvier caviats: you need to have an alignent on at least one star and there are still some error message shown by synscan drvier that can be safely ignored.

[artik]

Hello, a new version v41 was released: https://github.com/a...ases/tag/beta41

 

Android highlights

• Added support of remote indi camera - so you now can run your indi server/ekos on remote device and stack images on tablet
• Redesigned driver selection menu
• Added celestron_gps and celestring_aux drivers to indi package
• Fixes in libuvc - retry setting interface alt setting, prevent -99 error for svbony 105 cameras

Linux : linux specific manual: https://github.com/a...ning-the-app-ui

• An installation package is provided for x86_64 architecture, just untar package and run bin/ols_gui - it would open a startup GUI to run OLS. It would also add a menu entry on the first startup
  
  Note the package contains all dependencies needed except for Indi server and Indigo - to use them install them using official manuals
   
• A new GUI for configuring OLS and starting it was added, it provides following options:
  
  
  • Selection of a driver
  • Configuration of indi/indigo drivers/server start prior to running OLS
  • Configuration of data directory, default is ~/OpenLiveStacker
  • Other options
• All logs now stored in data directory
• Some indi/indigo camera driver improvements

 

And here is the set of different setups you can run OLS with:

 

 

 

 

Edited by artik, 03 May 2025 - 04:44 PM.