
If you have any issue and FoCal crashes, if you immediately restart FoCal and connect to the camera you will be given the option to restore the camera settings at this point. With regards to restoring the camera settings – before any test starts, FoCal saves the camera settings to disk. disconnect FoCal and try to take a shot by pressing the shutter button and the camera will fail to focus). Note that this issue is not a problem with FoCal – there seem to be certain times where the camera will fail to report AF lock with some lenses even when manually controlled (i.e.

You may find that if you rerun the test with the camera moved a little (20cm or so) either nearer or farther from the target you will get a successful test result. We have noticed that Sigma lenses in particular can be a little susceptible to “Failed to Focus” errors at certain specific distances (especially the Sigma 50/1.4). We don’t have a Sigma 85/1.4 in the lab all the time but have done a fair amount of testing with it without any significant issues. Thanks and all the best from the FoCal Team. In the meantime please continue to use the above workaround until this issue is resolved. As I suspected, my copy is significantly sharper at f1.8 than at f1.4.
#Reikan focal 85 1.8 update
Many thanks for your understanding and we’ll update you as we learn more. I did just micro-adjust my 58mm using Reikan FoCal software. We’re trying to isolate the problem but as you can appreciate the fact that it appears to be un-reproducible at this point makes it hard to determine if its genuinely a problem in the Canon SDK or elsewhere. Don’t worry FoCal will make all the actual changes automatically. So if you see this problem please go into the AFMA settings and set it to per lens and then change the value on the lens you’re testing to say -1. What we have found in all cases so far that setting the AFMA to ‘per lens’ and making a change by hand to the AFMA value seems to make the camera behave as expected. In fact the one time we saw this behavior it was after changing lenses with the power left on and connected to FoCal. It doesn’t seem linked ot any particular feature (we’ve combinations of custom functions such as disabling shutting release before connecting to FoCal) and it doesn’t seem reproducible. We’ve seen this once after some heavy testing after the the first reports came in. For some reason the camera doesn’t always respond to changes of AFMA made via the SDK.

We’ve tracked this down to an issue with changing the AFMA value automatically.

The symptoms manifest as FoCal reporting that it needs to take more shots because of inconsistent results and the resultant graph has shots that are as sharp across all AFMA values. We’ve been getting reports that some (not all) Canon EOS 6D cameras can give erratic results using FoCal.
