You can confirm it works when defining it manually.
sudo unlink /dev/ttymount
sudo ln -s /dev/ttyUSB0 /dev/ttymount
ls -l /dev/ttymount should show /dev/ttyUSB0
Then in the connection tab use /dev/ttymount (include /dev and no hyphen in tty-mount)
Did you have the take a Dark box checked? I seem to be having trouble with that lately. Works fine without but gets hung up for long periods when checked and finally takes everything down.
I think I'm back to something for the Mach1 I can use while the driver is being modified.
I did a build from current sources but into different bin directory. Then using github located the 4 lx200ap_experimental files from 1.8.5 replacing those in the local build area. After the build was run again, the indi_lx200generic binary was moved into the distribution's bin location.
The mount now starts up from cold unparked and tracking, Park/unpark and goto now work. Also KStars shows the correct location for the mount in the sky map. Many of the INDI panel's buttons are still dead, though I expect I will be able to edit the XML file to change settings in the meantime.
Now I suppose I should remove the PPA to prevent any updates.
There is one at github.com/wotalota/indi-rolloffino.git.
It is a INDI rolloff roof driver and includes two examples of Arduino programs communicating over USB. The driver is packaged as a third party driver but haa not been included with the standard distribution. The Arduino code needs to be modified to match the motor control selected, the INDI driver should work once installed.
See readme.txt for a brief overview of the communication protocol and INSTALL for build directions. After the build there will be rolloffino as an option under Dome when you edit the EKos profile. The driver works with the Observatory module and weather drivers as you would expect. I am presently using it with the Vantage, WeatherMeta and WeatherProxy for a RG11 rain detector.
For my install I used a Arduino Due with an Aleko gate motor. The 3.3V Due along with pull ups made the wiring more complicated than need be for the relay but I liked the extra USB port while debugging. The attached image shows an attempt at a matching diagram for the Arduino code. The relay & external power supply shown is and approximation just the only image of one I found.
"Until then I agree with your proposal, that the "Westerners" freeze their stack."
Any suggestions on how to go about doing that after already having accepted an update to the current stable release?
Open the INDI control, telescope panel, in the options tab. Look for Dome Policy entry and change it to Dome Ignored.
linuxUser, Thank you for those insights. Because I have not been able to image for some time but have been updating, its hard to pin down when it went wrong. Seems to have been between 3.4.2/1.8.5 and 3.4.3/1.8.6. I do not have a hand controller also would have to learn a lot more about git to attempt to go backwards.
I was wondering about trying to change over to the nightly build to see if anything was better, but seek boring predictability more than anything else so I would rather not.
Did you also see a change in how the mount initializes? It always started up un-parked and tracking. Now the driver indicates it is parked and not tracking.
There was a change in behavior some time ago. It used to be that when the experimental driver started it began unparked and tracking.
When running to test something else and not planning to image it was an irritation since I had to remember to park it or risk finding it a day later hitting the pier.
Now it starts up parked which I prefer, but perhaps that parked status was not really true. I noticed today that the indi driver UI indicates the expected Park2 position which matches the physical position of the telescope since last used. But KStars is showing it to be in the classic Polaris Park 3 position.
I'll see if unlocking the mount and changing to Park 3 will help reset things.
Thanks for looking at it.
I have not been following this closely but post here in case something has changed in the stable release 3.4.3. Tonight might have been the first chance to image with this release.
I am getting the following error. I am west of Greenwich and the Astro-Physics Experimental has been working well for me for a couple of years.
[2020-08-18T19:10:05.748 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <#:Sd -13*47:49#> "
[2020-08-18T19:10:05.748 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <#:Sd -13*47:49#> successful. "
[2020-08-18T19:10:05.748 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] <Slew> "
[2020-08-18T19:10:05.748 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] CMD <:MS#> "
[2020-08-18T19:10:10.745 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[SCOPE] RES ERROR <-4> "
[2020-08-18T19:10:10.745 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "Error Slewing to JNow RA 18:19:58 - DEC -13:47:49 "
[2020-08-18T19:10:10.749 EDT INFO ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[ERROR] Slew failed. "
[2020-08-18T19:10:10.749 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] EXPERIMENTAL: check status... "
[2020-08-18T19:10:10.754 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] check_lx200ap_status: received bytes 6, [100000210P000] "
[2020-08-18T19:10:10.755 EDT DEBG ][ org.kde.kstars.indi] - AstroPhysics Experimental : "[DEBUG] parkStatus: 1
Earlier there was some confusion whether the mount was parked or not at startup. The UI showed parked but selecting unpark gave measage: Telescope already unparked.
Look at your screen shot. The normal USB connection appears to be /dev/ttyACM0 and you are presently connecting to /dev/ttyUSB0. So first try and get the selection restored to the one that connects to the Arduino.
That should have fixed it.
Perhaps you did not execute the git command to fetch the changed code?
You could start over.
You need to follow the INSTALL directions again to rebuild the driver to be compatible with the release.
There have been changes to the way weather alerts are handled to park the mount and close the roof.
You will need to change over to use the watchdog driver. Watch out that your mount park switch locking of roof movement does not interfere with the software checks. If the roof locked light is on it will not respond to movement requests. By the time the park roof request is received the roof lock should have been released, but it needs testing.