Have a look at the Display Framerate (Top left button im the display frame). A default installation sets this to MAX, which a RPi cannot handle properly. Reduce to a value that allows smooth operation and you'll be fine.
Read More...
ppapadeas wrote: No need for such complexity! AstroHAT directly powers the RPi4 appropriately and with the right protections in place.
That is a great project! I am considering building a hat with at least 4 12V outputs for my gear. I though that would be something that's available commercially, but apparently not.
jnowat wrote: Perhaps the biggest spec for me on this board is the 12V input to the hat- it powers the Pi, correct? Heck. YES. Much needed. Who has time for 5V when you're mobile? Too much struggle, imo.
lboc wrote: I got it working using the indi_v4l2_ccd but not at that resolution. For instance 1024x768 works.
It all behaves a bit strange and not everything is reproducible. After fiddling around a bit, I couldn't expose at all. It would just sit there never finishing the exposure. I purged teh configuration and reconnected and the driver came up with a different resolution, but I could capture with that. I then set the camera's resolution in the driver (4056x3040) and tried to capture, which forced the server to shut down. I attached a log.
Read More...
Hi,
I am trying to use the new Raspberry Pi HQ Cam. I can access it using the V4l2 INDI driver, but I cannot set it beyond 640 x 480 pixels, the server just shuts down when I try an exposure. Also, pixel size (1.55) doesn't get saved but defaults back to 5.6.
Any ideas how to use this camera properly with INDI?
CS
Sven
Read More...
Hi,
I want to use FireCapture for Planetary/Lunar imaging on StellarMate OS. It runs, but slows the whole system to a crawl. After an action I have to wait a couple of seconds before the GUI becomes responsve again (whole System, not just FC). With AstroBerry, this works fine.
Has anyone tried that and can report?
Thanks
Sven
Read More...
Avocette wrote: could this be added to Astroberry?
To add to the monologue:
getting the value using
FocusBacklashN[0].value
One question remains; do I have to implement the actual compensation myself? I.e. get the value entered in the focus module or the device configuration and add it to the steps to move by hand (if the movement direction is reversed)?
Read More...
I am an idiot. I was trying to build against an ancient version of indi. Sorry for bothering you.
Sven
Read More...
Hi,
when using [1] to drive my motorfocuser, the backlash field in EKOS' focuser tab is greyed out. I had a look at the focus_simulator which uses FOCUSER_HAS_BACKLASH and two methods SetFocuserBacklash() SetFocuserBacklashEnabled(). Since with the simulator the field is no longer greyed out, I tried implementing it; it won't compile.
FOCUSER_HAS_BACKLASH and FOCUSER_CAN_REVERSE are not declared anywhere, and don't show up in the documentation [2] anymore. FACUSER_CAN_REVERSE at least used to work. Has this been removed? Also, FocusMAxPosN isn't declared anymore, although it shows up in the docs. Any ideas?
Sven
[1]
github.com/astrojuergen/indi-microstepper
[2]
www.indilib.org/api/classINDI_1_1FocuserInterface.html
Read More...
EKOS writes the focal length of my guidescope into the FITS header of my lights. Is that is used by astap to determine teh FOV, no wonder it cannot find anything. I am just about done with EKOS. Everytime I touch it another bug pops up.
Read More...