thierry2003
Member
- Join Date
- Oct 2003
- Posts
- 70
I always had a big interest in PLC's and automation but since my current job doens't allow me to do automation stuff myself I searched for some job (afterhours) myself.
So, after some weeks I already found someone who was willing to give me a shot.
The project was automating a palletizer used to palletize bags of potatoes. Since I had no practical knowledge of PLC's at all (I only knew what they're used for) I suggested that I would work on the 'no cure, no pay' principal.
So after talking a few times with my client it was time to buy the hardware. I started browsing these forums (and newsgroups, etc.) and came up with a 9,4" Easyview touch panel and a Automation Direct 260 CPU with 64 inputs and 48 outputs.
Luckely for me, my client, who I already knew a long time since he delivers to the factory I work in, wanted to pay for the parts himself. (so he could recuperate the VAT)
Finally it was programming time. I bought all the manuals from AD and just started playing with the PLC on my desk. Trying the timers, counters, simulating stuff on the touchscreen. After a week I already had my working program, at least, I thought I did
But when I got to my client and uploaded my program things were not working out as they should. The client didn't make a big thing out of it since I told him that I was still learning. After some debugging I saw my biggest mistakes. Double coiling was a major one. The other one was my debugging on site. I really started making a mess of my program! So I went back home and redid the whole program but this time I started out on paper, defining everything in small parts.
Went back to the site and saw my second big mistake. I used subroutines and make a major error. If you start a motor in a subroutine using an OUT instruction the output will stay on if the subroutine isn't called anymore, aargh.
That was the time when it all started making sense. I rewrote the whole program in 4 days and redid the HMI screens.
Went on site, uploaded everything and after debugging some small mistakes everything worked as planned. And I mean everything, it was a major rush! I simulated all the possible faults I could think off, explained everything to my client and so the machine is up and running now.
So, for everyone who wants to get into this stuff, my advice is JUST DO IT.
It will be hard, you will work long hours, but if you only talk about it it will get you nowhere. Find a real project and go for it.
This morning I spoke to my client and asked him why he got so much confidence in me. It was because I was always saying that I would try to make it work, even if it took me months. I never said that I was an expert I always told him that I was a beginner (I still am one). And the 'no cure, no pay' was the biggest one, 'Hell, if you are willing to pay for that stuff yourself, you must be sure of yourself'.
So, this is my first success- story, I hope many will follow.
Thanks to everyone on this forum for the help, actually I didn't asked a lot of questions but you can't imagine how the search-button on this site has helped me.
So, after some weeks I already found someone who was willing to give me a shot.
The project was automating a palletizer used to palletize bags of potatoes. Since I had no practical knowledge of PLC's at all (I only knew what they're used for) I suggested that I would work on the 'no cure, no pay' principal.
So after talking a few times with my client it was time to buy the hardware. I started browsing these forums (and newsgroups, etc.) and came up with a 9,4" Easyview touch panel and a Automation Direct 260 CPU with 64 inputs and 48 outputs.
Luckely for me, my client, who I already knew a long time since he delivers to the factory I work in, wanted to pay for the parts himself. (so he could recuperate the VAT)
Finally it was programming time. I bought all the manuals from AD and just started playing with the PLC on my desk. Trying the timers, counters, simulating stuff on the touchscreen. After a week I already had my working program, at least, I thought I did
But when I got to my client and uploaded my program things were not working out as they should. The client didn't make a big thing out of it since I told him that I was still learning. After some debugging I saw my biggest mistakes. Double coiling was a major one. The other one was my debugging on site. I really started making a mess of my program! So I went back home and redid the whole program but this time I started out on paper, defining everything in small parts.
Went back to the site and saw my second big mistake. I used subroutines and make a major error. If you start a motor in a subroutine using an OUT instruction the output will stay on if the subroutine isn't called anymore, aargh.
That was the time when it all started making sense. I rewrote the whole program in 4 days and redid the HMI screens.
Went on site, uploaded everything and after debugging some small mistakes everything worked as planned. And I mean everything, it was a major rush! I simulated all the possible faults I could think off, explained everything to my client and so the machine is up and running now.
So, for everyone who wants to get into this stuff, my advice is JUST DO IT.
It will be hard, you will work long hours, but if you only talk about it it will get you nowhere. Find a real project and go for it.
This morning I spoke to my client and asked him why he got so much confidence in me. It was because I was always saying that I would try to make it work, even if it took me months. I never said that I was an expert I always told him that I was a beginner (I still am one). And the 'no cure, no pay' was the biggest one, 'Hell, if you are willing to pay for that stuff yourself, you must be sure of yourself'.
So, this is my first success- story, I hope many will follow.
Thanks to everyone on this forum for the help, actually I didn't asked a lot of questions but you can't imagine how the search-button on this site has helped me.