cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Canon 60DA Won't Power On

timtrice
Contributor

I just received my brand new 60DA on Wednesday. I was able to use it, read the manual, get comfortable with it the rest of the evening. That night I hooked it to my scope and using Backyard EOS took it for a run capturing numerous pictures. No issues. When finished, I disconnected from the program, powered off, unplugged and put the body cap cover back on.

 

The next night, I was not getting any power at all. Thinking the battery may have drained (though it was fully charged during the two hour photo session), I removed it and plugged it into the wall charger. I then inserted the AC adapter. But it still would not power on. The battery was nearly charged as I was getting three flashing lights from the charger.

 

From what I've read so far some Canon camera's will not power on if there is an issue w/ the memory card or if the lens isn't put on correctly. None of those are issues (the memory card was present both occassions and not used to store images during the session and the camera was mounted to scope using t-ring). 

 

Humidity/Dew was not an issue neither eveninig.

 

I also read the switch inside the battery housing can sometimes defect though it locks in the battery fine and I see no reason to suspect it isn't operating.

 

Please someone tell me I didn't get a jacked up camera!!!

18 REPLIES 18

TCampbell
Elite

If you're using the battery then it may just be that the battery is drained.  The camera includes the AC adapter because astro imaging tends to take a great many exposures each of which are very long... this will really dip into the battery power far more than people experience when using a normal camera for daytime/terrestrial use.

 

If I'm doing very bright objects (e.g. the moon) then I'll go ahead and use the batteries because that's no different than taking normal pictures with a camera.  BUT... if shooting something in deep-space where the exposures are many minutes long each and I'll have to take a lot of them, I don't even bother with the battery... I use the AC adapter.  There's a small rubber flap near the battery door that opens to let you pass the wire out of the camera body.

 

It will power on with no lens at all.  That's no problem.  Have you recharged the battery and tried with both the battery and also with the AC adapter?  (e.g. if it's just the battery then the AC adapter will work fine.)

 

It's possible to put it into a mode where the rear LCD stays dark, but the top LCD should be displaying info so you'd still be able to tell that it's on if this is the case.

 

Tim Campbell
5D III, 5D IV, 60Da

Tim, I have alternated between the battery which was mostly charge and the AC adapter (even multiple outlets). I get no display on the top LCD nor on the viewfinder. I even just tried the fully charged battery about an hour ago. There is no response at all.

I grabbed my camera to check a few things.   There are two interlock switches that prevent the camera from powering up.

 

1)  If I leave the memory card door open (even though the card is inserted), the camera wont power up.  But it will power up if the door is closed.  

 

The door swings shut and then you have to slide it forward to lock it.  There are two tiny tabs on the door that slide into slots on the body when you slide the door forward to lock it in place.  The lower tab appears to press one of the interlock switches.  Make sure your tab isn't damaged and that the door is able to slide forward completely to lock in place.   The door should fit flush with the body.

 

2)  The other switch is on the battery compartment door.  If the battery door is open, the camera will not power on even if the battery or AC adapter is in place.    

 

This switch is a little more obvious.  If you look at the camera (upside down) there's one obvious tab on the side of the battery door nearest to the rear of the camera.  It presses a switch located in a hole also near the rear of the camera (opposite the side where you see the plastic locking tab that holds the battery in place.)  

 

Verify that tab isn't damaged/broken and that the door is able to close and latch flush with the body.

 

I'm not aware of any other interlock switches that keep the camera from powering up.  For example... you do not need to have a lens attached (I have several EOS bodies... all of them power up with no lens attached whether the lens cap is on or not.)

 

Hopefully it's a trivial thing to resolve, but if you are not able to resolve it, phone Canon support for assistance.  As the camera is only 1 day old, I should think you could also exchange it if they can't resolve the issue over the phone.

 

It is a very nice camera for astro imaging.  I bought mine because a member of my astronomy club had just been taking images of a galaxy (I think it was M101 - but this was more than a year ago).  Knowing that my old 5D II has better ISO performance than a 60D, I thought I'd take the identical image through the same telescope just to compare how much different it was... boy was I ever surprised.  At the identical exposure, I had almost nothing showing in my image.  I doubled the time and still had very little showing.  I tripled the exposure and then it was finally getting near to what the 60Da could do.  The following week I ordered my 60Da.

 

Tim Campbell
5D III, 5D IV, 60Da

An update on the issue as it has happened agian on the replacement (brand new) camera....

 

The camera was operating fine; I snapped several images of the moon before getting the scope aligned. Towards the end of my moon session I attempted five sequences at different exp/iso settings. Only three images were returned to the program I was using (Backyard EOS).

 

I did not think anything about it at the time and attempted another run of five shots at different exp/iso settings. Again, only three images were returned. But, not thinkin anything about only getting three out of five, I proceeded to move to a star cluster to have my first attempt at a star field.

 

The idea was to capture a one-minute exposure. However, as my setting was on M the program instructed me that I needed to change to B (I knew this, just forgot). While the camera was connected to the program, I changed the setting to B. This is when the program stopped responding. I went to check the camera (perhaps battery died). The LCD was on, battery was 3/4 charged. So I went back to the program and told it to connect. It made a long attempt but after several minutes never established a connection.

 

I then shut down the program and turned the camera off thinking I should reboot. However, when I attempted to turn the camera back on I got no response. Same issue as the last one. The program could not open a connection.

 

And now I have a second brand new non-working camera.

 

This is a segment of the program log from when the issues began till I shut down the program. What stands out are the out of memory errors which I would imagine in hindsight is why I never got all five images both occasions. The second is the StateEvent_Shutdown Fired which to my understanding cannot be invoked by the software. Then, after what seems like a potential successful connection at 21:34:13,952, it shows EDS_ERR_MEM_ALLOC_FAILED. I've emphasized (bolded) those points in the log near the end.

 

Desperately seeking some type of resolution to get my camera back on...

 

Start of log:

 

2013-08-11 21:32:03,942 [Main] INFO - Imaging session started.
2013-08-11 21:32:04,404 [Main] INFO - -----------------------------------
2013-08-11 21:32:04,404 [Main] INFO - Application state changed: 'ImageCaptureBusySessionPlan'
2013-08-11 21:32:04,404 [Main] INFO - Camera action fired: 'ValidateCapturePlan'
2013-08-11 21:32:04,420 [Main] INFO - CameraPropertyChangedArgs fired: ImageQuality = 'IMAGE_RLF+'
2013-08-11 21:32:04,867 [20] INFO - Temp folder: C:\Users\timtrice\Dropbox\Pictures\BackyardTEMP
2013-08-11 21:32:04,873 [20] INFO - Download folder: C:\Users\timtrice\Dropbox\Pictures\Astrophotography
2013-08-11 21:32:04,890 [CameraTakePictureOnMessageRecieved] INFO - Running: EDSDK.EdsGetPropertyData(CameraRef, BatteryLevel(8), 0, size(4), intPtr)
2013-08-11 21:32:04,890 [CameraTakePictureOnMessageRecieved] INFO - CameraPropertyChangedArgs fired: MirrorLock = 'On'
2013-08-11 21:32:04,943 [CameraTakePictureOnMessageRecieved] INFO - CameraPropertyChangedArgs fired: AeMode = 'MANUAL'
2013-08-11 21:32:04,950 [CameraTakePictureOnMessageRecieved] INFO - CameraPropertyChangedArgs fired: Tv = '2"'
2013-08-11 21:32:04,960 [CameraTakePictureOnMessageRecieved] INFO - CameraPropertyChangedArgs fired: Av = ''
2013-08-11 21:32:04,972 [CameraTakePictureOnMessageRecieved] ERROR - Make sure camera is set to BULB, turn dial to 'B'
2013-08-11 21:32:04,972 [CameraTakePictureOnMessageRecieved] ERROR - at BinaryRivers.Camera.Canon.CameraModel.SetDialBulb()
at BinaryRivers.Camera.Canon.CameraModel.<>c__DisplayClass3f.<CameraTakePictureOnMessageRecieved>b__3e()
2013-08-11 21:32:04,979 [CameraTakePictureOnMessageRecieved] INFO - Imaging session cancelled
2013-08-11 21:32:04,985 [CameraTakePictureOnMessageRecieved] INFO - Make sure camera is set to BULB, turn dial to 'B'
2013-08-11 21:32:04,985 [CameraTakePictureOnMessageRecieved] ERROR - Make sure camera is set to BULB, turn dial to 'B'
2013-08-11 21:32:04,985 [CameraTakePictureOnMessageRecieved] ERROR - at BinaryRivers.Camera.Canon.CameraModel.SetDialBulb()
at BinaryRivers.Camera.Canon.CameraModel.<>c__DisplayClass3f.<CameraTakePictureOnMessageRecieved>b__3e()
2013-08-11 21:32:06,835 [Main] INFO - -----------------------------------
2013-08-11 21:32:06,835 [Main] INFO - Application state changed: 'ImageCapture'
2013-08-11 21:32:06,870 [Main] INFO - Imaging session cancelled
2013-08-11 21:32:06,882 [Main] INFO - CameraPropertyChangedArgs fired: ImageQuality = 'IMAGE_RLF+'

 

............................................................. some pieces edited here .......................................................................

 

 2013-08-11 21:33:26,549 [Main] INFO - Running: EDSDK.EdsSetPropertyEventHandler(_cameraRef, EDSDK.PropertyEvent_All, null, IntPtr.Zero)

2013-08-11 21:33:26,549 [Main] INFO - Running: EDSDK.EdsSetCameraStateEventHandler(_cameraRef, EDSDK.PropertyEvent_All, null, IntPtr.Zero)
2013-08-11 21:33:26,549 [Main] INFO - Running: EDSDK.EdsSetObjectEventHandler(_cameraRef, EDSDK.PropertyEvent_All, null, IntPtr.Zero)
2013-08-11 21:33:26,549 [Main] INFO - Running: EDSDK.EdsCloseSession(_cameraRef)
2013-08-11 21:33:26,549 [Main] INFO - WARNING EDS_ERR_COMM_DISCONNECTED : EDSDK.EdsCloseSession(_cameraRef)
2013-08-11 21:33:26,549 [Main] INFO - Running: EDSDK.EdsRelease(_cameraRef)
2013-08-11 21:33:26,549 [Main] INFO - WARNING EDS_ERR_INTERNAL_ERROR : EDSDK.EdsRelease(_cameraRef)
2013-08-11 21:33:26,549 [Main] INFO - CAMERA IS DISCONNECTED!
2013-08-11 21:33:26,549 [Main] INFO - Camera state changed: 60D = 'Disconnected'
2013-08-11 21:33:27,047 [Main] INFO - -----------------------------------
2013-08-11 21:33:27,047 [Main] INFO - Application state changed: 'Disconnected'
2013-08-11 21:33:27,048 [Main] INFO - Camera state changed: 'Disconnected'
2013-08-11 21:33:27,509 [Main] INFO - -----------------------------------
2013-08-11 21:33:27,509 [Main] INFO - Application state changed: 'Disconnected'
2013-08-11 21:33:27,509 [Main] ERROR - ERROR EDS_ERR_INTERNAL_ERROR : EDSDK.EdsOpenSession(_cameraRef)
2013-08-11 21:33:27,510 [Main] ERROR - at BinaryRivers.Camera.Canon.CameraController.RunAndThrow(Func`1 function, String info)
at BinaryRivers.Camera.Canon.CameraController.Connect(String usbport)
at BinaryRivers.Orchestrator.MaestroCameraDslrExtension.CameraConnect(Maestro maestro, String drivername, Boolean postchoose)
2013-08-11 21:34:13,207 [Main] INFO - -----------------------------------
2013-08-11 21:34:13,207 [Main] INFO - Application state changed: 'Connecting'
2013-08-11 21:34:13,250 [Main] INFO - Attempting to connect camera...
2013-08-11 21:34:13,257 [Main] INFO - Camera action fired: 'MaestroChoose'
2013-08-11 21:34:13,261 [Main] INFO - Camera state changed: 'Disconnected'
2013-08-11 21:34:13,753 [Main] INFO - -----------------------------------
2013-08-11 21:34:13,753 [Main] INFO - Application state changed: 'Disconnected'
2013-08-11 21:34:13,753 [Main] INFO - Running: EDSDK.EdsGetCameraList(out cameraListRef)
2013-08-11 21:34:13,753 [Main] INFO - Running: EDSDK.EdsGetChildCount(cameraListRef, out cameraCount)
2013-08-11 21:34:13,753 [Main] INFO - Running: EDSDK.EdsGetChildAtIndex(cameraListRef, 0, out mCameraRef)
2013-08-11 21:34:13,753 [Main] INFO - Running: EDSDK.EdsGetDeviceInfo(mCameraRef, out mDeviceInfo)
2013-08-11 21:34:13,753 [Main] INFO - Canon EOS 60D FOUND!
2013-08-11 21:34:13,758 [Main] INFO - Checking IsEosUtilityRunning()
2013-08-11 21:34:13,951 [Main] INFO - EOS Utility is not running!
2013-08-11 21:34:13,951 [Main] INFO - Running: EDSDK.EdsGetCameraList(out cameraListRef)

2013-08-11 21:34:13,952 [Main] INFO - Running: EDSDK.EdsGetChildCount(cameraListRef, out cameraCount)
2013-08-11 21:34:13,952 [Main] INFO - Running: EDSDK.EdsGetChildAtIndex(cameraListRef, 0, out mCameraRef)
2013-08-11 21:34:13,952 [Main] INFO - Running: EDSDK.EdsGetDeviceInfo(mCameraRef, out mDeviceInfo)
2013-08-11 21:34:13,952 [Main] INFO - Canon EOS 60D FOUND!
2013-08-11 21:34:13,952 [Main] INFO - Registered IsSupport.Bulb
2013-08-11 21:34:13,952 [Main] INFO - Registered IsSupport.Liveview
2013-08-11 21:34:13,952 [Main] INFO - Registered IsSupport.MirrorLockOverUsb
2013-08-11 21:34:13,952 [Main] INFO - Camera 'Canon EOS 60D' is connected; model '287', protocol '2'.
2013-08-11 21:34:13,952 [Main] INFO - Port '\\?\usb#vid_04a9&pid_3215#6&13879db6&0&1#{6ac27878-a6fa-4155-ba85-f98f491d4f33}'
2013-08-11 21:34:13,952 [Main] INFO - Running: EDSDK.EdsOpenSession(_cameraRef)

 

............................................................. some pieces edited here .......................................................................

 

2013-08-11 21:34:14,169 [Main] INFO - Running: EDSDK.EdsSetPropertyEventHandler(_cameraRef, EDSDK.PropertyEvent_All, null, IntPtr.Zero)
2013-08-11 21:34:14,169 [Main] INFO - Running: EDSDK.EdsSetCameraStateEventHandler(_cameraRef, EDSDK.PropertyEvent_All, null, IntPtr.Zero)
2013-08-11 21:34:14,169 [Main] INFO - Running: EDSDK.EdsSetObjectEventHandler(_cameraRef, EDSDK.PropertyEvent_All, null, IntPtr.Zero)
2013-08-11 21:34:14,169 [Main] INFO - Running: EDSDK.EdsCloseSession(_cameraRef)
2013-08-11 21:34:14,169 [Main] INFO - WARNING EDS_ERR_COMM_DISCONNECTED : EDSDK.EdsCloseSession(_cameraRef)
2013-08-11 21:34:14,169 [Main] INFO - Running: EDSDK.EdsRelease(_cameraRef)
2013-08-11 21:34:14,170 [Main] INFO - WARNING EDS_ERR_MEM_ALLOC_FAILED : EDSDK.EdsRelease(_cameraRef)
2013-08-11 21:34:14,170 [Main] INFO - CAMERA IS DISCONNECTED!
2013-08-11 21:34:14,170 [Main] INFO - Camera state changed: 60D = 'Disconnected'
2013-08-11 21:34:14,630 [Main] INFO - -----------------------------------
2013-08-11 21:34:14,630 [Main] INFO - Application state changed: 'Disconnected'
2013-08-11 21:34:14,631 [Main] INFO - Camera state changed: 'Disconnected'
2013-08-11 21:34:15,086 [Main] INFO - -----------------------------------
2013-08-11 21:34:15,086 [Main] INFO - Application state changed: 'Disconnected'
2013-08-11 21:34:15,086 [Main] ERROR - ERROR EDS_ERR_INTERNAL_ERROR : EDSDK.EdsOpenSession(_cameraRef)
2013-08-11 21:34:15,086 [Main] ERROR - at BinaryRivers.Camera.Canon.CameraController.RunAndThrow(Func`1 function, String info)
at BinaryRivers.Camera.Canon.CameraController.Connect(String usbport)
at BinaryRivers.Orchestrator.MaestroCameraDslrExtension.CameraConnect(Maestro maestro, String drivername, Boolean postchoose)
2013-08-11 21:34:23,360 [Main] INFO - Camera state changed: 'Disconnected'
2013-08-11 21:34:23,824 [Main] INFO - -----------------------------------
2013-08-11 21:34:23,824 [Main] INFO - Application state changed: 'Disconnected'

I'm not quite sure what your saying, does the camera not power up at all, or just not with the software your using.

First port of call would be to disconnect the camera from EVERYTHING and see if it will power up, you need to determine if its a faulty camera or incompatible software.
_____________________________________________________________
EOS 1D Mark IV, EOS 50D, EOS 30D

EF 24-70 f/2.8 L, EF 24-105 f/4 L IS, EF 70-200 f/2.8 L IS, EF 100-400mm f/4.5-5.6L IS
EF-S 18-55mm f/3.5-5.6 EF 1.4 II Extender

580EX MKII, 430EX MKII

I hadn't considered that the only way the OP might be attempting to get the camera to wake up is through the software.

 

If this is indeed the case, I can vouch for the fact that that wont work.  If the camera goes to "sleep", the only way to wake it is to physically go up to the camera and press something to wake it (e.g. half-press the shutter button, etc.)

 

There is a menu for this... 

 

Yellow Wrench #1  (Press [Menu] then scroll the tab with the first yellow wrench icon).  

The top choice on that page is "Auto power off" and I believe the factory default is set to 1 minute.

It can be changed for up to 30 minutes -or- you can disable it entirely so that the camera wont auto-power off.

 

If you're working on imaging in the observatory and the camera is running off AC power instead of battery then you might want to set it to 30 minutes -or- set it to "Off" (never auto power off) but I'd only pick that choice if you bring the camera in after every session (if you leave this connected to the scope and the scope is in an observatory I probably wouldn't trust myself to remember to power off the camera.)

 

 

Tim Campbell
5D III, 5D IV, 60Da

Sorry for any confusion but the cameras would not turn on regardless. I attempted several times with the camera by itself either by battery or ac adapter and there was no response whatsoever.

I did want to post a follow-up as I've taken my rig out a few times but kept it simple. I've not had any issues w/ the 60D though I'm very nervous sometimes such as changing from M to B; I'll disconnect BYE but leave the camera on (it was during this procedure I lost the last camera). I'll also wait until the queue is empty and still give it a bit of time.

 

However, I have taken hundreds of photos over a few observing sessions and not once had an issue. It has been a tremendous pleasure to be able to enjoy capturing things from comets to nova to nebula and galaxy that even the waxing gibbous moon hasn't kept me inside (though clouds have recently).

 

Now I'm using the downtime to learn processing. When I get back out, I do plan on connecting the camera back to my laptop and using my GF's computer to slew the scope. Gradually if all goes well I'll do both on my computer again.

 

I do wish I hadn't had the issues w/ the 60Da because of the infrared issue and I won't mod this one but I do know there are some workarounds; so be it. I'm getting confidence in my equipment which is huge.

 

I am having the SAME issue. I got my canon 60Da. I took it out the first night right after i got it that day.

I was eager to try it out. I first tried to use the power cord to power it up and it would not turn on. I then trided the battery. It powered up just fine. I connected it to the telescope and then my labtop. Opened up BackyYardeos and got started. I spent about 4 hours working on taking pictures and had some with stars and some with out. I need more work on that. So i was done and i shut down the Backyard software then turned the camra off and went home. I then tried to power the camra back up and it would not. I made sure the battery had a full charge on it and tried again. Still no luck. Then started reading and some one said there was a ticking in theres. I then lessened to my camra and i could hear a fant ticking in mine.

I am now getting ready to call B&H to send it back. I will try one more camera and if it dose the same thing I think i will go after a differant camera. It is a shame because it looks like some people have had good luck with the camera and it looks like it takes good astrophotogorph pictures..

 

 

Ty

Announcements
11/22/2022: New firmware available for EOS R3, EOS R7 and EOS R10
11/16/2022: We're thrilled to be ranked among the Best Employers for Veterans in 2022 by Forbes.
10/14/2022: Help ensure your autofocus is properly aligned with a Canon Precision Alignment
09/19/2022: New firmware version 1.0.4.1 is available for EOS C70
08/31/2022: New firmware version 1.1.1 is available for RF 70-200mm L IS USM
08/09/2022: New firmware version 1.2.0 is available for CR-N 300
08/09/2022: New firmware version 1.2.0 is available for CR-N 500
07/28/2022: New firmware version 1.2.1 is available for EOS-R3
07/21/2022: New firmware version 1.6.0 is available for EOS-R5
07/21/2022: New firmware version 1.6.0 is available for EOS-R6
07/21/2022: New firmware version 1.1.0 is available for EOS-R7
07/21/2022: New firmware version 1.1.0 is available for EOS-R10
07/14/2022: New firmware version 1.0.1 is available for CR-X300
07/01/2022: New firmware version 1.3.0 is available for PowerShot PICK
06/10/2022: Service Notice:UPDATE: Canon Inkjet Printer continuous reboot loop or powering down
06/07/2022: New firmware version 1.3.2 is available for PowerShot G7 X Mark III
06/07/2022: New firmware version 1.0.3 is available for EOS M50 Mark II
05/31/2022: Did someone SAY Badges?
05/26/2022: New firmware version 1.0.5.1 is available for EOS-C500 Mark II
05/26/2022: New firmware version 1.0.3.1 is available for EOS-C300 Mark III
05/10/2022: Keep your Canon gear in optimal condition with a Canon Maintenance Service
05/05/2022: We are excited to announce that we have refreshed the ranking scale within the community!
04/26/2022: New firmware version 1.0.1.1 is available for EOS R5 C
03/23/2022: New firmware version 1.0.3.1 is available for EOS-C70
02/09/2022: Share Your Photos is back!
02/07/2022: New firmware version 1.6.1 is available for EOS-1DX Mark III
01/19/2022: READY FOR ANYTHING EOS-R5 C
01/13/2022: Community Update. We will be retiring the legacy profile avatars on 01/20/2022. Click this link to read more.
01/05/2022: Welcome to CES 2022!