Hi,
I wanted to use a ASI120MC-S as GuidingCam with ekos and indiserver. The indiserver (+3rdparty) should run on a Banana Pi with Arch Linux and is build from the latest svn sources. Guiding and everything else runs quite well for the first few minutes, but then the Asi cam hangs on Exposure done, Downloading Image. I monitored the virtual memory used by indi_asi_ccd and running a few times it always hang a little bit over 3GB virt memory used, which I think is the maximum the 32bit Arm architecture can address.
At the moment the Asi cam runs directly on my Sony Vaio (64bit Ubuntu 15.04, Ekos and server installed from PPA) and with now 3,5k continuous Frames in the focus tab the indi_asi_ccd uses 29GB virtual memory adding 8MB for each new picture.
As I'm new to indi I'm not quite sure where I have to look in the source code to free the used memory and make continuous exposures and guiding possible.
cs
Markus
I wanted to use a ASI120MC-S as GuidingCam with ekos and indiserver. The indiserver (+3rdparty) should run on a Banana Pi with Arch Linux and is build from the latest svn sources. Guiding and everything else runs quite well for the first few minutes, but then the Asi cam hangs on Exposure done, Downloading Image. I monitored the virtual memory used by indi_asi_ccd and running a few times it always hang a little bit over 3GB virt memory used, which I think is the maximum the 32bit Arm architecture can address.
At the moment the Asi cam runs directly on my Sony Vaio (64bit Ubuntu 15.04, Ekos and server installed from PPA) and with now 3,5k continuous Frames in the focus tab the indi_asi_ccd uses 29GB virtual memory adding 8MB for each new picture.
As I'm new to indi I'm not quite sure where I have to look in the source code to free the used memory and make continuous exposures and guiding possible.
cs
Markus