×

INDI Library v1.9.2 Released (14 Sep 2021)

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

Fuji X-T3 observations - what I've learned so far

  • Posts: 5
  • Thank you received: 0
Thanks once again Dave. I'm off to try this again now.
6 months 1 week ago #68191

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

  • Posts: 44
  • Thank you received: 2
Quick Update:  My trial using the FITS format as the "saved" one failed.  I was only getting greyscale images.  My processing software handles the RAF format just fine so I'm back to  just saving the "native" RAF format (to camera and to Pi).  Tried "compressed" RAF (in the camera, not in Kstars/Ekos/Indo setup) last night.  Seems to work and half the size. (Siril won't read the compressed file - or at least didn't last time I tried it, but PixInsight does).
Ran afoul of crashes last night - 3 hours outside and only 31m 2 minute exposures.  Hopefully tonight will be better (two clear nights in a row w/o moon, hasn't happened since last fall)
5 months 1 week ago #69740

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

  • Posts: 5
  • Thank you received: 0
Hello all, new X-T4 user here. I have been shooting with Astroberry using my old and beloved X-T10, guided by PHD2. As the X-T10 is not supported by gphoto I hoped I could finally control the camera through Ekos now with the X-T4 but it seems it's still very unstable.

Did you make any new progress / new insights using X-T3/4?
3 months 1 week ago #72050

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

  • Posts: 44
  • Thank you received: 2
I'm not sure I have any new insights, but I did want to flag an issue that's plaguing me. I started a quick response to Riccardo yesterday but decided to compose offline and include some log file information within the response.

I am still plugging away using my F-T3 and having some small successes. MOST of the time I get the results I'm hoping for - in terms of the camera behaving as defined in the Capture Module settings (ISO, exp. time, number of shots, etc.).  In each session  though something seems to go wrong, usually the exposure times get jumbled.

For example, on a clear night last week I had set up three exposure sequences: 2 x 1 sec., 20 x 120 sec. and another 20 x 120 seconds. The ISO sets correctly but (like every time), the first  exposure fails (I've learned to keep them short so I'm not wasting too much time). Usually the second attempt succeeds and thing progress as expected. But, not always. Frequently I get the "Could not wait for event" error message and then some attempts at exposures that are NOT in the sequence currently being exposed. These random exposures have always matched the current guide camera exposure setting. 

Here is a snippet of the the indi_fuji_ccd log from that session (with my annotations):

WARNING    1338.554369 sec    : All images and folders shall be deleted from the camera SD card after capture if capture target is set to SD Card.  ***** actually images are ALWAYS saved, regardless of this setting
INFO    2120.716599 sec    : Starting 1 seconds exposure.
ERROR    2121.845897 sec    : Error downloading image from camera: Directory not found    ***** to my knowledge the directory is properly defined in Ekos and Indi
ERROR    2121.846011 sec    : Failed to expose.
INFO    2121.913572 sec    : Starting 2 seconds exposure.        ***** wrong time, should be 1 second (this is the guide CCD exposure time)
INFO    2135.504177 sec    : Starting 1 seconds exposure.        ***** 2nd attempt - nothing…
INFO    2148.198707 sec    : Starting 2 seconds exposure.        ***** again, the wrong time reported (but corresponds the guide exposure time though ??)
INFO    2161.949513 sec    : Starting 1 seconds exposure.        ***** 3rd attempt - successful
INFO    2164.608158 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_1_secs_2021-06-03T23-18-16_001.raf
INFO    2173.711968 sec    : Starting 1 seconds exposure.        ***** second exposure of 1 sec. sequence started and saved
INFO    2176.331714 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_1_secs_2021-06-03T23-18-28_002.raf

    ***** start of first 120 second sequence - all looks good.

INFO    2186.458305 sec    : Starting 120 seconds exposure.
INFO    2311.656320 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-20-43_053.raf
INFO    2321.761852 sec    : Starting 120 seconds exposure.
INFO    2446.911192 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-22-59_054.raf
     ***** omitted lines here *****
INFO    4127.636040 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-50-59_066.raf
INFO    4138.788107 sec    : Starting 120 seconds exposure.
INFO    4264.340503 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-53-16_067.raf
INFO    4276.546513 sec    : Starting 120 seconds exposure.

    *****( Now things go wrong… after 15 correct exposures of 120 seconds, there are still 5 more to go:

ERROR    4396.466260 sec    : Error downloading image from camera: File not found
ERROR    4396.466368 sec    : Failed to expose.                      ***** until the download attempt everything appears to be working - not until the exposure is over is it noticeable
INFO    4396.508905 sec    : Starting 2.5 seconds exposure.    ***** once again, this is the guide camera exposure time
WARNING    4396.567961 sec    : Could not wait for event.       ***** don’t have any idea what event this refers to…
WARNING    4396.569318 sec    : Could not wait for event.
WARNING    4396.570312 sec    : Could not wait for event.
WARNING    4396.571333 sec    : Could not wait for event.
WARNING    4396.572407 sec    : Could not wait for event.
WARNING    4396.573457 sec    : Could not wait for event.
WARNING    4396.574483 sec    : Could not wait for event.
WARNING    4396.575529 sec    : Could not wait for event.
WARNING    4396.576570 sec    : Could not wait for event.
WARNING    4396.577570 sec    : Could not wait for event.
INFO    4396.577623 sec    : Starting 120 seconds exposure.    ***** an attempt to start the correct exposure - less than 0.1 seconds after the “event” issue
ERROR    4516.486066 sec    : Error downloading image from camera: File not found    ***** after the exposure, the same failure sequence occurs
ERROR    4516.486216 sec    : Failed to expose.
INFO    4516.510096 sec    : Starting 2.5 seconds exposure.    ***** again, an attempt at an exposure that corresponds to the guide camera setting…
WARNING    4516.557539 sec    : Could not wait for event.
WARNING    4516.559214 sec    : Could not wait for event.
WARNING    4516.560762 sec    : Could not wait for event.
WARNING    4516.562386 sec    : Could not wait for event.
WARNING    4516.564513 sec    : Could not wait for event.
WARNING    4516.566101 sec    : Could not wait for event.
WARNING    4516.567698 sec    : Could not wait for event.
WARNING    4516.569300 sec    : Could not wait for event.
WARNING    4516.570865 sec    : Could not wait for event.
WARNING    4516.572513 sec    : Could not wait for event.
INFO    4516.572630 sec    : Starting 120 seconds exposure.    ***** another  attempt to start the correct exposure - less than 0.1 seconds after the “event” issue

    ***** and so on until I noticed the Fuji’s back screen NOT showing an exposure countdown, just the normal live view. I finally aborted the sequence and “reset” the entire system including power cycling the Pi and the Fuji camera, restarting Kstars and reacquiring the target. Each of these failures happens after the (2 minute) exposure is supposed to have occurred.

This is typical of my observing sessions so far.  I have to keep periodic watch on the Fuji’s screen to see if an exposure are actually happening when Ekos indicates one is.

I am really curious to know why the Capture Module is attempting to make exposures that are numerically equivalent to the guide camera when an issue occurs with the Fuji download. Each time I see this, the random exposure is that currently being used by the guide camera.  Some cross-talk happening for some reason?  (the Indi guide CCD log file shows nothing unusual…)

UPDATE:  Last night is was unexpectedly clear so I hastily set up my rig to gather more data on NGC7000.  As I had too move the tripod, polar alignment took longer than usual (I do like the new display triangle).  Unlike every other session, this one came off without a hitch - in terms of the exposure sequences (after?the "first exposure attempt failure" event). I captured 30, two minute exposures without an issue.  I then changed objects to try another few exposures before heading to bed.  Upon looking out the window to see the mount was moving properly, I noticed I had left the Bahtinov mask on the telescope (the fancy WO one that came with my GT-71).  I have just over an hour of images with a beautiful collection of Bahtinov diffraction patterns.  Rats.


 
3 months 1 week ago #72126

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

Time to create page: 0.968 seconds