Posted: November 10 2003 at 18:16 | IP Logged

I have been out of the PowerHome loop for many months now because of a job change and a move, but getting ready to set everything back up and have a few questions.  In my new (old but new to me) house I had to have the HVAC system replaced and I decided to go all out this time and get a zoned system.  I bought a Trane system with a EnviraCom Control System from Honeywell ( color=#800080http://customer.honeywell.com/Catalog/Pages/Enviracom/default.asp) I also go the Serial interface which allows access through a PC.  They have a free API on the site, and there is also a partner company that writes software call Vicar Works ( color=#800080www.vicarworks.com/honeywell) but it cost $50 per year to use the software.  What I would like to do is interface PowerHome with the EnviraCom Serial adaptor so I can have a single interface.  The free API includes all the serial data for both read and write but not sure what I need to do to interface the two.

Posted: November 10 2003 at 21:40 | IP Logged

The serial port should make it easy. I wrote a quick app to interface PH to one of those RS232 LCD's before; would be similar. Also like my caller ID app.

Dave: How 'bout general serial support in the future?

Posted: November 25 2003 at 10:31 | IP Logged

Opus,

About the best you can do at this time would be to write a small interface app in VB using their API and interface to PowerHome using the Windows messaging.  If you're able to put together the API app, I can help you interface it to PowerHome.

I'll also look into adding some generic serial port support.  Im not sure if it would do much good since you can do so much with the serial port and to create something generic would probably be fairly limiting.

Another thought...you could also possibly put something together using the Windows Script Host portion of PowerHome and communicate to the COM port directly that way.  I havent played with this but don't see why it wouldnt be possible.

Dave.

Posted: November 26 2003 at 11:18 | IP Logged

Tony,

Not really...I did a search of Dejanews however and did turn up the following code snippet:

set oComPort  CreateObject("MSCommLib.MSComm")
' Set Com 3
oComPort.CommPort  3
' 9600 baud, no parity, 8 data, and 1 stop bit.
oComPort.Settings  "9600,N,8,1"
' Tell the control to read entire buffer when Input is used.
oComPort.InputLen  0
' Open the port
oComPort.PortOpen  True
' Send a command
oComPort.Output  "ATL1" & vbCr
' Wait for response - (Could use a loop here)
WScript.Sleep 2000
' Read response
Wscript.Echo oComPort.Input
' Close the port
oComPort.PortOpen  False

HTH,

Dave