RC-80B and PCA 3 questions

[ricks]

Wow - You guys are good!!! I'll pass this on to Cinemar.

Your worst nightmare... you've answered one question, now I'll ask another.

The current SDK seems not to address serial connections? In using the HAI SDK test program I get the following. Are there any plans to develop this further?

Thanks,
Rick

 

[HAI_fjh]

I just answered Cinemar about this issue on the HAI Forum about 2 minutes ago. I believe he already has it working...

 

[ricks]

Like I said, you guys are good!

Thanks,

 

[ricks]

Hi guys,

Saw the updated PCA today and downloaded. I get the following in the Status column:
TStat1 Heating, Cooling, Dehumidifying
TStat2 Off
TStat3 Off

The actual status of the tstats was TStat1 = off, TStat2 = Heating, TStat3 = off. Also not sure how/why TStat1 would show heating and cooling at the same time.

Is there anything I need to do to get my OMNI II in sync with the new PSA for these values to be correct?

Thanks,
Rick

 

[HAI_fjh]

This is a good one. I tested this before posing the update and just tested it again. It works perfectly on my system. You can get status combinations like heating and humidifying, but not like heating and cooling.

Can you give me some more info to go on?

What is the model and firmware version of your controller?
Same for the thermostats in question...
Are you using Fahrenheit or Celsius?

Could I connect to your system from here using my debugger so I could see what status bytes are actually coming back? If you want to do this DO NOT POST YOUR CONNECTION INFO HERE. Send an e-mail the HAI Tech support ([email protected]). Attach an EXP file for your system and ask them to forward the message to me (Fred Hebert). Reference this message. When I get your EXP file I will connect to your system and see what is going on. Also be sure to include a phone number. I won't connect to your system without contacting you first.

 

[ricks]

Hey Fred,

I have an OMNI II at firmware (20A04-1) 3.0. Obviously the PCA version is at the latest. All 3 TStats are identical RC-80B's with the following labels inside: chip = Model 80 ver. 16 or 1.6 (printing is too low to see which it is) and another label says REV E9 4782 0433-333. All TStat's connected to panel per specs. TSTAT setup is nearly at default with only changes being TStat address, Farenheit and HEAT ONLY.

What is your preferred method to connect? I typically use LogMeIn. Let me know. I will send the email this evening.

I could probably resolve most of these issues (also having problem with Cinemar connecting serially) by upgrading to an OPII but hate to retire this old, yet trusty workhorse. Just so you don't think I'm crazy I've attached an image.

Thanks,
Rick

 

[AnthonyZ]

What is the latest firmware that's meant to have the current state in it. I upgraded today to 3.2.0.523 and my list stops at the stat's settings and doesn't display the On/Off state (it also broke some triggered events...)

 

[ricks]

The one I downloaded today was 3.2.0.534.

Rick

 

[HAI_fjh]

What is your preferred method to connect? I typically use LogMeIn. Let me know. I will send the email this evening.

Hi Rick,

What I meant was to connect to the Omni remotely, not your PC. Is your network setup so that you can access your Omni remotely? (port forwarding, etc.)

What I wanted to do was connect to your system while running my PC Access in the debugger and examine tha raw data comming back from the controller to see why it is not being decoded properly.

Now that I see you have RC-80s and Omni Firmware 3.0, I am going to setup a test system here and test that configurartion. I may not need to connect to your system...

My pervious tests were with RC-2000s and Omni firmware 3.2b.

 

[HAI_fjh]

I upgraded today to 3.2.0.523 and my list stops at the stat's settings and doesn't display the On/Off state (it also broke some triggered events...)

Hi AnthonyZ,

I pushed out 3.2.0.534 just before lunch yesterday. So if you updated in the morning you would have gotten 3.2.0.532. Unfortunately ...534 is the one with the current status. So please update again...

Also what specifically was broken?

I definitely want to address this as quickly as possible.

Please give specific examples and don't forget to include the basics (Controller model & version, etc.). This will help me find and fix the problem quicker.

Thanks,
Fred.

 

[HAI_fjh]

RickS,

After some difficulty I was able to partially duplicate the problem.

The short answer is to reset the controller RAM.

Looking at your screen the Humidify setpoint is -36% and Dehumidify is 118%. This is obviously invalid. I don't know what other RAM values may be invalid, so I strongly recommend that you reset RAM.

After I reset the RAM in my controller the status tracking was correct again.

 

[ricks]

Hi Fred,

Reset the RAM, all went well. Went into PCA, connected serially and tried to do an update from the panel. PCA would crash reading "4608". This is the same problem (4608) Cinemar is having getting MLS to talk to the OMNI II via serial. I believe Dave has posted this on the HAI support forum.

I then wrote to the panel and then tried reading from panel - same crash.

Also, still have issue with Thermostat reporting a status of Heating, Cooling, Dehumidifying.

Rick

PS. Maybe you can email me and tell me how to port-forward to the OMNI II since it only connects via a serial connection to a local PC on the network.

 

[HAI_fjh]

RickS,

I got your EXP file. Something is wrong though, because the file only has one thermostat defined (Basement).

I missed the Omni II part and didn't realize you don't have an Ethernet port. I could still dial in using a modem if your Omni is connected to the phone line.

Looking at the firmware release notes for the Omni II I see that 3.1 corrected a problem with the extended status message. This sure sounds like the problem you are having. You should contact tech support about getting an upgrade chip for the the latest version.

Also after the upgrade let me know if you are still having the error reading from the controller.

Fred.

 

[ricks]

Hey Fred,

Thanks for all your help in hopefully isolating this problem. As a side note to the sales folks, $32 plus shipping to correct a firmware bug is a little steep. Must be an incentive to upgrade to an OP II. :huh:

Thanks,
Rick