CSI edit MCI?

[fixerup]

How can you determine if controller is in heating or cooling mode from INET?

[just_opinion]

get into the controller
then go to SUMARY then choose controller
find your point. it will tell you

[twisted pair]

Just Opinion's advice is good, but depending on what type of Sub-LAN Controllers you have there are a few ways to do it in I/NET.

If your workstation/laptop has graphics, that would be the easiest, but it depends who created them and if they have all the associated I/O Points populated on the graphic pages. The next easiest way is what Just Opinion said. Connect to the Site/Link > Connect to MCI Controller (Station Address DCU xx), then > Summary > Controller and all the resident I/O Points for that MCI will be displayed. You can sort them by physical address or point name. This way is good for most Sub-LAN controllers such as MR55's and MR88's and any other Micro Regulators.

The only problem with using the controller summary is with Application Specific Controllers (ASC's). Because the ASC's have a "canned" database when you look in the controller summary there may be a lot of points that you are not using, unless you modify or delete some of the factory points.

For any ASC's - MR-VAV-AX-C, MR-HPMP, MR-AHU you can connect to the Site/Link > Connect to the MCI Controller > Then Edit > Controller > ASC Parameters and highlight the ASC > click on display data and you can view from their. This only applies to ASC's not MR's. In ASC Parameters you can check your active Heat/Cool setpoints, actual space temp and commanded value to the associated outputs. I am not sure if that data is dynamic. I believe you might have to refresh the screen to update the data, but I am not positive.

[crab master]

Data is dynamic with everything I've worked with. (Inet 2000, INET Seven.)

[twisted pair]

You sure Crab? Some summaries in I/NET do refresh on there own. For example MCU Configuration, if you make a change you have to exit and go back in to see the change.

Give me a break I am just a Estimator/Salesman/Project Manager. My tech days are long gone!!!!!!!!!

[fixerup]

What I meant to ask was on A VVT system what determines if the RTU is in the heating mode or cooling mode?

[twisted pair]

I need to know what type of controller you are using. I know it is a Sub-LAN Controller because you mentioned an MCI.

My guess would be either an ASC (MR-AHU) or a progarmmable controller (MR88).

On a ASC there are certain parameters, and with an MR the programming is custom (calculations, events, etc..).

If you want to get me a save file I could easily tell you.

[just_opinion]

like I said. You go in to the Sumary/Controller and see everything live. It will update whenever the point change.

If you don't have graphic pages, or they are not reliable, then go to the controller and find its address. Then look into the sumary for that address.

Unless your MCI is all screwed up.

[twisted pair]

Like I said depends what type of controllers he has. If they are ASC's you need to know what I/O Points you are using when you are in the Controller Summary! Or else he is looking at points that might not be used and they will still have a value.

[twisted pair]

How does a MCI get all screwed up?

[crab master]

You sure Crab? Some summaries in I/NET do refresh on there own. For example MCU Configuration, if you make a change you have to exit and go back in to see the change.

Give me a break I am just a Estimator/Salesman/Project Manager. My tech days are long gone!!!!!!!!!

I am just talking if you go to controller then summary then the data is dynamic. Granted if you make certain changes on some items you actually have to take the controller offline and back online to see the change/add. Anyway, I was intending on giving you a bad time - just FYI. Also for the tech days being long gone you are posting some great advice.

[twisted pair]

Thanks Crab Master.

Yes I was well aware of the controller summary being dynamic. When we do commissioning we usually use the controller summary. I was referring to ASC Parameters which you can view once you are connected to an MCI.

Maybe I am not understanding Fixerup's question, but with primary controllers like a DCU or PCU I would always use the controller summary for checking I/O Points and I prefer to make DDC Logic graphics for following Direct Digital Control due to the number of DDC modules and lines. However with Sub-LAN Controllers sometimes for Application Specific Controllers I like the ASC Parameters for checking if something is in heating or cooling instead of the controller summary. With the TAC ASC's there are so many points with the ASC's. The percent load in the controller summary is also a good way to check deviation from setpoint. He was asking about a VVT System, but I was not clear whether he had Micro Regulators or Application Specific Controllers.

You also post good stuff.

[fixerup]

They are ASC controllers. Another question. How do you set min. airflow to allow heat to work the boxes I'm working on do not have a fan. I adjust the heat low flow and high flow settings and the damper will not move past 30. I need more airflow to make my flow saftey switch so my heat will energize.

[twisted pair]

Fixerup

Before I answer that I need you to clear something up. What Application Specific Controller are you using, I am assuming it is the MR-VAV-AX-C with integral damper actuator? for the VVT Zones. What about the Rooftop Units are those MR-AHU's or MR88's?

Your earlier statement said VVT. I just want to be sure it is VVT and not VAV. The MR-VAV-AX-C is designed to do most VAV applications except dual duct.

We have used them for VVT applications like a replacement of a Carrier Parker system or California Economizer system, but you need to do some custom programming.

Your question of how the RTU knows if it is in heating or cooling, depends on who did the programming. The jobs I have done using that product on a TAC I/NET system we had the VVT Zone Dampers reference the supply air temperature of the RTU if it was greater than 75 they knew it was in heat mode.

The logic behind this was in the occupied mode in mechanical cooling or economizer our supply air temperature should never be greater than 65 Deg. on the high end of cooling. TAC does not really make a controller specifically for VVT so you have to "tweak" it a little bit unlike Trane who makes a product specifically for VVT.

So if the VVT zones see a RTU SAT greater than 75 Deg. when the unit is occupied and if there zone does not require heat, that zone damper goes closed until the RTU comes out of heat (SAT<65 Deg.). I will have to check on those exact setpoints with the programmer that did the job for me. But I think they are pretty close.

There a different ways to do it. We really do more VAV applications because most of our clients have buildings with larger systems. Typically I only encounter VVT in smaller buildings. The 2 recent jobs we did that way have been working fine.

As far as the VVT local heat I understand your problem. You have a safety probably a airflow switch that is not satisfied. On VVT you are not reading velocity. What I am asking is do you have a pickup and pitot tube? Typically you would only use that on VAV not VVT.

Does the system have enough static pressure. What maintains static a bypass damper?