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

interesting USB conflict on Pi 4 (SSD vs SD card) - by: airscott

$
0
0
I've been experimenting with variations of my Pi 4 imaging configurations in Kstars/Ekos.

I recently bought a fast USB SSD to replace the SD card on a Pi 4 (4 GB) running Raspbian. Software installed using rlancaste's AstroPi3 scripts.

The SSD is plugged into a USB3 port on the Pi, and noticeably improves both boot times and application launch times. The whole system feels snappy and responsive.

But I can't really use this system for imaging, at least with my full-frame ASI094MC Pro, apparently because downloading the large image files conflicts with the SSD on the USB bus. Mostly INDI just fails to download the image from the camera completely.

I have been able to get images to download into Ekos by reducing the USB "bandwidth" in INDI settings to 40%, but even with a USB3 cable this takes about 2x as long as using the same camera attached to the same Pi4 using USB2 and a fast SD card.

There are lots of articles on Pi forums touting the benefits of replacing SD cards with fast USB SSDs. Unfortunately I think for astroimaging this is a dead end.

PHD2 can't be used as guider in KStars 3.4.3 - by: JCJ

$
0
0
This only occurs since KStars v. 343, not in previous versions
The error msg in the EKOS guider pane l is :
The following error occurred : unknown error.
Reconnecting to PHD2 host : localhost, port 0...

Internal guider store 2 calibrations - by: alacant

$
0
0
Hi everyone
I've 2 guide setups. One with a guide scope and the other with an oag. Separate cameras for each.

Question: is it possible to store and reuse calibrations for each?

Cheers and clear skies,
Steve

Astrohat - An open hardware RPi Hat for astronomy equipment - by: ppapadeas

$
0
0
Hello all,

For those of us that are having at the heart of our astronomical setup a RaspberryPi it has been for long now an idea to be able to centralize some critical monitoring and control functionality rather than having extra boards and equipment around. Power boxes are great, and they come in various flavors from many companies on the market. Unfortunately they are either lacking functionality, are expensive for what they are or simply are not open source enough for my taste. That's why I decided to spend some time and design a RaspeberryPi 4 compatible hat that includes the following functionality:
  • 4x 12V switchable outputs @3A each
  • 2x 12V PWM switchable outputs @3A each
  • 1 adjustable 6-12 V output @3A
  • Current and fault monitoring for each channel individually
  • Temperature, Humidity and Pressure sensor port (for an external readily available module)
  • Automotive grade electronics and design (to ensure reliability on all environments

Everything seems to fit nicely on a RPi hat form factor. Attached are some renderings of the design so far.
I designed everything on KiCad and the board designs are released as open source hardware (CERN-OHL) at this repository:
gitlab.com/pierros/astrohat

I am posting this here with the intention to solicit feedback and potential contributions to my effort.
The design can be considered complete for v1.0 and I plan to order some boards soon for testing and software development. I envision a daemon running locally on the RPi and an indi driver to communicate with it.

How does the feature set seem to people? Anything obvious missing?
Would people be interested in a small production run?

Once the first boards arrive and I can verify functionality and placement of ports, I plan to also design a case (probably an aluminum enclosure for the Hat together with the RPi).

Any ideas, feedback, comments are highly welcome!



ps. as a side note, I would really like to see more open hardware projects in the domain of astronomy (amateur or not) and see a flourishing community around them.

ASI2600MC - by: alintolea

$
0
0
so I installed astroberry 2.0.2 on a rasp 4 (8g). all fun and games, but I need to upgrade the indi drivers/library to the latest version, as what's there doesn't seem to have drivers for ZWO cameras (there;s no ASI/ZWO camera option in the indi web manager menus when creating a new configuration, and it really needs to be the latest to support my asi 2600-mc-pro.

So, how do i install the latest indi/drivers?

Alin

How to catch stream from indiserver with openCV - by: Stefie1987

$
0
0
I would like to catch a live stream from a ZWO ASI camera with openCV.
I kind of figured out how to use indiserver to connect to the camera and I found the stream option.
However, I have no idea where the stream is going or how to catch the stream, since there seems to be no object like /dev/video created by Indi_setprop "... STREAM=On".
Has anyone figured that out?

AstroBerry configurations - by: AradoSKYindi

$
0
0
Hello,

Last night became clear. I got setup to begin observing. GPSD is working. Polar alignment works well. The moon is rising. Jupiter and Saturn are rising. Andromeda is in view. I seek Andromeda and slew to the expected view. Nothing but empty. Next time, I will add a red dot to watch how INDI and the scope are traveling.

I seem to have missed a configuration. Or something is missing. The moon is east southeast to me this makes a meridian flip. Even Jupiter and Saturn start the same but are nearly south of me. I took pictures to explain my problem.




This is where KSTARS thinks the moon is. The moon maybe rising in another part of the world or a different date. But it is not below the horizon.

GPSD is working. Its UTC time is correct. KSTARS says the Date is July 31. Hmm... the PI date is July 31. I thought adding an RTC to the PI was supposed to prevent Drift or Time slew. SET TIME to Now starts to alter KSTARS to July 31. July 31 is the last time I had it internet connected to get updates.

Bummer. I set the UTC time manually. PI and KSTARS are both saying today. The moon pictures are after setting UTC time. When I compare Cassiopeia with Polaris to KSTARS, they kind of match. I will add a red dot to check the sync between KSTARS and the Scope. Neither are in sync.

EQMOD shows the Scope on Polaris. Sync shows EQMOD on target. If EQMOD is on target, what did I miss to produce my pictures?

Polaris Hour Angle & GPSD - by: AstroNico

$
0
0
Hello

I have a just setup an USB GPS module for my Pi4.
GPSD is working and VirtualGPS is disabled.

Do you know why "Polaris Hour Angle" is different between Ekos panel and INDI panel?
And which one should I use?


Thanks
Nico

PNew User - A speed question - by: psg8064

$
0
0
New user transitioning to INDI. I have been slowly getting all the components of KStar/EKOS to work over the past couple of weeks.

My setup:
  • Raspberry Pi3B running the INDI Library
  • Skywatchrer EQ6R
  • Canon EOS 77D DSLR
  • Sigma 70-200mm Zoom with 2/x Extender
  • ZWO 30mm guide scope w/ASI120mc camera

So far I have everything connected and working using KStars/EKOS on my laptop connected through my WiFi network to the Raspberry Pi. I have been able to align, guide and capture images.

However, the downloading of the images whether I'm capturing subs or images for alignment is very slow. It takes 40-60 seconds to download one image. I'm thinking there must something I'm doing wrong either in my process or my setup. I'm hoping someone might have some suggestions for me.

Also, is there a way to just save images to the SD card and not have them download? Once I'm happy with the image, it would be nice to speed things up by just running a sequence of captures where it only saves on the camera SD card.

I have format set to native and upload set to client. I am using the offline solver in alignment (with Astrometry loaded on the Raspberry Pi).

Raspberry Pi HQ Autoguiding? - by: DrBrainz

$
0
0
I’m thinking of acquiring a Raspberry Pi HQ Camera for autoguiding using PHD2; it has (from specs) decent sensitivity, capacity for binning and raw output, 12mp resolution, possibility to remove the IR filter as well, better at long exposures than Pi Cams v1 and v2. It does gave a rolling shutter however.

With an aftermarket 25mm c lens, it’d be equivalent to a 350mm lens on my crop sensor Nikon, and the 25mm lens is pretty fast at f/1.6. Whole thing would cost about 75 USD.

Any thought about this setup? Beats acquiring a dedicated guide scope or guide scope+cam, although a c-to-t mount exists if it is felt a guide scope would be necessary, and it’s be pretty easy to mount on the scope (straight-up 1/4 screw mounted on the ring) or on my astro dSLR body (hot shoe to 1/4 adapter). It seems to be supported by PHD2, but any optical or indi-related reason not to go for this setup?

Service not available - by: Dirk Tetzlaff

$
0
0
From time to time my floating menu ceases to work (see screenshot). Both the GPS and the Polaris Hough Angle Indicator are being affected. Alternatively to the message on the screenshot I see a grumpy smiley.
Does anybody know, why that is and how to remedy it ? Depending on the situation I had luck with doing an update / upgrade via "sudo apt-get" or with plugging in certain USB devices prior to startup. I tried to bring the menu back with "sudo systemctl restart GPSD.service", but this did not work....
Any advice is highly appreciated.
Ah, forgot to mention: the GPSD service seems to work ok, as the indi-GPSD works.

SPC900 LX without mod - by: alxgomz

$
0
0
I just got a Phillips SPC900 I hoped I could use for guiding.
Most things on the setup are working but I can't seem to get the long exposure working on this cam.

It's not moded but my understanding was that it was not 100% necessary.
In particular I was under the impression one could use the LED ioctl in order to transmit long exposure commands.
In particular this thread bellow filled my heart with hope:
www.indilib.org/forum/ccds-dslrs/721-how...d-long-exposure.html

@gaetan mentioned his driver can work without moding the cam (at least that's my understanding), so I ported his changes to the current driver and recompiled but despite I can load the new module with appropriate settings (flashled=1) I still get an error when clicking on the "SPC900 LED" button in the "Long Exposure" tab of the indi_v4l2_ccd panel:



Anyone know how to shoot long exposure frames with the SPC900? Is there any solution which doesn't involve soldering and buying more electronic parts?

Skywatcher AZ GTi in Az-Mode via cable? - by: RogueSquadron

$
0
0
Hello,

I am preparing the AZ-GTi for my vacation and I am a bit confused about the driver options in EKOS. I would like to operate it via cable (USB EQ direct) in AZ-mode.

What I found out so far:

AZ-GTi driver: WIFI only
EQMod Mount; works via USB EQ direct cable (without hand controller)
Alt-AZ driver: does not work via cable for me.

So it seems, I need to go with the EQMod Mount driver, but where can I set AZ or EQ mode of the mount?

Thanks in advance

Amin

after upgrade to 2.0.2 slow fits downloads... - by: MikeCEM60

$
0
0
First: Hats off to Kaczorek, ASTROBERRY is awesome and has served me very well over the last 24 month. Thanks Kacz!

recently updated from v1.1.0 to v2.0.2.

after the usual upgrade-hiccups I was able to connect, but downloads for my FITS - which I store on my desktop - have slowed down quite a bit: was 7ish seconds, now highly variable between 18 and 34sec. Maybe a VNC issue???

not too big a deal, but if there is an easy fix I would like to learn about it...

Thanks!

SM OS direct eth connect - by: dean

$
0
0
I have SM OS 1.5.3 running on RPI 4 8Gb. Burned the image directly to my SSD drive and all works. What I want to do
is run this over an ethernet cable from the pi to my laptop and then connect to the pi to run Kstars/Ekos over VNC.
I can connect this way if the hotspot configured by SM OS on the pi is running but I want it off, so I removed the network profile
for the hotspot. I have tried the instructions here
www.stellarmate.com/support/faq.html?view=faq&faqid=17
but no go. If there is no hotspot provided by the pi and it is not connecting to the LAN off my router, what address and or port
do I need to enter into VNC to connect over ethernet cable from laptop to pi ?

GPSD not establishing a fix, but gpsmon works - by: jerry

$
0
0
Is anyone able to guess an issue with gpsd connecting but not establishing a fix?

lsusb -v gives this:



Tthe /lib/udev/rules.d/60-gpsd.rules
rule looks OK to me

gpsmon shows that the gps is working as shown below, but under indi driver --> Name: GPSD, Exec: indi_gpsd, Version: 0.5, Interface 32832 it never gets a fix?


BTW, I previously had problems with the driver crashing which Jasem diagnosed as an old duplicate installation. Now it doesn't crash, but I don't get a fix.

Thanks

My focus values drift over time??? - by: DerPit

$
0
0
Hi,

I noticed an irritating thing when looking at my focus values over the last month. There is a substantial dift (to smaller numbers) of the focus points for one filter, something like 500 units by now which would compute to ~0.75mm - a LOT! And temperature was more or less constant around 12-13⁰C during that time.
Now the issue is, this is a R&P focuser, i.e., no slip possible. I re-checked the connection between the focuser axis and the motor (a Pegasus DMFC). No way this can slip. And the OTA/camera setup has not been disassembled during that time, I only move the whole unit in and out for observations. OTA is a 140/910 refractor, so no other moving optics in the game. So HOW could this change physically?

My suspicion is the Backlash. I did measure it with a micrometer, getting 165 steps BL. I entered this in the INDI driver and activated BL compensation. A quick check focusing forth and back using the INDI control panel confirmed that worked fine. When changing direction the motor would move the additional steps, and then correct the number. And I did end up at about the same dictances on the micrometer, no matter from which direction I approached a value.

I'm using the AF routine of EKOS to focus, and see that there is also a box with a BL value - the same I've entered in the INDI control panel. Does the AF module do anything with this value? Or is that only for display? I'd hope the latter, else it might get double 'corrections'....

Is anyone else seeing similar drifts in focus numbers, or has some explanation what's going on there?

interesting USB conflict on Pi 4 (SSD vs SD card) [NEVER MIND ...] - by: airscott

$
0
0
I've been experimenting with variations of my Pi 4 imaging configurations in Kstars/Ekos.

I recently bought a fast USB SSD to replace the SD card on a Pi 4 (4 GB) running Raspbian. Software installed using rlancaste's AstroPi3 scripts.

The SSD is plugged into a USB3 port on the Pi, and noticeably improves both boot times and application launch times. The whole system feels snappy and responsive.

But I can't really use this system for imaging, at least with my full-frame ASI094MC Pro, apparently because downloading the large image files conflicts with the SSD on the USB bus. Mostly INDI just fails to download the image from the camera completely.

I have been able to get images to download into Ekos by reducing the USB "bandwidth" in INDI settings to 40%, but even with a USB3 cable this takes about 2x as long as using the same camera attached to the same Pi4 using USB2 and a fast SD card.

There are lots of articles on Pi forums touting the benefits of replacing SD cards with fast USB SSDs. Unfortunately I think for astroimaging this is a dead end.

Best way to run indi_setprop to automaticaly configure a device (focuser) ? - by: basilr

$
0
0
What would be the best/easiest way to run indi_setprop to configure a device (a Moonlite focuser).?

When my Astroberry boots up I have the drivers to Start automatically. I would like to the drivers to load, then automatically run a script using indi_setprop to send specific config settings to the focuser (and other devices?).

Thank you!

Error initializing the CCD - by: CapnRon

$
0
0
I just received a new ZWO ASI533 MC Pro camera. I am running the Asroberry Server ver 2.0.5 with Kstars 3.4.2 on an Rpi 4. I tried updating the indi library for ASI devices and it said that I already have the latest version 1.7.

I plugged the camera into one of the RPI 4 USB 3.0 slots using the camera's USB 3.0 cable. I set up a test profile for the ZWO camera and started EKOS. THe Indi control panel shows the ZWO CCD ASI533MC Pro in the label. When I try to connect I get {ERROR} Error Initializing the CCD (16).

Any thoughts on how I proceed from here to get the camera running?

thanks,
Ron
Viewing all 15748 articles
Browse latest View live


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