Topics

Indi Driver for Exos2 PMC-Eight

Karl
 

I think I already know the answer, but in case I'm wrong, is the current PMC-Eight driver in Indi compatible with the Exos2, or is it specific to the G11?  I was able to talk to my Exos2 mount via Indi, but its slews were way off compared to using ExploreStars or the ASCOM driver.  For instance, Mars tonight was probably 15+ degrees off.  Hopefully I'm just doing something wrong?

Karl

Frank Kaszubowski
 

Would you like to describe the way you did it and which program you used (cdc, stellarium, kstars)?
Curious.

Frank

Karl
 

I polar aligned the mount using the polar scope and tested that everything was working by connecting to the mount with ExploreStars.  I tried slewing to several targets without choosing any alignment stars, and the mount slewed to them almost perfectly. 

So then I switched to a serial connection and connected my raspberry pi.  I opened Kstars, went to the Ekos menu, created a new profile using "Explore Scientific PMC-Eight" as the mount, and started up the Indi client.  After some initial connection difficulty, I realized the default baud rate was incorrect, switched it to 115200, and got a connection.

I then tried to slew in Kstars.  I tried several objects from the parked position, each time re-parking the mount and clearing the alignment.  The slew was off each time.  I didn't measure exactly, but it seemed to be by about 10-15 degrees each time.  So I parked the mount again, and made a remote connection to the indi client from Stellarium on my laptop.  The slew was off again by what appeared to be the same amount.

Just to check my cable, I unplugged the serial cable from the pi and into my laptop.  After reprogramming the cable back to its default settings (I had inverted DTR per the indi driver instructions), I started up StellariumScope and then slewed to the same objects in Stellarium.  The slews were back on target.

Some additional info in case it's helpful.  The Pi is running Ubuntu Mate.  The Kstars build is 12-21-2018.  The indi version is 1.7.6 from 12-19-2018.  My location in Kstars is slightly off (the difference between downtown and the suburbs), but it should be fine.  In fact, I've used the same pi to control my old Celestron mount just fine.  

Karl

Jerry Hubbell - Explore Scientific VP Engineering
 

Hi Karl,

Thanks for sharing your experience using the INDI driver. It sounds like the default motor count scaling may be fixed to the G11. Does the INDI driver allow you to select any different mounts?  If not then that may be the problem. Hopefully Michael Fulbright will respond to this thread soon to clarify.
--
Jerry Hubbell
Vice President of Engineering

Explore Scientific, LLC.
jrh at explorescientific.com

www.explorescientificusa.com
1010 S. 48th Street
Springdale, AR 72762
1-866-252-3811

Author: Scientific Astrophotography: How Amateurs Can Generate and Use Professional Imaging Data
             Remote Observatories for Amateur Astronomers: Using High-Powered Telescopes From Home



Thomas Olson
 

The current INDI driver for PMC8 is for the LoMandy G11. It uses a AXIS SCALE of...
pmc8driver.cpp:#define PMC8_AXIS0_SCALE 4608000.0
pmc8driver.cpp:#define PMC8_AXIS1_SCALE 4608000.0

Coincidentally, I was looking at how to do this. Compiled a new driver using...
#define PMC8_AXIS0_SCALE 4147200.0
#define PMC8_AXIS1_SCALE 4147200.0

But I am not sure best way to handle these kinds of choices, so submitted the issue to the INDILIB gitbub.

They are discussing it.


As far as a program to keep inverting the DTR in the FTDI firmware... all you need is to make a small
adaptor cable where by you disconnect the PMC8 DTR (pin4) from the computer end and then connect the PMC8 end pin4 to pin5(gnd). Voila!
Then the PMC8 will be in normal use mode permanetly. And not in programmer mode. Whenever it is decided to reprogram the Propeller chip then remove the adapter and use their progamming tools which deals with it the way they want. So with the adaptor you can use any USB2Serial cable without worry.

I saw somewhere where someone said it was a quirky thing with Linux.  The RS232 Standard is to bring DTR (+V) when the port is open. And low (-V) when the port is not open. It is the later use of the DTR to toggle boot modes, program modes etc that created the misuse of the DTR line and thus misunderstanding what happens when connected to legacy serial ports being unaware of the misuse.

Jerry Hubbell - Explore Scientific VP Engineering
 

Thanks Thomas for your work on the INDI driver. Perhaps you can upload the compiled driver to the files section of the forum so that Karl and others interested can use it on their EXOS 2 mounts. That would be great.

Thanks again!
--
Jerry Hubbell
Vice President of Engineering

Explore Scientific, LLC.
jrh at explorescientific.com

www.explorescientificusa.com
1010 S. 48th Street
Springdale, AR 72762
1-866-252-3811

Author: Scientific Astrophotography: How Amateurs Can Generate and Use Professional Imaging Data
             Remote Observatories for Amateur Astronomers: Using High-Powered Telescopes From Home



Thomas Olson
 

OK, done. I hope it works out. I created a directory/folder for INDI DRIVER related Stuff.

There are two tarballs. One for Fedore 28 x64. And one for Astroberry (RASPI)(Ubuntu 16.04.5 LTS).

The only thing changed in these files is the AXIS SCALES. Hopefully whatever other variables are based on the will by acceptable.
Oh, and you may note the driver size is much bigger than the released one. I compiled with DEBUGGING on so all that takes space.

As with the INDILIB relase mentions... this is beta and due diligance observing every move is needed.

Steve Mallia
 

Don't forget about the iEXOS-100.

I have been able to connect to it with my ASIAIR, but I haven't done any imaging with it. Right now I'm assuming that the same issue would exist.  

Karl
 

Thomas,

Thanks for doing that.  I copied the astroberry version over to my pi, running UbuntuMate, and it crashes with the error below.  I'm probably doing something wrong.  This is the error message I get:


2019-01-06T15:47:41: startup: /usr/bin/indiserver -v -p 7624 -f /tmp/indififo6e9bbecc

2019-01-06T15:47:41: listening to port 7624 on fd 3

FIFO: start indi_pmc8_telescope -n "Explore Scientific PMC-Eight"

With name: Explore Scientific PMC-Eight

FIFO: Starting driver indi_pmc8_telescope

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12127 rfd=4 wfd=7 efd=8

2019-01-06T15:47:41: Client 5: new arrival from 127.0.0.1:40352 - welcome!

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

Child process 12131 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #4

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12132 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

Child process 12132 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #5

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12133 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

Child process 12133 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #6

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12137 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

Child process 12137 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #7

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12139 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

Child process 12139 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #8

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12144 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

Child process 12144 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12146 rfd=4 wfd=8 efd=9

Child process 12146 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #10

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12147 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: Terminated after #10 restarts.

Child process 12147 died

Child process 12127 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #1

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12129 rfd=4 wfd=8 efd=9

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK

2019-01-06T15:47:41: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #2

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12130 rfd=4 wfd=8 efd=9

Child process 12129 died

Child process 12130 died

2019-01-06T15:47:41: Driver indi_pmc8_telescope: stderr EOF

2019-01-06T15:47:41: Driver indi_pmc8_telescope: restart #3

2019-01-06T15:47:41: Driver indi_pmc8_telescope: pid=12131 rfd=4 wfd=8 efd=9



Karl

Jerry Hubbell - Explore Scientific VP Engineering
 

On Sun, Jan 6, 2019 at 09:52 AM, Steve Mallia wrote:
Don't forget about the iEXOS-100.

I have been able to connect to it with my ASIAIR, but I haven't done any imaging with it. Right now I'm assuming that the same issue would exist.  
Hi Steve,

The iEXOS-100 PMC-Eight has the same scaling as the EXOS 2
 
--
Jerry Hubbell
Vice President of Engineering

Explore Scientific, LLC.
jrh at explorescientific.com

www.explorescientificusa.com
1010 S. 48th Street
Springdale, AR 72762
1-866-252-3811

Author: Scientific Astrophotography: How Amateurs Can Generate and Use Professional Imaging Data
             Remote Observatories for Amateur Astronomers: Using High-Powered Telescopes From Home



Thomas Olson
 

Hi Karl,
Why the use of a fifo.
I use...
indiserver -v indi_pmc8_telescope
and it returns...
2019-01-06T18:42:05: startup: indiserver -v indi_pmc8_telescope
2019-01-06T18:42:05: Driver indi_pmc8_telescope: pid=1943 rfd=3 wfd=6 efd=7
2019-01-06T18:42:05: listening to port 7624 on fd 4
2019-01-06T18:42:05: Driver indi_pmc8_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2019-01-06T18:42:05: Driver indi_pmc8_telescope: snooping on GPS Simulator.TIME_UTC
2019-01-06T18:42:05: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_PARK
2019-01-06T18:42:05: Driver indi_pmc8_telescope: snooping on Dome Simulator.DOME_SHUTTER

----
Are you running kstars/ekos on the Raspi from remotely?
Don''t need the -p flag for the default port 7624.
When running kstar/ekos on the Raspi I don't start indiserver. I let kstars/ekos handle that.
I only start indiserver on the Raspi when I access it from remote kstars/ekos.
In either case, I don't invoke a FIFO.


I did get error in ekos when I use the diagonal arrows to slew. Something about cans't do while slewing. Hmm. I was in tracking.
But the left right up down arrows didn't cause any error. Just worked. So don't know what the deal with the diagonal buttons is.

Oh, so for some comparisons; indiserver --help says INDI Library 1.7.6. I just wanted to make sure we are on the same revision. Looks like it.

Can you check the rights on the file in /usr/bin/indi_pmc8_*telescope with ls -l.
I get..
astroberry@astroberry:~$ ls -l /usr/bin/indi_pmc8_*telescope
-rwxrwxr-x 1 root root 216980 Jan  5 23:52 /usr/bin/indi_pmc8_exos2_telescope
-rwxr-xr-x 1 root root  58980 Dec 19 11:52 /usr/bin/indi_pmc8_g11_telescope
lrwxrwxrwx 1 root root     25 Jan  6 00:31 /usr/bin/indi_pmc8_telescope -> indi_pmc8_exos2_telescope

Tom

Thomas Olson
 

I don't know anything about the iEXOS-100. I only know what is in the document..

PMC_Eight_ProgrammersReferenceManual_Release1_2018_February_27.pdf
And this table...

Is there a more up to date Programmer's Manual ?

Tom

Jerry Hubbell - Explore Scientific VP Engineering
 

I'm working on it Tom.
--
Jerry Hubbell
Vice President of Engineering

Explore Scientific, LLC.
jrh at explorescientific.com

www.explorescientificusa.com
1010 S. 48th Street
Springdale, AR 72762
1-866-252-3811

Author: Scientific Astrophotography: How Amateurs Can Generate and Use Professional Imaging Data
             Remote Observatories for Amateur Astronomers: Using High-Powered Telescopes From Home



Karl
 

Tom,

I was just starting up indi with the Kstars device manager, and that's what the server log spit out.

Anyway, I started it up from the command line using "indiserver -v indi_pmc8_telescope" as you suggested, and I get the same output as you, followed by:

... Driver indi_pmc8_telescope: stderr EOF

It then repeats 10x and terminates, just like in the previous log I posted.

The rights are all the same as yours.    INDI library version is 1.7.6.  The size of the driver file is the same.  

So I'm not sure of this--is a Ubuntu binary compatible with UbuntuMate?  Seems like it should be, but I don't know for sure, and that's one obvious difference.  Just another thought--is it possible there's another file that the driver is trying to access that doesn't exist on my system?  Maybe a log file it's writing to?

Thanks again for your help.

Karl

Thomas Olson
 

Got me Karl. Try this attached one. I stripped out all the debugging and symbol tables...Just in case that is what is complaining about stderr EOF.

Karl
 

Same result.  Thanks anyway.  Guess I need to either try a different distribution or try to figure out how to compile it myself next time I get a free weekend.

Karl

Thomas Olson
 

What era of Ubuntu Mate do you have.
Please send result of...

uname -a

and

cat /etc/os-release

I may have it in VBOX.

Karl
 

Sure.


uname -a

Linux astropi3 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l armv7l armv7l GNU/Linux


cat /etc/os-release

NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial


- Karl

Stephen Vickers - Explore Scientific Software Developer
 

Are you running Ubuntu on a Raspberry Pi?

Thanks,
Stephen Vickers

Explore Scientific
1010 S. 48th Street
Springdale, AR 72762

o. 866.252.3811
m. 870.654.6995
stephen.vickers@...

On Jan 7, 2019, at 10:01 AM, Karl <es@...> wrote:

Sure.


uname -a

Linux astropi3 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l armv7l armv7l GNU/Linux


cat /etc/os-release

NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial


- Karl

Thomas Olson
 

Karl,

Anybody else doing INDI on Raspi that can test the submitted files?

Tom