Keyboard Shortcuts
Likes
Search
Problem with PEMPro not drawing in all needed G11G (Gemini 2) Mount & Camera info for valid PE review and analysis
Hi, I posted an issue over in CN Software, but I don't seem to be getting someone who may know the answer. I decided to map out and see about improving the basic PE in my mount using PEMPro. I have solved an earlier issue with connecting the mount and camera, but now, on the data gathering runs I have made o far, I can't get the log files to consistently suck in all the complete mount/camera scale information and tracking data for that run that allows proper analysis and follow-on PEC curving when reviewing the data. There has been a few occurrences when it did get all the right info, but I can't figure out why on some runs and not on others, usually the ones that worked are after I repositioned the scope, but I don't think it has anything to do with the repositioning, but rather with the integration between the information coming from ASCOM on the mount and camera, versus what is loaded into PEMPro directly or as default. Or maybe the way I connect the devices, but I have tried different things and there is no consistency to when this happens and when it doesn't. I have run the mount wizard and the calibration wizard, I get thru those ok, but it seems to have no affect. On the log files with the missing info, PEMPro wants to use its default values (such as worm period of 10) to create the PE chart and PEMPro Log Viewer will not properly run on those files at all because of the missing info (it doesn't have default values) , if I cut and paste in the info from the runs that did work I can get Log Viewer to work on those files.?
? On the collected data side, on those data runs that have the missing mount/scope info, there is also a missing data element that is seemingly important, it is the value in the column with the Controller Step for each exposure, that seems to be important for curve loading, it puts 1's in there instead of the step location....below are examples. ? I am sure this is something simple, like what I am connecting first, or how I set up for the runs, but can't figure it out. BTW I do have to Bin 2 just to get it to work thru calibration due to the file size on Bin 1 on that camera. Any ideas are appreciated. ? A Data Run Log File Extract Showing some of the Missing Mount/Camera info: # Gemini Firmware # # Gemini PEC Status # 0 # Gemini Worm Teeth # -270 # Gemini Guide Rate # 0.5 # Gemini PEC Guide Rate # 1 # Gemini PEC Cells # 12800 # Gemini PEC Max # 25600 # Gemini RA Spur Ratio # 25 # Gemini RA Encoder Resolution # 256 # Gemini RA Multiplier # 1 # Gemini PEC Worm Cycles # 2 # Gemini PEC Table Period # 0 # Gemini Minimum Step Size # 0 # Gemini PEC Index # 1 # Gemini PEC Phase # 0 # Camera Software # ASCOM # CCD Dimensions # 6280 4210 # CCD SubFrame # 50 x 50 # CCD Binning # 2 # Worm Period # 0.0000 # Rotation # 89.6270 # Reverse # False # Invert Curve # False # PEC State # PEC OFF ? A Data Run Log File extract from the same area from a good data file: # Gemini Firmware # 5.21 # Gemini PEC Status # 0 # Gemini Worm Teeth # 360 # Gemini Guide Rate # 0.5 # Gemini PEC Guide Rate # 0.5 # Gemini PEC Cells # 12800 # Gemini PEC Max # 6400 # Gemini RA Spur Ratio # 25 # Gemini RA Encoder Resolution # 256 # Gemini RA Multiplier # 1 # Gemini PEC Worm Cycles # 2 # Gemini PEC Table Period # 478.68939183834 # Gemini Minimum Step Size # 0.5625 # Gemini PEC Index # 1119 # Gemini PEC Phase # 41.8479241771174 # Camera Software # ASCOM # CCD Dimensions # 3140 2105 # CCD SubFrame # 50 x 50 # CCD Binning # 2 # Worm Period # 239.3447 # Rotation # -89.7188 # Reverse # False # Invert Curve # False # PEC State # PEC OFF ? Sample data line missing Stepper info (See 1's): 1 0:00:00.000 1606 198 26.024 26.347 32767.00 1 C:\Users\User\Documents\CCDWare\PEMProV3\Images\PEMPro_Ascom_0001.fit 2 0:00:03.191 1606 200 26.075 25.009 32767.00 1 C:\Users\User\Documents\CCDWare\PEMProV3\Images\PEMPro_Ascom_0002.fit ? Sample data line with good Stepper info (See 1431, 1516): 1 0:00:00.002 174 734 24.303 26.228 32767.00 1431 C:\Users\User\Documents\CCDWare\PEMProV3\Images\PEMPro_Ascom_0001.fit 2 0:00:03.167 174 736 24.040 23.385 32767.00 1516 C:\Users\User\Documents\CCDWare\PEMProV3\Images\PEMPro_Ascom_0002.fit ? I will explore all the info that is out there on analyzing, fitting a curve, the 76 sec issue, etc. I just need to get past this operational stuff first. ? Thanks |
Hi Mike,
toggle quoted message
Show quoted text
PEMPro reads the Gemini 2 settings using the Gemini ASCOM driver. It could be that communications failed intermittently between the Gemini driver and the mount, leaving some parameters missing when PEMPRo tried to read them. I can look at your logs if you use the PEMPro Log Zipper (in the Wizards menu) to zip all of the logs and Debug logs. You can attach it to a post here. -Ray Gralak (Author of PEMPro) -----Original Message----- |
Hi Ray, thank you for getting back to me. I have attached a zip of 5 files, 4 are the log file data runs for Nov. 13th, the 5th is the debug file for those runs.?
?
Run 1 - File 210114 (Full 30 min, Log is missing needed info to properly analyze)
Run 2 - File 214144 (Ended after 23 min. due to approaching Meridian, Log is missing needed info to properly analyze)
Repositioned scope using hand controller between Runs 2 and 3 to a part of the sky where I normally image, I believe I ran the calibration wizard again)
Runs 3 and 4 - Files 221509 and 225519 (Both ran full 30 min., both have all needed log info and run fine in Analysis and Log Viewer)
?
Also, if you can answer, what is the data element (Stepper Location) I described above and why would that also be missing from those problem runs, seems to indicate that no information was communicated from Gemini or the mount at all during those runs.
?
Thank you again for any help |
Hi Mike,
toggle quoted message
Show quoted text
The debug log does not indicate the underlying cause, but there was a lapse in communication with the Gemini driver from about 20:38:08 to 22:12:00, resulting in some empty mount values. I'll put in a check for communication problems like this in the next build. I also noticed that the selected star was saturated at 32,767.00 (the brightest pixel in the star) throughout the four logs. This indicates the star was saturated which can produce inaccurate star centroid locations. To fix this you should set the Max Star Brightness to 15,000 on PEMPro's setup tab. -Ray -----Original Message----- |