I just upgraded Gemini firmware and ASCOM 7 software and the mount keeps turning off PEC while doing imaging session.
Sometimes I see PEC checkbox is unchecked from Gemini hand controller screen. I also noticed from PHD log viewer after imaging night.
I don't really know if this is really related to the firmware and software update since I don't have old data.
I use NINA software to control everything. Is there any log in the Gemini to tell me why it turned off PEC?
|
On Fri, Feb 28, 2025 at 03:17 AM, Seokman Han wrote:
I just upgraded Gemini firmware and ASCOM 7 software and the mount keeps turning off PEC while doing imaging session.
Sometimes I see PEC checkbox is unchecked from Gemini hand controller screen. I also noticed from PHD log viewer after imaging night.
I don't really know if this is really related to the firmware and software update since I don't have old data.
I use NINA software to control everything. Is there any log in the Gemini to tell me why it turned off PEC?
It keeps turning off in the middle of a session, not at the beginning? That's strange.
?
ASCOM 7 is the common ASCOM platform across all mounts and devices, it doesn't know anything about Gemini or how to talk to it, or, how to turn on or off PEC. That's the job of the Gemini.NET ASCOM driver. Did you update that as well? What version of the driver do you have installed? The driver generates logs for the session, as well as, NINA. You can check both logs for errors or possibly disconnects.
?
?
|
Seokman,
You are not alone. I¡¯ve had the same thing happening to me for a few months now. It happens every session. At this point I check to see if PEC is still enabled after the sequence has been running a while and it consistently has been deselected at some point. I¡¯ve considered it a nuisance since my PEC on/vs PEC off performance is only about a 0.2 arcsec difference, I check fairly early in the sequence, and it seems to stay on after I manually enable it at that time again.?
It¡¯s been cloudy so my mount is inside but I¡¯ll grab my logs, ASCOM driver version, NINA version, and Gemini2 firmware version this weekend so we can compare notes.?
Ryan?
|
I actually updated to the new firmware and the software in January and noticed this PEC turning off problem. Last couple of nights I? got clear nights and both nights PEC appears to be off from looking at the PHD log file even though I had PEC checkbox was on. I don't know if this is a related issue or not, but the last couple of nights Gemini became unresponsive in the middle of night. It was disconnected from NINA, and I could not bring up the web page in the morning. I connected the hand controller, and the HC kept rebooting. I'm using 6.1 Gemini firmware. 1.1.28.0 Driver, 7.0.2 ASCOM Platform, and 3.1 HF2 NINA software. I will try to capture ASCOM log.
?
Thank you,
Seokman
?
|
On Fri, Feb 28, 2025 at 04:30 PM, Seokman Han wrote:
I actually updated to the new firmware and the software in January and noticed this PEC turning off problem. Last couple of nights I? got clear nights and both nights PEC appears to be off from looking at the PHD log file even though I had PEC checkbox was on. I don't know if this is a related issue or not, but the last couple of nights Gemini became unresponsive in the middle of night. It was disconnected from NINA, and I could not bring up the web page in the morning. I connected the hand controller, and the HC kept rebooting. I'm using 6.1 Gemini firmware. 1.1.28.0 Driver, 7.0.2 ASCOM Platform, and 3.1 HF2 NINA software. I will try to capture ASCOM log.
?
If PEC checkbox is on in the driver virtual hand-controller, then Gemini is reporting that PEC is being used. But, Gemini becoming unresponsive sounds like a bigger issue.?
?
If you use Ethernet to connect to Gemini, can you start Gemini.NET ASCOM driver, connect to the mount, and then go to Menu->Setup->Troubleshooting Report... Select all options in the list, and press Collect and Save button. Then, upload the resulting zip file to the Files section. This will include your ASCOM logs, as well as, a lot more information from Gemini.
?
?
Regards,
?
? -Paul
|
Hi Paul,
?
I uploaded the reporting Zip file to files section.
One more thing I noticed is that when I click on Setup -> Advanced Gemini Settings..., I get an error message saying 'Communications error' However I can still click on any of 'Get Settings From Gemini' from the settings screen and it gets settings from the Gemini.
?
Thank you,
Seokman
|
On Fri, Feb 28, 2025 at 05:41 PM, Seokman Han wrote:
Hi Paul,
?
I uploaded the reporting Zip file to files section.
One more thing I noticed is that when I click on Setup -> Advanced Gemini Settings..., I get an error message saying 'Communications error' However I can still click on any of 'Get Settings From Gemini' from the settings screen and it gets settings from the Gemini.
?
Thank you,
Seokman
?
Hi Seokman,
Thanks for uploading this! Looking into Gemini status log, it appears you've been experiencing very frequent restarts after a watchdog reset events (WD Reset). Here are some of the latest:
26264.88672 PECWormPos 7858, Restarted after WD Reset. UTC Date_Time 2025.02.26_04:57:01
26288.96875 PECWormPos 8755, Restarted after WD Reset. UTC Date_Time 2025.02.26_04:57:25
73736.87500 PECWormPos 8755, Restarted after WD Reset. UTC Date_Time 2025.02.26_18:06:03
17371.02344 PECWormPos 8755, Cold Started. UTC Date_Time 2025.02.27_02:25:14
25675.89844 PECWormPos 37, Cold Start enforced. UTC Date_Time 2025.02.28_04:39:21
67953.90625 PECWormPos 40, Cold Start enforced. UTC Date_Time 2025.02.28_16:22:04
85109.25000 PECWormPos 10592, Cold Started. UTC Date_Time 2025.02.28_21:07:12
3077.89062 PECWormPos 22084, Restarted after WD Reset. UTC Date_Time 2025.02.28_22:19:49
3241.95703 PECWormPos 12939, Restarted after WD Reset. UTC Date_Time 2025.02.28_22:22:33
?
I would suggest you try the following sequence of tests:
?
1. Replace the internal 3v battery with a new one
2. Reset Gemini to all default settings
3. After populating all the right settings, try to see if the problem re-occurs
4. If yes, you may want to try to re-flash Gemini firmware, then repeat at step 2.
5. If that doesn't work, I'll need some help from Rene or one of our repairers to see if there's a problem with Gemini memory.
?
Regards,
?
? -Paul
?
|
Hi Paul,
?
I will follow your suggestion. I have cloudy nights for the next week, I can try in the future.
Looking at those timestamp of events, they may be I was doing the reset. I used the web UI to cold restart the mount. what I noticed was that the mount kept rebooting if I stayed on the web page for cold reboot. I think the web browser kept refresh the web page when it cannot load the page. When it load web page after boot, it sends reboot commands again by refreshing the web page. 3 days ago, I was trying to figure out why my mount points to the wrong direction and I found out I set reverse RA.
?
Thank you,
Seokman
|
On Sat, Mar 1, 2025 at 11:09 AM, Seokman Han wrote:
3 days ago, I was trying to figure out why my mount points to the wrong direction and I found out I set reverse RA.
?
Did you also do a few reboots/resets on Feb 28? It looks like there were two WD Resets on that date, also.
?
|
I may have done those resets as well since they are in the afternoon right before I grab the log.?
|
I've been having this issue since I bought my G11T new last November. Tried just about everything and kept having the same issue. Went back to 6.02 a month ago and it's been working perfectly since.?
|
I've been dealing with this as well. It happens early in my automation during my startup sequence. I just watched the box "un-check" itself after the mount slewed to zenith, paused, and set tracking to sidereal rate.?
I think it might be related to the "Set Tracking Rate -? Sidereal" command in the NINA advanced sequencer.
I have had my parking mode set at "Explicit Wakeup" so I had "Set Tracking Rate - Sidereal" to make it track once it slewed to zenith for the initial autofocus run...
May go back to "Every Move" and get rid of the "Set Tracking Rate - Sidereal" command to see what happens. But I'll watch one more time to see if it is happening consistently at the Set Tracking command. It is consistently clicking off the PEC every imaging session, but it has been happening so consistently that I've just gotten used to clicking it back on 5-10 minutes later. Once I click it back on, it stays on the rest of the night.?
Due to the nature of the sequencer, the "Set Tracking Rate" is only commanded once at the very beginning.
Thoughts? I'm not super adept at interpreting the LOG file.
?
Thanks?
Ryan
?
?
I pasted aa copy of the Log file here... copied it a few minutes after it happened to avoid a huge log file: /g/Gemini-II/files/User_Logs_error_files_and_suggestions/Noonan/ASCOM.Gemini%20Telescope%20.NET.2108.270940.txt
|
So I woke up this morning and finished my coffee and started troubleshooting.
My System Startup process is:
?
Cool Camera (disabled for testing purposes)
Wait for time: Nautical Dusk (disabled for testing purposes)
Unpark Scope
Slew to Alt/Az (90/90)
Set Tracking Rate: Sidereal
Run Autofocus (disabled for testing purposes)
Start Guiding
?
?
I ran through my "System Startup" process over and over from the "Parked at CWD position" changing both the park modes and toggling the "Set Tracking Sidereal" each time:
Park mode: Every Move / Set Sidereal: ON - PEC turned off at sidereal command
Park mode: Every Move / Set Sidereal: OFF -? PEC remained on
Park mode: Go to Command / Set Sidereal: ON - PEC turned off at sidereal command
Park mode: Go to Command / Set Sidereal: OFF -? PEC remained on
Park mode: Explicit Wakeup / Set Sidereal: ON -? PEC turned off at sidereal command
Park mode: Explicit Wakeup / Set Sidereal: OFF -? PEC remained on
?
Every time that NINA commanded a "Set Tracking Rate: Sidereal", the PEC would deselect. It turns out it was an excessive command anyway, because the mount was already tracking at sidereal rate when it finished the slew to zenith.
This is a huge discovery for me. I've been manually turning PEC back on every time into my imaging sessions but I had no idea why it was turning off, or when. I've deleted the sidereal command and will let you guys know if anything else pops up, but I think it is solved.
No idea WHY the "Set Tracking Rate: Sidereal" is forcing the PEC to toggle OFF, but I can at least remove it from the process... it's like when you tell the doctor, "It hurts when I touch my toes" and he says, "Then stop touching your toes."
?
|
On Mon, Mar 10, 2025 at 10:07 AM, Ryan Noonan wrote:
No idea WHY the "Set Tracking Rate: Sidereal" is forcing the PEC to toggle OFF, but I can at least remove it from the process... it's like when you tell the doctor, "It hurts when I touch my toes" and he says, "Then stop touching your toes."
Hi Ryan, yes, the set Sidereal rate command appears to disable PEC. I'm guessing that this shouldn't happen, but let's see what Ren¨¦ says :)
?
Regards,
?
? ?-Paul
|