HAI Omnistat 80b not showing up in PCA

maxeym

Member
I recently had a Omnistat 80b go bad and stopped working. I received a new one but now none of my 80b stats are showing up in PCA. They are controlled by an Omni IIe controller with firmware 3.10c. I have verified the wiring and settings in the 80b to ensure they are what the IIe is expecting. I reset the ram and EPROM but still nothing works. Is there a diagnostic software for the Omni IIe? This is the third system I've installed and this is the first time I've not been able to get the communications working especially since they were working before the thermostat went out. Could it have damaged the IIe board--everything else seems to be working fine.
 
The first thing to check is to see that the new one is set to the same unit number as the old one was. Did the old one fail due to a lightning strike or some other electrical calamity? A couple of years ago I lost an RC1000 due to a lightning strike, but it also damaged the motherboard in my OPII. I had to send it in for repair.
 
All settings are the same. The troubling part is that all thermostats are not showing up. I have two and the one that was working before the event is not as well. The problem stated when one of the 80b quit working, seemed really hot. I order another unit, it was bad and finally got the "new" one and installed it. It powered up but could not control it, so I sent a command to the other unit and it too did not respond. I am guess it has not worked for the last 3 weeks and I just had not noticed it.
 
Make sure each thermostat has a separate address. Have you tried connecting up only one thermostat and then sending a command to it?
I have seen one thermostat "lock up" the thermostat communicating bus with 5 units. The other 4 worked fine after I found the bad unit and disconnected it.

Also, I have seen the Omni thermostat go bad when there is a lightning strike in the area. Also, it can also damage the input/output to the board. And the only option is to send it in for repair.
 
Let me see if I can help.

When you say 'not showing up in PCA" are you talking about the setup section or the status section? Do they show on on consoles, touch screens, or the iPhone/Android apps?

General info: In the Omni generally named = used. It's pretty simple. On my test system right next to me I have several thermostats defined in the setup. One for each type of thermostat and PESM we support. They are all named, in the name field, not just the description field. There are only two thermostats physically connected to the system. When I connect to the controller and go to status, all thermostats show up, even those the do not physically exist. The only ones that have valid readings are the ones that physically exist, the others have all 0's. So even if a thermostat dies, it should still show up, just with all 0's. If you have 2 thermostats with the same address they will both show up, but one will display all 0's and the other will have erratic values. (Because when the controller polls the thermostats "thermostat 1 give me you readings" they both respond and may/usually talk over each other.)

So check to be sure that everything is configured and named. Verify that the thermostats are addressed correctly. Finally make sure the configuration has been written to the controller.

After doing this let me know that happens.
 
They are named and as you indicate they show up in PCA but show all zeros. When I send a command to either they do not respond. I returned the IIe to HAI for repair and just got it back. No problem found. I've rechecked the addressing one is 1 and the other is 2, both are set to 100 baud. The console can not control them either. The time from the controller is not being shown on the thems as well. I checked the wiring but all seems well. I just reposted in the HAI section as well.
 
I just tried J-bird 47's suggestion and found out that the other RC80 must have been damaged at the same time as the 1st one. When I took it off the network the "just replaced RC80" began to function and respond to the controller. I replace that them with the extra one i had and now they both are communicating.

Thanks to all...should have applied basic trouble shooting "cut your problem in half" .
 
Back
Top