PDA

View Full Version : Trane



ddc-tech
03-30-2010, 03:17 PM
I have a trane summit with BCU.

I have RTUs coming back as bacnet/ip

I discovered the RTUs and the points.

The points come back the same name and instance
for each RTU. So I manually added them with R3,R4,etc
in front of the name for each respective RTU.

Every time I tried to add each point to CPL so
I can write the AO setpoint to the actual analog value
RTU point I get errors that the point doesn't exist.

If I go into site config and go to the device, all the points are there.
Do I need to update the BCU with the new points?

What am I doing wrong?

Also, if someone has an example of CPL program that will take
an AO and write its value to another point that would be helpful too.

mallron
03-30-2010, 06:46 PM
Not exactly sure of what you're trying to do, but if you are a 3rd party vendor and you have discovered the points available in the BCU then you should be able to override them directly. Then reference the appropriate AO's in the editor of the corresponding RTU.

scrooloose
03-30-2010, 09:14 PM
I think he is bringing stuff into the bcu.

Are you adding the AV via Edit -> Add Obj&Prop? That will guarantee that you are getting the correct name. My guess is maybe the point has a extra space or whatever and your cpl is not finding the point because of it.

broncobill
03-31-2010, 11:45 AM
whatever setpoint you're trying to control should be an Analog Output point in Summit. That point needs to be referenced to the value you're trying to control in the RTU.

Scrooloose is right in that you should be adding the points by using the Edit/Add Object and property. It will be an analog output type, pick the correct one and the property will be "present value"

willf650
03-31-2010, 02:15 PM
In your site configuration there is a property under the comunications tab that is "Non Trane Devices" "Disable Automatic Uppdates". You will want that button checked. I won't go into specifics but what you are describing is something that "could" be related to that tab. You will want to check it and then continue from there regardless.

The point will be an analog value in the editor. If you are just changing setpoints you can do it directly from a graphic/ that's the route I would and have gone.


Free advice/opinion

Those roof tops suck and that modlink thing is a piece of crap. There is a point called Modbus communication state you will want to read and display. If there is something wired into the shutdown point of the unit it will kill power to the units control board but not the modlink transmitter. The system will see nothing wrong as the communication to the unit will be up and all the last communicated values will still be read by the control system. The unit will be dead and not running in all actuality but the only way to tell is that one point called modbus communication state.

ddc-tech
03-31-2010, 06:52 PM
Not exactly sure of what you're trying to do, but if you are a 3rd party vendor and you have discovered the points available in the BCU then you should be able to override them directly. Then reference the appropriate AO's in the editor of the corresponding RTU.

Under non-trane bacnet devices...the points come back as AVs and BVs.
All the RTUs have the same point names and same Instances.

I was trying to add these points to the graphics but I cannot directly map these AVs and BVs to the graphics. The drop-down comes back
with three cooling setpoints(example) but I do not know what RTU this cooling setpoint comes from since all the names are the same.
So what I was thinking of doing is using CPL to have the AO write to the AV.
I added the points manually and gave them specific RTU name but everytime I perform a scan on another RTU the points I added manually go back to the original name in the controller.


Is there easier way?
What step did I miss?

The bottom line is I want to add these points to the graphics.
I don't care if it is directly or through CPL.

ddc-tech
03-31-2010, 06:54 PM
In your site configuration there is a property under the comunications tab that is "Non Trane Devices" "Disable Automatic Uppdates". You will want that button checked. I won't go into specifics but what you are describing is something that "could" be related to that tab. You will want to check it and then continue from there regardless.

The point will be an analog value in the editor. If you are just changing setpoints you can do it directly from a graphic/ that's the route I would and have gone.


Free advice/opinion

Those roof tops suck and that modlink thing is a piece of crap. There is a point called Modbus communication state you will want to read and display. If there is something wired into the shutdown point of the unit it will kill power to the units control board but not the modlink transmitter. The system will see nothing wrong as the communication to the unit will be up and all the last communicated values will still be read by the control system. The unit will be dead and not running in all actuality but the only way to tell is that one point called modbus communication state.



I agree these RTUs SUCK!!!!

I will check the Disable button.

ddc-tech
03-31-2010, 06:58 PM
I think he is bringing stuff into the bcu.

Are you adding the AV via Edit -> Add Obj&Prop? That will guarantee that you are getting the correct name. My guess is maybe the point has a extra space or whatever and your cpl is not finding the point because of it.


No I have not tried this...

When I add this, will I be able to change the name?

amigo
03-31-2010, 07:46 PM
Free advice/opinion

Those roof tops suck and that modlink thing is a piece of crap. There is a point called Modbus communication state you will want to read and display. If there is something wired into the shutdown point of the unit it will kill power to the units control board but not the modlink transmitter. The system will see nothing wrong as the communication to the unit will be up and all the last communicated values will still be read by the control system. The unit will be dead and not running in all actuality but the only way to tell is that one point called modbus communication state.

What brand/model of equipment is this?

scrooloose
03-31-2010, 09:00 PM
]I was trying to add these points to the graphics but I cannot directly map these AVs and BVs to the graphics. The drop-down comes back
with three cooling setpoints(example) but I do not know what RTU this cooling setpoint comes from since all the names are the same.
So what I was thinking of doing is using CPL to have the AO write to the AV.
I added the points manually and gave them specific RTU name but everytime I perform a scan on another RTU the points I added manually go back to the original name in the controller.


Is there easier way?
What step did I miss?

The bottom line is I want to add these points to the graphics.
I don't care if it is directly or through CPL.

You need to edit the .nto object located under the Tracer Summit\Database folder. It will be named "site name".nto You can then change any of the names you want to something that means something to you. In that you will see the 3 setpoints with the same name. Just change them to RTU1, RTU2, etc.. and then save the file. You can use notepad to open it. You must restart Summit to see the changes once you have saved the file.

Like willf650 said you will need to go to site config and remove the check mark for automatic updates. If you leave that checked it will erase all your point names the next time the BCU auto updates the nto.

willf650
03-31-2010, 10:00 PM
You need to edit the .nto object located under the Tracer Summit\Database folder. It will be named "site name".nto You can then change any of the names you want to something that means something to you. In that you will see the 3 setpoints with the same name. Just change them to RTU1, RTU2, etc.. and then save the file. You can use notepad to open it. You must restart Summit to see the changes once you have saved the file.

Like willf650 said you will need to go to site config and add the check mark for automatic updates. If you leave that unchecked it will erase all your point names the next time the BCU auto updates the nto.

Fixed

P.S.
You don't need to modify the NTO if you are using graphics to do control. The only time you would need to modify it is for your own benifit or CPL.

willf650
03-31-2010, 10:04 PM
What brand/model of equipment is this?

They are some of the smaller types of York units. If you really want models I can look tommorow on my work computer for the specific ones I had that issue with.

That modlinc thing is in several of their styles of units but I don't know if all the styls suffer that same emergency shutdown affliction.


See you, time to go back to lurking.

amigo
03-31-2010, 10:14 PM
They are some of the smaller types of York units. If you really want models I can look tommorow on my work computer for the specific ones I had that issue with.

That modlinc thing is in several of their styles of units but I don't know if all the styls suffer that same emergency shutdown affliction.


See you, time to go back to lurking.

no need for specific model#s, was generally curios about the make.
Thanks.

ddc-tech
03-31-2010, 10:49 PM
I want to thank all the replies...I will go forward with
Disable Automatic Updates and the Edit/Add Object and property.

So I can delete any existing CPL that refers to commanding these points.

If I have any trouble, I will let you know but

again thanks for all the help.

broncobill
04-01-2010, 09:37 AM
You said

"I can write the AO setpoint to the actual analog value RTU point"

What RTU point are you trying to write to? What type of rooftop? Is this just a Summit site or is there another vendor involved? What interface is on the RTU, Lontalk or proprietary?

M100 Tech
04-03-2010, 10:43 PM
Are they Trane RTU's? If so, what are you doing writing CPL? You need to set each RTU's configuration to reference the appropriate setpoint you want to use. Never fear, BCI-R is on its way for Reliatel. It is available for IPAK and is very easy to use! No more BACNET PTP.

ddc-tech
04-05-2010, 08:32 PM
They are York RTUs with factory Simplicity boards that
have RTU Modbus communication. The Simplicity boards
modbus communication is wired to York ModLinc module
that converts the RTU Modbus to Bacnet MSTP in each
of the RTUs. Then the Bacnet MSTP goes to a Bacnet MSTP
to Bacnet IP router. Then Bacnet IP goes to Trane Summit.

I first deleted the CPL logic someone created.
Then I checked the Disable Automatic Updates and manually
added the points, then performed the Edit/Add Object and property.
Added the Override buttons to graphics and now 3 out of 4 RTUs work.
I am able to adjust setpoints from the graphics.

The last RTU, someone disconnected the Simplicity board and installed
a line thermostat in the return duct to cycle the heat.
I removed the thermostat and re-connected the Simplicity board.
Went to the Trane Summit workstation and performed a point scan
and it seen the points. Went to lunch, came back and it stated
"cannot locate device 23004".
It seems comm is going in and out just on this unit.
I downloaded the Simplicity software but I need the adapter to connect.
As soon as I receive the adapter, I will check the Simplicity side and see
if I can see and adjust setpoints.
If I have able to see the Simplicity side, then I have an issue will
York ModLinc module in the unit. I tried to search for documents
on this module but I cannot find any.
Now, I wanted to know how to test these York modules.

I want to thank all you guys for the replies and the help!!!!!

willf650
04-06-2010, 07:12 AM
Try this, its a couple years old. Those units were some of the worst I've had to mess with. The larger York units are OK(Eco2) but those small ones aren't that fun to mess with. They do not accept BACnet priority levels. Seems any priority will write and last one wins.

ddc-tech
04-06-2010, 07:51 PM
Try this, its a couple years old. Those units were some of the worst I've had to mess with. The larger York units are OK(Eco2) but those small ones aren't that fun to mess with. They do not accept BACnet priority levels. Seems any priority will write and last one wins.


THANK YOU....this is what I been looking for!!!

So from reading this...since the address is the only
thing that needs to be changed on the ModLinc
and everything else is default (verified the 2300x device instance)
I will take that as the ModLinc is bad since my comm keeps
drops out and the last contractor already replaced the simplicity boards.
(don't worry I downloaded the simplicity software already and will verify)


I will order another ModLinc and let you know...

Again Thanks for all the replies.

smarco
07-19-2010, 09:21 AM
Did the new modlinc resolve the problem? I have a similar issue where I have a JACE controller that can see the BACNET/MSTP side of the Modlinc, however the Modbus side does not seem to communicate with the Simplicity Elite board. When the Modlinc is isolated and connected only to the Elite board it should overwrite any modified values with the default Modlinc values and this does not appear to be happening. Any additional thoughts would be welcome.