Rob Meades replied to the topic '[SOLVED] Indi CCD streamed mode' in the forum. 6 years ago

Many thanks. I did try clicking in the image part of the focus window but it always thinks I'm trying to select a star to focus on, giving me a small green box rather than crosshairs.

Rob

Read More...

Rob Meades replied to the topic '[SOLVED] Indi CCD streamed mode' in the forum. 6 years ago

Yup, confirmed that streaming works happily now.

I've also re-found the button that displays the focusser-captured image in a separate FITS viewer window, though I thought it used to update the FITS image whenever a new image arrived? I wanted to use the FITS viewer window particularly because it has the cross hairs and I was trying to line up the centre of my finderscope with my main scope. Managed to do that happily enough in the end by hitting the FITS image button again as needed.

Read More...

Rob Meades replied to the topic 'Indi CCD streamed mode' in the forum. 6 years ago

Thanks Jasem, will update later and also check the FITS window in the focus module.

Read More...

Rob Meades created a new topic ' Indi CCD streamed mode' in the forum. 6 years ago

My understanding (which may be wrong) is that Indi streamed mode uses the same exposure as you set in the main tab for each CCD.

I have used it successfully to get a continuous image stream from my CCDs (ASI 120 MC and QHY5-II) while aligning the finder with the main scope during the day, but when I use streamed mode at night I get blackness whatever I set the exposure to. If I take individual images by pressing the "set" button on the exposure tab then things work as expected and the exposure is obeyed.

Have I misunderstood streamed mode or am I doing something else wrong? Or is this just a feature of my cheap Chinese CCDs?

There used to be a mode on the focus tab where you could get repeated images in a FITS viewer window but that seems to have disappeared. Repeated automatic imaging is really useful for a newbie like me while trying to line everything up. Is there some other way to get it?

Read More...

Weehee! That's fixed it for me, thanks knro. @redcodex should have another try.

Read More...

I'm not running on a desktop or a Raspberry Pi I'm afraid, I'm on a Hummingboard Pro (a bit like a Pi but with a different processor and much faster IO) with Arch Linux. It isn't Indi that is crashing (though that is the net effect), it's the indi_qphy driver with what looks like a buffer overrun. Changing my Linux distribution to fix it seems like over kill.

Read More...

I'd be interested in any views on this as I have a similar issue with QHY5-II-M, my segfault being in memcpy (see journal below). The issue occurs the moment I attempt to grab an image. This is with latest indi and 3rd party drivers (retrieved from github a few days ago).

Since QHY was just as troublesome when I paused working on this 6 months ago, I'm wondering if it's time to give up on QHY and find another CCD that is compatible but less troublesome. Views?

Dec 31 14:50:37 AstroOne kernel: usb 2-1.1.1: New USB device found, idVendor=1618, idProduct=0921
Dec 31 14:50:37 AstroOne kernel: usb 2-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 31 14:50:37 AstroOne kernel: usb 2-1.1.1: Product: QHY5-II          
Dec 31 14:50:37 AstroOne kernel: usb 2-1.1.1: Manufacturer: QHY-CCD  
Dec 31 14:51:19 AstroOne systemd[1]: Started Indi server.
Dec 31 14:51:19 AstroOne indiserver[868]: 2016-12-31T14:51:19: Driver indi_eqmod_telescope: EnumeratePlugins - found plugin SVD Math Plugin
Dec 31 14:51:29 AstroOne indiserver[868]: 2016-12-31T14:51:29: Driver indi_qhy_ccd: recorder: setpixelformat 1497715271
Dec 31 14:51:29 AstroOne indiserver[868]: 2016-12-31T14:51:29: Driver indi_qhy_ccd: recorder: setsize 1280x1024
Dec 31 14:51:29 AstroOne indiserver[868]: 2016-12-31T14:51:29: Driver indi_qhy_ccd: recorder: setsize 1280x1024
Dec 31 14:51:47 AstroOne systemd[1]: Started Process Core Dump (PID 880/UID 0).
Dec 31 14:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: Driver indi_qhy_ccd: stdin EOF
Dec 31 14:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: Driver indi_qhy_ccd: restart #1
Dec 31 14:51:49 AstroOne indiserver[868]: Child process 871 died
Dec 31 14:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: select(18): Interrupted system call
Dec 31 14:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: good bye
Dec 31 14:51:49 AstroOne systemd[1]: indi.service: Main process exited, code=exited, status=1/FAILURE
Dec 31 14:51:49 AstroOne systemd[1]: indi.service: Unit entered failed state.
Dec 31 14:51:49 AstroOne systemd[1]: indi.service: Failed with result 'exit-code'.
Dec 31 14:51:50 AstroOne systemd-coredump[881]: Process 871 (indi_qhy_ccd) of user 0 dumped core.
                                                
                                                Stack trace of thread 871:
                                                #0  0x000000006d81db20 memcpy (libc.so.6)

Rob

Read More...

Solved it: I re-built the ASI driver and noticed that I had an indi_asiccd.xml file in my /usr/share/indi directory (which I think was the one I was using) as well as a shiny new indi_asi.xml file. I removed my old XML file and things are now behaving.

Read More...

Not entirely out of the woods yet: updating my indi server after 6 months of inactivity, my ASI CCD driver won't start anymore. It worked just before the update, then after git pulling everything and rebuilding indilib and all my 3rd party drivers, if I start indi with just the ASI CCD it's not very verbose:

$ indiserver -vvv indi_asi_ccd
2016-12-10T01:12:51: startup: indiserver -vvv indi_asi_ccd 
2016-12-10T01:12:51: Driver indi_asi_ccd: pid=277 rfd=3 wfd=6 efd=7
2016-12-10T01:12:51: listening to port 7624 on fd 4
2016-12-10T01:12:51: Driver indi_asi_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2016-12-10T01:12:51: Driver indi_asi_ccd: read defSwitchVector   Idle ro
2016-12-10T01:12:51: Driver indi_asi_ccd: read defTextVector   Idle ro

...and Ekos fails to find any devices. If I add my other devices (EqMod, Moonlight and QHY) they are all detected normally.

I will continue to poke around but any pointers are welcomed...

Read More...

S'OK, sussed it. I noticed that the date/time of the indi_eqmod_telescope binary file in /usr/bin was in June this year, then I remembered that when building libindi I'd forgotten to do the final sudo make install step until after I'd built one or two of the drivers. I suspect the version of indi_eqmod_telescope was an old one that came with libindi, building and installing indi_eqmod_telescope again did the trick, the time and date is now today and the indi server starts correctly.

Working again :-).

Read More...

Thanks for doing all this checking. I updated the Indi server stuff by pulling the code from git and building it for my devices (EQMOD mount, QPHY and ASI CCDS, Moonlight focuser). My mount is in /tty/USB1 rather than USB0 but it is mapped to /def/heq5 and sending "e1" to /dev/heq5 produces the response "=020401", so I know it's there. However there seems to be a need to set INDIDEV, which I guess wasn't there before. There must be a configuration file that I need to tweak somewhere...

2016-12-30T00:04:29: startup: indiserver -v indi_eqmod_telescope 
2016-12-30T00:04:29: Driver indi_eqmod_telescope: pid=395 rfd=3 wfd=6 efd=7
2016-12-30T00:04:29: listening to port 7624 on fd 4
2016-12-30T00:04:29: Driver indi_eqmod_telescope: Connecting to port INDIDEV at speed 76
2016-12-30T00:04:29: Driver indi_eqmod_telescope: Error:  -> Error connecting to port INDIDEV: Port failure Error: No such file or directory. Check if device is connected to this port.


Read More...

Hi there. I've just updated Indi, both client (on Ubuntu) and server (on ArchLinux) after 6 months of absence. Before I updated all was working fine, after update I can't start the Indi server, the error (for the simplest configuration of just starting the eqmod mount driver ) is shown below. I know the mount is there because I can talk to it on the expected port via minicom. I will keep looking, of course, but any pointers as to what might have changed are welcomed. I don't recall having to specify INDIDEV previously.

2016-12-29T20:58:30: startup: indiserver indi_eqmod_telescope 
2016-12-29T20:58:30: Driver indi_eqmod_telescope: Connecting to port INDIDEV at speed 76
2016-12-29T20:58:30: Driver indi_eqmod_telescope: Error:  -> Error connecting to port INDIDEV: Port failure Error: No such file or directory. Check if device is connected to this port.
2016-12-29T20:58:30: Driver indi_eqmod_telescope: stdin EOF
2016-12-29T20:58:30: Driver indi_eqmod_telescope: restart #1
Child process 318 died
2016-12-29T20:58:30: select(8): Interrupted system call
2016-12-29T20:58:30: good bye


Read More...