Major Crash & Burn 4.1.827 64 bit

[kaymann]

Three Things
1) Auto Focus worked

2) Plate Solve Failure
I selected M17 (Swan) from your catalog and everything worked perfectly except plate solve. Something was too thin error!?!
I ensured the focus was good and tried 4 more times - failed'
Several restarts including Windows restart - still failure
However, Live stack showed it was indeed centered.
I selected M16 (Eagle) and everything worked perfectly including plate solve center sync
I try again on M17 and only plate solve fails
So wanting to LiveStack M17 I proceed...

3) and get I get a disk error - this usually means disk full. I Shut down restart etc. I check and find nearly 300 gb free and I manually transfer around 20 gb through windows with no issues. However SC pushes up same error. For the night I got 2 FITS before Disk Error than no more. I tried shortening the file name as the catalog one was pretty long. Still no success, emptied trash no success etc...

Several Beta Error report dialogs popped up and I elected to send them, I hope you got them. I was so sure of 4.1 I uninstalled 4.0 so I cannot tell you if it was specific to our beta.

Logs attached

[admin]

Hi Randall,

thanks for sending the error reports - I think I saw one of them yesterday and found and fixed the problem.

What is happening is that the name of the target that you have chosen is so long that it overflows the FITS file header field for the target name. This isn't something that I've encountered before, so there was no special handling for the error which then falls back on the general 'saving a file failed - maybe it's disk space' message.

I already have a fix - future versions will trim the name (or other header fields) if they are too long.

Looking at the logs, it seems that the target name problem was also causing the plate solving error - for Astap, it tries to save the file to solve as FITS and by default it tries to write all the relevant info into the headers

Good that the focus worked though!

cheers,

Robin

[kaymann]

I tried to shorten the name that came out of your catalog goto but that did not fix it for me but I am glad you got the fix. Will the fix appear in Monday's beta?

[admin]

Hi,

yes, hoping to get the new update out in a few hours - depends if anything new comes up that needs fixing either in today's forum posts or in the weekend's bug reports.

cheers,

Robin

[kaymann]

So last night I confirmed the long name situation is definitely cured with your 4.1.856. However I got a couple of non-catastrophic errors with the automatic pop-up which I sent to you.

[admin]

Hi,

I've just checked the bug reports and only found one from build 10856, which was related to a problem with the ASCOM driver for a PLL focuser. Not sure if that was you. If it was, it looks like a bug in the setup window code for the ASCOM driver itself

cheers,

Robin

[kaymann]

My ASCOM 6.6 refuses to talk to my CGEM DX I have tried so many things to get it back with no success... PORT 3 does not have attached Celestron Mounts. My focuser mostly works most of the time. So I think it was me any ideas on the ASCOM problem (I do not expect you to answer all of my astronomy woes - though you mostly do).

[kaymann]

My ASCOM 6.6 refuses to talk to my CGEM DX I have tried so many things to get it back with no success... PORT 3 does not have attached Celestron Mounts. My focuser mostly works most of the time. So I think it was me any ideas on the ASCOM problem (I do not expect you to answer all of my astronomy woes - though you mostly do).

Well now I can put my ASCOM mount woes to bed - I found a spider nest deep in the USB Male port. Every time I reseated the USB cord I was compacting the nest up against the contacts until finally no contact and who knows how many USB issues that was causing down the USB pipe - replaced the USB cord and zero errors. So you can ignore that error report and my call to help...

[admin]

That made me laugh... A different kind of 'debugging' needed there

cheers,

Robin

[kaymann]

That made me laugh... A different kind of 'debugging' needed there

cheers,

Robin

Whoa I did not think of that pun and now I am LOL myself