fwiw we use 3D view all the time with both Anydesk and Teamviewer remote access software. never had problems-- Brian Brian Valente portfolio brianvalentephotography.com

Hi, I have an AP 1100 mount. Everything was working fine last night until I did a Go To. I thought my mount was lost and that I accidentally synced on something. I tried syncing on a known

As a data point, I use the 3D view every session and over RDP (over wifi which then ends up going over my home's internal 1Gb ethernet or wifi network) as well. The mini-PC that runs my stuff is a

The 3D view should not require too much 3D resource. I doubt a higher-performance graphics card would make a difference. What kind of desktop resolution are you using when you remote? If it is

Latest version of Windows. Using Windows 10 pro, so I RDP to it via Windows RDP. Latest version of APCC pro. Cat 6 ethernet to the observatory from my office upstairs in my home to the

It is now okay to update to ASCOM 6.5 SP1. Are you using Windows' built-in Remote Desktop? Or some 3rd-party application, like TeamViewer? Windows Remote Desktop is usually more efficient than

I think you may have pegged it. Yes, I am using remote desktop. I will test it out locally, but I could swear that it happens locally and yes, I have a separate card. Maybe I invest in another

One thing you can try is downloading updates to a thumb drive when you have access to internet that isn't metered, and installing them to your computer when you want to do updating. This would allow

That is a sign of a 3D graphics resource or performance issue. Are you using a remote desktop application of some sort? Some remote desktop apps are inefficient at displaying 3D. If not using

Are you running Voyager as Admin and letting it open APCC? I don't have APCC-Pro but it should make no difference. I suspect the above. Hopefully Ray can help but if he cannot replicate the issue

I use APCC pro. I don't leave my 3D view on. I have launched it from time to time to understand that it disconnects from Voyager and causes a problem when it is launched even before I start to slew

Hi (what's your name?) I am a user of Voyager and APCC also. I don't leave the 3D view on (I have an IPCam in my RoR shed in case I want to check where the mount/scope are) but I don't encounter the

Hello, I run Voyager on my computer to run my scopes, cameras, mount and so on and so forth. Whenever I launch the three dimensional view of my scope in APCC to see the scope and mount in operation,

The standard MNEA bit rate is 4800. My own ublox7 works fine at that. /dale

John HELLO, yes those Silver Metallic Sharpie's work great on dark colored surfaces. Like you said it will take a couple coats to see well. And if you need to change the name I have

Ray, Thank you. I’ll try a few different baud rates and see what happens.

Ouch! That's the power adapter that came with the mount. I will see if I can find another one. -- Homepage: http://www.asiaa.sinica.edu.tw/~whwang/ Astrobin

I also purchased the BUBM series of soft sided cases from Amazon after Tony's (Harley Davidson- aka starastronomer on YouTube) review video. What came to be hard was labeling the cases as there's no

Hi Wei-Hao, The mount is seeing many intermittent "Low Power" issues. I counted 17 in the logs you sent me.

Hi Ray, This is the link to the zipped APCC log: https://www.dropbox.com/s/nj83ukryf49r9a8/ApccZip-Academia_Sinica-2021-01-04-104109.zip?dl=0 I had updated the timeout and crosshair update rate