Ray Wells replied to the topic 'Indi_asi and indi_xagyl_wheel not playing nice.' in the forum. 6 days ago

Thanks! the hard part was that it worked on intel machines and it wasn't until I installed it on an ARM based system that the problem showed up. Compiler newness I guess.

Read More...

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

Just getting going tonight, finally some stars! As I was getting focused I noticed mine was double exposing. After a while I noticed the "frames" field was on 2. this is the number of frames to average(live stacking) before deciding focus values. If this is a high value it might explain the weird multi exposures.
Hope this helps!

Read More...

Jasem Mutlaq thanked Ray Wells in topic Moonlite focus short limit 2 weeks ago
Ray Wells replied to the topic 'Moonlite focus short limit' in the forum. 2 weeks ago

Got it fixed! Mine uses a variant of Robert brown's firmware and my own super simple one header nano/drv8825 design. I ran some tests from the IDE terminal talking directly to the unit. I think the eaprom data got corrupted somehow and was not saving via indi because when I manually updated max position using terminal commands and resaved to eprom everything seems to be working now.

Thanks for the help!

Read More...

Ray Wells replied to the topic 'Indi_asi and indi_xagyl_wheel not playing nice.' in the forum. 3 weeks ago

I finally nailed it down. TLDR - an oversized serial response to a command was being mishandled by the driver, but only in the arm system which compiled with buffer overrun(stack smashing detection) hack protection.

After running round and round and gathering info, researching the weird error message, groveling a bit and even begging for help, I finally had enough info to realize that though it wasn't failing on the Intel system and was on the Odroid, the key clue and common element was that the failure happened consistently on connect. With this in mind I supposed that it must be mishandling the serial command responses somehow so I started commenting them out one by one until I finally found where I had cheekily change the serial number response to be a long name and version of the emulator. So I shortened that and :woohoo: it worked!
Thanks again to everyone who helped along the way! And @knro, you might want to put a parse limit on filter wheel serial responses to prevent actual stack smashing from evil minded telescopes. :evil:

Read More...

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

Focus needs to be able to percieve(high enough snr) a star to focus. If it's way out it can't figure out which way to move. I think high backlash, as in the case of my o-ring/knob drive SCT version, can also cause fails in the algotrythm. Very unstable skies can also cause it to get confused. This seems like fairly normal robot activity to me. Handy, easily confused, sometimes comically so.

Read More...

Ray Wells replied to the topic 'Moonlite focus short limit' in the forum. 3 weeks ago

Thanks for verifying. Was that from current git? My current theory is corrupt info in my focuser somehow. I'll check it out.

Read More...

Ray Wells replied to the topic 'Moonlite focus short limit' in the forum. 3 weeks ago

I'll probaably find this was my problem somewhere in the junkpile that is my diy rig. It was a frustrating and too short evening trying to get in an hour between workdays on the one clear night.
I can set max to whatever I want and it will still snap back to 1000 limit at actual position. The limit doesn't appear to be stored in the xml and It was working fine a month ago then just got weird. I've been having trouble nailing down the usb map with all these different computers in the mix. It's unlikely but possible the wrong driver poked some packet that set my focuser like this. I'll have plenty of time to fiddle and check during MORE SNOW this weekend.
Thanks again for what you do. I've been lurking in Kstars chat for a week or so. Is there an Indi channel somewhere?
Also(unrelated to op) I already had a couple of arm systems when Stellarmate came out. Is there a way to get that distro or is it primarily using ubuntu mate as mine are?

Read More...

Ray Wells created a new topic ' Moonlite focus short limit' in the forum. 3 weeks ago

Why is Moonlite focus now limited to 1000 positions? It needs to be no limit or 100,000 at least.

Read More...

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

Woot on the testing! I found that if I save the params after setting stuff like that it tends to stay put better on reconnect, so that may be something to check. I have also noticed that the frequency doesn't default to anything until you update it with the button in some instances, which might be related, though I've had so much bad weather I can't remember if we fixed it yet.
re: dual focusers. How about making it change the focuser along with the camera as a setting somehow. It would take some coordinated efforts but seems like the way to go since we can change cams and even (filters now) in the focus page.

My ARM related stack smashing detected issue with my filter wheel has turned out to be a real problem. Keep an eye out for it in the indiserver output if you are using an Rpi or Odroid and get bizarre results.. Apparently any threat of a full buffer gets it upset. I made an issue at master git for it but the problem is rare and I think something in my arduino code could be triggering it somehow. It's at issue 539 if anyone is interested in trying to duplicate the problem.
github.com/indilib/indi/issues/539

Read More...

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

Mount bashing for fun and profit!
My post during the power outage appears to be missing. Must have been the 8 inches of snow that prevented it. My wife is ready for buggy summer months but I'm wishing for more clear 20F nights as I spent most of the season bashing on this upgrade and the rest dodging ice, snow, cloud, rain, sleet, mud, and the occasional windstorm complete with flying cows!

I thought it might be nice to see a screenshot of Ekos for reference here. This is the screen used most for focus. You set the number of steps to take (in or out) when you push the "focus in" or "focus out" in the box labeled "Step:" near the bottom. I usually start "framing" which takes shots as fast as the Exp: will take them and click in and out till I get the best short shots. I've had mixed results from autofocus but if you get close before you invoke it the script will net you the lowest HFR in most cases. Polynomial is used to calculate best position based on previous movements and HFR focus readings for faster results. The box marked "ticks" shows your current position in steps and is a stored variable. You can set an absolute value in the next box and push "Set" to go there, or as above focus in or focus out will move relative and in the amount preset near the bottom.
There's now a filter select in the ccd section which is handy for those of us afflicted with monochrome cameras. The filter wheel is the best excuse for having preset focus points I can think of with even decent filter sets needing a quick retune before use due to the different wavelengths passed, but the ccd tab has an option to re-autofocus on filter change so presets aren't not really needed. Atmospheric and mount condition changes often require a periodic refocus anyway.
Moonlite.cpp has a speed setting code as well as half or full step and also might be worth a look for some Ekos interfacing skeleton to link Onstep to that ekos screen. Others may also yield usable code examples, I've just been using that one for a while since I found a fellow diy'er that had already written the firmware and solved the usb protocol.

i.imgur.com/1fG7G59.png

Read More...

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

I never actually use the saved positions in Moonlite, since focus is condition specific anyway. I don't even bother to home the thing in most cases, just fire it up, hit framing and the hit in or out till the disks get small enough on the preview that I think the auto routine will go and then stop framing and hit autofocus. I usually use full frame to avoid having to select a star. Works pretty good in dark skies.

Read More...

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

Each focuser is 100% dependent on the ratio of the motor steps and connection hardware, and especially in the case of diy this is a very wide range of possibilities. The end result is always the same at the control end. 1 step = one position change. All the belts and gearheads and microstepping are relative to this. Unless a dc motor is used on a focuser I see no reason to ever do timed output either as it would only end up recalculated to steps anyway.

I think somebody in the OnStep group may have used the micrometer term in relation to a project and it stuck.


Just be sure to set max steps to something just short of infinity. :laughing:

Read More...

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

I almost remember something about taking pictures with a telescope, but I'm starting to think it was all a dream.
That's really all you need for a focuser, and maybe a home/reset function though if you have a large enough range its not really needed as it's relative in the end. I often get focus somewhere close by hand before going inside anyway. Keep an eye out for *stack smashing* on the pi. I've been finding sporadic reports just like my problem with various different arm based projects and don't have a cure yet. I know it's an anti hacker function built into gcc but that's about it so far. No idea why my intel stuff is fine but my arm machines both crash with it.

Read More...

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

Ice and snow tonight..yay.
I really think absolute position is the way to go unless you have a (commercial?) focuser that doesn't use a stepper. I just don't see open loop timing being repeatable or an enjoyable process for man or machine.
My arduino nano/drv8825 focuser project used the Moonlite focuser driver instead which uses absolute stepper positioning rather than timing. I haven't tried the onstep built in one as a result but I can see the lure there, just add another driver board to some open i/o and off you go. The Moonlite driver has repeatable position, saved relative and absolute variables and offsets and saved focus points. You might be able to look over that code or integrate it somehow to add the function options. When I got mine done even 40k wasn't enough range for a shaft coupled gearhead stepper like the 24byj-48 or someone using the 10x shaft, so that's something to be considered if you get into coding absolute positioning.

Read More...

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

(last post ghosted...it may return to haunt me)
Nice! I've been wanting that (55-65hz) for a while myself. I'll try it out next chance I get.
Has it been pulled into git master yet?

Read More...

Ray Wells replied to the topic 'Wrong guide rate for AP900 mount - Guide Calibration Failure' in the forum. 1 month ago

Has anyone had any luck with the *Stack smashing* buffer problems? I'm getting the same in indi_Xagyl_wheel on an Arm processors An rpi3 and my new Odroid-xu4 (Armbian/ubuntu 16.04-xfce). I tried the same setup compiled from git on an intel based notebook and it works fine, but I bought the shiny new XU4 to be a high speed usb3 server on the scope mount and really want it to work. It works nice but for this problem which is being extra stubborn.

Read More...

Ray Wells replied to the topic 'Indi_asi and indi_xagyl_wheel not playing nice.' in the forum. 1 month ago

I hunted and hunted for something wrong with the driver or xml read and finally even started an issue at git and asked Jasem about it. He agreed it was a crash. I fiddled around trying to get gdb to give up the answer and did some testing on an intel machine which works looking to compare the two to find it. Since it worked on Intel but not Arm processors I started looking into compiler stuff and found the answer.
***I changed -D CMAKE_BUILD_TYPE="Debug" to ..."Release". And poof! Working driver. ***

I got the instructions from INSTALL and never questioned that line. I am now questioning that line. :D My guess is there was a mismatched missing or otherwise doinked debug symbol that wasn't showing up when I compiled. Of course now I'm expecting at least 3 inches of snow. :dango:
Thanks for helping!

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!