Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 2 months ago

In TSX go to Tools->TCP Server. A pop up window will open. Click the check box "Listening for connections". This option will stay enabled and persist across TSX restarts.

By the way, you should not need to run TSX with sudo.

Read More...

Greg thanked Jasem Mutlaq in topic Optec Gemini Focuser/Rotator 3 months ago
Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 3 months ago

Jasem - excellent work and thank you for the help!
For others using this device, the documentation is here:
indilib.org/devices/focusers/optec-gemini-focusing-rotater.html

Read More...

Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 4 months ago

VM spun up. Latest indi and kstars/ekos installed and operating. I sent you an email (I think). Need to know who/where to let in.

Read More...

Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 4 months ago

Thanks for looking into this guys!

Jasem - I will spin up a VM and connect the gemini in to it and get you access. Give me a bit to get that running.

Read More...

Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 4 months ago

I'm able to connect now but still not working. I"ve tried selecting various device types including Optec TCF-Lynx 2/3 and TCF-S "Classic Converted". I get similar results in each case:

schwim@observatory ~/.indi/logs/2017-07-31/indi_lynx_focus $ cat indi_lynx_focus_04\:14\:24.log
INFO	25.892031 sec	: [FocusLynx] Session log file /home/schwim/.indi/logs/2017-07-31/indi_lynx_focus/indi_lynx_focus_04:14:24.log
INFO	31.459503 sec	: [FocusLynx] Device: FocusLynx
INFO	31.459541 sec	: [FocusLynx] Focuser model set. Please connect now...
DEBUG	31.459549 sec	: [FocusLynx] Absolute focuser detected.
INFO	33.644249 sec	: [FocusLynx] Device: FocusLynx
DEBUG	33.645057 sec	: [FocusLynx] CMD (<F1HELLO>)
DEBUG	33.647062 sec	: [FocusLynx] RES (!)
DEBUG	33.648059 sec	: [FocusLynx] RES (ERROR ID = 0)
INFO	33.648069 sec	: [FocusLynx] ERROR ID = 0 is detected.
INFO	33.648075 sec	: [FocusLynx] FocusLynx is online. Getting focus parameters...
DEBUG	33.648083 sec	: [FocusLynx] CMD (<F1SCDTOB>)
DEBUG	33.653078 sec	: [FocusLynx] RES (EXT = The received command is formattated incorrectly)
ERROR	33.653090 sec	: [FocusLynx] Controller error: EXT = The received command is formattated incorrectly
DEBUG	33.653218 sec	: [FocusLynx] CMD (<F1GETCONFIG>)
DEBUG	33.653231 sec	: [FocusLynx] RES (END)
ERROR	33.653236 sec	: [FocusLynx] Controller error: END
ERROR	33.653240 sec	: [FocusLynx] Failed to retrieve focuser configuration settings...
DEBUG	33.653261 sec	: [FocusLynx] CMD (<FHGETHUBINFO>)
DEBUG	33.654055 sec	: [FocusLynx] RES (!)
DEBUG	33.655084 sec	: [FocusLynx] RES (ERROR ID = 0)
ERROR	33.655094 sec	: [FocusLynx] Failed to retrieve HUB configuration settings...
INFO	33.655117 sec	: [FocusLynx] Device: FocusLynx
INFO	33.655320 sec	: [FocusLynx] Device: FocusLynx
INFO	33.655332 sec	: [FocusLynx] Device: FocusLynx
INFO	33.655804 sec	: [FocusLynx] Device: FocusLynx
INFO	33.656092 sec	: [FocusLynx] Device: FocusLynx
INFO	33.656261 sec	: [FocusLynx] Device: FocusLynx
INFO	33.656282 sec	: [FocusLynx] Device: FocusLynx
INFO	33.656316 sec	: [FocusLynx] Device: FocusLynx
INFO	33.656339 sec	: [FocusLynx] Device: FocusLynx
INFO	33.656360 sec	: [FocusLynx] Focuser model set. Please disconnect and reconnect now...
DEBUG	33.656371 sec	: [FocusLynx] Absolute focuser detected.
INFO	33.656378 sec	: [FocusLynx] Device: FocusLynx
DEBUG	33.656383 sec	: [FocusLynx] CMD (<F1SCTE0>)
DEBUG	33.660111 sec	: [FocusLynx] RES (ived command is formattated incorrectly)
ERROR	33.660124 sec	: [FocusLynx] Controller error: ived command is formattated incorrectly
INFO	33.660135 sec	: [FocusLynx] Device: FocusLynx
DEBUG	33.660138 sec	: [FocusLynx] CMD (<F1SCTS0>)
DEBUG	33.662077 sec	: [FocusLynx] RES (ERROR ID = 3)
ERROR	33.662098 sec	: [FocusLynx] Controller error: ERROR ID = 3
INFO	33.662107 sec	: [FocusLynx] Device: FocusLynx
DEBUG	33.662112 sec	: [FocusLynx] CMD (<F1REVERSE0>)
DEBUG	33.666113 sec	: [FocusLynx] RES (ERROR TEXT = The received identifier was not recognized)
ERROR	33.666128 sec	: [FocusLynx] Controller error: ERROR TEXT = The received identifier was not recognized
DEBUG	33.666158 sec	: [FocusLynx] CMD (<F1SCTCA+0000>)
DEBUG	33.667072 sec	: [FocusLynx] RES ()
ERROR	33.667092 sec	: [FocusLynx] Controller error:
ERROR	33.667106 sec	: [FocusLynx] Failed to set temperature coefficeints.
INFO	33.667117 sec	: [FocusLynx] Device: FocusLynx
DEBUG	33.667121 sec	: [FocusLynx] CMD (<F1SCTM@>)
DEBUG	33.668085 sec	: [FocusLynx] RES (D = 4)
ERROR	33.668095 sec	: [FocusLynx] Controller error: D = 4
INFO	33.668116 sec	: [FocusLynx] Device: FocusLynx
DEBUG	33.668120 sec	: [FocusLynx] CMD (<F1SCBE0>)
DEBUG	33.674038 sec	: [FocusLynx] RES (ERROR TEXT = The command received was for an invalid target device)
ERROR	33.674056 sec	: [FocusLynx] Controller error: ERROR TEXT = The command received was for an invalid target device
DEBUG	33.674076 sec	: [FocusLynx] CMD (<F1SCBS00>)
DEBUG	33.674089 sec	: [FocusLynx] RES (END)
ERROR	33.674092 sec	: [FocusLynx] Controller error: END
ERROR	33.674095 sec	: [FocusLynx] Failed to set temperature coefficients.
DEBUG	33.674129 sec	: [FocusLynx] Configuration successfully loaded.
INFO	55.442690 sec	: [FocusLynx F2] Device: FocusLynx F2
INFO	55.442730 sec	: [FocusLynx F2] Focuser model set. Please connect now...
DEBUG	55.442737 sec	: [FocusLynx F2] Absolute focuser detected.
INFO	61.571384 sec	: [FocusLynx F2] Device: FocusLynx F2
INFO	62.530229 sec	: [FocusLynx F2] Device: FocusLynx F2
INFO	68.726912 sec	: [FocusLynx F2] Device: FocusLynx F2
INFO	68.726942 sec	: [FocusLynx] F1 PortFD : 4
INFO	68.726947 sec	: [FocusLynx F2] F2 PortFD : 4
DEBUG	68.726953 sec	: [FocusLynx F2] CMD (<F2HELLO>)
DEBUG	68.726972 sec	: [FocusLynx F2] RES (!)
DEBUG	68.726990 sec	: [FocusLynx F2] RES (ERROR ID = 0)
INFO	68.726994 sec	: [FocusLynx F2] ERROR ID = 0 is detected.
INFO	68.726998 sec	: [FocusLynx F2] FocusLynx is online. Getting focus parameters...
DEBUG	68.727003 sec	: [FocusLynx F2] CMD (<F2SCDTOB>)
DEBUG	68.728776 sec	: [FocusLynx F2] RES (!)
DEBUG	68.729777 sec	: [FocusLynx F2] RES (ERROR ID = 0)
DEBUG	68.729934 sec	: [FocusLynx F2] CMD (<F2GETCONFIG>)
DEBUG	68.734784 sec	: [FocusLynx F2] RES (R TEXT = The received command is formattated incorrectly)
ERROR	68.734807 sec	: [FocusLynx F2] Controller error: R TEXT = The received command is formattated incorrectly
ERROR	68.734825 sec	: [FocusLynx F2] Failed to retrieve focuser configuration settings...
INFO	68.734844 sec	: [FocusLynx F2] Device: FocusLynx F2
ERROR	68.734862 sec	: [FocusLynx F2] Error loading user configuration. Unable to open config file. Error loading file /home/schwim/.indi/FocusLynx F2_config.xml: No such file or directory
. To save user configuration, click Save under the Configuration property in the Options tab.
INFO	96.867471 sec	: [FocusLynx] Device: FocusLynx
INFO	96.867886 sec	: [FocusLynx] FocusLynx is offline.
INFO	96.868005 sec	: [FocusLynx F2] Device: FocusLynx F2


Read More...

Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 4 months ago

Hmm. Gave that a try in various configurations. I don't see any way to specifically configure for a Gemini. Regardless I always get the same response:

DEBUG   37.951111 sec   : [FocusLynx] CMD (<F1HELLO>)
ERROR   39.953177 sec   : [FocusLynx] TTY error: Timeout error
INFO    39.953205 sec   : [FocusLynx] Error retreiving data from FocusLynx, please ensure FocusLynx controller is powered and the port is correct.


Read More...

Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 4 months ago
Greg replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 4 months ago

Bump - I seem to have everything else working with my rig including control of the Paramount. I just can't control the Optec Gemini. I'd be happy with just the focuser control for now. Any advice on how I might get this working with indi/Ekos?

Read More...

Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 6 months ago

Sounds good.

Any chance you can add the ability to home the paramounts? This might be a helpful start up sequence option, or even just a button to make it do this. I believe the command is findHome().

Thanks again!

Read More...

Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 6 months ago

I did another test using the telescope simulator in TSX. Seems to work now. If that works, it might be that users with non-bisque mounts may like this option as it can allow them to take advantage of TPoint. Maybe renaming the driver to TSX or TheSkyX would be apropos to such a case.

Read More...

Greg created a new topic ' Optec Gemini Focuser/Rotator' in the forum. 6 months ago

Anyone doing anything for the Optec Gemini? It operates over both serial and ethernet connections.

Read More...

Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 6 months ago

OK. It seems to be working with the mount attached. I did some basic tests and everything seemed to go well. Parking, unparking, turning tracking on/off, slews, etc all seem fine at least in the "lab". I'll need to dig into this a bit more once my next stint of travel finishes up - probably 2 weeks or so. On my todo list are guiding, astrometry-based slews, and general imaging. Anything else specifically I should test out? I can run a few more tests this weekend but they'll all be indoors.

I've attached the debug log file in case it is helpful.

This is very exciting. Thanks much for getting this going!

Read More...

Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 7 months ago

I am using Ekos. I assume you mean the Paramount driver?

I did a quick test with the Paramount driver against TSX running the mount simulator. I will test with the MX+ tomorrow.

Initial feedback:

- The TCP connection establishes, TSX sees it and registers transactions
- The driver does not actually register as connected and gives the error "unable to connect to telescope: (0).
- The IP and port settings do not persist between restarts of indi server

Read More...

Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 7 months ago

I can test it. Details?

Read More...

Greg replied to the topic 'Bisque Paramount - INDI driver for TSX TCP API?' in the forum. 2 years ago

knro wrote:

Thanks Anat! This would make developing an INDI driver straightforward. I wonder if there is a better way to communicate with the mount directly with the Javascript TCP server?

Can you elaborate on what you might consider to be better? I know the system can execute short programs in javascript. Is that what you mean?

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!