Viewstats... Worth the Headaches??
TurnipTruck
Posts: 1,485
in AMX Hardware
Greetings,
I have started using Viewstats on my last two big resi projects. Needless to say, they are by far the most finicky, least reliable piece of equipment I've ever integrated into a system.
Has anyone been particulary impressed or unimpressed with these things?
I have started using Viewstats on my last two big resi projects. Needless to say, they are by far the most finicky, least reliable piece of equipment I've ever integrated into a system.
Has anyone been particulary impressed or unimpressed with these things?
0
Comments
To answer your question, I guess I am unimpressed.
It's a shame, but I had to put a watchdog relay on their power. If there are no strings from the virtual device for thirty minutes, the relay pulls the power to all of the stats for a few seconds to bring them back to life.
Lessons learned.....
What sort of kinks have you ran into?
Mostly hardware kinks. Far and away is the rolling reset issue they get when they are confused. I've had this happen due to improper furnace connections, and defective disty boxes. Pretty much anything they don't like makes them go into a reset cycle.
The other kink, which I have eliminated in code, also resulted in runaway resets, but it was due to too-frequent polling (at least according to Aprilaire). I was using legacy code based on the fact that older Viewstats didn't report asynchronous changes properly; but the new ones do, so I scaled the polling way back and haven't had a problem since.
Something that is really important with these beasts is that you have to go into the setup of each stat and make sure they total mount of stats in the system is properly set. Don't pad it, don't skip addresses, and don't leave room for future stats. If you have 7 stats, set it for 7! The reason is it manages the 422 buss by waiting for all the stats to report back - and anything "missing" from the buss, it's going to wait for. Left at the default of 32, it's going to wait for all 32 to report even though they don't exist. It will timeout, but the waiting period makes the whole buss unresponsive. Too much of that and they start resetting.
On the system I am having trouble with, I am having a stat lock up on the order of once a day, killing the bus. I have been using my rebooting relay to bring the system back. No particulat stat, it could be any of them.
As of now there is no distribution panel. All stats home run to 110 punch blocks and are bussed together there, connected to an NXI serial port. It is my understanding that the disty panel does nothing more than what I am doing, but gives you the ability to pull stats off the bus more easily.
The disty panel definitely has circuitry to buffer and help manage the comm buss, plus the ability to pull them off said buss at will, as you mentioned. But it is definitely not just a dumb termination block. I would strongly recommend starting there and putting on in place of your 110 block.