From: Martin D. <mdo...@po...> - 2003-01-21 12:55:33
|
Bill, Thanks for the help. Yes it is through stargate version and not tied directly into the 485 bus, that a project for once I get the whole MH thing working the way I want. I'm fairly new to MH, and PERL so I've spent quite a few hour figuring that I'm doing something wrong since the code seems to have been around for a while. My .mht defs are as follows: STARGATETHERM, 3, Downstairs_THERM, HVAC|Downstairs STARGATETHERM, 1, Greatroom_THERM, HVAC|Greatroom STARGATETHERM, 2, Upstairs_THERM, HVAC|Upstairs in stargate: HVAC Zone name type RS 485 address 1 [unused] 2 Greatroom RCS TR15 485 2 3 up RCS TR15 485 3 4 Down RCS TR15 485 1 another oddity is that if I set all three in a row, I get RCS free error in the log (debug stargate ON) and it will miss one or two of the sets. I added a slight delay, between sets using $New_Second and it seems to work perfectly now. this is the syntax I'm using to set: set $Downstairs_THERM "setpoint:57"; I will try that change this afternoon and let you know what the results are. At 10:00 PM 1/20/2003 -0800, you wrote: >Martin, > > > I've just gotten my thermostats in stargate working with MH. They work >and > > I can do setbacks in MH instead of stargate and make them hopefully a lot > > smarter. I was wondering if anyone else has the same problem i did. > >What is your exact .mht definitions, we support both the SG485RCSTHRM (if >you have a comport tapped into the Stargate485 bus you can use this) as well >as the STARGATETHERM (this interfaces via the Stargate COM1 as with >vars/flags/etc). I wrote both, and as I recall both are 1 based since the >Stargate refers to them in a 1 based fashion. I'm going to assume your >refering to the STARGATETHERM objects and NOT the 485 modules. > >FYI, here are my zone defs >SG485RCSTHRM, 1, DownstairsThermostat, >Thermostats >SG485RCSTHRM, 2, UpstairsThermostat, >Thermostats >SG485RCSTHRM, 3, MasterBedroomThermostat, >Thermostats > >#STARGATETHERM, 1, DownstairsThermostat, >Thermostats >#STARGATETHERM, 2, UpstairsThermostat, >Thermostats >#STARGATETHERM, 3, MasterBedroomThermostat, >Thermostats > >As you can see, I'm using the 485 bus interface, so it is possible I did >something stupid in the code for the other type. > > > First try > > SG MH (items) result set > > 1 1 MH zone 1 set > > 2 2 MH zone 2 set > > 3 3 nothing set > > > > Second try > > SG MH(items) result set > > 1 0 nothing set (tries to access zone 0) > > 2 1 MH zone 1 set > > 3 2 MH zone 2 set > > > > Third try > > SG MH (items) result set > > 2 1 MH zone 1 set > > 3 2 MH zone 2 set > > 4 3 MH zone 3 set > >The first example confuses me, your saying that 1 mapped to 1, 2 mapped to >2, but 3 didn't work? As such I don't see how the thirdtry (2 mapped to 2, >3 mapped to 2, etc) fixed anything? Presuming we are off by one (very >likely). Can you try changing: > > my $output = "##%5e" . sprintf("%02x%02x%02x\r", $self->{address}, >$command, $data); > >to > > my $output = "##%5e" . sprintf("%02x%02x%02x\r", $self->{address}-1, >$command, $data); > >And then use 1 based defs in your .mht file. Let me know if that does the >trick and I'll get the SG code updated (I just restructured alot of it, and >I can't send it to you as you'll neeed other changes that Bruce is merging >in) > >Bill > > > > > >------------------------------------------------------- >This SF.NET email is sponsored by: >SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >http://www.vasoftware.com >________________________________________________________ >To unsubscribe from this list, go to: >http://sourceforge.net/mail/?group_id=1365 |