Someone help please!!! LCI-R

[lancerbomb08]

So here's my problem. I have about 9 smaller RTU's ranging from 3-7.5 tons. I am interfacing with these via the Lontalk board installed in these units. This, for the record, is the first time I've worked with these particualr units. Problem is, when I try to commission the boards, I get a program ID mismatch on all of them. This leads me to believe I have a bad XIF file. It tells me the error evolves from the nviOccSchedule which I won't even be binding to. Any help would be appreciated. If anyone also knows where to go and download a different file, that would be great too.

Any thoughts??

[dapper]

Best way is to 'upload from the device'.

[lancerbomb08]

already tried that....lol

BTW...i like your sig

[lancerbomb08]

so new question....if uploading from device doesn't fix it, what else could be causing the ID mismatch?? (subsystem#38)

[lancerbomb08]

ill check back in the morning before heading back to the site. But after doing a little more research, i might just try to rebuild the database if nothing else works. It might have been engineered wrong completely. Wouldnt take a long time, 9 LCI's and 6 programmables

you know what they say, its hard to stop a trane but its hard to start one too

[Gleng]

Why not just let the units run with a simple thermostat.Sounds like a lot of over controlled headache crap to me!!!!It is a rooftop unit,not a chiller.Keep it simple and it will work as intended.

[lancerbomb08]

Why not just let the units run with a simple thermostat.Sounds like a lot of over controlled headache crap to me!!!!It is a rooftop unit,not a chiller.Keep it simple and it will work as intended.

THATS WHAT IM SAYING!!!!!

haha. It is running off of a stat. They want to monitor fan command and run indication (for servicing purposes for a fan failure), space temp and want to send it occupancy.....city job...lol

but other than that, the unit is pretty much a stand alone system

[lontshooter]

lancerbomb08
The first thing that I would do will be to create a new network database and see if you can commission one of the boards in the RTU's.
If that works then the DB that you are using is not the correct DB, it could be older than what the device are comission with.
Next I would download the xif from the manufacture and plugin if they are available.
If you can find it at the manufacture then go to Lonmark.com and look there for them.
The program ID mismatch is from the device info does not match the DB info.
Is there a error message that goes with the mismatch, that would help also.

Lontshooter

[lancerbomb08]

Yes. It's being caused by nvoOccSchedule. When I open the XIF in text format, it shows to have two OccSchedule's. That would be my first guess.

Also, where can I go to download the stencil or do I just use a basic shape in visio. And I can't find a clearly updated xif file anywhere. Checked trane and lonmark.

[dapper]

Gleng.... have you got any T87Fs that you can lend him?
I see that you need an avatar, maybe freddy-b will let you share his.

[crab master]

What is your Network Management tool? If it is LonMaker Turbo you can have LonMaker ignore the program ID mismatch and still get the info, under the device templates find the RTU template and right click and choose properties and then choose ignore Program ID mismatch, you might have to also select something else, but from memory there are 3 buttons that are all selected by default. When that is done re-commission.
If your running the Non-Turbo LonMaker then I find what device template the RTU's are using and then delete all your 9 RTU's on the LonMaker drawing and resycronize. Then go into your device templates and find the template for the RTU's and delete that. Next do a commission but make sure you choose upload from device.
BTW - when you get this working you will see it will be worth it. You can get a lot of data, granted likely more than you'll ever need but when you need it...

[lancerbomb08]

Crab master- thanks man. I was already on the phone with a super smart guy in our tech support this morning and that's what he had me do. Delete devices and templates and add them back in and upload. And yes I'm using regular lonmaker. But you hit it right on the head. Everything is commissioning and coming up online perfectly now. The problem was is that I had an out of date xif and god knows trane can't post the new one up anywhere. Haha. But thanks everyone for your help. This is a great site with a ton of knowledgable people.

[crab master]

Glad to help and thanks for the update.

[Gleng]

It is just amazing to me that so much money would be spent on simple rooftops to see if they are running .I do not know the computerized system you are dealing with here.Nor do I care to learn about an unnecessary monitoring system.I guess someone has a bunch of money to piss away.Good for you,Take their money!!! Actually,explain to me the benefits of such a system.I am always looking to learn.Since i am not a big control guy.Let things stay simple .Less headaches

[crab master]

Nor do I care to learn about an unnecessary monitoring system.

So am I wasting my time responding to this part of the thread?


Actually,explain to me the benefits of such a system.I am always looking to learn.

Okay, maybe I can make a point or two. :D

You say simple rooftops, but what if that rooftop is controlling a server room, or how about a chocolate candy store? In this case you want monitoring, as the cost of replacement due to overheating the area more than justifies the cost of monitoring. Yes many systems have more than what they 'need' but then again when things can be adjusted remotely you can help control costs. The problem many times service techs run into is they see a control system and they throw up their hands. There can be frustration, but the integrated circuit boards on equipment is a control system in and of itself. Let's say a service call comes in but your techs are all busy and you look up the system to see it's calling for the fan but you have no airflow, well now you could send a filter changer/summer help out to look at it to check some of the basics - belt, filters, iced up, etc. Or what about a simple setpoint change or a general occupancy schedule applied to all the RTU's. How many times have you come into buildings and the schedules on all the stats are different when they should be the same? Think about the energy savings alone with 10-15 years average life operation on a RTU, let alone the life expectancy potentially added, which that alone typically will justify the upfront costs.

Here's a post of an end user that wants controls - http://hvac-talk.com/vbb/showthread.php?p=5564412&posted=1#post5564412

[Gleng]

O .K. I see your point in a critical situation and some other situations.Still seems like over kill for"most" situations.I guess it is good for when you need it!!!!! Spoke to a friend of mine,I have seen the system before,just have not needed to utilize it.Maybe I will need it in the future.

[24vac]

Here is a simple solution for rooftops and sends out email alerts.

http://www.mamacsys.com/ip_mt_101_description.html