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

Khalid,

seems the season is not good for testing :(

Unfortunately more patience is needed on my side before I can start serious testing in rteal conditions.
Most probably begining November if the weather play whith.

Some more patience, I'm sorry

Read More...

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

@Blueshawk and Avarakin

Thanks for the more precise description.
I really need to speed-up my setup to start testing in real situation.

I will make a trial with my EQ6-R mount and EQmod driver, could be interesting.

Read More...

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

@ Blueshawk
Nothing except patches because of variable overflow was done since March ... I was really lazy last few months :)

@ Khalid
yes you are right, OnStep uses ":GU" return codes to update tescope status so it reflects exactly the Firmware Status.
The Status is refreshed in the tab each time there is a change in the return code.

In the doubt, I checked some very little slews (1', 2', 10') both RA and DEC via terminal and status behaves normal
Did the same via Indi Control panel and same results.
2018-09-06T11:22:31: [INFO] Slewing to RA: 10:10:09 - DEC: -0:29:09
2018-09-06T11:22:26: [INFO] Slewing to RA: 10:10:09 - DEC: -0:29:10
2018-09-06T11:22:17: [INFO] Slewing to RA: 10:10:10 - DEC: -0:29:10
2018-09-06T11:22:13: [INFO] Slewing to RA: 10:10:10 - DEC: -0:29:03
2018-09-06T11:22:08: [INFO] Slewing to RA: 10:10:03 - DEC: -0:29:03
2018-09-06T11:22:02: [INFO] Slewing to RA: 10:10:03 - DEC: -0:29:02
2018-09-06T11:21:49: [INFO] Slewing to RA: 10:10:02 - DEC: -0:29:02
2018-09-06T11:21:37: [INFO] Slewing to RA: 10:10:00 - DEC: -0:29:00

@ avarakin
First of all, thanks for your time passed on testing and reporting.
Are you using version 1.3 or 1.4?

Do I understand well: You try to slew some second and the sleew starts but never ends!
Does the ":GU#" return change in the "ONStep Status" tab?
Do you have logs for this situation.

I did a test on bench (cannot do it in real situation, my hardware is not mounted)
I was not able to reproduce this problem when asking slews for 1' or 2' and I saw the status changing from Tracking to Slewing and Tracking again,
This status change cannot be seen in the control panel because sometimes it is too quick, but it really happens

Since in the driver code Scope status if set only once based on Status query it is unlikely that Scope Status is set to Slewing and vever reste to Tracking due to polling issues and missed state changes.
I also check is it is not Ekos setting TrackState=SCOPE_SLEWING, it is not the case.

I am sorry not to be in position to help here.
I will check further but if in the meantime you could take logs of the situation would help.

Read More...

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

@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

Read More...

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

@ clearskyhopper,

glad to hear it works.

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

Clear Skyes

Read More...

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

azwing wrote: @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 and as Khalid said, teensy udev rules must be installed
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"



Read More...

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

Hi Khalid,

we were edditing at the same time :-)

Read More...

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

@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"

Read More...

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

Blueshawk wrote: Thanks Alain.
I could also try Azwing/master against the Onstep change sometime without too much effort. I'll leave things as they are for the moment and play with it more, but no more double shifts for a while.

=> I would prefer to test by myself before asking others to invest their time on thing that are not finalized.

I'm not sure this is the right way to go. It relies on changes to code outside the scope of the driver which could leave it broken at a later date, as well as having implications for legacy user and non indi users of OnStep. We could also try a side branch with James's in driver version sometime after I lick my wounds a bit.

.

=> 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 !

Read More...

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

@ Blueshawk.
Thanks for your efforts.

I had a look in your last logs.
Seems that from an alignment point of view things behave correct:
====================
I see and Align request ":A3#"
then a lot of align status ":A?" answered by <413> meaning first star out of 3 is in process
then after :CM" (sync most probably from Ekos after plate solvind"
followed by align status ":A?" answered by <423> meaning second star out of 3 is in process ==> so Sync does what is expected
===============

I really need to speed up my work to complete my set-up to be able to test this in real situation.
Just ordered a "blue pill". I want to build a testing patform, hope this will arrive soon.

I like your approach with testing protocol, this is the right way I would like to go for testing when everythinbg is set-up.

What concerns current Git version, it is tested to work on bench but not in real situation, but form an align point of view, it should behave as version 1.3.

The only differences are the new alignment tab and PEC which both need rework.

Regards

Read More...

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

azwing wrote: @ Blueshawk

I am glad for you that you can observe and test imaging.
For the moment I just can use my manual DIY Newton 11''F6 but not motorized.
If you mean pictures of the observatory, yeas I will take one tomorow and post it, but don't be affraid ... it is still civil work to do :-(

Nice picture you made here.
I am estonished of the quality with this camera. I am trying to aford one next year and had a look on this model.
Your picture reinforce my impression to go for this one.
For the moment I just have a old Canon Rebel T3 not unfiltered.

Good luck for your tests


Here the picture of the work in progress (slow progress)
Most probably the first project since I am retired and will be the worst project in terms of delay I ever did.
I planed starting april ending august, bur this was without thinking I am not 20 anymore ....

Read More...

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

@ Blueshawk

I am glad for you that you can observe and test imaging.
For the moment I just can use my manual DIY Newton 11''F6 but not motorized.
If you mean pictures of the observatory, yeas I will take one tomorow and post it, but don't be affraid ... it is still civil work to do :-(

Nice picture you made here.
I am estonished of the quality with this camera. I am trying to aford one next year and had a look on this model.
Your picture reinforce my impression to go for this one.
For the moment I just have a old Canon Rebel T3 not unfiltered.

Good luck for your tests

Read More...

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

kbahey wrote: Alain,

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

Yes of course this is alreazdy done.

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


Unfortunately no, only test was indoor but after the fix of yesterday and looks like it works as expected.

Hope I can put everithing togetehr before winter so I can do intensive testing in the observatory even without motorization of roof but this is another story.
I really need to finish the works before snow is comming ....

Read More...

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

Khalid,

I tried to create branches on git to have multiple versions together but I discovered it is not as easy as that.
I tried to create the pull request starting from github.com/azwing/indi/tree/ONStep1.3 (the branch where I put the fix for version 1.3) but it ended up in a disater .
So yes if you could do the pull request would help, I am sure you manage git much better than me.

Thanks

Read More...

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

Finally I found that the variables were overwriten via overflow by Indi, so all of them should be sie of RB_MAX_LEN.

Just move definition of RB_MAX_LEN into header instead of cpp

char OSStat[RB_MAX_LEN];
char OldOSStat[RB_MAX_LEN];

char OSAlignStat[RB_MAX_LEN];
char oldOSAlignStat[RB_MAX_LEN];
bool OSAlignProcess=false;
bool OSAlignFlag=false;
bool OSAlignOn=false;

char OSPier[RB_MAX_LEN];
char OldOSPier[RB_MAX_LEN];




Read More...

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

@ Khalid,

I checked the last version of stable and can reproduce what you notice about align.
Sine I discovered the same issue in the development version I did suspect my code but the fact that Stable has the same issue make me think that something in Indi changed and affected the behavior.

Here my notes after debugging:
To maintain some status I use global variables defined as part of "class LX200_OnStep" in lx200_OnStep.h
The strange thing is that these variables are reinitialized each time a function from Indi is called as if there would be declared again and again ????
I checked older versions with the same code and this did work.
Moving the variables declaration out of the class did solve this issue but I still do not understand the problem so nothing is solved.

I suspect my coding approach is wrong and I missunderstand something in Indi.
Any idea?

these variables are
char OSStat[20];
char OldOSStat[20];

char OSAlignStat[10];
char oldOSAlignStat[10];
bool OSAlignProcess=false;
bool OSAlignFlag=false;
bool OSAlignOn=false;

char OSPier[2];
char OldOSPier[2];




Read More...

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

@ Khalid,

I think something is broken in the driver code.
I am not in position to test it but for sure it has someting to do with refresh of Align variables
I believe the OSAlignOn variable is reset somewhere (could not see where).
I did this conditional to minimize polling but think it is not necessary.
Have same issue in version 1.4 and fixed it by discarding test

===================== lx200_OnStep.cpp ======================
// Update OnStep Status TAB
IDSetText(&OnstepStatTP, "==> Update OnsTep Status");
if (OSAlignOn) //don't Poll if no Aligning
{
if(!GetAlignStatus()) LOG_WARN("Fail Align Command");
}
==================================================

Read More...

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

Thnak you Jasem,

I finaly got to compile libindi.
all the 3rdparty drivers also except "indi-rtlsdr" (I suppose dependency for libdspau issue)
I will cointinue to search ...

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!