Kevin Ross replied to the topic 'EQMod default settings' in the forum. 1 week ago

After you change it to your desired rate, did you go to the Options tab in the EQMod driver, and click the Save button next to Configuration?

Read More...

I'm glad you got things working.

However, if it were me, I'd much rather use the guidescope and ASI120mm for polar alignment than a DSLR. The main reason is when it comes time to adjust the alt/az bolts, you want to loop images quite quickly, about 1 per second. I've never been able to loop images from a DSLR anywhere near that fast. Faster looping of images makes the polar alignment routine so much more pleasant. And don't worry about accuracy, the resolution of a guide scope with the guide camera is plenty high enough to get you a good polar alignment. If you're autoguiding, you only need to be within a few arc-minutes of "perfect".

Read More...

Kevin Ross replied to the topic 'EQ6-R PPEC - Questions' in the forum. 1 month ago

Yes, that is correct.

Read More...

Kevin Ross replied to the topic 'EQ6-R PPEC - Questions' in the forum. 1 month ago

That's mostly correct. But you need to enable PEC in the INDI control panel for the mount to actually use it. When you power the mount on, that feature is turned off until you explicitly enable it.

But yes, I used PEMPro in Windows, let it collect about an hour's worth of data, created the curve in PEMPro. Now here's the important part. It will ask you to save the curve to EQMod. Say no to that, it won't do what we want. Instead, in PEMPro, go to the PEC playback tab, and start playing back the PEC curve. Then in the EQMod control panel, expand it so all the controls are visible, and press the "record PEC" button on the far right side. That is how you actually upload the PEC curve into the mount's firmware.

Read More...

Kevin Ross replied to the topic 'Unit of HFR' in the forum. 1 month ago

Heh, my high school physics teacher used to always tell us, a number without a unit of measure is meaningless. Ekos is mostly pretty good about that (showing what the unit of measure is along with the number). PixInsight is terrible about that.

Read More...

Kevin Ross replied to the topic 'EQ6-R PPEC - Questions' in the forum. 1 month ago

Even though the driver is called EQMod, it actually has nothing to do with the Windows ASCOM driver by the same name. In particular, there is no place to put a PPEC file for the driver to use.

To upload a PEC curve to the mount, the easiest thing to do is to do it via Windows and PEMPro.

Unfortunately, when you clicked the button to record the PEC to the mount, all you did was record an empty curve (a flatline). This is because while it is recording, it is "listening" for guiding pulses, and uses those to create the internal PEC model in the mount. But because you had guiding output disabled, you didn't actually record anything.

Please note that using PHD2 to try to create a PEC curve will not be optimal. It will record all the noise resulting from bad seeing, etc. since it will only record for a single worm period. Software like PEMPro will collect data over many worm cycles, create a smoothed curve, and can then upload that to the mount (through the Windows ASCOM driver).

To add some confusion, the Windows ASCOM driver can do its own PEC, independent of the PEC stored internal to the mount. That's not what we want. We want the PEC to be stored in the mount, so that when we reboot into Linux for INDI, the PEC is inside the mount and will just work.

The messages about the PEC being disabled while guiding are normal messages, which should probably be removed (or turned into debug messages). When you have PEC enabled in the mount, guiding pulses can end up being ignored or truncated. So to overcome that, the driver will turn off PEC, send the guiding pulse, then turn PEC back on. Those are the messages you are seeing, and is nothing to be concerned about.

Read More...

I also get the same results. If I bin my guide camera 1x1 (ASI290mm mini) it usually takes a few seconds after receiving the image and issuing the guide pulse and taking the next image. Binning 2x2 does speed things up, but still takes at least a second.

I do find this to be a bit weird, since on the autofocus tab, with full field enabled, it takes a couple seconds to find all the stars when binning 1x1 on my ASI1600mm Pro. If I bin 2x2 or especially 4x4, it's extremely fast. So I would expect the guiding tab to find the stars pretty fast, since it is lower resolution than my imaging camera.

Read More...

Kevin Ross replied to the topic 'KSTARS/EKOS for Windows issue' in the forum. 1 month ago

Sounds like you have a good workaround (revert to 3.5.4).

There are a couple things you can try.

1. Do you have a guidescope? If so, try using that for polar alignment instead of the Canon.
2. Try different plate solvers. Instead of the internal solver, try ASTAP, for example.

Read More...

Kevin Ross replied to the topic 'Relays for shutter release' in the forum. 1 month ago

Yes, but you still need the build tools and INDI headers. For your particular driver, you would create a build folder, run cmake (with the path to the source files), make, and make install.

You should be able to follow the instructions here: github.com/indilib/indi-3rdparty

See "Building individual 3rd party drivers"

Read More...

Kevin Ross replied to the topic 'Relays for shutter release' in the forum. 1 month ago

Well, I might not be the absolute best person to answer. I'm a software engineer of over 30 years. So what seems quite simple to me might not seem simple to you.

But, basically just install the build tools, the INDI headers (libindi-dev package), grab the indi-3rdparty from git, do the usual cmake; make; make install routine. See? Easy! :)

Read More...

Kevin Ross replied to the topic 'Relays for shutter release' in the forum. 1 month ago

I think I may have led you down the wrong path. I think the driver will try to complete the exposure and download the image before it considers the capture to be complete, and therefore running the close shutter script. But, the close shutter script must be run first, before the exposure can be completed and the image downloaded.

So I don't think that will work. :(

Your best bet is probably to modify one of the existing drivers to match the relay hardware you have.

Read More...

Kevin Ross replied to the topic 'Relays for shutter release' in the forum. 1 month ago

There's an alternate method you might want to look into. In Ekos, on the Capture tab, towards the bottom right there's a button titled "Scripts Manager". Click that button. There you will see pre-capture script and post-capture script. I think you can create a "startCapture.sh" and "stopCapture.sh" script in your home directory, where you execute the usbrelay commands necessary.

Read More...