John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Thanks azwing! That was indeed my problem. Its funny because I saw the /dev/pts/XXX line before and thought to myself that maybe I should be using that in ekos but for some reason never tried it. Ok, so I have attached two log files, one WITHOUT the udev mods that Dragonlost suggested, and one WITH the mods he suggested.

I need to do more testing, but it seems that Dragonlosts udev suggestion fixed my problem at least. I'll do more testing to comfirm. Here is the /etc/udev/rules.d file I'm using:

# UDEV Rules for Teensy boards, http://www.pjrc.com/teensy/
#
# The latest version of this file may be found at:
#   http://www.pjrc.com/teensy/49-teensy.rules
#
# This file must be placed at:
#
# /etc/udev/rules.d/49-teensy.rules    (preferred location)
#   or
# /lib/udev/rules.d/49-teensy.rules    (req'd on some broken systems)
#
# To install, type this command in a terminal:
#   sudo cp 49-teensy.rules /etc/udev/rules.d/49-teensy.rules
#
# Or use the alternate way (from this forum message) to download and install:
#   https://forum.pjrc.com/threads/45595?p=150445&viewfull=1#post150445
#
# After this file is installed, physically unplug and reconnect Teensy.
#
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"
#
# If you share your linux system with other users, or just don't like the
# idea of write permission for everybody, you can replace MODE:="0666" with
# OWNER:="yourusername" to create the device owned by you, or with
# GROUP:="somegroupname" and mange access using standard unix groups.
#
#
# If using USB Serial you get a new device each time (Ubuntu 9.10)
# eg: /dev/ttyACM0, ttyACM1, ttyACM2, ttyACM3, ttyACM4, etc
#    apt-get remove --purge modemmanager     (reboot may be necessary)
#
# Older modem proding (eg, Ubuntu 9.04) caused very slow serial device detection.
# To fix, add this near top of /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules
#   SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="04[789]?", GOTO="nm_modem_probe_end" 
#

The only difference between mine and the one from prjc's site is I added: SYMLINK+="onstep" to the end of the SUBSYSTEMS line. This creates a symlink from "onstep" to whichever port the teensy attaches to. You can put what ever you want for the name, I just used onstep. Then in Ekos, I just put /dev/onstep as the port.


azwing wrote: Hi Jrsphoto,

When you start slsnif do you get in return the following?

alain@alain:~$ slsnif -n -l log.txt -u -s 9600 /dev/ttyACM0
Serial Line Sniffer. Version 0.4.4
Copyright (C) 2001 Yan Gurtovoy (This email address is being protected from spambots. You need JavaScript enabled to view it.)
Started logging data into file 'log.txt'.
Opened pty: /dev/pts/3
Saved name of the pty opened into file '/tmp/slsnif_pty'.
Opened port: /dev/ttyACM0
Baudrate is set to 9600 baud.

it is the /dev/pts/3 that you need to enter as port in the option tab before connection

Happy to hear the trick with minicom does work, still the problem is here but located



Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Thanks for that bit of info. Its funny because during my testing last night, I starting looking into udev rules because of this page:


I figured that there must be a udev rule for the teensy but I didn't see that on Pauls site. I'll test this out today for sure. Also, in the udev rule he provides is this little bit of info:

# If using USB Serial you get a new device each time (Ubuntu 9.10)
# eg: /dev/ttyACM0, ttyACM1, ttyACM2, ttyACM3, ttyACM4, etc
#    apt-get remove --purge modemmanager     (reboot may be necessary)

So now at least the serial port used by the teensy will remain constant!


dragonlost wrote: This bug reminds me of a bug that I had with the old version of the driver that needed to send an initialization command via the serial link before I could use Indi.

I did not have this problem with a Mega arduino. Only with the Teensy.
To fix this bug you need to install the Teensy udev:

www.pjrc.com/teensy/49-teensy.rules

sudo cp 49-teensy.rules /etc/udev/rules.d/

I hope it will help you.



Read More...

John Scherer replied to the topic 'May I introduce - my Raspberry Pi Controller/Autoguider - TSC' in the forum. 4 months ago

That's a pretty amazing piece of work! It never ceases to amaze me what one person, some skill, a dash of will-power, and raw determination can accomplish!

Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Hi azwing,

I was testing this out tonight, trying to get the serial line sniffer program to work but every time I tried to use it, indi would fail to connect to onstep. If I stopped the serial sniffer program, indi was able to connect to onstep. With that in mind, my results are for the most part, identical to your findings. For some reason, onstep seems to become confused when trying to talk with indiserver. I then tried went into minicom and issue the :GD# or :GR#. A you have noticed, I did not get output for the first command, but the second one I did. After exiting minicom, indiserver loads and connects to onstep.

At present, I don't have this stuff installed on my telescope mount. My mount is a G-11 ( an older Celestron version) and I'm waiting for some parts to arrive so I can finish rebuilding it.. I can't wait to get all this stuff working together. The power of KStars, Ekos, and Indilib/Indiserver is really amazing.

azwing wrote: Jrsphoto,

I experienced this situation on both Teensy and Arduino hardware and found two workarrounds (not solutions).
1) Disconnect and Reconnect the OnStep controller USB which always solved the issue.

2) using a terminal (I use minicom) and issue a command (:GR# or :GD# to see if OnStep responds) and each time I saw OnStep not responding to the first command issue but answering correctly to the second and after that I diconnect terminal and retry a connection with Indi and it works.

I could not yet find out what is wrong and even was not able to find out which conditions produce this error but I am sure of one thing, the error is on OnStep side.
Somehow it happens that the serial communication hangs in a situation where AcK is not recognized.
May be there is some situation where at connection wrong serial charaters are received by OnStep (When I tried with terminal to send random characters I succeded to have OnStep not responding anymore, only after diconnect / reconnect)

Are you in position to test with a serial sniffer, to see if your problem is same I experience?

I use a scprit based on slsniff that I called « teensy »
The script uses slsiff
Opens a pseudo serial on devpts/n (where n can change)
You need to set this devpts/n in Indi Control Panel and connect

see screenshot 1
- Upper Left Terminal : Script call
- Lower Left Terminal : The script
- Lower Right the communication setup in Indi Control Pannel

Screenshot 2
After connection
as you can see the serial communication is printed on the top middle terminal


Hope this helps.

I am still trying to find a real solution but before I send a request to Howard Dutton I prefer to be 100 % sure that problem is on OnStep side



Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Email sent.. Thanks!

azwing wrote: Jrsphoto,

I forgot, if you are interested in getting the slsnif cource code (I modified a bit the original) then send me an Email:
to azwing at free dot fr
and make sure the subject is exactly as hereunder otherwise it will end up in the trash :-)
Subject: OnStep_INDI



Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Thanks AZWING, I've been away for a few day but I'm back now. I'll do some further testing with this. I will also test your serial data analyzer suggestion as well. The one thing I notice is that if I connect my MaxPCB to the raspberry pi with the full indilib installed, it seems to connect every time. But only when I have the MaxPCB connected directly to my computer do I see the connection failures. Have you tested this?

Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

I have been trying to get my OnStep Max connected to indi/ekos but Its failing. When I look at the logs I see this:

[2018-02-22T19:09:11.519 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Trying connection to /dev/ttyACM2 @ 9600 ... "
[2018-02-22T19:09:11.520 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Connecting to /dev/ttyACM2 "
[2018-02-22T19:09:11.520 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Port FD 6 "
[2018-02-22T19:09:11.520 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Connection successful, attempting handshake... "
[2018-02-22T19:09:11.520 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Testing telescope connection using ACK... "
[2018-02-22T19:09:21.630 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Failure. Telescope is not responding to ACK! "
[2018-02-22T19:09:21.630 PST DEBG ][ org.kde.kstars.indi] - LX200 OnStep : "[DEBUG] Handshake failed.

I'm running the latest Alpha version of Onstep from github with the lastest KStars-bleeding / Indi running on Ubuntu 16.04.

This same Onstep MaxPCB works

Read More...

John Scherer shared a photo. 4 months ago
John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Oh, sorry, funny.. TLC = tender, loving, care ;-)

Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

I did think about just breadboarding the layout. It's pretty simple. but in the end, I just ordered the PCBs from Oshpark. I have three boards coming, and I think I'll keep two of them, so if anyone else needs/wants a MaxPCB board, let me know. I think the individual costs/board for me was around $24 USD.

Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 4 months ago

Hi Alain, stopping by this forum post to say hi and offer my assistance, however I can. I was the guy on the onstep forum recently asking about focuser support for indi. I recently acquired Celestron labeled Losmandy G11 mount that I will be converting to OnStep shortly. My MaxPCBs should actually be here today, and the components to build it should be here tomorrow. The mount itself needs a bit of TLC and a few upgrades (mostly the Ovision worm upgrade), which will take a while to get here, and I'm having the stepper motor mounting brackets made as well and they should be done in a few weeks. I should, however, have my MaxPCB board up and running in short order.

Currently, my wife and I live in San Diego CA, but recently bought a 40' motorhome to travel around the USA/CANADA for a few years, in an effort to find some land that we can build a home on (with dark-skys for sure).

Read More...

John Scherer replied to the topic 'INDIWeb - error failed to add drivers to profile' in the forum. 5 months ago

I figured this out. It turns out that my ~/.indi directory was owned by root. I'm not exactly sure how I managed to do that but once I change the ownership back, things started working.

I'm building an OnStep MaxPCB controller for a Losmandy G11 mount and I'm excited to try all this stuff together in a few weeks. I'm running indiserver on a small little Pine64 computer and so far, things seem to be working well.

Read More...

John Scherer created a new topic ' INDIWeb - error failed to add drivers to profile' in the forum. 5 months ago

I've been racking my head trying to figure this out but I'm not having any luck getting indiweb to allow me to add devices to profiles. I've followed the indiweb github instructions to the letter. There does seem to be one error with those instructions however. If you want to install indiweb into the current users home directory you need to do it like this:

$ pip install --user indiweb

Without the --user it would not work for me. I do have indiweb running as my local users in ~/.local but I still can't add devices to profiles. When I do, I get a dialog box saying: error failed to add drivers to profile. Indiweb reports this:
Feb 05 18:06:42 indiserver indi-web[1094]:   File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 1740, in wrapper
Feb 05 18:06:42 indiserver indi-web[1094]:     rv = callback(*a, **ka)
Feb 05 18:06:42 indiserver indi-web[1094]:   File "/home/jrsphoto/.local/lib/python2.7/site-packages/indiweb/main.py", line 147, in save_profile_drivers
Feb 05 18:06:42 indiserver indi-web[1094]:     db.save_profile_drivers(name, data)
Feb 05 18:06:42 indiserver indi-web[1094]:   File "/home/jrsphoto/.local/lib/python2.7/site-packages/indiweb/database.py", line 130, in save_profile_drivers
Feb 05 18:06:42 indiserver indi-web[1094]:     pid = self.add_profile(name)
Feb 05 18:06:42 indiserver indi-web[1094]:   File "/home/jrsphoto/.local/lib/python2.7/site-packages/indiweb/database.py", line 99, in add_profile
Feb 05 18:06:42 indiserver indi-web[1094]:     c.execute('INSERT INTO profile (name) VALUES(?)', (name,))
Feb 05 18:06:42 indiserver indi-web[1094]: OperationalError: attempt to write a readonly database
Feb 05 18:06:42 indiserver indi-web[1094]: 10.1.1.3 - - [05/Feb/2018 18:06:42] "POST /api/profiles/test/drivers HTTP/1.1" 500 766

And this is my services file:
[Unit]
Description=INDI Web Manager
After=multi-user.target

[Service]
Type=idle
# MUST SET YOUR USERNAME HERE.
User=jrsphoto
ExecStart=/home/jrsphoto/.local/bin/indi-web -v
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

All of the indiweb files it should be using are in :~/.local/lib/python2.7/site-packages/indiweb, which I have 665 permissions to (well to that entire structure really). I just don't get whats causing the "OperationalError: attempt to write a readonly database" error!

Any clues?

Cheers

John

Read More...

John Scherer replied to the topic 'Support for BloomSky weather station' in the forum. 2 years ago

Awesome, let me see what I can cobble together ;-) Is this still the best way to get the source and start writing?

indilib.org/forum/general/210-howto-buil...st-libindi-ekos.html

I have kstars-bleeding installed on ubuntu 16.04, if I download the source and compile/install, do I need to be aware of anything? I assume the source version and kstars-bleeding versions can co-exist?

Read More...

John Scherer created a new topic ' Support for BloomSky weather station' in the forum. 2 years ago

I have a Bloomsky Weather station and I was wondering if support could be added to Indilib/Ekos for it. They are GIVING them away to those who would fill out a form here: community.bloomsky.com. Its how I got mine! Its really a nice station and includes a camera and solar panel for power. You can see my weather station data here: map.bloomsky.com/weather-stations/gqBxp6apnJSnnJW3

They recently started the developers program and the info for that is available here: weatherlution.com/bloomsky-api/ - Looks like data is returned from the device in a JSON format..

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!