Re: [micro-manager-general] Hamamatsu ORCA-ER Problem

[Mark T. <mar...@gm...>]

Hi Neil,

On Thu, Aug 14, 2014 at 01:33:19PM -0700, nranthony wrote:
> Hamamatsu ORCA-ER  C4742-95-12ERG
> µManager v1.4.18 & 1.4.10
[...]
> - µManager reports Error message unavailable (40) on Adding the
>   HamamatsuHam

On Tue, Aug 19, 2014 at 07:37:28AM -0700, nranthony wrote:
> The errors seen with this setup have, alas, been a collaborative process, so
> the information is in pieces.  Here is the information I received of what
> happened before the above details:
> 
> /The camera was previously working with 1.4.1
> 
> The computer is 32 bit windows 7 professional
> 
> A different, not well documented, problem occurred when I updated uManager.
> Then I tried to roll back to the old version, which would work until I tried
> to make a new hardware configuration and then it would not be able to
> connect to the camera. Then I tried to update the driver, Im fairly sure I
> could have messed something up at this point, and then you came in.
> 
> I just started things up, I attached the log and error files
> CoreLog20140818.txt
> <http://micro-manager.3463995.n2.nabble.com/file/n7583671/CoreLog20140818.txt>  
> hs_err_pid5228.log
> <http://micro-manager.3463995.n2.nabble.com/file/n7583671/hs_err_pid5228.log>  
> 
> This is what happened:
> 
> Start MM, load previously working configuration
> 
> Do "Live" works
> Stop live
> Click "Snap"
> Error – Camera Image Buffer Read failed
> Click "Snap"
> Worked
> Go to MultiD and set z stack
> Acquire
> Error – Acquisition failed Device failure: HamamatsuHam_DCAM
> Error – Acquisition cleanup failed
> 
> Went to Hardware configuration Wizard, got more errors about the camera.
> Unable to load either Hamamatsu Driver./

Is it 1.4.1 or 1.4.10, or both that was previously working (I thought
you were having the error 40 problem with both 1.4.10 and 1.4.18, and
you say that 1.4.1 was the working version, but when you "roll back to
the old version", the CoreLog records 1.4.10)?

In any case, it is a little hard to troubleshoot such old versions. It
is possible that the older Micro-Manager versions are not compatible
with the latest DCAM-API, in which case you might need to roll back the
driver in the Windows Device Manager (or use Windows's "System Restore",
if the restore point from before installing the new driver is still
available).

Best,
Mark


-- 
Mark Tsuchida
Micro-Manager Team (UCSF Vale Lab)