Khalid replied to the topic 'Canon DSLR Off By One Images - Very Dangerous!' in the forum. 12 hours 25 minutes ago

The danger of such a bug is that if I don't notice it, and do a plate solve, it will be on the wrong part of the sky, and the scope will wind itself around the mount. Happened to me a couple of times before I realized what is going on.

I workaround it by disabling touch capture, but sometimes I need that so I turn it on, then forget to turn it off. Then when I am fiddling with things, the shutter fires, and then INDI has to be stopped, and the camera disconnected from power.

You can simulate the exact problem by using the physical shutter button.

Read More...

Khalid replied to the topic 'Canon DSLR Off By One Images - Very Dangerous!' in the forum. 12 hours 52 minutes ago

Jasem,

Thanks, as always!

Kevin,

Did you try the scenario where the camera is connected to KStars, take a few pics, then go to the shutter button on the camera and take a picture? Then back to KStars and see if there is nothing in the queue?

This was one source of the problem: my Canon 650D has a touch screen, and if I touched it by mistake while zooming for focusing or something, it would go into that mode, and I have to stop INDI, shut down the camera by disconnecting power, then starting INDI again.

Read More...

Khalid replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 weeks ago

James,

Did you check the basics? Specifically : Polar Alignment, and Balancing, specially in RA?

I've had lots of problems due to these two recently (on a non-OnStep mount).

Read More...

Khalid replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

Howard solved it on April 1st by adding a sort of cloud remover


That is still a planned feature, not an actual one. The actual one in the April 1st release is a Light Pollution Eliminator!

Tracking rate


At one point, I was reviewing the spreadsheet , and noticed that 'Steps per second' is calculated as:

(Steps Per degree / (60 * 60)) *15

I thought that it should be 15.041066, because:

Sidereal day length = 23 hrs *60*60 + 56 mins *60 +4.1 seconds = 86,164.1 seconds

And 15 seconds would be 15.041066

When I asked Howard why he is using 15 instead of 15.041066, he said that the calculations use sidereal seconds already, not solar days, hours, minutes, or seconds.

This may be the source of the discrepancy that James is seeing?

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 3 weeks ago

Pull request merged into main repository.

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

Ok, got it.

Before passing the longitude, it is subtracted from 360.

Tested and works fine, east and west of Greenwich.

PR now changed to reflect this.

github.com/indilib/indi/pull/546

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

No.

As I said in a previous comment:

Sending

:Sg 080*12#

Works find, and sets the hand controller to -080:12, which is how Vixen says it should be, west of Greenwich.

Sending

:Sg 279*48#

Which is what the default code does in the lx200driver.cpp file, sets the hand controller wrongly to +080:12, which is east of Greenwich.

So, can't use the default code.

The code in the PR works for both cases (east or west of Greenwich)

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

That makes sense on paper.

The issue is that the hand controller now has +080:12 (i.e. east of Greenwich), instead of -080:12 (west of Greenwich). Having +080 totally messes up pointing.

My pull request works well on the coordinates I tried, both in KStars/INDI as well as the controller. It is off by one (80:11 instead of 80:12) if I don't put seconds in the longitude in KStars.

I wish Camiel Severijns would test and corroborate the findings, then comment here ... Maybe he moved on to another mount ...

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

This PR is now updated with the almost working code.

github.com/indilib/indi/pull/546

It is still off by one minute for longitude if I use xx:yy:00. yy will be yy -1. This is what getSexComponents() returns.

Since I enter the minutes and seconds in KStars, this is no longer an issue.

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

That does not work.

For 80:12:34 West, that does this:

"[SCOPE] CMD <:Sg 279:47#> "

And hand controller gets +080:13:00 (which is east of Greenwich!)

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

Here is a rewrite for the longitude function that seems to work, mostly.

It is off by one minute in some cases.

For example, when I use -80:12:00 in KStars, it sets it to 080*11 (not 12). If I use -80:12:20, then it uses 080*12 correctly. Don't know why.

// This override is needed, because the Sky Sensor 2000 PC requires a space
// between the command its argument, unlike the 'standard' LX200 mounts, which
// does not work on this mount.
int LX200SS2000PC::setSiteLongitude(double Long)
{
    int d, m, s;
    char temp_string[32];
    double longitude;

    if (Long < 0)
    {   
        // Long is negative in KStars, so west of Greenwich
        longitude = abs(Long);
    }
    else
    {   
        // Long is positive, so east of Greenwich
        longitude = 360 - Long;
    }

    getSexComponents(longitude, &d, &m, &s);

    snprintf(temp_string, sizeof(temp_string), ":Sg %03d*%02d#", d, m);

    return setStandardProcedure(PortFD, temp_string);
}


Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

I sent this from a terminal:

:Sg 312*00:00#

And the hand controller is +048:00:00.

So it seems correct east of 0.

West of 0, sending this:

:Sg 080*12#

Works, and sets the hand controller to -80:12:00. So, it is straight coordinates, but with a leading zero.

I am now a bit confused. What change to the code will work for both cases?

Remember that the standard LX200 will not work, since SS2K needs a space after the command for both long and lat, and a leading zero for Longitude.

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

I tested my PR with coordinates for Kuwait City.

Seems to be working properly as far as INDI/KStars are concerned.

2018-03-29T17:18:50: [INFO] Site location updated to Latitude: 29:04:00 - Longitude: 47:58:59

Here is the log output.

[2018-03-29T13:18:50.571 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:GG#> "
[2018-03-29T13:18:50.571 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] RES <+04> "
[2018-03-29T13:18:50.571 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] VAL [4] "
[2018-03-29T13:18:50.571 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:SG -03#> "
[2018-03-29T13:18:50.652 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:SG -03#> successful. "
[2018-03-29T13:18:50.654 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:St +029*04:00#> "
[2018-03-29T13:18:50.694 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:St +029*04:00#> successful. "
[2018-03-29T13:18:50.695 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:Sg -47*58:59#> "
[2018-03-29T13:18:50.746 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:Sg -47*58:59#> successful. "
[2018-03-29T13:18:50.748 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[DEBUG] Configuration successfully saved fo
r GEOGRAPHIC_COORD. "

But when I look in the hand controller, I see the longitude as +46:02:00.

When I use a location west of Greenwich, I get proper operation:

2018-03-29T17:34:23: [INFO] Site location updated to Latitude: 43:34:00 - Longitude: 279:48:00

The hand controller has -080:11:00 (Vixen designates west as negative).

And the logs:

[2018-03-29T13:34:23.427 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:GG#> "
[2018-03-29T13:34:23.427 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] RES <+04> "
[2018-03-29T13:34:23.427 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] VAL [4] "
[2018-03-29T13:34:23.430 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:St +043*34:00#> "
[2018-03-29T13:34:23.479 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:St +043*34:00#> successful. "
[2018-03-29T13:34:23.479 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:Sg 080*11:60#> "
[2018-03-29T13:34:23.569 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:Sg 080*11:60#> successful. "

So my code is working for west of Greenwich, but not east of it.

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

Jasem,

I tested with the code that is in the PR, and it works (for my coordinates)

github.com/indilib/indi/pull/546

Here is what is in the log:

"[SCOPE] RES <+04> "
"[SCOPE] VAL [4] "
"[SCOPE] CMD <:St +043*11:57#> "
"[SCOPE] CMD <:St +043*11:57#> successful. "
"[SCOPE] CMD <:Sg 080*22:29#> "
"[SCOPE] CMD <:Sg 080*22:29#> successful. "

I did not test with a longitude that is east of Greenwich.

Also, this change is specific to Sky Sensor 2000, because it requires a space after the :St and :Sg, unlike the standard LX200.

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

I am working on a patch, and once it is tested, I will submit a PR.

Read More...

Khalid replied to the topic 'Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

I found the problem.

The Sky Sensor 2000 PC driver calls updateLocation, which writes the coordinates to the mount, even if INDI is set to NOT update the mount.

Moreover, the code in setLongitude should subtract the minutes.

For example +080:11 is 279:49, not 279:33.

Also, the SS2000PC controller ignores the seconds, so no point in sending them ..

Moreover, the setLongitude and setLatitude functions do not log what the command was sent to the mount, nor what the response was.

Read More...

Khalid created a new topic ' Ekos sends wrong latitude/longitude to mount' in the forum. 4 weeks ago

I am using a Vixen Sky Sensor 2000 PC, with KStars on Ubuntu.

In KStars I set the location as

Longitude: -80 12 00.00
Latitude: 43 34 00.00

When I start INDI from KStars, I see this message:

Site location updated to Latitude: 43:34:00 - Longitude: 279:48:00
And in the hand controller, the coordinates were updated to: -080:11:00 +43:34:00

See how both are different from what I configured in KStars?

Here is the puzzle: even if I tell INDI to NOT update the mount, this still happens, which is wrong.

And it is not INDI that is at fault, it is Ekos/KStars somehow.

Because, when I connect to the mount from a terminal and execute the same commands I see in the log, everything is normal.

And when I start INDI from the command line and connect to it from Cartes du Ciels, everything is normal as well.

I don't see in the log anything that out of the ordinary.


[2018-03-28T16:33:18.478 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] Coordinate format is high precision
. "
[2018-03-28T16:33:18.478 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] <getSiteLatitude> "
[2018-03-28T16:33:18.478 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:Gt#> "
[2018-03-28T16:33:18.481 EDT DEBG ][ org.kde.kstars.indi] - CCD Simulator : "Error: Invalid range for Width (WIDTH). Valid
range is from 1 to 1280. Requested value is 4000 "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] RES <+43<EF><BF><BD>34> "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] VAL [43,34] "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] <getSiteLongitude> "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] CMD <:Gg#> "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] RES <080<EF><BF><BD>12> "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[SCOPE] VAL [80,12] "
[2018-03-28T16:33:18.534 EDT DEBG ][ org.kde.kstars.indi] - SkySensor2000PC : "[DEBUG] Mount Controller Latitude: 43.5667
Longitude: 279.8 "

So the correct coordinates are reported from the mount to INDI.

But then in the hand controller, it is not 80:12 anymore, it is 80:11.

And in the INDI control panel it reports this:

2018-03-28T20:33:18: [INFO] Site location updated to Latitude: 43:34:00 - Longitude: 279:48:00

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!