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
>>
>
>
>
>
>
>
>
>
>
>
>
>
>






Join main@ap-gto.groups.io to automatically receive all group messages.