Ben replied to the topic '2 x Meade DSI-Unable to find DSI. Has the firmware been loaded?' in the forum. 2 years ago

Nice work!

I take it that you are running with two instances of the dsi_ccd driver then? That sounds like a pretty good solution to me, though it seems that some other CCD drivers support multiple devices per driver. I don't know if there's something to be gained by that approach, though? Jasem?

I suspect that you could get a non-zero serial number reported by the devices by uncommenting DsiDevice.cpp:298. The comments regarding the actual serial numbers are not encouraging, but you might have a reasonable chance at getting something unique.

I'm glad to hear that your DSI III is working with the INDI driver...I think you're the first one to confirm this.

I'll work on improving the driver to include the DSI model name and serial number properties in the INDI control panel.

Thanks,
Ben

Read More...

Ben replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 years ago

Are you sure you're using the right serial port? You can use gnu screen or even cat to send simple commands and see onstep respond to them since it's all just ascii.
-Ben

Read More...

Ben replied to the topic 'indi_dsi_ccd not working after a while' in the forum. 2 years ago

I am able to reproduce the high memory usage of indi_dsi_ccd using the script that was provided. Interestingly, I don't see anything obviously wrong using valgrind. I think I was able to reproduce the same high memory usage when I was using ekos, but the memory usage was attributed to kstars rather than indi_dsi_ccd. I'm going to look at other driver code to see if they do something the indi_dsi_ccd driver does not.

I still haven't been able to reproduce the failed exposure.

Read More...

Ben replied to the topic 'indi_dsi_ccd not working after a while' in the forum. 2 years ago

I'm unable to reproduce either of these problems on my raspberry pi. Could you share your script?
-Ben

Read More...

Ben replied to the topic 'indi_dsi_ccd not working after a while' in the forum. 2 years ago

I was actually seeing kstarts ballooning up, not indi_dsi_ccd. The memory leak bug that I thought was there is actually in the code, but it seems g++ handles it just fine. So, I'm unable to reproduce the high memory usage of indi_dsi_ccd on my intel machine. I've also been unable to reproduce the problem of not being able to download an image.

I'll fire up my raspberry pi and see if i can reproduce it there.

It might be helpful if you could share the logs from the shell running indi_dsi_ccd (indiserver).

Thanks,
Ben

Read More...

Ben replied to the topic 'indi_dsi_ccd not working after a while' in the forum. 2 years ago

I think I see the memory leak in the code (and I definitely see it when running). I'm going to try and get valgrind running to make sure I get them all.

I'm attempting to reproduce the main issue that you posted about. I'll let it run overnight and see what happens.

Thanks,
Ben

Read More...

Ben replied to the topic 'indi_dsi_ccd not working after a while' in the forum. 2 years ago

Hi Soren,
I'm assuming this is repeatable, is that right? If so, could you provide instructions to reproduce it?

Thanks,
Ben

Read More...

Ben replied to the topic 'meade DSI 3' in the forum. 3 years ago

Hi,
Were you able to test the DSI III? I see an issue with the reporting (you would probably see a message saying "Found a DSI with an unknown CCD: 285AQ") but that shouldn't affect the functionality. Hopefully it's working for you!

Thanks,
Ben

Read More...

Ben replied to the topic 'meade DSI 3' in the forum. 3 years ago

The changes have been merged into the indilib:master. Do you use Jasem's PPA? If so, the initial support for DSI III color should be there tomorrow. Please let me know if you try it (whether it works or not).

Thanks,
Ben

Read More...