Get Connected!

Come and join our community. Expand your network and get to know new people!

Sorry, we currently have no events.
View All Events

Full run via scheduler last night from park to park and all parts executed but not as expected - THIS IS WIERD
1) Normal start - unpark...slew...focus....align...capture HA no issues
2) change filter to OIII no issues
3) Guide (@Hy) is all good at this point

4) at  correct time flip is pending - flip executes and takes the normal time based on my slew speeds
5) align happens and says complete - see first attached image - THIS IS NOT THE SAME TARGET
6) at this point there is no guiding - 00:31:44 Autoguiding aborted - which is right at the flip (good) - but no reason for it to STAY aborted - it should have resumed
7) at this point I have a few hours of unguided images in SII on an unknown patch of sky.....and THEN
(yes this is the weird part)
8) at 04:57 am the system decides to focus again on SII and THEN perform an align (3 iterations) - it is GOOD and back on target AND guiding kicks back in AND I am suddenly focusing on OIII
9 ) the system manages 1 final image in OIII with a flipped target properly centered and the image is in focus and well guided!

The 3 images here show the analysis window  and logs are attached - but WOW and WHY - the strange operation - funny thing is each function can operate but to suddenly align after 4 hours? 
Full run via scheduler last night from park to park and all parts executed but not as expected - THIS IS WIERD
1) Normal start - unpark...slew...focus....align...capture HA no issues
2) change filter to OIII no issues
3) Guide (@Hy) is all good at this point

4) at  correct time flip is pending - flip executes and takes the normal time based on my slew speeds
5) align happens and says complete - see first attached image - THIS IS NOT THE SAME TARGET
6) at this point there is no guiding - 00:31:44 Autoguiding aborted - which is right at the flip (good) - but no reason for it to STAY aborted - it should have resumed
7) at this point I have a few hours of unguided images in SII on an unknown patch of sky.....and THEN
(yes this is the weird part)
8) at 04:57 am the system decides to focus again on SII and THEN perform an align (3 iterations) - it is GOOD and back on target AND guiding kicks back in AND I am suddenly focusing on OIII
9 ) the system manages 1 final image in OIII with a flipped target properly centered and the image is in focus and well guided!

The 3 images here show the analysis window  and logs are attached - but WOW and WHY - the strange operation - funny thing is each function can operate but to suddenly align after 4 hours? 
I guess the main issues are 
1) why did align successfully align on nothing and then suddenly after 4 hours do another align and actually get the target
2) way did guide never resume after the flip/align at 12:30 am but suddenly start again at 5:00 am

Any insight would be helpful 
This is master branch build as of last Friday (sept 10) - beta 3.5.5 

File Attachment:

File Name: log_20-23-41.zip
File Size: 2,861 KB



  

Read More...

Julian created a new topic ' Canon EOS M3' in the forum. 1 hour 10 minutes ago

I am having trouble to get the EOS M3 working with Indi/Ekos. The Camera is officially listed as supported  by Gphoto. I can get the camera to capture an image over the command line when the shutterspeed dial is set to bulb on the camera:
<code>gphoto2 --capture-image</code>
Over the Indi Control Panel I could not manage to capture a picture. The camera does not show any reaction. I can set properties like the the capture target over the command line:
<code>
gphoto2 --set-config capturetarget=1
gphoto2 --get-config capturetarget
</code>

I noticed however that the camera crashes when I try to update the shutterspeed over the command line with:
<code>
gphoto2 --get-config shutterspeed
gphoto2 --set-config shutterspeed=1 [crash]
</code>

The camera always returns 30 sec indenpendent of the setting on the dial. 

Under the Indi Control Panel I believe I tried every possible combination of "force bulb", "capture target" and "transport format". The Indi log shows depending on the settings either simply "[ERROR] Failed to expose." (for a bulb exposure) or "Error downloading image from camera: Directory not found" (when doing a preset exposure). A Warning is displayed, that a mirror lock time should be set, but setting this time does not change anything nor does the camera have a mirror lock to my knowledge.

Did somebody manage to get the EOS M3 working with Ekos/Indi or has some advice what else I could try to track down the problem?

I have libgphoto2 and gphoto2 2.5.27 installed. So far I tried different settings on a 64 bit Linux system and on a 64 Bit RPI4 system. Capturing with the guide camera works.

Read More...

Probably yes, but blind solve is much better than no solve at all. 
​​​​​​ I always use sync option and I see if solve is near my target.

Also internal solver does not work at all, but I do not care too much as online is working. 
 

Read More...

I thought updating sdk manually was good and resolved some issues. Good to know it's better not to do it!

Read More...

@Jasem Is there a bug/wishlist item to make this work for remotely stored images? As I mentioned in my previous post, where does the Analysis tab gather the info to figure out that a capture has been done and could this same info be used as the basis for the scheduler to figure out the same info??

Read More...

Updates of binary drivers come along regular updates with apt . No manual update is needed nor recommended

Read More...

Would that do a blind solve?

Read More...

Is that the equivalent of doing a blind solve?

Read More...

Hi all,

I want to create a cloud/rain detection system with a MLX90614 infraredsensor. When pointed at a clear sky the temperature read is far below zero celsius. As soon as clouds move in the temperature rises considerable.
I want to create with arduino a utility that sensors a rise in temperature, indicating clouds, and shutting down the observing session. Parking the scope and closing the roof of my ROR.

Has anybody tried this or sees any difficulties?

Regards,

Joshua

Read More...

Hi all,

I've been using Kstars/Ekos via Astroberry on a Rpi4 for a while now with my DSLR etc and all is going fine.

I've just upgraded to a QHY294m-pro. Ekos can connect to the QHY camera but i have a question about its drivers. 

In the general info tab, the sdk shows 21.7.3 (see image) but i know the recent QHY SDK is 21.09.10. Should this be updated? How do i go about updating this if needed?
Also how do i know if version 2.8 and interface 2 is the most recent and if i need to update that too?

Any help would be greatly appreciated.

Cheers

Read More...

My club has a Meade 14 GPS scope permanently mounted and aligned on a equatorial wedge in its observatory.  I've been using Stellarmate on an EQ6 and a refractor, so I'm hoping it will be a simple switch to this scope and mount.  I got a USB-RS 232 cable, which connected right away.  My problem is that when I try to sync the mount to my KSTARS position, the scope indicators moves to the right position, but then immediately jumps far away - maybe 6-7 hours of RA.  My guess is that the GPS is conflicting with KSTARS in some way.  I'm wondering how to fix this problem.

I pointed the scope manually, and guiding worked well.  It calibrated quickly, and was able to track well, even at the 3600mm focal length.  (I was using an Off-Axis Guider for the first time, so it was a pleasant surprise when it worked right away.

Any suggestions on how to fix this?  I'm wondering about some way to disable the Meade's GPS and just do everything from KSTARS.

Thanks.

Read More...

I have reviewed the datasheet. The USB is disabled by default, to enable it I need to add a line in /boot/config.txt

dtoverlay=dwc2,dr_mode=host

Read More...

Just a quick note... I to found when I went to powered hub (USB 3, 12V) pretty much all my connectivity issues with the Pi cleared up. Except one. If I had my imaging camera (Fuji X-T3 at the time, USB 3) and my guide camera (ZWO 120mm mono, USB 2) plugged into the hub only one worked. Trial and error lead me to leave the guide camera plugged into one of the Pi's USB ports. The imaging camera and all othe USB devices remain plugged into the hub.

Read More...

Hardware is another question, indeed
(btw : Asiair contains RPi CM with additional board and original OS is Raspbian)

 

Read More...

And good point about the false positives, it could be that the evening sun casts some rapid shadow movements since it shines through the tree.

Read More...