No, I did not put the HC in PC direct mode. I wanted to use the mount in Alt-Az mode. I only use the eqmod direct connection for equatorial mode.
When connecting with the Synscan driver, you first have to do the alignment procedure via HC, than you should be able to connect to the HC without going in PC direct mode. The PC direct mode will bypass the HC. One can do this as an alternative to the eqmod direct connection for eqmod.
Just wonder, why I can´t sync.
For the first time I tried the Synscan driver for my AZ-EQ6 in Alt-Az mode. After the initial alignment procedure with the HC I was able to connect via the HC. I could execute Gotos, but I could not sync the Mount to the correct position. I tried to sync via the Ekos alignment module and also manually in the indi control panel by entering the data from the solver solution, but the new coordinates would not be accepted.
Thereafter ekos/kstars crashed and it kept crashing every time I tried to reconnect to the mount. The GDB log is attached. Any advice ?
I am having a persistent problem with running my QHY5III178 alongside ZWO devices (ASI2600MC is worst, problem occurs also in connection with ASI290MC and ASI Filterwheel).
Once I have my QHY camera running alongside any Zwo device it is only a question of time, until ekos crashes. Even if I only activate my Zwo camera in Firecapture, and have no active instance of Zwo in indi, ekos will crash. Log file is attached, but as far as I can tell, the log just stopped at the point of the crash.
I always had one little problem with my QHY: the video stream would not work. The window would open, even show a fps number, but would just remain black. I did not make much of it, as I mainly use my QHY for guiding, and the looping function and the single exposure function always worked as they are supposed to. As long as I operated the QHY with my Canon EOS the system appeared to be stable. When I tried to connect a Zwo filterwheel I would have crashes quite often at the start, but if I used the filterwheel only in oacapture, it would run ok. Now I have a Zwo ASI 2600MC and I just can´t get this camera to work reliably in parallel to the QHY. Running the 2600 alongside a Zwo 290MC is no problem at all.
My system is based on an astroberry running on Pi4. astroberry is most recent version.
Does anybody else have similar problems ? Any hints to get the system stable ?
@geehalel: I can´t stress enough how thankful I am for your help and efforts !
Just posted within the astroberry section of this forum to Kaczorek, the maker of astroberry. Maybe he has some idea, what the problem is.
What makes me curious is, that the compilation of the official branch of libindi did work, apparently. At least I got a working libindi afterwards. Did I understand you correctly, that it is your assumption that the compilation of libindi does not work on the astroberry ? I have the feeling that I missed something, anybody more knowledgeable with linux would automatically do.
@Kaczorek: I am having some difficulty "handcompiling" libindi within my astroberry. I am running astroberry on a pi4. I have done update & upgrade & distupgrade last week, so I assume I am current with regard to the version.
I wanted to try the Alt-Az driver for my AZ-EQ6. This driver will not work with the current version of libindi. Geehalel was kind enough to fix the problem and he set up a branch within libindi so I could compile it for my system ( indilib.org/forum/wish-list/7524-alt-az-...-eqmod.html?start=36 ).
However, after following the instructions to compile this branch, I ended up with a libindi which could no longer connect to most of my equipment. Neither the eqmod, nor the altaz driver would work. Only connection to the USB cameras did still work. I than reverted to the official branch by again following the instructions for hand compiling (as set out here: github.com/indilib/indi#building ). Thereafter, my indi would work normal again, but I did not have the benefit of the fixed Alt-Az driver.
Please let me know, whether you have any advice here of what I could do to make it work.
Many thanks & many thanks anyhow for the marvelous work you did with Astroberry. Great system !!!
@geehalel: first off, many thanks for your help, which I appreciate very much. Regarding the communication problems with my AZEQ-6: I guess something went wrong on my system with the compilation of your branch of the libindi. After com problems with other devices I reverted to the current official libindi by just following the compilation instruction on the github page. After that I could connect again with the eqmod and other drivers (not with the alt-az driver, though). Any ideas what might have caused the problems ? I have I relatively clean install with all recent updates of astroberry running on a pi4. The only amendments done to the astroberry is an installation of a wifi dongle. The compilation process did finish without any errors in both cases, i.e. installing your branch and the official one.
Regarding the alt-az drivers: I have not been aware, that these drivers implement kind of leapfrog tracking. Probably for the planetary imaging I would be better of to revert to the factory driver running off the handcontroller. Once this is initialised and aligned I can connect with the synscan driver. The only thing which put me off here, is that I first have to do the manual align according to the synscan manual as the driver will not accept any input before conclusion of the initial alignment routine. I would have to install and use the visual guide scope, which I retired already and every time punch in the current date, time & stuff. It sounded so promisingly easy to do all the alignment with with ekos alignment module.
So if there currently is no decent alternative to the factory drivers I would also pitch again for having some form of an alternative for alt-az control. As much as I understand the benefits of GEM mounts, the recent advancements with EAA made many things possible, e.g. live stacking of relatively short exposures, which makes DSO much simpler as one does not necessarely need guiding and even field rotation is not a problem as the image is being de-rotated by software. I happily volunteer for testing !
The big advantage of the alt-az mounts is the time you save when setting things up. You just have to level the base of the mount and are ready to go. Setting up my stuff in GEM config takes considerably more time: in my case I have to go to my backyard as the view of Polaris is obstructed from my terrace. The tripod for my alt-az mount has rollers attached, so I can just roll the entire rig out, level it and start. I am only a casual observer. So when i have lets say three hours for observing during evening hours, I loose 1 hour for mounting and dismounting my equipment and probably 20 min. for proper alignment of the scope. Something always goes wrong, so in the end I have max. 50% of the time for actual observing. With the alt-az I would just roll in and out in 10 minutes and have the scope aligned in 5 min. So effectively the time for observation is doubled. At least in theory...
Anyway, I would very much appreciate to have a system as good as eqmod for the alt-az mount. With the advancments in EAA I would guess that more and more people will use alt-az mounts as they are simpler to use and can bring more people to this fascinating hobby.
did the update. AltAzSimple still handshake failing; skywatcherAltAz does not connect due to other reasons. Log attached. First attempt is with AltAzSimple (because there the connection at least was initiated), second with skywatcher_AltAZ
checked the date of the indi drivers in /usr:
indiserver and skywatcherAltAzMount are with date of today. indi_eqmod_telescope is Apr 13.
Tried to "handconnect", also. No success.
Installed picocom and sent ": +CTRL-M"
My mount returns "!0" ; so different response from your AZEQ5...
For the setup: I have astroberry installed on a pi4. Pls. let me know what other info you need.
did another run now with the geehalel indi branch:
prior to the compilation I could connect to my mount via direct USB @115k. After the compilation I could not connect with either skywatcher_altaz, Altaz_simple or EQmod.
For the EQmod I received the following log message:
[2020-09-11T13:45:25.870 CEST INFO ][ org.kde.kstars.indi] - EQMod Mount : "[ERROR] Error: Communication failed -> tty write failed, check connection: Write Error: Bad file descriptor "
[2020-09-11T13:45:25.872 CEST DEBG ][ org.kde.kstars.ekos] - "EQMod Mount" is disconnected.
[2020-09-11T13:45:25.873 CEST INFO ][ org.kde.kstars.ekos] - "EQMod Mount is disconnected."
For the other two, I attach the log file. It occurs to me, that for the skywatcher_altaz the config.xml in the .indi directory is missing. I could set the connection parameters in the indi control panel, but I am unsure whether they have any effect:
@knro: may the problems with the slew speed reported by geehalel be connected with using the skywatcherAltAz driver instead of AltAzSimple driver ?
Ah, good to know. My understanding was that the AltAzMount driver has not been updated and the AltAzSimple driver is the way to go in Alt-Az mode. Will try the skywatcherAltAzMount instead...
The rfcomm device is a bluetooth dongle, which connects via the HC port in the mount. This has to be set to 9600 baud in order to work. The 115k is for direct connection via the USB port of the newer AZ-EQ mounts. I can use either way to connect.
many thanks again; I think the compilation worked; at least the whole process did finish without any error messages. Could not connect to my AZ-EQ6, though. But I also could not connect to normal EQmod and some other devices. Will do another compilation on a fresh install tomorrow...
@geehalel: many thanks ! Did as per the instructuction. Last command ("git checkout azeqaltaz") returned an error:
astroberry@astroberry:~/Projects $ git clone --depth 1 github.com/geehalel/indi.git
Cloning into 'indi'...
remote: Enumerating objects: 706, done.
remote: Counting objects: 100% (706/706), done.
remote: Compressing objects: 100% (667/667), done.
remote: Total 706 (delta 125), reused 131 (delta 24), pack-reused 0
Receiving objects: 100% (706/706), 2.34 MiB | 3.43 MiB/s, done.
Resolving deltas: 100% (125/125), done.
astroberry@astroberry:~/Projects $ cd ~/Projects/indi
astroberry@astroberry:~/Projects/indi $ git checkout azeqaltaz
error: pathspec 'azeqaltaz' did not match any file(s) known to git