HootnHoller
Guest
H
Hey All,
First, let me say that this is a great database of information. I have read through all the posts and amazed at the politeness, courteous and very intelligent answers/discussions I have seen. Keep up the great work and believe me, learned a thing or two on the way to this post ;-).
I have a question that is going to fall a bit from the normal post and would sincerely appreciate any input that you all may have.
First, a bit about myself, I have been an industrial technician for about 14 years. I have a knack for computers and electrical, and kinda 'fell' into plc programming. Most of my experience is with AB setups, AI, rs logix, slc, some panelmate, etc... But most has been from a troubleshooting aspect. Running diagnostics with a plc is a great tool to help with mechanical/electrical malfunctions, but the programming always intrigued me. Some of my coworkers would pick on me, since I would watch the leds on a plc, like the screensaver from the matrix, and 'pick out' the problem, without the schematic. (okay, probably more info then you needed...)
To continue, I have worked with plc contractors in the past, and recently, been offered a possible position with a programmer for a general machine builder. I have diagnosed this person's programs on site, to save him some travel time and believe I made an impression. Mostly, due to him allowing me to call him and discuss the issue, then following his instructions to the letter. Plus, I think he found an 'ally' in this scenario, since most people love to blame the program in my field, and I do have an idea on how rough it can be to think of every possible scenario. Plus, I have extensive knowledge in mechanical problems. An example: 'that cylinder isn't firing, the program must be corrupt!' "Did you remove an air line to check for blow by on the cylinder or valve?" 'Uh, no....' "Let's start there, the program worked fine yesterday..." Does this sound a bit familiar?
Anywho, due to recent events, I have been laid off due to my position being eliminated with my current company and have been fortunate enough to have a relative pay for a class with Allen Bradley. I am going to sign up for the Intermediate course in programming on Monday and start taking the class on Tuesday.
Okay, now that I bored you with details, and if you made it this far, thank you for your patience. My question is this... Should I try and land a job as a programmer with a machine builder, or should I contract, given my limited knowledge? I would like to contract, but no idea on how much to ask for contracts, pay, travel time, etc... and that does leave me a bit leery. Yes, I do doubt my abilities. I seem to do 'better then the average bear', but I do not classify myself in the realm with a lot of you fine people. In a nutshell, I'm mainly a grease monkey trying to climb the tree for the better bananas. Any input and experiences that you would be willing to share would be greatly helpful.
Hoot
First, let me say that this is a great database of information. I have read through all the posts and amazed at the politeness, courteous and very intelligent answers/discussions I have seen. Keep up the great work and believe me, learned a thing or two on the way to this post ;-).
I have a question that is going to fall a bit from the normal post and would sincerely appreciate any input that you all may have.
First, a bit about myself, I have been an industrial technician for about 14 years. I have a knack for computers and electrical, and kinda 'fell' into plc programming. Most of my experience is with AB setups, AI, rs logix, slc, some panelmate, etc... But most has been from a troubleshooting aspect. Running diagnostics with a plc is a great tool to help with mechanical/electrical malfunctions, but the programming always intrigued me. Some of my coworkers would pick on me, since I would watch the leds on a plc, like the screensaver from the matrix, and 'pick out' the problem, without the schematic. (okay, probably more info then you needed...)
To continue, I have worked with plc contractors in the past, and recently, been offered a possible position with a programmer for a general machine builder. I have diagnosed this person's programs on site, to save him some travel time and believe I made an impression. Mostly, due to him allowing me to call him and discuss the issue, then following his instructions to the letter. Plus, I think he found an 'ally' in this scenario, since most people love to blame the program in my field, and I do have an idea on how rough it can be to think of every possible scenario. Plus, I have extensive knowledge in mechanical problems. An example: 'that cylinder isn't firing, the program must be corrupt!' "Did you remove an air line to check for blow by on the cylinder or valve?" 'Uh, no....' "Let's start there, the program worked fine yesterday..." Does this sound a bit familiar?
Anywho, due to recent events, I have been laid off due to my position being eliminated with my current company and have been fortunate enough to have a relative pay for a class with Allen Bradley. I am going to sign up for the Intermediate course in programming on Monday and start taking the class on Tuesday.
Okay, now that I bored you with details, and if you made it this far, thank you for your patience. My question is this... Should I try and land a job as a programmer with a machine builder, or should I contract, given my limited knowledge? I would like to contract, but no idea on how much to ask for contracts, pay, travel time, etc... and that does leave me a bit leery. Yes, I do doubt my abilities. I seem to do 'better then the average bear', but I do not classify myself in the realm with a lot of you fine people. In a nutshell, I'm mainly a grease monkey trying to climb the tree for the better bananas. Any input and experiences that you would be willing to share would be greatly helpful.
Hoot