Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 weeks ago

@Azwing. Sorry for my unclear statement. And we all know about your recent troubles. Sick is not lazy. :P

I also encountered the never ending slew. It only happens when using plate solving with "slew to target" selected.
If you hit stop it completes and you find it actually did slew to target.
Using "sync" and then manually slewing to target completes slew okay.
Slewing away a bit and hitting slew to target for short changes also completes on mine.

I'm just speculating but this seems like it could be in the Ekos plate solving routine, but if it is it probably should show up for other mount drivers as well.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 weeks ago

--had we done the slew patch at that time, a month ago?

I've also encountered this while in use but haven't had time to look into it nor have I reported it as I've had my hands full recently and couldn't narrow that AND get the other work done in the short times I've had in the field. It did not effect the recent alignment test.

Khalid's remarks sound right. I would add that it has worked properly in the past.

As a temporary workaround, I've been using solve & sync instead of solve & slew, and then hitting the slew button with good results. This could also be a clue to where the problem lies since each routine runs okay standalone. This also works for manual 3 star alignment.

My mount is currently in the shop for either an RTC or GPS addon to correct timing issues. I'm not sure which I'm doing yet.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

Thanks Alain.
I could also try Azwing/master against the Onstep change sometime without too much effort. I'll leave things as they are for the moment and play with it more, but no more double shifts for a while.

I'm not sure this is the right way to go. It relies on changes to code outside the scope of the driver which could leave it broken at a later date, as well as having implications for legacy user and non indi users of OnStep. We could also try a side branch with James's in driver version sometime after I lick my wounds a bit.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

This log follows your instructions including changing to "master" which I decided must mean Indi git since all git repositories have a master branch. There are a couple extra slews I did at the end and a plate solve to see if it did anything. Since you never set a baseline I had none to go by and....
Observations: As before... it went too fast to be solving on my computer, even locally.

I will not do this again until changes are made.

I wrote a test procedure based on my experience using this equipment and 25 years writing test procedures for industrial electronics repair but I won't bore you with it. Too many variables.

File Attachment:

File Name: log_20-33-31.txt
File Size: 2,461 KB


Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

oh hey! I found them. I was looking in .indi/logs and just found them in /home/hawk/.local/share/kstars/logs/2018-08-28 instead! Who wants to read?

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

That is odd. Are you using the current master of KStars, or azwing's fork?

--I had the same thought this morning.I'm using Azwings fork, but maybe there's an error there.

That is odd. Latitude and longitude should be set in EEPROM,

-- I think a bit is set to load "first run" defaults when you download to the arduino, or it was at one time anyway..or it was in my servo software, can't remember.
--! I had a thought on this. It might due to a negative longitude stored in OnStep defaults. If so, maybe the indi driver reads that and gives an error instead of updating somehow? Anyway, the phone app fixed it in eeprom so I'm able to move on and we can tackle that possible bug later.

I need to get those logs working first, then I'll look into the indiserver, and by then it will be dark and we'll try again!
Fingers crossed everybody!

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

Set current alpha command.ino to verify operation of current system in mount.

Enabled full verbose logging in ekos.

Tracking now starts okay using indi
slewed to deneb.
Manual plate solve worked and synced. Slew to solved position was reasonably accurate. Normal operation.

bug 1. If unit unparked but tracking not started. Incorrect error given on slew to target command:
2018-08-29T01:32:54: [ERROR] Object below the minimum elevation limit.
2018-08-29T01:32:54: [ERROR] Error Slewing to JNow RA 20:42:05 - DEC 45:20:53
2018-08-29T01:31:45: [INFO] Mount is unparked.

bug 2. PEC still claims recording, still pops back on if off button pressed. I realize it's not doing anything but it's misleading.


Iinstalled alignment patched command.ino and downloaded to mega.

coords not set in firmware after update:
indi would not set them, longitude error. used phone app to set site coords.

Slewed to deneb and checked focus.
Manual plate solve captured and solved but resulted in a loss of ra/dec position. showing all zeros. then captured but could not solved based on previous 00:00:00 coords
patch breaks manual plate solve.

A manual sync after solving by hand also failed to update, and appears to have crashed the mount.

no logs found after. nice... I wonder where they went? Logging was enabled but I have nothing to show for it? wtf!?
I'll have to redo the whole thing another night as it's time for bed for a 6am start.

****Meanwhile a check of the sync call in OnStep command is needed. I think it never returned from a routine, causing blocking in the mount.

@KNRO -- Unrelated: Kstars is eating memory whenever temporary captures are made ASI drivers/focus module. leaving it looping adds up quickly. Conky reports high memory usage from Kstars. This eventually causes slowdowns and I have to kill it all and restart. I can already hear you telling me to upgrade my 16.04lts system. --my notebook doesn't do it with xubuntu 18.04lts

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

Okay thanks.The freshly downloaded zip is working but I'll do git checkout alpha next time. I knew there was some way, but had forgotten about that command.
I also had to move my pins.classic.h into the new src/pins folder since mine is a one off mega layout that predates the pcb's they have now and is built on a breadboard shield.

Next problem... EnableStepperDrivers(); not declared in this scope. Seems like Azwing mentioned something... That's where I am atm. Scope is set up and I saw bright Vega overhead.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

kbahey wrote: Beta is not a good choice for testing alignment, since Howard added lots of very useful changes in Alpha regarding alignment.

The patch still applies fine on the current Alpha.

$ patch -p1 < /tmp/onstep-plate-solve-align_2018-08-08.txt 
patching file Command.ino
Hunk #3 succeeded at 1991 (offset 2 lines).

Ignore the hunk thing.

Attached is a Command.ino file that is today's Alpha with the patch applied. Rename it from .txt to .ino only, and you are good to go.



Not until I solve this, as the code I have is apparently different.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

@Khalid
I pulled latest alpha and the patch would not apply because the code in command has changed. Do you want to redo that to keep up or should I go with the version I already had previously, which does compare with the patch? It's from the more stable Beta, which was updated from alpha about a month ago. I think we may be chasing an evolving situation unless we stay away from the main (alpha) branch at OnStep.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

@Awing Thanks for the words of support!
That looks terrific!
Masonry after 50 requires child support.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 3 weeks ago

Hi guys. I can test that tonight if it's still clear and I get a chance. I have to go off to a dinner but should get back in time to try. The mount is already setup so I just have to mount the scope and cameras and go. Not converting setups should allow me to get going faster as well.

@kbahey: Are there any changes to your onstep code or can I just use the one I got previously? If so could you attach it?

@Alain: That sounds exciting! can we get a picture or two?

Here's the fruits of our labors. Always good for a boost when things work.
The dumbell nebula(M27) is a nice little supernova remnant and despite lash in the dec axis causing guiding issues, I got enough frames to make this LRGB image. Looking at it always makes me say POW! You can even see the dwarf remnant at its center.
4lum,2red,1green,2blue @60sec ea.
TPO Os6in imaging newtonian
asi178mm /diy wheel using indi(emulating Xagyl)
diy focuser using indi (emulating moolite)
Celestron Omni CG-4 DIY converted to steppers using OnStep/indi/ekos

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 1 month ago

"Start Align" => sends ":A6#", <== If this was active when I did my test it might explain why it crashed the mount and then later refused to slew when I did a three star since it never finished?
@azwing, you might try going back over what I wrote that night to see if anything useful comes of it.

The rain finally stopped for a bit. I'm setting up this evening but since the code is in flux I'm not going to test anything. I am however going to use Jasem's align routine to see what it does without the onstep interaction. It looked like a nice way to use plate solving to get aligned, and now even better now that you can pick your own stars, much needed in my forest and I'd like to be more familiar with the procedure for next time.

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 months ago

@ Alain Yep. That's exactly what happened. I realized it was a better solution so I closed pr#667. Hope you feel better.

I also use Xubuntu (16.04) for Kstars/ekos from Jasem's ppa on the desktop
and indiserver compiled from Azwing's git on an Odroid-xu4 running Armbian 16.04 at the mount.

STILL raining here and hard. Flood watches in effect. :ohmy:

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 months ago

For anybody wanting a quick fix (in the case you have good sky. :P) building from Azwing's git should fix you up until we get it sorted out. Don't forget(like I do) to build 3rd party.
github.com/azwing/indi

@azwing I wish I could bottle this rain and send it. I have friends out in Oklahoma dry as a bone too. Instead I washed the mud off the car today in the rain - a seemingly futile gesture but it was no longer white...or see through. Also, I think we need to go ahead and patch main or lots of crash reports will be forthcoming.

@knro I tried to make a pr at git hub...I hope it wasn't a big mistake or too broad as I've not tried to do that before! - Looks right though, and we have quite a few changes from stable.
Or I pretend to be helping. :jester:

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 months ago

Total agreement on stable releases vs. testing. As per a discussion at Jasem's git, making a testing branch might be helpful..but we'll need to call something stable to do that. :P

Read More...

Ray Wells replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 2 months ago

I saw this message when I was making my filter wheel firmware(to emulate xagyl wheel. I renamed the version to show my changes and got the name too long. Some of the serial buffers cause that error if overflowed. @knro has it on his agenda to recode them one day and trap that. that info might give you guys a direction to look. I had a time finding the error until I realized it was really trying to say serial buffer overflow. It looked like it was in code but turned out to be induce by comms.
www.indilib.org/forum/ccds-dslrs/3109-in...ot-playing-nice.html

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!