Servo Motor is a device that can rotate with a certain amount of the desired angle. Servo Motor consists of four basic components, namely: motors, gears, feedback devices (such encoder) and the circuit controller. Motor will rotate through several gears and shaft encoder simultaneously. Encoder sends a signal to the controller circuit. If the controller circuit detects the correct position, then the controller will stop the motor circuit.
As industrial facilities become increasingly automated, the electronic equipment controlling manufacturing processes becomes more advanced, and more sensitive to voltage fluctuations. Servo motor systems, overseen by programmable logic controllers (PLCs), are what control automated processes where precision handling of material is required. One such process is the conveying of a product to a robotic welding arm at the split second that the arm is positioned to make contact.
Read more: http://www.articlesbase.com/electronics-articles/characteristic-plc-based-servo-control-system-3529166.html#ixzz1RVBfEGBE
Under Creative Commons License: Attribution No Derivatives
2011年7月8日 星期五
What Makes a Good PLC Program?
PLC programmers have been faced with a steep learning curve over the last 25 years, as technologies have moved quickly and almost all industries have implemented programmable logic controllers as a standard. This means that good experienced programmers are hard to find, and while most companies offer programming services there are important features which are often missed out.
Firstly a PLC programmer should write code so that it can be easily understood. Documentation and structure are essential. This often involves a working knowledge of the plant or process, a good PLC should be able to solve engineering problems from a specification, not just produce lines of code. From my experience the best PLC programmers are always firstly engineers.
Secondly the end user should never need to look at the PLC programmer's code this might seem a contradiction of point one but a good program will perform without intervention. I work on the theory if something looks rushed and untidy it usually is.
Thirdly think robustness this means if a machine or process stops the operator/technician should know why straight away, diagnosing software faults should not require a specialist. With the implementation of field busses and integrated devices this becomes increasingly difficult as programmers often adopt the Idea of it works leave it, upon the first failure nobody can ever diagnose the issue. When using new technologies time should be spent looking at the functionality. In a recent project I managed to mimic the entire Profibus network with over 50 drives into the SCADA, two days later a drive faulted and an operator was able to show the maintenance guy exactly where the fault was, the drive was replaced and production resumed within half an hour. Think information and look at what can hang up the operation.
One good technique I have found on making code more robust is sequential counts; I have spent the last 5 years developing my own ladder sequential charts. After working with manufacturers own add -on packages ,at a premium, my opinion is ladder steps are more cost effective and usable.
Documentation - As a minimum every PLC code should include as a minimum an Operand comment, whether this is an input output or internal register. In my project I will also always try to cross reference this with the electrical drawing. Block Comment the first block in a PLC code should include important traceability information, a comment of any modifications the date and reasons should be quickly visible. Rung comment all rungs should give a functional description of what they are doing.
Structure - Structure should always follow the flow of the machine, for example a packaging machine should start a infeed, define each operation in a separate routine and end with the out feed. This technique seems to have been missed by many programmers making diagnosis and modification difficult.
It should never be underestimated how much machine/process availability can be increased through good programming techniques. Remember PLC programming is not a black art, just because something is not visible does not mean it should not be done correctly. Always demand more from systems integrators and PLC programmers.
Read more: http://www.articlesbase.com/programming-articles/what-makes-a-good-plc-program-1169532.html#ixzz1RUysHWwI
Under Creative Commons License: Attribution No Derivatives
PLC|伺服馬達動作,分析
PLC|伺服馬達動作,分析
昨天在客戶廠內,看韓國機台的動作。
有一個左右移的平台,上搭配一個0度~90度的角度軸。
各自由一個伺服馬達帶動。
需要的動作:
1.平台在0度,跟接收玻璃位置。
2.等接收完成後。
3.平台升到90度,右移到放玻璃的位置。
有個干涉的部份。
在0度時,不可直接移到放玻璃的位置。
(會撞到門)
=========================
韓國人的動作是:
接收完玻璃後。
1.平台右移一小段(不會撞到門)
2.升到90度
3.平台再右移到放玻璃位置。
因為是2個伺服,3段動作,就會有3個加減速。
=============================
如果是自已寫的動作:
接收完玻璃後。
1.升到90度
2.平台再右移到放玻璃位置。
減化動作。也不會有撞機的危險。
昨天在客戶廠內,看韓國機台的動作。
有一個左右移的平台,上搭配一個0度~90度的角度軸。
各自由一個伺服馬達帶動。
需要的動作:
1.平台在0度,跟接收玻璃位置。
2.等接收完成後。
3.平台升到90度,右移到放玻璃的位置。
有個干涉的部份。
在0度時,不可直接移到放玻璃的位置。
(會撞到門)
=========================
韓國人的動作是:
接收完玻璃後。
1.平台右移一小段(不會撞到門)
2.升到90度
3.平台再右移到放玻璃位置。
因為是2個伺服,3段動作,就會有3個加減速。
=============================
如果是自已寫的動作:
接收完玻璃後。
1.升到90度
2.平台再右移到放玻璃位置。
減化動作。也不會有撞機的危險。
2011年7月7日 星期四
PLC|CIM write by PLC Part-12
PLC|CIM write by PLC Part-11
CIM 除了上報BC外,
還有跟上下游機台在交握,
上/下游機台也是一台設備,
也是一樣在寫CIM的程式,
所以有時候,傳遞的信號錯了,
不需要認定一定就是自已程式的問題,
也有可能是上游機台在傳遞時,
發生了問題。
我們寫CIM程式,會發生問題,
相對的,上下游機台,也是在寫CIM程式,
當然也會發生問題。
CIM 除了上報BC外,
還有跟上下游機台在交握,
上/下游機台也是一台設備,
也是一樣在寫CIM的程式,
所以有時候,傳遞的信號錯了,
不需要認定一定就是自已程式的問題,
也有可能是上游機台在傳遞時,
發生了問題。
我們寫CIM程式,會發生問題,
相對的,上下游機台,也是在寫CIM程式,
當然也會發生問題。
PLC|基礎篇-1
PLC最根本的就是動作:
控制一個(元件Y)。
精密度要要求一點,
會再加上(到位信號X)
再要求一點,
會加上時間計數(T)。
這就是最基本,也算完整的監控迴路。
==============
以氣缸定位來說明:
1.氣動電磁閥就是Y(輸出)
如果只是Y ON/OFF變化,
也可以達到氣缸前進/後退的動作。
PS:PLC不知道氣缸是否有動作,何時到定位點????
2.如果再加上氣缸定位檢知SEOSNR(磁簧開關)
當Y ON後,如果定位檢知,就知道已經完成定位了。
也可以減少時間。
PS:如果氣壓源不足,或是沒氣,也不會動。
3.再送出Y後,再加上時間檢知,
就可再檢查氣缸的動作,是否順暢,是否有異常。
一般氣缸如果只要3秒,時間檢知可以設為4秒,
如果氣缸4秒未到定位,就表示有問題了。
PS:如果要再精密一點,可以針對氣壓源檢查壓力是否足夠。
控制一個(元件Y)。
精密度要要求一點,
會再加上(到位信號X)
再要求一點,
會加上時間計數(T)。
這就是最基本,也算完整的監控迴路。
==============
以氣缸定位來說明:
1.氣動電磁閥就是Y(輸出)
如果只是Y ON/OFF變化,
也可以達到氣缸前進/後退的動作。
PS:PLC不知道氣缸是否有動作,何時到定位點????
2.如果再加上氣缸定位檢知SEOSNR(磁簧開關)
當Y ON後,如果定位檢知,就知道已經完成定位了。
也可以減少時間。
PS:如果氣壓源不足,或是沒氣,也不會動。
3.再送出Y後,再加上時間檢知,
就可再檢查氣缸的動作,是否順暢,是否有異常。
一般氣缸如果只要3秒,時間檢知可以設為4秒,
如果氣缸4秒未到定位,就表示有問題了。
PS:如果要再精密一點,可以針對氣壓源檢查壓力是否足夠。
2011年7月5日 星期二
PLC|找bug除了用眼睛看,用耳朵聽才重要。
PLC|找bug除了用眼睛看,用耳朵聽才重要。
一般人用眼睛找機台的動作是否正常。
但眼睛看不到的地方呢?
眼睛有視覺暫留,超過60hz,就難以分辨。
但耳朵可以聽到的音頻是20hz~20khz。
還有聲音的傳遞,不會因為看不到,就聽不到。
例:培林因為外力偏移磨擦時,通常看不出來,但會有磨擦的聲音。
如果不適時的找到發聲點,培林就會磨壞了。
機台正常運轉時,不正常的聲音,也是重大問題發生的前兆。
一般人用眼睛找機台的動作是否正常。
但眼睛看不到的地方呢?
眼睛有視覺暫留,超過60hz,就難以分辨。
但耳朵可以聽到的音頻是20hz~20khz。
還有聲音的傳遞,不會因為看不到,就聽不到。
例:培林因為外力偏移磨擦時,通常看不出來,但會有磨擦的聲音。
如果不適時的找到發聲點,培林就會磨壞了。
機台正常運轉時,不正常的聲音,也是重大問題發生的前兆。
2011年7月4日 星期一
PLC|順序動作 常見的幾種方法
PLC|順序動作 常見的幾種方法
1.自保式
|-|Y0|-| X2|-+---(Y1)-|
|-|Y0|-|/Y2|-+
|-|X1|-------+---(Y0)-|
|-|Y0|-|/Y1|-+
2.SFIFT(BSFL指令)
|-|/Y0|+|/Y1|+-/--[BSFL Y0 K2]-|
|-|/X0|+|/X1|+
Y0,,Y1是步序的順序
X0,X1是條件
3.DECO(BSFL指令)
|-|M0|-|X1|---[MOV K1 D0]-|
|-|M1|-|X2|---[MOV K2 D0]-|
|-|M2|-|X3|---[MOV K3 D0]-|
|-|SM400|----[DECO D0 K1]-|
PLC的寫法很多,沒有標準答案,
全看使用者的經驗&習慣。
1.自保式
|-|Y0|-| X2|-+---(Y1)-|
|-|Y0|-|/Y2|-+
|-|X1|-------+---(Y0)-|
|-|Y0|-|/Y1|-+
2.SFIFT(BSFL指令)
|-|/Y0|+|/Y1|+-/--[BSFL Y0 K2]-|
|-|/X0|+|/X1|+
Y0,,Y1是步序的順序
X0,X1是條件
3.DECO(BSFL指令)
|-|M0|-|X1|---[MOV K1 D0]-|
|-|M1|-|X2|---[MOV K2 D0]-|
|-|M2|-|X3|---[MOV K3 D0]-|
|-|SM400|----[DECO D0 K1]-|
PLC的寫法很多,沒有標準答案,
全看使用者的經驗&習慣。
訂閱:
文章 (Atom)