Quantcast
Channel: Recent Topics - INDI Forum
Viewing all 14088 articles
Browse latest View live

GPS NMEA Bluetooth - by: Gerard

$
0
0
Hello everybody,

I have played around with a Navigon bluetooth GPS NMEA...
It works well with the Raspberry under Ubuntu 16.04 so i can get all GPS datas with:

I have tried to use indi_gpsnmea but not support bluetooth connexion.
also GPSD does not send any data to Ekos...

Is it something I have got wrong or may be a bad driver connexion ?

I thank you in advance

ALccd-QHY 9: not supported by indi? - by: astronom

$
0
0
Hi everybody,

I've got an ALccd-QHY 9 monochrom CCD, and I thought should work with the indi_qhy_ccd driver. But all I get is a yellow light in Main Control / Connection tab.
Can anybody tell me if this CCD model is supported? It looks exactly like the QHY9S to me and QHY9S should be supported by indi_qhy_ccd.



The driver output is:


The USB ID is 1618:8301.
When I run qhy_ccd_test, I get the attached output.

The "PC" is a small embedded device with Ubuntu 18.04.02 and indi 1.7.6, linux kernel 4.15.0-46-generic. The camera is connected via USB2. Filter wheel not connected at the moment.

Cheers, Peter

Anyone using Altair cams on Raspberry Pi ? - by: kamisan

$
0
0
Has anyone had any experience using an Altair camera on Astroberry or StellarMate?

After several successful image captures my Altair 290M hangs with "0.00 seconds to go" and then times out after 3 minutes in Ekos Capture (i.e. ESQ).

I've tried adjusting the "speed" control in INDI control panel but it doesn't have any detectable effect.

To reduce the possibility that it is a power-to-the-Pi issue I unplugged all non-essential USB devices (e.g. U-Blox GPS, ASI EFW, and Flip Flat.) No discernible effect on the outcome.

I've had the camera for a year and a half. It works flawlessly using INDI/Ekos on my Linux laptop and in SharpCap on a Win7 laptop. This problem appears to be related to the Pi Model B.

I am using a standard length USB2 cable between the Pi and the camera. I have on order a 1.5 foot long cable. The camera is a USB2 device.

From INDI control panel I found the INDI driver version and firmware version. I compared versions on the Pi and Linux laptop. They look to be identical.

Any recommendations on how I can proceed with debugging this?

Thank you.

Park is a bit off - by: maxthebuilder

$
0
0
Hello,
Using the latest nightly build on RPI.
I go to INDI control panel - mount site management.
Do purge, default, write. It sets ALT to the correct 37° 22' 38" but DEC is a bit off at 89° 58' 46".
Is this a bug or my fault somewhere? It used to work right...
Thanks!

Usb dew point not connecting - by: fenriques

$
0
0
I always had big issues connecting to Usb_dewpoint (and to get help or any feedback from the manufacturer).
After starting the driver and trying to connect, usb_dewpoint doesn't work and also other serial devices are disconnected.

In the latest release usb_focus connection issues were fixed. Could it be that Usb_dewpoint had the same connection method and that can be fixed as well?

Ferrante

Fits viewer for Windows - by: maxthebuilder

$
0
0
Hello,
I use fitswork to view fits files on my windows PC. It's very good but only allows to view one file at a time.
Is there a fits file browser? I searched but couldn't find any.
I need a viewer/browser which shows all fits files in a folder so that i can discard the bad ones.
Thanks!

Network issues!! - by: AstronomerDaz

$
0
0
So, I WAS able to connect my astroberry server to my WLAN and remote onto it via the browser.... (note, was!!)

I decided to try and get the VAP working so I could connect in the field, and this is where it all went wrong!! I was not able to connect to the RPi at all using the 'astroberry' VAP, although my Ubuntu client 'seemed' to connect and receive an IP address. No matter what I tried (browser, VNC) I could not connect.

So, I went back to my WLAN to try and figure things out, and now the RPi won't connect to the WLAN at all... I've tried a static IP address, but that didn't work and now I get a "No DHCPOFFERS received" message when I restart the wlan0 interface! I can only access by plugging into the device with screen/keyboard/mouse, I can't remote to it at all...

The wpa_supplicant file shows the network correctly, and I have even deleted the entry and redone the wlanconf but still no joy!

Any thoughts??

I really don't want to rebuild if I can get away with it....

Thanks!

Got a stellarmate and... - by: Ron Kramer

$
0
0
I wanted to contribute in some small way at this point since I'm not quite operational... so I picked up stellarmate OS.
NICELY DONE. anyway - I went out and did the port assistant and it logged my devices. But when I connect it seems to hunt for ports still?
Am I suppose to change the connection tabs to /Dev/NexDome ? (with each device name I created?)
Or just ignore it now that it's done? Do I turn off scan for ports? It should just connect without question right?
Also I ran this from the PI (on screen in the dome) using the yellow assistant background). I have another one that pops up
in a window on Kstars (on windows?) it seems to have my devices I already mapped, but it pops up asking for more? (I can't unplug devices from in the house).

I ran the updater. (will that update the indi drivers and Kstars? I recently installed the latest Kstars and really liked the update. (on windows at this point).


Questions on Configuring Serial Shutter with GPhoto (DSLR Cameras) in Ekos - by: phattire72

$
0
0
Hello,

I am trying to setup a serial shutter release in Ekos using GPhoto (DSLR Cameras). When I try to connect to the serial cable I get the following error (attached picture):
Cannot Open Camera: Power OK?

In the info for GPhoto (DSLR Cameras) it show the following:

If your camera uses an external shutter release cable, make sure to indicate the port of the shutter release USB cable (usually /dev/ttyUSB0) in the Main Control tab of the GPhoto driver before connecting to the camera.

Additionaly, users may employ DSUSB/DSUSB2 from Shoestring Astronomy in order to control the shutter. Before you connect, the port field must be set to DSUSB.


I verified my Pi is seeing my USB Comm port and it is listed as /dev/ttyUSB0 when I have the terminal list devices.

Does anyone know what I could be doing wrong? I have not added the circuitry for the shutter release yet to the Comm port as I would like to verify GPHOTO sees the Comm port first.

Got a stellarmate and... - by: Ron Kramer

$
0
0
I wanted to contribute in some small way at this point since I'm not quite operational... so I picked up stellarmate OS.
NICELY DONE. anyway - I went out and did the port assistant and it logged my devices. But when I connect it seems to hunt for ports still?
Am I suppose to change the connection tabs to /Dev/NexDome ? (with each device name I created?)
Or just ignore it now that it's done? Do I turn off scan for ports? It should just connect without question right?
Also I ran this from the PI (on screen in the dome) using the yellow assistant background). I have another one that pops up
in a window on Kstars (on windows?) it seems to have my devices I already mapped, but it pops up asking for more? (I can't unplug devices from in the house).

I ran the updater. (will that update the indi drivers and Kstars? I recently installed the latest Kstars and really liked the update. (on windows at this point).

Nikon D3200 DSLR + Ekos Nightly - by: Wilkinson

$
0
0
I'm sure this has been raised before, but can't seem to find a way forward with it. So, here we go ...

I'm running Kstars nightly builds on Linux Mint, and have tried both GPhoto2 as well as Indi to control my Nikon D3200. I'm running the camera prime as my main camera, with a QHY 5 II guide scope. lsusb sees the Nikon body when I connect it via USB:

lsusb
Bus 002 Device 020: ID 04b0:042c Nikon Corp.

dmesg -w
[13018.896949] usb 2-1: USB disconnect, device number 19
[13036.136798] usb 2-1: new high-speed USB device number 20 using xhci_hcd
[13036.285555] usb 2-1: New USB device found, idVendor=04b0, idProduct=042c
[13036.285561] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[13036.285565] usb 2-1: Product: NIKON DSC D3200
[13036.285569] usb 2-1: Manufacturer: NIKON
[13036.285573] usb 2-1: SerialNumber: 000006245043

Also, I have a rule set up to prevent mounting the camera as a USB drive:
/lib/udev/rules.d
85-disable-dslr-automout.rules

cat /lib/udev/rules.d/85-disable-dslr-automount.rules shows:
# Nikon
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b0", ENV{UDISKS_AUTO}="0"

So, everything seems fine, and INDI can connect to the camera, however trying to take a test 2 second exposure, I get the following error:

INDI Ctrl Panel
2019-03-14T20:13:52: [INFO] Starting 2 seconds exposure.
2019-03-14T20:13:52: [ERROR] Exposure failed to save image... Unspecified error
2019-03-14T20:13:39: [INFO] Starting 2 seconds exposure.

I've enabled CCD debugging, and see this in the logs:
Indi CCD Logs
[2019-03-14T20:16:12.174 GMT INFO ][ org.kde.kstars.ekos.capture] - "Job requires 2.000-second images, has 0/3 frames captured and will be processed."
[2019-03-14T20:16:12.178 GMT INFO ][ org.kde.kstars.ekos.capture] - "Capturing 2.000-second image..."
[2019-03-14T20:16:12.223 GMT INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[INFO] Starting 2 seconds exposure. "
[2019-03-14T20:16:12.223 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Starting exposure (exptime: 2 secs, mirror lock: 0) "
[2019-03-14T20:16:12.223 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Mutex locked "
[2019-03-14T20:16:12.223 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Setting radio/menu widget iso: 3 (800) "
[2019-03-14T20:16:12.223 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Setting new configuration OK. "
[2019-03-14T20:16:12.223 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Setting radio/menu widget imagequality: 3 (NEF (Raw)) "
[2019-03-14T20:16:12.223 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Setting new configuration OK. "
[2019-03-14T20:16:12.224 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Using internal bulb widget:bulb "
[2019-03-14T20:16:12.224 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Setting toggle widget bulb: 1 "
[2019-03-14T20:16:12.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Failed to set new configuration value (GP result: -1) "
[2019-03-14T20:16:12.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Exposure started. "
[2019-03-14T20:16:12.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Time left: 1999 ms "
[2019-03-14T20:16:14.127 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Reading exposure... "
[2019-03-14T20:16:14.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Time left: -1 ms "
[2019-03-14T20:16:14.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Closing internal shutter. "
[2019-03-14T20:16:14.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Using widget:bulb "
[2019-03-14T20:16:14.226 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Setting toggle widget bulb: 0 "
[2019-03-14T20:16:14.227 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Failed to set new configuration value (GP result: -6) "
[2019-03-14T20:16:14.227 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Exposure complete. "
[2019-03-14T20:16:15.228 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #1, retrying... "
[2019-03-14T20:16:16.229 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #2, retrying... "
[2019-03-14T20:16:17.231 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #3, retrying... "
[2019-03-14T20:16:18.232 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #4, retrying... "
[2019-03-14T20:16:19.234 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #5, retrying... "
[2019-03-14T20:16:20.234 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #6, retrying... "
[2019-03-14T20:16:21.236 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #7, retrying... "
[2019-03-14T20:16:22.237 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #8, retrying... "
[2019-03-14T20:16:23.237 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #9, retrying... "
[2019-03-14T20:16:24.238 GMT DEBG ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[DEBUG] Event timed out #10, retrying... "
[2019-03-14T20:16:24.241 GMT INFO ][ org.kde.kstars.indi] - Nikon DSLR DSC D3200 : "[ERROR] Exposure failed to save image... Unspecified error "
[2019-03-14T20:16:24.242 GMT INFO ][ org.kde.kstars.ekos.capture] - "Capture failed. Check INDI Control Panel for details."

Does anyone have an idea how I can solve this?

Visual aid for the scheduler? - by: fenriques

$
0
0
having a remote observatory I rely a lot on the scheduler. What have been made so far is very powerful and with the last enhancements is even better (thanks Eric, Jasem and others that worked on that) but when planning an observation I still struggle to find the optimum schedule for different jobs.
E.g. if I plan 3 hrs on M31 it can be then too low on the horizon and knowing that, planning just 2 hours could lead to a better result .
After that, next job could be 2 hrs on M42 but starting 3 hours from now, M42 could be in a position too close to the meridian.
Of course I can simulate the timing of the job on the sky map or rely on the scheduler scoring but having a visual aid on the sky map that shows the tracks of the objects in the hemisphere could be very useful.

As a picture is worth a thousand words, in attachment a basic drawing of what I mean. Dotted / continuous line is like a job progress bar.

Re:Re:Slowdown in the Acquisition process - by: Frank

$
0
0
Hi guys!
I proudly use Kstars/Ekos 3.0.0 in a Macbook Pro (2.6 GHz Intel Core i5, and RAM 8 GB 1600 MHz DDR3).
I acquire data with a Zwo ASI 1600 MM-CC with the cooler switched on and to which I connect the guide camera ASI 120MM-CS via the USB port. In addition, I guide through PhD2.
I noticed that the acquisition process slows down all the windows of Kstars. If I want to close the FITS previewer window it takes several seconds to do it. As a consequence of the slowdown also the countdown for the single captures is not fluid. I think it is not a problem of my Mac, owing to the fact that the others applications works quite good. I also tried to uncheck the use of the FITS preview during the process but without any good result.
How can I solve the problem?
Thank you in advance!

Franck!

Cloudwatcher INDI - by: Ron Kramer

$
0
0
Anyone using a cloudwatcher? There is no serial interface to connect to the serving computer? I've installed the driver and it just sits there. There is no debug... and there are no connections because
the device has no such interface to the computer? My cloudwatcher is ONLY connected to a LAN port on my mesh router. So how in the heck would it connect to the computer to interface to it?

indilib.org/devices/weather-stations/aag-cloud-watcher.html <--- these pages aren't ever any help. How to connect? how to configure? where to ask questions?

VAP Connection Issue - by: AstronomerDaz

$
0
0
Me again!

So, having fixed my previous issue of not being able to connect to my WLAN, I now have been trying to get a remote connection to the ABS via the VAP.
Here's what I did:

Backup the wpa_supplicant file
Remove my WLAN details from the wpa_supplicant file, to mimic having no WLAN available
Restart the Pi

The device restarts and eventually (it seems to take some time!) the astroberry SSID is visible, but I cannot get a connection to it at all - I just get "Activation of Network Connection Failed" on my Ubuntu 18.04 client.
ifconfig shows



The pi is a model 3b, so uses the hostapd_3b.conf file, but just to be sure, I updated the 3bplus file with the Channel and Mode changes...

So, now I'm stuck again!

i don't think I've changed anything else in my previous WLAN issue, but if anyone has any insights, I'd be grateful!

FYI I-- AstroPhysics Experimental driver issue - by: Ron Kramer

$
0
0
I've left it with tracking off a couple times and it's gone into tracking mode and I've later found the mount maxed out against itself. = (
I'm not sure but I also believe I had it packed once and it also started tracking. Anyone else?

Orion G3 StarShoot on MacOSX - by: samy_astro

$
0
0
Hello,
I am new to this forum. I have seen people using Orion G3 here. I look for a solution to use this CCD camera on my macbook. Do you think this is possible? I have tried with indigo server and astroimager and oaCapture but the camera doesn't appear on the list
Regards

how to disable guide star being downloaded and displayed4 - by: alacant

$
0
0
After the last update to stable, the guide star once again displayed by default in both the guide module and the summary screen. Unecessary as we're using ohd2. How can it be disabled?
Thanks

Re:Fits viewer for Windows - by: maxthebuilder

$
0
0
Hello,
I use fitswork to view fits files on my windows PC. It's very good but only allows to view one file at a time.
Is there a fits file browser? I searched but couldn't find any.
I need a viewer/browser which shows all fits files in a folder so that i can discard the bad ones.
Thanks!

how to disable guide star being downloaded and displayed - by: alacant

$
0
0
After the last update to stable, the guide star once again displayed by default in both the guide module and the summary screen. Unecessary as we're using phd2. How can it be disabled?
Thanks
Viewing all 14088 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>