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

KStars Lite 4.0 does not start - by: VTVL

$
0
0
I have not used KStars Lite for about a year. It previously worked OK with my LX90 and RPI3. Recently I added more SD memory to my Android phone (Android 6.0) The increased memory was set (formated) to be an extension of the internal. My phone still complains about not having enough free memory to install some app updates.. Although there are lest complaints than before the memory increase. So I removed a no longer wanted app and uninstalled Kstars Lite which still would not start.. Then installed it again (version 4.0 from Playstore). This version is claimed to overcome a crash on start problem.
Still no joy, The sand clock sits there for a while and then a failure to start is reported with the option to report the problem, This forum is more direct I think.

Nighscape 8300 driver - by: dirkn

$
0
0
Hi,

Ive build a nightscape 8300 driver that's still pretty 'alpha' but perfroms fan/cooler and exposure control correctly. The image saving/downloading isn't completely stable because of some USB data transfer issues.

For stability, it needs the FTDI d2xx libraries but can run with libftdi1.

Is there any intereest in this? I know the camera is discontinued and support form Celestron limited now.

It was built based on reverse-engineering the messaging from the windows driver.

I have no idea how to run the non-KAF300 version of this.

Regards,

Dirk

New Filter Wheel - Darks and Bias - by: Megiddo

$
0
0
I'm pretty excited, got my new ZWO 5-Position filter wheel. I'm using a Canon DSLR 600D, so I didn't really get it for the LRGB filters, but instead for the ability to do my Darks and Bias without having to wake up and run outside in the wee hours. :P

So far even in the daylight I'm getting no light bleeding in. I do have it on the opposite side as my open slot and I covered the others (and used black flat paint for the shinny screws inside).

The drive ASI EFW seems to be working. I even had to go to a LYFNLOVE powered 3.0 USB hub (I know, a cheapy, but I already had it) that didn't work on my RPi3, but seems to be finding everything (after a couple of tries) on the RPi4.

Changing the filter names helps a bit, kinda cool feature and of course makes sense. And when I get a narrowband Filter, I'll be able to put that in there.

Driver OnStep (LX200 like) for INDI - by: dragonlost

$
0
0
Hello.

I would like to use the project "Onstep" to control my mount (GP2 vixen). I have already built a control card and I use a card Arduino Mega 2560 (but you can also use a teensy 3.2 for improved performance).

Onstep uses language LX200:
www.stellarjourney.com/index.php?r=site/software_telescope

The developper website identifies very well the controls.
There is an ASCOM driver for Onstep and a software which exploits all the functionality that has create the developer ( "planetarium sky").

I do not need a driver who operates every possibility (driver ethernet, wifi, bluetooth and usb).

I need a driver that connects via USB and has the following functionality:

hand control:
- connection
- On set
- abort
- Parking (park, unpark and set park position)
- Tracking (on and off)

motion control:

- Motion N / S (north and south)
- Motion W / E (West, East)
- Slew rate (guide, centering, find, max)
- Slew Target
- Tracking mode (sidereal, solar, lunar, custom)
- Tracking frequency

Site management:
- As "LX200 Autostar"

Guide:
- As "LX200 Autostar"

Firmware_data:
- As "LX200 Autostar"

I try using the driver "LX200 Autostar", "LX200 Classic", "LX200 GPS". The card that connects (with sudo chmod uga+rwx /dev/ACM0). I even manage to send it to precise position. But once possible to park unpark.

But that's what does not work:

- Sends the UTC time at start
- Sends the latitude and longitude
- The "unpark" (the "park" function works)
- No button to activate the tracking
- Tracking mode does not work
- So "firmware_data", "full" does not.

If we take the driver "LX200 Autostar" should be deleted:

Hand control:
- alignment
- Use pulse cmd

- The menu "Focuser"

It must be added:
- A button on / off tracking
- A set button sets the park position = Parking position this location

This must be corrected:

Hand control:
- unpark
- Connection (wrong order for the latitude and longitude).

Motion control:
- Correct the tracking mode

Site management:
- Correct latitude and longitude control ( "*" instead of a ":")

Firmware_data:
- Correct reading of the order to "full"


To test all this it just sufficed to have an Arduino Mega and inject the code of the branch of -alpha github onstep: github.com/hjd1964/OnStep/tree/Arduino-Mega2560-Teensy3.1-Alpha

Here I hope someone can help me!
It'll be cool Indi compatible with Onstep !!!!

Afterwards we can add features but the features above sity Suffice to good use Onstep.

Thank you in advance for any help you could give me.
Where can I get a tutorial to start working on this change?

I have the basics in Python and C.

ToupTek GCMOS Driver - by: feilimb

$
0
0
Hello, I am looking into a purchasing my (first ever) guiding camera which will be used in a 50mm mini guide scope. My indi server is running on an Odroid U2 ARM device with Ubuntu Mate 16.04.

I was wondering if anyone has had any success or know of any Indi driver development for the following camera:
ToupTek GCMOS ( www.touptek.com/product/showproduct.php?lang=en&id=137 )

I have read fairly good things about them, and they use the same sensor as in the ASI120MM but are available for a lower cost.

ToupTek provide Linux drivers and an SDK (see: www.touptek.com/download/showdownload.php?lang=en&id=28 ), although their current driver appears to be for x86 / x86_64 architectures so I'm not sure whether ARM support is out of the question (for eg. Raspberry Pi, Odroid variants).

Otherwise, can anyone recommend an alternative guiding camera which has Indi driver support on ARM architectures (Raspberry Pi & Odroid) ?

Many thanks for any advice!

New INDI Atik driver - Feedback requested - by: knro

$
0
0
Good news everyone! I just finished pushing a new INDI Atik driver. This is the new INDI ATIK driver based on an open-source INDI driver (the library part is still proprietary). So the good thing is that it will be in the PPA and there don't be anymore linking issues. It should be available in the INDI Nightly repo later tonight. Let me know if you have any problems with it. Treat it as a BETA driver.

Indi driver for SkyFi module - by: giorgio_ne

Kstars compiled on rpi4 with raspbian buster... - by: AstroNerd

$
0
0
Hello all,
Has anyone managed to get Kstars compiled on the new rpi4 with raspbian buster, I have got Indi on and working well, but after installing Kstars from git, it has errors, just not sure if it’s me of whether it’s happened during the compiling install...need to know whether to keep trying or whether I am wasting my time..
:)

Failure to take exposure with Starlight SXVR-M25C - by: bluthen

$
0
0
I've really enjoyed using INDI, well done!

The astronomy club I'm in recently got a used Starlight Express camera. The SXVR-M25C. However I am never able to get an exposure. When I try to take a 1 second exposure for example it just hangs there forever.

I seems to connect and it looks like it gets info from the camera. But when I expose I just never get the image. I see a lot of these in the logs

INDI Server: "2019-09-24T03:02:57: Driver indi_sx_ccd: sxReadPixels: libusb_control_transfer -> LIBUSB_ERROR_TIMEOUT"

I have it externally power, I've tried replacing the USB cable and also tried with the cooler on and off in the configuration.

Any help would be appreciated.

File Attachment:

File Name: log_21-59-40.txt
File Size: 50 KB

EKOS is missing buttons in the lastest release - by: AradoSKYindi

$
0
0
Hello,

When using EKOS, the minimize and full screen buttons are missing. This caused the Main page to hide the Indy page. To see the INDY page, EKOS has to be shutdown. To stop INDI, EKOS has to be reopened. Thank you.

Imaging with SER video - bad result - PIPP and Autostakkert show strange frames - by: maxthebuilder

$
0
0
Hello,
Tonight tried to shoot the Moon as SER video capture.
SM 1.4.3 RPI4 with yesterday's updates (KS 3.3.7)
ZWO ASI294MC
0 Gain
16 bit
0.007 sec/frame.

Looked nice in Ekos (in Live View)
Histogram was going up to 30000, not over-saturated.

Tried to open in PIPP. PIPP said there were no frames.
Tried to open in PIPP SER viewer. It said there's a problem with the file and offered to fix it.
Agreed to fix. Below is the result (single frame).
(Autostakkert produces the same result but doesn't complain).


Here's file info reported by ser viewer before fixing:


and after fixing:


First time using SER...
Any idea?
Has to be 8 bit? (Edit: same with 8 bit)

Thanks!

Auto Focus in Ekos always crashes - by: arminpro

$
0
0
Hi,

I am using the Auto Focus Module in Ekos with Stellar Mate with Rigel Focus device.
The first auto focus is working, but trying a second attemp it crashes.
Then Ekos crashes whatever i am doing in the focus module.
The only thing I can do is to focus manually in or out and capture with the capture module, but not with the focus module, since then it crashes.

Can anyone help?

Regards, Armin

[SOLVED] Unable to build 3rd party indi drivers in raspbian buster - by: sywong2000

$
0
0
Hi everyone,
I was trying to build the 3rd party indi drivers in raspbian buster but I've encounter following errors:
<strong>error: ‘ccdBufferLock’ was not declared in this scope</strong>



Can somebody help?


pi@raspberrypi:~/Projects/build/indi-atik $ make -j4
[ 25%] Building CXX object CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o
[ 75%] Built target indi_atik_wheel
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp: In member function ‘bool ATIKCCD::grabImage()’:
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:10: error: ‘unique_lock’ is not a member of ‘std’
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~~~~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:10: note: ‘std::unique_lock’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:30:1:
+#include <mutex>

/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:10:
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~~~~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:27: error: ‘mutex’ is not a member of ‘std’
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:27: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
<strong>/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:40: error: ‘ccdBufferLock’ was not declared in this scope
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~~~~~~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:34: error: ‘guard’ was not declared in this scope
std::unique_lock<std::mutex> guard(ccdBufferLock);</strong>
</strong> ^~~~~
make[2]: *** [CMakeFiles/indi_atik_ccd.dir/build.make:63: CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:110: CMakeFiles/indi_atik_ccd.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
pi@raspberrypi:~/Projects/build/indi-atik $

PAA & CEM25p unexpected behavior - by: khobar

$
0
0
The previous two nights I've been using my DIY GOTO LX70 without a hitch with Ekos, etc. Tonight I wanted to capture M31 with my CEM25p and compare the results. I can't get past polar alignment. This is on a rp4 with Stellarmate OS.

Basically, when I click "Start" it takes a pic, solves, slews, and right when it gets to 30 degrees, it beeps and attempts to park. I have tried about 10 times now, making sure GPS location time date etc was ok. It just is not cooperating.

What am I missing? Thanks!

Scope hitting pier - by: universalmaster

$
0
0
Hi!

I use an eq6 mount with the eqmod driver . Go-to and plate solve now seems ok. But the scope (Newton) is in many cases hitting the pier. For example, I park the scope on the west pier side. If I then unpark and go-to an object quite high in the sky but west of the meridian, the scope will stay on the west side and possibly hit the pier. The counter weight shaft is in this case pointing a bit up. Shouldn't the mount move the scope to the east side in this case?
Could eqmod somehow think the mount is already on the east side? If yes, how do I tell it that it is not?

Best regards
Søren

Starting compiled Ekos generates a segfault in Buster - by: elakrab

$
0
0
Hi,

I just finished compiling indi and kstars in Raspbian Buster. Kstars works fine until I start Ekos, which triggers a segfault. Has anyone experienced the same? This is the log I get in the terminal...

<code>libEGL warning: DRI2: failed to authenticate
org.kde.kstars: Welcome to KStars 3.3.7
org.kde.kstars: Build: 2019-10-13T17:07:12Z
org.kde.kstars: OS: "debian"
org.kde.kstars: API: "arm-little_endian-ilp32-eabi-hardfloat"
org.kde.kstars: Arch: "arm"
org.kde.kstars: Kernel Type: "linux"
org.kde.kstars: Kernel Version: "4.19.73-v7l+"
org.kde.kstars: Qt Version: 5.11.3
org.kde.kstars: Processing "unnamedstars.dat" , HTMesh Level 3
org.kde.kstars: Sky Mesh Size: 512
org.kde.kstars: Loaded DSO catalog file: "unnamedstars.dat"
org.kde.kstars: "Star HD20,794 not found."
org.kde.kstars: "Star HD98,230 not found."
File opened: "/usr/share/kstars/ngcic.dat"
org.kde.kstars: Loading NGC/IC objects
File opened: "/home/pi/.local/share/kstars/comets.dat"
org.kde.kstars: "Object named NGC 6050A not found"
static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
** Message: 18:49:34.679: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
glibc >= 2.1 detected. Using GNU extension sincos()
File opened: "/home/pi/.local/share/kstars/comets.dat"
File opened: "/home/pi/.local/share/kstars/asteroids.dat"
org.kde.kstars.ekos: "Starting INDI services..."
org.kde.kstars.ekos: "INDI services started on port 7624."
org.kde.kstars.ekos: Ekos received a new device: Focuser Simulator
org.kde.kstars.ekos: Ekos received a new device: CCD Simulator
org.kde.kstars.ekos: Ekos received a new device: Telescope Simulator
org.kde.kstars.ekos.focus: "Idle."
org.kde.kstars.ekos: "Focuser Simulator focuser is online."
org.kde.kstars.ekos.align: "Idle."
org.kde.kstars.ekos.align: "Detected Astrometry.net version 0.78"
org.kde.kstars.ekos: "CCD Simulator is online."
Segmentation fault
</code>

A few issues - by: Twistys

$
0
0
There are a few issues that I have been having with ekos that I have been working on.
Attached equipment is below:
EQ6-R pro with EQMOD
Canon EOS Rebel T6 imaging camera
ZWO ASI290mm mini guide camera
USB GPS (I am not near a time zone change for this to be an issue, KStars & Ekos are set to update from USB GPS)

The biggest issue is that the meridian flip function reports "waiting" but never actually performs the flip. I know that the function is set to wait for the current capture to complete, then perform the flip. In the attached logs, the flip is supposed to occur around 1am. I have included all modules that I am using as when I was doing some testing during the day with ccd and guiding simulator, the mount would perform a meridian flip. I have an EQ6R-pro with EQMOD. The way I have gotten around this issue is watching the failure happening, parking the mount and restarting the scheduler. The mount then slews to the correct side and continues tracking fine.

File Attachment:

File Name: log_23-35-45.zip
File Size: 5,374 KB


The next issue, which I do not currently have logs for is for the scheduler not starting the job process when I initialize the scheduler earlier on in the day and it is waiting for twilight. I adjusted the setting for pre-emptive shutdown to be longer than 2 hours but when the time comes for the job to start, nothing happens and the scheduler still reports "waiting for job start time".

When I open up the log directory from ekos to verify the destination, another copy of KStars is started and logging starts on that instance.

Post your INDI Setup! - by: knro

$
0
0
So while the details can be found in Ikarus Observatory site, I'll kick start this thread with my setup:



Odroid XU4 / RPI2 along with gigabit switch, remotely controlled power and digital relay.



1. Orion EON 120mm on HEQ5,
2. QSI 583wst CCD
3. Starlight Xpress Lodestar
4. MoonLite Focuser
5. FlipFlat



Davis Instruments Pro Weather Station



Blurry image of opened roof. The roll-off roof is completely automated from Ekos.

Raspberry Pi 4 vs Pi 3 performance test - by: han.k

$
0
0
Maybe of interest, a practical performance test between the Raspberry Pi 3 and Pi 4

Both system where running Raspbian Buster. The camera an ASI1600-MM Cool was connected using an USB 3.0 cable. The imaging program was CCDCiel and ASTAP was installed as the solver as described here . PHD2 was installed for guiding but not used in this test.



The results show that the Pi 4 is in average twice as fast as the Pi 3. A lot of time is lost by downloading and saving the image. A class 10 memory card was installed.
The time lost is the time between the exposures for downloading the image via USB and saving it to the memory card. So in the Pi 4 if you operate the ASI1600 camera in bin 2x2 mode there is 2.5 seconds lost between the exposures. That's pretty good for deep sky imaging.

The solving time is the time required for plate solving the image.

Han

Using KStars Lite for Astrophotography - by: Sathyakumar

$
0
0
I am able to control my mount using KSTars Lite. Now, I would like to use it for astrophotography. That is, sequencing a set of image capture/calibration frames and guiding. Anyone have any ideas?
Viewing all 14131 articles
Browse latest View live