D7000 - COM access denied

[jbrazio]

Hi,

After the 2.0.2 update my D7000 bulb mode stopped working with the error: Access to the port COMXX is denied.

I've searched and I see another related issue with the D5100 but no progress since beginning of May.

[admin]

 Ok, I think I got it.

Basically I made the port for the MBox configurable and it will only scan the configured port to verify if the MBox is available... leaving all other ports alone.

Please try this download, it has both BYN/BYE serial cable port denied bug fix.  This is not an official release, just a preview build with this bug fix.  If it works use it but as soon as I release it officially this link will disappear.

https://www.dropbox.com/sh/5m1u7zzvyjnjks3/AACj0_iksHfDJB_jCICXhl8Za?dl=0

Regards,

 

[admin]

Progress has been made... but not fixed yet, it's related to the installer.

What version were your using when it worked?  I may want to install that version again until this is resolved

Regards,

[jbrazio]

I believe it was 2.0.0.

Is there something we can "manually" do to make the latest version work ?

[jbrazio]

I have fallen back to 2.0.0 and RTS trigger is fully working.

[admin]

2 hours ago, jbrazio said:

I have fallen back to 2.0.0 and RTS trigger is fully working.

Thanks.

[admin]

4 hours ago, jbrazio said:

I believe it was 2.0.0.

Is there something we can "manually" do to make the latest version work ?

No, its a bug I need to fix

[admin]

3 hours ago, admin said:

Thanks.

Can you do me a favor?  Can you try 2.0.1 and see if this one works?

I only have 7 commits between 2.0.0 and 2.0.1 but I have over 30 commits since 2.0.1.  This should help to look at what changed since the last version it was working in.

Regards,

[skaven]

Commenting to subscribe to this thread.  I'll try the latest 2.0.x version as soon as I get back from Texas Star Party.

[admin]

I'm actually going through each commit I made since then one by one and rebuilding the app, installing , and then testing.  It's a painful process but I need/want to know exactly what I did to brake it in order to resolve it.

[skaven]

If your code is stored in git, use `git bisect` to find the offending commit -- much faster!

[astroman133]

Do you have a cable that shows the behavior? Does the DSUSB cable work or fail the same way?

Have you considered that a .NET update changed the behavior of the serial port class(es) and that it is not your app at all? Well, if that is the case, you should still have a problem with all versions of BYN, so that will point to an external difference.

Good luck!

[admin]

Found it.  It was the commit where we implemented the MBox.

Chris did this implementation so I'll have to check with him.  The MBox is a serial device and it scans all ports in an attempt to locate the device.... in the process it places a lock on the port used by the serial cable and does not release it... and this causes the access denied error.

Boy this was a pain to troubleshoot... I kept looking at code around the serial cable implementation and it was nowhere near.  And the fact that it always work from my development environment but not via the installer made things a bit more difficult.

Now the job begins to solve it without breaking the MBox implementation, they booth need to play nice with each other.

Regards,

[skaven]

This is great news!  I'm glad you found the root cause.  Once you have a test build, I'll be happy to try it out.

[fme001]

Thanks for the fix Guylain , I'm going to try it the evening.

Follow up => Tested = working !!

[admin]

On 5/24/2017 at 2:02 AM, fme001 said:

Thanks for the fix Guylain , I'm going to try it the evening.

Follow up => Tested = working !!

This is great news, finally!

It's beer o'clock then

[BigRD]

Sorted! Thanks Guylain. Tested with various plans with different exposure times. Worked every time.

Hope you're enjoying a cold beer.

[mikeonnet]

Hi Guys, sorry to jump on this post but I thought I would update you with the same issue I had (Access to the port Com6 denied). I upgraded to 3.12 still with the same issue but after reading this post and downloading the "unofficial" 3.1.12 RC from the dropbox link above, I can also now say that this has resolved the problem also. I'm assuming it's OK to carry on using this version for now (3.1.12 RC)?

It was perfect clear skies lastnight (UK) but a whole night wasted trying to get my Canon 400D to take exposures uninstalling everything, reinstalling etc but at least it's now shooting via the serial com port perfect and it should be another clear night tonight. So fingers crossed. Thanks.

[admin]

Yes, it is ok to use 3.1.12 RC fro the link above.  It is ready for release but I want to fix/address a few more things first.

[admin]

On 5/22/2017 at 10:33 PM, admin said:

 Ok, I think I got it.

Basically I made the port for the MBox configurable and it will only scan the configured port to verify if the MBox is available... leaving all other ports alone.

Please try this download, it has both BYN/BYE serial cable port denied bug fix.  This is not an official release, just a preview build with this bug fix.  If it works use it but as soon as I release it officially this link will disappear.

https://www.dropbox.com/sh/5m1u7zzvyjnjks3/AACj0_iksHfDJB_jCICXhl8Za?dl=0

Regards,

 

I will mark this thread a solved them.

Thank you for your patience on this one, it was a long road.