Connecting To A Voyager

[jogas]

As you can probably tell, I'm working on a problem job and am scrambling in several directions looking for answers.
I am thinking some of my problems lay in the voyager RTU's programming. I have Rover V5, SP9. Can I connect to the voyager using my rover to check it's setup? If so, how?
In the Summit voyager editor, when in Tracer control mode and the control mode is set to heating, the RTU shuts down. And when I go to status/object and properties, it says the control mode is in manual.
Any ideas?
jogas

[controldude]

What version of summit and what BCU image is this?

[jogas]

Here's the info.
Site BCU:
Application Software Revision: 14.032
Firmware Revision: 14.032
Model Name: BCU (BMTW), M1
My Laptop: Tracer Summit Version:16.00.0123 Serv Pak 6

Looking in the Status/Device/BCU Diagnostic 20 = 25643
The Summit Library Device/Properties defines this as:
Number of failing memory requests. A non-zero value is a warning
of memory problems.
Is this a serious problem? I do know there are many unused Summit inputs and outputs defined. Could this be the cause?
I have been told I cannot connect to a Voyager and get any more info than I see in Summit. Is this true?
jogas

[willf650]

You can't connect to to cofigure it. It's a packaged roof top unit and has to be able to be set on a roof and run with out having to play with it with a computer. It's configuration comes from what options boards it has in it. This is true of both the older voyagers and the newer ones with the relitel conrols as well.


What I don't understand is how is this a CV unit. Every voyager or intelipac I've ever worked on that had a VFD is set up for discharge air control. You can set it up for CV control by reconfiguring an intelipac it or unplugging options boards in a voyager but it loses control of the VFD. It will still start it and stop it but will not control the speed. Why is there a bypass box if this is a VAV voyager? Why would you have two devices trying to control one medium such as static pressure in this case. If you run the VFD at 100% all the time they actually use more electricity than a starter in this application. Are the VFDs factory installed in the unit or are they something that some one threw on.

And to answer another question from a previous post of your the being able to set it on a roof and run is why the static pressure pick up is in the unit.

And also to warn you not all things in the objects an properties actually exist.

[jogas]

You can't connect to to cofigure it. It's a packaged roof top unit and has to be able to be set on a roof and run with out having to play with it with a computer. It's configuration comes from what options boards it has in it. This is true of both the older voyagers and the newer ones with the relitel conrols as well.


What I don't understand is how is this a CV unit. Every voyager or intelipac I've ever worked on that had a VFD is set up for discharge air control. You can set it up for CV control by reconfiguring an intelipac it or unplugging options boards in a voyager but it loses control of the VFD. It will still start it and stop it but will not control the speed. Why is there a bypass box if this is a VAV voyager? Why would you have two devices trying to control one medium such as static pressure in this case. If you run the VFD at 100% all the time they actually use more electricity than a starter in this application. Are the VFDs factory installed in the unit or are they something that some one threw on.

And to answer another question from a previous post of your the being able to set it on a roof and run is why the static pressure pick up is in the unit.

And also to warn you not all things in the objects an properties actually exist.

Every thing that I have described that is on this job is what I have found, and know so far. I don't know why the installing contractor did what he did. I only know that this job has not worked properly since installed 4 years ago and I am trying to get it to run right.
I only say it is "CV" because I have never seen the VFD at any other speed than 60 Hz. The VFD is factory installed in the RTU.
As for the bypass, I think the intent was to provide adequate airflow thru the RTU for the gas heat at low heat loads. There is no reheat in the VAV's, so the RTU gas heat is the only system heating capability. As for the VFD, I'll have to check what options are in the RTU.
And thanks for letting me know that the static pickup is O.K. where it's at.
Could you expand on your objects/properties statement? And maybe explain how the link between summit and the MP581 works?
TIA,
jogas

[willf650]

As far as the objects and properties statement. There are many "properties" in controlers and packaged equipment that are dependant of what options the unit has but regaurdless of options they are avaiable in the summit system. A prime example that you may be aware of is the in mp580. It has up to 36 inputs if you add optional expansion modules. They are available to be read in summit whether they exist or not. There are also many points that seem to be put in the system for futher development or that may have been used in a previous generation of controller but are no longer there.


As far as the link from summit to the 580 its about the same as previous controllers with a little more. The summit can read alot of stuff from it that was not availble in previous controllers such as all the variables, inputs, outputs and names. You can pass values to it from summit via the editors reference pass thru.

[duke of earl]

Tell the engineer that designed this one that he/she should find another profession like mailman or shoesalesman.

[D_Woods]

I think Diag.20 in this case is for a BTMS BCU. You need to look a little further down the Diag Chart to see the Diag for BTMW and BTMX BCU's.
Best of Luck
D_Woods
Looking in the Status/Device/BCU Diagnostic 20 = 25643
The Summit Library Device/Properties defines this as:
Number of failing memory requests. A non-zero value
is a warning of memory problems.

[jogas]

Things are finally starting to operate somewhat normally. Both RTU's now changeover between economizer and DX cooling properly.
The DX stages properly now also. The previous contractor had hard-wired delay on close TD's in the compressor circuits set for 10 minutes. By the time the delay made, both compressors were bring called for. After removing the TD's, the compressors stage properly now.
I've gotten the hang of connecting the different levels of logic with each other also.
We still haven't gotten to the VFD, or Area, or VAS, or VAV setup, but will soon.
This morning (65* OAT), each RTU would energize 1 stage DX cooling at 3-5 zones calling, and would shut off at 1 zone calling. Later in the day (78* OAT), 1 DX stage ran continuously.
Thanks to all who put up with my endless questions....and especially to those who replied. Man it's cool when a BAS works right!
jogas