×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Clestron mounts and hibernate

  • Posts: 456
  • Thank you received: 76

Replied by Derek on topic Clestron mounts and hibernate

Celestron got back to me.
This was added in 5.21 handset firmware..

I have NXS4.21 on my handset so it looks like I still need my hibernate-robot workaround for now.
I think I cant upgrade to 5.21 unless I change the physical handset. (Will have to bring the telescope + hc back from observatory to be sure)

Anyway, I hope this helps someone who wants to use a celstron fully remotely.

Derek
8 years 5 months ago #5503

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

  • Posts: 271
  • Thank you received: 72
Hi.

I have been looking at the celestron_gps driver to see if it would be obvious to me how to implement
Hibernate : x
Wake (from Hibernate) : y
But i cannot say it is.

I have the celestron AVX with NexStar+ controller and it is HC:GEM 5.22.3141 firmware so it should work?
I really want to test if i can get this to work, and would really appreciate if someone could give me some tips on how to implement this.
I have been working on a indi driver project, so i can implement the switches and other necessary code, but i dont know how to send the commands to the scope.

Thanks in advance, Mag
Proud owner of Observatory 17b - A remote Linux observatory.
Website: Observatory 17b
Build thread @ SGL: Starting summers observatory project
8 years 4 months ago #6157

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

I'll add it later today or by tomorrow and will let you guys know.
The following user(s) said Thank You: Magnus
8 years 4 months ago #6158

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

So where does this belong? When connecting/disconnecting from the mount? when parking/unparking? Need to make sure to put the commands at the correct places.
8 years 4 months ago #6162

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

  • Posts: 271
  • Thank you received: 72
I think that when the mount is parked is a good place to have it.
hibernating is something that you probably only want to do when packing things up for the night.

Not sure how connecting to a hibernated mount would work, as there will be no com to the mount.
Perhaps a message that the mount is hibernated and must be unparked?
Proud owner of Observatory 17b - A remote Linux observatory.
Website: Observatory 17b
Build thread @ SGL: Starting summers observatory project
8 years 4 months ago #6163

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

I guess I can always send "wakeup" upon connection. I also can't check "firmware" until there is an established connection, so it would have to be sent to all mounts. Will see how to approach this but needs some testing later on not only from recent firmwares but also older models.
8 years 4 months ago #6164

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

  • Posts: 271
  • Thank you received: 72
I can at least test on NexStar+ (5.22) :)
Proud owner of Observatory 17b - A remote Linux observatory.
Website: Observatory 17b
Build thread @ SGL: Starting summers observatory project
The following user(s) said Thank You: Jasem Mutlaq
8 years 4 months ago #6165

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

  • Posts: 271
  • Thank you received: 72
Could you not update a DeviceHibernationNP switch property. Then you only have to wake from hibernate if enabled.
If you add a test on firmware (when connected) so that unsupported mounts never can set DeviceHibernationNP to true?
Proud owner of Observatory 17b - A remote Linux observatory.
Website: Observatory 17b
Build thread @ SGL: Starting summers observatory project
8 years 4 months ago #6166

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

  • Posts: 456
  • Thank you received: 76

Replied by Derek on topic Clestron mounts and hibernate

I can do regression testing with my NXS4.21 handset.
Derek
The following user(s) said Thank You: Jasem Mutlaq
8 years 4 months ago #6175

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

Ok, I added the hibernate/wakup stuff. So I'm not really sure how this works, but I added "Use Hibernate" option in the Options tab. It works as following:

1. Once mount is parked, it is sent an 'x' to hibernate. After that, disconnect and turn off mount.
2. Turn on mount, and in the driver's Connect function, I send "wakeup", but this assumes that the port is up and running, which should be if there is power.

At any rate, test and see.
8 years 4 months ago #6176

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

  • Posts: 112
  • Thank you received: 12
I have a Celestron CG5 mount with the GEM 4.21 driver.
I'm testing the park option. Everything seems to be good when I park it but I'm not able to unpark it. The error message indicates :

2015-12-13T23:16:08: Firmwre version 4.1 or higher is required to sync. Current version is 4,0.

I was thinking that what would be great for debuging, is to create a database with indi user, their equipment and their version. So when you develop or improve a driver you can ask a lot of user with a lot of different version.
Linux Mint 19 Cinnamon using PPA for latest KStars-bleeding and INDI
Raspberry Pi 3 B+ with StellarMate
Atik 314E - ASI120M - CG5 with Celestron C9.25
8 years 4 months ago #6216
Attachments:

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

  • Posts: 271
  • Thank you received: 72
Did a test on the NexStar+

To go to hibernation went well. I then disconnected from indi controll panel and turned mount on and off.
At the first attempt to connect to indi again i got a message "failed to read firmware received #2 bytes expected 3"
I then got a message that "nothing" on my scope was supported. like Update time site, get RA DEC..

As i could not connect i tried to set Hibernate to Off in config.xml, and park to false in ParkData.xml. And manually waking mount from hibernate
Now it connects but i get this message (when connecting)
<code>2015-12-14T07:11:50: Failed to read RA/DEC values.
2015-12-14T07:11:50: Timeout error
2015-12-14T07:11:44: Failed to read RA/DEC values.
2015-12-14T07:11:44: Timeout error
2015-12-14T07:11:38: Mount UTC offset is 1,00. UTC time is 2015-12-14T07:11:32
2015-12-14T07:11:38: Mount is unparked.
2015-12-14T07:11:38: Unrecognized model (20).
2015-12-14T07:11:38: Telescope is online. </code>
Looks like something is happening with the firmware test, as i get unrecognized model?
When i disconnect it now i get this message
<code>2015-12-14T07:30:35: Write Error: Bad file descriptor
2015-12-14T07:30:35: Failed to retrive firmware information.
2015-12-14T07:30:35: Write Error: Bad file descriptor
2015-12-14T07:30:35: Failed to read RA/DEC values. </code>
This is what i get when running indiserver -vv
2015-12-14T07:41:58: Driver /usr/bin/indi_celestron_gps: read <message device='Celestron GPS' name=''>
2015-12-14T07:41:58: Client 0: queuing <message device='Celestron GPS' name=''>
2015-12-14T07:41:58: Client 0: sending <message device="Celestron GPS" timestamp="2015-12
2015-12-14T07:41:58: Driver /usr/bin/indi_celestron_gps: read <setNumberVector device='Celestron GPS' name='EQUATORIAL_EOD_COORD'>
2015-12-14T07:41:58: Client 0: queuing <setNumberVector device='Celestron GPS' name='EQUATORIAL_EOD_COORD'>
2015-12-14T07:41:58: Driver /usr/bin/indi_simulator_ccd: queuing snooped <setNumberVector device='Celestron GPS' name='EQUATORIAL_EOD_COORD'>
2015-12-14T07:41:58: Client 0: sending <message device="Celestron GPS" timestamp="2015-12
2015-12-14T07:41:58: Driver /usr/bin/indi_simulator_ccd: sending <setNumberVector device="Celestron GPS" name="EQUA
2015-12-14T07:41:58: Client 0: sending <setNumberVector device="Celestron GPS" name="EQUA
Proud owner of Observatory 17b - A remote Linux observatory.
Website: Observatory 17b
Build thread @ SGL: Starting summers observatory project
Last edit: 8 years 4 months ago by Magnus.
8 years 4 months ago #6218

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

Time to create page: 0.332 seconds