[The_bluester (Paul)]

We were finding when using it all on board via screen sharing (Using it's hotspot mode to a Mac laptop a couple of feet away) that it would be great for a time then suddenly get very very laggy and non responsive, particularly if you pulled Ekos down out of the way and tried to search an object in Kstars. If you connected to it via the smartphone app it appeared OK via that route but you would have to reboot it via the smartphone to get it to respond again in any other way. At one point we had it guiding and while it was non responsive, you could hear the mount guiding still.

That is using an SD card to boot it (Pi4) and a genuine Rpi power supply, I doubt it would be heat, it was doing it in about the same amount of time between the (Warm) garage and when we did a test under the stars last night. The temp was low enough outside to have us in jackets and beanies! The Pi was in a FLIRC case that is supposed to double as an effective heat sink. Logging was per the out of the box configuration so I might have to look at that.


The next step will be to put it in direct connect mode and set the Mac up with the right IP address so we can eliminate anything to do with screen sharing bandwidth limitations over wifi. Regardless, it was a very promising start with it up and running and connected to all Andy's gear successfully and plate solving and pointing working. One other issue for us to look at is probably more related to the Indi driver for his Temma, the park/initial position is given as pointed at the pole, counterweights down, but it actually seems to be pointed at the pole, counterweights east and it is a bit nerve wracking due to the relative RA and Dec slew speeds of the Temma, some slews to and from the park position take the camera nerve wrackingly close to the pier! It is supposed to be able to be set to a different position within Ekos, but once done it would head on back to the original position regardless!