256MB should be enough. However, for testing, it's worth increasing if you hear that they've been doing something with buffers.

Please confirm that everything is fine for the newest INDI / INDI-3rdParty builds with the old library.

LD_PRELOAD=/path_to_library/libASICamera2.so.1.16 indiserver indi_asi_ccd


Read More...

Yes, I mean 1.17.
I am not getting detailed information from ZWO, I am trying to establish cooperation with them. I am working on the libASICamera2Boost library. Unfortunately, each camera has a different implementation and it's hard for me to keep developing without the original library source.

In original library (1.17), there are probably larger double buffers used for communication with the camera.
The usbfs_memory_mb value should be at least '6 x Resolution'. For now, these are guesses, I need to analyze the library more.
Anyway, to rule out a memory problem, I suggest temporarily increasing the usbfs_memory_mb value and testing indi with different ZWO libraries.
For example:

sudo sh -c 'echo 512 > /sys/module/usbcore/parameters/usbfs_memory_mb'
# test for biggest camera
# sudo sh -c 'echo 1024 > /sys/module/usbcore/parameters/usbfs_memory_mb'

# Test different versions of the ZWO library.
LD_PRELOAD=/path_to_library/libASICamera2.so.1.16 indiserver indi_asi_ccd
LD_PRELOAD=/path_to_library/libASICamera2.so.1.17 indiserver indi_asi_ccd


Read More...

In the latest SDK, the problem with damaged frames during long exposure is fixed.
Probably it required more library modification and maybe something got corrupted.
I still offer cooperation for ZWO, unfortunately without success.

Read More...

This can actually be a problem for a specific camera.
Each camera has its own implementation of receiving data.

For example, Jasem keeps mentioning to me that he has no problems running 2 cameras at once.
Of course it is, the ASI178MM and ASI120MM-Mini cameras have a similar communication implementation, in a cooperative global variable. So you can't run them all at once.
The ASI178MC and ASI120MC cameras can already be run together, they have completely different communication implementations.

Read More...

Please rebuild the indi and pyindi-client from git.

Read More...

Paweł Soja replied to the topic 'Problem importing PyIndi' in the forum. 7 months ago

I added a build test for PyIndi.
If @geehalel accepts the changes, I will also add unit tests.
github.com/geehalel/pyindi-client/pull/11

Read More...

Paweł Soja replied to the topic 'Problem importing PyIndi' in the forum. 7 months ago

Thanks, I think I can support pyindi, monitor the status, and suggest an easier way to write in python (using INDI Library).
All upgrades are backwards compatible for C++, but I can see there are problems with swig - to be taken care of.

Read More...

Paweł Soja replied to the topic 'Problem importing PyIndi' in the forum. 7 months ago

Cases where people will write exotic macros here and there that will probably continue break swig (without even considering the static binary dependency for the client)


The macro is not exotic and it was never a problem. The error was in using a macro without a proper include in pyindi-client.
Most of the problems with PyIndi are related to the work on the INDI Library to keep the interface in the future without rebuilding dependencies.
Also, high-level functions that facilitate the development process are implemented.

I am currently creating automatic builds for Linux / MacOS. If you like, I can add additional tests for pyindi-client.

Read More...

Hi!

I'm coming back after a break.
I thought that we would be able to solve the problems in the original library with ZWO, unfortunately in short I got the answer "most of the users is not so critical about the speed on PI".

So I will continue to develop the boost library. I will take a look at the problems that were mentioned on the forum.

There is low speed writing to the card on the Raspberry PI and it will be difficult to get around this problem. The solution is to introduce:
- compression before saving to the memory card
- saving a short recording - using the version with a large amount of RAM
- sending directly over the network and saving to another computer

I also got "Asus Tinker Edge R" for testing, where most problems can be solved.
asus-tinker-edge-r-rk3399pro-arm-biglittle-a72a53-wifibluetooth-4gb-ram-16gb-emmc.jpg

After all, there is still a problem with long exposure, if my library solves the problem, I'll be glad my work isn't wasted.

Read More...

Hi Paul,

when you write about tests, you mean the original, unmodified ASI library? right?
If I finish some minor fixes on high-frame speed recording, I'll move on to fixing long exposure.
Apart from the hiccups when starting high-speed recording, it seems to me that the situation in my library is under control.

I am also planning to buy a bigger camera from ASI and I think I will get the situation under control as well.
What kind of camera would you buy? Maybe I'll buy the same one.

I put the 8/16-bit version on branch master, which works fine for me. I added the ability to set the size of buffers using the function and using the configuration file. Everything well described in the README and header file.
My next step is to fix timeouts and run capturing smoothly.

Maybe tonight, Polish time, I will manage to find some time and get it over with ;)
After completing the library and Indi, I'll take a look at other programs. FireCapture added to the list.

Read More...