Wim van Berlo replied to the topic 'Pegasus FocusCube and Eqdir - just a heads up' in the forum. 2 hours 47 minutes ago

AstroNerd wrote: Very strange, now that the new driver is available for the Pegasus UPB I have been using that, which also has the FTDI chipset for the focuser part, and I also use a FTDI EQMOD cable, and yet no such issues at all....It just worked straight away, wonder why this works and the focus cube did not..
Anyway glad you sorted.... :) :)

Is that driver included in indi? I use the one that is included. The only thing I did to get the focuser working, was installing the nightly build. When I went back to the stable release after the port "assignment", it stopped working.

Read More...

Wim van Berlo created a new topic ' Pegasus FocusCube and Eqdir - just a heads up' in the forum. yesterday

I recently bought a Pegasus Focuscube to replace my simple DC focus motor / Arduino homebuild. Installation went fine, and worked with the simulator telescope. But when I had the chance yesterday to connect it to my AZ-EQ6 (Eqdir) telescope, I got timeout errors and the focuser didn't work.
It turned out that the focuser uses a FTDI usb chip, the same as my eqdir cable. This causes a conflict in USB ports.
This is how I fixed it:
I created a new rules file in /etc/udev/rules.d called 99-usb-serial.rules
The file contains two lines:

SUBSYSTEM=="tty",ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001" SYMLINK+="telescope"
SUBSYSTEM=="tty",ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015" SYMLINK+="focus"

(Note that for this to work, you need to enter the correct vendor and product ID. If these aren't unique, you may need to add some sort of serial number. Anything so you can differentiate between the eqdir and focuser.)
Then I updated the rules:

sudo udevadm trigger

Rebooted the mount computer (Rock64), just to reset everything, and started indi

indiserver -v indi_eqmod_telescope indi_dmfc_focus indi_asi_ccd indi_asi_wheel

Connected to the drivers from Ekos/Kstars on my windows machine, started up indi and connected. In the Connection tab of the focuser I set the usb port as

/dev/focus

and in the Connection tab of the mount (telescope) I set the usb port as

/dev/telescope

Then save the configurations.
Done.

I hope this can be of use to someone.

Read More...

Wim van Berlo replied to the topic 'Re:Ekos plate solver woes' in the forum. 1 month ago

I used to have a time out problem to. I solved it by decreasing the search radius. If you know that the scope is close to the target, decreasing the search radius can help.
Just a thought.

Wim

Read More...

Wim van Berlo replied to the topic 'subpixel accuracy - autoguiding' in the forum. 2 months ago

If you set the correct FL and pixel size in your guider software, guiding error will be displayed in arcsevonds. Otherwise it will be displayed as pixels.
I'm not aware of any books, specific on guiding. Two general books on astrophotography are
Making Every Photon Count, by Steve Richards, and
Long Exposure Astrophotography, by Allan Hall.
A good online resource is Craig Stark's website:
www.stark-labs.com/craig/articles/articles.html
Stark is the original developer of PHD guiding software.
As for best guiding fl, a general rule of thumb is that the guiding pixel scale shouldn't be more than about 2 times the imaging pixel scale. In practice, if your guiding is too coarse, you can't get good pictures, while if it's too fine, you'll be guiding the noise.
Hope this helps.

Read More...

Wim van Berlo replied to the topic 'subpixel accuracy - autoguiding' in the forum. 2 months ago

You can't set it. It's a result. The guide camera images a star. The guiding software then calculates a star profile (centroid) from the pixel data. The software then calculates where to move the mount, such that the peak of the calculated profile stays at the same position. In theory, the movements may be smaller than one pixel. If the software can kerp the guidong error below one pixel of the guide camera, you have subpixel accuracy.

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

No worry about the side thread, Maudy.
I run arm64. The system works fine with indi, and kstars on windows. It's just that if I run kstars on the Rock, that I have this problem. The keyboard works when I run xrdp with cnv4server and windows remote desktop. But the app screens in ekos freezes. This otoh works fine with xrdp and tightvncserver. But then the keyboard in the kstar's find dialog and ekos configuration manager don't work (q becomes c, etc). The keyboard works fine in libre office and terminal.
For now, I'll continue using indi headless on the Rock.

Read More...

Wim van Berlo replied to the topic 'Abort current exposure when hour angle is greater than 0' in the forum. 5 months ago

I see two problems with your suggestion:
The client could abort a 1 hour exposure even when only a few seconds are left. Discard or keep that exposure? Then what about a few minutes left? What decides?
In your edit, what if the exposure is again one hour, and the flip will occur just before that hour has passed? Should the sequence be halted for almost an hour? That seems precious imaging time lost. It would be easier to force an early flip or a late flip.
Personally I would calculate where in the sequence a flip needs to occur, and insert a forced flip there, between exposures. With one hour exposures, the flip is then no more than half an hour early or late. I think that most setups allow for this margin before the scope hits the pier.

Read More...

Wim van Berlo replied to the topic 'ASI CCD cannot connect if EqMod driver not chosen' in the forum. 5 months ago

Have you tried leaving the mount out altogether? When I shoot darks, I just connect to the ccd and the fw (although I don't really need that). Worked fine last time I imaged (April).

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

Note to self:
I uninstalled all vncservers I could find, as well as xrdp
Then reinstalled xrdp and vnc4server (one of the recommended support packages). This had the following effect
- the keyboard problem in kstars was solved
- starting ekos with simulators froze the ekos screen after it had started an instance of indi. There may have been a message window behind the ekos window that caused this. i could drag windows across the desktop, but they were just not responsive when clicked in.

Uninstalled vnc4server and xrdp and reinstalled xrdp
Installed tightvncserver. The keyboard problem was back, but kstars and ekos worked flawlessly, no unresponsive windows.

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

Thanks again.
Of course I run my machine headless, so there is no session to view. Fortunately the first link you provided contains information regarding this.

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

I downloaded this and the tightvnc viewer for windows. But I still have issues getting this to work. Tigervnc doesn't seem to have an arm64 version. x11vnc installs, but I'm having trouble connecting. Have to figure out the exact cause. It could either be a firewall setting or some services colliding.

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

Can you recommend a good/stable vnc client for windows 8?
I just defaulted on rdp because it worked (so far)

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

Ihoujin wrote: There are known keyboard issues with certain VNC servers, such as with TightVNC. Switch to something like X11VNC or TigerVNC. I use x11vnc. it should resolve your issue.


Unfortunately: no luck
I use windows remote desktop to connect to the linux computer. On this I have xrdp running and tightvncserver installed. When I uninstall tightvncserver and install x11vnc, I can't get a connection with remote desktop. TigerVNC can't even be located. (Note that I run arm64 not armhf on my rock64. Maybe there's no arm64 version of tigervnc?)
I have now uninstalled vnc servers and reinstalled tightvnc. remote desktop allows me to start a session, but the keyboard is still messed up in kstars. Ie back to square 1.

Read More...

Wim van Berlo replied to the topic 'keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

Will try that. Thanks.

Read More...

Wim van Berlo created a new topic ' keyboard messed up in Ekos/Kstars on Rock64' in the forum. 5 months ago

When I use Kstars (v 2.9.3) on my Rock64 the keyboard is all messed up. I connect through Windows Remote Desktop from my laptop. The keyboard works fine in Ubuntu and OpenOffice. It even works fine in Kstars File menu. But when I try to edit a new profile in Ekos or try to find an object in Kstars, the keys are all jumbled, not the standard qwerty layout.
So far, I have used Kstars and Ekos on my laptop (windows), but I now want to use it directly on the Rock64.
Does anyone have a solution to this? Any help appreciated.

Read More...

Wim van Berlo replied to the topic 'Indi on the rocks (a Rock64 to be exact)' in the forum. 8 months ago

I can't really tell how much current it draws. I use mine with an ac adapter. My guess is that it draws about as much as the idroid. Current draw is (mainly) determined by speed of the processor, faster = more power hungry.

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!