Got this sorted out with a fresh image, and full install.
Tried both pip, and pip3 to install indiweb on the rock64.
Traceback (most recent call last):
File "/usr/local/bin/bottle.py", line 868, in _handle
File "/usr/local/bin/bottle.py", line 1748, in wrapper
rv = callback(*a, **ka)
File "/usr/local/lib/python3.5/dist-packages/indiweb/main.py", line 244, in start_server
File "/usr/local/lib/python3.5/dist-packages/indiweb/main.py", line 101, in start_profile
if info == 1:
Anyone know why this error is coming up when I try to start the server via indiweb?
Not familiar with the issue.
I did update everything before attempting to use ASTAP as the solver. So far have had no issues at all. I've used the images generated from INDI & ASTAP solved in Aladin and Astrometrica. Seems to work fine.
Using an older Nautilus 4x2" filter wheel. It works perfectly with the quantum driver.
The only issue I'm having is getting it to connect. It seems to only connect randomly, then works fine. Most of the time INDI is giving me this:
/dev/ttyUSB0 is already used by another driver or process.
If I move the FW around to different USB ports on the hub, eventually it will connect.
Any idea what is causing this?
Just want to say, I had nothing but headaches working with the astrometry.net local server. This ASTAP solver is GREAT! Can't believe the improvement. Solves all fields, and usually within 1 second. Amazing.
Just an FYI. I have the Nautilus 4 position 2" filter. This worked perfectly first try using the Quantum drivers. Thanks for the thread!
Interestingly, using the simulators and "upload and solve" the images that were not solving night before last are now solving, sorta.
The positions are off, by over 1.5 arcmin in RA and DEC.
Attached is a screenshot showing the nova.astrometry.net solve, the All sky plate solver solve (astrometry.net) vs Kstars solve.
The pixel scale is also still off in Kstars.
I agree, the user should be able to just override these settings if they know the scale.
I haven't had a chance to setup again. I'm trying to do a load & solve using the CCD simulator with the same setting as my DSLR. I'll see if I can get it to work.
The setting in Kstars are correct. Again, no idea what is causing it to constantly fail solves.
That all makes sense. Platesolve 2 is closed and windows based.
I'm not sure why I've had such a hard time getting it to work, especially when All Sky works great every time. I had these issues with the QHY163M as well. Any time I got anywhere close to the milky way, it would not solve.
I played with the settings for a few hours in Kstars / Ekos and couldn't get it to solve. If it's reading the image position and the position is way off, is there a way to just do a completely blind solve?
"The solver options in the KStars options box for the scale that you posted say 1.99 to 2.44." - I figured these were being calculated from the pixel size, focal length, ect?
"Based on your screenshot, I don't think that the astrometry.net solution is that far off from the other one you posted. " I wasn't able to even get Kstars to solve it.
Thanks for the help.
This has really been an issue since I started using INDI. Getting the plate solving working reliably seems impossible at times.
It would be nice if there were more than one option, SGP supports Platesolve2 from planewave that smokes ansvr in every way. planewave.com/downloads/software/
Anyway, I've attached an image I can't get Ekos to solve. Yet, All Sky Plate Solver, which also uses astrometry.net, solves it in a few seconds no issues. I see a discrepancy between the two.
As you can see, the "calculated" image scale is way different in Kstars than it is after being solved in Allksy Solver. Unchecking "auto update" and setting it manually doesn't help. It reverts back to using the scale calculated in the software, which is way off.
1.19 to 2.4 is way above the actual values of 1.1.
I'd suggest at some point adding support for platesolve2, as it is just better in every way.
Any suggestions as to what may be causing this issue?
Using latest everything, Ekos, Kstars, Indi, Win10. Canon 6D.
Okay, figured that out too. The 6D has a Manual and a Bulb setting. I had to put it on Bulb.
Main issue was caused by Capture target set to SD. Now I can't get the exposure times to change.
Now it does everything correct but update the shutter speed in the camera...