EOS 200D not connecting to BYEOS either with WIFI or USB

[AstroDazee]

Below is the Log file from BYEOS. 

Camera connects ok with EOS Utility using WIFI but not to BYEOS.

Camera is the Canon 200D 

Computer is running windows 8 64bit.

11:08:57  Licensed to AstroDazee
11:08:57  Processor Affinity
11:09:53  Attempting to connect camera...
11:09:53  Canon drivers 'Canon\' initialized.
11:09:54  DEVICEINFO DESCRIPTION IS Canon EOS 200D
11:09:54  DEVICEINFO NUMBER IS 2971957804.
11:09:54  YOUR *REAL* MODEL NUMBER IS 2147484695(80000417)
11:09:54  YOUR camera is not currently supported by the Canon SDK available at the time of this software release.
11:09:54  Camera Not Found!  Make sure it's connected to the PC and turned ON

[admin]

What version of BYE? 

[AstroDazee]

3.1.16 premium

 

[admin]

That would do it.

3.1.16 is almost 2 years old.

Support to the 200D was added in 3.1.17.  Please upgrade.

Wifi is not officially supported in BYE.

[AstroDazee]

updated version to 3.1.17 and get this far

 

12:53:22  Licensed to AstroDazee
12:53:22  Processor Affinity
12:54:19  Attempting to connect camera...
12:54:19  Canon drivers 'Canon\' initialized.
12:54:24  Attempting to connect camera...
12:54:24  Canon drivers 'Canon\' initialized.
12:54:42  Attempting to connect camera...
12:54:42  Canon drivers 'Canon\' initialized.
13:00:29  Attempting to connect camera...
13:00:29  Canon drivers 'Canon\' initialized.
13:00:49  Attempting to connect camera...
13:00:49  Canon drivers 'Canon\' initialized.
13:02:11  Attempting to connect camera...
13:02:11  Canon drivers 'Canon\' initialized.
13:03:27  Attempting to connect camera...
13:03:27  Canon drivers 'Canon\' initialized.
13:03:48  Attempting to connect camera...
13:03:48  Canon drivers 'Canon\' initialized.
13:04:14  Attempting to connect camera...
13:04:14  Canon drivers 'Canon\' initialized.

[admin]

3 minutes ago, AstroDazee said:

updated version to 3.1.17 and get this far

 

12:53:22  Licensed to AstroDazee
12:53:22  Processor Affinity
12:54:19  Attempting to connect camera...
12:54:19  Canon drivers 'Canon\' initialized.
12:54:24  Attempting to connect camera...
12:54:24  Canon drivers 'Canon\' initialized.
12:54:42  Attempting to connect camera...
12:54:42  Canon drivers 'Canon\' initialized.
13:00:29  Attempting to connect camera...
13:00:29  Canon drivers 'Canon\' initialized.
13:00:49  Attempting to connect camera...
13:00:49  Canon drivers 'Canon\' initialized.
13:02:11  Attempting to connect camera...
13:02:11  Canon drivers 'Canon\' initialized.
13:03:27  Attempting to connect camera...
13:03:27  Canon drivers 'Canon\' initialized.
13:03:48  Attempting to connect camera...
13:03:48  Canon drivers 'Canon\' initialized.
13:04:14  Attempting to connect camera...
13:04:14  Canon drivers 'Canon\' initialized.

That is not very helpful

Is the camera connected to the PC with the USB cable?

 

[admin]

Also, please try with the latest 3.1.18-RC3 in the pre-release section, I updated the Canon SDK to the latest early August in that pre-release.

[AstroDazee]

ok thank you it seems to be working now. Just have to get my head around how to run the programme properly. Working with wifi also which is good.

Thank you again...

[s3igell]

It is good to hear that you are reporting Success using WiFi connectivity.

Please elaborate a bit on how you are connecting to WiFi - directly from startup or starting BYE Connection via USB during EOS Utility use (as has been the trick for some previous Canon DSLRs).

Please realize that Canon has never guaranteed WiFi support through its Canon SDK (software required to connect to the DSLR), so Guylain has been hesitant to provide debugging support for WiFi.  If your EOS R connects easily via WiFi, perhaps this is signs of a Change at Canon - and good for more future Canon DSLRs.

[AstroDazee]

Hi there, I think the main crux to getting wifi to work with my Canon 200D was up grading the BYE to the recent latest 3.1.18-RC3  version. This update only came out last month I believe. I first started with 3.1.16 which totally didn’t work.

3.1.17 wasn’t much better either. Finally when admin offered the link to 3.1.18-RC3 which is still in the pre-release area of BYE somewhere.

but anyway, after updating BYEOS started working. Not smoothly though. This I think was mainly due to not really fully understanding how to use the program. 

I wanted to do 180 x 60sec exposures in my backyard but it didn’t like it. If just froze after the first exposure. Using abort or suspend didn’t help either. It was a matter of disconnecting the wifi connection and start again. This didn’t work either. 

I ended up doing shorter plans of 20 x 60sec exposures. Will try 50, 75, 100 etc soon to see how many it likes without freezing. 

Ive always been able to connect to the EOS utility on start up when downloading files from my camera to the laptop without a hitch. BYE won’t connect if EOS utility is running so make sure it is not running. 

I have an ASUS Laptop running Windows 10 with 64bit. This is only a few mths old. 

My camera is a Canon 200D DSLR which is less than 12mths old.

There was a lot of connecting and dis-connecting before I managed to get it up and running properly.

so that’s about it, any Q’s please ask. I’m kore than happy to try and answer. 

[astroman133]

BYE takes the exposures 1 at a time so I would think that it is very unlikely that the number of exposures would cause a capture plan to fail.

I would also be curious if you can reboot the PC and get BYE to connect to the camera via WiFi without running the EOS Utility first.

[admin]

If BYE works to x exposures and fails after x+1 then there is something else going on.  I run BYE regularly with 1000+ images as stress tests.

In most cases where BYE freezes after x+1 images down the road is caused by Windows going to sleep, or even hard drive going to sleep.  In your case, and it's one of the reason I don't officially support WIFI, is that your WIFI may have stopped transmitting for a short while... a single 1 millisecond interruption in communication and all bets are off... it will stop working because as far as BYE knows the camera has disconnected due to a break in communication.