Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Gemini 2 L 6.02 Needed to Be Re-Flashed
I've been running L6.02 for 7 months, since May, and it has run beautifully.... my guide error went way down as compared to L5, and my plate solving got a lot more accurate.
?
Then, about a week ago, my plate solving all of a sudden crashed.? Normally, I can get within 10 pixels of error for both RA and DEC, but all of a sudden, I could not get any better than 600 pixels error for RA, and around 3000 pixels for DEC.? The error started initially at much larger values, and would get better for successive solving attempts, but never got better than 600/3000.
?
I use ASTAP in SGP for my plate solving, and I kept double checking all the specs for camera and plate solving, and could not come up with any setup mistakes.
?
So..... I re-flashed Gemini to L6.02 again with the GFU.? I did a Cold Start and synced on a bright star.
?
I then slewed to 2 different objects, 2 different solving attempts.? On the first object, I solved to less than 10 pixel error for both axes on the 3rd attempt, and on the second object, I solved to less than 10 pixels both axes for the second attempt.
?
I am convinced a re-flash of L6.02 was necessary, and fixed my plate solving problem.
?
Has anyone else had to do this?? What could have caused this?? It seems as though somehow L6.02 got corrupted.
?
Thanks in advance.
?
Dan
?
?? |
Hi Dan,
?
I suspect you just needed a reset of Gemini settings and not a full firmware re-flash. Firmware flashing operation can clear out and reset Gemini settings, so you may have done what was necessary, anyway :)
?
The settings storage in volatile memory is much more "corruptible" than flashed firmware, which is why I think that's where your issue was. But, it is also possible that the firmware could get corrupted. All electronic circuits are subjected to constant bombardment by cosmic rays, for example. This can cause occasional bits to be randomly flipped. Error correction circuits usually take care of fixing these, but not always. Sudden supply voltage change, static electricity, etc. can also result in data corruption.
?
Regards,
?
? -Paul
?
On Sat, Dec 21, 2024 at 10:13 AM, <dkfcpalfd@...> wrote:
|
Thanks for that, Paul.
?
It sounds like you are saying something like an HGM Reset on the HC (not looking at it now, but that's my recollection)?
?
I had run PEMPro 7 months ago, when I first flashed the 6.02 firmware, and my guiding got superb.? After last night's reflash, I noticed the reflash wiped out my PEC data on the table, so I just uploaded the same PEC curve from 7 months ago.? My RA guiding was lousy after that.??
?
I then tried just training the drive from the HC, it seemed to be improved, but I think I need to collect data by camera and rerun PEMPro again.
?
Do you happen to know if L6.02 is improved for PEC training via the HC vs. L5.0?
?
Let me know if an HGM Reset on HC is what I needed to do.
?
Thanks so much.
?
Dan |
?
PEC shouldn't work after a full reset, and programming the same PEC curve shouldn't work either. Gemini keeps track of the current worm position in memory. When you reset all settings or do a reflash that does the same, Gemini will no longer remember the correct worm position. As the result PEC will be played back out of sync (out of phase) with the actual worm error, which is likely to make tracking error even worse than without PEC. If you want PEC, you'll need to redo PEMPro calibration/capture/program steps one more time.
?
Regards,
?
? -Paul
?
On Sat, Dec 21, 2024 at 09:53 PM, <dkfcpalfd@...> wrote:
|
to navigate to use esc to dismiss