Thanks Jasem,
I'll update the software and hope for a clear night sometime during December. Not always an easy thing to find in the Seattle area during the winter months

Bill

Jasem, you rock! That last fix solved the guiding problem. I managed to get everything fired up and tested about a half-hour before a cold front rolled in and clouded everything out. The RST-135 slewed to Mirfak and plate-solved no problem. I then cleared the old calibration info out of Ekos and told Ekos to pick a star and start guiding. And that is exactly what it did!

Stopped guiding and slewed to M43, plate solved, and then clicked on guide again. Ekos worked flawlessly and was guiding and taking 30-second subs until the clouds rolled in and blocked the sky. Looking at the long-term weather forecast it'll be at least 2 weeks before I can test again. Maybe Andrew will get a shot at testing.

Bill

Jasem, I can confirm, it's all working well now! Thanks! Happily guiding away.

Just woke up to check the nightly session and found the meridian flip didn't happen. KStars was crashed when I came to it this morning, and I had to restart the Raspberry Pi.

The mount automatically stops tracking at the meridian, this is the default behavior. So I set the flip of HA > .10 degrees, thinking it would sit idle not tracking for a minute or two, then issue the GOTO command to slew, but it appears that did not happen. I didn't have logging on, but do have the Analyze tab data. It shows the guiding stopped right where the flip was supposed to happen. I can only assume when the mount stopped tracking, guiding failed. Could this be why the flip didn't happen as possibly the schedule aborted? But the Analyze tab shows it still took images for three more hours despite it having 6 more hours until twilight where I requested it stop. So this must have been where the crash occurred. The mount was physically on the west side of the pier facing east still, so the GOTO command was never issued to move it east, facing west.



I'm thinking I'll just set it to flip right at the meridian, and hopefully the clocks in both the mount and EKOS match so that it doesn't issue the command a second or so early. I'm not really sure what other options there are. I've had successful flips with ASIAir, and NINA on PC using the ASCOM driver (set to flip 5 minutes after meridian).

Any suggestions or thoughts?

I have the Rainbow Astro RST 400 which uses the same ascom driver as the RST 135. My RST 400 has a guiding issue still today. The star is driven right off the screen and can not be tracked. Additional when I stop guiding the mount just keeps on going. I have to bring up the joystick control and hit the stop command to keep it from continuing on. I tried reducing the guide rate, and the pulse duration for calibration no change. Any help please... Bruce

I also submit a ticket for plate solving not working. I think I 7nderstand why, the driver is not passing pointing data to the solver.... Bruce

You have to switch to the StellarMate beta and run the terminal command in Jasem’s post above to get the fixed driver.

Tried the terminal command listed above.
Install was good. MY RST400 still failed for guiding and plate solving. After 6 guide steps the mount just starts slewing off. The plate solving just fails. The motion control works. This mount has been idle because of focusing system failure which was just fixed. I also do a Stellarmate update and upgrade from time to time... I have the standard Stellarmate installed. How do I get the beta??.... Bruce

Open the web browser and go to the control panel. On one of the tabs you should find the option to switch to Beta. Once you said it to Beto run the update icon that’s on the desktop then reboot. When it loads KStars you should be able to go to the about menu and see if you’re on the beta. If you are on the beta then run that terminal command to get the latest drivers.

I have done the update_indi_core command via vnc terminal app. I am now not able to start ekos from my Mac. “Failed to start profile on remote INDI Web Manager...” is the message. The web manager equipment profile driver list seems much reduced, not sure if that is the problem. Ekos starts fine from the iPad app or the vnc interface.

Not sure what the origin of this problem was but a clean install of stellarmate from image followed by update_indi_core seemed to do the trick

Don't forget to run update_indi_drivers as well.

Jasem,
After running that last command I had success on guiding and plate solving. When I connected to the mount it threw a couple of dbug errors that quickly disappeared. On an earlier attempt here is the log file
My mount is the RST 400.
org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] CMD <:GR#> "
[2020-12-26T22:43:12.549 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] RES <:GR05:36:01.8> "
[2020-12-26T22:43:12.550 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] CMD <:GD#> "
[2020-12-26T22:43:12.565 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] RES <:GD-05*23'42.1> "
[2020-12-26T22:43:12.566 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] CMD <:GZ#> "
[2020-12-26T22:43:12.581 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] RES <:GZ158*45'39.3> "
[2020-12-26T22:43:12.582 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] CMD <:GA#> "
[2020-12-26T22:43:12.597 CST DEBG ][ org.kde.kstars.indi] - Rainbow RST-300 : "[DEBUG] RES <:GA+49*06'42.9> "


As always many thanks to you and your team of programers, this is a fine product... Bruce