×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

indi-nexstarevo issues and questions

  • Posts: 171
  • Thank you received: 41
Did you re-login after adding you to the group?
4 years 1 week ago #21223

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

  • Posts: 27
  • Thank you received: 2
Ha! I should but I did not :) Ok, works! ... well sort of. I ended up with same issue as nexstar_evo wifi connection:
- It does not move my mount :( . I'm trying to move any direction (as I would do with manual pad) but I am not getting any response from the mount


Thanks!
4 years 1 week ago #21233
Attachments:

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

  • Posts: 180
  • Thank you received: 50
@tmdag - I am glad you are trying to make my driver work.
First - it is not going to work via the cable (yet). The other ways of communication are not implemented but planned. Unfortunately the AUX protocol is a bit tricky.
So wifi-only for now.
Regarding the connection: what is the sequence of blinking of your mount wifi-light. It should be fast (not connected, waiting for client) - slow (Client assigned IP, no connection yet) - constant (Client connected).
If wifi light is constant please run the driver with debugging (you can also run indiserver with extra -v to get even more debugging) and upload the log. We will se what is wrong. If you are running on linux and have python3.6 available you can also run it against the simulator from the source directory to eliminate problems with your network/ap/etc.
Also check if you have alignment system active - sometimes this could be a problem. Make also sure that you have your position correctly entered. Evo is an alt-az mount and really needs to know your position.
P.
4 years 1 week ago #21246

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

  • Posts: 180
  • Thank you received: 50
One more thing - The celestron-nexstar driver will not work with the usb-aux cable. I hope you do not mean usb-serial cable. The AUX socket is different and *must not* be connected to regular serial line (actually it is serial with different voltages and wiring). I hope you did not fry your mount!
Furthermore, this is completely different protocol. For the celestron-nexstar driver you need a correct usb-serial adaptor with small RJ plug at the end.
You can connect it to the base of the hand-controller and use it that way. It is quite straightforward and should work if you get permissions right.
The nexstarevo driver uses low-level AUX protocol which is present in the WiFi transmission and in AUX sockets on the mount.
P.
4 years 1 week ago #21247

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

  • Posts: 27
  • Thank you received: 2
Hey Johym! Witam witam! :)

As for the cable:
I have bought from Amazon two cables:
- "Celestron Nexstar RS 232 PC Interface" cable
- "RS 232 to usb"
I have connected those to my USB and Celestron Hand control AUX output. (Nothing fried just yet, Hand control, controls mount as expected)
Is that correct procedure?

As for Wifi debugging, I will let you know asap :)
4 years 1 week ago #21254

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

  • Posts: 27
  • Thank you received: 2
>"Regarding the connection: what is the sequence of blinking of your mount wifi-light. It should be fast (not connected, waiting for client) - slow (Client assigned IP, no connection yet) - constant (Client connected)."
It seems to be contected, it's constant. And driver confirms it.

>you can also run indiserver with extra -v to get even more debugging
In configuration of Kstars/Indi I did not found any option to enter additional flags. I've tried to modify settings to run indi server as '/usr/bin/indiserver -v' but that didn't worked. What would be proper procedure to do so ?

Unfortunately I didn't got much of an info from debug option in driver:
2017-11-23T05:27:57: [INFO] NexStar Evolution is offline. 
2017-11-23T05:26:42: [INFO] Telescope aborted. 
2017-11-23T05:26:23: [INFO] NexStar Evolution is online. 
2017-11-23T05:26:15: [INFO] Connecting to 1.2.3.4@2000 ... 
2017-11-23T05:21:42: [INFO] Debug is enabled. 
2017-11-23T05:21:37: [INFO] NexStar Evolution is offline. 
2017-11-23T05:20:07: [INFO] NexStar Evolution is online. 
2017-11-23T05:20:04: [INFO] Connecting to 1.2.3.4@2000 ... 
2017-11-23T05:20:02: [INFO] NexStar Evolution is offline. 
2017-11-23T05:18:23: [INFO] Device configuration applied. 
2017-11-23T05:18:23: [INFO] Debug is disabled. 
2017-11-23T05:18:23: [INFO] Loading device configuration... 
2017-11-23T05:18:23: [INFO] NexStar Evolution is online. 
2017-11-23T05:18:18: [INFO] Connecting to 1.2.3.4@2000 ... 
2017-11-23T05:18:03: [ERROR] Error! Server address is missing or invalid. 
2017-11-23T05:17:59: [INFO] Debug is enabled. 

I did not enter anything under alignment system. I am afraid I would need to ask for some help here or docs. I am not even sure where and how would I get such info ?
From Hand control I managed to get info from MENU/Utilities/Get Axis Postion (as Azm/Alt)

4 years 1 week ago #21255
Attachments:

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

  • Posts: 27
  • Thank you received: 2
I haven't tested your driver from source, altho I am comfortable with python, I will have to spend some more time to get my head around what is where and what should i run. Lots of docs to go thorough! :)
Maybe I should do 2 steps back and highlight here that I am total beginner in this field.
4 years 1 week ago #21256

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

  • Posts: 180
  • Thank you received: 50
I will gladly help you make it work. Do not worry - we may get a decent docs out of this. The beginner is actually perfect for such exercise.

1) The cable: Please do not connect *ANYTHING* (except Hand Controller) to the AUX ports in the mount unless it is clearly marked as intended for the AUX ports. These are *NOT* RS232 ports at all. The RS232 port you can use is the one at the base of the HC. Unfortunately, my driver does not implement the serial connection yet - sorry.

2) The connection - thanks for the logs I am bothered by the online-offline flipping messages. Are you sure your network settings are not messed up by the auto-connect features of your OS. The 1.2.3.4 IP selected by celestron is really stupid - this is a real routable IP not assigned at the moment but not intended for such use and network stacks expect it to be a regular internet IP. That is why I am using my mount in the infrastructure mode with a portable access point - much less connectivity problems. If you cannot switch to infrastructure mode we will keep fighting with AP mode - do not worry. It is supposed to work in both modes.

3) The settings looks fine. I'll try to reproduce the problem on my end. Which version of the indi distro you are you using? The os is Fedora 27 I understand but indi is from this page or from the fedora distro?
P.
4 years 1 week ago #21261

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

  • Posts: 180
  • Thank you received: 50
I assume you are using the 1.6 distro for fedora 27 as described in the download section of the site
I have installed:
  • kstars-bleeding
  • indi-nexstarevo-bleeding
The fedora is an upgraded clean install and running in virtualbox. In this config all was working with the simulator.
On the other hand it is not working with the actual mount - so the problem is not yours!
Thanks for the heads up. Something broke recently. I'll try to fix it ASAP.
P.
4 years 1 week ago #21264

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

  • Posts: 27
  • Thank you received: 2
> These are *NOT* RS232 ports at all
Oh! I have blindly bought such cable as it was sold by Celestron itself (hence my assumption it is the right thing!).
When testing (with "Celestron NExstar" driver) I was connecting this cable to hand controllers input only (not the mount) from what i saw on internet (www.cloudynights.com/uploads/monthly_11_...42000-1479812820.jpg)


As for Software versions, I had some problems in different topic but i hope i am up to date:
indilib.org/forum/ccds-dslrs/2840-asi-29...ing-on-fedora27.html
>  rpm -qa | grep kstars
kstars-17.08.1-3.fc27.x86_64
 
>  rpm -qa | grep indi
indi-maxdomeii-bleeding-1.6.0-4.1.x86_64
indi-dsi-bleeding-1.6.0-4.1.x86_64
indi-sx-bleeding-1.6.0-4.1.x86_64
indi-apogee-bleeding-1.6.0-4.1.x86_64
libindi-bleeding-1.6.0-3.1.x86_64
indi-mi-bleeding-1.6.0-4.1.x86_64
indi-sbig-bleeding-1.6.0-4.1.x86_64
libappindicator-gtk3-12.10.0-16.fc27.x86_64
guice-multibindings-4.1-8.fc27.noarch
indi-fli-bleeding-1.6.0-4.1.x86_64
indi-qsi-bleeding-1.6.0-4.1.x86_64
indi-aagcloudwatcher-bleeding-1.6.0-4.1.x86_64
indi-atik-1.26-1.7.x86_64
indi-nexstarevo-bleeding-1.6.0-4.1.x86_64
indi-gpsd-bleeding-1.6.0-4.1.x86_64
indi-ffmv-bleeding-1.6.0-4.1.x86_64
indi-spectracyber-bleeding-1.6.0-4.1.x86_64
libindicator-gtk3-12.10.1-11.fc27.x86_64
indi-gphoto-bleeding-1.6.0-4.1.x86_64
indi-asi-bleeding-1.6.0-4.1.x86_64
indi-tess-bleeding-1.6.0-4.1.x86_64
indi-eqmod-bleeding-1.6.0-4.1.x86_64
indi-fishcamp-bleeding-1.6.0-4.1.x86_64
indi-qhy-bleeding-1.6.0-4.1.x86_64
lupinix-indi-bleeding-1.0-176.3.noarch

Looks like I am not using kstars-bleeding. Not sure If I am supposed to and not sure what is the difference :) (does "bleeding" stands for development version? :) )

Thank you for your help!
Last edit: 4 years 1 week ago by Albert Szostkiewicz.
4 years 1 week ago #21268
Attachments:

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

  • Posts: 180
  • Thank you received: 50
One more data point - the same problem shows itself on debian/ubuntu with Jasem oficial packages.
I am working on it.
P.
4 years 1 week ago #21270

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

  • Posts: 180
  • Thank you received: 50
1) Connection: fortunately the socket is different - so you are safe. Unfortunately the driver does not support serial connection so it is only useful with celestron-nexstar-gps driver (standard celestron driver). And it should work very well.
2) Driver: the 1.6 version has definitely some problem. Could you try the 1.5 version distributed with fedora 27? It should work. You can just install kstars and libindi from the standard fedora repo.
P.
4 years 1 week ago #21271

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

Time to create page: 0.647 seconds