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

Hi James,
Your implementation for the focuser works fine as far I could verify and also Autofocus works great.
The anoing thing is that when I have a second focuser in the firmware then I have two different implementations and that's really confusing.
I would prefer to go a step back, removing all code about the second focuser so that we have a clean code again before asking for merging in Master.
Are you OK with that approach?

Read More...

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

James,

If the tracking is not good most probably the Autofiocus will fail.
But As far as I tested, auofocus odes fail after some pictures, not running and endless loop.
May be Blueshawh has more experience with Autofocus (I just tested it because he reported on that and for my own curiosity).

Do you autoguide with ST4? May be there is something on this side! I eperienced erratic corrections because I forgot the Pullup in config ....

I do not understand the "Shaft coupler came undone" (Google translator ...)

Read More...

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

Hi,

Weather: Seems we all are in the same situation. Howard solved it on April 1st by adding a sort of cloud remover in the code :-)
Weather is completly crazy, rain, wind clouds hot then cold again.
Even my observatory project is stopped, my foundation hole transformed in a mud lake ... and at the end I got the flue :-)

Tracking Rate: Concerning the connect and OnStep using a custom tracking instead of Sideral seems strange.
At connection the only comands sent are the one related to location, time and date and confirmed by sniffing the communication.
It is true that the tracking frequency is only updated when a set is issued, but the filed is not the actual tracking frequency of Onstep nbut the last setiing, an it is confiusing I agree. The tracking speed setting is not handled by OnStep driver but uses Indi standard way of doing.
There could be a way to update with the ":GT#" command but with limitation if I believe the code herunder.
=============== OnStep code
// :GT# Get tracking rate
// Returns: dd.ddddd# (OnStep returns more decimal places than LX200 standard)
// Returns the tracking rate if siderealTracking, 0.0 otherwise
===============
I don't see any way to check which tracking is actual in OnStep (Sidereal, Solar, Lunar or Custom)
How did you notice you are on Custom Tracking after connect?

Second Focuser: May be it is possible to declare a second Focuser so that Indi would be aware of the second Focuser but I have no clue on how to do that ... I am still not understanding C++ :-(

Read More...

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

That explains this :-)

I wil try it

Read More...

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

James,

lucky me, it is raining like deluge so I could take some time to test your code.
From a focuser point of things are ok.
Ekos does not recognize that there is a focuser. How did you setup Ekos to detect OnStep Focuser?

Thanks

Read More...

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

James,

I see you make nice progress in your development.
Just for information, I checked with Howard about the presets. He is thinking to use EEprom to save presets in frimaware (most probably adding some new commands). As far I saw till now in Indi presets are saved on driver side. May be recheck with Howard before starting coding on this part.
As soon I have some time (spring is comming and somebody keeps me busy on other tasks :-) I will test your code in real.
That's all promising improvements and will add a new brick to the Driver.
Don't kow you follow the posts in This email address is being protected from spambots. You need JavaScript enabled to view it., it seems interest for Indi is growing also there.

Bon courage

Read More...

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

Jasem,

Language abuse on my side! thank you to follow our discussion and to steer us in right direction when we go the wrong way.

I fact the compliance with Indi focuser interface is my concern, I don't want to change the code ending up in non compliance.
there are some different point of view for example concerning on how to save focus points (one would use firmware , I would like to use Indi approach)
I whant to clarify this before doing anything else.

Read More...

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

I would suggest the following user interface for the Focuser
See attached picture



Read More...

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

James,

as you can see I merged your pull request but discovered later on the few ".directory" entries in github.
I removed those but take care next time as these entries are rejected when it comes to merge in main stream.

All seems to work, another step towards infinite .... perfection :-)

Read More...

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

James,

there are some days where it's better do nothing ... :-)
I have a lathe, if you need some special parts may be I can help, just need a drawing and material spec.

regards

Read More...

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

I knew I missed someting!

I am stupid, why do you guys not tell me :-)

Just checked with focuser travel set as hereunder
#define MinAxis4 0.0 // minimum allowed Axis4 position in millimeters, default = -25.0
#define MaxAxis4 38.0 // maximum allowed Axis4 position in millimeters, default = 25.0
and now I have my defined reference point.
I didn't see the forest, to much trees !!! and really was stuck in the idea by default the initial position was in the middle travel ... I'm getting old!

Mount is remounted, PEC sensor is working, motors run in the right direction, I now can test the real world but sky is still cloudy and it is snowing.

Good you are here to challenge the topic.

Read More...

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

Blueshaw,

I more or less use focuser as you describe.

James,

Are you sure the ":FI#" and ":FM#" do initialize Focuser at Min respectively Max? As far I see it only returns Min and Max but no action.*

- Timed control does not work or at least makes no sense for stepper focuser, I think we all agree on this, good this is one thing we can lease aside.
- Initialization, I believe we also agree we need a fixed starting point if absolute positioning is the way we wana go.

May be we can suggest this to howard (at least as a config like Focuser_Init_In or Out).
I checked on my board to init considering focuser is full In and starting from there I could have acceptable reproductible positions.

So the plan could be:
- leave the pulse as is (I am not happy with it but some other people may)
- leave the relative setpoint as is
- add an absolute setpoint.
- add three butons to initialize (but this would required change code in OnStep or I am wrong)
- add a function to save / retrieve values, ideally saved by name.

Joke of the day for you guys
I dismantled my EQ6 to add an indexer on the RA axis for the PEC and since it is dismantled to clean and renew grease .... tune ... tune ... tune
By remounting axis stays blocked in the middle of coarse, no way to move anymore :S
Hours of axis cooling and body heating later finally it slipped in place :)

Read More...

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

James,

I am a bit perplex on this topic and here is why.

When we are speaking about focuser position there are four things to consider:
1) The Software side is handling absolute position in micrometers at high accuracy and reproductibility which is a fine thing.
2) The mechanic which is composed of the stepper and the gear / belts. This has a limited accuracy and reproductibility and certainly not in the micrometer range, rather in the 1/100 mm range. On my homebrew focuser I reach a +/- 0,03 mm reproductibility when moving 20mm and I suppressed backlash by doind 0 to 20 then 20 to 19 then returning to 20)
3) The camera fixture, depending on the type of fixture, difference between setup can be as big as 0,03 mm (measured on my focuser)
4) The temperature influence (For aluminium there is a 23µm difference between 0°C and 20°C for 50mm (and considering the tube length of a 1,5m Focal where elongation would be 736µm for this 20°C delta T)

So by the end all together the absolute position precision is in the best case not better 1/100 mm and most probably worse.

Additionally to this, OnStep is considering that focuser is at 0 when starting so one has to position this focuser to middle coarse before start which is also not trivial. My opinion would be more accurate to use full In or Out which would be easier to achieve.

Where I want to come, is simply to say that all I need from a focuser is to have the possibility to adjust it with the most little displacement steps to reach focus and this without vibrations and once is is focused to stay in place.

I set up the focuser in this way:
1) Mount the camera
2) Set manually the focuser at mid coarse (the 0 for OnStep), again I woulkd prefer full In or Out (I included a clutch in my focuser)
3) find focus on liveview by entering an arbitrary relative travel
4) then use any tools I have to fine adjust the focuser and here I use also relative +/- travel

Honestly, I never use the pulse movements, I prefer the relative which is predictible.

By the end I really don't care about the absolutre position except for the two max/min positions but even here I did cheat
the firmware by telling +/- 18 instead of +/- 19 (may fosuser has 38mm travel) so that I never reach the mechanical limits (which can rapidly detroy the friction mechanism).

Now most probably I am certainly missing something here because may other posts are discussing around absolute focuser position. Till now I never found the rationale behind.

Attached what I use for my Focuser

File Attachment:

File Name: Stepper_Focuser.pdf
File Size: 1,096 KB


Read More...

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

James,

yes I made a mix between Absolte position read and Relative set.
I do not see the advantage of using abolute and relative setting when relative can do both and the difference was by head in my thinking :-)

Seriously I was thinking too on a adjustable timer for the in / out commands but also here I still don't kwow how to have predictable results.
The same happens with the bluetooth commands, the pulse are not always moving the same amount.

Read More...

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

Thank you James,

I will check and merge when I have time. Sorry I'm a bit busy on some other stuff for my boss :-).*

A propos Focuser, I agree I found also it is too short.
I just finished my new Focuser since I had to replace the CC motor by a stepper to be driven by OnStep.
I used a 48 stepper from a scanner with a reduction gear 21/1. Works fine.
Since no good weather (still snowing) I started to dismantle the mount to adapt everything to OnStep but beeing stopped in my hobby ...

Regards

Read More...

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

Hi Blueshawk,

Hope no damage due to the storm. Last time I spent some time on the roof replacing tiles :-(

On my side I am making progress on the hardwar, OnStep and Raspberry inside the box and ... I retrieve the bug with OnStep not connecting the first time.
Now I think I now where it comes from.
Some spurious data from Raspberry when connecting usb.
The difference between now and before is that Teensy is already powered when USB connects and/or Raspberry boot at box power on.
On the breadboard I powered the Teensy with USB this is why it never happened before.

I asked udev to solve this for me by running a script at connection (excerpt of 49-teesy.rules)
KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", MODE:="0666", SYMLINK+="teensy", RUN+="/usr/local/bin/teensy"

So now each time I connect to raspberry udev runs this script:
===========
#!/bin/sh
echo :# > /dev/teensy
===========

Since I did this I never had connection issues again.

Read More...

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

Hi,

thanks for the udev mention, I forgot to mention it, was trivial to me but I should know trivial does not exist :-)

Blueshawk, still KStars crashes?
What version and on wich distro are you running KStars?
I currently have 2.9.3 on Debian Buster and no crashes since a long time.

Would be nice if you could share your experience with the Odroid-XU4.
Looks like a powerfull solution.

regards

Read More...

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

Hi Jrsphoto,

When you start slsnif do you get in return the following?

alain@alain:~$ slsnif -n -l log.txt -u -s 9600 /dev/ttyACM0
Serial Line Sniffer. Version 0.4.4
Copyright (C) 2001 Yan Gurtovoy (This email address is being protected from spambots. You need JavaScript enabled to view it.)
Started logging data into file 'log.txt'.
Opened pty: /dev/pts/3
Saved name of the pty opened into file '/tmp/slsnif_pty'.
Opened port: /dev/ttyACM0
Baudrate is set to 9600 baud.

it is the /dev/pts/3 that you need to enter as port in the option tab before connection

Happy to hear the trick with minicom does work, still the problem is here but located

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!