Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - dansawyer

#1
The issue was focusing. The lens is a Canon 200mm macro FD. The camera is a mirrorless M1. The adapter matches the FD to the M1.
The mount is a Ioptron tracker. It was reasonably aligned to CNP using the polar scope and a Polaris position app.
The system appears to focus beyond infinity. Using the 10x feature on the M1 I carefully focused on Deneb at f4. That was touchy, there was a definite halo on Deneb. I then stopped down to f5.6 and proceeded to take 40 50 second images. This was a test, no dark or bias images were used.
The result was actually very impressive for a first try. I stacked the images using siril. There were hot pixel track in the final image.
The M1 worked very well. I am looking for a how to to finish the color processing. The M1 raw image from the original question is answered. Thank you all. Dan
#2
Thank you both. As follow up, after reading the comment I tried again. I carefully mounted the camera and very carefully focused a bright star at 10x. The camera is an M1, the lens is a Canon 200mm f4 macro. The mount is an Ioptron Pro. (I am really impressed with the performance)
I focused at f4 and then stopped down to f5.6. I set ISO to 800. That seemed to do the trick. Focusing was difficult and definitely touchy. The focus display definitely show halos on the stars. I was able to complete about 40 images of 50 seconds each.
I was centered on North American Nebula.
I looked for options to attach a file but could not find the command.
#3
The camera is a Canon M running Magic Lantern. I am taking pictures with a Canon 200mm macro. Stars appear sharp and 1x. At about half full magnification on the display all stars including dim ones begin to show area. At full magnification all stars including dim ones show a definite circle. No stars are points.
My question is are there Magic Lantern settings that effect star sharpness or size on the M? I would like to adjust the image for the sharpest values. Thanks Dan
#4
Use of astro.mo
I was able to compile and install astro.mo. Last night I tried to test it and have a couple of general questions.
First, it generally worked. I was using a an EOSM and a 90 mm fl f4 lens. This may be short for the module design target, but I believe the fl should not matter significantly. The issue above of the red background oscillating in and out did not occur in actual use, only in the menu screen.
First, the number of visible stars was very limited in the display. I was aiming generally West and chose Vega around 3 AM. Other stars did not show up in the field. Is this the general experience or on there something I am missing? Should I use EV display amplification? Will that distort the operation by creating noise?
Second, the actual focus display seemed to vary quite a bit on its own. That is the min bar would move to null then up several bars, then back down. This variation seemed to be on the same order of magnitude as changes in focus. Is this normal? Is there an error in my testing? Is this the result of a relatively short fl lens. 
I am looking forward to testing this on my Celestron 9.25.
#5
Thank you for the pointer, long exposure noise reduction does indeed appear to be the culprit. I am using ML and the intervalmeter feature. What appears to be happening is when a program is set up in intervalmeter and long exposure noise reduction is set the camera appears to take a time out to preform long exposure noise reduction.
While the camera is performing LENR the screen is displaying "BUSY". The intervalmeter appears to be suspended.
I did a test with LENR both on and off. When it was on the screen flashed busy for close to the length of the exposure. When this was complete the intervalmeter program seemed to restart where it was 'suspended'.
When LENR was off the math behind the take a picture every and the exposure length worked as documented.
The take away is LENR seems to insert a timeout from the intervalmeter.
#6
The camera is an EOS M1 and the application is astrophotography. After several attempts I have the basic operations in place and astrophotography is working. There is a remaining question; DOF settings remain active and there is a settable variable remaining "Circle of Confusion". The value is in um. The camera is in manual mode and the focus is set to infinity. Exposures are long, typically 30 to 90 seconds. The range of values are 1 um to 100 um.
In this case what is the effect of changing the Circle of Confusion value in astrophotography?
#7
Quick update:
First thank you for the build chain. That worked smoothly and produced a zip w/o errors.
The zip file was unziped and the files copied to the SD card from an EOS M, firmware version 2.02.
The files copied were: autoexec.bin  and ML-SETUP.FIR. The ML directory was also copied.
The SD card was moved to the camera and the firmware was reloaded. The instructions were followed.
Module info showed the build time and system consistent with the build. This is reasonable confirmation the build and firmware load process worked.

One quick observation, when the color scheme is set to red the display flashes periodically to normal.
#8
Thank you. When running an intervalmeter sequence there are 4 displays on the screen:
1. The count down to starting the intervalmeter.
2. The display when the shutter is open.
3. The image after the exposure is taken
4. "BUSY" is displayed on the screen.
What does "BUSY" signify? What causes it to be displayed?
#9
This may be redundant. After reading the thread carefully there is a July branch uploaded. It says to download with:
hg pull && hg update astro_photography_module
However this generates an error: abort: no repository found in '/home/dan/downloads' (.hg not found)!
How can hg be configured to identify the magic lantern repository?
Is there a way to download the branch w/o using hg?

Follow on: I copied the files with cut and paste :( then removed the leading + with sed and compiled. (yes the kluge award for the day )

Is this error significant:

Not checked (compile ML for these cameras first):
    1100D, 500D, 50D, 550D, 5D2, 5D3.113, 5D3.123, 600D, 60D, 650D, 6D, 700D, 7D, EOSM
make: *** [../Makefile.modules:82: astro.dep] Error 1

I am using an EOSM version 2.02


#10
I have been using ML off on for several months. There appears to be a change in the intervalmeter operation.
The change is in the relationship between the 'take a picture every time' setting and the exposure time. The original operation seemed to be the 'take a picture every time' setting had to be greater than the exposure time value. That seems to have changed. The take a picture every time value now appears to operate as a delay between the end of the previous photo and beginning of the next shot. I am using ML is astrophotography so the exposure times are long, bulb values of 1 to 2 minutes. Is there a configuration variable that controls the operation of the 'take a picture every time' setting?
#11
Attempts to compile the source result in:
../../src/module.h:344:28: fatal error: module_strings.h: No such file or directory
Is there a resolution to this error?
Is there an alternate source for this library?
There is library strings.h. Is this equivalent?

This was resolved by loading python docutils and adding the following to the path:

PATH=$PATH:/home/extended/downloads/gcc-arm-none-eabi-6-2017-q2-update/bin/