Finally to confirm - connected up the NEQ6, ATIK 383L+, ATIK Titan, and my own robofocuser (arduino) and it all seems to work nicely - tracking and slewing works. I'm using the indiserver in a local remote form so I can run a 32bit indi_atik_ccd driver on the 64bit build.
Only issue is I can't see on the bleeding edge build where the guider is (compared to previously). Maybe the system hasn't matched the guider "ATIK Titan CCD" (or my description).
Finally switched from the VM to a native Ubuntu MATE 16 LTS on my Lenovo W510. First thing I noticed I cannot maximize the ekos window, which was possible in the VM. Also I'd like to move the ekos window on the second virtual screen. Can you fix this?
Yup it's a little convoluted if you want the bleeding edge due to the dependencies -the main thing is the KDE development framework that is massive but sorts out the nasty one that you can't find anywhere by using apt searches. Then it's a case of pulling the apt based dependencies.
Then it's a case of compiling for 64bit - just do what you'd do normally.. although the asicam will fail as there's no v8 binary.. so you'll need to tell the build to ignore that in the build sequence.
Probably worth building cfitsio (source from nasa) and then using that for the dependency as the standard repo is based around 32bit ARM..
If you want the standard build then use 32 bit with the standard apt repo packages and if you need the atik drivers, get those but use a symbolic link to solve the issue where it's not found.. or use LD_LIBRARY_PATH additions to find the right architecture libcfitsio shared library.
You will find that the astrometry.net scripts have a problem with 64bit ... because they use python and dynamic typing on the read of the FITS file... so the result is that the system attempts to create different types to what the code is... that's bad programming by the developers. Switching to png works without a problem.
I now have a fully functioning system - including focusing etc.. .. all on the C2. I have a 16GB eMMC card for the main system (including the packages)..and a 128GB SSD to hold the 32GB of astrometry.net indices..
Without hi-jacking this thread... how did you get the Atik Titan to work on an Odroid please?
I have the C1 and it is not working at all... I see you have a C2, please share the magic on how to get the Titan to work
Kstars Mac osx
Odroid C4 / WO Redcat51 / CEM25p / ZWO533MC / QHY5L-II-M (OAG)
Hi Gonzo, it's been a while and I've been pulled away but I will be firing the system backup ahead of the SGL star party. I can't sort that in the next week due to work priorities :/ From memory I recompiled the sources into 64bit and use a rebuild/symbolic link as per the previous post with the latest driver (that did work with the titan) at the time. I do use a powered hub (it's fed off a step down and can provide the titan with the current it really needs - it's fed off the USB rather than plug in power).