Stephen replied to the topic 'HELP resolve: solve-field, works command line not in Ekos' in the forum. 2 days ago

Will do. Thank you

Read More...

Stephen created a new topic ' HELP resolve: solve-field, works command line not in Ekos' in the forum. 3 days ago

Hi,

When Ekos loads a fit to slew to the coordinates it fails. Ekos uses the following command:

/usr/bin/solve-field --no-verify --no-plots --resort --no-fits2fits --downsample 2 -O -3 234.433 -4 65.6544 -5 15 -L 17.4512 -H 28.889 -u aw --parity neg -W /tmp/solution.wcs /home/pi/www/images/NGC2403.fit

However, when the following command is run from the command line on the RPI3 the fit solves in seconds:

/usr/bin/solve-field --no-verify --no-plots --resort --no-fits2fits --downsample 2 -O /home/pi/www/images/NGC2403.fit

How can Ekos be updated to remove these options: "-3 234.433 -4 65.6544 -5 15 -L 17.4512 -H 28.889 -u aw --parity neg -W /tmp/solution.wcs"?

I have clicked the edit pencil and these options are continually added.

Thank you

Read More...

Stephen created a new topic ' astrometry fails in Ekos and command line... used to work' in the forum. 3 days ago

Hi,

Running solve-field is failing. I am not sure why... can someone help. The error is below.

Thank you,
Stephen



/usr/bin/solve-field --no-verify --no-plots --resort --downsample 2 -O -3 83.8187 -4 -5.39549 -5 15 -L 19.3223 -H 26.6952 -u aw -W /tmp/solution.wcs /home/pi/www/Test_image.fit
Reading input file 1 of 1: "/home/pi/www/Test_image.fit"...
Header has 29 cards
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/usr/lib/python2.7/dist-packages/astrometry/util/image2pnm.py", line 323, in <module>
sys.exit(main())
File "/usr/lib/python2.7/dist-packages/astrometry/util/image2pnm.py", line 320, in main
mydir, fix_sdss=options.fix_sdss)
File "/usr/lib/python2.7/dist-packages/astrometry/util/image2pnm.py", line 248, in convert_image
(imgtype, errstr) = image2pnm(infile, outfile, sanitized, force_ppm, no_fits2fits, extension, mydir, fix_sdss)
File "/usr/lib/python2.7/dist-packages/astrometry/util/image2pnm.py", line 184, in image2pnm
errstr = fits2fits(infile, sanitized, fix_idr=fix_sdss)
File "/usr/lib/python2.7/dist-packages/astrometry/util/fits2fits.py", line 86, in fits2fits
hdu.scale('int16', '', bscale, bzero)
File "/usr/lib/python2.7/dist-packages/pyfits/hdu/image.py", line 383, in scale
bzero=bzero, blank=None)
File "/usr/lib/python2.7/dist-packages/pyfits/hdu/image.py", line 441, in _scale_internal
self.data += -_zero
TypeError: Cannot cast ufunc add output from dtype('int32') to dtype('uint16') with casting rule 'same_kind'
augment-xylist.c:588:backtick Failed to run command: /usr/bin/python -m astrometry.util.image2pnm --sanitized-fits-outfile /tmp/tmp.sanitized.bM9KHh --fix-sdss --infile /home/pi/www/Test_image.fit --uncompressed-outfile /tmp/tmp.uncompressed.II4Xbf --outfile /tmp/tmp.ppm.jFomFc --ppm
ioutils.c:567:run_command_get_outputs Command failed: return value 1

Read More...

Stephen replied to the topic 'ASI120MM (Again)' in the forum. 2 weeks ago

Hi,

I just recompiled indi_asi_ccd to this version resolved things: github.com/indilib/indi/blob/5d4f4ca8d6c...indi-asi/asi_ccd.cpp

- 16 bit RAW is usable again
- 120s image downloads.

Regards,
Stephen

Read More...

Stephen replied to the topic 'ASI120MM (Again)' in the forum. 2 weeks ago

Everything worked for me on Feb 5th. Tonight, Feb 10th, the ASI224 can be used to guide

PROBLEM: ASI1600 does not capture an image.

A complete reboot allowed it to capture a provide of 30s. a 5 or 15 sec preview would not work. After the one working preview, then the camera will not take an image again...

To be specific, the ASI1600 will go through the motions, and the completely saturated image will be obtained.

There is another symptom. The RAW 16 bit cannot be set. The error is - Cannot change format while streaming/recording.

I am not recording, and have tried turning it on, and off to see if it would turn it off. Debug log only has:
INFO 605.100979 sec : [ZWO CCD ASI1600MM-Cool] Session log file /root/.indi/logs/2017-02-11/indi_asi_ccd/indi_asi_ccd_03:04:16.log
ERROR 958.047321 sec : [ZWO CCD ASI1600MM-Cool] Cannot change format while streaming/recording.


PLEASE roll it back to what was working!!

Read More...

Stephen replied to the topic 'Ekos, INDI, SkySafari, and NexStar' in the forum. 2 weeks ago

This is not forgotten and only delayed due to time - logs are coming. Thank you for the help.

The test will be:

RPI3:
1. Setup Ekos per normal, with debug loging enabled
2. Use Kstars to slew mount.

On Mac:
1. Start Skysafari
2. Connect Skysfari to mount:
- uses libnexstar-0.15.tar.gz, ser2net and socat
- ser2net uses: 3300:raw:0:/dev/ttyUSB0:9600 NONE 1STOPBIT 8DATABITS
3. Use Skysafari to slew to a different star

Test:
a) disconnect INDISERVER and stop INDI
b) Use Skysafari to slew to another star
c) restart INDIServer, connect, and use KStar to slew to another star.

EXPECTED results:
- INDISERVER will not reconnect.

As soon as logs are gathered they will be posted.




3300:raw:0:/dev/ttyUSB0:9600 NONE 1STOPBIT 8DATABITS

Read More...

Stephen created a new topic ' twitter script...' in the forum. 2 weeks ago

Hi,

Does anyone have a twitter script that can work with Ekos already?

The concept is to used the script to post a tweet when the scheduler completes, or perhaps the guide star is lost. Perhaps even to warn of a meridian flip.

I am looking to create one if not. Using PTT tweeting from the command line is possible.

Read More...

Stephen created a new topic ' Ekos, INDI, SkySafari, and NexStar' in the forum. 3 weeks ago

Hi,

So far things with Ekos are going well. One thing that is a problem is when Ekos/KStars exists..

If SkySafari is used to slew the mount while previewing images with Ekos, then Ekos/KStar exits (crashes or shuts down), when Ekos is relaunched the INDIServer will not reconnect to NexStar. All other devices reconnect fine.

Any ideas how to resolve over than rebooting the rpI3?

Thank you,
Stephen

Read More...

Stephen created a new topic ' Where are the default astrometry options for solve-field' in the forum. 3 weeks ago

Had a great two days with Ekos on RPI3. Things work well, and the solver will do some images. Thank you for the great project and fun.

Where are the default options, such as -- download 2, set?

I have updated the CCDs, the Solvers own options, and yet when load a file to solve they defaults are used.

Thank you,,
Stephen

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 4 weeks ago

You all replied so quick, and I am grateful for it. Sorry I was not able to update sooner. I wish to correct that now.

In short all seems to be working now. Hoping for clear skies tomorrow to confirm all works. Thank you all for the great support it is most appreciated.

Summary:

- Not successful
- INDIserver/servermanager.py running as user pi. ASI224 fails to connect. Potential solution is to move the 99-asi.rules to /etc/udev/rules.d instead of /lib/udev/rules.d. I have not been able to get this to work yet, and assume it is something I missed.
- Configuring ZWO CCD in the CCD and guider section.

- Successful: (allowing Ekos to work so far)

- Jan 23rd update allowed ASI1600 to capture and save as expected.
- INDIserver, or servermanager.py running as user root works: ASI24 connects. 99-asi.rules is left in /lib/udev/rules.d
- Both ZWO cameras configured in INDIServer as CCDs only; guiders is left blank

Remaining tests - mount tracking, ASI224 auto guiding, while ASI1600 and ASI EFW doing captures.

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 4 weeks ago

Hi,

Just an update for anyone attempting this.

The INDI settings for the two ZWO cameras will not work if one is CCD and one is Guider.

The only way I can get this to work so far is to have both ZWO224 and ASI1600 as CCD.

I cannot test the guider for really this way. Everything does seem to work though.

Still testing to confirm all is good.

Regards,
Stephen

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 4 weeks ago

Hi,

I explored with ZWO too: zwoug.org/viewtopic.php?f=21&t=6785&p=12098#p12098

You helped greatly with the Jan 23rd INDI updated - ASI1600 worked today.

ZWO helped as well with the ASI224. The said to make the indiserver run as root, and it corrected it. Although, I would prefer running as pi. Having everything work now was the goal!

I will create a test run tonight with the whole setup - ccd, guide, efw - to confirm all is good.

Aside, I will be testing running Ekos in a web browser off the RPI3. I can post the setup if it is of interest. My goal is to have everything running to be controlled from browser, so I can monitor from PC, iPad, phone... :)

Thank you so much for the great project and support.

Cheers!
Stephen

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 4 weeks ago

No, but there is a change.

- ASI1600 will now take an image
- ASI224 gets the new Error connecting mentioned above.

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 4 weeks ago

Hi,

The indi release tonight helped sort of...

The ASI1600mm-c is now capturing its image and saving the files. This is great.

The ZWP EFW is also working.

However, the ASI224mc-c will no longer connect: "Error connecting to the CCD (5)"

The specific log entry:
INFO 50.206727 sec : [ZWO CCD ASI224MC-Cool] Debug is enabled.
DEBUG 62.953859 sec : [ZWO CCD ASI224MC-Cool] Attempting to open ZWO CCD ASI224MC-Cool...
ERROR 62.955346 sec : [ZWO CCD ASI224MC-Cool] Error connecting to the CCD (5)

If there is more information I can provide let me know.

The ASI224 connected prior to Jan 19, as I used it as a guide camera the first night with ASI1600 when I found out images did not work, and in December with my canon DSLR.

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 1 month ago

Everything on the RPI3 was installed via apt-get per the tutorials.

Jan 18th I was able to connect my ASI224mc-c as a guide camera using Ekos local Indi server on RPI3. Now the camera will not connect at all. Jan 18th was first night with ASI1600mm-c. I thought I was just my in experience new camera.

To confirm all equipment (two cameras and EFW) works, I setup/connected all the equipment directly to my Mac using Kstars and Ekos. Everything worked.

So last night on RPI3 all indi-full and kstars was removed and reinstalled using apt-get hoping It may have corrected something. It did not.

I have now tried connecting only the previously working ASI224mc-c directly to RPI3 and it will not connect at all give error (5). The ASI1600mm-c connects with Ekos remotely/local but only local allows for a preview image.

Below is the indi_asi.xml at the location you mentioned.

<?xml version="1.0" encoding="UTF-8"?>
<driversList>
<devGroup group="CCDs">
<device label="ZWO CCD" mdpd="true">
<driver name="ZWO CCD">indi_asi_ccd</driver>
<version>0.5</version>
</device>
</devGroup>
<devGroup group="Filter Wheels">
<device label="ASI Wheel">
<driver name="ASI Wheel">indi_asi_wheel</driver>
<version>0.5</version>
</device>
</devGroup>
</driversList>

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 1 month ago

A quick update - no RPI3 progress yet; it seems beyond me.

A quick test with a Mac version suggests that things can work: indilib.org/forum/ekos/525-ekos-on-mac-o...tml?start=1212#13945

The setup is one cable from ASI1600MM-c (imaging) to Mac, then using the ASI1600 hub the ASI EFW and ASI224MM-c (guider) is connected. This setup seems to allow images to save to the mac.

KStars on the Mac is connecting to the CloudMakers Indi Server. The indi_asi.xml needed to be copied from the IndiServer into the Kstar package, and all came up. Unfortunately this setup does not work in real use for me; it at least confirms the new hardware does work.

I will check another setup tonight on the RPI3 and report back. There is clearly a difference if the using the servermanager.py on the RPI3 instead of the indiserver within Ekos. In some cases the images seem to appearing the preview, some cases they do not, and in others they do not save to the RPI3 - they appear in the directory and disappear :(

Regards,
Stephen

Read More...

Stephen replied to the topic 'HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 1 month ago

Thank you. I will contact ZWO/Sam too to ask.

It is not clear if I should continue though..

The ZWO site has a FWTool here: astronomy-imaging-camera.com/software/ on the SDK & Upgrade Tool.

There is no firmware for the ASI1600mm-c, only:
- ASI120MM-compatible.iic
- ASI130MM-compatible.iic

And these are dated over Dec 2013.

Is this a confirmed successful approach?

Regards,
Stephen

Read More...

Stephen created a new topic ' HELP - RPI3 - ASI1600 - ASIGetExpStatus failed (0)' in the forum. 1 month ago

Hello:

I have been using Ekos successfully with a Canon T6i, on my RPI3. It does not matter the indiserver is running remote on RPI3 - 127.0.0.1.

The new ASI1600MM-C v3 just arrived and I am unable to get a single frame, whether it is a preview or scheduled.

Debug is turned on and en excerpt is:


INFO 5.202128 sec : Session log file /home/pi/.indi/logs/2017-01-21/indi_asi_ccd/indi_asi_ccd_22:18:$
INFO 5.202262 sec : Upload settings set to client only.
DEBUG 5.202442 sec : Requested CCD Frame is ( 0, 0) (4656 x 3520)
DEBUG 5.202492 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 0)
DEBUG 5.255528 sec : Setting frame buffer size to 16389120 bytes.
DEBUG 5.255730 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 0)
DEBUG 5.246331 sec : Setting frame buffer size to 16389120 bytes.
DEBUG 5.246526 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 0)
DEBUG 5.299397 sec : Setting frame buffer size to 16389120 bytes.
DEBUG 5.299629 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 2)
DEBUG 5.290327 sec : Setting frame buffer size to 16389120 bytes.
DEBUG 5.290556 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 2)
DEBUG 5.390950 sec : Setting frame buffer size to 32778240 bytes.
WARNING 5.391542 sec : 16 bit bayer format GRBG it not supported by the SER recorder.
DEBUG 5.391898 sec : Configuration successfully loaded.
DEBUG 5.384632 sec : Setting frame buffer size to 32778240 bytes.
WARNING 5.384728 sec : 16 bit bayer format GRBG it not supported by the SER recorder.
DEBUG 5.384918 sec : Configuration successfully loaded.
WARNING 6.432385 sec : World Coordinate System is enabled. CCD rotation must be set either manually or $
WARNING 6.455092 sec : World Coordinate System is enabled. CCD rotation must be set either manually or $
DEBUG 41.941423 sec : StartExposure->setexp : 10.000s
DEBUG 41.920465 sec : StartExposure->setexp : 10.000s
INFO 41.948078 sec : Taking a 10 seconds frame...
INFO 42.101601 sec : Taking a 10 seconds frame...
DEBUG 52.371764 sec : ASIGetExpStatus failed (0). Restarting exposure...
DEBUG 52.472024 sec : StartExposure->setexp : 10.000s
INFO 52.472308 sec : Taking a 10 seconds frame...
DEBUG 52.685237 sec : ASIGetExpStatus failed (0). Restarting exposure...
DEBUG 52.785550 sec : StartExposure->setexp : 10.000s
INFO 52.785859 sec : Taking a 10 seconds frame...
DEBUG 62.765265 sec : ASIGetExpStatus failed (0). Restarting exposure...
DEBUG 62.865561 sec : StartExposure->setexp : 10.000s
INFO 62.865829 sec : Taking a 10 seconds frame...
DEBUG 66.170600 sec : ASIGetExpStatus failed (0). Restarting exposure...
DEBUG 66.270935 sec : StartExposure->setexp : 10.000s
INFO 66.271203 sec : Taking a 10 seconds frame...
ERROR 73.122929 sec : Exposure failed after 3 attempts.

Read More...

Stephen replied to the topic 'What would you like to see in Ekos in 2017?' in the forum. 2 months ago

Thank you for such as great project. Using Kstars and Ekos on RPI3 is improving. Some thoughts:

1. A stable release label and bleeding edge label to help control when to update (supporting already mentioned idea)
2. Imaging camera view with telescope control to help frame shots, without a focuser; helps to capture two objects when not just centring with plate-solving
3. No slewing option with scheduler - Celestron precise goto often can frame shot nicely, and would be good to just start sequences when it is a newly frame sequence.
4. Separate build of Ekos from Kstars (supporting already mentioned idea)
5. Ability to use another planetarium, like SkySafari. Currently can use both Kstars and Skysafari at same time as long as INDIserver is not stopped/restarted or such.

Cheers!

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!