Relight logic, could someone proof this?

Russ

Lifetime Supporting Member
Join Date
Jun 2002
Location
Ohio.. Go Bucks!!!!
Posts
261
Hello,
I could use a second pair of eyes to look this stuff over. I wrote up some code for automatically attempting to light a burner up to 3 times, and I wrote it remotely (on the modem since I'm almost 300 miles away). I also added a 20 position history log, whose values will be reflected on a panelview screen (once I'm onsite I'll dump the updated program into the panelviews).
Some of the logic is original, some I modified.

Code:
Rung
0000 all I added was the T4:50/TT xio
0001 I added the everything except the B3:255/0 and TON
0002 through 0007 written by me
0008 the alarm itself was untouched
[code]

This is part of a self-sustaining system. When the temperature goes 50F above setpoint the burner shuts off. At 10F above setpoint it turns back on (well it’s supposed to :)). Due to the nature of the system this doesn’t always occur, so I’ve added logic to give it a few more attempts. According to Reg 86 (1999 edition) the unit doesn’t need to purge before relight until the temperature is below 1400F. Even with that in mind I thought a mini-purge couldn’t hurt. 
 Please look it over. It is the attached file. Let me know if there’s something amiss. I'm using RSLogix500 version 5.20.00 (the logic I coded is in the attached zip file).

Thanks,
Russ
 
I've made a few slight adjustments since last night.
What I added was a way to store the number of relite attempts that occur in a week. This value (along with the week) can be stored for 4 weeks.
As usual, after I got offline, I thought that it would be a good idea to find out just how many times a flame failure occurs (shoot!). But that's just an easy fix, add another ctu and slightly adjust the storage rung to reflect the additional word (N13;102), which then offsets the stored word locations as well as their length. Oh well....
It looks alright to me, but I don't want to miss something.



Thanks,
Russ
(the new file has the same name, and it is zipped)
 
Well, I didn’t like something in the previous version so I made a final adjustment. A counter was also added to capture the number of flame failures that occur in a given week.
Did I miss something??



Thanks,
Russ
 
well... so far so good... one last change (brain-**** fix more or less) was done.. by placing the weekly ctu below the end of week move rung (transfer the current data to history)... that's about it...
It seems to be working pretty well.. the only thing is that so far it seems that the burner has lit on its first attempt every time (well I should say within the past 20 cycles that I can see whenever I get online with it)....
Anyways.... so far so good I guess... I'm thinking about adding two more words so that I can capture how many times the burner lites after 2 attempts and how many times the burner lights after 3 attempts.

Anyways... merry christmas everyone!!




Russ
 

Similar Topics

Hello, I am trying to replicate a piece of logic on the PLC5 onto an SEL RTAC. I am using ladder on SEL and FBD. I am having issue on the ladder...
Replies
10
Views
110
Hello again..trying something on an existing poorly written program and just wanted to double check something system is an A-B MicroLogix 1200 In...
Replies
5
Views
165
Good morning fellow sea captains and wizards, I am being asked to do the above and obtain 4 values from each slave, I know about the MRX and MWX...
Replies
27
Views
631
I have a machine which is undergoing upgradation. As part of the process two SEW drives are being replaced., existing Gen B with new Gen C. The...
Replies
3
Views
197
Hello Dear users, I am writing about a problem that has been bothering me for a few days, i.e. I am trying to establish remote access to the Allen...
Replies
0
Views
88
Back
Top Bottom