ok just tried taking darks, dark flats and biases and didn’t get a single prompt to cover my camera lens. I’m sure I have in the past.
The camera took all the images using the shutter. The biases at an automatic speed supposedly of a blistering 1/32000 which I would have thought is faster than the camera can go.
Tried doing darks using the dark library with the same result.

The indi device log gave a warning saying my camera had no shutter and I needed to cover it.

Read More...

@Peter I’ve wondered about that in the past and for some reason didn’t think it kept the shutter closed. Will have a play as that would be great.

@Jasem If Peters suggestion doesn’t pan out I will give that a go. Couldn’t the dark flats just follow the same type of process that darks follow and ask to cover the telescope? NB I currently tend to set things to take a batch of images and then sit and wait rather than set up a whole set of things so I’m not sure if that happens with darks when there’s a set of jobs

Thanks

Nigel

Read More...

Hi

not sure I’m going to help here but I run kstars/ekos on a 4gb Pi using Astroberry so currently 32 bit. I have a sony a7rii so using a gphoto related indi driver. Camera takes raw but transports it in fits format. I’ve got a large chunk of the index files installed and when stellarsolve runs it appears to check and then says it cannot load in parallel but continues and solves pretty quickly. So unless there’s some weirdness around having 8gb I would have expected it to work.
Have you tried using the astap or watney based solvers to see if they work? They have their own index files and internal star finding routines.

I seem to remember reading somewhere that it’s pretty simple to set the linux kernel to be 64bit even without having to have all the programs converted over. Didn’t look to be any help for me given i’ve only got 4gb but might be worth investigating but then you should be working fine anyway…


Regards

Nigel

Read More...

Hi
I’m just at the point in my learning curve where I’m trying to improve my calibration frames.

From what I can tell for a cmos based camera (in my case a sony a7rii) I need darks, flats and dark flats (rather than biases). So I’ve got myself a light panel and have used the flats wizard to take flats around 8000 adu. Camera is 14 bit so I believe I need to have values around that and the frames captured seem ok.

Having done that I thought I would get the other wizard on the capture tab to add dark flats to the job queue after I’ve added flats. It works adds the dark flats to the queue, then I set it going, it works out the exposure takes the flats and immediately starts taking the dark flats. However there is no pause between the two to enable me to make things dark.

Is there some way of putting in a pause between the two jobs ? Or is there something I’m missing?

Regards

Nigel

Read More...

Nigel Dunmore replied to the topic 'Fits viewer questions' in the forum. 1 week ago

Hi Paul

The sv305 driver has an option to basically bit shift the 12 bit reading it gets to 16 bits. However I’ve not seen such an option in the sony dslr driver.

If what you say is true then something else appears to be wrong as I’ve yet to see any of my images pass 16384. I’ve looked at them in fits viewer stats and astroimagej.

The 3d plot in astroimagej of my flats shows a nice dome shape due to vignetting. However the ones I took using the t-shirt method showed a flat area in the middle compared with ones taken with a led panel. To me this indicates overexposure and this again occurred at 16384.

The cameras in your sig both appear to be ccd and look to be 16bit. Do you have any images from a cmos 12/14bit camera where they have been multiplied up?

Regards

Nigel

Read More...

Nigel Dunmore replied to the topic 'Fits viewer questions' in the forum. 2 weeks ago

The sony is definitely 14bit. I’ve had a look at a few of my lights and the centres of the stars hit no more than 16384.
I’ve now tried an led light panel and tried the auto flats function which gave an exposure of approx 0.6secs for an adu of 8000+-1000 and that seemed to give a nice mid range exposure.

If the saturated level is hard coded to 65000 then I think it would be pointless for dslr type cameras and probably a lot of others. Perhaps if it cannot get the actual setting from the driver perhaps a setting for the viewer or a guess based on a maximum showing up equivalent to 12, 14 or 16 bits could be used.

Read More...

ok I’ve now got an led flat panel by the magic of Amazon.
I tried the auto flats option in ekos which came up with an exposure around 0.6 sec and also manually using aperture priority which gave 0.07 secs. Both came out with pretty similar distributions of pixel levels.

I still had first exposure out of the 10 or so I did hit 16384, the rest seemed fine.

The interesting/learning thing was that I used AstroImageJ to inspect the images using a 3d plot and found that my old flats where over exposed in the middle. You could see the dent of it hitting the limit in the middle of the dome of the vignetting. The new ones were a nice smooth dome which didn’t get flattened by hitting the limit. Expect that will make a difference to the final images.

Read More...

Nigel Dunmore replied to the topic 'StellarSolver FOV calculation' in the forum. 2 weeks ago

Hi Greg

just a slight side question. Those frame settings are they your cameras real resolution? I ask as my sony in aps-c mode seems to have similar settings and they aren’t the ones I set and from a quick google of your camera it looks like they aren’t correct for the 60d

Thanks

Nigel

Read More...

I’ve found my sony a7rii seems to go into what may be a sleep state where it won’t show anything on its back screen no matter which buttons I press. Using ekos to take a picture seems to bring it back to life.

Read More...

Hi Paul

yes it is rather faster than I was expecting. I’ve tried this on both blue sky and cloudy sky days with similar problems. Did wonder if it was shifts in brightness due to clouds but it just seems so random, rapid and extreme. Most shots are showing similar stats but every now and then there’s these jammed up at the limit.

Currently on the initial part of the learning curve about these things but can see the impact of flats so want to try and get these right. Biases I can vaguely understand but I’m not yet at the stage where I notice much change to my images, darks just seem a pain. Given the changes from people using ccd to cmos and the comments people make I do wonder which are worth the effort though definitely flats are.

I’m going to look for a light panel, tried holding an ipad in place but it’s just to awkward as I’m using that to control things.

Regards

Nigel

Read More...

Nigel Dunmore created a new topic ' Fits viewer questions' in the forum. 2 weeks ago

Hi

I’ve been taking flats and am getting a bit confused by the fits viewer.

When the stats show 16384 (my camera is 14bit so I believe that’s the maximum) for my images surely that means that the pixels are blown out? If it’s that for the averages, minimum surely the whole image is so why is it only a lighter grey? Is it rendering things to the equivalent of 18% grey?
If I click on the red button to show pixels that are saturated I’m not seeing anything change on either my 16384 flats or on star images with some pixels at 16384. Could someone tell me what’s supposed to happen in case I’m missing something please?

Also the histogram doesn’t always look like it’s updating between images and seems inconsistent with what is being reported in the stats. Is there some way of zooming in so I can see whether the exposure is up against the left edge or not and what is the bottom scale in?

Sorry for all the questions just happened to be a clear night (well what passes for night in the uk at this time of year - more like dusk at 1 in the morning:) ) so had ended up actually trying to take some pictures rather than just reading about taking pictures….and then the questions came…



Regards

Nigel

Read More...

Hi
I’ve been taking flats using the t-shirt over lens and pointing at the sky method, however the exposure varies quite strangely between shots. Most of the time I get images with the max and median values down in the low thousands and minimum down in the hundreds but sometimes I get ones where the values seem to be maxed out pretty much at 16384 (14 bit camera). I’m taking the images at 0.001 secs exposure with a sub second download time so I don’t think the sky brightness is changing that rapidly to cause this.

I also seemed to have similar problems determining a suitable exposure to actually take them at with a seemingly random correlation between exposure time and the statistics in the fits viewer.

This is using a sony a7rii camera connected to an astroberry running the latest kstars.

Has anyone noticed this with their setup?

Regards

Nigel

Read More...

I thought I would check. If you hover the mouse over that Device entry it says it will lock it to the name, the permanent mac address or both. I’ve sort of taken that setting it to wlanX (aa:bb:cc:did:ee) that I’ve ended up with the particular device with that mac address being given that name and used for this network setup. I could be wrong and maybe I should just use the mac address though I’ve not had an instance where the networks haven’t worked (excepting the usual flakiness )
If you want set names you can enable predicable network names using raspi-config then use those to tie the device to you network config.

Read More...

Yep that’s the setting I rather randomly changed :)
I also use zram/zswap for swap and even used tmpfs for /tmp (though ran into problems due to temporary files building up when doing plate solving). This all on a 4gb PI. I don’t think I’ve run out of ram and only ever had minimal swap usage so kstars/ekos isn’t exactly eating all the memory. That said I’ve only gotten things all working recently so have only taken around a hundred images in a session.

I used to have more problems when I used to take larger resolution images (with the same camera ) but stopped using the fits viewer all the time, switched off the notification sounds, changed to aps-c resolution and applied lots of updates which seems to have ‘cured’ that.No idea what it was though as it was quite random :)

Read More...