Jarno Paananen replied to the topic 'Internal Guider not calibrating' in the forum. 1 month ago

I don't think it has ever worked better for me than it does now (which isn't perfect but usually enough), it was much worse before Robert's changes some time ago and I've used PHD2 with Ekos for about two years now. Anyway, it would be nice to figure out the issue and fix it for sure :)

Read More...

Jarno Paananen replied to the topic 'Re:Joystick input stops tracking' in the forum. 1 month ago

One thing to notice is that there is backlash also in the RA axis so tracking might not be immediately visible after slewing east until all the gears come into contact again.

Read More...

Jarno Paananen replied to the topic 'Internal Guider not calibrating' in the forum. 1 month ago

Unfortunately this doesn't have any direct impact on dithering with PHD2 as such, only that the dither pulses would be more accurate than before. For me dithering seems to usually work, though at times Ekos doesn't seem to register settling signal after dither, but resumes after timeout anyway. More rarely PHD2 doesn't seem to receive the dither command from Ekos at all so there seems to be some fragility with the communication between the two.

Read More...

Jarno Paananen replied to the topic 'Internal Guider not calibrating' in the forum. 1 month ago

I use HEQ5 Pro with EQDIR-BT dongle with PHD2 and have recently made some changes to EQMod driver for this purpose. The original code didn't take into account communication delay with the mount which is around 50ms per command when using BT and around 16ms when using EQDIR cable and 32ms when using PC Direct mode via the hand controller. This made each pulse essentially that much longer. Also the code used timer for all pulse lengths which made short pulses quite unreliable. Last issue was that if mount status query timer happened to hit during the pulse duration, the pulse got significantly longer as command to end the pulse got delayed. These issues should be remedied by current EQMod driver version from nightly which added configuration items to ignore very short pulses and configurable limit how long pulses are handled synchronously. The value for minimum pulse should be around the communication delay so 50 ms for BT, less for wired connection, the default value of 10 ms is very conservative. Default value for timer threshold (100 ms) is probably good as is, but I've used slightly longer 150 ms as the limit myself.

As for the guide rate I've settled on 0.5x after testing 0.3x, 0.75x and 1x, it seems to be a good compromise between correction speed and not over correcting. I'm not sure what you mean by minimum pulse rate, I use 3s exposures so PHD2 does corrections only every 3s to average out effects of seeing. Sometimes I use 2s or even 1s, but 3s has proved to be good compromise.

Read More...

Jarno Paananen replied to the topic 'Re:Twilight altitude setting' in the forum. 1 month ago

No, not meridian, I mean specifying if the limit should apply both when starting (dusk) or ending (dawn) or both, currently it's always both, so the sequence doesn't start until it's dark enough. My use case would be that I want to start the sequence (usually repeating) asap when I'm setting things up and it might still not be astronomical dark, but then I'd like it to stop at - 6 degrees for example (civil dawn I think). Currently I have turned twilight check off and specified end time manually, but that was a bit cumbersone when the day shortened by 20 minutes each day around equinox :) Also specifying time isn't as useful in some cases as the degree as duration of dusk/dawn varies. But it might be a good option as it's possibly easier to understand than how low sun must be.

Read More...

Jarno Paananen replied to the topic 'Re:Twilight altitude setting' in the forum. 1 month ago

Yes, or just setting to select if the limit applies to one or both.

Read More...

Jarno Paananen replied to the topic 'Re:Twilight altitude setting' in the forum. 1 month ago

This would be very useful here in the north where at the moment we don't have astronomical darkness at all :) Also in some cases it might be useful to be able to start the job asap in the evening but still have twilight as abort condition in the morning.

Read More...

Jarno Paananen replied to the topic 'Mirrored Fits : Fits header missing order information ?' in the forum. 2 months ago

Yes, this is a problem with FITS as there doesn't seem to be a standard keyword to indicate which way the image should be, which is why PixInsight for example has configurable orientation. Looking at the source it seems Siril unconditionally flips the image, which is also the default with PixInsight as it seems to be more common. INDI just dumps the data to file and most cameras have origo at top-left so the image ends up flipped in these programs.

Read More...

Jarno Paananen replied to the topic 'Flip-flat Automation?' in the forum. 2 months ago

I don't have Flip-Flat myself, but similar device called Gemini SnapCap and it works very well. Ekos closes it when I want to take darks and controls the light per filter for flats. I have 7nm Ha filter and with maximum brightness I use around 12s exposures. For narrow band filters I've set brightness so that I can use 3s exposures due to the mechanical shutter of my Atik 383L+.

Read More...

Jarno Paananen replied to the topic 'Help communicating with focuser' in the forum. 2 months ago

USB_FocusV3 device is a bit problematic from communication protocol point of view as it doesn't have start-command sync characters like most others and relies on the fact that all commands are six characters long so it gets out of sync if someone writes anything to it before the INDI driver sends SWHOIS command. I had the same issue with ModemManager writing some AT-commands to the port even if it was supposed to ignore it with the udev-rule and only removing ModemManager altogether stopped that. In my own version of the driver I added some hacky code to send space characters to the device until it gives an error to achieve sync if the initial command failed, but that is not really a good solution either. You can also do that manually with minicom or similar if you want to try.

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!