Good idea. I'll add more "slop" to my temperatures. I guess when I run the camera for a bit, it would heat up slightly. It's an ASI120MM Mini.
This is the handful of darks I managed to capture last night when trying to figure this out.
Could my temps be varied too much? Seems pretty close. I'm not super picky about how accurate the darks are yet, I'm just trying to figure out how to make my autoguiding run realiably. I'm close, It will be going fine for a while, then a random spike of 10-20 arcsecs that has me banging my head on my dome! It then settles down again for a while. I'll have to graph my data and see if it's random or repeating. Another topic for a different thread.
So if there is a flat in the folder that is the same time/binning it should just use that once the "[ ] Flat" box is checked? It kept telling me to cover my scope and I never saw it look different once it took it. I do have maybe 5 files in my flat's folder, but not sure how to tell it to load one of the flats. Nothing changed on the file, still 3 seconds and 2x2 binning.
Thanks for the help with that first question I had.
Next question: Anyone know how to load a flat frame for the guider? I did create a small library of them and would like to load one to clean up my autoguide image. Seems that when the "Dark" box is checked it would create one if there wasn't something saved already? I try that and it keeps asking me to cover the scope an take another.
How do I load a dark that is already made and use that?
Ah! There it is. They tucked it away in a totally different area than the guider options. I'll turn that off and see how it goes. I usually do a re-calibrate often, but when I'm on the same one and for some reason I have to stop the guiding, it's a pain to have to redo that.
I was looking all over for a checkbox like that, but mine doesn't have that. I'm running version 3.4.0 of KStars / Ekos.
I'm very slowly learning to autoguide my mount (Stellaremate OS / EQ6-R Pro / Stellarvue refractor).
When using flats in the guider, I understand it will save flats in the flats folder and from what I read, it should pull one out (up to the validity day limit). How do you load one of these pre-made flats to use for guiding? In the folder it says "double click to open" but it just highlights the part of the file info currently pointed at. Do you select on and hit the OK button? I don't see it loading, and it still tells me to cover my scope for flat.
I understand the flats will help with noisy images, so if you run a filter that clears the image up a little more (median seems to improve it for example) does the guider use that cleaner image for guiding or is this just for the advantage of the user to watch the guiding?
I also have it seem to run the guide calibration often even in the same chunk of sky that I'm currently in. I didn't clear the guiding, but it does it itself. Is there a setting to keep the current guide calibration or is this something it need to do often? It is pretty quick to run, but just annoying when it does it so often.
Thanks in advance. I'm very happy with Ekos/Kstars and the non-Microsft world, just climbing a learning curve.
Ok, now it's saving! Not sure what I was doing, but I think I have it going now....or have a good idea how to get it away from 270 degrees. I'll try it when it's dark and see where I go. I think I have it worked out for now. Finally, I can give this Pi4 a test run. Yay!
I think I figured something out after spending a couple hours messing with things.
It seems that when my dome slaving settings are all set to 0.00, the dome will go to 270 degrees and do nothing else. When I set some numbers in there (like the attached photo) the slaving works!
But, for some reason they aren't saving the settings when I shut down the Pi, so when I restart they are all back to zero. At least I'm making some progress with this problem.
All set, but nothing is writing.
Logs from the .local and .indi folders?
I ran it and tried slewing around. Just goes to 270 and won't even attempt to slew anywhere else the mount does.
Yep. I updated the Pi3/Astromate using the software updater. I didn't want to do anything too drastic on that one (like full new image) since it's working ok. The Pi4 with both Astroberry or Stellarmate are fresh installs. I am playing with Astroberry more right now since I'm having problems with making the monitor setting stick in config.txt (but that's a whole different issue).
As far as I can tell, I have the settings matched up in EKOS. I'll spin it around a few times and see what I can find in the log.
Your Stellermate on the Pi3 that I helped you test, works beautifully though! Just trying to upgrade.
I'll log the rotation and see what that shows. That might give me a clue what's going on.
I have my dome parked at 100 degrees, home position is at 180 (from my LX200 days wedge parking). I now use an EQ6-R mount that parks on Polaris, I still have to move the magnet to 360.
As soon as I unpark the scope the dome goes to 270. Maybe has something to do with my 180 home?
Strange that it's only with the new Pi 4 though.
I did post this before a while back but tried the suggestion and no change.
- me observatory with motors
EQ6-R Pro mount
Raspberry Pi 3 (trying to upgrade to 4)
All runs great on the Raspberry Pi3 which I have Stellarmate installed on.
I'm trying to upgrade to a much faster Pi 4, running either Stellarmete or Astroberry.
When I get everything connected fine, then try to sync the dome with the mount, it slews to 270 degrees and that's pretty much it. I don't have any problems running it on the older PI 3, but Pi 4 unit always does this. I have the same problem with either the Stellarmate or Astroberry.
Any ideas what to try? Where in the settings that 270 degrees might be lurking? Can I copy the configuration files from the working Pi3/Stellarmate to the new Pi 4?
I'm totally confused and not sure where to look, I've been all over the settings and not finding a hint of the 270 degree "slew to" or whatever is going on!