Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New "reset" function using MD01 #51

Open
varenius opened this issue May 28, 2021 · 3 comments
Open

New "reset" function using MD01 #51

varenius opened this issue May 28, 2021 · 3 comments

Comments

@varenius
Copy link
Owner

May need to reset the telescope pointing from software.
Azimuth:
MD01 and BIGRAS/HR rotor can go around forever in azimuth. This is good, as long as we keep track so we don't damage cables due to wrapping. But, to align we cannot use end-positions as there are not any.
We have installed https://se.rs-online.com/web/p/proximity-sensors/7858468/ on both SALSA Vale and Brage. This provides a reference point in azimuth.
Currently, the sensors are mounted at azimuth 181 deg (Brage) and 187 deg (Vale). Can be read via I/O card polling.
The sensor span (where the signal is given) is 1-2 degrees. But, if approaching carefully from one end, it should be possible to align with 0.2 deg precision (since MD01 accuracy is 0.1 deg).
Elevation:
For elevation, we can (hopefully) use the hardware limit switches. This means; make sure we have e.g. 10 seconds before PULS timeout, then drive telescope to somewhere sensible, like 20 degrees, and then down towards the limit. This has to go around the software limits, as we want to push into the maximum. Keep track: If telescope is not moving, but did not reach where we wanted, then we are done (as long as we did send the telescope inside the MD01 limits, else it won't move).

Can set the MD01 position after reset from software via "CALIBRATE" command, https://github.com/varenius/salsa/blob/main/Developer_notes/BIGRAS_HR_MD0X/MD01-python3-test.py#L61. So, once we know where we are, we can use this to realign.

@varenius
Copy link
Owner Author

varenius commented Jun 8, 2021

Should be fixed in 67389b0, but only tested on Brage so far.

@varenius
Copy link
Owner Author

varenius commented Jun 8, 2021

Works also on Vale.
But! Seems to be some residual strange bug where sometimes the azimuth checking step (at least on Brage) just does not progress. It says something like this:
Screenshot 2021-06-08 at 16 47 17

But it never reaches that position. This is strange, I've never seen that in any other use of the telescope. Including several days of position-switching on/off the sun. Well, restarting the control program and doing a reset again for now works. But want to understand the reason for this!

@varenius
Copy link
Owner Author

varenius commented Jun 8, 2021

... should fix so that the "RESET" action in telescope controller is actually used, instead of calling the reset function from main as is now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant