Hi John,
AP4 is returning the "star too bright" message when I try to do a RGB Measurement. I get the same result on multiple targets and with or without "AUTO" checked.
Although the target G2V is in the center of my chip (FLI P9000), AP appears to be looking at a sub frame with a hot pixel near the edge of the chip. This location is always the same: x=65,y=317,H=W=140.
I have tried to use auto darks but I believe that AP overides the Maxim 4.62 Settings.
I note that the Trace log shows flush series but I have this feature turned off in Maxim.
I have attached a trace log, a session log with my equipment setup, and a subframe with the hot pixel.
All other AP features seem to be working fine.
Thanks in advance for any help or guidance you can provide.
Frank

Trace20090923_195300_RGB_Ratio_Auto.log (1 KB, 11 downloads) Fits sub frame

What is the peak ADU of the hot pixel?

Never mind - figured it out. Based on the exposure length, it appears to be more of a stuck pixel than a hot pixel.

Nevertheless, if you want to test along with me, try the attached patch file. I think it will solve your issue. Copy the attached ccdautopilot.exe to C\Program Files\CCDWare\CCDAutoPilot4. You may want to back up the original ccdautopilot.exe just in case.

If you give it a test, let me know how it works out.

ccdap4158p1.zip (394 KB, 1 downloads) patch file

Hi John;
The hot pixel is 65536 ADU.
Subframe is attached.
Thanks
Frank

RGB_Ratio_Auto.fit (45 KB, 4 downloads) Sub with hot pixel

Thanks for the patch John,
Hope to try it tonight and will keep you posted.
Frank

Hi John;
I ran the patch last night with generally good results.
In one case the G2 star was being overexposed. Canceling the measurement resulted in an Unhandled Exception.
A second run with 5 stars was perfect.
I am using a FLI PL9000 and Maxim4.62.
Traces and some noted are attached.
Thanks for your help,
Frank

quote:

Originally posted by John Smith:
Never mind - figured it out. Based on the exposure length, it appears to be more of a stuck pixel than a hot pixel.

Nevertheless, if you want to test along with me, try the attached patch file. I think it will solve your issue. Copy the attached ccdautopilot.exe to C\Program Files\CCDWare\CCDAutoPilot4. You may want to back up the original ccdautopilot.exe just in case.

If you give it a test, let me know how it works out.

Traces.txt (25 KB, 5 downloads)

Hi Frank,

Unfortunately there is no (elegant) way to abort a G2V run once it has started. This is probably why the unhandled exception was triggered. This is something that needs to be done at some point.

I take it there were no issues with your hot pixel in any case?

Hi John;
I ran the RGB Measure about 10 times. It worked good and gave consistant results excluding the overexposures mentioned in my previous message.
Thanks again,
Frank

Great! Thanks, Fred.