Well my modus operandi is to have two profiles, one with the SV305 as the imaging camera and CEM26 mount (for plate solving to position), and a separate profile with an ASI120MM camera set as the guide camera with the CEM26, sans main camera. I can also apply a sim camera emulating the '305 FOV, but that's not really important. Once plate solved with the '305 as the main camera, I would switch profiles, start autoguiding with the ASI, and connect the '305 to AstroDMX.

However running some tests I'm seeing massive CPU usage and rising temps when running simulated shooting sessions with AstroDMX, as you can see below. When idle at shooting speed, CPU usage is around 85%(!) the temps are up around 65°C(!). For some reason CPU usage drops somewhat when actually shooting. There's slightly less CPU overhead at 8 bits, but "the song remains the same". Some formats are more taxing than other.

So I'm wondering if I should just scrap planetary shooting with the Pi altogether and just use my Windows ASCOM setup tethered instead