Yoddha

 APT DC is updated to 1.8. Fixes the calculations in the Daylight Saving period.

APT DC was updated to version 1.7

2019/01/02 - v1.7 Upgrade
-Added support for Android 9
-Added better location coordinates detecting
-Updated design

More info and links at: https://www.ideiki.com/astro/MobileApps.aspx

Many thanks! You are welcome anytime

Interesting idea! We will explore it for the desktop application first

12 hours ago, Stub Mandrel said:

I hate to say this but... it doesn't do very much does it? I get the same from Clear Outside app and that tells me the weather as well.

Hi Neil,

It is matter of taste I prefer to use other forecast and this app fits my needs to check if particular night has enough time for imaging

Also it was fun to build it (in fact my wife made the Android version, I built the iOS). It is absolutely free - no ads, no tracking or marketing data gathering. If it is useful for somebody - great! If it is not - nothing bad is happening It is a gift for the community - wanted or unwanted

BTW I also use it for a fast way to see my GPS coordinates  

12 hours ago, happy-kat said:

Hi, I'm having trouble with the app on both my devices. I've got a saved location set up on both and attempt to switch to it and what ever I try, refresh, save and calc etc, my DSD times are N/A. The app is up to date, and have tried with location services on or off.

6.1 and 4.3

Anything you can suggest I try please?

Hello,

The Moon is big now and there is no absolute darkness... Could you try to change the date using Prev/Next or by tapping on the date?

It has iOS version too The Android version was released first and that is the reason to have two topic here...

APT DC was just updated

2018/08/05 - v1.6 Upgrade
-Added better location coordinates detecting

More info and links at: https://www.ideiki.com/astro/MobileApps.aspx

APT DC was updated to 1.5 and now supports Androids back to 4.0.3 (Ice Cream Sandwich)

Hello,

The iOS version in final tests phase

Many thanks David!

Hi Frank,

Thank you for the feedback!

A full port of APT to mobile platform is not possible, however some alternatives are considered in a bit longer term

Many thanks!

All times are local. APT DC takes the time zone from the phone.

What is Full ADT? The DSD is taking into account the Moon...

Hi David,

Could you make a screenshot (usually by holding Power and Volume Down buttons pressed in same time) and take a look which version of Android is running on your A5?

Hi David,

Many thanks! We will try to make a simulation for A5. On the test Moto here it is working!?!? Does it behaves same for all 3 locations? ( Just to exclude copy-paste error ) 

Cheers! You are getting virtual beer

Please share feedback! 

Hello, 

We have just released our first mobile app - APT Darkness Clock (APT DC) which allow to calculate the Deep Sky Darkness (DSD) time for selected night.

For link and QR code take a look here:

https://www.ideiki.com/astro/MobileApps.aspx

 Or navigate directly here:

https://play.google.com/store/apps/details?id=eu.distinct_solutions.aptcalc

Hope you will find the app useful

David, take a look on the LiveView parameters in the camera menu. If Face detection is enabled then there is no Zoom

Don't get me wrong I don't say that there is no need to implement the compensation in the controller/driver... Just if the imaging application is capable I would use it...

BTW keep in mind that optics are inert and react relatively slow to the temperature changes. Wind gust will give rapid changes of the temperature reading, but this doesn't mean that focus is changing. A good approach is to average the readings for certain period and then to decide if there is need to change the focus

Thanks Mick!

As I know all focusers that has temperature sensor are offering in driver/controller temperature compensation, but my opinion is that the right place is in the imaging application, because the action can be made between the exposures

Is it the whole EEPROM that will fail or just the memory addresses I am using?

Just the memory address you will use will fail

There is one more approach.

On address PosOffset in the EEPROM are reserved 2 bytes. They keep the memory address where the position is stored. So when you need to store the position it uses the address, writes the value, then reads it back and if it is no the same, then increase the address PosOffset with two more bytes and start to use a new cell

Here is my code:

void WritePosition(unsigned int Value)
{
    unsigned int Address = ReadTwoBytes(PosOffset);   
    WriteTwoBytes(Address, Value);   
   
    if(Value != ReadTwoBytes(Address))
    {
        WriteTwoBytes(PosOffset, Address+2);
        WriteTwoBytes(Address, Value);
    }
}

So It is important to place the first PosOffset to point after all other stored variables in order to be able to use the rest of the EEPROM. Also you can increase the life of the cells by using timer that is started on button press and when the button is released to store the position just once

Many thanks Gina!