Just posted, and saw this thread below mine, seems like a very similar thought to my mine - I wasn't consciously aware of this thread when I wrote mine, perhaps I'd unconsciously seen it over the last couple of days!
Well, I'm on course for replacing my ASI120MC-S guide camera with an ASI290MM mini, which I will be putting on my OAG.
I've been thinking about what I could do with my ASI120MC-S, it does come with an all-sky fisheye lens, so I could dabble with that, whiling away the time through my 300s exposures, with some very wide field stuff.
Then, I came across a thought: When I am imaging, from the comfort of indoors, and the telescope out the back, I'm not immediately aware of clouds coming over. When clouds do appear, everything goes haywire - guiding goes out of control, focusing sends my focuser to the end of it's tether (literally) and it gets stuck there. Could I, somehow, use the ASI120MC-S, mounted to a small guide-scope piggy-backed on my main scope, to work as a plate-solving camera.
Plate Solve - If plate solving fails --> halt focusing and guiding activities
Plate Solve - If plate solving doesn't fit with location of imaging (with a threshold) - then, perhaps, at next main telescope exposure, schedule a re-alignment...
What are everybody's thoughts about this?
I know I could get a weather type station, or cloudwatcher, but just thought that this extra bit of kit might be useful.
amendolajamie wrote: Here's a little more:
ssh -l pi -C -X 192.168.247.108
This adds the "-C" for compression which helps with some things. I also had to use the "pi" account for some reason, probably to do with all my mucking around.
When I am in my back garden. I run INDI server on the Pi4, with it connected via an Ethernet cable on my home network and I run Kstars and Ekos from the warmth of my house. All is powered via house AC via 12V regulated power supply.
I am planning on doing some remote astro in the future, at which point I would probably switch to using Kstars and Ekos on the Pi4.
The reasoning for this is that I can run the Pi4 off a battery, and conserve Laptop and Tablet power by only using VNC on the Laptop to set up and troubleshoot the scheduler session, and then only using VNC on the tablet to monitor the session progress, if an issue occurs I will bring the Laptop out of sleep mode, try and correct the issue and then revert back to the Tablet (View only). I can recharge the Tablet off the car adapter, don't have a recharge for the Laptop though, so would want to conserve its power as much as possible during the session.
Hoping that a PiJuice comes into stock soon, with a large battery, then I can use both the PiJuice battery and the Power Tank together to make sure that the Pi doesn't run out of power.
amendolajamie wrote: OK, so I've got some success. It looks like it is the hdmi. I set hdmi_ignore_hotplug=1 in /boot/config.txt and now it boots and I can ssh to it over wifi using 2.4G. All while my camera is plugged in to USB3. This is great, I think that I've got a fix. I just need to install a VNC separate from X11/HDMI and I should be good to go. I can still VNC. but now just get a blank screen "can not currently show desktop". I verified that HDMI is not working by plugging it into a TV. No HDMI output.
wvreeven wrote: Regarding using a powered hub for the ASI equipment: I have been using ASI1600MM and ASI6200MM cameras with an ASI120MC-S and ASI EFW chained to it with no issues whatsoever on USB3 ports of various hardware, including RPi4. Just my $0.02
This is interesting, as I think I've seen evidence of a recent glitch.
Need to try again before really reporting anything.
There does seem to be an increase in reporting of issues that might be related to mount perceived Lat/Long and Time settings.
Looking at the photo here:
Has anyone actually got one of these? I thought they're still only available as a pre-order item.
The mount should be attempting to track, if it is an Equatorial and well aligned then I wouldn't expect to see a very large deviation.
To many parameters in play for me to say, some more experienced people might have some input.
Probably lost your guide star.
1. Increase guiding exposure time.
2. Look at SEP Multistar (new feature) in latest versions of Ekos, can help track a moving guide star by referencing the positions of other stars in a field.
3. OAG badly out of focus? Not parfocal or focusing failure?
I have the ASI120MC-S on an OAG, and sometimes images seem rather noisy, soon to upgrade to the ASI290MM mini for the OAG - hope for better SNR, and lower noise in general, plus it is mono, so should be better on many fronts.
With my experience, I will confirm on next outing, my CGX (latest firmware etc...) tracks once aligned, and continues to track when slewing.
I can only assume, that either mount thinks it is not aligned, or not set to sidereal tracking.