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

reverse direction back to normal when connecting to Ekos - by: greenwich43

$
0
0
Hi everyone,

I've built this amazing focuser but it won't stay in reverse direction once connected to Ekos through Kstars.

The configuration with Windows app is ok, when I disconnect and I reconnect the focuser to the Windows app, the reverse checkbox stay checked. The fact to connect the focuser to Ekos turns back the reverse mode to normal. (disconnection from Ekos and connection to Windows config app lets appear the reverse checkbox unchecked.

My actual firmware is: myFP2_DRV8825HW203_293
I've also tried with previous firmwares but without but results.

Any ideas ? Do I need to reverse motor wires ?

Thanks a lot for any help and many thanks for your work and your time spent around this project

3.3.9 Mac EKOS focus and plate solve preview issues - by: Lead_weight

$
0
0
Running 3.3.9 tonight on my Mac laptop to a RPi4 running INDI server.

The new preview looks great on the main summary window, but it's really messed up for the plate solve and focus modules. I have to seriously increase the number of seconds of each frame for any stars to show up or the auto focus routine can't find the stars. The previews for them are mostly black, very difficult for the software to pick up anything. The options for auto stretch seems to be gone? or am I missing something.

I'm using a ZWO ASI071 camera tonight. Not sure what's going on, as it's never done this before.



DIY Flatfield Dustcover with RPi - by: pauledd

$
0
0
Hi there

Since I discovered a regional dealer that got flatfield foils with a evenly white spectrum
I plan to build a DIY flatfield dustcover in the next 2 to x months.
My plan is to follow the nice article
indilib.org/support/tutorials/165-diy-au...telescope-cover.html
but since I never had anything to do with servo motors its a bit unclear to me
what kind of servo I should look for. Especially what force and what gear (metal or plastic).
And of cause it should be as cheap as possible.

I currently focus on the BMS-390 DMH servo that has metal gear and a force of 46NM/cm/4.8V.
That mean that it should handle about 4,6 kilogram 1cm away from the axis. 10cm away makes
460 gramms. My flatfieldfoil will be taped on an 22x22x0,1cm aluminium plate that weights about 200g.

The flatfield would be switched on/off by a relay.
Now my qestion is would it be possible to integrate the flatfield into indi, is there already an solution in indi or do I need to write a new driver
for that?
[Edit] ok I see, thats the purpose of the wiringPi/usb-relay part

Device not appearing in Ekos profile editor - by: Kaczorek

$
0
0
I have encountered a strange problem while setting up profiles in Ekos with a custom driver, which are not listed in Ekos dropdowns.
XML file for the driver is located in /usr/share/indi and it has proper syntax. The problem does not appear in new installations but pops up in case of updated systems with a new version of the driver. Among a few changes in the driver's binary (connection plugins) the XML was updated to reflect driver's name change i.e.
Before update:

After update:


Installing the driver on new system works OK, it appears on the Ekos list and works as designed.
Installing the driver on a system where previous version was installed results in the drivers does not appear on the Ekos list. This applies also for full removal and reinstallation of INDI/KStars/Ekos BUT removing local configuration files for KStars.
When I manually edit the driver's XML and change the label and name to e.g. "Test Driver" it appears on the Ekos list and works OK. If I reedit this file in the next step and change "Test Driver" to anything else it disappears from the Ekos list.

The above suggests that a driver name is somehow cached by KStars/Ekos (where?) and changing XML label/name for a driver results in kind of conflict between cache and source XML. As the result the driver does not appear on the list.

Now the question is where this cache is sitting so I can purge it.

New Bahtinov Mask Assistant Tool - by: sneubert

$
0
0
Dear all,

I have started to make a prototype for a Bahtinov aid, which eventually I would like to put into the EKOS Fokus module.
The idea is the same as with the tools available in APT or the Bahtinov grabber. Since I wanted to understand the problem (and Bahtinov grabber is not very well documented) I developed my own solution in the form of a likelihood fitter.

I attach a few examples what the Bahtinov fitter can do at the moment. For the examples on the Wikipage ( en.wikipedia.org/wiki/Bahtinov_mask ) it can correctly identify the two out of focus pictures, by measuring the displacement of the center line (shown in green) with respect to the two crossing lines.
So I am quite happy and think I understand the problem well enough to start thinking about how to put this into EKOS.

If you guys can send me example shots taken with your Bahtinov mask I would be able to see how robust the fitter is. That'd be super helpful!
Also, the framework can easily be adapted to fit non-standard mask shapes. If you have one of those, please send me the specs and pictures.

If there are suggestions what you would like to see in such a feature I can try to accommodate this.

Thanks!
Sebastian

dslr - image info - by: rkonrad

$
0
0
Hi,

When I connect my canon dslr, I get a message that I should update my camera pixel information in the "image info" section. That section seems to be read only so I'm not sure if there is something wrong. Thanks in advance.

Richard

Incorrect coordinates in FITS header - by: El Corazon

$
0
0
Most, but not all, of the FITS files of various objects I have been imaging over the last few months have incorrect coordinates in their FITS headers. Usually Polaris, but sometimes the coordinates of other objects I have been imaging that night.

Has anyone else had that experience?

Here a link to an image of NGC1499 aka California Nebula with the coordinates in the header pointing to Polaris:

www.dropbox.com/s/bvon7s4r67dgpwe/Califo...-08-09_014.fits?dl=0

It would be great to solve that issue. I have been trying to use these FITS files on subsequent nights to take more images of the exact same frame, but was stymied by the fact that the solver could never come to a solution until I saw that the coordinates in the FITS header are blatantly wrong.

Thanks

Jo

Filter cycling in Sequence Queue? - by: AstroGabe

$
0
0
Would it be possible to add a function in Ekos which cycles through the filters? Let's use an RGB example. Say I have an RGB sequence w/ 8 subs per filter. Instead of imaging 8R, 8G, 8B, I would like to have a function where you take RGBRGBRGB..., so RGB is the sequence which gets executed 8 times. There's a similar functionality in SGP, which I'm coming from, and it was very helpful for planning a session that might be interrupted by clouds - you'd have a roughly equal number of RGB frames as your progress evolves.

Now, I could just do separate 1 off RGB entries in the Sequence Queue, but that would quickly become unwieldy and cumbersome, especially for long sequences

Also, I could do just a 1x RGB sequence, and have the scheduler repeat is 8 times, but the Est. Duration doesn't get reflected in the Scheduler for some reason.

Gabe

Disaster with the last update.... (HELPPPPP) - by: josemsubcn

$
0
0
Dear,

I have the Astroberry server 2.0.0 in a RPI4, just to today the systems works very well, except a full funcitionality of Pegasus PPB driver. I update the system regularly and today today I made the last update with "sudo apt-get update && sudo apt-get upgrade" and there were many library updates. When I perfomed the RPI4 reboot there are some drivers that not work, for example EAF focusser driver, and Pegasus PPB driver.....

Fcouser driver without any error message, but when I want to move the focusser, the driver shows the movement steps, but really the focusser don't move, it seems that works like a simulation driver.....

In the case of Pegasus PPB, the last driver before the update don't works at 100% but at least I can select some funciotionallity, now the driver shows connections errors, and I can't configure any paramenter.

Please, any solution?.

Thanks,

Indi Web Manager Shut down button for Pi - by: RvB

$
0
0
Hello All!

I´m talking about a remote session with Windows KStars and an INDI-Server running on a Pi.

When the astro-session is finished, it would be the easy to shut down the Pi by a Button that is integrated in the INDI Web Manager.
Up to now I then start VNC, log in into Ubunto Desktop and start the shutdown-sequence from there. A bit laboratious, isn´t it ?

Because I´m new to INDI, perhaps someone has a better way for me.

CS
Reiner

AsiAIR + Atlas EQ-G mount - by: cz550

$
0
0
Hi everybody :)

It's my first post in the forum . I live in France ( Alps) and I have a question .
I plan to buy an ASIAIR or ASIPRO . I use a CELESTRON 11 on an ATLAS EQ-G mount ( aged 13 years more or less )
Is somebody could tell me if ATLAS EQ-G mount is recognized by ASI AIR ? is someboby use it with this mount ?

Thank you :)

Philippe

Platform stability - by: giorgio_ne

$
0
0
I’ve been a huge fan of INDI and KStars since I started to play with an OTA mounted RPi in 2016. Things have improved immensely since those days and 2019 has been a truly exceptional year with six releases of KStars and the launch of the Raspberry Pi 4!

I’m immensely grateful to all the people that have poured efforts and huge commitments to this project. The increased visibility and adoption of the INDI platform in its open or embedded forms (both free and paid) is testimony of this great effort.

As our time under the stars is limited by a number of concurrent factors (weather, family & friends, health, work etc.) we all know how precious are those nights when we can dedicate ourselves to Astronomy. Especially for those of us who need to setup and teardown their equipment or need to drive to a dark sky location.

The necessity of being able to have a test environment and a production environment is very acute. Right now unfortunately I’m in a bit of a pickle because, among new features and platform changes, I’m finding increasingly difficult to isolate those INDI/KStars or OS versions that I can safely use in the field without being impaired by: bugs on new features, regression issues, driver issues, Rpi 4 specific issues and OS related issues. On the latter my problems are compounded because I run KStars on a client laptop: I have 3 laptops (Mac OS, Ubuntu Mate and Windows 10).

I’d like to hear from you on what solutions, configurations or software versions have you have adopted to make sure issues and bugs associated to this great wave of innovation do not affect your precious and limited time under the stars.

Thank you all and happy 2020!
Giorgio

My Frustration !!!! - by: Gonzothegreat

$
0
0
So this evening, with just a couple of hours of clear night I got my new QH5L-II-M camera setup, so much more sensitive than the original QHY5.
Now, the frustrating part...
<strong>The ATIK 314 no longer works.
Unable to solve anything, local or remote (astrometry)
</strong>

I spend more time fixing stuff and getting annoyed than taking any astro pictures, really really does my head in.
And yes everything is up2date to this day, server and client. No I do not have a log file, clouds rolled in now. I have to wait another 2 months until I'm back here now.

root@heidenrod-obs:/home/heidenrod# dpkg -l | grep atik
ii indi-atik 2.4~201911160020~ubuntu18.04.1 armhf INDI Driver for Atik cameras and filter wheels.
ii libatik 2.2.6~201911071658~ubuntu18.04.1 armhf Library for Atik Cameras.
root@heidenrod-obs:/home/heidenrod#

root@heidenrod-obs:/home/heidenrod# dpkg -l | grep libindi
ii libindi-data 1.8.2~201911200846~ubuntu18.04.1 all Instrument-Neutral Device Interface library -- shared data
ii libindi-dev 1.8.2~201911200846~ubuntu18.04.1 armhf Instrument-Neutral Device Interface library -- development files
ii libindi1:armhf 1.8.2~201911200846~ubuntu18.04.1 armhf Instrument-Neutral Device Interface library -- shared library
root@heidenrod-obs:/home/heidenrod#


This is what I get with the Atik, no matter which exposure I use.

Disaster with the last update.... - SOLVED - by: josemsubcn

$
0
0
Sorry for all,

I did not connect the power of Pegasus PPB then not enought current to work with the mount and EAF focuser. Now all is working well, included the Pegasus PPB with all the functionallity.

Thanks for the great job to update the libraries, and sorry for my mistake.

Jose


"Dear,

I have the Astroberry server 2.0.0 in a RPI4, just to today the systems works very well, except a full funcitionality of Pegasus PPB driver. I update the system regularly and today today I made the last update with "sudo apt-get update && sudo apt-get upgrade" and there were many library updates. When I perfomed the RPI4 reboot there are some drivers that not work, for example EAF focusser driver, and Pegasus PPB driver.....

Fcouser driver without any error message, but when I want to move the focusser, the driver shows the movement steps, but really the focusser don't move, it seems that works like a simulation driver.....

In the case of Pegasus PPB, the last driver before the update don't works at 100% but at least I can select some funciotionallity, now the driver shows connections errors, and I can't configure any paramenter.

Please, any solution?.

Thanks,"

Frustration !!!! - by: Gonzothegreat

$
0
0
So this evening, with just a couple of hours of clear night I got my new QH5L-II-M camera setup, so much more sensitive than the original QHY5.
Now, the frustrating part...
<strong>The ATIK 314 no longer works.
Unable to solve anything, local or remote (astrometry)
</strong>

I spend more time fixing stuff and getting annoyed than taking any astro pictures, really really does my head in.
And yes everything is up2date to this day, server and client. No I do not have a log file, clouds rolled in now. I have to wait another 2 months until I'm back here now.

root@heidenrod-obs:/home/heidenrod# dpkg -l | grep atik
ii indi-atik 2.4~201911160020~ubuntu18.04.1 armhf INDI Driver for Atik cameras and filter wheels.
ii libatik 2.2.6~201911071658~ubuntu18.04.1 armhf Library for Atik Cameras.
root@heidenrod-obs:/home/heidenrod#

root@heidenrod-obs:/home/heidenrod# dpkg -l | grep libindi
ii libindi-data 1.8.2~201911200846~ubuntu18.04.1 all Instrument-Neutral Device Interface library -- shared data
ii libindi-dev 1.8.2~201911200846~ubuntu18.04.1 armhf Instrument-Neutral Device Interface library -- development files
ii libindi1:armhf 1.8.2~201911200846~ubuntu18.04.1 armhf Instrument-Neutral Device Interface library -- shared library
root@heidenrod-obs:/home/heidenrod#


This is what I get with the Atik, no matter which exposure I use.

Astroberry Bluetooth GPS - by: tweet

$
0
0
Very happy with Astroberry - got it running on a Pi3B+ in my obsy but using it in client/servermode with Kstars/Ekos on my MacbookPro - now got a Pi4 so I can run it all standalone for outreach but having problems trying to connect an old Tom Tom GPS device to Astroberry so it can pick up date and location out in the field or at Outreach Events. Currently running Astroberry 2.0.0 - have run updates and upgrades.

Astroberry Bluetooth System Icon sees GPS device but would not connect with error 'No useable services' ...

So after lots of Googling ... on INDI site and others ...

www.raspberrypi.org/forums/viewtopic.php?t=152143 Talks about adding serial connections and rfcomm

Added --compat option to ExecStart=/usr/lib/bluetooth/bluetoothd in /etc/systemd/system/dbus-org.bluez.service because Googling says Bluez 5 needs it for old devices - raspberrypi.stackexchange.com/questions/...ch-file-or-directory

Enabled Serial Communication in raspi-config - learn.adafruit.com/adafruits-raspberry-p...bling-serial-console

Updated GPSD init script for /dev/rfcomm0 etc - As per INDI forum - See attached file.

Ran hcitool to get macaddress of TomTom BT GPS Device

Ran "rfcomm connect 0 macaddress &" and device connects to astroberry pi. Have to run it as rfcomm is no longer 'bound' (?) in some Pi OSes - bugs.launchpad.net/ubuntu/+source/linux/+bug/416056

Used cat /dev/rfcomm0 and that shows some GPS data - See attached file

However even though device now seems to be connected - Astroberry GPS does not seem to get a fix - assigned GPSD as INDI device.

Can you help?

Do I have to run this? "gpsd -b /dev/rfcomm0" - although presume INDI runs that when you set up the GPSD device using the GPSD Init file.
Do I have to 'bind' rfcomm somehow - so that it connects at boot time without having to run commands.
Maybe I am just selecting the wrong devices in Astroberry/INDI?

Thanks

Terry

Solver not moving mount enough when slewing to center target. - by: Lead_weight

$
0
0
This is happening to me a lot lately. It might be a side effect of having a 10Micron mount where it thinks it's accurately pointed to the center of a target, but it's slightly off. I have a target picked in the scheduler, and part of the initial setup is to slew to the target. It has taken 18 slew commands to move 1 arc second at a time to try and center the target. I don't suppose there is any way to nudge it to the center. The slew command to the target over and over isn't always working smoothly. This is especially the case after a meridian flip for some reason where the pointing model might not be as accurate on one side of the mount. But I don't know for sure.

.NET Indi Client - by: MikeP

$
0
0
Hello!

New here with a (hopefully) simple question.

I'm considering adding INDI support to my AllSkEye all-sky imaging application (to allow image acquisitions from a RPi connected camera). I've looked through the client tutorial but was wondering if there already is a .NET (C#) implementation I could have a look at?

Thanks!

Mike

Optical Train for KStars 4.0.0 - by: knro

$
0
0
In order to support N arbitrary cameras in Ekos, I'm beginning to toy with the idea of simplifying the system and reducing complexity.

So I'm planning to create the optical_train Git branch to test this idea. Basically, you will no longer be able to select any camera, focuser, filter wheel, rotator, or scope in Ekos. Instead when you create your equipment profile, you will be asked to create optical trains.

The equipment profile will also undergo significant changes to allow selecting multiple mounts, focusers..etc. You will no longer be limited to only a set number of devices in the profile. You can add 10 cameras if you desire so.

For most use cases, you would have at minimum the primary image train. In each train, you will be asked to select the devices in the train itself (including passive devices like focal reducers). Once the train is saved, it will be used throughout Ekos. In Capture/Focus/Guide/Align, that's the only selection you make. This would require significant re-structuring of Ekos code, which might take a year or so.

So I'm just throwing this idea out here to get your preliminary feedback on this approach and to see if there any major flaws in the idea that I perhaps overlooked.

I come back with other issues of qhy10 - by: htly9981

$
0
0
hello, I could solve former problem.

It was quite simple

I changed to the raspberry pi 4 instead of sell qhy10

there is no issue about the resolution, but I still get in trouble with other issues

first, I can't use live video in camera tap.

second I can't use whole plate and solve tap, It's all gray

I thought if it because my camera was out of focus, but it still occur when the focus is right

and I got some strange messages, about telescope and aperture

l'm a brand new guy for liunx so l took capure

what seems to be the problem?
Viewing all 15748 articles
Browse latest View live


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