Date   

Re: My AP1100 CP4 died (I think ..., need confirmation)

Cheng-Yang Tan
 

Any suggestions as to what to test?

I thought I had at least checked that some of the USB cabling, PS, computer were ok with the Mach1.

cytan

On Saturday, May 29, 2021, 11:51 PM, Roland Christen via groups.io <chris1011@...> wrote:

It's highly unlikely your CP4 died.

You had a motor stall. Possible poor connection of your motor cable. Possible poor connection to your power supply.

Rolando



-----Original Message-----
From: Cheng-Yang Tan via groups.io <cytan299@...>
To: main@ap-gto.groups.io
Sent: Sat, May 29, 2021 11:36 pm
Subject: [ap-gto] My AP1100 CP4 died (I think ..., need confirmation)

Hi guys,
   I think my AP1100 CP4 died this evening. The first symptom was that my CP4 wasn't recognized with the USB connection. But I could talk to it via TCPIP (my backup). But APCC couldn't move the DEC. It gave the error message in APCC shown in the attachment. I thought it could be the latest Win update, USB port, USB cable, bad motor cable, Power supply etc. I checked that the CP4 module LED was lit red (and it was). I power cycled the CP4 a few times to be sure that it wasn't hung up on something. That didn't fix the problem.

  After two hours of monkeying around, I gave up and brought everything back inside. Since I have a Mach1GTO with its CP4, I used the same USB cable, power supply and computer to verify whether any of them were the problem. These tests showed that the same computer, USB cable and PS worked with my Mach1GTO CP4.

  So after the Mach1GTO tests, I wanted to test the AP1100 CP4 again. But this time the LED didn't light up.

  Well, I guess the CP4 must have died a slow painful death :(  Is there anything else I should or can test before I ask for an RMA to ship it back to AstroPhysics for repair?

cytan

--
Roland Christen
Astro-Physics


Re: My AP1100 CP4 died (I think ..., need confirmation)

Roland Christen
 

It's highly unlikely your CP4 died.

You had a motor stall. Possible poor connection of your motor cable. Possible poor connection to your power supply.

Rolando



-----Original Message-----
From: Cheng-Yang Tan via groups.io <cytan299@...>
To: main@ap-gto.groups.io
Sent: Sat, May 29, 2021 11:36 pm
Subject: [ap-gto] My AP1100 CP4 died (I think ..., need confirmation)

Hi guys,
   I think my AP1100 CP4 died this evening. The first symptom was that my CP4 wasn't recognized with the USB connection. But I could talk to it via TCPIP (my backup). But APCC couldn't move the DEC. It gave the error message in APCC shown in the attachment. I thought it could be the latest Win update, USB port, USB cable, bad motor cable, Power supply etc. I checked that the CP4 module LED was lit red (and it was). I power cycled the CP4 a few times to be sure that it wasn't hung up on something. That didn't fix the problem.

  After two hours of monkeying around, I gave up and brought everything back inside. Since I have a Mach1GTO with its CP4, I used the same USB cable, power supply and computer to verify whether any of them were the problem. These tests showed that the same computer, USB cable and PS worked with my Mach1GTO CP4.

  So after the Mach1GTO tests, I wanted to test the AP1100 CP4 again. But this time the LED didn't light up.

  Well, I guess the CP4 must have died a slow painful death :(  Is there anything else I should or can test before I ask for an RMA to ship it back to AstroPhysics for repair?

cytan

--
Roland Christen
Astro-Physics


My AP1100 CP4 died (I think ..., need confirmation)

Cheng-Yang Tan
 

Hi guys,
   I think my AP1100 CP4 died this evening. The first symptom was that my CP4 wasn't recognized with the USB connection. But I could talk to it via TCPIP (my backup). But APCC couldn't move the DEC. It gave the error message in APCC shown in the attachment. I thought it could be the latest Win update, USB port, USB cable, bad motor cable, Power supply etc. I checked that the CP4 module LED was lit red (and it was). I power cycled the CP4 a few times to be sure that it wasn't hung up on something. That didn't fix the problem.

  After two hours of monkeying around, I gave up and brought everything back inside. Since I have a Mach1GTO with its CP4, I used the same USB cable, power supply and computer to verify whether any of them were the problem. These tests showed that the same computer, USB cable and PS worked with my Mach1GTO CP4.

  So after the Mach1GTO tests, I wanted to test the AP1100 CP4 again. But this time the LED didn't light up.

  Well, I guess the CP4 must have died a slow painful death :(  Is there anything else I should or can test before I ask for an RMA to ship it back to AstroPhysics for repair?

cytan


Re: DEC error message

Tim Morrill
 

Yep. It’s.
Helo4@...


Re: DEC error message

Roland Christen
 

I tried to send you some instructions but I don't have your e-mail address. Can you send me an e-mail please?

Roland Christen
chris1011@...



-----Original Message-----
From: Tim Morrill via groups.io <helo4@...>
To: main@ap-gto.groups.io
Sent: Sat, May 29, 2021 4:10 pm
Subject: [ap-gto] DEC error message

Last week I had a RA problem. It had a very loud clicking noise but that was fixed after following Roland‘s advice with switching the cables. But just had another clear night and went to test. And I am now  getting this error. (see attached screenshot) everything seems to working and sounds good, except it won’t park and it is completely lost.
 

--
Roland Christen
Astro-Physics


Re: DEC error message

Roland Christen
 

?



-----Original Message-----
From: Tim Morrill via groups.io <helo4@...>
To: main@ap-gto.groups.io
Sent: Sat, May 29, 2021 4:34 pm
Subject: Re: [ap-gto] DEC error message

Yes. 

--
Roland Christen
Astro-Physics


Re: DEC error message

Tim Morrill
 

Yes. 


Re: DEC error message

Roland Christen
 

We sent you two new cables. Did you receive them and did you put them on your mount?

Roland Christen
Astro-Physics Inc.


-----Original Message-----
From: Tim Morrill via groups.io <helo4@...>
To: main@ap-gto.groups.io
Sent: Sat, May 29, 2021 4:10 pm
Subject: [ap-gto] DEC error message

Last week I had a RA problem. It had a very loud clicking noise but that was fixed after following Roland‘s advice with switching the cables. But just had another clear night and went to test. And I am now  getting this error. (see attached screenshot) everything seems to working and sounds good, except it won’t park and it is completely lost.
 

--
Roland Christen
Astro-Physics


Re: APCC compatibility with ASCOM 6.5 SP1 (?)

Ray Gralak
 

There wasn't a "compatibility problem" between APCC and ASCOM. There was a severe bug in the ASCOM platform 6.5 that caused an issue translating between J2000.0 and local apparent RA/Dec coordinate systems. This was fixed in ASCOM Platform 6.5SP1.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Stelios via groups.io
Sent: Saturday, May 29, 2021 2:03 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC compatibility with ASCOM 6.5 SP1 (?)

I know that there have been reports (a fair time ago) of problems with APCC and ASCOM 6.5. As a result, I am
WAY behind in both APCC updates and ASCOM (I am on 6.4) updates, as I did not want to introduce problems in
a simple and working system.

OTOH, I now see that ASCOM 6.5 SP1 is the new standard release of that platform. Does this fix issues with
APCC compatibility? Can I go ahead and update my system (both ASCOM and APCC)?

I'd rather err on the side of caution, but I also know that staying too far behind current releases is not a good idea,
so... what's the verdict?


DEC error message

Tim Morrill
 

Last week I had a RA problem. It had a very loud clicking noise but that was fixed after following Roland‘s advice with switching the cables. But just had another clear night and went to test. And I am now  getting this error. (see attached screenshot) everything seems to working and sounds good, except it won’t park and it is completely lost.

 


APCC compatibility with ASCOM 6.5 SP1 (?)

Stelios
 

I know that there have been reports (a fair time ago) of problems with APCC and ASCOM 6.5. As a result, I am WAY behind in both APCC updates and ASCOM (I am on 6.4) updates, as I did not want to introduce problems in a simple and working system. 

OTOH, I now see that ASCOM 6.5 SP1 is the new standard release of that platform. Does this fix issues with APCC compatibility? Can I go ahead and update my system (both ASCOM and APCC)? 

I'd rather err on the side of caution, but I also know that staying too far behind current releases is not a good idea, so... what's the verdict? 


VIDEO - Mach2 Right Ascension Belt Adjustment

Harley Davidson
 

Astro-Physics Mach2 Equatorial Mount Right Ascension Belt Adjustment
https://www.youtube.com/watch?v=2YMXr6ewAjs

This is a followup video to the vibration I had on my Mach2 mounts RA axis.

tony


Re: APCC Environmental Settings do not stick #APCC

Ray Gralak
 

Hi Eric,

That worked Ray. Thanks.
There were 4 <HorizonLimit> sections and multiple <PointingModel>, <Initialize>, and other sections. I assume
that shouldn't be the case?
Correct, there should not be multiple sections with the same tag. The settings file was corrupted.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Eric Claeys
Sent: Friday, May 28, 2021 4:21 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Environmental Settings do not stick #APCC

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


Re: APCC Environmental Settings do not stick #APCC

Eric Claeys
 

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


Re: Question: How do I safety replace the CW shaft adapter (got it off, grease?)

Don Anderson
 

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 and/or the mating surface of the adaptor. Better yet, use one of APs Delrin washers and you will never have a problem. If you are worried about wearing out the threads (could take 50yrs to do that) you could put a small amount of 3 in One oil on the threads. If you want an anti seize compound, Christopher has recommended a god one. Also, if you are near a marine store, you can get anti seize compound at any marine or automotive supply store.
My advice is worth as much as Christopher's!Emoji

Don Anderson


On Friday, May 28, 2021, 03:42:19 p.m. MDT, Cheng-Yang Tan via groups.io <cytan299@...> wrote:


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

cytan

On Friday, May 28, 2021, 04:38:55 PM CDT, Christopher Erickson <christopher.k.erickson@...> wrote:


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 them. It will penetrate into optical assemblies and contaminate them. It will destroy older-style coatings on vintage lenses. It is infamous for penetrating past primers and ruining ammunition stores. Used properly to break free rusted nuts on trucks and stuff is what it is meant for.

A small drop of Break-Free CLP is an excellent anti-galling lubricant for aluminum and stainless threaded things. Wipe away any excess that comes out of the threads. If you leave too much of it in threads, it could wick out a bit and spread around. Although it is not a penetrant.

I hope this helps.

-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Fri, May 28, 2021, 6:07 AM M Hambrick <mhambrick563@...> wrote:
I use a little bit of powdered graphite on the counterweight shaft threads.


Re: APCC Pro with MSGBox V2

Dale Ghent
 

On May 28, 2021, at 17:30, W Hilmo <y.groups@hilmo.net> wrote:

I suppose that using both GPS devices would allow me to use one of them for time sync and the other for APCC location data (since two pieces of software cannot connect to one GPS at the same time).
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 Sourceforge:

https://sourceforge.net/projects/com0com/files/com0com/3.0.0.0/

and download the hub2com and com0com software, there's a ReadMe in the hub2com zip file that details how to set up a COM port mirror. An example is given using a GPS device. This is handy for read-only applications such as this.

So, if you're really stuck between a rock and hard place and need something that lets you read the GPS device via COM port with 2 (or more) different apps, then this might get you out of those woods.


Re: Question: How do I safety replace the CW shaft adapter (got it off, grease?)

Cheng-Yang Tan
 

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

cytan

On Friday, May 28, 2021, 04:38:55 PM CDT, Christopher Erickson <christopher.k.erickson@...> wrote:


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 them. It will penetrate into optical assemblies and contaminate them. It will destroy older-style coatings on vintage lenses. It is infamous for penetrating past primers and ruining ammunition stores. Used properly to break free rusted nuts on trucks and stuff is what it is meant for.

A small drop of Break-Free CLP is an excellent anti-galling lubricant for aluminum and stainless threaded things. Wipe away any excess that comes out of the threads. If you leave too much of it in threads, it could wick out a bit and spread around. Although it is not a penetrant.

I hope this helps.

-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Fri, May 28, 2021, 6:07 AM M Hambrick <mhambrick563@...> wrote:
I use a little bit of powdered graphite on the counterweight shaft threads.


Re: Question: How do I safety replace the CW shaft adapter (got it off, grease?)

Christopher Erickson
 

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 them. It will penetrate into optical assemblies and contaminate them. It will destroy older-style coatings on vintage lenses. It is infamous for penetrating past primers and ruining ammunition stores. Used properly to break free rusted nuts on trucks and stuff is what it is meant for.

A small drop of Break-Free CLP is an excellent anti-galling lubricant for aluminum and stainless threaded things. Wipe away any excess that comes out of the threads. If you leave too much of it in threads, it could wick out a bit and spread around. Although it is not a penetrant.

I hope this helps.

-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   


On Fri, May 28, 2021, 6:07 AM M Hambrick <mhambrick563@...> wrote:
I use a little bit of powdered graphite on the counterweight shaft threads.


Re: APCC Pro with MSGBox V2

W Hilmo
 

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 for GPS, but I’m torn on where to place it.  For best GPS reception, it should have an unobstructed view of the sky.  But for the most accurate temperature information, it should be out of the sun during the day.  These two things are somewhat exclusive from each other.  Of course sun hitting the MGBox at night, when I am either building or using a pointing/tracking model is probably not a problem.  I suppose that using both GPS devices would allow me to use one of them for time sync and the other for APCC location data (since two pieces of software cannot connect to one GPS at the same time).

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Jeffc
Sent: Friday, May 28, 2021 1:22 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro with MSGBox V2

 

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 solution for a “portable” setup.  

 



On May 28, 2021, at 1:10 PM, Ken Sablinsky <kensablinsky@...> wrote:



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 degrees in SGP when I first connect it (with 0's for the pressure and humidity), but within a few seconds (maybe up to 10-20 seconds?), it switches to the proper temp and shows the rest of the data.  This is going through either the ASCOM MGBox driver or through the observatory conditions hub.  I've never seen the issue when I run the native MGBox software, so I just thought it takes SGP a bit longer to get the data from the device and properly display the correct temp.

 

-Ken

 

On Fri, May 28, 2021 at 12:30 PM Dale Ghent <daleg@...> wrote:


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 a variant of the same named BMP280) and it's very straight-forward i2c stuff. The Arduino library for it emits the temp in Celsius. Maybe the MGBox app works in Kelvin for some reason. Who knows, but glad it works for you now.

> On May 28, 2021, at 12:57, W Hilmo <y.groups@...> wrote:
>
> 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 this interesting little section:
>
> 0000061 2021-05-28 08:28:57.875:       Info,   Environmental, EnablePolling = True
> 0000062 2021-05-28 08:28:57.877:       Info,   Environmental, Polling Interval = 10 (secs)
> 0000063 2021-05-28 08:28:57.879:       Info,   Environmental, DeviceType = ASCOM ObservingConditions
> 0000064 2021-05-28 08:28:57.881:       Info,   Environmental, ObservingConditions ASCOM Driver = ASCOM.MGBox.ObservingConditions
> 0000065 2021-05-28 08:28:58.144:       Info,   Environmental, Successfully connected to ObservingConditions ASCOM Driver ASCOM.MGBox.ObservingConditions
> 0000066 2021-05-28 08:28:58.144:       Info,   Environmental, ObservingConditions ASCOM Name: Ascom Driver for Astromi.ch MGBox
> 0000067 2021-05-28 08:28:58.145:       Info,   Environmental, ObservingConditions ASCOM DriverVersion: 6.2
> 0000068 2021-05-28 08:28:58.146:       Info,   Environmental, ObservingConditions ASCOM DriverInfo: Ascom Driver for MGBox. Version: 6.2
> 0000069 2021-05-28 08:28:58.146:       Info,   Environmental, ObservingConditions ASCOM InterfaceVersion: 1
> 0000070 2021-05-28 08:28:58.149:       Info,     Environment, Temp (C) = -273.1, Humidity(%) = 0.0, Dew Point (C) = -273.1, Pressure (mbar) = 0.00
> 0000071 2021-05-28 08:29:27.147:       Info,    Async Window, <*closing*>
> 0000072 2021-05-28 08:29:37.153:       Info,     Environment, Temp (C) = 18.8, Humidity(%) = 34.0, Dew Point (C) = 2.7, Pressure (mbar) = 933.63
> 0000073 2021-05-28 08:29:47.172:       Info,     Environment, Temp (C) = 18.9, Humidity(%) = 34.0, Dew Point (C) = 2.7, Pressure (mbar) = 933.65
> 0000074 2021-05-28 08:29:57.173:       Info,     Environment, , Pressure (mbar) = 1010.00
> 0000075 2021-05-28 08:29:57.910:       Info,    Async Window, <*closing*>
>
> The information at line 70 is what was showing up in APCC, but about 40 seconds later, it got the right information, as well as on the next poll another 10 seconds later (but never updated the display from the "test" button in APCC's environmental settings.
>
> -----Original Message-----
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Dale Ghent
> Sent: Friday, May 28, 2021 9:20 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APCC Pro with MSGBox V2
>
>
> 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 various ObservingConditions properties and the info is consumed  by both APCC and NINA, and haven't seen this  sort of problem.
>
> Dew point is not measured by a sensor but is derived from the temperature and humidity. Does your dew point reading look sane in APCC? If it was derived using the 237K, used as C, then it would certainly be wonky as well. That could narrow down where the problem is.
>
>> On May 28, 2021, at 11:58, W Hilmo <y.groups@...> wrote:
>>
>> 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 the MGBox V2 in the appropriate properties for the observing conditions hub.  I have also tried selecting “Astromi.ch MGBox Observing Conditions” in the Select Driver box.
>>
>> Both methods give the same results.
>>
>> I have also tried enabling “Trace on” in the MGBox driver, but I haven’t figured out yet where I can go to read the trace.
>>
>> Finally, I just found the ASCOM “Observing conditions Hub test harness”.  When I run that tool and connect to the observing conditions hub, it shows the correct information (below).  I was originally thinking that this would probably be a problem with the MGBox ASCOM driver (and I asked about it here to see how others were getting it to work with APCC), but now I suspect that it actually *is* an APCC problem, since the ASCOM test app works correctly:
>>
>> 5/28/2021 8:54:41 AM
>> ASCOM Observing Conditions Hub (OCH). Version: 6.5.1.0 AveragePeriod :
>> 0.0 CloudCover - This property is not implemented DewPoint : 2.7
>> Humidity : 34.0 Pressure : 933.8 RainRate - This property is not
>> implemented SkyBrightness - This property is not implemented
>> SkyQuality - This property is not implemented SkyTemperature - This
>> property is not implemented StarFWHM - This property is not
>> implemented Temperature : 18.9 WindDirection - This property is not
>> implemented WindGust - This property is not implemented WindSpeed -
>> This property is not implemented CloudCover is not implemented
>> DewPoint Description : MGBox uses a Bosch BME280 sensor Humidity
>> Description : MGBox uses a Bosch BME280 sensor Pressure Description :
>> MGBox uses a Bosch BME280 sensor RainRate is not implemented
>> SkyBrightness is not implemented SkyQuality is not implemented
>> SkyTemperature is not implemented StarFWHM is not implemented
>> Temperature Description : MGBox uses a Bosch BME280 sensor
>> WindDirection is not implemented WindGust is not implemented WindSpeed
>> is not implemented
>>
>> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of
>> Phillip Klein
>> Sent: Friday, May 28, 2021 8:46 AM
>> To: main@ap-gto.groups.io
>> Subject: Re: [ap-gto] APCC Pro with MSGBox V2
>>
>> Hi Wade,
>>
>> Under Data Source have you selected Ascom?
>>
>> Phil
>>
>>
>> On Fri, May 28, 2021 at 8:36 AM W Hilmo <y.groups@...> wrote:
>> In my quest for unguided imaging, I've picked up an MGBox V2 so that I can get temp, pressure, humidity and dew point.
>>
>> I have installed the MGBox V2 and verified that it is working correctly in its own application.  I've also installed the ASCOM driver 1.6 for the MGBox V2.  The problem is that I cannot get it to work correctly with APCC.  All of my attempts to test it cause APCC to display -237.2C (absolute zero) for both temperature and dew point, and zeros for pressure and humidity.  I have tried connecting directly through the ASCOM ObservingConditions selection in APCC, and also by connecting to the ASCOM Observing Conditions Hub and selecting the MGBox V2 for the relevant specific devices.
>>
>> Does anyone have any suggestions or troubleshooting steps to figure this out?
>>
>> Thanks,
>> -Wade
>> Attachments:
>>
>>      • MGBox.JPG
>>
>
>
>
>
>
>
>
>
>
>
>
>
>






Re: APCC Pro with MSGBox V2

Jeffc
 

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 solution for a “portable” setup.  



On May 28, 2021, at 1:10 PM, Ken Sablinsky <kensablinsky@...> wrote:


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 degrees in SGP when I first connect it (with 0's for the pressure and humidity), but within a few seconds (maybe up to 10-20 seconds?), it switches to the proper temp and shows the rest of the data.  This is going through either the ASCOM MGBox driver or through the observatory conditions hub.  I've never seen the issue when I run the native MGBox software, so I just thought it takes SGP a bit longer to get the data from the device and properly display the correct temp.

-Ken

On Fri, May 28, 2021 at 12:30 PM Dale Ghent <daleg@...> wrote:

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 a variant of the same named BMP280) and it's very straight-forward i2c stuff. The Arduino library for it emits the temp in Celsius. Maybe the MGBox app works in Kelvin for some reason. Who knows, but glad it works for you now.

> On May 28, 2021, at 12:57, W Hilmo <y.groups@...> wrote:
>
> 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 this interesting little section:
>
> 0000061 2021-05-28 08:28:57.875:       Info,   Environmental, EnablePolling = True
> 0000062 2021-05-28 08:28:57.877:       Info,   Environmental, Polling Interval = 10 (secs)
> 0000063 2021-05-28 08:28:57.879:       Info,   Environmental, DeviceType = ASCOM ObservingConditions
> 0000064 2021-05-28 08:28:57.881:       Info,   Environmental, ObservingConditions ASCOM Driver = ASCOM.MGBox.ObservingConditions
> 0000065 2021-05-28 08:28:58.144:       Info,   Environmental, Successfully connected to ObservingConditions ASCOM Driver ASCOM.MGBox.ObservingConditions
> 0000066 2021-05-28 08:28:58.144:       Info,   Environmental, ObservingConditions ASCOM Name: Ascom Driver for Astromi.ch MGBox
> 0000067 2021-05-28 08:28:58.145:       Info,   Environmental, ObservingConditions ASCOM DriverVersion: 6.2
> 0000068 2021-05-28 08:28:58.146:       Info,   Environmental, ObservingConditions ASCOM DriverInfo: Ascom Driver for MGBox. Version: 6.2
> 0000069 2021-05-28 08:28:58.146:       Info,   Environmental, ObservingConditions ASCOM InterfaceVersion: 1
> 0000070 2021-05-28 08:28:58.149:       Info,     Environment, Temp (C) = -273.1, Humidity(%) = 0.0, Dew Point (C) = -273.1, Pressure (mbar) = 0.00
> 0000071 2021-05-28 08:29:27.147:       Info,    Async Window, <*closing*>
> 0000072 2021-05-28 08:29:37.153:       Info,     Environment, Temp (C) = 18.8, Humidity(%) = 34.0, Dew Point (C) = 2.7, Pressure (mbar) = 933.63
> 0000073 2021-05-28 08:29:47.172:       Info,     Environment, Temp (C) = 18.9, Humidity(%) = 34.0, Dew Point (C) = 2.7, Pressure (mbar) = 933.65
> 0000074 2021-05-28 08:29:57.173:       Info,     Environment, , Pressure (mbar) = 1010.00
> 0000075 2021-05-28 08:29:57.910:       Info,    Async Window, <*closing*>
>
> The information at line 70 is what was showing up in APCC, but about 40 seconds later, it got the right information, as well as on the next poll another 10 seconds later (but never updated the display from the "test" button in APCC's environmental settings.
>
> -----Original Message-----
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Dale Ghent
> Sent: Friday, May 28, 2021 9:20 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APCC Pro with MSGBox V2
>
>
> 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 various ObservingConditions properties and the info is consumed  by both APCC and NINA, and haven't seen this  sort of problem.
>
> Dew point is not measured by a sensor but is derived from the temperature and humidity. Does your dew point reading look sane in APCC? If it was derived using the 237K, used as C, then it would certainly be wonky as well. That could narrow down where the problem is.
>
>> On May 28, 2021, at 11:58, W Hilmo <y.groups@...> wrote:
>>
>> 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 the MGBox V2 in the appropriate properties for the observing conditions hub.  I have also tried selecting “Astromi.ch MGBox Observing Conditions” in the Select Driver box.
>>
>> Both methods give the same results.
>>
>> I have also tried enabling “Trace on” in the MGBox driver, but I haven’t figured out yet where I can go to read the trace.
>>
>> Finally, I just found the ASCOM “Observing conditions Hub test harness”.  When I run that tool and connect to the observing conditions hub, it shows the correct information (below).  I was originally thinking that this would probably be a problem with the MGBox ASCOM driver (and I asked about it here to see how others were getting it to work with APCC), but now I suspect that it actually *is* an APCC problem, since the ASCOM test app works correctly:
>>
>> 5/28/2021 8:54:41 AM
>> ASCOM Observing Conditions Hub (OCH). Version: 6.5.1.0 AveragePeriod :
>> 0.0 CloudCover - This property is not implemented DewPoint : 2.7
>> Humidity : 34.0 Pressure : 933.8 RainRate - This property is not
>> implemented SkyBrightness - This property is not implemented
>> SkyQuality - This property is not implemented SkyTemperature - This
>> property is not implemented StarFWHM - This property is not
>> implemented Temperature : 18.9 WindDirection - This property is not
>> implemented WindGust - This property is not implemented WindSpeed -
>> This property is not implemented CloudCover is not implemented
>> DewPoint Description : MGBox uses a Bosch BME280 sensor Humidity
>> Description : MGBox uses a Bosch BME280 sensor Pressure Description :
>> MGBox uses a Bosch BME280 sensor RainRate is not implemented
>> SkyBrightness is not implemented SkyQuality is not implemented
>> SkyTemperature is not implemented StarFWHM is not implemented
>> Temperature Description : MGBox uses a Bosch BME280 sensor
>> WindDirection is not implemented WindGust is not implemented WindSpeed
>> is not implemented
>>
>> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of
>> Phillip Klein
>> Sent: Friday, May 28, 2021 8:46 AM
>> To: main@ap-gto.groups.io
>> Subject: Re: [ap-gto] APCC Pro with MSGBox V2
>>
>> Hi Wade,
>>
>> Under Data Source have you selected Ascom?
>>
>> Phil
>>
>>
>> On Fri, May 28, 2021 at 8:36 AM W Hilmo <y.groups@...> wrote:
>> In my quest for unguided imaging, I've picked up an MGBox V2 so that I can get temp, pressure, humidity and dew point.
>>
>> I have installed the MGBox V2 and verified that it is working correctly in its own application.  I've also installed the ASCOM driver 1.6 for the MGBox V2.  The problem is that I cannot get it to work correctly with APCC.  All of my attempts to test it cause APCC to display -237.2C (absolute zero) for both temperature and dew point, and zeros for pressure and humidity.  I have tried connecting directly through the ASCOM ObservingConditions selection in APCC, and also by connecting to the ASCOM Observing Conditions Hub and selecting the MGBox V2 for the relevant specific devices.
>>
>> Does anyone have any suggestions or troubleshooting steps to figure this out?
>>
>> Thanks,
>> -Wade
>> Attachments:
>>
>>      • MGBox.JPG
>>
>
>
>
>
>
>
>
>
>
>
>
>
>






4461 - 4480 of 83230