Needing Color Viewstat help

Bigsquatch

I'm getting started on code for the new ENV-VST-C thermostats and I'm confused by the reference guide. I've never programmed any Axlink devices before so I'm not sure what to do with the channels that the guide lists.

For example, 140 is Increment Cool Set point.

So do I do:

  SEND_COMMAND dvTstat1, 'CMD 140'

or am I supposed to turn the channel on and off similar to doing button feedback?

And is feedback from the tstat all done through levels or will it send me strings?

I don't have Viewstats at the shop right now to do trial and error on.

Joe Hebert

Bigsquatch wrote:

I'm getting started on code for the new ENV-VST-C thermostats and I'm confused by the reference guide. I've never programmed any Axlink devices before so I'm not sure what to do with the channels that the guide lists.

You can think of an Axlink device the same as any other device. An Axlink device only has one port but other than that there?s not much difference from a programming standpoint.

Bigsquatch wrote:

For example, 140 is Increment Cool Set point.

So do I do:

  SEND_COMMAND dvTstat1, 'CMD 140'

Nope, you would pulse the channel like this:

PULSE[dvTstat1,140]

Bigsquatch wrote:

And is feedback from the tstat all done through levels or will it send me strings?

Levels are used to report the temperatures and set points as per the manual on page 28. The heat and cool setpoint levels are listed as for both command and feedback, however, I was only able to get the levels to work for feedback. To change setpoints I had to use the MD SEND_COMMAND on page 24.

Channel events are used for control and feedback as listed in the manual.

There are strings that come back but I think levels and channels give me the feedback I need.

Hope some of this helps.

Bigsquatch

Yes, that does help.

I had already started coding that way and thought that I would have to use ON[X,X] for sure and was guessing PULSE[X,X] would work for increment & decrement, but wasn't 100% sure.

The MD command info will definitely save me some troubleshooting.

Thanks Joe!

TurnipTruck

Let me know if you find a way to set the relative humidity to a non-integer number. Last I checked the RH was brought in by an Axlink level.

Joe Hebert

TurnipTruck wrote: »

Let me know if you find a way to set the relative humidity to a non-integer number. Last I checked the RH was brought in by an Axlink level.

I don't think there's a way to express a non whole number.

ericmedley

Joe Hebert wrote: »

I don't think there's a way to express a non whole number.

Axlink_Level *100/255 = percent_level


solve for what you need. It even does the rounding for you.

TurnipTruck

ericmedley wrote: »

Axlink_Level * (100/255) = percent_level
solve for what you need.

Right, but the thermostat gets it relative humidity data for display by means of an Axlink level. So the RH can only be 30, 29, 28 (look out Toto!)

Joe Hebert

ericmedley wrote: »

Axlink_Level *100/255 = percent_level


solve for what you need. It even does the rounding for you.

That looks like a solution to a different problem. I think T squared is looking for a way to set the value to something like 72.5 instead of 72 or 73. He doesn't want the rounding. At least that's the way I'm reading it.

TurnipTruck

Joe Hebert wrote: »

That looks like a solution to a different problem. I think T squared is looking for a way to set the value to something like 72.5 instead of 72 or 73. He doesn't want the rounding. At least that's the way I'm reading it.

That's right. Relative humidity is generally expressed in hundreths. xx.xx

I have no idea how to get there with an Axlink level.

Joe Hebert

TurnipTruck wrote: »

That's right. Relative humidity is generally expressed in hundreths. xx.xx

I have no idea how to get there with an Axlink level.

There is no way to do that with one level, Axlink or not. If there were two levels for RH, one that expressed the whole number and one that expressed the hundredths then you'd be in business...