Greg Beaton replied to the topic 'Synscan coordinates differ from those of the solver' in the forum. 7 days ago

kross wrote: I played with this some over the weekend. I changed the code so it sends RA/Dec instead of Alt/Az. The Dec axis gets updated just fine, but the RA axis wouldn't update. Not sure what's going on. I will have to mess with it some more.


By the way, I hope you guys can keep this driver compatible with the V3 hand controller because I discovered that older HEQ5 mounts cannot upgrade to the V4 version. Thank you for your work on this!

Read More...

Greg Beaton created a new topic ' Mount model not syncing lately' in the forum. 1 week ago

In my last two outings, I've had trouble with syncing the scope position with plate solve position. I goto a star and its pretty close , do capture&solve and slew to target but can't get a solution. I reduced the accuracy and then it would work but I noticed that the mount position on teh kstars map is not being updated(repositioned) to the target when syncing. Usually, a successful plate solve and sync or slew would put the mount reticle right on the target. Its not doing that now. I have to manually re-position the scope with NSEW controls, do a plate solve and see if the FOV reticle is where I want it. The mount reticle remains about 0.5deg off.

This problem seems to be co-incedent with a couple of updates - I've updated to 2.9.5 from 2.9.3 (on Mac and StellarMate) but I've also started using INDI (eqmod) mount connection shared with PHD2 running on the RPi.

I don't have logs right now. I'll have to turn them on and try again. I can try tonight from my balcony but without polar alignment. I don't think polar alignment is necessary for this to work properly.

Question: If I plate solve with the guide scope and sync, is this model kept separate from the main scope model?

Read More...

Greg Beaton replied to the topic 'ASI Camera - Gain/Offset/x-Bit' in the forum. 2 weeks ago

Maybe I lost track of the thread but the 50% was a reference to a question Helge had about an ASI guide cam setting.

Read More...

Greg Beaton replied to the topic 'ASI Camera - Gain/Offset/x-Bit' in the forum. 2 weeks ago

ElevatedG wrote:

HelgeMK wrote: Thanks a lot for sharing! Maybe the observation spot I am using for testing is too light-polluted?

When you say, fitsviewer auto‘s everything, do you mean the autostretch function is enabled? In my case it is disabled.

Could you kindly share also a screenshot with the „control“ settings of the asi drivers? Just that I can cross-check if I messed up accidentally any other parameter.


Helge,

Yes, I set kstars fitsviewer settings to include autostretch and occasionally debayer as was in that image. I included my settings page for both cameras. I hope you have better luck with the camera.

WHERE is everyone getting this gain of 50 for HDR on the asi cooled cmos cameras? I keep seeing post with that value included but it's not what Sam at ZWO states as Highest Dynamic Range (widest range of signal that the sensor can record) Cooled ASI Camera Settings


It’s not camera dynamic range you are trying to achieve. It’s star SNR. If you have high gain the bright stars with high SNR will be saturated. These are all trade offs of course so it’s also related to exposure time. Because you probably have to have longer exposures for guiding to smooth things out. You’ll have to turn down the gain. You can corroborate what I’m saying with PHD2 “best practices”

Read More...

Greg Beaton replied to the topic 'ASI Camera - Gain/Offset/x-Bit' in the forum. 2 weeks ago

andreas.d wrote: @ gbeaton:
I think this is a misconception. Calibration frames like bias or darks might be clipped on the left side of the histogram with offset 0. This could introduce artifacts during calibration.
jonrista.com/the-astrophotographers-guid...oise-and-histograms/
scroll down to "Anatomy of Signals in Histograms". The offset value prevents the "separation" of beeing negative.
Andreas


Yes, you could be right. I forgot to mentioned that as far as offset goes, I haven't studied it.

Read More...

Greg Beaton replied to the topic 'ASI Camera - Gain/Offset/x-Bit' in the forum. 2 weeks ago

I’m writing a guide on exposure and there are a couple of goals you can strive for in your settings. I won’t explain why for now as it will be in the guide.

One is to place the sky background peak at 2.2% of the full scale on a linear histogram like in fits viewer.

The second is to set your camera ISO/gain such that you have 11 stops/64 dB of SNR.

With regards to offset, I don’t see this as an important factor as any image will only have usable content above the background level, which is to be set at 2.2% as mentioned. So 0 offset is probably fine.

Read More...

Greg Beaton replied to the topic 'Internal Guider not calibrating' in the forum. 2 weeks ago

I put my asi120mm to gain of 50% unless theres a problem. I never changed the offset so I imagine its 0 or whatever the default is. Lowering the gain means you'll guide on brighter stars which have higher SNR.

Read More...

Greg Beaton replied to the topic 'Re:How to update telescope coordinates?' in the forum. 4 weeks ago

To get rid of cône error you have to physically adjust the seating or your scope in the mount. Check your manual for more. But a good 3 star alignment will help a lot.

Read More...

Greg Beaton replied to the topic 'Re:How to update telescope coordinates?' in the forum. 4 weeks ago

El Corazon wrote: Now I am thoroughly confused. How can a mount know where it is pointing to if it doesn't have encoders?

That being said, I am always seeing my Atlas Pro mount, which I gather is essentially an HEQ6, being off target by 2-3 degrees upon the first slew and then again after a meridian flip, whereas my low end iOptron SmartEQPro+ always nails the intended target almost exactly on the first try. I have the suspicion that one of my settings on the Atlas Pro is off, but can't figure out which one that is supposed to be.

Perhaps someone can weigh in on that.


They all have encoders. The earlier models have "relative encoders" and the later models have "absolute encoders". So the mounts like the EQ5 lose their position if you unlock the AZ or DEC axis. However, those like the AZ-EQ5 will not.

My friend has the Atlas Pro as well and he was having trouble with his pointing too. I think your issue is the time of year. The stars its selecting for 3 star alignment is not good enough. Its only covering half the sky. The 3 star alignment will only compensate for targets within the alignment triangle and for some reason the Atlas pro - synscan controller - is choosing the wrong stars for this time of year. You can add stars to your alignment - check your manual. Or select 3 stars that surround the whole sky you will be working in.

Read More...

Greg Beaton replied to the topic 'Kstars crashes on OSX' in the forum. 4 weeks ago

I've downloaded and ran simulators. things seem to be Ok. Thanks!

Read More...

Greg Beaton replied to the topic 'Kstars crashes on OSX' in the forum. 4 weeks ago

2.9.4 has issues on the Mac. Backup to 2.9.3 until 2.9.5 is re-released.

Read More...

Greg Beaton replied to the topic 'How to update telescope coordinates?' in the forum. 1 month ago

There's only one point that you can enter manually. That's the park position, which is assumed to be pointing at the NCP. (Some scopes allow you to set other positions like having the OTA horizontal in a stowing position but mine doesn't have this so I'm not sure how you tell Ekos that.) When you're scope is in this position, you can go to the "site management" tab of the mount in the INDI control panel, and click "current" and "write data". This sets the parked position to the present position and saves it. You're scope position should show AZ=0 and DEC=90.

Read More...

Greg Beaton replied to the topic 'Pentax K-5 capture failed' in the forum. 1 month ago

I just thought I would add some confusion...

I think the fits viewer is got some buffering problems. I was playing with the preview again because I wasn't understanding what was happening with the histogram display. So I was going from one ISO to another and frankly I couldn't corroborate what I was seeing with the settings. Also, I got the impression, looking at the histogram, that the fits viewer was adding two, even three captures together. Finally I closed the viewer and did a couple more previews and things appeared to be. This isn't a feature is it?

See in images two and three histogram peaks. This is because I left the fits viewer open and I went through 3 exposure settings.

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!