Khalid replied to the topic 'Re:RE: Manual Focusing' in the forum. 1 week ago

TallFurryMan wrote: Most of those are made for day-time use, and diffraction spikes are not so bright.


That is not always the case. Yes, with dim stars, it is not possible to focus.

But if you select one of the brighter ones, and zoom to 10X, the diffraction spikes from a Bahtinov are certainly visible, and usable too.

Try it out, it will work.

Read More...

Khalid replied to the topic 'Manual Focusing' in the forum. 1 week ago

For myself, I don't have a motorized focuser, although the controller I use allows for a focuser (OnStep STM32).

Since this means I have to focus manually, it also means I will be standing next to the telescope (I usually operate the telescope from indoors after the setup is complete).

So I just use a Bahtinov mask and Live View on the DSLR. Go to a fairly bright star, and center the middle diffraction spike in between the other two spikes, and you are done. Takes one minue.

Just remember to remove the Bahtinov mask before you go indoors!

Read More...

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

By the end of the night (3:15 am or so), all the precision slews (about a handful) were all successful. No hangs. I set the precision to 30 arc seconds.

Read More...

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

I should also mention that I did one precision slew tonight (it is clear, but with a bright moon), and it worked without a problem. It does not happen in every case. Not sure what triggers it.

Read More...

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

james_lan wrote: Also, can you check if it's got Pulse Guiding set to ON (Main tab, I think)


I have 'Use Pulse Cmd' set to On, which is I think is the default, since I did not mess with it, nor use the ST4 port in anyway.

james_lan wrote: There's also this checksumming which I think is good. Might resolve some problems, but does mean that we'll have to re-implement some of the LX200 stuff (or we could restrict that to just things like guiding/moving and see if that resolves the issues?


Yes, I think this requires reimplementing everything. So it is a parallel set of commands with the same functionality, but return codes on some that have no return codes in the LX200.

It can be implemented with some effort, but it may be the case that the OnStep telescope driver in INDI to be totally separate from the underlying LX200 class, with everything implemented with the new command set.

Also, it means that OnStep users have to use Alpha only?

Read More...

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

Did anyone diagnose what the source for the precision slew never ending problem is? Or at least what conditions trigger it?

For example: Could it be when the backlash compensation setting is more than the required precision?

I have seen it several times, but can't seem to get a pattern of when it would happen.

Read More...

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

[quote="azwing" post=29293
In the meantime I should receive STM32 and rest of the hardware so I could be in position to test Teensy/STM32 and Arduino.[/quote]

The STM32 is equivalent in speed and features to the Teensy 3.2 and the MiniPCB. So if you have one, you don't need the other.

In case you have not seen it, there is a PCB for the STM32 now, which makes the build much easier.

I look forward for you sharing the STM32 build details on the group. Many will benefit from seeing others build it.

[/quote]Did you succeed to have your OnStep mount ready for testing?[/quote]

Not yet. I am waiting for the belts before I have a friend help me with drilling holes to mount the motors.

But he (Dave) has a CG5 type mount that runs OnStep with the STM32.

Read More...

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

kbahey wrote: Now that I looked in the log, the alignment using plate solving is working as intended.

Before :CM#, there are Sr and Sd commands (set RA, set Dec), and the results from :A?# increment the number of 'stars' aligned on, from 413, to 423 to 433.

The first digit, 4, is the maximum number of alignment stars (because this is an Arduino Mega), and the second digit is the number of star aligned on, and the third digit is the number of stars that are intended to align on.

Once the second and third digit are equal, alignment is complete.

You mentioned that it is not plate solving (too fast or something). That is separate issue, but at least coordinates are returned and are used in Sr, Sd, then CM syncs.

Thanks for testing this. It confirms what I found testing indoors.


Howard merged the plate solving align code into OnStep Alpha (as of a few minutes ago).

So anyone who wants to use the Mount Model tool, can do so, with the stable version of INDI packages (no need for a special fork or branch).

The procedure is the same: click 3 Star (or a number suitable to your controller and obstructions), go to Mount Model and select stars that are far apart, and then click Run. That is all there is to it.

Read More...

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

Ignore KStars and INDI for a moment, and focus on USB at the Linux level.

Close KStars and make sure no INDI driver is running, then unplug the controller from your Linux box.

Plug it again, then do the following:

lsusb

Do you see a device for it?

ls -l /dev/ttyU* /dev/ttyA*

Do you see an ACM or USB device?

Install picocom, then do this:

picocom -eq -b9600 /dev/ttyX

(replace X by USB0 or ACM0, depending on what you see above.

If that is successful, enter:

:GU#

See if there is a response.

You may need to add the Teensy's udev rules .

Read More...

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

Now that I looked in the log, the alignment using plate solving is working as intended.

Before :CM#, there are Sr and Sd commands (set RA, set Dec), and the results from :A?# increment the number of 'stars' aligned on, from 413, to 423 to 433.

The first digit, 4, is the maximum number of alignment stars (because this is an Arduino Mega), and the second digit is the number of star aligned on, and the third digit is the number of stars that are intended to align on.

Once the second and third digit are equal, alignment is complete.

You mentioned that it is not plate solving (too fast or something). That is separate issue, but at least coordinates are returned and are used in Sr, Sd, then CM syncs.

Thanks for testing this. It confirms what I found testing indoors.

Read More...

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

There are too many variables in your setup.

If it was me doing it, I would do it as follows:

1. On the OnStep side:

a) Download Alpha,
b) patch it with the plate solve align patch
c) Compile it, and upload it to the Mega
d) Using the WiFi, set the longitude, latitude, UTC offset, date and time.

2. On the INDI site:

a) Download the current master (NOT azwing's fork)
b) Compile it. That way you get the buffer fixes and guarantee that the results returned from USB commands are valid.

Test the Plate Solve Align as follows:

1. In INDI click on 3-Stars. Tracking should start.
2. In KStars, select Mount Model, and choose 3 stars that are far apart and visible in your location.
3. Start the Mount Model tool.

Check the screen where KStars display the delta errors (the difference between where the object is, and where it was supposed to be).

Read More...

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

Blueshawk wrote:
Installed alignment patched command.ino and downloaded to mega.

coords not set in firmware after update:
indi would not set them, longitude error. used phone app to set site coords.


That is odd. Latitude and longitude should be set in EEPROM, and recalled from there if they are not sent from KStars. When I am using KStars, I always choose 'KStars updates mount' and that way, longitude, latitude, UTC offset, date and time are all sent at the beginning of sessions. But regardless, if you don't do that, OnStep should remember the last latitude and longitude you used.

Slewed to deneb and checked focus.
Manual plate solve captured and solved but resulted in a loss of ra/dec position. showing all zeros. then captured but could not solved based on previous 00:00:00 coords
patch breaks manual plate solve.

A manual sync after solving by hand also failed to update, and appears to have crashed the mount.


That is odd. Are you using the current master of KStars, or azwing's fork?
There was a problem in the last stable version where INDI would not get back returned data because of the buffer size change (RB_MAX_LEN thing). The fix is in the current master (not the PPA builds yet).

Perhaps that is related?

Read More...

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

This should work:

git checkout Alpha

Then copy your Config.xxx.h, and my Command.ino, and you are now with the latest Alpha with the plate solving patch applied.
git diff Command.ino
will give you the changes, in case you want to review them.

Read More...

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

Beta is not a good choice for testing alignment, since Howard added lots of very useful changes in Alpha regarding alignment.

The patch still applies fine on the current Alpha.

$ patch -p1 < /tmp/onstep-plate-solve-align_2018-08-08.txt 
patching file Command.ino
Hunk #3 succeeded at 1991 (offset 2 lines).

Ignore the hunk thing.

Attached is a Command.ino file that is today's Alpha with the patch applied. Rename it from .txt to .ino only, and you are good to go.

Read More...

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

@Blueshawk

If you mean the plate solve align, then the best way is to download (or checkout) the latest version of OnStep, then apply my plate solve align patch to it, as per the instructions here .

The procedure to test it is the same as before: Go to the INDI panel click on the 3 star align, then go to Mount Model and select 3 stars to align on, then let it run its alignment. At the end of the process you should get more accurate Goto pointing, and the :A?# command should show 633 as the result.

Read More...

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

Alain,

Jasem merged the fix into master. So that part is taken care of now. The next stable should have the fix.

Did you get a chance to test the plate solve align with OnStep (the patch that I created a while ago)?

Read More...

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

Done.

Tested it, and I see the status of the alignment again.

Here is the PR for Jasem.

github.com/indilib/indi/pull/687

Read More...

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

Thanks for finding the root cause.

So, will you create a pull request for the fix against master, or should I do that?

Read More...

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

I upgraded today to the latest stable KStars and INDI.

The good news is that the driver no longer crashes, after the fixes for the tty_nread changes. So slewing is normal, ...etc.

The bad news: One problem: when starting an Align (1 star or 3 star), the 'Align Process' line does not change to the value returned from :A?#. It still says 'Manual Alignment Process Idle', instead of the return value from said USB command.

Read More...

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

That makes sense.
I have not heard of lots of people using these features within OnStep.
But if something is present, and readable over USB, then why not display a value for it? Maybe of use to someone.

Going back to the Mount Model, and the number of stars to use. In theory, we can modify Ekos to query OnStep via :A?# and automatically select the same number of stars. However, Ekos is not for OnStep only, and tens of other mounts run on it, so I am not not in favour of moving mount-specific complexities in the code and UI for Ekos.

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!