Tracer Summit v17

[jingoism]

I am having an issue with some of our BCU's and thought someone might enlighten me as to what they think this could be.

The problem is that last week I came in and three or four of my BCU's had a new override that set all of the air handler and pump setpoints to 0. I did a clear ram and reset ( first time ive had to do that ) and was unpleasantly surprised to find out that instead of setting all my defaults back it just ramped all my equipment up to 100%. It finally managed to come back online and then the defaults had been reset, but you can imagine what might of happened when my pumps shot to 100%. :oops:

We are using tracer summit v17 and have a dialup connection to each BCU ( yes I know it sucks not my idea ).

After I cleared all of the overrides from the sites ( by hand since im now scared of CRAR ) everything was good again.

I came in today and one of the sites I cleared out AGAIN had all the setpoints set back to 0 by an override. :eek2:

I havent been using TS very long, but what could possibly keep injecting this override back into my BCUs? I know its not tracer summit because were on dialup and we were not dialed up. There is another group on site that has access to the BCUs through TS, but they swear up and down they haven't been connecting.

[scrooloose]

In your override screen you should see at what level (1 through 16) and who did it and when. For example it would say 12 - User low by joe at 2/16/10 5:30 am.

Find out what is controlling it then you can narrow down more what might be happening.

On the CRAR the BCU goes offline for the period of time it takes to start back up (all overrides are erased and default values will be used, once equipment starts communicating again. Could be 5-10 min on Lon link). If you do not have good comm loss/default values in the equipment (mp580 specifically) you risk the chance of your equipment not being under control and having unforeseen issues. I would recommend placing items in hand if it is critical enough that damage could occur.

[summit-dude]

Do you have user profiles set up or does everyone sign in using a default username and password??? Find out what priority the overrides are at and insure that you don't have some kinda screwy CPL controlling these points. If you dont have profiles set up for individual users I'd recommend it. This way you can set up your alarm log to display system print events and you will know when someone logs in and as scrooloose said you will know who overrode what point then you can take that ability away from that user.

[jingoism]

We only have two users set up on the system and one has only read privileges.

It shows up as Custom Programming ( lvl 16 ) and the user shows up as Incoming Request Server.

EDIT: I'm the only one with access at our terminal to make changes, but not the only one on our site. I have no control over what the others are doing though ( crazy I know, but it is what it is ).

[willf650]

We only have two users set up on the system and one has only read privileges.

It shows up as Custom Programming ( lvl 16 ) and the user shows up as Incoming Request Server.

EDIT: I'm the only one with access at our terminal to make changes, but not the only one on our site. I have no control over what the others are doing though ( crazy I know, but it is what it is ).




Do you have some type of external front end some where?
Sounds like another device/system is munipulating points. Only time I've ever seen the controll property of Incoming Server Request was in a BACnet integration application.

[jingoism]

That's actually why I am writing this.

I think its someone from the site trying to control the system, but I have to make sure it's not something I am doing before I point the finger of doom. :rules:

[willf650]

When I say external device/front end I'm not talking about another Tracer Summit computer. Unplug the network cable and see if you issue goes away. If you dialing into it, it won't hurt anything. If some one else is munipulating points via a Summit work station or custom programing it should state the user, program name or CPL Interpruter. As far as I know, as I stated, Incoming Server Request is from a BACnet device.

[jingoism]

I should have been more clear on my reply.

Yes I think it is another device that is attached to the BCU through the ethernet cable running from the wall. I have no access to said ethernet and have absolutely no idea where it goes, or what is attached to it.

Its all rather confusing to try and diagnose since I do not have full access to the whole system, but such is life. :rolleyes:

[scrooloose]

Honestly with the problem you are seeing, it is more than we could help you walk through on here. Unfortunantly your best bet is to get someone out there who has experience with getting in the BCU and investigating what other device is talking to it through the ethernet.

Without having full access to network or without know what else is out there on the network you are just in the dark to much to troubleshoot this.

[jingoism]

I found some information out today on the eth link and I am working with the others on trying to figure out what is talking to the BCU.

All I know for sure is that it's nothing on my end, and it must be coming from the eth link.

[M100 Tech]

Usually incoming request server is seen with a BACNET panel.

[jingoism]

Well I still have had no luck at tracing down the problem since the equipment in question is not accessible without an escort, but I already fixed it the best way I know how at this time.

I wrote a CPL program that will check all of the points in question, and if they are changed more than 10% it will immediately change them back to the default.

I know that it's a pretty nasty hack, but it will have to do until I can find the actual culprit.:eek2: