Hi folks, my question is two-fold.
First, I'd like to use the Ekos focus module to manually focus with a Bahtinov mask. Now I found some old threads from 3-4 years back that seem to allude to being able to do this, but they're not clear on some things. Also, I was watching one of the old Stallarmate videos on the focus module, and looking at what is there now things have been shifted around since the video. I see for instance that Bahtinov has been added to detection, but I'm not sure how this is used, or if I even need it when using a Bahtinov mask. Activating it doesn't appear to do anything. I also see autostretch under effect, but it doesn't seem to do anything, but there's a toggle stretch button in the transparent buttons that seems to work and is on by default, is this the same process? Right now I'm just testing this looking at a starfield in Stellarium, so I haven't used this module in the wild, so dunno if using the starfield on the computer screen is confusing the processes. Basically I want to be sure I can effectively see a star clearly enough while a Bahtinov mask is on the scope, but things don't appear to be responding as I think they should. I see a live view button, but that window doesn't appear to have an autostretch option, so I don't think I'd be able to use it for focusing with a Bahtinov mask. The INDI docs I found on the focus module only cover using it with a motorized focusing unit, is there any docs on how to use this module manually? I'm a bit at a loss as to how to do so, inasmuch as it does appear to be possible.
Now with auto focus, can this module control a DSLR autofocus lens? I have a friend I'm helping to set up with an Astroberry setup, and he'll be using AF camera lenses as opposed to my manual focus telescope. Can his AF lenses be effectively used for continuous AF while shooting, or is he better off just manually focusing? If so I take it the process is as described for using the motorized telescope focusers, correct?
Thanks for any info on this.
Thanks for your reply.
In the WiFi channels, the band defaults to 2.4 gig for the Astroberry, and the channel say default. Does default mean automatic? There is an auto setting for bands, but not for channels.
Is the Samba password also defaulted to astroberry? Does the sudo smbpasswd astroberry command put you in the change password mode? How critical is it to change Sanba and VNC?
I read where you should change your Pi password due to potential Linux Trojans. I saw where you change the base Pi password (sudo passwd pi) and I also changed the Astroberry password in the Raspberry Pi configuration box, which was set to Astroberry.
However I have some questions on the WiFi login. I right-clicked on the network icon and got the box to configure them, and saw a generic WiFi connection, as you can see in the composite below. I have no idea why that other config is there, I don't recall ever making that. Is it safe to simply remove it? Also, just to confirm, this is where the WiFi login for the Astroberry is set, so when I login via WiFi I have make a new connection in my VNC Viewer app on my laptop with the updated password, correct? A web browser would also take this new password, correct?
Besides improving the security of the system, I plan to go shooting with a friend I've helped set up an Astroberry server on a Pi 4. We need to change our Astroberry logins from default to be different. However our Pi's will be in close proximity to each other, is there any potential for WiFi interference from one Pi to the other? I noticed there were Band settings for 2.4 and 5 gig, plus auto, would that be of any help?
As a follow-up on this, I took the mount to a more secluded site and, other than a firmware update, I decided to guide as I had before. I had a much better time of it, as you can see below, despite the guider tracking through some cloud cover. How much can that affect the guide tracking? This is obviously better than the +15 arc second spikes I was getting earlier! I also did try guider with GPG RA Guider activated, although I'm not sure if what if any affect that had. I believe this screen grab below was when it was running. I was so distracted by cloud cover that I forgot to let it run past a worm cycle, not sure that's important because I entered the mount's 600 second cycle in the GPG RA Guider setting and disabled the Estimate Period box.
So do you think the cloud cover was affecting the guider tracking? It seemed to barrel through it regardless, and I wasn't sure about what may have been causing the spikes. I haven't yet let it run without correcting.
On a different note, is there any way to change the graph colors? I'm viewing on a dimmed screen, and it's almost impossible to figure out what's DEC and what's RA. If I could swap the DEC and SNR colors, that would be great.
Yeah well, if you took a look at my plot above, you can see why I'm trying to understand the parameters and how to apply them as best I can. I simply don't know what to think about that data. Someone on another site mentioned their GEM28 (very similar to myCEM26) was vastly improved with the latest firmware update. I also just updated the firmware on my CEM26, but have yet to get a clear night to test it out. In the meantime I'm trying to sort out understanding these parameters, as that plot was created using the default Ekos guider settings.
Well I'm just going by the listed spec for a 600 second worm period, should I let it try to see if it's something else? I guess I would have to let it roll for the estimated 600 seconds, and then some in that case, right?
So, also discussing this elsewhere, if I have this correctly, I have to turn the PEC Playback OFF in the mount settings in Ekos, and activate the GPG RA Guider, enter my 600 second worm period in the Major Period box and deactivate the Estimate Period checkbox, correct?
Thanks for that info. On my CEM26, the worm period is listed at 600 seconds. Strangely, that data was only listed online and not in my CEM26 manual. However another strange spec listed is "Permanent PEC". I'm not sure what this means or if I have to be concerned about it. I just hope the mount isn't going it's own way with PEC all the time. The hand controller only lists 3 options for PEC, Record, Playback, and Data Integrity. I have not used this function, and I'm going to assume that "Playback" means activating PEC in the mount. Seems a rather clumsy approach to this.
So I'm just going to assume there is no active PEC going on in the mount and I'll enter 600 seconds in the GPG RA Guider Major Period box and deactivate the Estimate Period checkbox, correct?
...also, when temporarily disabling RA and DEC, do I need to disable the buttons underneath, or does that not matter?
Thanks for your reply. I'll try these out and see if it can show me if my issues are hardware related. I just got this CEM26,and so far only had 3 outings with it, and the plots have been like this. Although the mount was on concrete, itself on bedrock, there was significant traffic nearby, and I'm wondering if that was an external contributor. I will set the mount up somewhere more isolated for further tests, and I'll turn these function off and on and see what kind of results I get.
Thanks for your reply.
Well looking around online it appears I should NOT use the mount's PEC along with a guider. However in the Ekos guider I don't see the same settings options I see for PHD2. You mention the predictive PEC option, but I don't see where to set that. Also is there a guiding Assistant as there is in PHD2? There appears to be a lot of control parameters missing in the Ekos guider that's present in PHD2. Looking in the Ekos options, I see an option for an RA only set of controls called GPG RA Guider, although it's not clear to me what that is. I also see and option for DEC backlash in guide calibration, but how do you perform guide calibration, or is that something that just happens when I press the main GUIDE button?
I would rather not use PHD2 in Ekos, but I feel I need to run the Guiding Assistant for my mount, as my first forays with this new mount have given me insane plots, as you can see below. So I'm trying to get a handle as to what's causing these things, if they are internal to the mount, incorrect software settings, or if there are external variables causing this.
Thanks again for your reply.
Is it possible to use the PEC in my iOptron CEM26 along with the guider in Ekos, or PHD2 and it's PEC capability? I see conflicting info on whether it can or not.