I do not touch a program without a backup

If I do not have a copy of the old program, I do not say «it was like this» from memory. I do not change a line before I take the copy. If the copy cannot be taken I write that and I do not touch the program that day. Someone who talks as if they touched it cannot put the line back the next day. I do not like that morning. If the password is with you, bring it. I do not try to break the password. A password that cannot be broken turns a program job into a read job. A read is still useful: I write which input is lying, and I do not invent the program.

A drive code is not a PLC code. OC, OCF and similar words have the drive's own page. I do not cheapen them here. If there is a smell I do not have the drive reset a second time. If there is no smell, once, then it stops. I do not open its cover while it is live. The DC bus stays charged for a while. I have seen someone put a screwdriver in the cover without knowing that. I do not put one in. I also do not run an autotune on an empty oven. A drive that learned while the oven was empty gets lost when the oven is full.

If the sensor lamp is on and the shaft is not moving, the sensor is lying. I do not correct the program to match that lie. I see the sensor on site: dust, a lost setting, a crushed cable. I do not treat a crushed cable as a program line. If a contactor has welded, the output goes dark and the motor still turns. That is not the program either. A welded contactor has its own sound. I described the hum on its own page. I do not write it again here like an advert. I separate it, I write it, and I do not dump the contactor onto the program.

I do not open the cover while it is live. I do not approach the panel on a wet floor. Do not clear the alarm and say «it fixed itself» either. The cleared alarm is the sentence I was going to read. When the sentence goes, the read gets longer, and the figure gets longer. I say the longer part before I start. I want a photo: the writing on the screen, with the cover closed. Do not photograph the inside of the cover with a flash.

4,000 to 12,000 TRY is for reading. It covers which input went quiet, which output is lying, and noting a drive code and leaving it. 10,000 to 35,000 TRY is for a change in the program after the backup is taken. I do not make the two into one price in an advert. Nights and public holidays are separate. If a contracted plant has a contract time standing, I do not break it. We work as an approved technician network. I do not talk as if I had a crew. I do not leave Istanbul for Gebze from this page. The arrival window is stated clearly on the call.

When I finish I write where the backup sits, what I changed, and what I deliberately did not touch. The thing I do not touch is usually a drive parameter. I do not open it without a backup, with a smell, on a second reset. I take your approval before I put the pencil down. I do not write a locked price for a line I have not seen.

I do not like changing a program on the night shift. The operator is tired, the alarm has been cleared, and the last button is not remembered. A button that is not remembered lengthens the read. If the read will lengthen I say, before I put the pencil down, where it will land in the 4,000–12,000 band. I do not say «the program finishes by morning» before I say that. A job that can finish by morning is one whose backup has been sitting since afternoon and whose alarm was not cleared. On a cleared alarm I only take a note at night. The note holds the place of the program in the next daylight. If I change a line that night as if it did not, I cannot put the line back in the morning.

Someone who saves the backup on the desktop as «final» does not know a week later which final it was. I write the folder's name with the date. Do not think I put the password inside the folder. The password stays with you. I write the folder's place in the note. I do not make a second change without looking at the note. If the second change is written on top of the first backup, the way back dies. A dead way back leaves the job in the 10,000–35,000 band to luck. I do not leave it to luck. If I did I would be repairing memory, not the line. Repairing memory is not this page's promise.

A quiet motor is not always the quiet of the program. If the contactor coil has burnt, the output command goes and the motor does not move. Someone who treats the coil as a program line and raises the value finishes the burnt coil with overcurrent as well. I measure the coil. If it has burnt I write the replacement separately. I do not bury it in the program band. If the drive is writing a fault I leave that writing on its own page. Here I only separate the input and the output the PLC sees. While I separate them I do not open the cover live, I do not print a parameter number, and I do not run a learn on an empty oven. Those three stand as the border of this page, not as a decorative sentence.

If the read is finished and the program will not change, I stay in the 4,000–12,000 band. I do not force the 10,000–35,000 sentence. Forcing it is talking as if I took a backup and not changing a line. If I will change a line I write the date of the backup folder in the note, I leave the password with you, and I do not put the pencil down on the night shift. The pencil goes down in daylight, if the operator remembers the button. If they do not, the alarm was cleared, the read lengthens, and the lengthening is said before it starts. A lengthening that is not said is a second invoice in the morning. I do not invent a second invoice on a contracted plant either. If the contract time is standing I do not break it, and I do not promise my own minute. I do not leave Istanbul. The note I write before I leave carries which input is lying and which motor went quiet because of its coil. If the coil went quiet, the program band does not inflate.

A read and a program are not the same invoice. The read is 4,000–12,000. The program after a backup is 10,000–35,000. If I gather the two in one sentence I would look as if I changed a line without taking a backup. I do not stand there. Before a line changes, the folder's date stays in the note, the password stays with you, and a parameter number is not written on this page. What gets written is which input is lying and which motor went quiet because of its coil. If the coil went quiet I do not also carry the drive code here. Carrying it would bury an OC writing inside the program band. Burying it is a second invoice. I do not invent a second invoice with a night note either.

If the card's label says 24 volt direct current, that screw does not accept 230. The person who ties a 230 volt sensor to this card burns the card that day, then blames the program. The lamp of a burnt card is dark, and the shaft is quiet too. I do not treat that as a program line. If the sensor is PNP, its output pushes toward positive. If the card's common looks toward negative, the lamp lights on the sensor and the PLC input lamp does not. I do not correct the program to match that picture. I seat the common on the label. I do not write an NPN sensor the same way onto a common that looks toward positive. A transistor output card does not pull a contactor coil. The coil goes to a Schneider or Siemens interface relay. On a direct-current coil the diode sits across the two ends of the coil. A coil without the diode punches the transistor the first time it drops. I do not revive a punched output by forcing it in the program. I do not fit a diode on an alternating-current coil. If I did, the coil would hum and the card would heat again.

I do not feed a contactor coil from the PLC's 24 volt sensor supply. That supply belongs to the card. The coil collapses it. On a collapsed supply every input goes dark at once, the line stops, and the blame is written on the program. The blame is in the supply. On a 4–20 milliamp analog input, zero does not mean the tank is empty. Zero is a broken wire. Four milliamps is the live zero. The wire is still there even if the tank is empty. Shifting the scale in the program while the wire is broken, so that zero looks full, overflows the tank on the next fill. The shield comes down at one end, onto the panel earth bar. A shield that comes down at both ends makes the reading wander. I do not treat a wandering reading as a program constant. If I wrote a constant, the operator would push more into a tank that is already full.

The coil terminals of the interface relay are A1 and A2. The contact is 11 and 14. The person who writes the coil onto the contact and the contact onto the card leaves the motor quiet while the PLC output is lit. I do not treat that as the program. The card's output goes to A1, and the card's zero goes to A2. 11 and 14 are the path of the contactor coil. I do not write the path backwards and change a ladder line. The small lever on top of the relay is for pulling it by hand. I do not leave the lever held down with tape. A taped lever does not stop the line when the sensor fails. The operator thinks the tape is temporary, and the tape stays until evening. Tape that stays until evening is the same fault as a force forgotten inside. I take both off before I leave.

A forced bit is not the program in the dated folder. The force sits inside the CPU. When only the program comes down into the folder, the force does not come down. After I leave, the line listens to that bit, not to the real sensor. Before I leave I write the list of forces and I clear all of them. If a bit will not clear, I write its address in the note and I do not count the job finished. Finished would mean the next shift works on a blind line. If the CPU is in STOP, the switch is on STOP or a fault has stopped it. I do not download a new program before I read the switch and the record. If I downloaded, I would write over a record I have not read, onto a CPU that is stopped. The record is which input went dark. There is no download while the record is standing. A download is the 10,000–35,000 band, and it comes after the backup. I do not write the force inside that band as if the program had changed.

If the remote rack's BF lamp is red and the local input lamp is green, the fault is not in the program. The rack's station name is not the same as the name in the project, or the cable is a telephone cable. A bus does not run on a telephone cable. A shielded industrial cable goes in. I do not invent the name and change a ladder line. If an old CPU's battery is finished, the program goes when the power is cut. I do not write the gone program from memory. If there is no dated folder I do not write a line that day either. If I did, in the morning the line would start in the order I invented. The work does not leave Istanbul. Gebze is not written from this page.

The band below is the published 2026 list. It is an estimate. The binding figure is written on site after measurement, and the work starts after that.

Service covers the neighborhoods of Istanbul's 39 districts. Not the whole of Turkey. A survey is not a binding quote.