T1i D/L issue

[SKYGZR]

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.

[astroman133]

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.

[SKYGZR]

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.

[admin]

By Cam1 / Cam2 you mean the executables, right?

They are identical, this is odd... but they both have their how config file.

Keep us updated.

[astroman133]

No, the OP has 2 T1i cameras (Cam1 and Cam2). He also has 2 computers (one in his observatory and the other for use in the field). Apparently Cam2 works with both computers but Cam1 only works with one computer. When Cam1 is connected with the Observatory computer it apparently fails to provide an image to BYE and BYE times out after 129 seconds.

Other factors are that when a camera is used in the Observatory it is powered by A/C power rather than a battery. When in the field the cameras are powered by batteries. Also, the "field" PC is running a much older version of BYE (3.0.?).

I hope that I have that right!

If so, then the next thing that I would try is to run the camera with the issue (Cam1???) in the observatory as normal to confirm failure then try it again when the camera is powered with a fully-charged battery.

[admin]

29 minutes ago, astroman133 said:

No, the OP has 2 T1i cameras (Cam1 and Cam2). He also has 2 computers (one in his observatory and the other for use in the field). Apparently Cam2 works with both computers but Cam1 only works with one computer. When Cam1 is connected with the Observatory computer it apparently fails to provide an image to BYE and BYE times out after 129 seconds.

Other factors are that when a camera is used in the Observatory it is powered by A/C power rather than a battery. When in the field the cameras are powered by batteries. Also, the "field" PC is running a much older version of BYE (3.0.?).

I hope that I have that right!

If so, then the next thing that I would try is to run the camera with the issue (Cam1???) in the observatory as normal to confirm failure then try it again when the camera is powered with a fully-charged battery.

LOL, I'm not in my game this week... I've misread a few posts... good thing is it's Friday... and it is a clear moonless night... seeing is not that good but it's clear... so I'm going to be outside all night   

[s3igell]

46 minutes ago, admin said:

LOL, I'm not in my game this week... I've misread a few posts... good thing is it's Friday... and it is a clear moonless night... seeing is not that good but it's clear... so I'm going to be outside all night   

Going Outside - better for your health than Going to the Bar!!

I've got a Clear Sky Clock for the local "Semi/Somewhat-Dark'ish Site" for tomorrow night.  I think I'll join you outside...  So, don't suck up all the Photons!!

[admin]

1 hour ago, s3igell said:

Going Outside - better for your health than Going to the Bar!!

I've got a Clear Sky Clock for the local "Semi/Somewhat-Dark'ish Site" for tomorrow night.  I think I'll join you outside...  So, don't suck up all the Photons!!

WHOA.... A f/3 the photons are all mine.  Get it line

[SKYGZR]

Cam 1 & Cam 2 are two different modded 500D's.

To update, the Obsv 'puter is running V3.1.19. After testing on all other 'puters it worked just fine..went back out to the Obsv just now, hooked up the one that had the "issue" (Cam1)..

and it now functions as nothing ever happened...10s 12,800iso snap..OK without disconnect...360s 1600iso light, OK..completed that just fine...

Perplexing to say the least...perhaps the battery contacts were/are a bit dirty? (will have to check)..and removing & reinstalling a battery a few times helped?

If the issue returns, will add to this post..yet am going to use Cam2 for now...yet the chance to use it might be awhile due to mother nature..

[astroman133]

Thanks for letting us know.

[astroman133]

Is it possible that anti-virus software is interfering with the image download?

[admin]

What does D/L means?

[SKYGZR]

D/L = Down Load & no anti virus software.

[admin]

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,

[astroman133]

2 hours ago, admin said:

... 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...

I agree!

[SKYGZR]

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

[astroman133]

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?

[SKYGZR]

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.

[astroman133]

Perhaps the camera is broken. I would try shooting the same types of exposures with the Canon EOS Utility.

[admin]

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?

 

[SKYGZR]

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.

[admin]

send me the log file.

 

[SKYGZR]

Log files have been attached in an above post

[admin]

7 minutes ago, SKYGZR said:

Log files have been attached in an above post

I don't see them.

Please don't attached them to a post in the forum.

Send them to the support@otelescope.com email as per instructions.  

 

[astroman133]

I see a couple of log files in a post from SKYGZR on Sunday at 1:08 PM. What I saw in the first one was a 129 second timeout waiting for the image to become available.

[admin]

Oh, I see the log files now... I'll take a look.

[admin]

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.
 

 

[SKYGZR]

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.

[admin]

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

 

[astroman133]

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.

[SKYGZR]

" 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.