VSTAT with ICSNET
flcusat
Posts: 309
I'm having difficulties using the ICSNET version of the AMX module for the VSTAT. I'm not getting any feedback in the TP from the VSTAT and also any press of a button in the TP doesn't reflect any change in the VSTAT either. Here is what I'm getting when I press a button in the TP.
Any suggestions?
Line 134 :: String To [33002:1:10]-[INITIALIZED=0] - 21:49:51 Line 135 :: String From [33002:1:10]-[INITIALIZED=0] - 21:49:51 Line 136 :: String To [33002:1:10]-[INITIALIZED=0] - 21:49:51 Line 137 :: String From [33002:1:10]-[INITIALIZED=0] - 21:49:51 Line 138 :: Command To [10001:3:10]-[!T$A0<< INITIALIZED=0] - 21:49:51 Line 139 :: Command To [10001:3:10]-[!T$A0<< INITIALIZED=0] - 21:49:51 Line 140 :: Command To [10001:3:10]-[!T$A0] - 21:49:56 Line 141 :: Input Status:Pushed [10001:3:10] - Channel 152 - 21:51:18 Line 142 :: Command To [36865:1:10]-[T-0 COOL-+] - 21:51:18 Line 143 :: Command From [36865:1:10]-[T-0 COOL-+] - 21:51:18 Line 144 :: Command To [36865:1:10]-[T-0 COOL-+] - 21:51:18 Line 145 :: Command From [36865:1:10]-[T-0 COOL-+] - 21:51:18 Line 146 :: Input Status:Released [10001:3:10] - Channel 152 - 21:51:18 Line 147 :: Input Status:Pushed [10001:3:10] - Channel 152 - 21:51:21 Line 148 :: Command To [36865:1:10]-[T-0 COOL-+] - 21:51:21 Line 149 :: Command From [36865:1:10]-[T-0 COOL-+] - 21:51:21 Line 150 :: Input Status:Released [10001:3:10] - Channel 152 - 21:51:21 Line 151 :: Input Status:Pushed [10001:3:10] - Channel 153 - 21:51:23 Line 152 :: Command To [36865:1:10]-[T-0 COOL--] - 21:51:23 Line 153 :: Command From [36865:1:10]-[T-0 COOL--] - 21:51:23 Line 154 :: Input Status:Released [10001:3:10] - Channel 153 - 21:51:23 Line 155 :: Input Status:Pushed [10001:3:10] - Channel 153 - 21:51:23 Line 156 :: Command To [36865:1:10]-[T-0 COOL--] - 21:51:23 Line 157 :: Command From [36865:1:10]-[T-0 COOL--] - 21:51:23 Line 158 :: Input Status:Released [10001:3:10] - Channel 153 - 21:51:23
Any suggestions?
0
Comments
I think you should tell us the story, so we can avoid any mistakes.
Thanks
The module assigns address to the thermostat in the range of 104xx:1:0 This address has to be change to the actual address in the thermostat(1:1:0)
On Saturday while I was playing with this, I was in a hurry and what I posted here might not be the actual scenario, since the settings in both VSTATs were pretty much similar and I'm not sure now if what I posted earlier was accurate.Yesterday, I cut the power to both VSTATs and powered up the thermostat that was installed first, which has assigned address #1 and it showed in the panel. Then I powered up the second thermostat, with address 2 but is not showing in the panel, however this VSTAT is communicating with the master an is even getting the time from the master.
The problem I'm having is that the module is assigning the same device number to both thermostats
Any ideas?
One thing stands out - are those device numbers valid for an ICSNet device? Not all things can use all device number ranges.
The one system that I have done with ISCNet ViewStats. (all others are Serial) the device range is up in the 10,000s.
in fact, here's the device declarations
Also, just as a point of clarification, when you say you address the T-Stats as 1,2,3, etc... are you referring to the addressing that you do on the T-Stat's menu? If so, those all need to be set to #1. It's the ICSNet boards that need to be set to sequencial numbers.
The addressing done on the T-Stat's menu is for the RS-422 communication from the T-Stat. When the T-Stats are controlled via RS-422, they are usually connected in a loop / daisy chain. (similar to AxLink) commands are sent out with an address attached to them so the proper T-Stat will respond or comply. Other devices will ignore.
In the case of the ISCNet T-Stat, the little card is simply an RS-422 to AMX-speak translator. Since the Viewstats are connected directly to the cards, ther is only one T-Stat rs-422 connection and it's address is assumed to be always #1.
Just a thought.
eric
Originally the module comes with the devices declared in the 1040X range. I had it like that and I was having the same problem I'm having now. I called tech support and they suggested to change it to what I had declared above.