I think I have the same cam model (cooled imx571 Color) - what works for me is to leave the usb setting at 2 and timeout >6. The cam is connected to usb3 of pi4 with cooling and fan active. Other than that pi is used only to run drivers and occasionally phd - all pictures are loaded up to my client computer via 1gb cable Ethernet.I had occasionally timeouts but the above removed them and now it happens very seldom, and never for calibration frames. Also, the driver description says it is sensitive to power fluctuations, so make sure the power supply works fine with enough power if you use the usb hub on the cam.

Thanks. I am running KStars on a mini-pc, as I found the pi just not up to the task of the large files produced by the IMX571 camera. I will leave usb=2 and timeout=10 for now. Tonight, hopefully, I will run a schedule without any short calibration captures (the imaging train has not been altered since I last took flats). Hopefully it will just run all night without timing out.

I run on mains power, so I have the luxury of having a separate 12v power supply for just the camera. The mount and everything else runs off of the 12v brick that came with the CEM40. That includes the powered usb3 hub through which the camera is connected to the pc, but I don't think the camera draws much, if any, power through its usb port. If I have trouble tonight I will try swapping in a different 12v supply for the camera.

well, this looks legit and should work. The only tuning I've done to the cam hardware was replacing the fan with Noctua's but this should not change much. Good luck and let us know how did it go - the sky clears here too so I'll try to do few shots myself.

Mariusz

Thanks. I went ahead and swapped out the power brick for a different one. Made it through one full night. So, cautiously optimistic.

interesting, hopefully it works for you - what's the difference between the power sources?

Both power bricks are 12v 3A. I have so many of them - I should get into the habit of labeling their original sources. I can't recall if the RisingCam ships with a brick? If so, then that is the "old" one. The "new" one, I cannot recall when or why I acquired it.

Ugh.

The driver / download timeout issue is back. There are two configuration changes. One is that the rig is indoors, with the telescope on the ground rather than in the saddle (I just needed to take some flats) - so the usb cable routing is different. The other is that I just updated KStars to the latest stable build. It downloaded and installed several camera drivers during the process, including Toupcam.

Whichever is the culprit, the driver times out quite frequently and would be useless for an imaging session.

This is a known issue with this driver, especially if you have two Touptek cameras connected at the same time. I don't know what is causing it, I've introduced lots of workarounds for the SDK timeouts, but it appears this is not sufficient.

Thanks for the information, Jasem. I have only the one Touptek camera, by the way. Are any of the known workarounds on the user side?

I switched everything off and re-seated some connectors and was able to get through some test captures OK after that, but it's worrisome to maybe have to rely on luck after driving an hour to a dark site. Hopefully a real solution can be found someday.

Hi Ron,

Just for the sake of narrowing down the possible problem sources - are you able to test the cam with the native touptek windows software/drivers (or N.I.N.A.)?

It's likely to come to that. When I bought the Beelink I cloned the Windows11 installation to another SSD before I installed Ubuntu (not sure I did it completely - I think I still need to make it bootable). I am seriously considering swapping that SSD in and setting up to give NINA a try.

I suppose it would be wise to try just from my Windows laptop the next time I have the camera inside, before I go to all the trouble of setting up the Beelink for Windows imaging. I'd miss you guys A reliable IND driver would be the best solution.

Well, as said, it's to identify the cause - if you have the same problem with windows drivers, then NINA won't help neither. But it's always good to explore - Good luck!