Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,681
  • Joined

  • Days Won

    133

Everything posted by astroman133

  1. Peter, One nagging issue that happens very rarely is that one of the BYE configuration files becomes corrupted and prevents the app from starting. The way to fix it is to re-install BYE to a different folder location. I hope this helps.
  2. Oh, thanks. I kind of expected that it would be a step that you could add into a plan, to automatically park the scope after shooting lights.
  3. He means that he can't find the Park control in the updated version. I saw it when I ran BYE for the first time after upgrading to 3.1.4, but now I can't find it either, even when I connect to a scope. I thought that it was a hyperlink beside the load and save capture plan links below the capture plan, but it was not there when I ran it today.
  4. .NET 3.5 is installed with Windows 7, by default, but for whatever reason Microsoft decided not to install it. That is something that you need to do via Programs and Features in the Control Panel. This may not have been your issue since having .NET 3.5 not active should have prevented BYE from running at all. Anyway, I am glad that you are now working!
  5. Please provide the correct camera model. What version of Windows is on the PC that the camera is not connecting to? Some Canon models will only work on a 32-bit version of Windows. What version of BYE are you using? You say that Windows recognizes the camera, What model does it recognize? Are the USB ports using version 2.0 or 3.0 of USB? Are you sure that the combination of camera and cable work on other PCs? Does Canon's EOS Utility connect to the camera on the system where BYE does not connect? Answering these questions will give Guylain and the rest of us more information to help you troubleshoot your issue.
  6. You need to use both cables. The DSUSB cable is for BULB exposures, the other cable is for everything else. Did you set the Cable Support dropdown in the Capture Plan center???
  7. astroman133

    Loading an avatar

    I tried to upload a picture and it did not work (the image that was apparently uploaded did not replace the silouette or allow me to crop it.
  8. The errors are several seconds apart. What are you trying to do when you get those errors? Did you extract only the errors from the log to paste into your post? If so, they are out of context for what BYN was trying to communicate to the camera. Some errors may be normal when BYN is initially trying to determine your camera's capabilities. Is the camera connected to a telescope at prime focus or does it have a lens attached? Only the latest version of BYN (1.0.2) has the ability to download images to a PC AND save image to the camera's memory card. And, this capability only works for some cameras due to irregular support from Nikon. Do you have mirror lock disabled in the camera? You should not need a serial cable for BULB. Providing more information will help you get a quicker reply/resolution of your issue!
  9. I agree. There is something else going on. The battery should run the computer or not, depending on it's ability to provide the necessary power. Lack of power should cause the laptop to shutdown, not cause communications glitches or CPU overload.
  10. The left-most number is the position of the absolute focuser and the number in the center is the temperature, in degrees Celsius, of the focuser, if the focuser reports a temperature. The right-most number is only visible when you hover the mouse pointer over one of the movement buttons. It is the amount that the position will be adjusted when that button is clicked. If you look closely you will see some vertical text labels beside the first two numbers. They are "Absolute" and "Temperature".
  11. Your are the only person who has reported issues with BYE and Windows 10. In fact, as posted in this topic -- http://www.otelescope.com/index.php?/topic/1078-windows-10-and-bye/?view=getnewpost -- Guylain just finished testing the latest BYE with Windows 10 and experienced no issues. BTW, nobody calls the programs BackYardDSLR. There is BYE and there is BYN. Also, not sure what you mean by Microsoft, Canon, and Nikon getting in sync. All three vendors release things independently. If you have a BYE issue with Windows 10, perhaps you should post a new thread in the BYE forum and explain exactly how the software is not behaving as expected. You seemed to be saying that images captured with BYE are not downloaded and displayed on the screen and are not in the Download folder. Also I am not sure what you mean by "nor are images imported into the BYEOS image thumbnails/viewer screen". Can you explain exactly what you are trying to do and what you are seeing? By import do you mean drag and drop images while on the Preview tab is not working? Thanks,
  12. Geoff, Do you have Long Exposure Noise Reduction turned on in the camera?
  13. Is the fix in the recent release (BYE 3.1.4), or will it be in the next release?
  14. If you really want to use your 20D, you could try running 32-bit XP in a virtual machine.
  15. $1000 may be a decent downpayment for a CCD camera, or for the high end Canon or Nikon DSLRs. I spent closer to $5K for a QSI 583wsg with 8-position filter wheel, 7 Astrodon filters and an SBIG STi guide camera. So, if that is all you have to spend, I would stay in the DSLR realm and continue looking for a heads up comparison of Canon and Nikon prosumer cameras when used for AP. When cooled down to -10 degC my QSI is extremely low read noise with virtually no pattern noise (horizontal or vertical banding). I hope that BYE and BYN get autofocus capability before seeing BYCCD. I have no doubt that the user interface for BYCCD would be first rate, but there are already lots of apps for controlling CCD cameras, which are much simpler to control than DSLR's, IMO.
  16. First, the 20D is an older camera so you have to choose the camera group on the left before connecting. Then it will only work with a 32-bit version of Windows (see the Camera Support Grid), because there is no system-level driver on the 64-bit OS's. The 70D is fully supported with LiveView and Bulb exposures with only a USB cable on all versions of Windows since XP. For the 70D you have to select the camera group on the right before connecting. If you have a 32-bit OS and are selecting the correct camera group when connecting but still won't connect, you should make sure that you are using a good USB cable. What version of Windows? 32-bit or 64-bit? Did you try to connect your cameras during the trial period? Have you ever been able to connect?
  17. I misunderstood what you were saying in the previous post that I responded to. Perhaps I am wrong, but I do think that what Guylain is displaying is all of the data that is available from the LiveView stream in the main window. Then he is extracting a rectangular area of pixels that roughly corresponds to the zoom box and he is simply displaying those pixels in the other panel in BYN, and letting the GDI rendering engine scale them to fit. So it is the same pixels just displayed in a larger area (no more details). What you are suggesting is that it may be possible to get that same rectangular region-of-interest area, but at a higher resolution, via an SDK call. That would be cool. I don't think that this is available from the EOS SDK. I don't regularly use a mask for focusing. I prefer the numeric metric, usually the HFD. However, with my Canon, I have had no problem getting focus with a mask or with the HFD. I stopped using the mask when I discovered it was only confirming what the metric was telling me.I understand that the camera scales down the image to display on the LCD. It is this scaled down image that BYE gets, and I assume BYN from a Nikon. The data from a LiveView frame is not very bright, but still suitable for using a mask or metric to reilably focus. I would assume that it is also possible with BYN, but it may be best for one of the BYN users to comment.
  18. I am not familiar with the Nikon SDKs so I don't know whether the LiveView image is available at a higher resolution that what BYN is displaying, However, I would be pretty confident in saying that BYN is calculating the focus metric value based on the array of pixels that were downloaded from the camera, so however the image is zoomed would have no effect on the calculated result. If you zoom in enough on any image you will start to see pixelation. It is possible to mitigate that by processing (upsampling) the image. This may be what the other camera control program is doing and while this would lead to a more pleasing image, it would affect the calculated star size when done on an astrophotography image. The difference between the displayed images could also be that the OSX is upsampling and Windows is not when displaying the image at a particular size.
  19. dts350z is correct. Using a DSLR for narrowband imaging will require very long exposures, since the filter is passing only a small fraction of the total light. There should be no other special considerations during capture. Except that if the filter is a clip-in filter, focusing can be a major pain. You can get close to critical focus without the filter, then you have to dismount the camera, insert the filter, and remount the camera. You then should re-adjust the focus, but you need a star that is bright enough in the narrowband wavelength to focus on. This most often means that you will not be able to use LiveView, but instead will have to take snap images for focusing. Your processing workflow will depend on how you intend to use the narrowband data. Say that you are using a Hydrogen alpha (Ha) filter. Since the Ha wavelength is deep in the red range, only the red pixels on you sensor will collect any photons. The values for the green and blue pixels will only have noise. Now you go through your normal stacking process (debayer, calibrate, normalize, grade, align, and combine are typical steps). You will end up with a color (RGB) image, but only the red channel will have any data. So, what do you do now??? The simplest thing is to extract the red channel data into a monochrome image. How you do that will depend on what app you are using. You can then process and publish that monochrome image, or you could process it and re-combine it with other data in some way. There are really several options.One possibility is to combine Ha data with RGB data for the same target by aligning the Ha data with the RGB data and then layering the Ha data in as a luminance layer. Another option is to replace the red data in the RGB image with the Ha data. One good source for how to combine Ha with RGB data is Photoshop Astronomy by R. Scott Ireland, published by Willmann-Bell. IMO, and with all of that said, I do not recommend shooting narrowband with a DSLR, or any one-shot color camera for that matter. Others will likely disagree, since just purchasing a filter is much cheaper than purchasing a CCD camera with a filter wheel, plus filters. In my above example, with an Ha filter, only 25% of the pixels (those with red filters) collect any data. The debayering process then interpolates (makes up) red data for the green and blue pixels. Contrast that with a monochrome astroCCD camera where every pixel will collect the Ha data with a 16-bit data range, and you can bin 2x2 to increase the sensitivity. It makes your processing much easier to create a satisfying image.
  20. I believe that what you are seeing is the designed behavior. The image fragment in the Zoom Box window is the portion of the full image that is inside the white rectangle. It is digitally zoomed because the size of the zoom box image is larger than the size of the white rectangle. I believe that this is just how windows zooms an image to fill the size of the display frame. I am not sure what issue you have with this behavior. I don't believe that the image portion in the Zoom Box is used for anything except to display the area that is used to calculate the star size, but the star size would not be based on the zoomed image size.
  21. Scroll down to the bottom of this page and click on Compare Editions under BYE on the left hand side of the page.
  22. One big exception to your statement are the .NET app.config and user.config files which must be in the same directory as the executable. I believe that these files are what sometimes cause problems like the one in this thread. If Guylain were to change where these files are located, I would expect that it would probably in the User\AppData tree. I would not recommend using Isolated Storage because it is a pain for developers since Debug and Release builds are stored in different folders due to the different signature of the exe file.
  23. If it is not listed in the Camera Support Grid, then the camera is not supported. There can be a delay of several months between when Canon releases a camera and when they release a new verson of the SDK that supports it.
  24. You can also watch the You Tube videos. They are for BYE, but will be very helpful. Just look at the first few topics in the BYE forum.
×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use