Magnus replied to the topic 'help on indi wiringPi gpio crash' in the forum. 4 months ago

Done, done and done.

The code that limits the dust cover position for the light source was removed on August 17th 2017 :)

Read More...

pauledd thanked Magnus in topic help on indi wiringPi gpio crash 4 months ago
Magnus thanked pauledd in topic help on indi wiringPi gpio crash 4 months ago
Magnus replied to the topic 'help on indi wiringPi gpio crash' in the forum. 4 months ago

Nice catch.

Updated the repository, as this is a good fix.

Read More...

Magnus created a new topic ' indi_sense_aux ?' in the forum. 4 months ago

So in a month or so, I will start updating my obsy to get it ready for the autum, and close to robotic?.....

Initially I would just use indi_wiringpi_gpio to se if microswitches was triggered to see if roof is open close, and mount is parked. At the moment there is no good way to to tell the mount or dome drivers to 'care about' the switch states.
I could implement a update in the mount and dome driver I'm using, but it seams a little hackish.

So what about a indi_sense auxiliary device that mounts, domes, 'and more?', could snoop on to sense state of physical devices.
If there is a superclass with 'bool mountIsParked', 'bool domeIsOpen', 'bool domeIsClosed', etc, then other sensing could be added as a subclass without any changes to the overall device.

I would add a config tab to setup witch wiringpi_gpio pins that checks mount parking and dome state, but other hardware like @Gonzo's gyro to test mount park state 'could' be added as a subclass that implements the 'bool mountIsParked' method.

Is this something others think is good, nice or necessary? Is this a good way in doing this, or is there a better way?

Like to hear what you think.

Read More...

Magnus thanked pauledd in topic help on indi wiringPi gpio crash 4 months ago
Magnus replied to the topic 'help on indi wiringPi gpio crash' in the forum. 4 months ago

First of all, thanks for being so patient and locating the issue.

My servers are remote, so I do not do any dist upgrades remotely.

For me the imaging seson is pretty much over at april 22. as there is no more true nighttime here in at my latitude. I will try to image the next full moon, but then there will be no more imaging before ~ August 22.

I have several things to fix / upgrade in my obsy, and one of them is using wiringpi_gpio to sense roof state, and telescope parking in an attemp to move to a closed loop robotic observatory :)
I will then collect my servers from the remote location, take them home, and get everything up to code.

For now all of INDI works with the setup I have, but as you say it's likely for issues to arise eventually.

Read More...

Magnus replied to the topic 'help on indi wiringPi gpio crash' in the forum. 4 months ago

~/Projects/indi $ git log -1
commit 04a1d39c566f4d84def71176191feb635ebf1afd
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Sun Apr 8 21:36:55 2018 +0300

Fix armhf build on Launchpad



Read More...

Magnus replied to the topic 'help on indi wiringPi gpio crash' in the forum. 4 months ago

gcc -v

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Raspbian 4.9.2-10+deb8u1' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv6 --with-fpu=vfp --with-float=hard --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 4.9.2 (Raspbian 4.9.2-10+deb8u1)


Read More...

Magnus created a new topic ' Starlight Xpress CoStar CMOS Autoguider' in the forum. 4 months ago

I'm getting rid of my OSSAG to get a fully working no hastle guide camera.

I know from other posts that the Lodestar and Lodestar x2 works great. Is this the same for the CoStar? www.firstlightoptics.com/guide-cameras/s...cmos-autoguider.html

The Lodestar is a little to expencive for me, and with a short focal lenght, I do not think I need it.
The CoStar seams like a nice guider, but it is of cource the functionality with indi and ekos that is top priority :)

Read More...

pauledd thanked Magnus in topic help on indi wiringPi gpio crash 4 months ago
Magnus replied to the topic 'help on indi wiringPi gpio crash' in the forum. 4 months ago

Hi.

Sorry to hear that you are having sutch dificulties with this driver.
For some reason I cannot reproduce this still.

I Recompiled the wiringpi library and indi_wiringpi_gpio with no issues.
I have however not updated the wiringpi library in quite a while, as the version i'm using works, and I have not made any dev to the driver in a while.

Just to be sure, I'll upload the library I'm using to google drive. I you have time to test if it makes any difference, that would be great.
Link to the lib drive.google.com/open?id=15V7A0tJ4mlCVVq5E8bYl2UfD7hR6iBTF

Read More...

Magnus replied to the topic 'Building the induino MeteoStation with 3d printed housing' in the forum. 5 months ago

Hi Florian.

It seams to me that the firmware chrashes.

It might be that the code for reading the barometric sensor does not work with MPL3115A2, or possibly wiring / connection issues.

I would suggest using the meteoTEST firmware untill everything is up to code.
The test firmware will fail in a spesific point in the code, making it easyer to debug.

If you get the test firmware up and running without errors, then try to squeeze / pull on the soddered and other connection points, to se if you can make it crash from communication error.

Read More...

Magnus replied to the topic 'Building the induino MeteoStation with 3d printed housing' in the forum. 5 months ago

issue command

locate meteostation_sk.xml
Im thinking it might be in
/usr/local/share/indi

Read More...

Magnus replied to the topic 'DIY Flatfield Dustcover with RPi' in the forum. 6 months ago

I'm not 100% sure, but at the drawing of circle one I see one thing that can possibly be the reason.

The pivot point is not at the point where the angle for the lid arm is. Looks to be half a cm or so offset up to the hole for the link.

Thats the great thing with 3d printing. If first prototype is off, then try again :)

Read More...

Magnus replied to the topic 'DIY Flatfield Dustcover with RPi' in the forum. 6 months ago

If you change circle one so it has a smaller radius than circle two, you will get more range, but loose some lifting force.

Read More...

pauledd thanked Magnus in topic DIY Flatfield Dustcover with RPi 6 months ago
Magnus replied to the topic 'DIY Flatfield Dustcover with RPi' in the forum. 6 months ago

hy-fye1 wrote: Hi Pauledd,
the servod isn't running. How can I do this? There nothing stand in the tutorial.

Markus


Hi. In the tutorial point 5.2 explanes how to install servoblaster
$ cd ~/Projects
$ git clone https://github.com/richardghirst/PiBits.git
$ cd PiBits/ServoBlaster/user/
$ sudo make servod
$ // Follow instructions on screen to add the init script and start servoblaster service (servod)

@Pauledd.

In the youtube video, it looks like you are not using all of the servos travel? perhaps around 80 or 70%?
It looks like you stop the servo travel early at the closed position, so the servo horn does not hit the hinge?

Try using the outer hole for the servo to cap link that you have made. Then reposition the anodized servo horn so it can close the lid with some force, and without extencive binding. It's ok if it slightly binds.

On the picture with the mounting point for the lid, with the circle and question mark.
If you want the lid to have more range. (Now it opens and closes 90 degrees). Then you can make the mount point closer to the pivit point.

If you visualize the circumference of the circle made by the center / pivit point, and the linkage mount point. Then a large circle has the most tourqe, and a smaller circle will have more speed, and in ths case a greater range. (The circumference will be shorter, and the servo will still move the linkage the same length, so the lid will be rotated further around the pivit point).

Hope this makes sense. It's a cool project, and I'm envious of the built in flatlight.
I think next summers upgrades for me will be finnaly mounting the wall mounted flat light :)

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!