Added "newexposure" to ZWO config file

[EricClaeys]

No description provided.

[EricClaeys]

Hi Thomas, The dev branch still says it's 9 commits ahead and 1 behind the master branch.  It also said that last night when I did the PR, which is probably why it included more than just the one file I  changed. How do we fix it? Eric

[thomasjacquin]

@EricClaeys ,

Once I've merged dev into master, the easiest is probably to delete your local dev branch and pull the new one from the repo.

git stash     <-- Stash your changes if you have any outstanding code changes
git branch -D dev    <-- deletes your local dev branch
git fetch     <-- retrieves latest repo changes
git checkout dev      <-- select the dev branch
git pull      <-- pull the branch changes from the repo. This creates your new dev branch
git stash pop       <-- This brings back your changes onto the dev branch

Then you should be good to make new commits on the dev branch.

[bbillp]

I’m a bit confused about the all the recent updates because I’ve been out of town for 10 days, are all the 0.8 changes updated in github now ? Bill P.

…

Sent from my iPad

On Sep 2, 2021, at 11:25 AM, Thomas Jacquin ***@***.***> wrote:  @thomasjacquin approved this pull request. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[EricClaeys]

Bill,
what's in GitHub is a fix for people with version 0.8 that were getting the ASI_ERROR_TIMEOUTs. The fix allows you to turn off the "Version 0.8 Exposure" mode, which then uses the version 0.7 mode. All the other version 0.8 features are still active though.
If you use the GUI you'll want to update it as well as "allsky" since the GUI fix includes that new option - click on "Show Advanced Settings" at the bottom of the page, then look for "Version 0.8 Exposure".
If version 0.8 is currently working for you, you don't need this fix. Unfortunately using the version 0.7 exposure method results in a warmer camera.

[bbillp]

I use 2 SD cards one for 0.7 nightly and another for 0.8 tests and do not use the GUI interface yet. Should I reload 0.8 from scratch to pick up all the new changes ? 0.7 camera heat is my concern with the ASI178MC at gain 225. Thanks ….. Bill in Orange County California

…

Sent from my iPad

On Sep 2, 2021, at 1:33 PM, EricClaeys ***@***.***> wrote:  Bill, what's in GitHub is a fix for people with version 0.8 that were getting the ASI_ERROR_TIMEOUTs. The fix allows you to turn off the "Version 0.8 Exposure" mode, which then uses the version 0.7 mode. All the other version 0.8 features are still active though. If you use the GUI you'll want to update it as well as "allsky" since the GUI fix includes that new option - click on "Show Advanced Settings" at the bottom of the page, then look for "Version 0.8 Exposure". If version 0.8 is currently working for you, you don't need this fix. Unfortunately using the version 0.7 exposure method results in a warmer camera. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[EricClaeys]

Bill,
You can just download the changed files - capture.cpp, README.md, and settings_ZWO.json.repo. But if you're more comfortable downloading everything from scratch you can do that, too.
Note that disabling the 0.8 exposure mode (i.e., setting "newexposure" to 0) also disables the "cooler sensor" improvement in 0.8, but for people getting the ASI_ERROR_TIMEOUTs in 0.8, there's no way around that.