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

T1i D/L issue


SKYGZR
 Share

Question

Cam has worked just fine till this. Last time used, OK. Cam hasen't left the scope, no fiddling with it since last use.

Start BYEOS, fine. Turn on Cam, little message pop's up--normal (This is on XP), Cancel that, Connect BYEOS to

Cam, OK. Frame & Focus window to take a 10s, 12,800iso snap shot, Select, starts, then stops-takes almost the full

10s shot, Not OK. (Think that when D/L image to screen, is when it does the following, and Main

Window reverts back to the connect cam/starting screen, the pop-up comes up again. Try again, same result. Turn Off Cam, unplug (from the

powered hub) the USB cable, plug into another port. Try again, same issue.

Perplexed? Hints to try to resolve?

 

I do have another T1i that I will try later, yet this seems a bit "weird"...

I can upload the log file later.

Link to comment
Share on other sites

Recommended Posts

  • 0

The key phrase here is "Window reverts back to the connect cam/starting screen".

This confirms that camera has disconnected and therefore BYE goes back to the disconnected mode.

If this happens just as the image download occurs this is the classic case for your usb hub/connection being either faulty or over saturated with data.

I would run a few tests with only the camera connected directly in a computer usb port, then add the hub, then add the other devices... eventually you'll hit the bottle neck and this should confirm this.

If could the cable as well as the they deteriorate over time, might good to change usb cables.

Also, make every cable is properly seated and the connection is tight and secure.

Keep us posted,

Link to comment
Share on other sites

  • 0

Tried the other T1i & it works just fine using the same connection (with the hub). Have not tried directly hooking up the one that has an issue directly to the 'puter.

Since the other works OK, seems that the connection isn't the issue.

Attached are (2) log files. 20180205 is from when the issue started, 20180210 is when trying again, same result, then trying again with the other cam.

logfile-[20180205-20h56m55s901]-[3448]-2018-02-05.txt

logfile-[20180210-13h59m05s406]-[8672]-2018-02-10.txt

Link to comment
Share on other sites

  • 0

I had a quick look at the first log file. It appears that BYE is taking a BULB exposure in Frame & Focus mode. It is expecting an image to be downloaded from the camera and times out after 129 seconds when the image is not available.

I would compare the camera settings in the camera that works and the one that doesn't work for differences. Do you see any difference if you take a short Tv exposure?

Link to comment
Share on other sites

  • 0

Doesn't matter what is tried, always disconnects. 129s seems a bit weird, as it disconnects almost imeaditily, doesn't "hang". I did try it directly to a 'puter USB port w/o the hub, and same thing. Strange thing is, like previously mentioned, worked just fine up till this..didn't change any settings. I'll get around to comparing the settings.

Link to comment
Share on other sites

  • 0
1 hour ago, SKYGZR said:

Doesn't matter what is tried, always disconnects. 129s seems a bit weird, as it disconnects almost imeaditily, doesn't "hang". I did try it directly to a 'puter USB port w/o the hub, and same thing. Strange thing is, like previously mentioned, worked just fine up till this..didn't change any settings. I'll get around to comparing the settings.

No, it's not weird.  BYE is hard programed to wait about 2 minutes for an image to download after an image is taken.  If the camera does not provide an image in this time frame BYE will timeout.

Are you using RAW, JPG, or both?

 

Link to comment
Share on other sites

  • 0

Always RAW only..I am leaning towards the cam finally giving up the ghost, yet will continue playing around with it from time to time. If I can get it to take a "normal" pic, then perhaps can use it with an intervelometer as it's modded & would like to @ least be able to use it somehow.

Link to comment
Share on other sites

  • 0

Okay, looked at both log files.

Here is what I think is happening.  The camera is overheating and it shuts down.  In both your you logfiles the original error is the camera disconnecting while in live view, not the download.  I suspect this is caused by live view overheating the camera and thus the shutdown.

Do you get the timeout only in Frame & Focus or imaging as well?

 

2018-02-05 21:18:34,542 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)
2018-02-05 21:18:34,886 [OnStateEventHandler] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2018-02-05 21:18:35,058 [OnStateEventHandler] DEBUG - ERROR EDS_ERR_INVALID_HANDLE : EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1) 
2018-02-05 21:18:35,058 [OnStateEventHandler] DEBUG -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon215.CameraProperties.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyEvfZoom.set_Value(String value)
   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass99_0.<PropertySet>b__0(IProperty x)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at BinaryRivers.Common.Model.CameraModelBase.PropertySet(CameraPropertyEnum property, String value, Boolean force)
   at BinaryRivers.Common.Model.CameraModelCanonBase.set_PropertyZoomEvf(String value)
 

 

2018-02-10 13:59:47,156 [Main] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, ImageQuality(256), 0, size(4), 34864911)
2018-02-10 13:59:48,203 [Main] ERROR - ERROR EDS_ERR_COMM_DISCONNECTED : EDSDK.EdsSetPropertyData(cameraRef, ImageQuality(256), 0, size(4), 34864911) 
2018-02-10 13:59:48,203 [Main] ERROR -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon215.CameraProperties.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.set_Value(String value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.SetQuality(ImageQualityBestFitEnum quality)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.TrySetQuality(String captureImageQuality)
   at BinaryRivers.Common.Model.CameraModelBase.CameraPropertySetOnMessageRecieved(Object sender, MessageBusEventArgs`1 messageBusEventArgs)
2018-02-10 13:59:48,312 [Liveview image push 890] INFO  - Parameter is not valid.
 

 

Link to comment
Share on other sites

  • 0
2 hours ago, admin said:

Do you get the timeout only in Frame & Focus or imaging as well?

Seems to be only in Frame & Focus..haven't tried it in the Imaging screen...after all, to start a "session", one would use F&F to begin with...yet in the Imaging screen, the cam is connected, & seems to be OK..yet have not actually tried to use it to capture under that screen. I could do a test to confirm it's behavior.

Link to comment
Share on other sites

  • 0

If you use F&F for a long time, you could Pause LiveView when you are not actively using it. I would suggest using the Snap images from F&F as throwaway images. For example, take the Snap image and display it on the screen but don't save it to your hard drive. They are small JPG images and not what you would want to use to produce a final image. If you use them only for framing and focusing then you don't need to save them. Capture your actual light frames as RAW from the Imaging screen.

Link to comment
Share on other sites

  • 0

" Are you saying that you never use the image capture to take your images once you are done with Frame & Focus? "

NO, always use the Imaging tab to take a series of images after framing & focusing. I am trying to convey that I have not tried using the cam, in the imaging area to take a series of normal lights (or darks, etc.), like one would do when actually running a sequence, to see if it stays connected

and completes a run.

"  using the Snap images from F&F as throwaway images "

That is what I do & where it's having it's disconnect issue. I don't leave Live View running for any longer than to focus & then to frame.

I have been using this software for years & am familiar with how to use it.

Link to comment
Share on other sites

  • 0

Thanks for the information.

Does the camera always disconnect during a sequence of Snap images during download?

After looking at the log file, I do not believe that the shutdown is due to overheating. This is because BYE is sensing the shutdown only 3.3 seconds after the start of LiveView (a major source of the camera heating up).

2018-02-10 13:59:44,890 [Main] DEBUG - ButtonPlus_MouseClick(btnFrameFocus = 'Frame & Focus')
2018-02-10 13:59:44,953 [Main] INFO  - Camera action fired: 'LiveviewStart'
2018-02-10 13:59:44,968 [Main] INFO  - Running (log): EDSDK.EdsGetPropertyData(CameraRef, BatteryLevel(8), 0, size(4), intPtr)
2018-02-10 13:59:44,984 [Main] INFO  - Success: EDSDK.EdsGetPropertyData(CameraRef, BatteryLevel(8), 0, size(4), intPtr)
2018-02-10 13:59:44,984 [Main] INFO  - Running (log): EDSDK.EdsSetPropertyData(this.mCameraRef, EDSDK.PropID_Evf_OutputDevice, 0, 4), (uint)Canon.OutputDeviceENUM.EvfOutputDevice_PC)
2018-02-10 13:59:45,015 [Main] INFO  - Success: EDSDK.EdsSetPropertyData(this.mCameraRef, EDSDK.PropID_Evf_OutputDevice, 0, 4), (uint)Canon.OutputDeviceENUM.EvfOutputDevice_PC)
2018-02-10 13:59:45,015 [Main] INFO  - Running (log): EDSDK.EdsCreateMemoryStream(0, out this.mLvMemStreamRef)
2018-02-10 13:59:45,031 [Main] INFO  - Success: EDSDK.EdsCreateMemoryStream(0, out this.mLvMemStreamRef)
2018-02-10 13:59:45,031 [Main] INFO  - Running (log): EDSDK.EdsCreateEvfImageRef(this.mLvMemStreamRef, out this.mLvImageRef)
2018-02-10 13:59:45,046 [Main] INFO  - Success: EDSDK.EdsCreateEvfImageRef(this.mLvMemStreamRef, out this.mLvImageRef)
2018-02-10 13:59:45,968 [Main] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2018-02-10 13:59:45,984 [Main] INFO  - Success: EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2018-02-10 13:59:46,546 [Main] INFO  - CameraPropertyChangedArgs fired: LiveviewZoom         = 'Fit'
2018-02-10 13:59:46,890 [Main] INFO  - Camera action fired: 'LiveviewResume'
2018-02-10 13:59:47,156 [Main] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, ImageQuality(256), 0, size(4), 34864911)
2018-02-10 13:59:48,203 [Main] ERROR - ERROR EDS_ERR_COMM_DISCONNECTED : EDSDK.EdsSetPropertyData(cameraRef, ImageQuality(256), 0, size(4), 34864911)
2018-02-10 13:59:48,203 [Main] ERROR -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon215.CameraProperties.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.set_Value(String value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.SetQuality(ImageQualityBestFitEnum quality)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.TrySetQuality(String captureImageQuality)
   at BinaryRivers.Common.Model.CameraModelBase.CameraPropertySetOnMessageRecieved(Object sender, MessageBusEventArgs`1 messageBusEventArgs)
2018-02-10 13:59:48,312 [Liveview image push 890] INFO  - Parameter is not valid.
2018-02-10 13:59:48,312 [Liveview image push 890] ERROR - Parameter is not valid.
2018-02-10 13:59:48,390 [Liveview image push 890] INFO  - Parameter is not valid.
2018-02-10 13:59:48,390 [Liveview image push 890] ERROR - Parameter is not valid.
2018-02-10 13:59:48,421 [Main] INFO  - -----------------------------------
2018-02-10 13:59:48,421 [Main] INFO  - Application state changed: 'FrameFocus'

<Some log entries deleted for brevity>

2018-02-10 13:59:48,937 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)

See how the camera behaves with the Canon EOS Utility. Failure with the EOS Utility may report a useful error and would tend to eliminate BYE as a cause.

If two models of the same camera have the same settings but behave differently when connected to the same software on the same computer with the same cable. Then one could reasonably conclude that one of the cameras is malfunctioning.

 

Link to comment
Share on other sites

  • 0

"Then one could reasonably conclude that one of the cameras is malfunctioning."

This is what I'm leaning towards..it's "old" and has been fairly well used...not gonna give up quite yet though...might do a complete "reset" & see if any thing changes. I'll play with the Utility before any reset is tried just for "fun".

Link to comment
Share on other sites

  • 0
5 hours ago, astroman133 said:

Thanks for the information.

Does the camera always disconnect during a sequence of Snap images during download?

After looking at the log file, I do not believe that the shutdown is due to overheating. This is because BYE is sensing the shutdown only 3.3 seconds after the start of LiveView (a major source of the camera heating up).

2018-02-10 13:59:44,890 [Main] DEBUG - ButtonPlus_MouseClick(btnFrameFocus = 'Frame & Focus')
2018-02-10 13:59:44,953 [Main] INFO  - Camera action fired: 'LiveviewStart'
2018-02-10 13:59:44,968 [Main] INFO  - Running (log): EDSDK.EdsGetPropertyData(CameraRef, BatteryLevel(8), 0, size(4), intPtr)
2018-02-10 13:59:44,984 [Main] INFO  - Success: EDSDK.EdsGetPropertyData(CameraRef, BatteryLevel(8), 0, size(4), intPtr)
2018-02-10 13:59:44,984 [Main] INFO  - Running (log): EDSDK.EdsSetPropertyData(this.mCameraRef, EDSDK.PropID_Evf_OutputDevice, 0, 4), (uint)Canon.OutputDeviceENUM.EvfOutputDevice_PC)
2018-02-10 13:59:45,015 [Main] INFO  - Success: EDSDK.EdsSetPropertyData(this.mCameraRef, EDSDK.PropID_Evf_OutputDevice, 0, 4), (uint)Canon.OutputDeviceENUM.EvfOutputDevice_PC)
2018-02-10 13:59:45,015 [Main] INFO  - Running (log): EDSDK.EdsCreateMemoryStream(0, out this.mLvMemStreamRef)
2018-02-10 13:59:45,031 [Main] INFO  - Success: EDSDK.EdsCreateMemoryStream(0, out this.mLvMemStreamRef)
2018-02-10 13:59:45,031 [Main] INFO  - Running (log): EDSDK.EdsCreateEvfImageRef(this.mLvMemStreamRef, out this.mLvImageRef)
2018-02-10 13:59:45,046 [Main] INFO  - Success: EDSDK.EdsCreateEvfImageRef(this.mLvMemStreamRef, out this.mLvImageRef)
2018-02-10 13:59:45,968 [Main] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2018-02-10 13:59:45,984 [Main] INFO  - Success: EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2018-02-10 13:59:46,546 [Main] INFO  - CameraPropertyChangedArgs fired: LiveviewZoom         = 'Fit'
2018-02-10 13:59:46,890 [Main] INFO  - Camera action fired: 'LiveviewResume'
2018-02-10 13:59:47,156 [Main] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, ImageQuality(256), 0, size(4), 34864911)
2018-02-10 13:59:48,203 [Main] ERROR - ERROR EDS_ERR_COMM_DISCONNECTED : EDSDK.EdsSetPropertyData(cameraRef, ImageQuality(256), 0, size(4), 34864911)
2018-02-10 13:59:48,203 [Main] ERROR -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon215.CameraProperties.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.set_Value(String value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.SetQuality(ImageQualityBestFitEnum quality)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyImageQuality.TrySetQuality(String captureImageQuality)
   at BinaryRivers.Common.Model.CameraModelBase.CameraPropertySetOnMessageRecieved(Object sender, MessageBusEventArgs`1 messageBusEventArgs)
2018-02-10 13:59:48,312 [Liveview image push 890] INFO  - Parameter is not valid.
2018-02-10 13:59:48,312 [Liveview image push 890] ERROR - Parameter is not valid.
2018-02-10 13:59:48,390 [Liveview image push 890] INFO  - Parameter is not valid.
2018-02-10 13:59:48,390 [Liveview image push 890] ERROR - Parameter is not valid.
2018-02-10 13:59:48,421 [Main] INFO  - -----------------------------------
2018-02-10 13:59:48,421 [Main] INFO  - Application state changed: 'FrameFocus'

<Some log entries deleted for brevity>

2018-02-10 13:59:48,937 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)

See how the camera behaves with the Canon EOS Utility. Failure with the EOS Utility may report a useful error and would tend to eliminate BYE as a cause.

If two models of the same camera have the same settings but behave differently when connected to the same software on the same computer with the same cable. Then one could reasonably conclude that one of the cameras is malfunctioning.

 

 

While this true for that log file, the other one is the classic error generated from overheating.   I think this is actually 2 separate issues leading to a similar outcome.

2018-02-05 21:18:34,542 [OnStateEventHandler] INFO  - StateEvent_Shutdown Fired! (inParameter=0)
2018-02-05 21:18:34,886 [OnStateEventHandler] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1)
2018-02-05 21:18:35,058 [OnStateEventHandler] DEBUG - ERROR EDS_ERR_INVALID_HANDLE : EDSDK.EdsSetPropertyData(cameraRef, LiveviewZoom(1287), 0, size(4), 1) 
2018-02-05 21:18:35,058 [OnStateEventHandler] DEBUG -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)
   at BinaryRivers.Camera.Canon215.CameraProperties.PropertyBaseUint.UploadPropertyValueToCamera(UInt32 propertyid, Int32 param, UInt32 value)
   at BinaryRivers.Camera.Canon215.CameraProperties.Properties.PropertyEvfZoom.set_Value(String value)
   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass99_0.<PropertySet>b__0(IProperty x)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at BinaryRivers.Common.Model.CameraModelBase.PropertySet(CameraPropertyEnum property, String value, Boolean force)
   at BinaryRivers.Common.Model.CameraModelCanonBase.set_PropertyZoomEvf(String value)

 

Link to comment
Share on other sites

  • 0

A quick update..so last night I used the older XP machine that was previously in the OBSV (the "newer" one there, also has XP on it), to try the EOS utility..Found the cam fine & seemed to function OK. So, decided to fire up BYEOS (VEr 3.0.0) that is still on that machine, hooked up the cam, & it seemed to work just fine. Frame & Focus, 10s 12,800iso, completed & didn't disconnect. Tried it again, worked...Hmm?  Weird...Will have to check what version of BYEOS is on the current OBSV 'puter, but I do believe it's the most recent build.

 

I'm going to test on the field laptop's next....stay tuned.

Link to comment
Share on other sites

  • 0

I am confused about what machines you have, which versions of BYE are installed, and what works.

Are you saying that one of your T1i's does not run with BYE 3.1.16 on a new computer but the other camera works fine. Also that both cameras do run on a different computer with BYE 3.0.0? Are you using the same short cables? That would be very strange.

You still need to try the EOS Utility on the machine that is having problems.

Link to comment
Share on other sites

  • 0

I will get around to trying the one w/the issue on the Obsv 'puter (XP), EOS utility (and verify what version of BYEOS is on that machine).  Trying to clairify:

1. Cam1 worked fine on Obsv XP 'puter till this disconnect thing appeared.

2. Cam2 was hooked up with the same USB cable to powered hub on the same 'puter & works.

3. Cam1 was then hooked up to an XP machine (that used to be in the Obsv) and worked w/ BYEOS v/3.0.0 & worked w/ the EOS utility on that 'puter.

4. (This was just done last night) Cam1 was hooked up to a W7 PRO HP Laptop (for field use) and worked w/BYEOS v/3.1.16. Did a 10s, 12800iso snap shot in frame & focus, then a 360s/1600iso

"test" in imaging. Cam1 (the one with the issue) completed both. This was using a regular camera battery.

The Obsv setup has a 110v step down battery (Canon Factory) power supply, and was used to test Cam2 with success & worked fine w/Cam1 till this issue.

Since Cam2 worked when trying on the Obsv 'puter, have left it there for now.

Will update when I find out more.

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