gnthibault
gnthibault
@hiro3110i I updated Indi to v2.0.3 I updated indi-3rd-party libs to v2.0.3 I updated indi-3rd-party indi_playerone_ccd to v2.0.3 And now, I do not even see the device appearing in device...
Okey, so I think I found the main rootcause of the issue (not 100% sure though). The Playerone Ares-M Pro camera seems to rely on a very specific initializion/deinitialization order:...
Ok another aspect that I didn't managed to mention earlier, is that, in order to get a successful "reset", I need to restart completely the indiserver, just restarting the driver...
I have contacted playerone support to get some feedback hopefully.
Ok, so I didn't get any relevant feedback from PlayerOne, but I had the opportunity to test-out the camera under windows with their driver + Ascom driver. Interestingly Sharpcap didn't...
I have implemented a setup where I consistently restart the indiserver as well as implement a proper power-on/power-off strategy. I seeems this way the camera is working as expected, I...
I got some feedback from playerone saying that their hardware engineers are looking into the problem, I will report any other news I receive here.
Interestingly, I cam across this interesting post from Pegasus support: https://pegasusastro.com/forum/viewtopic.php?p=387#p387 That was for ZWO camera though, but the symptoms seems much similar to the one I am experiencing
Thanks, this weekend I cannot, but I'll do next week
I have more tests to do, but it seemed like in my context this might not be an issue as problematic as I initially thought. I am working on a...