Plate Solver Error: Path is not of a Legal Form

Sequence Generator SGPro Support
1

Description

Hello! I had several failures last night with the latest version. The sequence would immediately fail upon calling the plate solver, PlateSolve2. It would respond with the message:

Auto center failed! Error solving with { sPlateSolverName }: The path is not of a legal form.

This issue only started since I updated to the most recent version 3.1.0.415; the solver was calibrated properly and has worked flawlessly for me since I started using SGP. It also worked earlier in the evening when slewing and centering to first target. It failed several times while attempting second target, but eventually worked after several tries. Third and final target failed and exhausted recovery attempts.

I tried searching for anything similar in the forums and came up empty. Is this a known issue? Thank you!

Link to Logs

Useful Info

OS: Microsoft Windows 10 Pro
Ver: 3.1.0.415
.NET: 4.8

2

The problem is not with the solver here, but rather that the camera is failing to produce an image for the centering routine to use:

Caught exception in USB Bulb capture: [kNkMAIDResult_BulbReleaseBusy] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 248965584)

I am not 100% sure what this means (it’s an error from the Nikon camera). What happens when you use “Frame and Focus”, “Take One” option for a length of time equal to the centering exposure?

3

Thank you very much for looking over the logs and replying. I took an exposure as you asked and everything worked fine. Here is the link to the log file:

4

Ok, sure. Please let us know if this is consistently problematic or if the issue seems contained within just the one session. Also, if you are imaging in cold weather and use a powered USB hub, please take measures to keep it warm(-ish). Other than that, just ensure that no connectivity problems were introduced during mount movement.

5

Hello again!

Unfortunately the issue persists. It seems very selective of when it fails; it ran through the entire auto-focusing routine with no issues, then immediately failed when the centering routine began. After cancelling the sequence, taking focus frames also works without issue. I use through-mount cabling on a CEM60 and triple-checked cable management through the mount’s range of motion, no issues there. Thank you again for looking into this!

Log file via OneDrive:

6

I am having the same issue with an ASI071.

Tried both the native driver and the ASI driver. Same fail. Don’t have a log file yet. Got to go bust down all the equipment and cover it up.

Merry Christmass.

ps; I will post a log later.

7

Last night was extremely frustrating. Everything was connected and working fine. The sequence was acting ‘normally’ and even slew and centered the first two targets. On the next target and every centering afterwards I got this error message.

I tried re-booting everything a couple of times. Even pulled and cleaned the USB and power connectors. Still the “not a legal form” error.

Yes I am using a powered hub. I have been using this hub and cable set up for over a year without issue until the upgrade to 3.1.0.413

Here is a link to two log files.

8

Update on my end; everything worked flawlessly last night through three targets and two meridian flips. Same settings as the past week. Out of 5 nights of imaging, I ran into this error on three of them.

9

Hrm, what were your conditions?

For me it was warm but very humid. Sky was clear and dark.

Meant to add this is the USB hub I am using.

10

Medium humidity, temperatures between -5 and 5.

11

I suppose with the holidays and such the good people of SGP are on a holiday, perfectly understandable

This morning I did a brief web search and came across this.

It basically means that the program is calling for a file with an ‘illegal’ path name.

I don’t know if that is of any help or not.

12

Just so there is no confusion… the issues reported in this thread are completely different. One has to deal with a failure of the camera to produce a plate solve image (@rhart426) and the other has to do with an actual bug that can be seen in certain circumstance (@UlteriorModem).

The issue reported by @UlteriorModem will be addressed in 3.1.0.426.