Just out of curiosity, can you try renaming the file ON the astroberry to not have any spaces, commas, or special characters and see if it works?
Read More...
I'll do some more testing tomorrow on it. Maybe I've got something wrong in the hand controller somewhere, since no one else is having the issue.
Read More...
The code could also be modified to do the check as suggested:
if (driver.is_slewing(&slewing) && !slewing)
{
LOG_INFO("Slew complete, tracking...");
TrackState = SCOPE_TRACKING;
// Track Mode (t) is only supported for 2.3+
if (checkMinVersion(2.3, "track mode"))
{
CELESTRON_TRACK_MODE ctm = CTM_OFF;
if (driver.get_track_mode(&ctm))
{
if (ctm == CTM_OFF)
{
SetTrackEnabled(true);
}
}
}Read More...
For the AVX and CGX-L, if the mount is not tracking, then you do a slew, does it start tracking automatically?
Read More...
Related to #1, this may only be happening at the start of my night, but I've developed the habit of always toggling tracking off then on after a slew to be sure. So it might be that I'm unparking the mount (which doesn't enable tracking unless you've saved your mount config while it was tracking), doing a slew, then seeing the issue.
As the code stands now, because it is assuming it will always be tracking after a slew, but there are conditions where it may not actually be tracking, the safest thing to do is to explicitly start tracking.
Read More...
To answer your statements/questions:
1 & 2: I've had to manually toggle the tracking off then back on to get the mount to track after a slew. Otherwise the indi driver's state shows that it is tracking, but the mount actually isn't.
3: The code in Ekos seems to always check to see if the mount is tracking before sending a command to start tracking. It is always wrapped in an if statement like this one:
if (currentTelescope && currentTelescope->canControlTrack() && currentTelescope->isTracking() == false)4: Not sure about what the indi specification says, but the driver code itself as currently written DOES assume the mount will start tracking, and sets its internal state to SCOPE_TRACKING.
case SCOPE_SLEWING:
// are we done?
bool slewing;
if (driver.is_slewing(&slewing) && !slewing)
{
LOG_INFO("Slew complete, tracking...");
TrackState = SCOPE_TRACKING; switch (TrackState)
{
case SCOPE_SLEWING:
// are we done?
bool slewing;
if (driver.is_slewing(&slewing) && !slewing)
{
LOG_INFO("Slew complete, tracking...");
SetTrackEnabled(true);
// update ra offset
double raoffset = targetRA - currentRA + SlewOffsetRa;
if (raoffset > 0.0 || raoffset < 10.0 / 3600.0)
{
// average last two values
SlewOffsetRa = SlewOffsetRa > 0 ? (SlewOffsetRa + raoffset) / 2 : raoffset;
LOGF_DEBUG("raoffset %4.1f, SlewOffsetRa %4.1f arcsec", raoffset * 3600 * 15, SlewOffsetRa * 3600 * 15);
}
}
break;
case SCOPE_PARKING:
// are we done?
if (driver.is_slewing(&slewing) && !slewing)
{
if (driver.set_track_mode(CTM_OFF))
LOG_DEBUG("Mount tracking is off.");
SetParked(true);Read More...
I recently (a couple months ago) upgraded my hand controller firmware on my Celestron CGX, and since then my mount does not start tracking immediately following a slew. I've looked in the hand controller for a setting to change this, but can't find anything. Looking at the celestrongps.cpp file, the driver seems to assume that the mount will start tracking after slewing.
Has anyone else seen this behavior?
Also, I created a small patch that I believe will fix it, and I don't think it would have any side-effects other than possibly sending a command to the mount that isn't always needed.
diff --git a/drivers/telescope/celestrongps.cpp b/drivers/telescope/celestrongps.cpp
index 1f616e11..3be85ea9 100644
--- a/drivers/telescope/celestrongps.cpp
+++ b/drivers/telescope/celestrongps.cpp
@@ -847,7 +847,8 @@ bool CelestronGPS::ReadScopeStatus()
if (driver.is_slewing(&slewing) && !slewing)
{
LOG_INFO("Slew complete, tracking...");
- TrackState = SCOPE_TRACKING;
+ SetTrackEnabled(true);
+
// update ra offset
double raoffset = targetRA - currentRA + SlewOffsetRa;
if (raoffset > 0.0 || raoffset < 10.0 / 3600.0)Thoughts?
Read More...
This is awesome. Trying to track down the default names for drivers can seem strange. When I start indiserver with just a driver name like "indiserver indi_celestron_gps", the connection I need to use is "Celestron GPS"@remote_ip, but when I start it locally with Ekos, the name of the telescope is something like "Celestron CGX". I know it's in the drivers.xml, but this will make things a lot easier.
BTW, the client/server architecture of this is so nice. I connected a Raspberry PI Zero to the hand controller of my CGX that auto-starts indiserver (no web manager, it just starts the server/driver as a systemd service). Then my RPI4 that runs KStars doesn't need that USB cord hanging down to connect to the hand controller, I can just connect over wireless. That means the only cable I need that can possibly get in the way of the mount is a single power cord.
And since the RPI0 is only $10 for the wifi version, it's probably the cheapest piece of gear in my kit. Much cheaper than buying a Celestron SkyPortal or a SkyFi.
Read More...
fenriques wrote: awesome work! thank you. All the insight needed to monitor and review the session in one window; to me it should replace the Setup tab.
@Rick, I'm thinking to use the .analyze file as the only source of information for Astrodom. What do you think?
ferrante
@fenriques I think that would be fine. Might simplify things a lot for you, but it would tie your software really closely with Ekos, meaning anyone who uses other tools wouldn't be able to use it. But since I only use Ekos for imaging at the moment, it wouldn't affect me.
Read More...
@knro Does indi-pentax still depend on libraw20? I'm trying to do a fresh install on 20.04 using the stable ppa and I'm getting the following error:
sudo apt install -y indi-full
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
indi-full : Depends: indi-pentax but it is not going to be installedWhen I try to include libraw20, I get the following:
sudo apt install -y indi-full libraw20
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libraw20 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libraw20' has no installation candidateRead More...