Jump to content

Banner.jpg.b89429c566825f6ab32bcafbada449c9.jpg

Possible issue regarding guiding and use of remote desktop


Mark_C

Recommended Posts

Hi all,

Just thought I'd stop by and inform you of some interesting observations I've made relating to dreadful guiding performance I've been experiencing lately. Before these issues occurred, PHD had been working wonderfully for me. Baffled by the sudden degradation in performance, I aimed to solve the issue as soon as possible as I was losing out on valuable imaging time. I went through a list of things that I may have changed to cause these issues, however nothing had been changed recently. I did, however, overlook one thing... the method to which I remotely connected to the laptop controlling the mount.

Usually I would connect via VNC but I was finding it lags and became rather irritating after a while so I switched to remote desktop which I found to be much more responsive and I could use multiple displays of the local computer to control many windows at once. It worked great, however I discovered that remote desktop was the cause of the dreadful guiding performance. My PHD graphs were all over the place and stars were struggling to stay round above 3 minutes in exposures when RDP was being used. I've switched back and VNC and the issues have disappeared. I've tried switching back and to from VNC to RDP multiple times and I am able to repeat the issue.

I suspect it may be something to do with the virtual display adapter being used with remote desktop messing with the imaging drivers and causing the guiding process to work improperly but I can't be entirely sure. It could also be an issue with the QHY5L-II drivers or PHD, or a combination of both. I haven't tried other software so it's difficult to say at this stage where the issue lies, but I just thought I'd make you all aware in case you have this combination of hardware and are experiencing similar issues.

Anyway I hope this helps. I'd also like to wish everyone a merry christmas and happy new year.
Clear skies! :)
Cheers
Mark.
Link to comment
Share on other sites

I shall have to give TeamViewer a go, I've heard nothing but good things about it.

There is definitely an issue with using RDP, whether or not it's lack of processing power or just incompatibility is hard to tell. The laptop being used is a Dell D630 with a Core 2 Duo and 4gb of RAM so I wouldn't have thought there was a lack of processing power.

Link to comment
Share on other sites

RDP is ruled out for me as the observatory PC is running Windows 7 home. I will take a look at TeamViewer though to see how it compares with Nomachine. As I'm using a lowly Netbook CPU resources are limited so if it uses less it could be switch time.

Andrew

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.