Difference between revisions of "Onstep telescope control"

From Blue-IT.org Wiki

(Created page with "== Max PCB v1.135 == === Teensy 3.6 === Problems with connecting to modem manager: * https://askubuntu.com/questions/1034495/arduino-over-dev-ttyacm0-recognized-but-on-group-t...")
 
 
Line 1: Line 1:
 +
I am using the [https://groups.io/g/onstep/wiki/home Onestep telescope control] in conjunction with a [[Raspberry PI]] and the [[Astroberry Server]] and an old refurbished EQ-5 (when times come, I will post a reference for the project here).
 +
 
== Max PCB v1.135 ==
 
== Max PCB v1.135 ==
=== Teensy 3.6 ===
+
=== Teensy 3.6 and INDI ===
Problems with connecting to modem manager:
+
After dealing with a lot of trouble getting teensy to connect with EKOS/INDI (see [[Astroberry Server]]), I had to do the following things on my astroberry server:
 +
 
 +
1. Problems with teensy connecting to modem manager:
 
* https://askubuntu.com/questions/1034495/arduino-over-dev-ttyacm0-recognized-but-on-group-tty-instead-dialout-ide-fails
 
* https://askubuntu.com/questions/1034495/arduino-over-dev-ttyacm0-recognized-but-on-group-tty-instead-dialout-ide-fails
 +
 +
Uninstall modem manager (it is not needed anyway until you like to use an usb modem):
  
 
  sudo systemctl stop serial-getty@ttyACM0
 
  sudo systemctl stop serial-getty@ttyACM0
Line 11: Line 17:
 
  apt-get remove --purge modemmanager
 
  apt-get remove --purge modemmanager
  
In any case install the udev rules!:
+
2. In any case install the udev rules!:
 
* https://www.pjrc.com/teensy  
 
* https://www.pjrc.com/teensy  
 
* https://www.pjrc.com/teensy/49-teensy.rules
 
* https://www.pjrc.com/teensy/49-teensy.rules
  
I use these rules:
+
I use these special rules which ensure, that the teensy always get the same device address: "/dev/onstep":
 
* https://www.indilib.org/forum/development/1406-driver-onstep-lx200-like-for-indi.html?start=144#23792  
 
* https://www.indilib.org/forum/development/1406-driver-onstep-lx200-like-for-indi.html?start=144#23792  
  
Line 23: Line 29:
 
  KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", MODE:="0666"
 
  KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", MODE:="0666"
  
So you can use as teensy device in Ekos:
+
So you can use as teensy device in Ekos for the LX200 OnStep:
  
  /dev/onestep
+
  /dev/onstep
  
 
== Indi driver ==
 
== Indi driver ==
 +
There is an interesting thread about the Indi driver LX200 Onstep in the indilib forum.
 
* https://www.indilib.org/forum/development/1406-driver-onstep-lx200-like-for-indi.html?start=180
 
* https://www.indilib.org/forum/development/1406-driver-onstep-lx200-like-for-indi.html?start=180

Latest revision as of 17:33, 29 December 2018

I am using the Onestep telescope control in conjunction with a Raspberry PI and the Astroberry Server and an old refurbished EQ-5 (when times come, I will post a reference for the project here).

Max PCB v1.135

Teensy 3.6 and INDI

After dealing with a lot of trouble getting teensy to connect with EKOS/INDI (see Astroberry Server), I had to do the following things on my astroberry server:

1. Problems with teensy connecting to modem manager:

Uninstall modem manager (it is not needed anyway until you like to use an usb modem):

sudo systemctl stop serial-getty@ttyACM0
sudo systemctl disable serial-getty@ttyACM0

and

apt-get remove --purge modemmanager

2. In any case install the udev rules!:

I use these special rules which ensure, that the teensy always get the same device address: "/dev/onstep":

ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789A]?", ENV{MTP_NO_PROBE}="1"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789ABCD]?", MODE:="0666" SYMLINK+="onstep"
KERNEL=="ttyACM*", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789B]?", MODE:="0666"

So you can use as teensy device in Ekos for the LX200 OnStep:

/dev/onstep 

Indi driver

There is an interesting thread about the Indi driver LX200 Onstep in the indilib forum.