Hy Murveit replied to the topic 'focus and Polar align "issues"' in the forum. 13 hours 22 minutes ago

You are right. That got released after 3.3.8.


Hy Murveit replied to the topic 'focus and Polar align "issues"' in the forum. 20 hours 26 minutes ago


The stretch button (fifth from the left, "Toggle Stretch") should work whether or not the auto-stretch is turned on/off by default. The latter just decides the initial state. The toggle shouldn't care whether the initial state is on or off, just toggle whatever it is.
If you ever confirm that the buttons don't work depending on that auto-stretch config parameter, let me know.



Hy Murveit replied to the topic 'For those with focus issues' in the forum. 21 hours 10 minutes ago

As Wouter said, he, Jo and I are iterating on improving this algorithm, but would be happy to get additional testers.
I think things are better with the latest nightlies (the most recent one will show "v3" on the menu where you select the algorithm: "Linear (Experimental v3)"

One of the weaknesses is that you need to select an appropriate step size--ultimately we should have a "wizard" for that, but until things are more mature, I think it should be done by hand.

Søren: As I am not familiar with your particular configuration I can't recommend anything, but probably each step size might be the kind of small steps you'd use manually when you were somewhat close to focus. If you go too small, though, the algorithm can get caught in the noise of the focus system.

Søren: I suspect you weren't using the latest release, because there was a bug in there a week or so ago that caused that last output line. Are you sure you're using v3?

Pit: join in!

Anyway whoever does want to provide feedback, please have logging to a file turned on with at least verbose, file and focus logging enabled.

Note, you don't have to waste a nice evening to do these tests. If there are clouds, so it's not the ideal evening to image, but there's a patch of clear sky, you can try a few autofocus rounds pointing at that patch.



Hy Murveit replied to the topic 'ttyUSB0 issues on OnStepp and raspi4' in the forum. 21 hours 35 minutes ago

I didn't mention it above, but it's likely you have to reboot after you modify the /lib/udev/rules.d/99-observatory.rules file for the change to take effect.


Hy Murveit replied to the topic 'ttyUSB0 issues on OnStepp and raspi4' in the forum. 21 hours 37 minutes ago

I'm not familiar with OnStep, but I am a bit (unfortunately) familiar with ttyUSB0 issues. Whenever you have more than on serial device, I believe it's wise to use symbolic links rather than the specific device filenames that linux seems to randomly assign.

So, first, if you setup, and you're having this issue, figure out which device your OnStep was assigned. E.g. in a terminal type:
ls /dev/ttyUSB*
and perhaps you'll see /dev/ttyUSB0 and /dev/ttyUSB1.

Then you know your device is one of the two, and you can change the port (in your picture above) to the right device (test the both) and see if things are working.
If this doesn't work, sorry, I guess I misunderstand and ignore the rest of this post. If it does, continue.

The above is a short-term solution, though, because you probably don't want to do this every time you boot up your RPi.
Assuming though that this solved your problem in the short term, the next step is to permanently assign symbolic names to your OnStep device.

I have only done this on Raspbian, so I can't say whether the advice below will work on your OS (not sure what you're using) but this is what I do on Raspbian:

I have two serial devices (focuser and mount) that are randomly assigned, one to /dev/ttyUSB0 and one to /dev/ttyUSB1. To avoid this randomness,
I create symbolic device names for them by adding the following four lines to /lib/udev/rules.d/99-observatory.rules

# MoonLite Focuser
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A601WGWD", MODE="0666", SYMLINK+="focuser"
# EQMod Mount
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="FTA663FB", MODE="0666", SYMLINK+="mount"

You'll always want to use "usb" and "0666" above, but the other magic strings in quotes (after idVendor, idProduct, and serial) come from the commands below:

(a) the output of the 'lsusb' command gives you vendor and product:

> lsusb
Bus 001 Device 008: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

(b) you can get the value needed for "serial" from the below command:

# I'm sure the moonlite is connected to USB1 right now
udevadm info -a -n /dev/ttyUSB1 | grep '{serial}'

(c) Of course, the SYMLINK name (in my case "mount" or "focuser" is arbitrary, but once you have chosen it, you
set your port for your OnStep to that, e.g. /dev/focuser


Hy Murveit replied to the topic 'focus and Polar align "issues"' in the forum. 22 hours 4 minutes ago

Just having gone through this thread, I wanted to comment on a couple of things, perhaps redundantly.

1- When I set up Ekos for the first time (e.g. I've helped a few friends locally) I always check "independent window" in the FITS, INDI, and EKOS sections of the Options window (which e.g. you can get to in the bottom right corner of the catpure tab and in many other places). IMHO this should be the default configuration.

2- Re stretching in the focus tab. Yes, you can (a) click the "auto stretch" button in FITS settings. Should be the default, if it isn't, but it can be turned off. Also, though, (b) whenever you mouse over that image window in the focus tab, (or the other embedded image display windows like in the align & guide tabs) there is a floating icon menu that appears near the top of the image, which allows you to (from left to right icons) to zoom in, zoom out, default zoom, zoom-to-fit, TOGGLE STRETCH, ... So, you can click the toggle stretch button when the image isn't stretched, and a stretched version of the image should appear. There is no way, though, to adjust the stretch in that tab with sliders like you can with the fitsviewer.


Hy Murveit replied to the topic 'Memory Leak' in the forum. 1 week ago

I'm curious if there's a common thread among the people who experience this leak (e.g. I still can't replicate it, and as of recently, I don't believe Jasem could either--I know he's hard at work looking into it). For instance, are you all DSLR users? RGB camera users with debayering, etc?

If you experience this leak, could you please post more details about the minimum configuration you use that will trigger this leak.
camera model and type, e.g. Canon DSLR with resolution WxH, ZWO 1600 monochome resolution WxH, ...
fits, raw, ???
Running fitsviewer while you capture?
Processor (e.g. RPi4) on what OS (Raspbian? Ubuntu 18.04? Stellarmate?)
How did you install KStars (Stellarmate, AstroPi3, AstroBerry, ...)
What release are you using when you observed the leak? (released 3.3.9, nightly at what date),

Also, can you tell how much is leaked per image? (e.g. by running the linux command 'ps aux | grep kstars" after every 5th or 10th image for as long as makes sense) and how that relates to the size of the image your camera captures



Hy Murveit replied to the topic 'Multiple Zwo Cameras' in the forum. 2 weeks ago

Thanks you two. It turned out that plugging the 290 into the 1600 did the trick (whereas plugging both into the powered hub didn't work).
Love this forum!


Hy Murveit thanked Doug S in topic Multiple Zwo Cameras 2 weeks ago

Hy Murveit created a new topic ' Multiple Zwo Cameras' in the forum. 2 weeks ago

I'm trying to configure Ekos with a ZWO 1600 for imaging, and a ZWO 290 for guiding.
I don't see how to do that. In the configuration setup, I selected ZWO CCD for both Guider and CCD in the Profile editor.
I connect both cameras, start up Indi, but we only get one camera tab in the indi window, and don't think we have the guider connected.

Is this possible? How should we proceed?


Hy Murveit replied to the topic 'Disaster with the last update.... - SOLVED' in the forum. 2 weeks ago

Glad you fixed it. Funny thing is that a similar thing just happened to me the other day--my Moonlight focuser wasn't working and I discovered that even though the indi focuser driver tab showed movement, the physical focuser was not moving. It turned out I hadn't connected the serial cable between the focuser-controller and the focuser-motor. I was about to respond to you asking if you might have bad cables.

I guess many of these focusers don't really have an accurate mechanism for knowing their current position.


Jose Corazon thanked Hy Murveit in topic Memory Leak 2 weeks ago

Hy Murveit replied to the topic 'Memory Leak' in the forum. 2 weeks ago

I was wondering, for the folks with the memory leak--do you have the option "Single Preview Tab" checked? (I think you should have it checked).
You find that under the KStars options, then FITS, then it's a checkbox on that page.
I believe that KStars/fitsviewer would leak tabs if you had it unchecked (perhaps it should limit the number of tabs, I don't know if it does or doesn't).