Unfortunately it also happens when using a laptop directly connected !
Just read your response Brian - thanks. Im beginning to think that the ZWO hub struggles with the filter wheel, guide camera and trying to download a large image file. I guess the guide camera consumes the most bandwidth under normal operation so it might be that the bus hangs sometimes when a download is initiated at a specific part of the cycle and causes the download issue. I am now connecting my guide camera directly to my laptop so the camera will have practically all the bandwidth for download as the filter wheel only consumes bandwidth when changing the filter. As this happens when using the PI and also with a laptop it is more likely to be at the ZWO end . I think the Pi bus may be a bit flaky but the laptop internal USB bus should be fairly reliable.
I will keep it under monitor now I have made this change - hopefully the problem will go away !
Thanks for your response.
I have used a Pi connected over WiFi and powerline terminal kit but have always downloaded the images to a local USB stick. I found transferring it over the network to be to unreliable. I now use a Laptop running Ubuntu and KStars as my remote device instead of the Pi as I found the Pi to be a little but underpowered for reliable imaging runs ! I found that KStars would close unexpectedly for no obvious reason. The laptop is a lot better but I still download the images locally. I have experienced the missing download state with the two systems and as I download locally it cant be due to network transfer issues. The two systems use different drivers as well. I often wonder about the reliability of the ZWO 's hub as I also plug the guide camera and filter wheel into the hub and have found the guide camera has difficulty connecting to Ekos sometimes which was fixed by a direct connection to the latptop. I have an earlier version of the 1600 and there were some initial issues with downloading due to the use of too high a USB speed. I experienced this with APT and needed to lower the USB speed to the minimum setting to make it reliable. However the pro version implemented buffering to overcome this. I guess its always difficult to establish where the issue is when it involves the interface between two devices - is it hardware or software and which bit of software ! I guess it may be worth raising the problem on the ZWO forum to see if they are aware of it .
Thanks for your responses Eric and Brian
I havent been using guiding Eric so it does not appear to be related to that but good thought.
Looks pretty similar to your issue Brian but I am not using USB3 ! I can go through a whole imaging session with hundreds of downloads and it behaves properly . However something can trigger it into the pattern of not downloading and the only way I have discovered to reset it is to close Kstars/Ekos down and start again ! Its almost like Ekos does not trigger the download and carries on through the sequence straight away. When in this mode it does not count a valid image though so it does not actually progress through the imaging sequence and eventually aborts.
I will check next time to see if there is any evidence in the log files..........
I am currently using Kstars/Ekos with Ubuntu 16.04 on a conventional laptop. I have updated both Indi and Kstars to the latest versions.
I use a ZWO ASI 1600mm-c as my primary camera.
I find that occasionally I get an issue with the capture module where the symptoms are that the capture is initiated and when the timer times out instead of the image being downloaded the timer resets to the initial value and again times out without downloading the image and this sequence is repeated. This can occur in the middle of an imaging session even after taking and downloading a large number of images correctly. The symptoms persist even after disconnecting and reconnecting the camera ! It just appears to get stuck in this mode. I normally set the bandwidth to the lowest speed available ie 40. This can be quite frustrating and disruptive to an imaging session !
I was wondering has anyone else experienced this and solved the issue please ?
I guess a quick solution to this would be to re-install Kstars 3.0.0 which works ok with the Atik driver.
Can anyone help with how I can download an older version of Kstars please. ?Can't find any previous versions on the KDE site
Any news on this please ?
Thanks Jasem - appreciated
Its Ubuntu Mate 16.04.6
Ive just updated KSTARS /EKOS to the latest version 3.1.0.
However I'm finding my ATIK filter wheel now crashes every time it starts.
Please see device manager log below
2019-03-02T12:45:08: startup: /usr/bin/indiserver -v -p 7624 -f /tmp/indififo2a590ac3
2019-03-02T12:45:08: listening to port 7624 on fd 3
FIFO: start indi_atik_wheel
FIFO: Starting driver indi_atik_wheel
2019-03-02T12:45:08: Driver indi_atik_wheel: pid=2450 rfd=4 wfd=7 efd=8
2019-03-02T12:45:08: Client 5: new arrival from 127.0.0.1:44610 - welcome!
2019-03-02T12:45:08: Driver indi_atik_wheel: indi_atik_wheel: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /usr/lib/x86_64-linux-gnu/libflycapture.so.2)
Child process 2450 died
2019-03-02T12:45:08: Driver indi_atik_wheel: stderr EOF
Any help really appreciated !
Thanks Edgar and Helge for your info.
I certainly will have a look at both these leads to find if they can solve the problem.
It seems that Blue tooth cannot find a port to connect to ! Not sure what is the difference between Ubuntu Mate 16.04 and Ubuntu 18.04 but it works ok in the former........