Hi Eric, Correct, there should not be multiple sections with the same tag. The settings file was corrupted. -Ray

That worked Ray. Thanks. There were 4 <HorizonLimit> sections and multiple <PointingModel>, <Initialize>, and other sections. I assume that shouldn't be the case? Eric

Hello Cytan I wouldn't bother putting anything on the threads. If you are worried about the CW shaft getting stuck to the adaptor, use some anti seize compound and put it on the shoulder of the shaft

There's a way to mirror COM ports on Windows, although it's a little janky and a bit manual. If you go to the com0com project on

Thanks for the warning about WD40. That's another reason to ask here because I'm really not mechanically inclined. cytan

I would say to NEVER use WD-40 on anything on a telescope. It is a PENETRANT, not a LUBRICANT. It will penetrate into circuit boards and ruin them. It will penetrate under paint coatings and destroy

I have a separate device for GPS, but that is primarily to sync the clock. I only connect APCC to the GPS when I need to set up a new site for the first time. I’ve thought about using the MGBox

Btw, when I had the MGBoxV2 on top of the OTA I did have a problem getting GPS lock. I ended up putting at about 6 feet off the ground on a photo tripod near the mount. I need to find a better

I didn't realize you could use the MGBox through the ASCOM observing conditions Hub to get multiple sources for some of the data (that's cool!). I've noticed my MGBox v2 will initially report -273.15

Eh. Definitely something up with the device. Perhaps related to the thing that Jeff mentioned. I've built my own temperhum-type devices using the same sensor that's in the MGBox (the Bosch BME280, and

Denice, As Kenneth and Kevin noted, I used the ASIAIR Pro plate solve using two different ASI cameras on the same scope, an SV115 Triplet APO. Stellarvue's spec was 800mm, but the with the ASI2600

Thanks for the log location. Unfortunately, the MGBox driver logs were utterly useless. They essentially show that something connected, but no details. I went and checked the APCC logs and found

Now that it’s working, the data looks good. I currently have it set up in my home office, where I have independent temperature and humidity data. The results from the MGBox are essentially the

I also recently acquired a MGBoxV2, and it seemed to work fine on serial, but I was getting odd "cached" results for Ascom. Since I also have a UPBv2 with temperature sensor, I compared the values and

ASCOM logs end up under in your user's Documents\ASCOM folder, subdivided by date. This is an odd issue you're having. I also use the ASCOM OCH because I have 3 different devices that source info for

…And now that I’ve seen it work with the ASCOM test app, it’s now working correctly with APCC. I love it when a problem disappears on its own (sarcasm). The only thing that I can think of,

I use a little bit of powdered graphite on the counterweight shaft threads.

Yes, I am connecting to “ASCOM ObservingConditions” as the source. In the “Select Driver” box, I have tried “ASCOM.OCH.ObservingConditions”, followed by setting the ASCOM driver for

also make sure your MGBox application is not connected to the MGBox via serial connection, it will block APCC-- Brian Brian Valente portfolio brianvalentephotography.com

Hi Wade, Under Data Source have you selected Ascom? Phil