If this is your first visit, be sure to check out the FAQ. You must register before you can post. Your first post will be checked for appropriate content
(SPAM) - please allow a bit of time for that. After that, you'll be able to post at will!
No. The design based upon the DS2438 rather than the DS2406 is supported. I believe hobby-boards.com has the supported design, but I'm not postive of this. Mitch at Midon Design will know which is supported by the Temp08.
Hi guys...thanks for the input. I was previously using all these sensors under weather display but liked the look of Michaels MCSTemp program and the triggers it could perform. Unfortunatley I only have the one 1wire interface being The Link from AAG which I can't use for both Homeseer and WD at the same time. Looks like a Tempo8 purchase if I want to expand my network using the current setup. Thanks again
I located the JAVA interface software for this unit and converted it to VB. No problems with this conversion. This was the same approach I used to interface the AAG LCD Text Display. I do not have any desire to purchase the device, but if someone is willing to loan one then I will try to integrate it.
Are you looking for a TAI8570 to be loaned to you? If so, I may be able to part with mine for a couple of weeks to get MCSTemp to work with it. I recently switched over to OWW on a linux box to read weather data, but would rather be using MCSTemp again.
I just wish MCSTemp outputted in Henriksen WServer format, then the world would be perfect.
I missed your offer and am willing to give it a try. I'll send you a PM with the mailing address. Where is the Wserver protocol published? I see it supports TCP/UDP/DDE.
I have the AAG Barometer functional for both the Baro and Temperature readings. My baro readings are about 0.5 lower than the readings provided by the internet. The temperature reading is about 4 degrees cooler than the Temp05 is providing with its onboard DS1820. These may be both a result of no local calibration on the AAG unit.
As I expected the interface is a slug. It is about 30 seconds to obtain the humidity reading and this ties up the application for the full duration. In the xapmcs1Wire the burden is tolerable since data collection is all that it is doing. For mcsTemperature it is not a good thing as it will likely also slow down HS. I suspect I will only implement the interface in xapmcs1wire and leave mcsTemperature to take the same route as Temp05 with only the DS2438-based barometer. The AAG unit will still have the path of xap->hs->mcsTemperature.
If someone has a specific link on method to calibrate the barometer then I will complete the process, otherwise I will return the unit to mloebl who was kind enough to provide the loaner. I looked on the OWW site, but I did not know where to specifically look.
I have the AAG Barometer functional for both the Baro and Temperature readings. My baro readings are about 0.5 lower than the readings provided by the internet. The temperature reading is about 4 degrees cooler than the Temp05 is providing with its onboard DS1820. These may be both a result of no local calibration on the AAG unit.
As I expected the interface is a slug. It is about 30 seconds to obtain the humidity reading and this ties up the application for the full duration. In the xapmcs1Wire the burden is tolerable since data collection is all that it is doing. For mcsTemperature it is not a good thing as it will likely also slow down HS. I suspect I will only implement the interface in xapmcs1wire and leave mcsTemperature to take the same route as Temp05 with only the DS2438-based barometer. The AAG unit will still have the path of xap->hs->mcsTemperature.
If someone has a specific link on method to calibrate the barometer then I will complete the process, otherwise I will return the unit to mloebl who was kind enough to provide the loaner. I looked on the OWW site, but I did not know where to specifically look.
Comment