DAVID J EISENLORD replied to the topic 'Optec TCF-S3 broken' in the forum. 5 years ago

Jasem, you are the MAN. It's working fine now for me. When we ever get clear skies I'll try some real focusing but it seems to behave well now.

Question, is there a simple way for me to know when this will make it into the stable repos?

Thanks again,
David

Read More...

DAVID J EISENLORD replied to the topic 'Optec TCF-S3 broken' in the forum. 5 years ago

Seems inoperable now. Waited 15+ min for maybe a time out, didn't get one. In looking at the logs I don't understand the new calls are responses having to do with temperature and "Mode 1". I'm suppose to be in manual mode, just commanding position, nothing to do with temp. Log attached.

Read More...

DAVID J EISENLORD created a new topic ' Optec TCF-S3 broken' in the forum. 5 years ago

Hi, updated KStarts/Ekos/Indi yesterday from the stellermate repos and now my Optec TCS-S3 focuser operation is broken. It was maybe a year since my last update so that's unfortunate as it seems quite a few changes. Very basic operation is broken, it seems to operate in relative mode only, and in only a single direction . I've attached a log with just the focuser in the profile. Connected the focuser and tried to do an absolute move to 1000 from the driver control panel. It does a +1000 relative move to 6200 from its original position of 5200.

David

Read More...

So had you installed originally using apt-get install and had apt-get upgrade before you had the strange behavior? How did you come up with you were running 1.7 of indi?

Read More...

No problem.

I may be wrong however !!

I dug into this a bit more as I've recently gone from using source builds on a Mac to a rasberry pi / stellearmate via the standard repositories.
It appears that for the AP driver the latest pi repository is @ 1.7.3 found via.

deisenlord@IkePI: $ apt-cache show indi-bin | grep Version:
Version: 1.7.3~201805251740~ubuntu16.04.1
Version: 1.1.0-1ubuntu1

Looking this up on launchpad.net/~mutlaqja/+archive/ubuntu/ppa for indi-bin yields a date of 5/25/2018 which should encompass the AP driver updates.
So if you had done an apt-get upgrade I would have thought you would have had the AP fixes.

You might try the above apt-cache show command on your system and see if it says 1.7.3
David

Read More...

I did some looking on github for you and there were a lot of change to the AP experimental driver made in early May. 1.7.0 of indi was dated April 8th so it's not going to include the changes for parking and guiding.
Best,
David

Read More...

You didn't happen to capture any logs from both working/unworking sessions did you? The developers would find them very helpful.

You can click on the Logs button next to the Start button and select "File" as location, then select Mount in both the Ekos and Drivers section. The logs will be written under the .indi directory.

Read More...

fyi, Don't know if you've seen this.

indilib.org/develop/developer-manual/104-scripting.html

This is indi properties vs EKOS but you may be able to get what you want. Your idea of "variables" like $filter, etc is a great idea.

Read More...

DAVID J EISENLORD replied to the topic 'AP experimental' in the forum. 6 years ago

have just verified that that latest build of the Astro-Physics Experimental driver fixes the problem I had with Park Positions. They are all correct for me with a CP3 and V level firmware. I did my test on a source code build under OSX. My stellarmate is still on the old code and still has the problem.

This is probably understood but if not... The driver internally converts ALT/AZ coordinates to equatorial before sending to the mount. This means your lat/long/date/time needs to be correct and sync'd between your mount and indi/kstar or park positions will be wrong.

Thanks @mikefulb !!

Read More...

DAVID J EISENLORD replied to the topic 'Astrophysics Updates' in the forum. 6 years ago

have just verified that that latest build of the Astro-Physics Experimental driver fixes the problem I had with Park Positions. They are all correct for me with a CP3 and V level firmware. I did my test on a source code build under OSX. My stellarmate is still on the old code and still has the problem.

This is probably understood but if not... The driver internally converts ALT/AZ coordinates to equatorial before sending to the mount. This means your lat/long/date/time needs to be correct and sync'd between your mount and indi/kstar or park positions will be wrong.

Thanks @mikefulb !!

Read More...

I have just verified that that latest build of the Astro-Physics Experimental driver fixes the problem I had with Park Positions. They are all correct for me with a CP3 and V level firmware. I did my test on a source code build under OSX. My stellarmate is still on the old code and still has the problem.

This is probably understood but if not... The driver internally converts ALT/AZ coordinates to equatorial before sending to the mount. This means your lat/long/date/time needs to be correct and sync'd between your mount and indi/kstar or park positions will be wrong.

Thanks @mikefulb !!

Read More...