Mossyback avatar
Using N.I.N.A. Advanced Sequencer with SX694 Mono camera last night and I had an odd thing happen. After N.I.N.A opened the ROR, unparked the scope and homed it things went weird. The next step was slew and centre and I got the following message “unexpected error occurred. Start exposure called while in state of camera error.” This must have been during plate-solving.

Prior to starting the sequence, I had slewed to the target and plate-solved and took some pictures to check exposures with no problems.

I have checked to make sure that I have ASTAP set properly. I’ve never had this happen before. I’d appreciate any suggestions as to what I’ve done wrong so that I can get back to imaging.

Hank
Christian Großmann avatar
Hi,

this sounds a bit like there was an error during the communication with the camera in some way. I doubt it has to do with the fact that you did some plate solving before. Personally I use the nightly builds and such things may happen using them. After restarting NINA the problems were always solved in my case, but I never experienced the error message you had. If everything worked before, I assume it was bad luck and will work next time. But maybe you can try to reduce the speed of the USB transfer in the camera settings. Depending on the equipment you use and the time, this equipment talks to the PC, there may be some errors. Especially if everything is connected to the same hub. The errors usually dissappear when slowing down the traffic on the bus.

In my case, errors with NINA are very rare even with the nightly builds. But it may depend on serveral things like camera type, PC type, etc. I hope your problem just dissappears.

CS

Christian
Helpful Supportive
TiffsAndAstro avatar
Using N.I.N.A. Advanced Sequencer with SX694 Mono camera last night and I had an odd thing happen. After N.I.N.A opened the ROR, unparked the scope and homed it things went weird. The next step was slew and centre and I got the following message “unexpected error occurred. Start exposure called while in state of camera error.” This must have been during plate-solving.

Prior to starting the sequence, I had slewed to the target and plate-solved and took some pictures to check exposures with no problems.

I have checked to make sure that I have ASTAP set properly. I’ve never had this happen before. I’d appreciate any suggestions as to what I’ve done wrong so that I can get back to imaging.

Hank


TRy a new usb cable.
Everything is solved by a new usb cable. Maybe ;)
Mossyback avatar
Hi Christian,

I just went out to the observatory to check and I have routed the camera through the mount prior to the problem, rather than direct to the computer. I’ve changed it back and we’ll see if that solves the problem. Thanks for the suggestion. If that doesn’t work then I’ll try a new cable as TiffsandAstro has mentioned.

Hank
Well Written Respectful
Tony Jerig avatar
Yes, guessing this was a loose or strained cable connection or the computer didn't like some component software driver sequence loading after the plate solve.  Reseating cables and restarting the computer are my go to for these type errors that I have seen on rare occasions.
Logan Carpenter avatar
I second the idea of trying a second USB cable, I had out of the blue loss of communication with my ASI2600mmPro which started off intermittent over a few weeks and then became permanent. Replaced the USB3 cable and (to be sure) the power cable to the camera and all seems ok again.
Helpful Concise
Mossyback avatar
I was able to do a short Sequence run last night and all went well. I use a SB MtY mount and a mini PC mounted on the scope. Last night I ran the camera USB cable direct to the mini PC rather than through the mount and the problem seems to have disappeared. The cable from the ROR motor runs through the mount with no problems.
Helpful
Related discussions
Help Need for Message
I’m using N.I.N.A. with a SB MtY mount. My target was NGC 6888 and I sent it to the Framing window and it looked fine. However, when I clicked “slew” nothing happened and I got the following message. “ASCOM Driver Error - Object Reference Not Set To ...
N.I.N.A. slew and sequencing issues with similar camera/mount setup.
Oct 13, 2025
Focuser trouble when NINA starts
Hello, I’m new to NINA (was using ASIAIR before), I was able to connect and set everything and to perform two nights of imaging. Here is my issue, the last two times I turned all my equipment on, my focus was lost (I mean stars wereway out of focus, ...
N.I.N.A. startup and camera connection problems relevant to error state.
Sep 3, 2025
Slew rate does not make sense
Hi, I have a problem where NINA (or possibly SynScan Pro or the mount) is slewing way faster in the RA axis than it thinks it is. This leads to the mount overshooting substantially and I have no idea how to fix this. The following is what I can see:P...
N.I.N.A. slew issues that may relate to sequencing problems.
Oct 13, 2025