John Scherer replied to the topic 'What's next for EKOS?' in the forum. 3 weeks ago

I completely agree, RoMe. Your experience mirrors mine. There is some good information on kstars/indi/ekos out in the wild, but its scattered all over the place. I really love this suite of applications, but man it can sure be frustrating at times ;-)

Read More...

John Scherer replied to the topic 'Astrometry file downloads crashes KSTARS' in the forum. 3 weeks ago

I just ran some quick tests with /usr/share/astrometry permissions at 777 - So far from within ekos/align/options I've been able to download index-4204 through index-4213 and index-4107 through index 4113 with zero problems. In a terminal, nethogs was showing about 2.5 to 3 MB/sec throughput. While typing this, I started index-4203 and its moving along at about 2MB/sec. I allowed it to finish, which it did normally.
I can try these tests with /usr/share/astrometry at its default permissions (755) if that's of interest. Also, If it matters, this is an Ubuntu 16 VM with all the latest patches but not upgraded to 18. 4GB ram and 50gb disk

Read More...

John Scherer replied to the topic 'Astrometry file downloads crashes KSTARS' in the forum. 3 weeks ago

You're saying that kauth is in fact working and that the problem is not with kauth? When I was having this same problem, I changed permissions to /usr/share/astrometry.net to 777 and the problem went away. I'll try it again and report back.

John

Read More...

Alfred thanked John Scherer in topic What's next for EKOS? 3 weeks ago
John Scherer replied to the topic 'What's next for EKOS?' in the forum. 3 weeks ago

I actually reached out to Trevor a while back, asking if he would take look at kstars/ekos for a future video. That being said, even for someone like Trevor I think, kstars/ekos would have a pretty steep learning curve. Installation and configuration are involved. Learning the ins/outs of scheduling observations, and working through any issues that come up (to the point where you feel like you can trust it) can take many weeks, especially if the weather is not cooperating.

From what I’ve read on the forums, I feel that bug fixes & stability issues are critical. Closely behind that would be more/better documentation.

For me, my first point of confusion was where to get information. We have three significant applications, the main one in my mind being kStars and yet most of the information on configuration information for all of those applications is found on the indilib.org forums. This is nothing broken per sa, but from a new user, this can be confusing. I’d love to see one Kstars website, with indi and ekos sections.. but I digress.

There is also a tutorial section on the indilib.org website, however, most of the guides available are on more advanced topics. Nothing for someone just starting out, trying to get things functional. This would be a good place to have a step-by-step guide on getting kstars/ekos installed and configured, and on how to actually schedule a basic observation using ekos. The basic stuff that someone new to this suite of applications might want to know.

More recent, up-to-date videos would be a big help as well. Jasem, I know that you have these in the past but they become out of date after a bit of time and many of yours are years old. Please note, I'm not complaining, nor am I suggesting that you do more. You have many hats to wear, and they have a huge time component to them. Its just the way things are.

From what I have seen, the end result of not having these things is that the forums here become full of people asking the same questions, over and over. And without good documentation that someone can follow – step by step, everyone just answers the same questions over and over. Not time wasted if it's getting more people using it, but it could be optimized I think.
Maybe this community could pull together and do some of this?

Read More...

John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 8 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. 8 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. 8 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. 8 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. 8 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. 8 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. 8 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. 8 months ago
John Scherer replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 8 months ago

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

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!