T7i Support

[sjgoossen]

Just tried 3.1.11,  still won't connect to my T7i's (got 2).

any word from Canon when they will be releasing the SDK, and/or when BYE will support the T7i ?

 

cheers,

            sjg

 

[dvwalker]

looks like the m5 was canon's first digic 7 image processor camera to hit the retail market back at end of 2016.   As a new t7i user,  I'm hoping canon sdk team begin their development life cycle from that timeline, and release is fast approaching.  

As a side note, just finished watching all the excellent BYE overview video's which lead me to purchase the classic edition for now.   Excellent info in the videos thanks for sharing your passion of love with the community.    Must say the application GUI makes complex tasks so intuitive and stupid easy, this is very difficult to achieve so excellent job.  Can't wait to use future release of BYE with my new t7i.

[admin]

Thank you for the kind words.

I checked yesterday and the SDK is not out yet

Regards,

[sjgoossen]

just so you don't feel alone ... both MaxIm DL and TSX are seeing issues with the new SDK/DLL's...

cheers,

             sjg

 

[admin]

4 minutes ago, sjgoossen said:

just so you don't feel alone ... both MaxIm DL and TSX are seeing issues with the new SDK/DLL's...

cheers,

             sjg

 

The T7i will work with the pre-release 3.1.12 RC5.  Go to download section an download the pre-release.

Regards,

[sjgoossen]

thanks, so far so good.  (doing a 500 frame run atm...) also really like the full 25slot display... (i'm using 22 for daylight-2-daylight timelapse work :-) )

cheers,

 

[sjgoossen]

well.... displaying all 25 exposure slots is nice, however when loading saved sequences (from 3.1.11) everything was loaded... except exposure times !!!

also 500 frame run terminated @ 325, but suspect this in a win 10 issue...

 

cheers,

 

[sjgoossen]

hitting the 'reset' button (after loading one of the above saved sequences, BYE hung... 'non responsive' on exit attempt...

seq file attached....

cheers,

           sjg

dusk til dawn.txt

[admin]

Can you post the log files.  This is running fine here.

[admin]

Hi, I just tried 3 times on 3 computers using your attached plan and I was able to load your saved plans all the time using RC5.

Please install in a new folder at try again, I'm curious to see if it will work on a different install.

[astroman133]

4 hours ago, sjgoossen said:

hitting the 'reset' button (after loading one of the above saved sequences, BYE hung... 'non responsive' on exit attempt...

seq file attached....

cheers,

           sjg

dusk til dawn.txt

I am unable to duplicate what you are reporting with either version 3.1.11 or 3.1.12RC5. I can load your dust til dawn capture plan and clear it by pressing Reset. BYE does not misbehave.

Although I confess to being confused by what you are reporting. Did BYE become non-responsive after resetting the capture plan or when attempting to exit the program? I tried to duplicate both behaviors and could not. I will say that if you power the camera off while BYE is connected, it may hang. That is easily avoided, however.

[sjgoossen]

unfortunately we're just getting ready to head out of town for a few days (i.e. the equip is packed up).  We send the logs once i have access again.

the big issue for me is losing the exposure times in the capture plan.

on the non-responsive issue, once after hitting reset,  second time reset went fine but exiting after hung the prog...

will try a)duplicating  and be running with a std install. current config has some files in my doc dir, and image cap in user\public...

 

cheers,

          sjg

[astroman133]

Again, I am able to load your exposure plan into BYE 3.1.12 RC5 and all the values are displayed, including the Shutter values. The bulb Duration values are empty since you are using all Tv values.

[admin]

23 minutes ago, astroman133 said:

Again, I am able to load your exposure plan into BYE 3.1.12 RC5 and all the values are displayed, including the Shutter values. The bulb Duration values are empty since you are using all Tv values.

Same here so please keep us posted on your findings when get the time to try a duplicate the issue.

Regards,

[sjgoossen]

see next post

 

[sjgoossen]

plan is on the left, on the right is the result of loading the plan... (byeload in zip file)

some notes: 

Camera is in M, on/off it @ on <also has video mode>

Current camera exposure is 15sec. (verified via EOS util, which was killed before starting BYE)

Creating a 'new' plan works fine (light_new_plan.txt)

Loading the old dusk til dawn results in the attached jpg

Saving the old dusk til dawn <Light-dusk2dawn_new> loses the TV values in the original

note that the original dusk-til-dawn plan was created with a different camera (old Xti) with fewer ISO values

bye screen caps.zipbye screen caps.zip

logfile-[20170618-17h46m25s923]-[6484]-2017-06-18.zip

 

cheers,

          sjg

[astroman133]

sjg,

I am able to duplicate what you are seeing when I use BYE 3.1.11, but the plan loads correctly when I use 3.1.12 RC5!

I am not sure what is going on but it seems like it may be fixed in the next release.

I guess the reason that I did not see it before was because I was using the release candidate to test some other changes for Guylain.

This is good news!

Thanks!

[admin]

In RC5 I'm doing using an InvariantCultaure when performing an Equal operation to locate the shutter speed.  That was the only thing I could find that could be the culprit here.  Looks like this might have been it.

[astroman133]

Canon doesn't publicize when they will release new versions of the SDK. In fact, the SDK is not actually supported at all. It has been released in different parts of the world months apart and Guylain is bound to only distribute the North American release. He and we are entirely at Canon's mercy.

I know that it is not what you want to hear, but it could be months before Canon has released a version of the SDK that supports the T7i. It could also be just a few weeks.

[admin]

It won't connect because it is not supported yet.

See camera support grid here: https://www.otelescope.com/store/category/2-backyardeos/

Based on past history it can take Canon between 4 to 8 months to release the SDK

Sad but true.