Stephen Wong replied to the topic 'Slow RPI3 Offline Platesolving' in the forum. 2 weeks ago

OK. I've located the problem:

1. I did messed up the FOV - Thanks wvreeven
2. EKOS is not passing parameters to solve-field (well at least at "Load & Slew"). I did point the telescope simulator close to the targets, specifies the FOV. And then I've found from the log that the -3, -4, -5 params are not passed - this caused the solver to do a blind solve. In the options I did find the params are correct. Just somehow it's not being sent to the solve-field command. See screen cap. If I run the same command myself at the shell, by adding the -3, -4, -5, the solver is able to get the result in 90 seconds.

Ubuntu 16.04 on RPI 3
Kstar version 2.9.6
KDE framework 5.18.0

Read More...

Stephen Wong created a new topic ' Slow RPI3 Offline Platesolving' in the forum. 2 weeks ago

Hi
I was trying to use the offline platesolving (astrometry 0.67) with my Raspberry Pi 3 on ubuntu 16.04. I've found the offline platesolver is very very slow and run into timeout. I used a FITS file captured with my Atik 490EX (with Tak 85ED with 0.67 reducer) and load it with "Load & Slew" to test. See below logs.

If I use the online platesolver that's no problem. I saw from other posts saying a RPI3 usually takes 30-60 secs to solve, if it's offline. But you can see from the log it takes a lot of time on certain steps. Is it normal?

2018-10-31T22:52:40 Solver aborted after 360 seconds
2018-10-31T22:49:05 Field 1 did not solve (index index-4209.fits, field objects 1-10).
2018-10-31T22:49:04 Field 1 did not solve (index index-4210.fits, field objects 1-10).
2018-10-31T22:49:04 Field 1 did not solve (index index-4211.fits, field objects 1-10).
2018-10-31T22:48:09 Reading file "/home/ubuntu/Light_005.axy"...
2018-10-31T22:48:09 Solving...
2018-10-31T22:48:04 Reading sort column "FLUX"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
2018-10-31T22:48:00 simplexy: found 2131 sources.
2018-10-31T22:46:48 Extracting sources...
2018-10-31T22:46:41 Reading input file 1 of 1: "/home/ubuntu/Light_005.fits"...
2018-10-31T22:46:41 /usr/bin/solve-field -O --no-plots --no-verify --resort --no-fits2fits --config /etc/astrometry.cfg -W /tmp/solution.wcs /home/ubuntu/Light_005.fits
2018-10-31T22:46:41 Starting solver...
2018-10-31T22:46:41 Solver iteration #1

Read More...

Assuming I have captured a FITS file on disk. Can I specify the CCD simulator to load the FITS as simulate the image capturing?
What I'm trying to do is to test the offline platesolving in EKOS.
I have very limited time in image capturing session on the field, so I just want to test the offline platesolving, making sure it would work when I'm on the field.

Thanks!

Read More...

Stephen Wong replied to the topic 'KStars icon missing in my LXDE environment.' in the forum. 8 months ago

I have the same issue
I am using Raspbian and I build the Kstars myself from the pi3.

The icons are critical to me. When I focus using the focus frame, I need to zoom in/out, and enable/disable the star circles. Now the screen shows the "text" on the buttons, but the window is not large enough to display all the text. Meanwhile if it's the icon, it's a small square box which I can see the icons without problems.

Stephen

Read More...

Stephen Wong replied to the topic 'Unable to zoom-in (above 100%) in the focusing module?' in the forum. 8 months ago

yes I saw that button, and able to switch it off. Yet I do this in a separate ubuntu, not raspbian. Anyway issue is resolved. Thank you!

Read More...

Stephen Wong replied to the topic 'Unable to zoom-in (above 100%) in the focusing module?' in the forum. 8 months ago

No.
But it turns out I'm suffering from some other problems in the raspbian. I switched to ubuntu and update to the latest version and able to get the zoom working.

Read More...

Stephen Wong created a new topic ' Unable to zoom-in (further) in the focusing module?' in the forum. 8 months ago

Hi,

I'm using Kstars 2.9.1 in Raspbian. I've found that in the focusing module, I cannot zoom in beyond 100%. e.g. I can't do 120% or 150% in the framing setup.
Is this normal?

Plus I use a Bahtinov mask to focus, which I only need the framing and zoom to work. I do not need the star detection and FWHM. I can see the EKOS always try to detect the stars, and draw circles around them. Can I disable the drawing of such circles?

Stephen

Read More...

Stephen Wong replied to the topic 'My Raspberry Pi 3 Setup' in the forum. 10 months ago

Well I'm living in Hong Kong. Me and my friends mostly heads to the dam at the east side which is a protected area that only allows public transport (e.g. taxi) to get in. Private cars are not allowed unless there's a permit. So every time we have to carry like 10-20kg of equipment and get on a taxi and then walk for 800m slope to get to the area. So we have to think of different ways to lower the weight of the equipment. We also have to think of how to set up as quick as possible as we do not have much clear time during the night.

Read More...

Stephen Wong replied to the topic 'Indi on the rocks (a Rock64 to be exact)' in the forum. 10 months ago

Hi Wim,
May I ask the fastest FPS (say certain resolution like 640x480) you can achieve on the rock64 usb3?
Thanks
Stephen

Read More...

Stephen Wong replied to the topic 'Indi on the rocks (a Rock64 to be exact)' in the forum. 10 months ago

wimvb,
Try upgrading the firmware of ASI120 from ASI website. That solves my problem.
What I encountered was, I was on a Pi3, having one SD card with ubuntu installed, and another one with raspbian.
The ubuntu works fine with the ASI120mm (usb2)
but Raspbian unable to connect.
Then I go upgrade the firmware.. then works fine in both OS
Stephen

Read More...

Stephen Wong replied to the topic 'indi_asi_ccd crashed when start capturing for ASI ZWO 183MM Pro' in the forum. 10 months ago

unfortunately it's a 32-bit. if there's anything I can do to get the debug info please let me know

uname -m
armv7l

Read More...

Stephen Wong replied to the topic 'indi_asi_ccd crashed when start capturing for ASI ZWO 183MM Pro' in the forum. 10 months ago

I'm capturing RAW with max resolution. The OS is a ubuntu 16.04 in RPi 3. I think it's 64bit and I'll have to recheck later tonight to make sure. I did switched on the Debug in the EKOS but all it captures was just a few lines.

If you can get me a debug version of 64Bit I can certainly put this and run the test and send you back the Debug info. Thank you.

Read More...

Stephen Wong created a new topic ' indi_asi_ccd crashed when start capturing for ASI ZWO 183MM Pro' in the forum. 10 months ago

EKOS was able to connect to the ASI ZWO 183MM Pro.
But crashed on Preview or Capturing... anybody help? Here's the log, see below in RED



org.kde.kstars.indi: INDI: Starting local drivers...
org.kde.kstars.indi: Starting INDI Server: ("-v", "-p", "7624", "-m", "100", "-f", "/tmp/indififo332d64f8") -f "/tmp/indififo332d64f8"
org.kde.kstars.indi: INDI Server Started? true
org.kde.kstars.indi: INDI: INDI Server started locally on port 7624
org.kde.kstars.indi: Starting INDI Driver "indi_asi_ccd"
org.kde.kstars.indi: Adding managed driver "ZWO CCD"
org.kde.kstars.indi: INDIListener: Adding a new client manager to INDI listener..
org.kde.kstars.indi: INDI: Connecting to local INDI server on port 7624 ...
org.kde.kstars.indi: INDI server connected.
org.kde.kstars.indi: Connection to INDI server is successful
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: startup: /usr/bin/indiserver -v -p 7624 -m 100 -f /tmp/indififo332d64f8 "
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: listening to port 7624 on fd 3"
org.kde.kstars.indi: INDI Server: "FIFO: start indi_asi_ccd"
org.kde.kstars.indi: INDI Server: "FIFO: Starting driver indi_asi_ccd"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: pid=4146 rfd=4 wfd=7 efd=8"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Client 5: new arrival from 127.0.0.1:47212 - welcome!"
org.kde.kstars.indi: INDI Server: ""
org.kde.kstars.indi: Received new device ZWO CCD ASI183MM Pro
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:09:51: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY"
org.kde.kstars.indi: INDI Server: ""
org.kde.kstars.indi: INDIListener: New device ZWO CCD ASI183MM Pro
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CONNECTION >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < DRIVER_INFO >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < DEBUG >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < SIMULATION >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CONFIG_PROCESS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < ACTIVE_DEVICES >
org.kde.kstars.ekos: 1 devices connected out of 1
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_EXPOSURE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_ABORT_EXPOSURE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_FRAME >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_BINNING >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < FITS_HEADER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_TEMPERATURE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_INFO >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_COMPRESSION >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD1 >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_FRAME_TYPE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_FRAME_RESET >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_RAPID_GUIDE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < TELESCOPE_TYPE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < WCS_CONTROL >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < UPLOAD_MODE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < UPLOAD_SETTINGS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_VIDEO_STREAM >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < STREAM_OPTIONS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < FPS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < RECORD_STREAM >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < RECORD_FILE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < RECORD_OPTIONS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_STREAM_FRAME >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_STREAM_ENCODER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_STREAM_RECORDER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_COOLER_POWER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_COOLER >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_CONTROLS >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_CONTROLS_MODE >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < CCD_VIDEO_FORMAT >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < DEBUG_LEVEL >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < LOGGING_LEVEL >
org.kde.kstars.indi: < ZWO CCD ASI183MM Pro >: < LOG_OUTPUT >
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] Toggle Debug Level -- Driver Debug "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] Toggle Logging Level -- Driver Debug "
org.kde.kstars.ekos.capture: Preparing capture job "Light" for execution.
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] ASIGetExpStatus failed (0). Restarting exposure... "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] ASIGetExpStatus failed (0). Restarting exposure... "
org.kde.kstars.indi: ZWO CCD ASI183MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
*** stack smashing detected ***: terminated
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: stderr EOF"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: restart #1"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: pid=4165 rfd=4 wfd=8 efd=9"
org.kde.kstars.indi: INDI Server: "Child process 4146 died"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME"
org.kde.kstars.indi: INDI Server: "2018-01-07T13:10:16: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY"
org.kde.kstars.indi: INDI Server: ""
org.kde.kstars.indi: INDI driver "indi_asi_ccd" crashed!

Read More...

Stephen Wong replied to the topic 'My Raspberry Pi 3 Setup' in the forum. 10 months ago

I got a LEGO case for my Rpi and with a piece of LEGO attached to a case of 5V lithium battery outfit, I can attach the RPi to the battery. Then mount it with a special made saddle on the counterweight side. The saddle also allows me to mount a large 12V lithium battery so I don’t need to carry a counterweight at all during the image session.

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!