When I start the streaming in PHD2, I can start an exposure from Ekos, the Indi Control Panel from kstars as well as from PHD2.
The result of this is an error mesage about error 14 in ASIStartExposure. It also stops the streaming of the video.

What I am actually trying to figure out is why this error occurs while I am not intentionally starting an exposure when both ekos and
PHD2 are running. I have modiified my local copy of the ASI driver such that ASIStartExposure/ASIStopExposure are not called
while the camera is in streaming mode. Hopefully, this prevents the problem from occuring spontaneously during guiding. Still have
to test that.

Read More...

Hi Jasem,

While trying to solve some problems related to guiding with PHD2 using a video stream from my ASI120mini,
I noticed that it is possible to start an exposure while the camera is in streaming mode and vice versa.
This is easily fixed in the ASI driver. However, it could be that this problem occurs with any similar camera.
Is there a way to prevent this problem in a more generic way? It would for exampe be nice of the exposure
control is disabled during streaming and the streaming controls while an exposure is being taken.

Regards,
Camiel

Read More...

Indeed very similar what the cameras are concerned.
I don't have other pairs of similar devices, so can't check for the focussers.

Read More...

It appears that this problem is not related to the cameras. The same problem occurs when using a ZWO ASI and DMK camera.
I did a test with only two cameras connected. First, I disconnected the DMK camera (V4L2 driver). The screenshots show what the
ASI camera tab in the INDI control panel looks like before and after disconnecting the DMK camera. After disconnecting the ASI
camera too and reconnecting both, I did a similar test by disconnecting the ASI camera first. I have included the screenshots of
the V4L2 camera tab in the INDI control before and after disconnecting the ASI camera too. I have also included the debug log
file from EKOS. The odd things is that with the CCD and Guide simulators this problem does not occur.

Read More...

Recently I have noticed that when I disconnect my guide camera (ZWO ASI120 mini)
images are not downloaded any more from my imaging camera (Atik 11000). Exposures
with it are still possible but the images is never shown in the FITS viewer. Many of
the options and settings are removed from the Indi Control panel of the Arik camera
as well. Any idea on why this happens? I am using kstars 3.5.1 beta pulled and build
from the repository Friday, Dec 4.

Read More...

Hi Gregory,

I'll test the new version and let you know the result.

Regards,
Camiel

Read More...

Hi Gregory,

The new version works for me.
If noticed that a bug that I fixed earlier, didn't make it in the version that was put into the repository.
From line 226 the code should read:

                {
                    // Skip response strings consisting of a single termination character
                    if (nbytes_read_total == 0 && response[0] == Termination)
                        response[0] = LX200Pulsar2::Null;
                    else {
                        nbytes_read_total += nbytes_read;
                        done = true;
                    }
                }
            }

I have also been thinking about a way to ensure that the mutex is always locked and unlocked
properly. In the attached source file (a modified version of your code from this weekend), I have
introduced the Transaction class for this purpose.

Read More...

Hi Gregory,

The code works except for one small issue that I noticed while scanning the log files in more detail:
the old Pulsar apparently doesn't support the setting of the user rate. The driver tries to read
the response (which never comes) after which a resynchronisation is done. This doesn't
prevent the driver from working in other respects.

I have attached a version of the driver code in which the mutex is controlled by std::unique_lock.
This is safer since it will always release the mutex automatically when the scope is closed:
on a normal exit, an early exit, and even when a C++ exception is thrown.

I also renamed functions that I think should become private with
a leading and trailing underscore. The resynchronize function needs some more work.
And the mutex should remain lock when the reading is completed fully instead of unlocking/relocking
it between the call to sendReceive() and subsequent reading of the planetary data.

Regards,
Camiel

Read More...

Hi Gregory,

I'll try the new code.

It would be useful if the solution for the sign problem in the driver could be moved to the getSexComponents() function.
This requires changes in many drivers but a this would be required anyways to fix this problem.

I think the driver is good enough to be released .

Next to adding a few more commands, a bit of code cleanup would be good as well. E.g., it would be better to get all
code involving the mutex localized by introducing a function sendOnly(). The low level send and receive functions could
then be hidden in a private scope. At the time, the serial port code of the standard LX200 driver didn't work well. It may be
worth to check whether this is still the case. If not, we could use the generic routines which saves some lines of code.

Regards,
Camiel

Read More...