×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

INDI Driver for SVBONY cameras

  • Posts: 105
  • Thank you received: 11
Hi Collin, these are great news, I am loking forward for the update.
Hades
2 months 3 days ago #77537

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 19
Hello Hades,

Another bug : the LiveView recording (.ser file) was broken for the SV305M Pro.
Fixed in my repository. Pull Request on it's way.

I also removed some wrong FITS entries (color controls on a mono camera...)

Best regards !

Thx8411
2 months 1 day ago #77608

Please Log in or Create an account to join the conversation.

  • Posts: 26
  • Thank you received: 13
I might have figured out what is causing the doubled exposure time.  I made a new script that is a "minimum viable product" to take exposures, but performs all of the configuration in the way it is normally done in my program.  Doing this I could quickly change various settings to see how the program would react.  I found that I could not consistently get the doubled exposure until I was taking 9 second exposures.  8 seconds and below, it might happen rarely, but at 9 seconds it happened fairly often.

This is my MVP test script:
github.com/aaronwmorris/indi-allsky/blob...ting/exposureTest.py

My indi code (which is based on Marco Gulino's indi-light-tools) has a synchronous mode for taking exposures.  Basically, it sets the exposure value and then queries the status of the exposure control until it is idle.  The code I was using would query the status of the control every 0.05 seconds, or 20 times a second.  Backing off to 0.15 seconds between status calls seems to do better.  It appears the cause of the doubled exposure is aggressively querying of the status of the exposure control.  I am not sure if it is the total number of status calls or just the calls-per-second causing the behavior.

It does appear to be specific to the sv305.  I have tested several other cameras (ASI, QHY) and they do not exhibit the same behavior.

This is the code where my script queries the status:
github.com/aaronwmorris/indi-allsky/blob...exposureTest.py#L352
The following user(s) said Thank You: Jasem Mutlaq
2 months 1 day ago #77636

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 19
Hello Hades,

The SV305M PRO should be fully supported now.
The SV305M PRO being a mono camera, it's much more sensitive.
I added ROI support in live view for fast fps planetary imaging.
Binning also works in live view now.

Version 1.2.9 is in my repo.
Submitted a PR.

Best regards !

Thx8411
The following user(s) said Thank You: Joakim
1 month 3 weeks ago #77813

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 19
Hello Aaron,

Thanks for your diagnostic.
Could you please enable the debug log level on the indi server side, and send me the resulting logs in "real use".
We could have some useless internal calls in the driver, introducing time delays.

Best regards,

Thx8411
1 month 3 weeks ago #77814

Please Log in or Create an account to join the conversation.

  • Posts: 105
  • Thank you received: 11
Hi Collin, thank you for all your effort, I appreciate it. How can I now compile it?
Hades
1 month 3 weeks ago #77823

Please Log in or Create an account to join the conversation.

  • Posts: 26
  • Thank you received: 13
I was wrong regarding my finding about querying the exposure control.  I switched my code to run exposures asynchronously and I am still receiving exposures in twice the expected time.

I will work on generating the debug logs from the indiserver.
1 month 3 weeks ago #77853

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 19
Hello Hades,

<<  How can I now compile it? >>

Clone my repo again (github.com/thx8411/indi-3rdparty.git), or just update your local copy if you still have it.

your "libsv305" should already be up to date.

You just have to build and install the "indi-sv305" package :

in a dedicated folder :

>cmake <path to you local git clone>/indi-sv305/
>make
>sudo make install

If you want to test it before the installation, just launch :

>indiserver ./indi_sv305_ccd

like your already did before.

Best regards !

Thx8411
The following user(s) said Thank You: Albert Tamayo
1 month 3 weeks ago #77878

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 19
Hi !

First light for my SV305M Pro this evening.
Jupiter imaging with Ekos.

A wanted to try "full spectrum" imaging. Bad idea, my pictures are messy on my Mak (no IR/UV filter on the camera).
Rofl ! No way to get a sharp focus...

But I'm pretty happy :

- 88 GB of data, no crash, no issues
- up to 240 fps at 960x540 8 bits
- at half gain, 1ms exposures !

Best regards !

Thx8411
 
The following user(s) said Thank You: Albert Tamayo
1 month 3 weeks ago #77908

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 19
Hi folks!

My blurry Jupiter...

 

SV305M Pro, full spectrum on a Mak 127/1900, no barlow.

Full spectrum imaging on a not fully reflective telescope, low in the sky isn't a good idea, lol !

Best regards,

Thx8411
Last edit: 1 month 2 weeks ago by Collin.
1 month 2 weeks ago #78120
Attachments:

Please Log in or Create an account to join the conversation.

Thanks! I just received my SV305 Pro a couple of days ago. I can capture normal images just fine (still to need to adjust some settings) but the video feed is always black, what's going on there?
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 month 2 weeks ago #78156

Please Log in or Create an account to join the conversation.

  • Posts: 105
  • Thank you received: 11
Hi Collin, I am getting this error:
lukas@astrotracker:~/SVBony$ cmake ../indi-3rdparty/indi-sv305/
-- CFITSIO not found.
CMake Error at /home/lukas/indi-3rdparty/cmake_modules/FindINDI.cmake:285 (message):
  Could not find INDI include directory
Call Stack (most recent call first):
  CMakeLists.txt:14 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/lukas/SVBony/CMakeFiles/CMakeOutput.log".

 

File Attachment:

File Name: CMakeOutput.log
File Size:43 KB
1 month 2 weeks ago #78169
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 1.306 seconds