Wondering if the 64bits RPI build for ASTAP can be used with the ODroid N2 (ARM architecture) or if a separate build is required.
ASTAP is in fact a separate install. You can get itas a DEB package for the RPI at
. You will also need to install the star database (G17 or G16, same website) in order to use it as a astrometry solver.
Thanks for your reply Han. You can disregard my recent 'edit'.
What is great with ASTAP as an astrometry solver is that not only it is very fast, its catalog, compared with the astrometry.net catalog, is manageable sizewise for systems that do not have much storage capacity (RPI, ODroid,...) and do not have access to the Internet for online solving. (y)
What I found running ASTAP, in a simulated environment (pointing to Alnitak), is that it would not solve with an exposure of 8 seconds but did solve with an exposure of 4 seconds; and wickedly fast (1~2 seconds). I have not done thorough tests but it would seem that the number of stars used to solve, as mentionned previously, may be a factor as there will be more stars in longer exposures. I will do another simulated test with less stars being used when using longer exposures. So, if ASTAP doesn't solve you may try to reduce the exposure in astrometry.
As far as real life solving, the current weather tells me that I will have to wait .
If you like having the EKOS icons on the left of the window instead of the top, the Observatory icon is on its side! Somewhat funny but I assume it wasn't meant to be like that. The screen capture below shows that (4th icon from top).
Thanks for your info. I now know what 'Manual' is for, and as far as I know the mount was not parked.
I have tested this issue with my prototype OnStep controller (motors but no mount) and the problem remained. As I did not know then what the Manual option was for, I thought I could check it and use the "Mount Control" window to move it in RA. As one can expect, nothing much happened but... nudging the mount a bit with the "Mount Control" made things work. After the 'nudge' EKOS slews the mount to, and acquires and solves in the second and third positions. So, its either that the OnStep driver/controller needs a little convincing or there is a small bug somewhere. Anyway, there is a workaround and I can live with it for the moment, as long as I do not forget the little mount control trick.
As it is heavily raining, I wanted to do a quasi real-life practise with the PAA. I have set up to use my mount (LX200-OnStep, not simulated) with the CCD simulator, and the astrometry driver to do just that.
The PAA simulation goes well until when the mount is supposed to slew to the next position. It just sits there saying that its moving the mount to the next position but its continuing tracking instead of slewing. The capture gets done (a GSC image gets displayed), followed by the successful astrometry solving but then, no slew to next target (30 degrees west).
Am I doing anything wrong or is there something stopping the mount from slewing if we are using the CCD simulator with a real mount instead of a real camera with real stars? Everything works well in full simulation mode and in real life I can capture, solve and slew to target (but haven't tried PAA). My setup: latest KStars and Indilib, WO GTF81, OnStep modified mount, ASI1600 that gives me almost 2x1.5 degrees field of view. BTW, I get no error message.
Any insight will be appreciated.
Here is a photograph of my Indi setup. It consists of:
An OnStep modified Astro-Physics AP400 mount;
An ODROID N2 computer running Ubuntu, KStars, EKOS and Indi server;
A RPI running as a hotspot;
A ZWO ASI1600 camera and Zagyl filter wheel;
A Pegasus Astro DFMC focuser and Power Box;
All this on a home made telescope cart (missing a wheel ) that will allow me to roll it out of the garage and get ready for observing/astrophoto within minutes.
The OnStep controller is the grey box mounted on a small plexiglass sheet, attached to the tripod leg. The cart design was an adaptation of one, presented by the BBC Sky at Night Magazine ( www.skyatnightmagazine.com/advice/build-...ing-telescope-dolly/ ).
I decided to install meteostationWEB, a few days ago, to find out if I had the same issues as you had but to a lesser degree from what I understand. I got only a few of the "impossible IPState" messages you got but I got a fair bit of "MinMax FAIL" messages that I can't explain, not knowing the code enough. Sorry I can't/couldn't be of better help.
If that interests you, I built my meteo station using the BME280 instead of the BMP280/DHT22 that where used, with minor changes to the arduino code. The BME280 measures temperature, pressure and humidity in a single I2C sensor. I am also considering changing the solar cell by a TSL2591 I2C light sensor that has a much larger dynamic range that the solar cell and could give a rough estimate of the sky quality (SQM).
Thanks and good luck in your debugging.
Mine works fine with the latest KStars, etc... I do not get the message you get. Have you checked the values in the Indi Meteo tab of the MeteoStation driver? That could tell you if the hardware talks to the driver.
From what I seem to understand, you use the graphing capability of the MeteoStation software (web based if I remember); I do not use that feature and wonder if that could be the source of your problem, unless its hardware related.
Vey nice remote observatory! Wondering what you use as outside panels. They seem light and water resistant with the added bonus of not requiring painting.
In the Main Control panel, you should make sure tracking is ON by clicking on it (it's OFF when indi starts). That should solve the 'non responsive/non-tracking' issue.
I get a "Focuser failed to move to new requested position." error message when issuing a focus command (either in or out) on the Pegasus Astro UPB focuser, even though the focuser moves to a different position. I don't know if the UPB reports a focus position before the focuser gets to the requested position, or if the problem is caused by something else but the log file is attached as a reference.
Any help in solving this issue would be appreciated.