I just reset the the park position using the handset (find home, set park to current) and now it works again.
What I noticed was I could use the Park command in Indi but it never completed, if I gave the goto home command with Indi then I did get the status "Mount is Parked". I guess Indi was never reaching the "home" position so it did not register as parked.
"Clear Outside" says it going to be totally clouded over but I have blue skies, should at least be able to experiment a little.
I need new glasses! The published driver is the 1.3 driver, I thought it read "1.5" but that is not the case.
I am still confused as the behaviour does seem to have changed, I am sure I could Park and Unpark previously.
Can anyone with GEM45 conform the behaviour?
I have just upgraded to the latest version of the the Indi library and I notice that the behaviour of the GEM45 mount driver has changed. It is now using the iOptronV3 driver Version 1.5 Interface 5.
I upgraded the firmware in my GEM45 a few weeks ago and loaded the iOptronV3 driver Version 1.3 Interface 5. The park function was working perfectly in that version. I used it for many sessions.
In the version from the latest library the mount will park once but it is not possible to Unpark it from EKOS. EKOS keeps the Unpark button greyed out, the Park is still active.
If I park it from Indi it says "Parking in Progress..." and stays in that state.
If I then unpark it from Indi it says "Parking/Unparking aborted" followed by "Slew Complete, tracking..." and it switches on the tracking.
So I thought I will just revert back to the 1.3 driver (I always keep one SD card with my last good working version) but the behaviour there is now the same!
It seems like the 1.5 driver has sent some command to the mount to change its behaviour.
Does anyone know why I am seeing this behaviour and how I can get back to the V1.3 behaviour?
I know that a lot of people use the Autofocus function with success but I have never got it to give me a sharp focus. I have been using a Bahtinov mask which always works well. Last night it was cold and I thought let's give autofocus another try. It completed successfully and I started imaging. When I took a look this morning (I know I should have checked last night) the images I though looked good we're all out of focus.
Does anyone have any tips?
I also noticed that I could get it to work anymore. Any tips how to activate it?
The Indi drivers do track the major versions (so we test for V1 or V2 in the code) but Pegasus have made quiet a few changes recently to their firmware (almost daily at one point). Quite a few of these versions were not stable so I really don't want to support them and the advice is run the latest version. With the wisdom of hindsight it would have been better to do a version check on the "DA" command. There is not a way to load old firmware so from a development side it would be very difficult to ensure the code runs with every version and to be honest I would not have the time either.
The driver will not chew up memory. It reads the messages and then throws them away. These messages indicate that we sent a command and the response we received was not the expected one and in many cases is truncated.
They are actually correct that they do not maintain the Indi driver, we do.
These messages do not effect the way the driver works in any way but indicate that there was an error receiving the status data. I could just remove the messages but I would like to get to a state where they no longer occur.
I have been running both the latest firmware and Indi driver for a while now without issues.
I will upgrade to the latest Indilib to make sure there is no difference between the driver I have been using and the currently released driver.
Sounds like Pegasus are already looking into this for you
I have just asked Pegasus if there is a non Windows way of upgrading.
There is a test version of Parallels available for the M1 but no idea if that would work.
You need to use the Pegasus UPB Windows App. If you connect the UPB to a Windows machine running the app it will detect that you have an older version and offer the upgrade.
Is you UPBv2 upgraded to the latest firmware?
I am using the latest V3 driver on my Gem45 with the latest firmware and the park works perfectly.
I use the handset to find home (which is my preferred park position) and then I set the park position using the handset to the current position. After that I can use the Park command in Indi to set the mount to the park position.
I have a similar setup. I have the RPi and a Pegagsus UPB mounted on a losmandy plate.
Managed to do a session running everything on the Pi. I am definitely going to stick with this.
Kstars seems more stable on the Pi than on the Mac and I don't have to worry if the Mac battery runs out.
Very curious to see your first results.
Is it advisable to use PEC and guiding together or will they get in each others way?