Jump to content

Canada's top-tier Telescopes & Accessories

admin

Administrators
  • Content Count

    6,597
  • Joined

  • Days Won

    43

Everything posted by admin

  1. It's confirmed then; it can't work with BYE. Looks like canon has butchered the M6 just as they did the M1 to M5.
  2. First thing first. Try your M6 with EOS Utility. Can you take BULB images in EOS Utility with your M6? If yes we have a fighting chance of making it work. If you can not take BULB images in EOS Utility and your M6 it means Canon has butchered the SDK implementation of the M6 just as the did with the M1 to M5. Keep us posted please.
  3. admin

    ISS Transit

    Yes, have fun with it and blame him, lol. The underlying issue is that W10 updates will often replace the entire windows install folder (or a large majority of it) and this triggers the "this is not the same computer" event in the licensing schema and it causes the license key to be re-validated.
  4. Are you referring to the M6 or M6 Mk II? There are not the same. The M6 Mk II is supported with the latest 3.1.18 pre-release which can be downloaded from the download section pre-release section. These are the Canon mirror less camera currently supported with the pre-release EOS R EOS RP EOS M50 EOS M6 Mk II The EOS M1 to M5 are definitely not supported, and never will be because Canon butchered the SDK by preventing BULB exposures over USB. The EOS M6 may be possible since the M6 Mk II is now supported. EDIT: If the M6 is closely related to the M1 to M5 we are out of luck... but if it is more closely related to the M6 Mk II we may have a fighting chance. If you have an M6 try it with EOS Utility and see you you can take BULB images with the M6 and EOS Utility. Regards,
  5. There is no setting. That counter (25 / 180) is *always* displayed during the image capture. If you are taking 60 second images this number should be displayed for 60 seconds. I suspect that you may be taking 180 very short images. The only way this number would be flashing would be when taking short exposures of only a few seconds. How long are your exposures? Regards,
  6. This does seems like an odd Windows behavior. Did you try on another PC just to see if Windows show the correct file size there? If it does at least now you'll it's specific to the windows installation on the other PC and your assessment of it being caused by a Windows update may be correct. Also, can you restore your PC to a date where you know it was working? This would also give you another clue if it was a Windows update issue.
  7. admin

    ISS Transit

    This is so cool, thanks for sharing that picture! EDIT: Some windows update will cause the license to be re-validated. I suspect this is the cause for having to re-validate your key.
  8. Rick, in your experience, does most ASCOM driver provide that list ordered by fastest to slowest speed? Your suggestion makes sense, I just need to figure out a few things (like dithering speed) before making the call to plunge or not. Also, what if the mount supports the move axis command but that list is empty (is that even a possibility) or only has one value? I guess a one size fits all would be to somehow allow the user to select from that list and keep the percentage to scale that speed sort a speak. For Jim, that would give him all 3 speeds to choose from a list, and with the percentage set to 100%, would mean the Genimi ASCOM driver would always set the Gemini slew speed to the appropriate value. I'm I reading this right? I'm not saying this is what I'll be doing, or even a timeline, I'm merely trying to understand the command flow at this stage so that any decision taken is an informed one. Regards,
  9. I just looked at the Driver.cs file from that github repository and the switch statement at line 1331 is where the Gemini ASCOM driver changes the slew speed. The Gemini ASCOM driver will *ALWAYS* change the rate to either slew/center/guide according to this code below; this is a Gemini specific behavior. What is your ideal outcome Jim? Is there one that you prefer the mount to be set to once the MoveAxis is complete?
  10. Please start a new thread in the future as this thread has been marked as solve by the OP. The D3100 will not work as you found out. The D5100 should work, in fact I have one and it does connect. Does windows even see the D5100 camera?
  11. Oh, and to answer your questions in your email... The trial is NOT the pre-release. BYE comes in 3 editions and is defined by your software key. Trial Edition Classic Edition Premium Edition. The trial edition IS the premium edition but will only work for 30 days. Aside from that the Trial edition is the same as the premium edition. A pre-release is NOT an edition.... it's a download of the next version that is not yet release that people can try with their current software key. It does not matter if your software key is the trial, classic, or premium key... your key will work a pre-release. Because a pre-release is NOT an edition (trial, classic, premium)... you only need to download it form the "DOWNLOAD" pre-release section and use your *same* key. Click "Download" from the website top menu bar, then click on the "pre-release" section on the right option panel.
  12. Ok, I think I found the account.... is it "yamada" with your pec....@gmail.com account?
  13. Please DO NOT reply to forum posts by email. You must post directly on the forum to ensure the conversation remains public; this way other users may benefit from the conversation and outcome. I need to know that account you used to purchased and gets locked as you say. Without this I can not find the account to unlock it. Regards,
  14. According to your logfile from May you selected the default Nikon driver in BYN when connecting and it worked fine. Does Windows see the camera?
  15. I'm confused. What is locked? I looked at your profile and I do not see any BYE Premium license key under the account you are using to post this message. Can you please elaborate a little bit more on your issue? Thank you.
  16. I see on the activation server that your purchase key has been activated once. I'm I to assume that you have it working now?
  17. The system still reads your trial key... and it's expired. Click ok and you should be prompted to enter your purchase key. Regards,
  18. Since it works for 8 to 16 frames as per OP my experience tells me this is a power/sleep issue on the PC (or host PC). Just a hunch.
  19. This is a Nikon SDK / internal camera error... it can't start the bulb exposure. My guess is that camera was disconnected form the PC (or host PC) and all bets of off after this. Something might be going to sleep... usb port, computer, hard drive, etc.
  20. I'm glad you got it to work. Thank you for not posting your license key on the forum
  21. I think you should be able to use it now because version 2.0.9 created a license file on your computer and 2.0.10 will read that file if there is a problem with the registry. Regards,
  22. I think the issue may be related to Windows registry, it may be a permission issue. To confirm this, please download and install 2.0.9 and see id this one works. If it does it confirms the issue is the registry because in 2.0.9 or earlier version I was not using the registry. Please let me know if your still have issues after you've tried 2.0.9.
  23. What version of BackyardNIKON are you using? The full version number please.
  24. What is the EXACT error message you are getting?
×
×
  • 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