DAVID J EISENLORD replied to the topic 'KStars/GPS time confusion' in the forum. 2 days ago

Rebuilt and can verify its fixed.
Best
David

Read More...

DAVID J EISENLORD replied to the topic 'KStars/GPS time confusion' in the forum. 2 days ago

Glad I could help, thanks!

Read More...

DAVID J EISENLORD replied to the topic 'KStars/GPS time confusion' in the forum. 2 days ago

Added log fike

Read More...

DAVID J EISENLORD created a new topic ' KStars/GPS time confusion' in the forum. 2 days ago

I have GPS Nema configured in Indi and picking up time/location from the GPS2IP app on my iphone. The time from the GPS is UTC -5 which is correct for Minnesota central daylight savings time. The time in KStars is UTC -4, which seems extra strange, as UTC -6 is normal central standard time. In the Kstars Indi preference panel I have it configured that GPS & mount update kstars, both time and location. In this case using telescope simulator and its picked up UTC -5 correctly.
Nothing to report in the logs that i can find.
Advice on trouble shooting?







Read More...

You can bring up the console app on the Mac to view your crashes.

Read More...

DAVID J EISENLORD replied to the topic 'KStars 2.9.3 on MacOS crashes during imaging' in the forum. 2 weeks ago

You can run the Console app on your Mac to get the kstars crash dump. Attaching it here would be good. And getting Indi logs will be very important as they will indicate the details of what was going on.

Here's a link on submitting logs.
http://indilib.org/support/logs-submission.html

Fsbof

Read More...

DAVID J EISENLORD replied to the topic 'KStars 2.9.3 on MacOS crashes during imaging' in the forum. 2 weeks ago

The first thing to do is on the Indi control panel summary page, right next to the start / stop button is a "Logs" button. Hit this and turn on verbose logging for all your devices and Indi. On this page there is also an Open Logs button where you can open a log and view and you can also attach it here to a message so developers can take a look and see what your system was doing and what devices you have.

Are you saying the crashes only started with 2.9.3? What version were you running before that didn't crash.

Read More...

DAVID J EISENLORD replied to the topic 'Pyxis Rotator question' in the forum. 2 weeks ago

Your new approach is going to work great Jasem. One caveat, we need to gracefully handle TTY_OVERFLOW as N-1 calls to the read will overflow and the last (containing the F) will complete successfully. Ie.

if (rc == TTY_TIME_OUT)
            return false ;
else if (rc == TTY_OVERFLOW)
{
            LOGF_DEBUG("RES <%s>", res);
            return false ;
}

I'm working on some changes to allow the driver to know if its connected to a 2 inch or 3 inch rotator as the resolution and default step rate are different.
I found out from Optec there is a command CVxxxx that will return the firmware version and from this we can determine the hardware type and hence resolution and
default step rate. I have an prototype running that uses this info to allow the Rotator GUI in Ekos to dynamically update as the rotator rotates and sets the correct default rotation rate.

Will be in touch.
Thanks again for your help.
David

Read More...

DAVID J EISENLORD replied to the topic 'Pyxis Rotator question' in the forum. 2 weeks ago

Good grief your fast !!
Thanks,
David

Read More...

DAVID J EISENLORD replied to the topic 'Pyxis Rotator question' in the forum. 2 weeks ago

Jasem, just had a brainstorm about what the problem is, I think we need to consume a ! character for each microstep the rotator makes and we are only reading/checking every 100ms. Will investigate further and do some testing.
David

Read More...

DAVID J EISENLORD replied to the topic 'Pyxis Rotator question' in the forum. 2 weeks ago

Indeed and glad I'm not crazy :)

I'll let you know what I hear from Optec.
Thanks, David

Read More...

DAVID J EISENLORD replied to the topic 'Pyxis Rotator question' in the forum. 2 weeks ago

Jasem, maybe I'm still confused but this doesn't work for me. Just rebuilt everything from scratch. I cannot get the rotator into debug without hacking ekos_manager.cpp to stop undoing my clicking the rotator into debug. See attached my log screen from the summary indi page and the rotator indi properties page. Notice the messages at the bottom showing that every every time I click "Debug" Ekos undoes this and you see it say Debug disabled.





Also, I tested the rotator under WinDoz with the Optec Rotator command program. All seems fine, it doesn't show the behavior of a lagging acknowledgement. It displays the rotation in "real time" as it rotates. So I'm back to thinking Indi doesn't have the protocol quite correct. I haven't heard from optec yet I just sent the message late friday afternoon.

On the debug issue, what am I missing?
Best, David

Read More...

DAVID J EISENLORD replied to the topic 'Pyxis Rotator question' in the forum. 3 weeks ago

Jasem, took me a while to work around the debug problem. As soon as I would put the rotator in debug it would immediately be taken out of debug automatically. I found the code that does this, I guess to only enable/disable debug when all other drivers are the same. I only had a CCD simulator, or real CD, and no matter what I couldn't get the driver into debug. I could see the debug flags flash on the screen and see "DRIVER DEBUG" was off before it automatically disabled debug again.
Same behavior OSX and Linux.

Anyway I hacked the code to not "re-disable debug" and finally got a debug log. I've attached.
The behavior is the rotator rotates to the position and then there is almost a minute pause until the GUI in the rotator sync's with the new angle.

Read More...

DAVID J EISENLORD created a new topic ' Pyxis Rotator question' in the forum. 3 weeks ago

I've been testing a Pyxis 3 Inch rotator. After setting the rotation angle though the rotator control the rotator moves and then there is a ~50 second delay before the rotator GUI, and the Indi Pyxis control panel updates showing the new angle. I'm assuming this isn't normal as if I set a PA angle in the rotator dialog and start a sequence the rotator rotates but the sequence never starts as it appears to be waiting for the rotator to complete. If I cancel the sequence and bring up the rotator dialog, after a few seconds it updates to the correct angle. I get the same behavior under ubuntu and OSX. I've tried two different configurations of official Optec serial cables and USB dongles. The new integrated type that goes directly from RJ to USB and the older style that goes RJ to 24 pin to USB. No difference. I've enabled debugging for indi and aux but the driver doesn't seem to output anything.

Any ideas?
I haven't looked at the code yet but certainly am willing.
David

Read More...

DAVID J EISENLORD replied to the topic 'ASI120MM, oh I hate to even ask.' in the forum. 3 weeks ago

Thanks guys. I tried the camera under Ubuntu and although its much, much better, it still occasionally has the framing issue at a 1 second exposure. Seems fine at anything above that. Looks like it is unworkable under osx though. I'll look at getting the USB3 version.

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!