My RGH might be dead. When taking an image it's stuck on "reading CCD camera". I've experienced abends on Maxim v6.12 running under ACP. These errors have yet to be explained. In an attempt to start clean I completely removed Maxim. Since that time I can connect to the main camera, but not to the RGH...so maybe it isn't really dead, but configured improperly. CCDOPS will not communicate with the camera either. Curiously, CCDOPS crashes similarly to Maxim with the following albeit evidently not terribly useful information. Note the DLL called out is the same one that Maxim lists in my other posts on the issue of Maxim crashing. Problem Event Name:APPCRASH Application Name:Ccdops.exe Application Version:5.5.8.3 Application Timestamp:54d4fac0 Fault Module Name:ntdll.dll Fault Module Version:6.1.7601.19045 Fault Module Timestamp:56258e62 Exception Code:c0150010 Exception Offset:00084a6b OS Version:6.1.7601.2.1.0.256.1 Locale ID:1033 Additional Information 1:5377 Additional Information 2:53776900658af79ba4e03b17ed4e9ab9 Additional Information 3:53fb Additional Information 4:53fb8b518c095196fc505747cbc73f1c Just an hour ago the RGH was humming along with the AO-X just fine if you ignore the abends from time to time. What approach should I take to getting this fixed? -Lloyd 678-427-6341
Hi Tim... It's been a while since I've been able to test the system. The 16803 just got back to me and I installed it yesterday. The abend persists...it only did it once and at no particular time. The system was under the control of ACP Expert and it just stopped and gave the same abend info as above. I have since turned on logging as per your earlier guidance. Hopefully I can trap the error next imaging session. Do you know what role ntdll.dll might have in this? There are lots of varied reports on this dll as the named cause of various issues. It's a rather low level component of windows. Will follow what ever protocol you can suggest. Until then, I'll keep logging on.
