Sergio replied to the topic 'Import masters in Dark library?' in the forum. 3 months ago

Hi there,

just if anyone is interested: I used this bash script (on Ubuntu Bionic) to import a (master) dark to the Darks Library, following Jasem's tip of handling directly the sqlite database. Sorry, no warranty provided.

It assumes that the FITS file has some keywords (INSTRUME, XBINNING, YBINNING, EXPTIME) with the correct values (and that it has the correct bit depth, etc.), so you only have to input the path to the filename, and the temperature value (my guide camera doesn't provide it). Copy the code below and save with filename import-dark.sh. You should then give execution permission to the file: $ chmod u+x import-dark.sh

To import a dark: $ <path.to>/import-dark.sh <filename> <temperature>

After importing you may have to hit "Refresh" on the Dark Library configuration page on KStars to actually see the new row.

Hope it helps.

#!/bin/bash
#
# Requires package 'sqlite': $ sudo apt install sqlite
# Requires package 'astropy-utils': $ sudo apt install astropy-utils
# Requires 'readlink -e' command


if [[ -z "$1" || -z "$2" ]] ; then
  echo "Usage: import-dark.sh <filename> <temperature>"
  exit 1
fi

TIMESTAMP=`date +"%Y-%m-%d %H:%M:%S"`
echo "Timestamp: $TIMESTAMP (now)"

TEMP=$2
echo "Temperature: $TEMP (ºC, provided as argument)"

SOURCE=$(readlink -e "$1")
BASENAME=$(basename "$1")
FILENAME="$HOME/.local/share/kstars/darks/$BASENAME"
echo "Copying $BASENAME to $FILENAME..."
cp "$SOURCE" "$FILENAME"
echo "Reading headers of file $FILENAME..."
declare -a FITSKEYS
readarray -t FITSKEYS <<< "$(fitsheader -e 0 -t ascii.csv -k INSTRUME -k XBINNING -k YBINNING -k EXPTIME "$FILENAME" | cut -f 4 -d , | tail -n +2)"
CCD="${FITSKEYS[0]}"
BINX="${FITSKEYS[1]}"
BINY="${FITSKEYS[2]}"
DURATION="${FITSKEYS[3]}"
echo "  CCD:       $CCD"
echo "  BinX:      $BINX"
echo "  BinY:      $BINY"
echo "  Duration:  $DURATION (s)"

SQL="insert into darkframe(ccd, chip, binX, binY, temperature, duration, filename, timestamp)  values('$CCD', '0', '$BINX', '$BINY', '$TEMP', '$DURATION', '$FILENAME', '$TIMESTAMP')"
# echo "Importing dark..."
echo "Executing '$SQL'..."

sqlite3 ~/.local/share/kstars/userdb.sqlite "$SQL" && echo "Done."
exit $?


Read More...

Sergio created a new topic ' Ekos tries to offset focus when no focuser defined in profile' in the forum. 3 months ago

Hi everyone. I have two profiles in Ekos:

- telescope #1 with focuser (imager, guider, etc)
- telescope #2 without focuser

For the first profile, I've defined filter offsets for convenience. But when I use the second profile, if I change filters in capture module and start an exposure, Ekos seems to try to apply the offset configuration. As no focuser is available, Ekos keeps waiting ("Changing focus offset by n steps" message) and the exposure is not started. At that point I have to cancel the exposure and try again, this second time Ekos doesn't see a filter change so the exposure is initiated as expected.

Thanks

Read More...

Sergio created a new topic ' Import masters in Dark library?' in the forum. 3 months ago

Hi everyone. Is there any way (or trick) to import my master darks into the Dark Library? E.g., my guider camera doesn't have a shutter and I find uncomfortable to manually have to cover the guidescope every once in a while (sometimes in the middle of a guiding session, when temperature change exceeds the threshold, I guess).

Thanks!

Read More...

Sergio replied to the topic 'Moravian G2-8300FW getting libusb_bulk_transfer_failed' in the forum. 5 months ago

If anyone is interested on this: the discussion follows on github (issue 580) .

Read More...

Sergio created a new topic ' Moravian indi_mi_ccd_usb Cannot set read-only property CCD_GAIN' in the forum. 6 months ago

Hi everyone,

I noticed what it seems a small glitch in Ekos Focuser tab, whenever I start a capture o begin an autofocus loop with my MI G2-8300FW, I see these messages in the log:

[2018-04-18T14:31:54.202 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2018-04-18T12:31:54: Driver indi_mi_ccd_usb: indi_mi_ccd_usb dispatch error: Cannot set read-only property CCD_GAIN"

I noticed there is in fact an editable "Gain" box in the focuser tab (which I'm not touching), but my Moravian camera don't accept this setting. Previous versions of the driver didn't show the gain box.

Just to let you know.
Thanks in advance

Read More...

Sergio created a new topic ' Moravian G2-8300FW getting libusb_bulk_transfer_failed' in the forum. 6 months ago

Hi everyone. I'm facing random issues with my MI G2-8300FW, hope you can help me.

When I'm imaging (or focusing) sooner o later I start to get errors from indi_mi_ccd_usb driver ("[ERROR] Getting voltage failed: Camera is not connected. ", "[ERROR] Getting image ready failed: Camera is not connected. ", and so on). At this point the only thing I could do is shutdown the indi server and start it again.

Here is the relevant section of the log, where you can see that the driver is reporting an error on libusb_bulk_transfer failed():

[2018-04-18T13:50:40.138 CEST INFO ][   org.kde.kstars.ekos.capture] - "Capturing image..."
[2018-04-18T13:50:41.080 CEST DEBG ][           org.kde.kstars.indi] - MI CCD G2-8300 : "[DEBUG] Taking a 1.000 seconds frame... "
[2018-04-18T13:50:41.121 CEST DEBG ][           org.kde.kstars.indi] - MI CCD G2-8300 : "[DEBUG] Exposure in progress: Time left 0.97s "
[2018-04-18T13:51:42.218 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2018-04-18T11:51:42: Driver indi_mi_ccd_usb: [gxccd] error: libusb_bulk_transfer failed(): cmd: 0x11, write: false, ret: -7, Operation timed out, transferred: 0, in_len: 2, out_len: 5"
[2018-04-18T13:51:42.219 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2018-04-18T13:51:42.220 CEST INFO ][           org.kde.kstars.indi] - MI CCD G2-8300 :  "[ERROR] Getting voltage failed: Camera is not connected. "
[2018-04-18T13:51:42.222 CEST INFO ][           org.kde.kstars.indi] - MI CCD G2-8300 :  "[ERROR] Getting image ready failed: Camera is not connected. "
[2018-04-18T13:51:43.222 CEST INFO ][           org.kde.kstars.indi] - MI CCD G2-8300 :  "[ERROR] Getting temperature failed: Camera is not connected. "
[...repeats...]

I'm running indiserver and kstars/ekos (latest versions) under Ubuntu Mate 17.10 (up to date) on an Intel NUC6CAYH (BIOS up to date). USB controller seems to be using Linux 4.13.0-38-generic xhci-hcd driver.

dmesg output shows two warnings about "invalid maxpacket" upon plugging (not sure if it's related to the issue):
--- inmediately after I plugged the camera: ---
[Wed Apr 18 13:45:10 2018] usb 1-2: new high-speed USB device number 4 using xhci_hcd
[Wed Apr 18 13:45:10 2018] usb 1-2: New USB device found, idVendor=1347, idProduct=0406
[Wed Apr 18 13:45:10 2018] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
--- when I start indiserver ---
[Wed Apr 18 13:46:15 2018] usb 1-2: USB disconnect, device number 4
[Wed Apr 18 13:46:16 2018] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[Wed Apr 18 13:46:16 2018] usb 1-2: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[Wed Apr 18 13:46:16 2018] usb 1-2: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[Wed Apr 18 13:46:16 2018] usb 1-2: New USB device found, idVendor=1347, idProduct=0406
[Wed Apr 18 13:46:16 2018] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Wed Apr 18 13:46:16 2018] usb 1-2: Product: G2-1600
[Wed Apr 18 13:46:16 2018] usb 1-2: Manufacturer: Moravian Instruments
[Wed Apr 18 13:46:16 2018] usb 1-2: SerialNumber: G2-1600-0001
--- when I shut down indiserver: ---
[Wed Apr 18 13:53:52 2018] usb 1-2: USB disconnect, device number 5

Tests I've done:
- Changed the usb cable. Same result.
- Tested the camera (with original cable) in a windows box. No issues found (tested through six hours of continuous shooting).

I didn't experience any of these problems before on my previous astro box, which was based on a RPi3 but I was running earlier versions of indi and moravian driver.

Any ideas? Thanks in advance.
Sergio

Read More...

Sergio replied to the topic 'ASI120MM on RPi3' in the forum. 1 year ago

Hi Piero,

I may be wrong, but looking at the source code of lin_guider it seems that it uses the SDK "ASIStartVideoCapture" function instead of "ASIStartExposure" , which is the one used in the INDI driver. See asi_core::start_exposure() in lin_guider/src/video_dev/asi_core.cpp and ASICCD::StartExposure in indi/3rdparty/indi-adi/asi_ccd.cpp.

The SDK manual, describing ASIStartExposure says: "Usage: start a single snap shot. Note that there is a setup time for each snap shot, thus you cannot get two snapshots in succession with a shorter time span that these values."

Also, Yang from ZWO confirmed to me that the SDK calls to libusb for a device reset on each exposure ( zwoug.org/viewtopic.php?f=17&t=6901&sid=...7cb64f649d24e#p12521 ); that seems to explain the message we see on dmesg and the "setup time" mentioned on the SDK manual (and hence, the relatively slow performance).

Not very helpful, I guess, just to let you know.

Best Regards.
Sergio

Read More...

Sergio created a new topic ' ASI120MM on RPi3' in the forum. 2 years ago

Hi everyone, I'm new on this forum and Ekos/INDI, need your help with this one.

I saw in other thread that Jasem, maybe others, has indiserver hosted on a RPi3, as I do, and did some testing with an ASI120MC.

I'm struggling with an ASI120MM and wonder which specific configuration you have on your RPi3. Would you point me the exact version of these? (in parenthesis is what I have)

  • distro (Raspbian Jessie; last apt-get update on Feb 28th)
  • kernel (4.9.13-v7+)
  • indilib (1.4.1, compiled from git sources as of Feb 28th)
  • indi-asi (0.5, compiled from git sources as of Feb 28th, but I manually replaced LibASICamera2.lib (SDK v0.6.0110) with the one I extracted from SDK V0.4.0929 --downloaded directly from ZWO--)
The reason I replaced the SDK embedded in indi-asi is because this driver got stuck (but didn't crash) at "StartExposure->setexp : ..." after some exposures, and I saw these messages on dmesg:
[27070.448662] usb 1-1.4: new high-speed USB device number 5 using dwc_otg
[27070.699494] usb 1-1.4: New USB device found, idVendor=03c3, idProduct=120a
[27070.699506] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27070.699514] usb 1-1.4: Product: ASI120MM
[27070.699522] usb 1-1.4: Manufacturer: ZWOptical company 
[27070.699529] usb 1-1.4: SerialNumber: 00000
[48180.056128] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
[48181.566120] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
[48183.306141] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
... ("reset" message repeats on each exposure)

Don't you see these messages on your RPi3?

With SDK versions 0.6.0103 and 0.5.1215, I get this very same results as with 0.6.0110, so I kept rolling back to V0.4.0929, when things improved, as the "reset" messages no longer showed, and testing with Focus->Framing kept running for a higher number of exposures. But eventually it fails again at "StartExposure", sometimes after 45 minutes, sometimes after five hours. Not good for guiding.

I want to thank everyone involved in Ekos/Kstars/INDI for their amazing work.

Thanks in advance,
Sergio

Read More...

Sergio replied to the topic 'ASI120MM on RPi3' in the forum. 2 years ago

I compiled the driver from git, which already has SDK v0.6.0110 as Jasem commented in his commit (also checked by binary comparison).
Thanks.

Read More...

Sergio replied to the topic 'ASI120MM on RPi3' in the forum. 2 years ago

It seems that max_usb_current=1 has no effect on RPi3, it is hard-wired to provide 1.2A max.
www.raspberrypi.org/forums/viewtopic.php?p=930695#p930695
www.raspberrypi.org/help/faqs/#powerReqs
Anyway I also ran a test with max_usb_current=1 before finding that information and got the same results as I reported on the opening post.

Read More...

Jasem Mutlaq thanked Sergio in topic ASI120MM on RPi3 2 years ago
Sergio replied to the topic 'ASI120MM on RPi3' in the forum. 2 years ago

A last update, as I've repeated the test (Focus -> Framing) several times. results summarize as follows:

* exposure < 1 second: get frequent ASIGetExposureStatus failed (0) (every other exposure if I set 0.5 seconds) , first retry seems to work. I guess any momentary load on the system could lead to reach max retries and then failure. I guess this is not surprising as long as the SDK is resseting the USB communication on each exposure.
* exposure >= 1 second: no fails whatsoever for 8-9 hours on a freshly booted RPI. But in one test I did without rebooting before starting the Focus->Framing sequence, it "freezed" (no response to StartExposure, as described in the opening post) after 9 hours.

So these results may be considered just enough for guiding, provided that the RPi is booted before each night session. But also may be considered as enough reason to return the camera to the provider.

Unfortunately I didn't have yet the opportunity to perform an actual test guiding and imaging due to bad weather.

Read More...

Sergio replied to the topic 'eqmod died when saving configuraton for the first time' in the forum. 2 years ago

Great, thanks Jasem

Read More...

Sergio replied to the topic 'ASI120MM on RPi3' in the forum. 2 years ago

Well, yesterday it kept running until I stopped it, after more than 8 hours without issues. I'm waiting for clear skies to test again along with the other devices (main imager, focuser, mount). Meanwhile, I'll run a test again to see if this result is repeatable.
dmesg is flooded with usb reset messages, but according to Yang from ZWO ( zwoug.org/viewtopic.php?f=17&t=6901 ), they are "normal", as a reset is requested by the SDK on each exposure (but it seems to me some rough workaround).
I'm not sure about the differences between Raspbian Jessie and Ubuntu MATE regarding USB management... maybe different kernel compile options.
All in all, this is not reassuring at all, any update (kernel, sdk, etc) could break it.

Read More...

Sergio created a new topic ' eqmod died when saving configuraton for the first time' in the forum. 2 years ago

Hi,

I started recently with Ekos/INDI, and I want to report a problem I had with indi_eqmod_telescope on its first use.

Scenario: INDI compiled from sources (yesterday), started indiserver with indi_eqmod_telescope, then from Ekos 'Start INDI'. Before I could connect to the mount, I had to configure the device port, so I went to the INDI control panel, EQMod tab, click on Debug and check Driver Debug, then I set the correct device port and click 'Set', then 'Save'.

The UI keeps a yellow light at "Saving configuration" message on the control panel console.

In the console where I started indiserver, I got this:

2017-03-06T09:37:17: Client 0: new arrival from 192.168.0.7:45538 - welcome!
Child process 1944 died
2017-03-06T09:39:51: Driver indi_eqmod_telescope: stderr EOF
2017-03-06T09:39:51: Driver indi_eqmod_telescope: restart #1
2017-03-06T09:39:51: Driver indi_eqmod_telescope: pid=1969 rfd=8 wfd=16 efd=17
2017-03-06T09:39:51: Driver indi_eqmod_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2017-03-06T09:39:51: Driver indi_eqmod_telescope: snooping on GPS Simulator.TIME_UTC
2017-03-06T09:39:51: Driver indi_eqmod_telescope: snooping on Dome Simulator.DOME_PARK
2017-03-06T09:39:51: Driver indi_eqmod_telescope: snooping on Dome Simulator.DOME_SHUTTER
2017-03-06T09:39:51: Driver indi_eqmod_telescope: EnumeratePlugins - found plugin SVD Math Plugin

(I've seen a similar report before on the forum but it seemed it was related to a problem with the PPA)

Upon error, I noticed that the configuration files appeared on the .indi folder, but they are empty:

aristarco@messier:~/.indi$ ls -la EQMount*
-rw-rw-r-- 1 aristarco aristarco 0 mar 6 10:39 EQMod Mount_config.xml
-rw-rw-r-- 1 aristarco aristarco 0 mar 6 10:39 EQMod Mount_config.xml.default

Log file only says:
aristarco@messier:~/.indi$ cat logs/2017-03-06/indi_eqmod_telescope/indi_eqmod_telescope_09\:37\:10.log
INFO 136.358250 sec : Session log file /home/aristarco/.indi/logs/2017-03-06/indi_eqmod_telescope/indi_eqmod_telescope_09:37:10.log
DEBUG 154.664311 sec : ProcessTextProperties - name(DEVICE_PORT)
DEBUG 161.028627 sec : ProcessSwitchProperties - name(CONFIG_PROCESS)
DEBUG 161.028791 sec : ProcessSwitchProperties - name(CONFIG_PROCESS)


Having a look a the code, I decided to comment these two lines out in indi/3rdparty/indi-eqmod/eqmod.cpp :

aristarco@messier:~/indi/3rdparty/indi-eqmod$ git diff eqmod.cpp
diff --git a/3rdparty/indi-eqmod/eqmod.cpp b/3rdparty/indi-eqmod/eqmod.cpp
index f21571c..e0a4059 100644
--- a/3rdparty/indi-eqmod/eqmod.cpp
+++ b/3rdparty/indi-eqmod/eqmod.cpp
@@ -3118,8 +3118,8 @@ bool EQMod::saveConfigItems(FILE *fp)
{
INDI::Telescope::saveConfigItems(fp);

- IUSaveConfigNumber(fp, BacklashNP);
- IUSaveConfigNumber(fp, GuideRateNP);
+// IUSaveConfigNumber(fp, BacklashNP);
+// IUSaveConfigNumber(fp, GuideRateNP);

#ifdef WITH_ALIGN_GEEHALEL
if (align)

then I'm able to save the configuration (I deleted the empty configuration files before trying again).

For what it's worth, what I see in the EQMod tab (before I connect to the mount) are the 'Main Control', 'Options' and 'Aligment' tabs. There are no options regarding backlash or guide rate.

I would like to help more but for now I lack the skills needed.
I hope this would help to catch the issue (for reproducing the problem I think that it's important to start indiserver without the config files).

Regards,
Sergio

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!