Mini PC crashing caused scope to hit mount

Jon Foulkes · Mar 11, 2026, 01:10 PM

Looking for some help/advice please, on how to understand what caused my mini pc to crash & also how to stop the mount continuing to drive in the event of a pc hanging-up..

Following a recent imaging session I awoke to find my mount (an EQ6-R) had rotated through 180 deg leaving the scope hard up against the pillar mount. The power light on the mini pc (a Mele Quieter 4c) was still on, and the TEC cooling lights on the camera were on, as was the power to the mount (all are mains powered through the supplies that came with the equipment) . My indoor laptop had lost remote connection and wouldn’t re-connect to the mini pc.

After cycling power everything was still working. The last image taken prior to the crash was at 01:19am. The log file from N.I.N.A. shows that the last action was to start an exposure at 01:19:52. The log from PHD2 showed no issues, with the last update occurring at 01:21:44. So everything seemed to be running ok until around 01:21, then simply stopped. I’ve tried checking the Windows11 log files using event viewer, with limited success. The last event recorded was at 01:16, then nothing until I recycled power around 07:15 the following morning. When the mini pc did restart, one of the first events logged at 07:16 showed an error - ‘a previous system shutdown at 01:16 was unexpected’. A further critical event at 07:15 shows system rebooted without cleanly shutting down first - I’m assuming this was as a result of me power cycling the equipment. I’m no expert in win logs, but I suspect there maybe something I’m missing in those logs which might shine a light on what’s happened - would really appreciate any help with this.

My current assumption is that the pc froze, but did not reboot. As the pc stopped responding, then the Meridian Flip didn’t happen (this is set-up via N.I.N.A.). As the mount was tracking at sidereal rate, although there was no further guiding pulses from PHD2 the mount continued to track, which ultimately brought it up against the pillar mount. Although mount limits were set (and enabled) in EQMod, these appear to have had no effect. So my question here - is there some way that the mount limits can be set within the mount which would continue to work even if the pc lost comms?

I have had the same issues in the past (twice I think), fortunately without pier crash. The only thing I could gather that would solve the issue is limit switch that cut the power to the mount in case the RA axis goes physically above a certain angle. Someone on stargazer lounge did a diy on that:

https://stargazerslounge.com/topic/436819-mount-ra-overrun-prevention/#comment-4610601

https://stargazerslounge.com/topic/436714-harmonic-mounts-just-a-bit-too-powerful/page/3/#comment-4610675 (scroll up a bit to find photos of his set up).

Unfortunately I’m shit at diy electronics so I just wake up for meridian flips now, don’t even move out of my bed but I check on my phone that the flip did occur at least. And I wake up to bring back the rig inside quickly after the sequence stopped too.

More advanced mounts have internal limits but not the cheaper models.

Over the years I’ve learned to check for any “Automatic Updates” occurring.

Particularly Windows Security Updates. Because Windows doesn’t like third party App’s on any computer running Windows. They only readily accept App’s from the Windows Store. Which none of our typical equipment apps come from.

So check and see if any Updates have come into your minicomputer lately.

That is the one thing that I’ve found consistent with bad behaviors.

I do hope the crash didn’t bugger up your telescope. Make sure your limits are set correctly, too.

SonnyE · Mar 11, 2026 at 02:10 PM

Over the years I’ve learned to check for any “Automatic Updates” occurring.

Particularly Windows Security Updates. Because Windows doesn’t like third party App’s on any computer running Windows. They only readily accept App’s from the Windows Store. Which none of our typical equipment apps come from.

So check and see if any Updates have come into your minicomputer lately.

That is the one thing that I’ve found consistent with bad behaviors.

I do hope the crash didn’t bugger up your telescope. Make sure your limits are set correctly, too.

I do wonder if a windows update is the cause - there have been several updates since Jan 26 which have caused rdp issues, which ties in to when I started getting this problem. The equipment seems ok, thank God. At the moment I use EQMod for limits (I have proven they work in the past) but need to investigate if anything can be done in the mount itself.

Jon Foulkes · Mar 11, 2026, 02:39 PM

Rick Krejci · Mar 11, 2026 at 02:10 PM

I had a Beelink mini PC that would sometimes reset itself due to the power supply it came with being insufficient. When it would do something computationally intensive (like plate solving/analyzing a new image after download), it would sometimes reboot itself. Once I used my overspeced scope power supply rather than the little brick it came with, all my problems went away.

On the AP mount, you can set it to stop tracking if it loses communication for a certain period of time.

I’d love to know how to stop tracking if it loses comms

For the Astro-Physics mounts using APCC, in the Park tab, there’s a Safety Park feature where you can have it Park to the current position (or any other park position) after a configurable amount of time after losing communication with your PC.

For your mount, it’s not as easy. The last post in this thread seems to indicate a work-around. https://www.cloudynights.com/forums/topic/824870-eq6r-pro-auto-park-on-pc-crash/#findComment-11918131

Rick Krejci · Mar 11, 2026 at 02:55 PM

Jon Foulkes · Mar 11, 2026, 02:39 PM

Rick Krejci · Mar 11, 2026 at 02:10 PM

I had a Beelink mini PC that would sometimes reset itself due to the power supply it came with being insufficient. When it would do something computationally intensive (like plate solving/analyzing a new image after download), it would sometimes reboot itself. Once I used my overspeced scope power supply rather than the little brick it came with, all my problems went away.

On the AP mount, you can set it to stop tracking if it loses communication for a certain period of time.

I’d love to know how to stop tracking if it loses comms

For the Astro-Physics mounts using APCC, in the Park tab, there’s a Safety Park feature where you can have it Park to the current position (or any other park position) after a configurable amount of time after losing communication with your PC.

For your mount, it’s not as easy. The last post in this thread seems to indicate a work-around. https://www.cloudynights.com/forums/topic/824870-eq6r-pro-auto-park-on-pc-crash/#findComment-11918131

Thanks - I’ll look into that 👍

Given the timing, I’d really think windows update got you. You can search ‘update history’ in the windows search and it will give you a log of all previous updates. Per your theory that the PC was frozen, I don’t believe it. You hard reset the PC, and it logged that action. That means it wasn’t frozen up to that time. What I believe is your windows update happened, and it sent you back to the main windows login screen, and some services didn’t start up. RDP being one of them. Don’t ask me why, but this is EXACTLY what happened to me the one time I experienced an update.

Easiest and simplest way to disable automatic updates is to set your network connection to metered. That’s it. No crazy registry changes. Now, keep in mind if for some reason the connection changes, like you get a new router, you’ll have to update that setting again, but I’ve done this now for 2-3 years on all my rigs and only had an issue once, and that was because I created a new wifi, didn’t update metered.

EQMOD mount limits will not work if EQMOD is not on, or frozen.

You can breathe some fresh air in knowing it’s pretty hard to damage an EQ6R in a situation like this. Unless you’re cranking down on the clutches, they allow things to slip. It’s just a brass knob pushing against the smooth brass of the gears, with a bit of grease in the middle. Not the same story for the electronics like the camera, but for this reason I never tighten the clutches more than I need to stop free movement + little bit of wind.