OK all done.
Just checking that you don't want me to create a clone as per the INDI repo instructions.
I have an error code on a Cmake . Here is the last part of the terminal code
mike@mike-pi:~$ mkdir -p ~/Projects
mike@mike-pi:~$ cd ~/Projects
mike@mike-pi:~/Projects$ mkdir -p ~/Projects/build/indi-core
mike@mike-pi:~/Projects$ cd ~/Projects/build/indi-core
mike@mike-pi:~/Projects/build/indi-core$ cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi
CMake Error: The source directory "/home/mike/Projects/indi" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
mike@mike-pi:~/Projects/build/indi-core$ make -j4
Is this OK to proceed
I have not entered the sudo make install
So if the above is OK. We are ready for the next step
Happy to give it a go. Once I have got up to speed I will get back to you.
In a word "no" but happy to learn. Any tips where I can upskill? I will start with GIThub?
Crazy busy at work but can look at this as a replacement for gym, socialising, pub life, going out for meals etc, etc, etc.
I appreciate the pointers in the error log.
I did a bit more troubleshooting and it appears that the settings for Park 2 and Park 3 are the same. So when when manually set in the Park 3 position it still thinks that it is in the Park 2 position and this is shown on the sky chart. To my simplistic view it would be a matter of resetting the mount co-ordinates for Park 3 to the proper AP Park 3 which is weights down and Dec 90 deg. All the other Park positions work perfectly as described by the Astrophysics manual (1,2 and 4).
Hope that this is of some help
No hurry here. I appreciate the help.
As you say previously this is what happened
bring the mount manually to Park 3 position (only for the first time, e.g. a cold start)
slew with INDI the mount and it goes to the correct position, the star is "on the" crosshair (more or less)
park the mount again with INDI and it reaches HA = +/- 6 hours but Dec = 0 degree
unpark it again and slew it with INDI and the final position is correct again
park it again with the same result as in step 3
Now however when the mount is set at AP Park 3 it shows the position on start up to be the HA = +/- 6 hours but Dec = 0 degree position
Despite switching off for a while I cannot get it to work as per the cold start described above. So bearing this in mind the following described the debug log attached
Mount is in the HA = +/- 6 hours but Dec = 0 degree position on start up.
Kstars is started and the astrophysics profile started.
Indi popup starts
I open up the astrophysics mount tab and connect (setting the "last parked" does not seem to make a difference so it is set to "Last parked" position
The mount position appears on the Star Chart to be correct for the HA = +/- 6 hours but Dec = 0 degree position
To confirm it knows where it is I do a load and slew of an image of miaplacidus and using astrometry.net this solves and slews to miaplacidus on the star chart.
I press park (set to AP Park 3 position) but the mount parks at the HA = +/- 6 hours but Dec = 0 degree position rather than the 90 deg dec position
The indi driver is indi_lx200ap_experimental
The mount driver is VCP4-P01-11
Let me know if there is anything you need me to try
File Attachment:File Name: log_15-21-59.txt
File Size: 540 KB
Finally managed to get the mount set up indoors as the weather is still awful. So I am in Australia in Brisbane. The setup is AP1100 with GTPO CP4 controller. I am using a standard RPi 3b with latest version of KStars and Ubuntu Mate 18.04. I am using astrometry.net offline as solver. I test using a load and slew protocol usually pointing to somewhere not too far from the pole like miaplacidus or acrux.
The mount is parked at the standard AP Park 3 (Dec is at 90.00). The driver is set to unpark from last parked position and to park to Park 3.
The good news is that when the scope is started it knows where it is and will slew to the correct position. However when set to park it goes to the correct position on Azimuth but still goes to 00.00 Dec which means that the scope is at 90degrees in dec to the proper AP Park 3.
When parked in this position and asked to slew again it knows where it is but always parks to 00.00 in Dec.
As I said before this is not a problem in practice. I set up in this Dec 00.00 position and everything works fine.
So I don't have any complaints, it is just that I suppose for completeness, when set to park at park three it should be the AP Park 3.
Let me know if you want me to do anything else or send in logs. I will leave the scope set up and see if we can sort it out if you have the time.
It is still a great driver. Thanks for the work that you have done!
I appreciate the work that has gone into the driver. I will get back to you once I have put it on the test bed and I will get you all the info that you need.
The weather is so bad that I will test indoors.
The mount is definitely an AP 1100GTO. Unfortunately not mine!
Wow long time since I posted this. I was unable to resolve the issue at that time and have not had another opportunity to attempt a solution.
I still am the custodian of the AP1100 so I can try a set up but I am really time poor at the moment ( I work in health planning and coronavirus has basically taken out any spare time).
I almost certainly will get a chance to set it up again in the next week. I don't use the AP1100 myself so the urgency is much less and as I said this really does not affect any other aspects of the mount just a nuisance really.
Let me know if you have any ideas as happy to work through the problem time permitting.
All the best,
Just to let anyone know that I was unable to overcome the EQMod driver crashes on the current nightly build. The only solution currently is to roll back to the last stable build for Ubuntu (KStars 3.3..
Use the following to roll back to 3.3.8
sudo apt-get install ppa-purge
sudo ppa-purge ppa:mutlaqja/indinightly
Everything now works as expected.
Terrible weather with the bushfires around Brisbane so I have not had a chance to use the scope for a few weeks. I did a nightly build upgrade yesterday so have the latest build . Running EQ6 Pro using EQMod with ZWO cameras & MyFocuserPro2. Everything was working fine but when I tried to do a quick test that everything was working I got repeated EQMod driver crashes.
I have not changed any hardware so I presume a recent EKOS update may be to blame. I am using ASTAP as solver but this has worked flawlessly from the get go.
I have attached the log. The last time this happened I uninstalled the EQMod driver then reinstalled it and it worked again. This strategy did not work this time. Anyone else having this problem? If it is just me I will work through it.
For some reason it did not want to download on my laptop. It has just downloaded fine on my PC.
I can confirm that the KStars 3.3.7 now connects to INDI and the ASTAP solver works as expected on a loaded FITS. The solving speed is amazing. Less than 1 sec!!
Thanks ++++++ to Han and yourself for all the work on ASTAP.