Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Canon 6D log history


bcashion
 Share

Question

I had been using a Canon T3i with BYEOS for more than a year and it was trouble-free.  Recently I switched to a Canon 6D.

It often locks up BYEOS (3.1.16).  I have to shutdown BYEOS AND do a cold re-start on the 6D.  In looking into all this, I find that there are NO logfiles for the 6D.  Is there another folder where they might be besides BackYardTemp?

Clicking View Log History reveals the abbreviated information, but clicking Open Log Folder reveals an empty folder (BackyardTemp).

Have others had issues with 6D-BYEOS connectivity?

 

Bryan

Link to comment
Share on other sites

11 answers to this question

Recommended Posts

  • 0

Unfortunately, this sounds like Yet Another case where Windows User Privileges for the BackyardTemp Folder has gotten messed-up.  (Many of us experienced these types of Errors after some of the larger Windows Updates.)

Unless you are skilled in managing Windows User and File/Directory Privileges, the standard solution is to re-install BYE into a NEW Directory (which creates a new Folder Tree including a BackyardTemp Directory - but "dislocates" all of your existing Configuration).

If you are skilled, the issue is to ensure that the User has Full Rights to the BackyardTemp (as well as other Image Directories used as final Image Destination) Directory Tree.

Link to comment
Share on other sites

  • 0

The log files should be at the same location.

Now, the 6D produces larger image files, much larger than the T3i.  I'm pretty sure your issue is realted to USB issue. 

Are you using a USB hub?  How many devices do you have connected to the hub?

Link to comment
Share on other sites

  • 0

A powered hub a irrelevant here, the issue us the amount of data that goes on the usb cable at once, I'm pretty this is the root cause.  Plug the camera directly into a computer usb port and see if this makes a difference.  If yes we found the root cause.

 

Link to comment
Share on other sites

  • 0

Guylain

The powered USB cable made no difference.  I know that the cable is good.

I was able to capture a sequence of flats using the original configuration.  No log file was written in BackYardTemp/logs.

I tried another image capture program.  it works without issue.

Bryan

Link to comment
Share on other sites

  • 0

I removed BYE using Revo Uninstaller, which does an excellent FULL remove, including files and registry entries.

Everything seems to be good now, including generation of logfiles.  

One question.  For a 6D with DIGIC 5+, which driver should I use (CANON or CANON 215)?  Both seem to allow proper operation and both are listed as acceptable for DIGIC 5.  I had been using Canon 215 for the 6D. Is there any way to determine when my 6D was built in order to distinguish pre and post 2014?

Thank you for your help!

Bryan

Link to comment
Share on other sites

  • 0

FYI

 

After my last note, I continued to have issues with BYEOS locking up.  I finally found the source.  I had started using a DC power adapter for the 6D through a Kendrick Power Hub.  I switched back to dedicated AC power to the 6D via the Canon supplied transformer.  I have had NO issue since of any kind with BYEOS locking up or not generating logfiles.

 

Bryan

Link to comment
Share on other sites

  • 0
17 minutes ago, bcashion said:

FYI

 

After my last note, I continued to have issues with BYEOS locking up.  I finally found the source.  I had started using a DC power adapter for the 6D through a Kendrick Power Hub.  I switched back to dedicated AC power to the 6D via the Canon supplied transformer.  I have had NO issue since of any kind with BYEOS locking up or not generating logfiles.

 

Bryan

Ah, the camera had insufficient power, or intermittent power... witch probably disconnected the camera from the PC momentarily and BYE lost connectivity and led to the issue.  Glad you figured it out.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • 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