.

=> I agree it is not the way to go. I tried to setup two branches, "OnStepTest" and OnStep1.3", thinking I can keep;
-Master as the in Progress but tested version
-OnStepTest as the testing version
-OnStep1.3 as the stable vesion

It works in my local git, I can switch from one to the other with "fgit checkout OnStepxxxx" but I cannot use fixes on version 1.3 to pull requests in main master.
Git is most probably very powerfull but I am not able to use it in the right way I guess.

Concerning Legacy ... this is the reason why I don't want to release any changes before everything is tested against a stable version of OnStep Firrmware.
Seems the cat bites his tail here but soon or later we will manage.

Rome was not built in one day !

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.

Hi Folks,
I have the following issue.

Connecting the indi_lx200_OnStep driver that came with kstars the following error arises
#2018-09-02T16:13:38: [WARNING] Communication with /dev/ttyACM0 @ 9600 failed. Starting Auto Search...

There is no /dev/USB0 as suggested by default. So the determination of the /dev/ttyACM0 works (scan).
But i am not possible to establish a connection

Using MaxPCB (V1.12), libindi V1.7.x

May be you have a solution for this?
Regards,
Gerrit

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:

Do you see a device for it?


Do you see an ACM or USB device?

Install picocom, then do this:


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

If that is successful, enter:


See if there is a response.

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

@Clearskyhopper,

Using maxpcb you have a teensy 3.5 or 3.6 I suppose.
First of all do you have read/write access to /dev/ttyACM0
========= here how you check the port rights
alain@alain:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 sept. 2 18:32 /dev/ttyACM0
========= then check if you are in the dialout group
alain@alain:~$ groups
alain tty dialout voice cdrom floppy sudo audio dip video plugdev scanner netdev bluetooth pulse

If not in the dialout group you shoud use "sudo vigr" to add you in the "dialout" group

========= Can you test the connection with minicom
alain@alain:~$ minicom -s

then configure your serial port and speed as well
and type someting like
:GR#
or
:GD#
to see if you get answers from OnStep

========================================= excerpt of minicom screen

Bienvenue avec minicom 2.7.1

OPTIONS: I18n
Compilé le May 6 2018, 08:02:47.
Port /dev/ttyACM0, 18:32:19

Tapez CTRL-A Z pour voir l'aide concernant les touches spéciales

:GR#12:55:51#
:GD#+90*00:00#
=========================================================
Try this and see if you can have access

====================

If no success please come back here with indi logs and copy ls -l /dev/ttyACMx
and we will see further

Additionally it is a good idea to have you device listed in udev so you can refer to always the same symbolic device
============= hereunder my udev rules for usb serial
alain@alain:~$ more /etc/udev/rules.d/99-usb-serial.rules
SUBSYSTEM=="tty", ATTRS{idVendor}=="2a03", ATTRS{idProduct}=="0042", ATTRS{serial}=="8553130323135141D1F0", SYMLINK+="onstep"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A600emN7", SYMLINK+="arduino"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="AH032K35", SYMLINK+="picastro"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", ATTRS{serial}=="EB1XJY0G", SYMLINK+="eqmod"

Hi Khalid,

we were edditing at the same time

Hi Folks,
i added the udev rules already

1. lsusb:
Bus 003 Device 004: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial

2. ls -l /dev/ttyU* /dev/ttyA*
crw-rw-rw- 1 root dialout 166, 1 Sep 2 18:58 /dev/ttyACM1

3. picocom -eq -b9600 /dev/ttyACM1
:GU# nNpHzE0#
:GR# 03:06:34#
:GD# +90*00:00#

So it seems to work. I think the trick was in restarting the onstep, and not only in rebooting the system.
Many thanks!

And now I can connect the indi_lx200_OnStep driver as well.
Regards,
Gerrit

@ clearskyhopper,

glad to hear it works.

Woulkd be nice if you give feedback of your experiences in field.

Clear Skyes

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.

@Khalid,

thanks for the effort on the Firmware side.
This brings a new milestone where to base on for the next revision of Indi Driver.
On my side I succeeded to make progress on the observatory so that I have goog hope to finish all before winter.
In the meantime I should receive STM32 and rest of the hardware so I could be in position to test Teensy/STM32 and Arduino.

Did you succeed to have your OnStep mount ready for testing?

Regards

[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.