×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Celestron Motorised Focuser - Is it supported in EKOS yet

  • Posts: 30
  • Thank you received: 1
focuser of _gps

2019-03-07T19:04:47: [INFO] Focus Limits: Maximum (-23055) Minimum (1993) steps.
2019-03-07T19:04:47: [INFO] update focuser properties
2019-03-07T19:04:47: [INFO] Mount UTC offset is 1.00. UTC time is 2019-03-07T22:17:14
2019-03-07T19:04:47: [INFO] Mount is unparked.
2019-03-07T19:04:47: [INFO] InitPark: No Park data in file /home/hugo/.indi/ParkData.xml: No such file or directory
2019-03-07T19:04:46: [INFO] Mount model: AVX
2019-03-07T19:04:46: [INFO] Controller version: 5.30
2019-03-07T19:04:46: [INFO] Celestron GPS is online.

and standalone:
2019-03-07T19:04:47: [INFO] Device configuration applied.
2019-03-07T19:04:47: [INFO] Loading device configuration...
2019-03-07T19:04:46: [INFO] Celestron SCT focuser paramaters updated, focuser ready for use.
2019-03-07T19:04:46: [INFO] Focus Limits: Maximum (42737) Minimum (2249) steps.
2019-03-07T19:04:46: [INFO] Celestron SCT is online.
2019-03-07T19:04:46: [INFO] Celestron SCT Focuser is online. Getting focus parameters...
2019-03-07T19:04:46: [INFO] Firmware Version 7.15.8240

compare the max-limits
Current gear:
- AVX
- E8HD + ASI294MC
- Celestron 150x30 + ASI224 for guiding
- Celestron Focuser for harp stars

SW:
- Linux NUC + Ubuntu + INDI nightly on the server
- Linux Ubuntu + KSTARS nightly on the client (via CAT5 wire)
Last edit: 5 years 3 weeks ago by Stefan.
5 years 3 weeks ago #36115

Please Log in or Create an account to join the conversation.

Please submit the verbose debug log files (check my signature for how to).
5 years 3 weeks ago #36118

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 1

File Attachment:

File Name: log_21-22-52.txt
File Size:84 KB


hope it helps
Current gear:
- AVX
- E8HD + ASI294MC
- Celestron 150x30 + ASI224 for guiding
- Celestron Focuser for harp stars

SW:
- Linux NUC + Ubuntu + INDI nightly on the server
- Linux Ubuntu + KSTARS nightly on the client (via CAT5 wire)
5 years 3 weeks ago #36122
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 13
  • Thank you received: 2
I run mine from the USB port on the PI without issue
5 years 3 weeks ago #36123

Please Log in or Create an account to join the conversation.

  • Posts: 554
  • Thank you received: 138
Thanks, that's the sort of thing I need but the same log from the driver that's giving the incorrect values would help. I'm looking for the messages from the focuser.
5 years 3 weeks ago #36125

Please Log in or Create an account to join the conversation.

  • Posts: 554
  • Thank you received: 138
What system are you using? I think it's happening because of the way different systems and compilers handle the conversion between char and int.

Jasem, the celestron-gps code is using a char buffer for all it's replies:
char response[MAX_RESP_SIZE];
would changing this to:
unsigned char response[MAX_RESP_SIZE];
or
uint8_t response[MAX_RESP_SIZE];
help and not interfere elsewhere? Most other places either use ascii characters or the incorrect conversion doesn't matter.

I'd like to get this right but I'm not seeing the problem and the incorrect conversion isn't picked up by the CI builds so it's going to be difficult to ensure that it's OK until the user sees it.
Getting late now so I'm going to leave it until the morning.
5 years 3 weeks ago #36128

Please Log in or Create an account to join the conversation.

Chris,

Try with uint8_t and see if you get any issues.
5 years 3 weeks ago #36129

Please Log in or Create an account to join the conversation.

  • Posts: 36
  • Thank you received: 0
Chris,
You wanted the verbose log file I think. Attached please find the log file for focuser in which I only opened profile, and in focus module I requested to move focuser a few times, in each direction. There was NO movement of the focuser. In system action/status window at bottom of Focus module, it reports this below (but there is no movement), the outward focus requests result in no response .


2019-03-07T20:14:09 Focusing inward by 100 steps...
2019-03-07T20:14:08 Focusing inward by 100 steps...
2019-03-07T20:13:57 Focusing inward by 100 steps...
2019-03-07T20:13:55 Focusing inward by 100 steps...
2019-03-07T20:12:57 Idle.

Control panel for Celestron SCT focuser reports 0 for min, max, abs, and relative positions.
I did not redo calibration prior to this run. Next, I will redo calibration with Celestron Utility, put focuser in middle of its range, and re run this and get that log.
Hope this helps. Thanks
glen
(Hope I got this attachment inserted correctly.)

File Attachment:

File Name: log_20-08-34.txt
File Size:4,892 KB
5 years 3 weeks ago #36140
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 36
  • Thank you received: 0
Chris,
Ok, now I calibrated focuser first, and set focuser to some middle setting (near my focus point), specifically 26300.
By the way, as before, the calibration does not reach 0 or 60000, never has. Its minimum is ~2000, and its maximum is ~37000, according the utility . And these values vary a little each time it runs the calibration. (Does yours really cover the full 0-60000 range)?

Anyway, I then connect to stellarmate, and opened profile, and requested 'focus in' and 'focus out' a few times, and got no motion, although status window gives these comments:

2019-03-07T21:41:32 Focusing inward by 100 steps...
2019-03-07T21:41:29 Focusing inward by 100 steps...
2019-03-07T21:41:27 Focusing inward by 100 steps...
2019-03-07T21:41:25 Focusing outward by 100 steps...
2019-03-07T21:41:23 Focusing outward by 100 steps...
2019-03-07T21:41:21 Focusing outward by 100 steps...
2019-03-07T21:39:54 Idle.

I assuming pushing 'foucs in' and 'focus out' should move the focuser. Also tried to move to a new location, 27000, but got no response. Control panel this time shows, 26300 for absolute position, and min, max, and relative all 0.

In control panel the absolute position button(far left) was red. It had 26300 reading. I pressed it's 'set' button, and motor started moving until I aborted it a few seconds later. It then read 24000-23000 something.
Hope this helps. Let me know what other actions I can take to help?
Thanks.

File Attachment:

File Name: log_20-08-...3-08.txt
File Size:855 KB


Attached please find the new log.
5 years 3 weeks ago #36143
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 554
  • Thank you received: 138
@Penguin, good morning,
I've had another look at your log and can see that you are running both the Celestron GPS telescope driver and the Celestron SCT focuser driver. Both are getting data from the focuser. I don't need any more logs for now.

This all seems to work and I can see the two limit reports. The same data is converted differently, a problem with signed char to unsigned char conversion which I don't see on my RasbPi.

Your position data would be affected the same way if either of the two bytes returned go over 127 0x7f.
I'll try to get a new version of the celestron gps driver out later this morning.
5 years 3 weeks ago #36144

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 1
@CHRISROWLAND, thanks for that. Indeed for that I ran both but the error also came as iit ran alone. Happy to test the next version tonight (UTC 15h)

as you were talking about signed/unsigned stuff. maybe OT but. If I use the EKOS handcontroler and press the left, the scope turns right and other way round (celestron_gps) strange behaviour where I don't know the reason for (may be because the AVX only went through quick align and then solving?)
Current gear:
- AVX
- E8HD + ASI294MC
- Celestron 150x30 + ASI224 for guiding
- Celestron Focuser for harp stars

SW:
- Linux NUC + Ubuntu + INDI nightly on the server
- Linux Ubuntu + KSTARS nightly on the client (via CAT5 wire)
5 years 3 weeks ago #36145

Please Log in or Create an account to join the conversation.

  • Posts: 554
  • Thank you received: 138
@Glen, thanks for the log.
There seems to be an issue with debug where it isn't enabled until after the initial startup so I can't see the messages to the hardware but the limits are reported as the maximum and minimum both zero. I think that's coming from the hardware.

Are you sure that this run had the full calibrate process done? I found when I was testing that if the calibrate process is interrupted at any point the limits are set to zero. It has to wait until the focuser has moved to the low stop, the high stop, returned to the start position and stopped.

The errors and lack of motion seem to be partly because the code you are using to control the focuser is checking and refusing to move if the position is out of range. I don't think the driver is actually getting any move commands.

I've a new version of the sources released that will check the limits and only update them if they are sensible, that the maximum is significantly greater than the minimum. This should help. It also improves the log output.

You seem to be running the released compiled version and I'm not sure how a new version will be generated, if it isn't then you would need to build indilib from the sources.
5 years 3 weeks ago #36146

Please Log in or Create an account to join the conversation.

Time to create page: 1.536 seconds