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

Hi David, That means there was an error parsing the response from the device. It could be that the data received was corrupted, or in an unrecognized format. If the error persists, it could be

I like the gearbox noise! Don Anderson I think you are mixing apples and oranges. Massive heatsinks are not required on our CP controllers. Microstepper servos need current to hold

Great and informative explanations Roland and thanks. Jeff

All, I am trying to connect a U-Blox7 GPS to v1.8.8.0 of APCC and I get this error message: UpdateLocation. Index and length must refer to a location within the string. Parameter name: Length. The

Oh, and one more thing, at normal tracking, the current consumption is 0.7 amps at 24 volts, so just under 17 watts being sent to the CP controller, of which most goes directly to the motors and

I think you are mixing apples and oranges. Massive heatsinks are not required on our CP controllers. Microstepper servos need current to hold position, otherwise the rotor falls back to one of the