“Temperature Plan Is Empty” Error with Voyager and Moravian C5A-100M - Forums

Hello all,

I recently installed a Moravian C5A-100M on my CDK24. Imaging has been ok a few nights except last night. It imaged ok for the first half of the night, but starting about 1:30am or so Voyager Advanced (running RoboTarget) just kept dumping this error in a loop for 4.5 hours and took no images at all:

I have never seen this error previously on my ZWO or QHY cameras. Things were a little humid (80%) and a little cold last night (33-37F) at SRO and I am not sure if the Moravian camera had an issue.

Has anyone here encountered this error previously, and if so, what camera was it on, and what was the fix?

Many thanks,
Ani

I have not seen this occur on any of the Voyager and Moravian systems we run. The first thing to check would be that the drivers are on the latest version and the firmware is up to date. Second I would make sure the camera is connected via USB2 instead of USB3 (or that the USB3 run is extremely short) and that the camera is getting the proper voltage.

Thanks so much for your prompt response Bill.

I am using the native power supply and extension cable that Moravian sent. I do use USB3, but it is a very short cable (~1m) from the C5A to an Eagle 5XTM.

As for the driver and firmware versions, I installed the latest drivers from their site, and the camera is a few weeks old so I assume Moravian has installed the latest firmware on it already. Here is what SIPS shows:

I assume that is similar to what your systems are running?

Thanks,
Ani

I would update the firmware:

https://www.gxccd.com/cat?id=203&lang=409

You’ll need the firmware utility:

https://www.gxccd.com/cat?id=150&lang=409

After part 2 of the install you may get a failure error which is misleading. After the firmware completes just connect the utility again and confirm the new firmware version shows properly.

The camera will reboot during the process. You’ll want to make sure no software other than the firmware utility is connected.

Thanks again Bill.

The camera firmware was originally 50v9.14 and the latest is 50v9.15. I ran the firmware update utility and everything work correctly including phase 2 and verification. However the firmware version shows as 50v9.0 after the update. I tried both manually pointing to the correct file as well as trying the automatic method, to no avail.

What do your cameras show as the firmware revision?

Thanks,
Ani

Nevermind, it needed a connection to an imaging software with an image taken for the firmware version to show up correctly. No clue why. But it is showing the latest firmware now.

I will see if this makes any difference. Thanks again for your thoughts.

Ani

As I think more about this, the strangest part is that Voyager isn’t executing any other instructions besides saying “temperature plan empty”.

It’s almost as if it took a nap in the middle of robotarget loop and ended the night with zero errors. If there was a camera error, it should have reported it (and restarted the camera since I had that option checked).

It should have been running auto focus, filter change, imaging, and other robotarget instructions but the log shows there was nothing going on (or it was hanging on the temperature plan management instructions).

Ani

It seems like between Voyager's support and Moravian's support they'd probably be the best equipped to help.

Thanks Kyle, yes, I have had them all on a single thread since before this post, and no meaningful answers so far besides “turn it off and on again”.

Ani

Ani Shastry:
Thanks Kyle, yes, I have had them all on a single thread since before this post, and no meaningful answers so far besides “turn it off and on again”.

Ani

Has it reproduced?

Haven’t had clear skies yet to test again. Thursday or Friday this week seems to hold promise.

Ani

Ani Shastry:
Thanks Kyle, yes, I have had them all on a single thread since before this post, and no meaningful answers so far besides “turn it off and on again”.

Ani

That’s very disappointing given it’s a quite expensive, “premium” camera and a commercial software suite with an excellent support expectation as a primary feature.

Kyle Goodwin:
Ani Shastry:
Thanks Kyle, yes, I have had them all on a single thread since before this post, and no meaningful answers so far besides “turn it off and on again”.

Ani

That’s very disappointing given it’s a quite expensive, “premium” camera and a commercial software suite with an excellent support expectation as a primary feature.

In general I’ve found Moravian support to be pretty good. They’re no FLI though, and it’ll be great once their cameras are back in the hands of imagers.

Dark Matters Astrophotography:
Kyle Goodwin:
Ani Shastry:
Thanks Kyle, yes, I have had them all on a single thread since before this post, and no meaningful answers so far besides “turn it off and on again”.

Ani

That’s very disappointing given it’s a quite expensive, “premium” camera and a commercial software suite with an excellent support expectation as a primary feature.

In general I’ve found Moravian support to be pretty good. They’re no FLI though, and it’ll be great once their cameras are back in the hands of imagers.

Did they ever get back to you on that shutter question?

Kyle Goodwin:
Dark Matters Astrophotography:
Kyle Goodwin:
Ani Shastry:
Thanks Kyle, yes, I have had them all on a single thread since before this post, and no meaningful answers so far besides “turn it off and on again”.

Ani

That’s very disappointing given it’s a quite expensive, “premium” camera and a commercial software suite with an excellent support expectation as a primary feature.

In general I’ve found Moravian support to be pretty good. They’re no FLI though, and it’ll be great once their cameras are back in the hands of imagers.

Did they ever get back to you on that shutter question?

Yes there will be an optional shutter. How much that option is, is unknown at this point. Waiting on those details still.

Just curious, other than the message itself (temp. plan empty), does the camera work as usual? If yes, can you just continue to image and ignore the message?