‫‪Techno-Electro.

com‬‬

‫ﺑﺴﻢ ﺍﷲ ﺍﻟﺮﺣﻤﻦ ﺍﻟﺮﺣﻴﻢ‬

‫ﭘﻴﻜﺮﺑﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ‬

‫ﺷﺒﻜﻪ ‪PROFIBUS‬‬
‫ﺑﺎ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪STEP7‬‬

‫ﻣﻬﻨﺪﺱ ﻋﻠﻲ ﻛﺮﻳﻢ ﺍﻟﺪﻳﻨﻲ‬ ‫ﺗﺎﻟﻴﻒ ‪ :‬ﻣﻬﻨﺪﺱ ﻣﺤﻤﺪ ﺭﺿﺎ ﻣﺎﻫﺮ‬

‫ﺑﺎﻫﺘﻤﺎﻡ ‪ :‬ﺷﺮﻛﺖ ﺻﺎﺑﻜﻮ‬

‫‪Techno-Electro.com‬‬

‫ﺍﻳﻦ ﺻﻔﺤﻪ ﺑﺮﺍﻱ ﻣﺸﺨﺼﺎﺕ ﭼﺎﭖ ﻣﺎﻧﻨﺪ ﺗﻴﺮﺍﮊ ﻭ ﺷﺎﺑﻚ ﻭ ‪ ....‬ﺭﺯﺭﻭ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
Techno-Electro.com

‫ﭘﻴﺸﮕﻔﺘﺎﺭ ﺻﺎﺑﻜﻮ‬
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﭘﻴﺸﮕﻔﺘﺎﺭ ﻣﻮﻟﻔﻴﻦ‬

‫ﺳﭙﺎﺱ ﻣﻌﺒﻮﺩ ﺑﻲ ﻫﻤﺘﺎ ﺭﺍ ﻛﻪ ﺩﺳﺖ ﻟﻄﻔﺶ ﻣﺎ ﺭﺍ ﺩﺭ ﺗﻬﻴﻪ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﻳﺎﺭﻱ ﺑﺨﺸﻴﺪ‪.‬‬
‫ﺁﻧﭽﻪ ﭘﻴﺶ ﺭﻭ ﺩﺍﺭﻳﺪ ﻣﺎﺣﺼﻞ ﻧﻜﺎﺕ ﻣﻬﻢ ﻭ ﻣﺒﺎﺣﺜﻲ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﻣﺪﺍﺭﻙ ﻣﺨﺘﻠﻒ ﺍﺯ ﺟﻤﻠﻪ ﻣﺴﺘﻨﺪﺍﺕ‬
‫ﮔﺴﺘﺮﺩﻩ ﺯﻳﻤﻨﺲ ﻭ ﻣﺪﺍﺭﻙ ﻣﻮﺳﺴﻪ ﺑﻴﻦ ﺍﻟﻤﻠﻠﻲ ‪ Profibus‬ﺩﺭ ﺯﻣﻴﻨﻪ ﺷﺒﻜﻪ ﺻﻨﻌﺘﻲ ‪ Profibus‬ﺁﻭﺭﺩﻩ‬
‫ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺍﻳﻦ ﻣﻄﺎﻟﺐ ﺑﺎ ﻧﮕﺎﻫﻲ ﻛﺎﺭﺑﺮﺩﻱ ﻭ ﺑﺪﻭﻥ ﭘﺮﺩﺍﺧﺘﻦ ﺑﻪ ﺑﺤﺚ ﻫﺎﻱ ﺗﺌﻮﺭﻳﻚ ﺷﺒﻜﻪ ﮔﺮﺩ ﺁﻭﺭﻱ ﻭ‬
‫ﻋﺮﺿﻪ ﺷﺪﻩ ﺍﺳﺖ‪.‬ﺑﻤﻨﻈﻮﺭ ﺍﺳﺘﻔﺎﺩﻩ ﺑﻬﻴﻨﻪ ﺍﺯ ﻣﻨﺪﺭﺟﺎﺕ ﺍﻳﻦ ﻛﺘﺎﺏ ﻻﺯﻡ ﺍﺳﺖ ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﺑﺎ ﺩﻭ ﭘﻴﺶ‬
‫ﻧﻴﺎﺯ ﺯﻳﺮ ﺑﻪ ﺍﻧﺪﺍﺯﻩ ﻛﺎﻓﻲ ﺁﺷﻨﺎ ﺑﺎﺷﺪ‪:‬‬
‫‪ .١‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ Step7‬ﺑﻮﻳﮋﻩ ﺍﺯﺟﻨﺒﻪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ‬
‫‪ .٢‬ﻣﻔﺎﻫﻴﻢ ﻭ ﺍﺻﻄﻼﺣﺎﺕ ﻣﻬﻢ ﺷﺒﻜﻪ ﻫﺎﻱ ﺻﻨﻌﺘﻲ‬
‫ﺷﺮﺡ ﻣﻮﺭﺩ ﺍﻭﻝ ﺭﺍ ﺑﺎﻳﺪ ﺩﺭ ﻛﺘﺎﺏ ﻫﺎ ﻭ ﻣﺮﺍﺟﻊ ﺟﺪﺍﮔﺎﻧﻪ ﺍﻱ ﻳﺎﻓﺖ ﻭﻟﻲ ﺩﻭﻣﻴﻦ ﻣﻮﺿﻮﻉ ﺩﺭ ﺣﺪ ﻧﻴﺎﺯ‬
‫ﺩﺭﺍﻧﺘﻬﺎﻱ ﺑﺨﺸﻬﺎﻱ ﺍﺻﻠﻲ ﻛﺘﺎﺏ ﺣﺎﺿﺮ ﺑﻌﻨﻮﺍﻥ ﺿﻤﻴﻤﻪ ﺁﻭﺭﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺗﻮﺻﻴﻪ ﻣﻴﺸﻮﺩ ﻋﺰﻳﺰﺍﻧﻲ ﻛﻪ ﺑﺎ‬
‫ﻣﻘﻮﻟﻪ ﻫﺎﻳﻲ ﻣﺎﻧﻨﺪ ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ ،‬ﺗﻜﻨﻴﻚ ﺩﺳﺘﺮﺳﻲ ‪ ،‬ﻣﺪﻝ ‪ OSI‬ﻭ ﺍﻣﺜﺎﻝ ﺁﻥ ﻛﻤﺘﺮ ﺁﺷﻨﺎ ﻫﺴﺘﻨﺪ ﺍﺑﺘﺪﺍ‬
‫ﺿﻤﻴﻤﻪ ﻣﺰﺑﻮﺭ ﺭﺍ ﻣﻄﺎﻟﻌﻪ ﺑﻔﺮﻣﺎﻳﻨﺪ‪.‬‬
‫ﺍﻣﻴﺪ ﺍﺳﺖ ﻧﺸﺮ ﺍﻳﻦ ﻛﺘﺎﺏ ﻛﻪ ﺑﻪ ﺍﻫﺘﻤﺎﻡ ﺷﺮﻛﺖ ﺻﺎﺑﻜﻮ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺍﺳﺖ ﺑﺘﻮﺍﻧﺪ ﮔﺎﻣﻲ ﺩﺭ ﺟﻬﺖ ﺍﺭﺗﻘﺎﺀ‬
‫ﺩﺍﻧﺶ ﻓﻨﻲ ﻣﺘﺨﺼﺼﻴﻦ ﻋﺮﺻﻪ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺻﻨﻌﺘﻲ ﺑﺮﺩﺍﺭﺩ‪.‬ﺍﺯ ﺩﻳﺪﮔﺎﻫﻬﺎﻱ ﺻﺎﺣﺐ ﻧﻈﺮﺍﻥ ﻛﻪ ﻣﺎ ﺭﺍ ﺍﺯ‬
‫ﻃﺮﻳﻖ ﺗﻤﺎﺱ ﺑﺎ ﭘﺴﺖ ﺍﻟﻜﺘﺮﻭﻧﻴﻜﻲ ‪ reza.maher@gmail.com‬ﻳﺎ ‪ akarimoddini@yahoocom‬ﺳﺮ ﺍﻓﺮﺍﺯ‬
‫ﻧﻤﺎﻳﻨﺪ ﺍﺳﺘﻘﺒﺎﻝ ﻣﻲ ﻛﻨﻴﻢ‪.‬‬

‫ﻣﺆ ﻟﻔﻴﻦ‬
‫ﺷﻬﺮﻳﻮﺭ ‪١٣٨٤‬‬
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﻓﻬﺮﺳﺖ ﻣﻄﺎﻟﺐ‬
‫ﺻﻔﺤﻪ‬

‫ﻓﺼﻞ ﺍﻭﻝ – ﺁﺷﻨﺎﻳﻲ ﺑﺎ ‪Profibus‬‬

‫‪٢‬‬ ‫‪ FIELDBUS ١-١‬ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬

‫‪٦‬‬ ‫‪ PROFIBUS‬ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ‬ ‫‪٢-١‬‬

‫‪٩‬‬ ‫‪PROFIBUS DP‬‬ ‫‪٣-١‬‬

‫‪٩‬‬ ‫‪ PROFIBUS DP ١-٣-١‬ﻭ ﻧﺴﺨﻪ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺁﻥ‬

‫‪١٥‬‬ ‫ﺗﻜﻨﻮﻟﻮﮊﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ‪PROFIBUS DP‬‬ ‫‪٢-٣-١‬‬

‫‪٢٤‬‬ ‫ﺩﺭ ‪PROFIBUS DP‬‬ ‫ﺗﻜﻨﻮﻟﻮﮊﻱ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ‫‪٣-٣-١‬‬

‫‪٣٠‬‬ ‫‪PROFIBUS FMS‬‬ ‫‪٤-١‬‬

‫‪٣١‬‬ ‫‪PROFIBUS PA‬‬ ‫‪٥-١‬‬

‫‪Profibus‬‬ ‫ﻓﺼﻞ ﺩﻭﻡ – ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬

‫‪٤٠‬‬ ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬ ‫‪١-٢‬‬

‫‪٤١‬‬ ‫‪DP Master‬‬ ‫‪١-١-٢‬‬

‫‪٤٣‬‬ ‫‪DP Slave‬‬ ‫‪٢-١-٢‬‬

‫‪٤٧‬‬ ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS FMS‬‬ ‫‪٢-٢‬‬

‫‪٢٥‬‬ ‫‪PROFIBUS‬‬ ‫‪ ٣-٢‬ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬

‫‪٤٨‬‬ ‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ‪RS485‬‬ ‫‪١-٣-٢‬‬

‫‪٥٠‬‬ ‫‪ ٢-٣-٢‬ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫‪٥٤‬‬ ‫‪ ٣-٣-٢‬ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ‬

‫‪PROFIBUS‬‬ ‫ﻓﺼﻞ ﺳﻮﻡ – ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ‬

‫‪٥٦‬‬ ‫‪ ١-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ‬

‫‪٦٠‬‬ ‫‪ ٢-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ‬

‫‪٦٤‬‬ ‫‪ ٣-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ‬

‫‪Techno-Electro.com‬‬

‫‪ PROFIBUS-DP‬ﺩﺭ ‪STEP7‬‬ ‫ﻓﺼﻞ ﭼﻬﺎﺭﻡ – ﭘﻴﻜﺮﺑﻨﺪﻱ ﺷﺒﻜﻪ‬

‫‪٦٩‬‬ ‫ﺑﺨﺶ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻳﻚ ﭘﺮﻭﮊﻩ ‪STEP 7‬‬ ‫‪١-٤‬‬
‫‪٧٠‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٢-٤‬‬
‫‪٨٦‬‬ ‫‪ ٣-٤‬ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ﺷﺒﻜﻪ‬

‫‪٨٨‬‬ ‫‪ ٥-٤‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﭼﻨﺪ ‪ Master System‬ﺑﺼﻮﺭﺕ ﺗﺮﻛﻴﺒﻲ‬

‫‪٨٩‬‬ ‫‪ ٦-٤‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎ‬

‫‪ Intelligent Slaves‬ﺩﺭ ‪STEP7‬‬ ‫ﻓﺼﻞ ﭘﻨﺠﻢ – ﭘﻴﻜﺮﺑﻨﺪﻱ‬

‫‪٩٤‬‬ ‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫‪ ١-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫‪١٠٠‬‬ ‫ﺑﺎ ‪DP Slave‬‬ ‫‪I-Slave‬‬ ‫‪ ٢-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫‪١٠٢‬‬ ‫‪ ٣-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ I-Slave‬ﺑﺎ ‪ DP Slave‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ DP Master‬ﻫﺎﻱ ﻣﺨﺘﻠﻒ‬

‫‪١٠٣‬‬ ‫‪DP Master‬‬ ‫‪ ٤-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ I-Slave‬ﺑﺎ‬

‫ﺷﺸﻢ – ﺳﺎﺧﺘﺎﺭﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ‪STEP7‬‬ ‫ﻓﺼﻞ‬

‫‪١٠٦‬‬ ‫‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫‪ ١-٦‬ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ‬

‫‪١٠٩‬‬ ‫‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫‪ ٢-٦‬ﺳﺎﺧﺘﺎﺭ ﭼﻨﺪ ﺷﺒﻜﻪ‬

‫‪١١٠‬‬ ‫‪ PROFIBUS‬ﺩﺭ ﭼﻨﺪ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫‪ ٣-٦‬ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ‬

‫‪PROFIBUS-DP‬‬ ‫ﻓﺼﻞ ﻫﻔﺘﻢ – ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

‫‪١١٤‬‬ ‫‪Master / Slave‬‬ ‫‪ ١-٧‬ﺳﺮﻭﻳﺲ ‪ DP‬ﺑﺮﺍﻱ‬

‫‪١١٦‬‬ ‫ﺳﺮﻭﻳﺲ ‪ DP‬ﺑﺮﺍﻱ ‪Master / I-Slave‬‬ ‫‪٢-٧‬‬

‫‪PROFIBUS‬‬ ‫ﻓﺼﻞ ﻫﺸﺘﻢ –ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫‪١٢٨‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﻴﻦ ‪ PLC‬ﻫﺎﻱ ‪S7‬‬ ‫‪١-٨‬‬
‫‪١٤٥‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﻴﻦ ‪ PLC‬ﻫﺎﻱ ‪ S7‬ﻭ‪S5‬‬ ‫‪٢-٨‬‬
‫‪١٤٨‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ ‪Multiproject‬‬ ‫‪٣-٨‬‬
‫‪١٤٩‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﺎ ‪Unknown Project‬‬ ‫‪٤-٨‬‬
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﻧﻬﻢ – ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺷﺒﻜﻪ ‪PROFIBUS FMS‬‬

‫‪١٥٢‬‬ ‫ﺷﻨﺎﺧﺖ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١-٩‬‬
‫‪١٥٤‬‬ ‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪٢-٩‬‬
‫‪١٥٨‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪٣-٩‬‬
‫‪١٦٤‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪ ٤-٩‬ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ‬

‫‪PROFIBUS‬‬ ‫ﻓﺼﻞ ﺩﻫﻢ – ﻋﻴﺐ ﻳﺎﺑﻲ ﻭ ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ ﺩﺭ‬

‫‪١٧٧‬‬ ‫‪ ١-١٠‬ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬

‫‪١٨٤‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪Step7‬‬ ‫‪٢-١٠‬‬

‫‪١٨٧‬‬ ‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪Step7‬‬ ‫‪ ٣-١٠‬ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ‬

‫ﺿﻤﻴﻤﻪ ‪ – ١‬ﻣﺮﻭﺭﻱ ﺑﺮ ﻣﻔﺎﻫﻴﻢ ﻭ ﺍﺻﻄﻼﺣﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﺻﻨﻌﺘﻲ‬

‫‪١٩٢‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬
‫‪١٩٦‬‬ ‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬
‫‪٢٠٥‬‬ ‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬
‫‪٢١٠‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ ‪OSI‬‬
‫‪٢٢١‬‬ ‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫‪٢٢٨‬‬ ‫ﺿﻤﻴﻤﻪ ‪ - ٢‬ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺑﺮﺧﻲ ﺍﺯ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

‫‪٢٤٠‬‬ ‫ﺿﻤﻴﻤﻪ ‪ -٣‬ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺷﺒﻜﻪ ‪PROFIBUS‬‬

‫‪٢٤٤‬‬ ‫‪ S7‬ﻭ ‪FMS‬‬ ‫ﺿﻤﻴﻤﻪ ‪ -٤‬ﻣﻘﺎﻳﺴﻪ ﻓﺮﻣﺖ ﺩﻳﺘﺎ ﺩﺭ‬

‫‪٢٤٦‬‬ ‫ﺿﻤﻴﻤﻪ ‪ -٥‬ﻛﺪ ﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫‪٢٥٤‬‬ ‫ﻛﻠﻤﺎﺕ ﺍﺧﺘﺼﺎﺭﻱ‬

‫‪٢٥٨‬‬ ‫ﻣﻨﺎﺑﻊ ﻭ ﻣﺮﺍﺟﻊ‬

Techno-Electro.com
Techno-Electro.com

PROFIBUS ‫ﻓﺼﻞ ﺍﻭﻝ – ﺁﺷﻨﺎﻳﻲ ﺑﺎ‬

: ‫ﻣﺸﺘﻤﻞ ﺑﺮ‬

‫ ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬FIELDBUS ١-١

‫ ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ‬PROFIBUS ٢-١
PROFIBUS DP ٣-١
PROFIBUS FMS ٤-١
PROFIBUS PA ٥-١
‫‪Techno-Electro.com‬‬

‫‪ Fieldbus‬ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬ ‫‪٢‬‬

‫‪ FIELDBUS ١-١‬ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬

‫ﺗﺎﻗﺒﻞ ﺍﺯ ﻗﺮﻥ ﺑﻴﺴﺘﻢ ﻣﻴﻼﺩﻱ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻨﺘﺮﻝ ﻓﺮﺁﻳﻨﺪ ﻣﺒﺘﻨﻲ ﺑﺮ ﺗﻜﻨﻮﻟﻮﮊﻱ ﻣﻜﺎﻧﻴﻜﻲ ﻭ ﻭﺳﺎﻳﻞ ﺁﻧﺎﻟﻮﮒ ﺑﻮﺩﻧﺪ ‪ .‬ﺑﻌﺪ ﺍﺯ‬
‫ﻣﺪﺗﻲ ﺗﻜﻨﻮﻟﻮﮊﻱ ﻛﻨﺘﺮﻝ ﭘﻨﻮﻣﺎﺗﻴﻜﻲ ﻭ ﻫﻴﺪﺭﻭﻟﻴﻜﻲ ﻣﻄﺮﺡ ﮔﺮﺩﻳﺪ ﻛﻪ ﻛﻨﺘﺮﻝ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ‪ Remote‬ﺭﺍ ﺗﻮﺳﻂ ﻛﻨﺘﺮﻝ ﻛﻨﻨﺪﻩ‬
‫ﻣﺮﻛﺰﻱ ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﻣﻴﺴﺎﺧﺖ‪ .‬ﺩﺭ ﺍﻭﺍﻳﻞ ‪ ١٩٦٠‬ﺑﻮﺩ ﻛﻪ ‪ PLC‬ﻫﺎ ﭘﺎ ﺑﻪ ﻋﺮﺻﻪ ﻭﺟﻮﺩ ﮔﺬﺍﺷﺘﻨﺪ ﻭ ﺑﺘﺪﺭﻳﺞ ﺟﺎﻳﮕﺰﻳﻦ ﻣﺪﺍﺭﺍﺕ‬
‫ﺭﻟﻪ ﺍﻱ ﺷﺪﻧﺪ‪ .‬ﺑﺎ ﺗﻮﺳﻌﻪ ‪ PLC‬ﻫﺎ ﺑﺤﺚ ﻛﻨﺘﺮﻝ ﻏﻴﺮﻣﺘﻤﺮﻛﺰ ﻣﻄﺮﺡ ﺷﺪ ﻭ ﺍﻭﻟﻴﻦ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻨﺘﺮﻝ ﻏﻴﺮ ﻣﺘﻤﺮﻛﺰ ﻳﺎ ‪ DCS‬ﻫﺎ ﺩﺭ‬
‫ﺍﻭﺍﺳﻂ ‪ ١٩٧٠‬ﻋﺮﺿﻪ ﺷﺪﻧﺪ‪ .‬ﺩﺭ ﻫﻤﻴﻦ ﺩﻭﺭﺍﻥ ﺷﺒﻜﻪ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﻣﺤﻠﻲ )‪ (LAN‬ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺑﻴﻦ ﻛﺎﻣﭙﻴﻮﺗﺮﻫﺎ ﺭﺍ ﺑﻬﺒﻮﺩ‬
‫ﺑﺨﺸﻴﺪ ﻭ ﺍﻧﺪﻳﺸﻪ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺷﺒﻜﻪ ﺟﻬﺖ ﻣﻘﺎﺻﺪ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺻﻨﻌﺘﻲ ﺷﻜﻞ ﮔﺮﻓﺖ‬
‫هﺰﻳﻨﻪ‬ ‫ﻛﻪ ﺩﺭ ﺩﻫﻪ ‪ ٩٠‬ﺑﺎ ﻋﻨﻮﺍﻥ ‪ Fieldbus‬ﻋﻤﻠﻲ ﺷﺪ‪ .‬ﺷﺒﻜﻪ ﻫﺎﻱ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺻﻨﻌﺘﻲ‬
‫ﺳﻴﺴﺘﻢ‬ ‫ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﺩﺭ ﺳﻄﺢ ﻓﻴﻠﺪ ﻛﻪ ﺑﻪ ‪ Fieldbus‬ﻣﻌﺮﻭﻑ ﺍﺳﺖ ﻣﺰﻳﺘﻬﺎﻱ ﺑﺴﻴﺎﺭﻱ‬
‫ﻣﺘﻤﺮﮐﺰ‬
‫ﺳﻴﺴﺘﻢ‬ ‫ﺭﺍ ﺑﺮﺍﻱ ﺳﻴﺴﺘﻢ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺑﻪ ﺍﺭﻣﻐﺎﻥ ﺁﻭﺭﺩ ﻛﺎﻫﺶ ﺣﺠﻢ ﻭ ﻋﻤﻠﻴﺎﺕ ﻛﺎﺑﻞ‬
‫ﻏﻴﺮ ﻣﺘﻤﺮﮐﺰ‬
‫ﻛﺸﻲ ﺳﻬﻮﻟﺖ ﻧﺼﺐ ﻭ ﻛﺎﻫﺶ ﻫﺰﻳﻨﻪ ﺍﺯ ﺁﻥ ﺟﻤﻠﻪ ﺑﻮﺩ‪.‬ﺍﻳﻦ ﻛﺎﻫﺶ ﻫﺰﻳﻨﻪ‬
‫ﺑﻮﻳﮋﻩ ﻭﻗﺘﻲ ﭼﺸﻤﮕﻴﺮ ﺑﻮﺩ ﻛﻪ ﺳﻴﮕﻨﺎﻟﻬﺎﻱ ‪ Field‬ﺑﺎ ﻛﻨﺘﺮﻝ ﻛﻨﻨﺪﻩ ﻓﺎﺻﻠﻪ‬
‫ﻓﺎﺻﻠﻪ‬
‫ﺯﻳﺎﺩﻱ ﺩﺍﺷﺖ‪ .‬ﻧﻤﻮﺩﺍﺭ ﺷﻜﻞ ﺭﻭﺑﺮﻭ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻛﻪ ﺑﺎ ﺍﻓﺰﺍﻳﺶ ﻓﺎﺻﻠﻪ ﭼﮕﻮﻧﻪ‬
‫ﻫﺰﻳﻨﻪ ﻫﺎﻱ ﻳﻚ ﺳﻴﺴﺘﻢ ﻣﺘﻤﺮﻛﺰ ﺍﻓﺰﺍﻳﺶ ﻣﻲ ﻳﺎﺑﺪ ﻭ ﺍﻳﻦ ﻫﺰﻳﻨﻪ ﺩﺭ ﻣﻘﺎﻳﺴﻪ ﺑﺎ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﻴﺴﺘﻢ ﺗﻮﺯﻳﻊ ﺷﺪﻩ ﭼﮕﻮﻧﻪ ﺍﺳﺖ‪.‬‬

‫ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﻣﺰﺍﻳﺎﻱ ﻣﻬﻢ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ Fieldbus‬ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﺻﻮﺭﺕ ﺯﻳﺮ ﺑﺮ ﺷﻤﺮﺩ‪:‬‬
‫ﻛﺎﻫﺶ ﺳﻴﻢ ﻛﺸﻲ‬ ‫•‬

‫ﻛﺎﻫﺶ ﻣﺤﻮﻃﻪ ﺍﺷﻐﺎﻝ ﺷﻮﻧﺪﻩ ﺟﻬﺖ ﻧﺼﺐ‬ ‫•‬

‫ﻛﻨﺘﺮﻝ ﺻﺤﺖ ﺍﻃﻼﻋﺎﺕ ﻭ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺧﻄﺎ ﺑﺪﻟﻴﻞ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﻴﮕﻨﺎﻝ ﺩﻳﺠﻴﺘﺎﻝ ﺑﺠﺎﻱ ﺁﻧﺎﻟﻮﮒ‬ ‫•‬

‫ﻣﺼﻮﻧﻴﺖ ﺑﻴﺸﺘﺮ ﺩﺭ ﻣﻘﺎﺑﻞ ﻧﻮﻳﺰ‬ ‫•‬

‫ﺗﺴﺖ ﻭ ﻋﻴﺐ ﻳﺎﺑﻲ ﺭﺍﺣﺖ ﺗﺮ ﺑﺪﻟﻴﻞ ﻭﺟﻮﺩ ﺳﻴﺴﺘﻢ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‬ ‫•‬

‫‪ Open‬ﺑﻮﺩﻥ ﺳﻴﺴﺘﻢ ﻭ ﺍﻣﻜﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﺤﺼﻮﻻﺕ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﺘﻠﻒ ﺭﻭﻱ ﻳﻚ ﺷﺒﻜﻪ‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪٣‬‬ ‫‪ Fieldbus‬ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬

‫ﺳﻴﺴﺘﻢ ﻣﺘﻤﺮﮐﺰ‬ ‫ﺳﻴﺴﺘﻢ ﻏﻴﺮ ﻣﺘﻤﺮﮐﺰ‬

‫ﺟﺎﻳﮕﺎﻩ ‪ Fieldbus‬ﺩﺭ ﻫﺮﻡ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ‬

‫ﺑﺮﺍﻱ ﺳﻄﻮﺡ ﻣﺨﺘﻠﻒ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻳﻚ ﺳﺎﺧﺘﺎﺭ ﻫﺮﻣﻲ ﺷﻜﻞ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ ﺗﻌﺮﻳﻒ ﻣﻴﺸﻮﺩ ‪:‬‬
‫‪Field Level‬‬
‫ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﺳﻨﺴﻮﺭﻫﺎ ﻭ ﻋﻤﻠﮕﺮﻫﺎ ﻭ ﻭﺳﺎﻳﻞ ﺍﺑﺰﺍﺭ ﺩﻗﻴﻖ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ‪ .‬ﺣﺠﻢ ﺩﻳﺘﺎ ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﻛﻢ ﺍﺳﺖ ﻭﻟﻲ ﺯﻣﺎﻥ ﺍﺭﺳﺎﻝ ﻳﺎ‬
‫ﺩﺭﻳﺎﻓﺖ ﺍﻃﻼﻋﺎﺕ ﺑﺎﻳﺪ ﻛﻮﺗﺎﻩ ﻭﺩﺭ ﺣﺪ ﻣﻴﻠﻲ ﺛﺎﻧﻴﻪ ﺑﺎﺷﺪ‪.‬‬
‫‪Control Level‬‬
‫ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻛﻨﺘﺮﻟﻲ ﻣﺘﻤﺮﻛﺰ )‪ (PLC‬ﻳﺎ ﻏﻴﺮﻣﺘﻤﺮﻛﺰ )‪ (DCS‬ﻫﺎ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﻧﺪ‪ .‬ﺣﺠﻢ ﺩﻳﺘﺎ ﻧﻴﺰ ﺩﺭ ﺍﻳﻦ ﻧﺎﺣﻴﻪ ﻛﻢ‬
‫ﻭ ﺩﺭ ﺣﺪ ﺑﺎﻳﺖ ﺍﺳﺖ ﻭﺯﻣﺎﻥ ﺗﺒﺎﺩﻝ ﻧﻴﺰ ﺑﺎﻳﺪ ﻛﻮﺗﺎﻩ ﻭ ﻛﻤﺘﺮ ﺍﺯ ﺛﺎﻧﻴﻪ ﺑﺎﺷﺪ‪.‬‬
‫‪Supervisory Level‬‬
‫ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﻣﺎﻧﻴﺘﻮﺭﻳﻨﮓ ﻳﺎ ﺍﺻﻄﻼﺣﹰﺎ ‪ HMI‬ﻫﺎ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﻧﺪ ﻛﻪ ﺍﭘﺮﺍﺗﻮﺭ ﺍﺯ ﻃﺮﻳﻖ ﺁﻧﻬﺎ ﻭﺿﻌﻴﺖ ﭘﺮﻭﺳﻪ ﺭﺍ ﻣﻴﺒﻴﻨﺪ‬
‫ﻭ ﻓﺮﻣﺎﻧﻬﺎﻱ ﻻﺯﻡ ﺭﺍ ﺻﺎﺩﺭ ﻣﻴﻜﻨﺪ ‪ .‬ﺣﺠﻢ ﺍﻃﻼﻋﺎﺕ ﺩﺭ ﺣﺪ ﻣﺘﻮﺳﻂ ﻭ ﺯﻣﺎﻥ ﻧﻴﺰ ﺩﺭ ﺣﺪ ﺛﺎﻧﻴﻪ ﺍﺳﺖ‪.‬‬
‫‪ERP Level‬‬
‫‪Management Level‬‬ ‫ﺳﻄﺢ ‪ Enterprise Resource Planning‬ﻛﻪ ﺑﻪ ﺁﻥ ﺍﺻﻄﻼﺣﺎﺕ ﺩﻳﮕﺮﻱ ﻣﺎﻧﻨﺪ ‪ Factory Level‬ﻭ‬
‫ﻧﻴﺰ ﺍﻃﻼﻕ ﻣﻴﺸﻮﺩ ﺑﺎﻻﺗﺮﻳﻦ ﺳﻄﺢ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻭ ﺩﺭ ﻭﺍﻗﻊ ﺳﻄﺢ ﺍﻃﻼﻋﺎﺕ ﻣﺪﻳﺮﻳﺘﻲ ﺍﺳﺖ ‪ .‬ﺣﺠﻢ ﺍﻃﻼﻋﺎﺕ ﺩﺭ ﺍﻳﻦ‬
‫ﺳﻄﺢ ﺯﻳﺎﺩ ﺍﺳﺖ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺗﻮﻟﻴﺪ ﻭ ﺗﻌﻤﻴﺮﺍﺕ ﻭ ﺍﻣﺜﺎﻝ ﺁﻧﻬﺎ ﻛﻪ ﻣﺮﺑﻮﻁ ﺑﻪ ﻳﻚ ﺷﻴﻔﺖ ﻛﺎﺭﻱ ﻳﺎ ﻳﻚ ﺭﻭﺯ ﻳﺎ ﻳﻚ‬
‫ﻫﻔﺘﻪ ﻳﺎ ﻳﻚ ﻣﺎﻩ ﺍﺳﺖ ﻻﺯﻡ ﺍﺳﺖ ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﺗﺒﺎﺩﻝ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪ Fieldbus‬ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬ ‫‪٤‬‬

‫ﺑﺎﻳﺪ ﺩﻗﺖ ﻛﺮﺩ ﺩﺭ ﺳﻄﻮﺡ ﭘﺎﻳﻴﻦ ﺍﮔﺮ ﭼﻪ ﺣﺠﻢ ﺩﻳﺘﺎ ﺍﻧﺪﻙ ﺍﺳﺖ ﻭﻟﻲ ﺯﻣﺎﻥ ﺩﺭﻳﺎﻓﺖ ﻳﺎ ﺍﺭﺳﺎﻝ ﺁﻥ ﺑﺴﻴﺎﺭ ﺣﺴﺎﺱ ﺍﺳﺖ ﺍﺯ ﺍﻳﻨﺮﻭ‬
‫ﺑﺮﺍﻱ ﺍﻳﻦ ﺳﻄﻮﺡ ﺍﺻﻄﻼﺡ ﺣﺴﺎﺱ ﺑﻪ ﺯﻣﺎﻥ ﻳﺎ ‪ Real Time‬ﺑﻜﺎﺭ ﺑﺮﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺮﺍﻱ ﻳﻚ ﻣﺪﻳﺮ ﺩﺭ‬
‫ﺳﻄﺢ ‪ ERP‬ﺗﺎﺧﻴﺮ ﭼﻨﺪ ﺩﻗﻴﻘﻪ ﺍﻱ ﺑﺮﺍﻱ ﮔﺮﻓﺘﻦ ﺍﻃﻼﻋﺎﺕ ﻣﻮﺭﺩ ﻧﻈﺮ ﻗﺎﺑﻞ ﺍﻏﻤﺎﺽ ﺑﺎﺷﺪ ﻭﻟﻲ ﺩﺭ ﺳﻄﺢ ﻛﻨﺘﺮﻝ ﻛﻮﭼﻜﺘﺮﻳﻦ‬
‫ﺗﺎﺧﻴﺮ ﺯﻣﺎﻧﻲ ﺩﺭ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺍﺯ ﻛﻨﺘﺮﻝ ﻛﻨﻨﺪﻩ ﻣﻤﻜﻦ ﺍﺳﺖ ﻣﻨﺠﺮ ﺑﻪ ﺍﻳﺠﺎﺩ ﺧﺴﺎﺭﺕ ﻭ ﺗﻮﻗﻒ ﻓﺮﺁﻳﻨﺪ ﺷﻮﺩ‪.‬‬

‫ﻭﻗﺘﻲ ﺻﺤﺒﺖ ﺍﺯ ﺟﺎﻳﮕﺎﻩ ‪ Fieldbus‬ﺩﺭ ﻫﺮﻡ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻣﻴﺸﻮﺩ ﺑﻴﺶ ﺍﺯﻫﻤﻪ ﺫﻫﻦ ﺑﻪ ﺳﻄﺢ ‪ Field‬ﻣﻌﻄﻮﻑ ﻣﻴﺸﻮﺩ ﻳﻌﻨﻲ‬
‫ﺷﺒﻜﻪ ﻛﺮﺩﻥ ﺳﻨﺴﻮﺭﻫﺎ ﻭ ﻋﻤﻠﮕﺮ ﻫﺎ ‪ .‬ﺍﻳﻦ ﺫﻫﻨﻴﺖ ﺍﮔﺮ ﭼﻪ ﺩﺭﺳﺖ ﺍﺳﺖ ﻭﻟﻲ ﺩﺭ ﻋﻤﻞ ﭘﺮﻭﺗﻜﻞ ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﻛﻪ ﺗﺤﺖ ﻋﻨﻮﺍﻥ‬
‫‪ Fieldbus‬ﻋﺮﺿﻪ ﺷﺪﻩ ﺍﻧﺪ ﺑﻌﻀﹰﺎ ﭘﺎ ﺭﺍ ﻓﺮﺍﺗﺮ ﮔﺬﺍﺷﺘﻪ ﻭ ﺩﺭ ﺳﻄﺢ ﻛﻨﺘﺮﻝ ﻧﻴﺰ ﻛﺎﺭﺑﺮﺩ ﭘﻴﺪﺍ ﻛﺮﺩﻩ ﺍﻧﺪ ﻛﻪ ‪ Profibus‬ﻧﻴﺰ ﻳﻜﻲ ﺍﺯ‬
‫ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﺍﺳﺖ ‪ .‬ﺍﺯ ﭘﺮﻭﺗﻜﻞ ﻫﺎﻱ ﻣﺸﻬﻮﺭ ﺩﺭ ﺯﻣﻴﻨﻪ ‪ Fieldbus‬ﻣﻴﺘﻮﺍﻥ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺭﺍ ﻧﺎﻡ ﺑﺮﺩ ‪:‬‬
‫•‬ ‫‪LON‬‬ ‫•‬ ‫‪ASI‬‬
‫•‬ ‫‪SDS‬‬ ‫•‬ ‫‪CAN‬‬
‫•‬ ‫‪ControlNet‬‬ ‫•‬ ‫‪EIB‬‬
‫•‬ ‫‪DeviceNet‬‬ ‫•‬ ‫‪FOUNDATION FIELDBUS‬‬
‫•‬ ‫‪Ethernet‬‬ ‫•‬ ‫‪HART‬‬
‫•‬ ‫‪Interbus‬‬ ‫•‬ ‫‪PROFIBUS‬‬
‫•‬ ‫‪WORLD FIP‬‬

‫ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ ﺣﻮﺯﻩ ﻛﺎﺭﺑﺮﻱ ﺑﺮﺧﻲ ﺍﺯ ﺷﺒﻜﻪ ﻫﺎﻱ ﺻﻨﻌﺘﻲ ﺭﺍ ﺩﺭ ﻫﺮﻡ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪ .‬ﺑﺮﺍﻱ ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻘﺘﺮ‬
‫ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﻣﻴﺘﻮﺍﻧﺪ ﻣﻘﺎﻳﺴﻪ ﺑﻴﻦ ﻣﺸﺨﺼﺎﺕ ﻣﻬﻢ ﺑﺮﺧﻲ ﺍﺯ ﺷﺒﻜﻪ ﻫﺎﻱ ﻣﻌﺮﻭﻑ ﻓﻴﻠﺪﺑﺎﺱ ﺭﺍ ﺩﺭ ﺿﻤﻴﻤﻪ ‪ ٢‬ﻣﺸﺎﻫﺪﻩ ﻧﻤﺎﻳﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٥‬‬ ‫‪ Fieldbus‬ﻭ ﺗﺎﺭﻳﺨﭽﻪ ﺁﻥ‬

‫ﻣﻘﺎﻳﺴﻪ ﺷﺒﮑﻪ هﺎى ﻣﺨﺘﻠﻒ ‪ Fieldbus‬از‬

‫ﻧﻈﺮ ﻣﺤﺪوده ﮐﺎرﺑﺮى در هﺮم اﺗﻮﻣﺎﺳﻴﻮن‬
‫‪Techno-Electro.com‬‬

‫‪ PROFIBUS‬ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ‬ ‫‪٦‬‬

‫‪ PROFIBUS ٢-١‬ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ‬
‫ﺗﺎﺭﻳﺨﭽﻪ ‪ PROFIBUS‬ﻛﻪ ﺑﺮ ﮔﺮﻓﺘﻪ ﺍﺯ ﻛﻠﻤﻪ ‪ Process Fieldbus‬ﺍﺳﺖ ﺑﻪ ﺳﺎﻝ ‪ ١٩٨٧‬ﺑﺮﻣﻴﮕﺮﺩﺩ‪ .‬ﺩﺭ ﺁﻥ ﺯﻣﺎﻥ‬
‫ﺑﻴﺶ ﺍﺯ ‪ ٢٠‬ﻛﻤﭙﺎﻧﻲ ﻭ ﻣﻮﺳﺴﻪ ﺁﻟﻤﺎﻧﻲ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﭘﺮﻭﮊﻩ ﺍﻱ ﺭﺍ ﺗﺤﺖ ﻋﻨﻮﺍﻥ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺳﺎﺯﻱ ﺷﺒﻜﻪ ﺩﺭ ﺳﻄﺢ ﻓﻴﻠﺪ‬
‫ﺷﺮﻭﻉ ﻛﺮﺩﻧﺪ‪ .‬ﻛﻤﭙﺎﻧﻲ ﺯﻳﻤﻨﺲ ﻧﻴﺰ ﺩﺭ ﺑﻴﻦ ﺁﻧﺎﻥ ﺑﻮﺩ‪.‬ﻫﺪﻑ ﭘﺮﻭﮊﻩ ﺍﻳﺠﺎﺩ ﻳﻚ ﺷﺒﻜﻪ ﺑﺎﺯ )‪ (Open‬ﺑﻮﺩ ﻛﻪ ﺑﺘﻮﺍﻧﺪﺳﻴﺴﺘﻢ‬
‫‪PROFIBUS FMS‬‬ ‫ﻫﺎﻱ ﻛﻨﺘﺮﻝ ﻣﻮﺟﻮﺩ ﻣﺎﻧﻨﺪ ‪ PLC‬ﻭ ‪ DCS‬ﺭﺍ ﭘﻮﺷﺶ ﺩﻫﺪ‪ .‬ﭘﺲ ﺍﺯ ‪ ٣‬ﺳﺎﻝ ﺗﻼﺵ ﺩﺭ ﺳﺎﻝ ‪١٩٩٠‬‬
‫ﺍﺭﺍﺋﻪ ﮔﺮﺩﻳﺪﻛﻪ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻃﺎﺕ ﭘﻴﭽﻴﺪﻩ ﻛﻨﺘﺮﻟﻲ ﺑﻜﺎﺭ ﻣﻴﺮﻓﺖ ﻭ ﻫﻨﻮﺯ ﻧﻴﺰ ﻛﺎﻣﻼ ﻛﻨﺎﺭ ﮔﺬﺍﺷﺘﻪ ﻧﺸﺪﻩ ﺍﺳﺖ‪.‬ﺳﭙﺲ ﺩﺭ ﺳﺎﻝ‬
‫‪DP-V2 , DP-V1 , DP-V0‬‬ ‫‪ PROFIBUS DP ١٩٩٣‬ﻃﺮﺍﺣﻲ ﺷﺪ ﻛﻪ ﺗﺎ ﺍﻣﺮﻭﺯ ‪ ٣‬ﻧﺴﺨﻪ ﺍﺯ ﺁﻥ ﺗﺤﺖ ﻋﻨﻮﺍﻥ‬
‫ﻋﺮﺿﻪ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﻋﻼﻭﻩ ﺑﺮ ﺍﻳﻦ ﺩﻭ ﺑﻤﻨﻈﻮﺭ ﭘﻮﺷﺶ ﺩﺍﺩﻥ ﻧﻴﺎﺯﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻣﺤﻴﻂ ﻫﺎﻱ ﺧﻄﺮﻧﺎﻙ ﻭ ﺍﻧﻔﺠﺎﺭﻱ ﺩﺭ ﺳﺎﻝ‬
‫‪ PROFIBUS PA ١٩٩٥‬ﭘﺎ ﺑﻪ ﻋﺮﺻﻪ ﻭﺟﻮﺩ ﮔﺬﺍﺷﺖ‪.‬‬
‫‪ PROFIBUS‬ﺍﮔﺮﭼﻪ ﺍﺑﺘﺪﺍ ﺩﺭ ﺁﻟﻤﺎﻥ ﻣﻄﺮﺡ ﺷﺪ ﻭﻟﻲ ﺑﺴﺮﻋﺖ ﺗﻮﺳﻌﻪ ﭘﻴﺪﺍ ﻛﺮﺩ ﻭ ﺟﺎﻳﮕﺎﻫﻲ ﺑﻴﻦ ﺍﻟﻤﻠﻠﻲ ﺑﺨﻮﺩ‬
‫ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩ ﻭ ﺳﺎﺯﻣﺎﻧﻲ ﺑﺎﻋﻨﻮﺍﻥ ‪ Profibus Neutzer Organization‬ﻳﺎ ‪ PNO‬ﺍﻳﺠﺎﺩ ﺷﺪ ﻛﻪ ﺑﻌﺪﺍ ﺯﻳﺮ ﻧﻈﺮ‬
‫ﻣﻮﺳﺴﻪ ﺑﻴﻦ ﺍﻟﻤﻠﻠﻲ ‪ ) PROFIBUS International‬ﺑﺎ ﻧﺎﻡ ﺍﺧﺘﺼﺎﺭﻱ ‪ ( PI‬ﻗﺮﺍﺭ ﮔﺮﻓﺖ ‪ PI‬ﺩﺭ ﺳﺎﻝ ‪ ١٩٩٥‬ﺗﺸﻜﻴﻞ‬
‫ﮔﺮﺩﻳﺪ ﻭ ﺍﻣﺮﻭﺯﻩ ﺑﻴﺶ ﺍﺯ ‪ 1100‬ﺷﺮﻛﺖ ﻣﻌﺘﺒﺮ ﻋﻀﻮ ﺁﻥ ﻫﺴﺘﻨﺪ ‪ .‬ﻫﺪﻑ ﺍﺻﻠﻲ ‪ PI‬ﺗﻮﺳﻌﻪ ﻭ ﺑﻬﺒﻮﺩ ﺗﻜﻨﻮﻟﻮﮊﻱ‬
‫‪ PROFIBUS‬ﺑﺮﺍﻱ ﻣﻘﺒﻮﻟﻴﺖ ﺟﻬﺎﻧﻲ ﺍﺳﺖ‪.‬‬
‫ﺷﻜﻞ ﺯﻳﺮ ﺟﺎﻳﮕﺎﻩ ‪ PROFIBUS‬ﺭﺍ ﺩﺭ ﻫﺮﻡ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻼﺣﻈﻪ ﻣﻴﺸﻮﺩ ﮔﺴﺘﺮﺩﮔﻲ ﺁﻥ ﺍﺯ‬
‫‪PROFIBUS FMS‬‬ ‫‪ Supervisory‬ﺍﮔﺮ ﭼﻪ ﻣﻴﺘﻮﺍﻥ ﺍﺯ‬ ‫ﺳﻄﺢ ﻓﻴﻠﺪ ﺗﺎ ﺳﻄﺢ ﻛﻨﺘﺮﻝ ﻣﻴﺒﺎﺷﺪ‪ .‬ﺩﺭ ﺳﻄﺢ ﺑﺎﻻﺗﺮ ﻳﻌﻨﻲ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻭﻟﻲ ﺍﻣﺮﻭﺯﻩ ‪ Ethernet‬ﺻﻨﻌﺘﻲ ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﻋﻤﻼ ﺟﺎﻳﮕﺰﻳﻦ ‪ PROFIBUS‬ﺷﺪﻩ ﻭ ﺑﻨﺪﺭﺕ ﺍﺯ ﺁﻥ ﺩﺭ‬
‫ﺳﻄﻮﺡ ﺑﺎﻻﺗﺮ ﺍﺯ ﺳﻄﺢ ﻛﻨﺘﺮﻝ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﮕﺮﺩﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٧‬‬ ‫‪ PROFIBUS‬ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ‬

‫ﻣﻴﺰان ﮐﺎهﺶ هﺰﻳﻨﻪ هﺎ‬

‫‪ PROFIBUS‬ﻣﺰﺍﻳﺎﻳـﻲ ﻛﻪ ﺑﺮﺍﻱ ﺧﺎﻧﻮﺍﺩﻩ ‪ FIELDBUS‬ﺫﻛﺮ ﻣﻴﺸﻮﺩ ﺭﺍ ﺑﺎ ﺧﻮﺩ ﺩﺍﺭﺩ ﺑﺎ ﺍﻳﻦ ﻭﺟﻮﺩ ﺫﻛﺮ ﻭﻳﮋﮔﻴﻬﺎﻳﻲ‬
‫ﻛﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﻌﻀﹲﺎ ﺧﺎﺹ ‪ PROFIBUS‬ﺑﺎﺷﺪ ﺧﺎﻟﻲ ﺍﺯ ﻓﺎﻳﺪﻩ ﻧﻴﺴﺖ ‪:‬‬
‫‪Twisted Pair‬‬ ‫ﻧﻮﻳﺰ ﭘﺬﻳﺮﻱ ﻛﻢ ﺑﻌﻠﺖ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻭﺳﺎﻳﻂ ﺍﻧﺘﻘﺎﻝ ﻣﻨﺎﺳﺐ ﻣﺎﻧﻨﺪ ﻛﺎﺑﻞ‬ ‫•‬

‫‪RS485‬‬ ‫ﭘﻬﻨﺎﻱ ﺑﺎﻧﺪ ﻭﺳﻴﻊ ﺑﻌﻠﺖ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺭﻭﺵ ﺍﻧﺘﻘﺎﻝ ﻣﻨﺎﺳﺐ ﻣﺎﻧﻨﺪ‬ ‫•‬

‫‪Token Pass‬‬ ‫ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎﻱ ﻣﻄﻤﺌﻦ ﻭ ﺑﺪﻭﻥ ﺗﺪﺍﺧﻞ ﺑﻌﻠﺖ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺭﻭﺵ ﺩﺳﺘﺮﺳﻲ‬ ‫•‬

‫ﻛﺎﻫﺶ ﻫﺰﻳﻨﻪ ﻫﺎﻱ ﻧﺼﺐ ﻭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺑﻌﻠﺖ ﺣﺬﻑ ﻛﺎﺑﻞ ﻛﺸﻲ ﻫﺎﻱ ﻣﻮﺍﺯﻱ‬ ‫•‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺳﺮﻳﻊ ﺑﻌﻠﺖ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﻴﺴﺘﻢ ﻫﺎﻱ ﺗﻮﺯﻳﻊ ﺷﺪﻩ‬ ‫•‬

‫ﺍﻧﻌﻄﺎﻑ ﭘﺬﻳﺮﻱ ﺯﻳﺎﺩ ﺟﻬﺖ ﺗﻮﺳﻌﻪ ﺳﻴﺴﺘﻢ ﺑﻌﻠﺖ ‪ Open‬ﺑﻮﺩﻥ ﻭ ﻋﺪﻡ ﺍﻧﺤﺼﺎﺭ ﺑﻪ ﺳﺎﺯﻧﺪﻩ ﺧﺎﺹ‬ ‫•‬

‫ﻣـﺰﺍﻳﺎﻱ ﻓﻮﻕ ﻣﻮﺟﺐ ﺍﺳﺘﻘﺒﺎﻝ ﺍﺯ ﺑﻪ ﻛﺎﺭ ﮔﻴﺮﻱ ‪ PROFIBUS‬ﺩﺭ ﺷﺒﻜﻪ ﻫﺎﻱ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺻﻨﻌﺘﻲ ﺩﺭ ﺳﻄﺢ ﺟﻬﺎﻥ ﺷﺪﻩ‬
‫ﺍﺳﺖ ‪ .‬ﺑﺮﺧﻲ ﺁﻣﺎﺭﻫﺎ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﺳﻄﺢ ﺍﻳﻦ ﺍﺳﺘﻘﺒﺎﻝ ﺍﺳﺖ ﻣﺎﻧﻨﺪ ﺟﺪﻭﻝ ﺯﻳﺮ‪:‬‬

‫‪Bus‬‬ ‫*‪User‬‬ ‫‪Application‬‬ ‫‪Sponsor‬‬

‫‪CANs‬‬ ‫‪25%‬‬ ‫‪Automotive, Process control‬‬ ‫‪OVDA, Honeywell‬‬
‫)‪PROFIBUS (3 kinds‬‬ ‫‪26%‬‬ ‫‪Process control‬‬ ‫‪Siemens, ABB‬‬
‫‪LON‬‬ ‫‪6%‬‬ ‫‪Building systems‬‬ ‫‪Echelon, ABB‬‬
‫‪Ethernet‬‬ ‫‪50%‬‬ ‫‪Plant bus‬‬ ‫‪all‬‬
‫‪Interbus-S‬‬ ‫‪7%‬‬ ‫‪Manufacturing‬‬ ‫‪Phoenix Contact‬‬
‫‪Fieldbus Foundation, HART‬‬ ‫‪7%‬‬ ‫‪Chemical Industry‬‬ ‫‪Fisher-Rosemount, ABB‬‬
‫‪ASI‬‬ ‫‪9%‬‬ ‫‪Building Systems‬‬ ‫‪Siemens‬‬
‫‪Modbus‬‬ ‫‪22%‬‬ ‫‪obsolete point-to-point‬‬ ‫‪many‬‬
‫‪ControlNet‬‬ ‫‪14%‬‬ ‫‪plant bus‬‬ ‫‪Rockwell‬‬
‫‪*source: ISA, Jim Pinto‬‬
‫‪Sum > 100%, since firms support more than one bus‬‬
‫)‪(1999‬‬
‫‪Techno-Electro.com‬‬

‫‪ PROFIBUS‬ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ‬ ‫‪٨‬‬

‫ﭘﺮﻭﺗﻜﻞ ‪ PROFIBUS‬ﻭ ﺍﻧﻮﺍﻉ ﺁﻥ‬

‫ﭘﺮﻭﺗﻜﻞ ‪ PROFIBUS‬ﺩﺭ ﻻﻳﻪ ﻫﺎﻱ ﺧﻮﺩ ﺍﺯ ﻣﺪﻝ ‪ ISO / OSI‬ﭘﻴﺮﻭﻱ ﻣﻴﻜﻨﺪ ﻭﻟﻲ ﺗﻤﺎﻡ ﻻﻳﻪ ﻫﺎ ﺭﺍ ﺑﻪ ﻛﺎﺭ ﻧﻤﻲ ﮔﻴﺮﺩ‬
‫ﺷﻜﻞ ﺯﻳﺮ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻛﻪ ﻻﻳﻪ ﻫﺎﻱ ‪ ۱‬ﻭ ‪ ۲‬ﻭ ﺩﺭ ﺻﻮﺭﺕ ﻟﺰﻭﻡ ﻻﻳﻪ ﻫﻔﺘﻢ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﻧﺪ‪.‬‬

‫‪ PROFIBUS‬ﺩﺭ ﺍﻳﻦ ﻻﻳﻪ ﻫﺎ ﺍﺯ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻫﺎﻱ ﺯﻳﺮ ﭘﻴﺮﻭﻱ ﻣﻴﻜﻨﺪ‪:‬‬

‫•‬ ‫‪EIA RS-485‬‬
‫•‬ ‫‪IEC 870-5-1‬‬
‫•‬ ‫‪EN60 870-5-1‬‬
‫•‬ ‫‪DIN 19245‬‬
‫•‬ ‫‪IEC 955‬‬
‫•‬ ‫‪ISO DIS 7498-4‬‬
‫‪ PROFIBUS‬ﺑﻪ ﺳﻪ ﺩﺳﺘﻪ ‪ DP‬ﻭ ‪ FMS‬ﻭ ‪ PA‬ﺗﻘﺴﻴﻢ ﻣﻴﮕﺮﺩﺩ ﻛﻪ ﻫﺮﻳﻚ ﻭﻳﮋﮔﻲ ﻫﺎﻱ‬ ‫ﺍﺯ ﻧﻈﺮ ﻛﺎﺭﺑﺮﺩﻱ ﭘﺮﻭﺗﻜﻞ‬
‫ﺧﺎﺹ ﺧﻮﺩ ﺭﺍ ﺩﺍﺭﻧﺪ ﻭﺩﺭ ﺻﻔﺤﺎﺕ ﺁﻳﻨﺪﻩ ﺑﻪ ﺗﻔﺼﻴﻞ ﺷﺮﺡ ﺩﺍﺩﻩ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪ .‬ﺗﻮﺳﻌﻪ ﺍﻧﻮﺍﻉ ‪ PROFIBUS‬ﺩﺭ ﺷﻜﻞ‬
‫ﺯﻳﺮ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٩‬‬ ‫‪PROFIBUS DP‬‬

‫‪PROFIBUS DP‬‬ ‫‪٣-١‬‬

‫‪ PROFIBUS DP ١- ٣-١‬ﻭ ﻧﺴﺨﻪ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺁﻥ‬
‫‪ PROFIBUS DP‬ﺍﺯ ﻻﻳﻪ ﻫﺎﻱ ‪١‬ﻭ‪٢‬ﻭ ﻫﻤﭽﻨﻴﻦ ﺍﺯ ﻳﻚ ‪ User Interface‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﺪ‪ ،‬ﺩﺭ ﺍﻳﻦ ﭘﺮﻭﺗﻜﻞ ﻻﻳﻪ ﻫﺎﻱ‬
‫‪ ٣‬ﺗﺎ ‪ ٧‬ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﻲ ﺷﻮﻧﺪ ‪.‬ﺍﻳﻦ ﺳﺎﺧﺘﺎﺭ ﺳﺎﺩﻩ ‪،‬ﺍﻧﺘﻘﺎﻝ ﺳﺮﻳﻊ ﺩﻳﺘﺎ ﺭﺍ ﻣﻴﺴﺮ ﻣﻲ ﺳﺎﺯﺩ ﺳﺮﻭﻳﺲ ‪ DDLM‬ﻛﻪ ﻣﺨﻔﻒ ﻛﻠﻤﻪ‬
‫‪ Direct Data Link Mapper‬ﺍﺳﺖ ﺍﻣﻜﺎﻥ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﻻﻳﻪ ﺩﻭﻡ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻴﻜﻨﺪ‪ .‬ﺗﻮﺍﺑﻌﻲ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺑﻪ ﻛﺎﺭ ﻣﻲ‬
‫ﺭﻭﻧﺪ ﻭ ﻣﺸﺨﺼﺎﺕ ﺳﻴﺴﺘﻢ ‪ PROFIBUS DP‬ﻭﺗﺠﻬﻴﺰﺍﺕ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﺩﺭ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻒ ‪ DP‬ﺩﺭ ﺑﺨﺶ ﻫﺎﻱ ﺑﻌﺪﻱ‬
‫ﺑﺤﺚ ﻭﺑﺮﺭﺳﻲ ﻣﻲ ﺷﻮﻧﺪ‪.‬‬

‫‪USER‬‬ ‫‪cyclic‬‬ ‫‪acyclic services‬‬

‫‪interface‬‬ ‫‪exchanged‬‬ ‫‪- control‬‬ ‫‪- alarm function‬‬
‫‪data and‬‬ ‫‪- diagnostic‬‬ ‫‪- upload‬‬
‫‪status‬‬ ‫‪- parameterizion‬‬ ‫‪- download‬‬
‫‪messages‬‬
‫‪cyclic and acyclic communication services‬‬
‫‪DDLM‬‬

‫‪OSI‬‬ ‫)‪Fieldbus Data Link (FDL‬‬

‫‪layer 2‬‬ ‫)‪Fieldbus Management (FMA‬‬
‫ﺳﺮﻋﺖ ﺁﻥ‬ ‫ﻣﺰﻳﺖ ﺑﺰﺭﮒ‪ DP‬ﻧﺴﺒﺖ ﺑﻪ ‪ FMS‬ﺁﻧﺴﺖ ﻛﻪ ﻻﻳﻪ ﺑﺎﻻﺳﺮﻱ ﻳﻌﻨﻲ ﻻﻳﻪ ﻫﻔﺘﻢ ﺩﺭ ﺁﻥ ﺣﺬﻑ ﺷﺪﻩ ﻭ ﺍﻳﻨﻜﺎﺭ‬
‫ﺭﺍ ﺑﻬﻴﻨﻪ ﻛﺮﺩﻩ ﺍﺳﺖ‪ DP .‬ﺑﺼﻮﺭﺕ ‪ Master/Slave‬ﻛﺎﺭ ﻣﻴﻜﻨﺪ ﻳﻌﻨﻲ ﻛﻨﺘﺮﻟﺮ ﻣﺮﻛﺰﻱ ﻳﺎ ‪ Master‬ﺑﺼﻮﺭﺕ ﺳﻴﻜﻠﻲ‬
‫ﻭﺭﻭﺩﻱ ﻫﺎ ﺭﺍ ﺍﺯ ‪ Slave‬ﻫﺎ ﻣﻴﺨﻮﺍﻧﺪ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎ ﺭﺍ ﺑﻪ ﺁﻧﻬﺎ ﻣﻴﻔﺮﺳﺘﺪ‪ .‬ﺑﻪ ﺩﻭﺭﻩ ﺯﻣﺎﻧﻲ ﻛﻪ ﺩﺭ ﺁﻥ ﺍﻳﻦ ﻋﻤﻠﻴﺎﺕ ﺍﻧﺠﺎﻡ‬
‫‪Scan‬‬ ‫ﻣﻴﺸﻮﺩ ﺳﻴﻜﻞ ﺑﺎﺱ )‪ (Bus Cycle‬ﮔﻔﺘﻪ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻳﻦ ﺳﻴﻜﻞ ﺑﺎﻳﺪ ﺍﺯ ﺯﻣﺎﻥ ﺳﻴﻜﻞ ﺑﺮﻧﺎﻣﻪ ﻛﻨﺘﺮﻟﺮ ﻣﺮﻛﺰﻱ ﻳﻌﻨﻲ‬
‫‪ Cycle‬ﻛﻮﺗﺎﻫﺘﺮ ﺑﺎﺷﺪﺗﺎ ﺧﻠﻠﻲ ﺩﺭ ﻛﺎﺭ ﻛﻨﺘﺮﻟﺮ ﭘﻴﺶ ﻧﻴﺎﻳﺪ‪ .‬ﺳﺮﻋﺖ ‪ DP‬ﺑﮕﻮﻧﻪ ﺍﻱ ﺍﺳﺖ ﻛﻪ ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ﻋﺮﺽ ﻳﻚ‬
‫ﻣﻴﻠﻲ ﺛﺎﻧﻴﻪ ‪ ٥١٢‬ﺑﺎﻳﺖ ﺩﻳﺘﺎﻱ ﻭﺭﻭﺩﻱ ﻭ ‪ ٥١٢‬ﺑﺎﻳﺖ ﺩﻳﺘﺎﻱ ﺧﺮﻭﺟﻲ ﺭﺍ ﺭﻭﻱ ‪ Slave ٣٢‬ﺑﺎ ﺳﺮﻋﺖ ‪ 12 Mbps‬ﺗﺒﺎﺩﻝ‬
‫ﻛﻨﺪ‪.‬ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺑﻪ ﺗﻌﺪﺍﺩ ﺍﻳﺴﺘﮕﺎﻩ ﻭ ﺳﻴﻜﻞ ﺑﺎﺱ ﺍﺭﺗﺒﺎﻁ ﺩﺍﺭﺩ ‪ .‬ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ ﻭﺍﺑﺴﺘﮕﻲ ﺍﻳﻦ ﺳﻪ ﭘﺎﺭﺍﻣﺘﺮ ﺭﺍ ﺑﻪ‬
‫ﻳﻜﺪﻳﮕﺮ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪١٠‬‬

‫‪ DP-V1‬ﻭ ‪DP-V2‬‬ ‫ﺗﺎﻛﻨﻮﻥ ﺳﻪ ﻧﺴﺨﻪ ﺍﺯ ‪ PROFIBUS DP‬ﻋﺮﺿﻪ ﺷﺪﻩ ﺍﺳﺖ ‪ DP-V0‬ﻭ‬

‫‪DP-V0‬‬
‫‪Master‬‬ ‫‪ DP-V0‬ﻧﺴﺨﻪ ﭘﺎﻳﻪ ﺍﺳﺖ ﻭ ﻓﻘﻂ ﺍﺟﺎﺯﻩ ﺍﺭﺗﺒﺎﻁ ﺳﻴﻜﻠﻲ ﺑﻴﻦ ‪ Master‬ﻭ ‪ Slave‬ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻴﺴﺎﺯﺩ‪ .‬ﻳﻌﻨﻲ‬
‫ﺑﺼﻮﺭﺕ ﺳﻴﻜﻠﻲ ﻣﺮﺗﺒﺎ ‪ Slave‬ﻫﺎ ﺭﺍ ﻳﻜﻲ ﭘﺲ ﺍﺯ ﺩﻳﮕﺮﻱ ﻓﺮﺍ ﻣﻴﺨﻮﺍﻧﺪ ﻭ ﺑﺎ ﺁﻧﻬﺎ ﺑﻪ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﻣﻲ ﭘﺮﺩﺍﺯﺩ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ‬
‫ﻣﻴﺪﺍﻧﻴﻢ ‪ PROFIBUS DP‬ﻛﻪ ﺍﺯ ﺍﻳﻦ ﺑﻪ ﺑﻌﺪ ﻣﻤﻜﻦ ﺍﺳﺖ ﻣﺎ ﺍﺯ ﺁﻥ ﺑﻪ ﺍﺧﺘﺼﺎﺭ ﺑﺎ ‪ DP‬ﻳﺎﺩ ﻛﻨﻴﻢ ﭘﺮﻭﺗﻜﻞ ﭘﺮ ﺳﺮﻋﺘﻲ‬
‫‪Master‬‬ ‫ﺍﺳﺖ ﻛﻪ ﺑﻮﻳﮋﻩ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ‪ Master/Slave‬ﺑﻬﻴﻨﻪ ﺳﺎﺯﻱ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻦ ﺳﺎﺧﺘﺎﺭ ﻣﻤﻜﻦ ﺍﺳﺖ ﻓﻘﻂ ﻳﻚ‬
‫ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﻛﻪ ﺑﻪ ﺁﻥ ﺳﻴﺴﺘﻢ ‪ Mono Master‬ﻣﻴﮕﻮﻳﻨﺪ ﻭ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ‪ Master‬ﺑﻄﻮﺭ ﻧﺎﻣﺤﺪﻭﺩ ﺑﺎﺱ ﺭﺍ ﺩﺭ‬
‫ﺍﺧﺘﻴﺎﺭ ﻣﻴﮕﻴﺮﺩ‪ .‬ﺣﺎﻝ ﺍﮔﺮ ﺑﻴﺶ ﺍﺯ ﻳﻚ ‪ Master‬ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ )‪ (Multimaster‬ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ‪ Master‬ﻫﺎ ﺑﻪ‬
‫ﻧﻮﺑﺖ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻣﻴﮕﻴﺮﻧﺪ ‪ .‬ﺩﺭ ﻫﺮ ﺩﻭ ﺣﺎﻟﺖ ﻓﻮﻕ ﻫﺮ ‪ Master‬ﻭﻗﺘﻲ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺩﺍﺭﺩ ﺑﻄﻮﺭ ﺳﻴﻜﻠﻲ ﻭ‬
‫ﺑﺘﺮﺗﻴﺐ ﺑﺎ ‪ Slave‬ﻫﺎﻳﺶ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ‪.‬‬

‫ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﻭﻗﺘﻲ ﻳﻚ ‪ Master‬ﻣﻴﺨﻮﺍﻫﺪ ﺑﺎ ‪ Slave‬ﺻﺤﺒﺖ ﻛﻨﺪ ﺍﺑﺘﺪﺍ ﻣﺮﺍﺣﻞ ﺁﻣﺎﺩﮔﻲ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﺍﺩﻩ ﺳﭙﺲ‬
‫ﺑﻪ ﺧﻮﺍﻧﺪﻥ ﺩﻳﺘﺎ ﻳﺎ ﻧﻮﺷﺘﻦ ﺁﻥ ﻣﻴﭙﺮﺩﺍﺯﺩ‪.‬ﺩﺭ ﻣﺮﺣﻠﻪ ﺁﻣﺎﺩﮔﻲ )‪ (Initialization‬ﺳﻪ ﮔﺎﻡ ﺑﺮﺩﺍﺷﺘﻪ ﻣﻴﺸﻮﺩ‪:‬‬
‫ﮔﺎﻡ ‪ Master :۱‬ﺩﺭﺧﻮﺍﺳﺖ ﺷﻨﺎﺳﺎﻳﻲ ﻭﺿﻌﻴﺖ )‪ (Diagnostic‬ﻣﻴﻜﻨﺪ ﻭ ‪ Slave‬ﻭﺿﻌﻴﺖ ﺧﻮﺩ ﺭﺍ ﺍﻋﻼﻡ ﻣﻴﻜﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١١‬‬ ‫‪PROFIBUS DP‬‬

‫ﮔـﺎﻡ ‪ Master : ۲‬ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻳـﻲ ﻛـﻪ ‪ Slave‬ﺑـﺎﻳﺪ ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺍﺯ ﺁﻧﻬﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﺪ ﻣﺎﻧﻨﺪ ﺯﻣﺎﻥ ﭘﺎﺳﺦ ﺩﻫﻲ ﺭﺍ ﺑﻪ ﺁﻥ‬
‫ﻣﻴﻔﺮﺳﺘﺪ ‪ Slave .‬ﺗﺎﻳﻴﺪ ﻗﺒﻮﻝ )‪ (Acknowledge‬ﺭﺍ ﺑﻪ ‪ Master‬ﺍﻋﻼﻡ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﮔﺎﻡ ‪ Master : ٣‬ﺳﺎﺧﺘﺎﺭ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﭘﻴﻜﺮﺑﻨﺪﻱ ﺷﺪﻩ ﺑﺮﺍﻱ ‪ Slave‬ﺭﺍ ﺑﻪ ﺁﻥ ﺍﻋﻼﻡ ﻣﻴﻜﻨﺪ‪ .‬ﺍﮔﺮ ‪ Slave‬ﺗﻔﺎﻭﺗﻲ ﺑﻴﻦ‬
‫ﺁﻥ ﻭ ﺳﺎﺧﺘﺎﺭ ﻭﺍﻗﻌﻲ ﺑﺒﻴﻨﺪ ﺑﻪ ‪ Master‬ﺍﻋﻼﻡ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﭘـﺲ ﺍﺯ ﺍﻧﺠﺎﻡ ‪ ٣‬ﻣﺮﺣﻠﻪ ﻓﻮﻕ ﻛﺎﺭ ﺗﺒﺎﺩﻝ ﺳﻴﻜﻠﻲ ﺷﺮﻭﻉ ﻣﻴﺸﻮﺩ ‪ .‬ﻳﻌﻨﻲ ‪ Master‬ﺩﺭﺧﻮﺍﺳﺖ ﺩﻳﺘﺎ ﻣﻴﻜﻨﺪ ﻭ ‪ Slave‬ﺑﻪ ﺁﻥ‬
‫ﭘﺎﺳﺦ ﻣﻴﺪﻫﺪ‪ .‬ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺣﺪﺍﻛﺜﺮ ‪ ٢٤٤‬ﺑﺎﻳﺖ ﻭ ﺳﺮﻭﻳﺴﻲ ﻛﻪ ﺑﻜﺎﺭ ﮔﺮﻓﺘﻪ ﻣﻴﺸﻮﺩ ‪ SRD‬ﺍﺳﺖ‪.‬‬
‫ﺩﺭ ﻋﻴـﻦ ﺣـﺎﻝ ﻛـﻪ ﺗـﺒﺎﺩﻝ ﺳـﻴﻜﻠﻲ ﺍﻧﺠـﺎﻡ ﻣﻴﺸﻮﺩ ﻣﻴﺘﻮﺍﻧﺪ ﭘﻴﻐﺎﻣﻲ ﺗﻮﺳﻂ ‪ Master‬ﺑﻪ ﺗﻤﺎﻡ ‪ Slave‬ﻫﺎ ﺍﻋﻼﻡ ﺷﻮﺩ )ﻳﻌﻨﻲ‬
‫ﺑﺼـﻮﺭﺕ ‪ (Broadcast‬ﻭ ﻫﻤﻴﻨﻄﻮﺭ ﻣﻴﺘﻮﺍﻧﺪ ﭘﻴﻐﺎﻣﻲ ﺑﻪ ﮔﺮﻭﻫﻲ ﺍﺯ ‪ Slave‬ﻫﺎ ﺍﻋﻼﻡ ﺷﻮﺩ) ﻳﻌﻨﻲ ﺑﺼﻮﺭﺕ ‪( Multicast‬‬
‫ﻛﻪ ﺩﺭ ﻫﺮ ﺩﻭ ﺣﺎﻟﺖ ﺍﺯ ﺳﺮﻭﻳﺲ ‪ SDN‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﻳﻌﻨﻲ ﻧﻴﺎﺯ ﺑﻪ ﺗﺎﻳﻴﺪ ﺩﺭﻳﺎﻓﺖ ﺍﺯ ﻃﺮﻑ ﮔﻴﺮﻧﺪﻩ ﻧﻴﺴﺖ‪.‬‬
‫‪DP-V1‬‬
‫ﻧﺴﺨﻪ ﺑﻌﺪﻱ ‪ DP-V1‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺁﻥ ﺍﻣﻜﺎﻥ ﺍﺭﺗﺒﺎﻁ ﻏﻴﺮ ﺳﻴﻜﻠﻲ ﻧﻴﺰ ﺍﺿﺎﻓﻪ ﺷﺪﻩ ﺍﺳﺖ ﺑﺮﺍﻱ ﺩﺭﻙ ﺑﻬﺘﺮ ﺍﺭﺗﺒﺎﻁ ﻏﻴﺮ‬
‫ﺳﻴﻜﻠﻲ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﺩﺭ ﭘﺮﻭﺗﻜﻞ ‪ DP‬ﺩﻭﻧﻮﻉ ‪ Master‬ﺗﻌﺮﻳﻒ ﺷﺪﻩ ﺍﺳﺖ ‪:‬‬
‫‪ DP Master Class 1‬ﻛـﻪ ‪ DPM1‬ﺧﻮﺍﻧـﺪﻩ ﻣﻴﺸﻮﺩ ‪ .‬ﺍﻳﻦ ﻫﻤﺎﻥ ﻛﻨﺘﺮﻟﺮ ﻣﺮﻛﺰﻱ ﺍﺳﺖ ﻛﻪ ﺑﺼﻮﺭﺕ ﺳﻴﻜﻠﻲ ﺑﺎ‬ ‫•‬

‫‪ Slave‬ﻫﺎ ﺩﺭ ﺩﻭﺭﻩ ﺯﻣﺎﻧﻲ ﻣﻌﻴﻨﻲ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﻳﻚ ‪ PLC‬ﻳﺎ ﻳﻚ ‪ PC‬ﺑﺎﺷﺪ‪.‬‬
‫‪ DP Master Class 2‬ﻛـﻪ ‪ DPM2‬ﺧﻮﺍﻧـﺪﻩ ﻣﻴﺸـﻮﺩ ‪ .‬ﺍﻳـﻦ ﻭﺳﻴﻠﻪ ﻣﺎﻧﻨﺪ ‪ PC‬ﻳﺎ ‪ PG‬ﺩﺭ ﻃﻮﻝ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﻳﺎ‬ ‫•‬

‫ﺗﺸـﺨﻴﺺ ﻋﻴـﺐ ﻳﺎ ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﻛﺎﻟﻴﺒﺮﺍﺳﻴﻮﻥ ﻭ ﺍﻣﺜﺎﻝ ﺁﻥ ﺑﻪ ‪ Slave‬ﻫﺎ ﻣﺘﺼﻞ ﻣﻴﺸﻮﺩ‪ .‬ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺁﻥ‬
‫ﻣﻮﻗﺖ ﺑﻮﺩﻩ ﻭ ﻻﺯﻡ ﻧﻴﺴﺖ ﺑﻄﻮﺭ ﺩﺍﺋﻢ ﺑﻪ ﺑﺎﺱ ﻣﺘﺼﻞ ﺑﺎﺷﺪ‪.‬‬
‫‪:‬‬ ‫‪ DPM1‬ﺑﺼﻮﺭﺕ ﺳﻴﻜﻠﻲ ﻭ ‪ DPM2‬ﺑﺼﻮﺭﺕ ﻏﻴﺮ ﺳﻴﻜﻠﻲ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪١٢‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻣﺸﺨﺺ ﺍﺳﺖ ‪ DP Master 1‬ﭘﺮﭼﻢ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻪ ﻭ ﺑﺎ ‪ Slave‬ﻫﺎﻳﺶ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ‬
‫ﻣﻴﻜﻨﺪ ﻭﻗﺘﻲ ﺑﻪ ﺁﺧﺮﻳﻦ ‪ Slave‬ﺭﺳﻴﺪ ﭘﺮﭼﻢ ﺭﺍ ﺑﻪ ‪ DP Master 2‬ﻣﻴﺪﻫﺪ ﺗﺎ ﺩﺭ ﺯﻣﺎﻥ ﺑﺎﻗﻴﻤﺎﻧﺪﻩ ﺍﺯ ﺳﻴﻜﻞ ﺑﺎﺱ ﺑﺎ ﻫﺮ‬
‫‪DP Master 1‬‬ ‫‪ Slave‬ﻛﻪ ﻣﻴﺨﻮﺍﻫﺪ ﺑﺼﻮﺭﺕ ‪ Acyclic‬ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻛﻨﺪ‪ .‬ﺩﺭ ﭘﺎﻳﺎﻥ ﺳﻴﻜﻞ ﭘﺮﭼﻢ ﺩﻭﺑﺎﺭﻩ ﺑﻪ‬
‫ﺑﺮﮔﺸﺖ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬
‫ﻭﻳﮋﮔﻲ ﺩﻳﮕﺮ ‪ DP-V1‬ﺍﻣﻜﺎﻥ ﻫﺪﺍﻳﺖ ﺧﺮﻭﺟﻲ ‪ Slave‬ﻫﺎ ﺑﻪ ﺣﺎﻟﺖ ‪ Fail Safe‬ﺍﺳﺖ‪ .‬ﺑﺮﺍﻱ ‪ DPM1‬ﺳﻪ ﻣﺪ ﻛﺎﺭﻱ‬
‫‪ STOP‬ﻭ ‪ CLEAR‬ﻭ ‪ OPERATE‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﻗﺎﺑﻞ ﺗﻨﻈﻴﻢ ﺍﺳﺖ‪.‬‬
‫ﺩﺭ ﻣﺪ ‪ STOP‬ﻫﻴﭻ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎﻳﻲ ﺑﺎ ‪ Slave‬ﻫﺎ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ‪.‬‬ ‫•‬

‫ﺩﺭ ﻣﺪ ‪ OPERATE‬ﻛﺎﺭ ‪ Master‬ﺑﺎ ‪ Slave‬ﻧﺮﻣﺎﻝ ﺍﺳﺖ ﻳﻌﻨﻲ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬ ‫•‬

‫ﺩﺭ ﻣﺪ ‪ CLEAR‬ﺍﻃﻼﻋﺎﺕ ﻭﺭﻭﺩﻱ ﺍﺯ ‪ Slave‬ﻫﺎ ﺗﻮﺳﻂ ‪ Master‬ﺧﻮﺍﻧﺪﻩ ﻣﻴﺸﻮﺩ ﻭﻟﻲ ﺧﺮﻭﺟﻲ ﺁﻧﻬﺎ ﺩﺭ‬ ‫•‬
‫ﺣﺎﻟﺖ ‪ Safe‬ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﺩ‪.‬‬

‫ﻭﺍﻛﻨﺶ ﺳﻴﺴﺘﻢ ﺩﺭ ﺻﻮﺭﺕ ﻭﻗﻮﻉ ﺧﻄﺎ ) ﻣﺜﻼ ﺧﻄﺎ ﺭﻭﻱ ﻳﻚ ‪ (Slave‬ﺑﺴﺘﮕﻲ ﺑﻪ ﭘﺎﺭﺍﻣﺘﺮ ‪ Auto Clear‬ﺩﺍﺭﺩ ﺍﮔﺮ ﺍﻳﻦ‬
‫‪Safe‬‬ ‫ﭘﺎﺭﺍﻣﺘﺮ ‪ True‬ﺑﺎﺷﺪ ﺑﺎ ﺑﺮﻭﺯ ﺧﻄﺎ ﺭﻭﻱ ﻳﻚ ‪ Slave‬ﺧﺮﻭﺟﻴﻬﺎﻱ ﺗﻤﺎﻡ ‪ Slave‬ﻫﺎ ﺗﻮﺳﻂ ‪ Master‬ﺩﺭ ﺣﺎﻟﺖ‬
‫ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﺩ ﻭﻟﻲ ﺍﮔﺮ ﭘﺎﺭﺍﻣﺘﺮ ﻓﻮﻕ ‪ False‬ﺑﺎﺷﺪ ‪ DPM1‬ﻛﻤﺎﻛﺎﻥ ﺩﺭ ﻭﺿﻌﻴﺖ ‪ OPERATE‬ﺑﺎﻗﻲ ﻣﻴﻤﺎﻧﺪ ﺗﺎ ﺍﭘﺮﺍﺗﻮﺭ‬
‫ﻭﺍﻛﻨﺶ ﻣﻘﺘﻀﻲ ﺭﺍ ﺑﻪ ﺧﻄﺎ ﻧﺸﺎﻥ ﺩﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٣‬‬ ‫‪PROFIBUS DP‬‬

‫‪DP-V2‬‬
‫ﺑﻌـﺪ ﺍﺯ ﻧﺴـﺨﻪ ‪ DP-V1‬ﻧﺴـﺨﻪ ‪ DP-V2‬ﻋﺮﺿـﻪ ﺷـﺪﻩ ﺍﺳـﺖ ﻭ ﺩﺭ ﺁﻥ ﺍﻣﻜـﺎﻥ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎﻱ ﻣﺴﺘﻘﻴﻢ ﺑﻴﻦ ‪ Slave‬ﻫﺎ ﻧﻴﺰ‬
‫‪Slave‬‬ ‫ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﻣﻨﺠﺮ ﺑﻪ ﺻﺮﻓﻪ ﺟﻮﻳﻲ ﻗﺎﺑﻞ ﺗﻮﺟﻬﻲ ﺩﺭ ﺯﻣﺎﻥ ﻣﻴﺸﻮﺩ ﺯﻳﺮﺍ ﻻﺯﻡ ﻧﻴﺴﺖ ‪ Master‬ﺩﻳﺘﺎ ﺭﺍ ﺍﺯ ﻳﻚ‬
‫ﺑﮕـﻴﺮﺩ ﻭ ﺑـﻪ ‪ Slave‬ﺩﻳﮕـﺮ ﺑﺪﻫـﺪ ﺍﻳـﻨﻜﺎﺭ ﻣﺴـﺘﻘﻴﻤﺎ ﺍﻧﺠـﺎﻡ ﻣﻴﺸـﻮﺩ‪ .‬ﺍﻳﻦ ﺭﻭﺵ ﺑﺼﻮﺭﺕ ‪ Broadcast‬ﺍﺳﺖ ﻳﻌﻨﻲ ﻳﻚ‬
‫‪ Slave‬ﺑﻌـﻨﻮﺍﻥ ‪ Publisher‬ﺩﻳـﺘﺎﻱ ﺧـﻮﺩ ﺭﺍ ﺟﻬـﺖ ﺍﺳﺘﻔﺎﺩﻩ ﺳﺎﻳﺮ ‪ Slave‬ﻫﺎ ﻛﻪ ‪ Subscriber‬ﻧﺎﻣﻴﺪﻩ ﻣﻴﺸﻮﻧﺪ ﺭﻭﻱ‬
‫ﺑﺎﺱ ﻗﺮﺍﺭ ﻣﻴﺪﻫﺪ‪ .‬ﺗﺎ ﺩﺭ ﺻﻮﺭﺕ ﻧﻴﺎﺯ ﺁﻧﺮﺍ ﺧﻮﺍﻧﺪﻩ ﻭ ﺑﻌﻨﻮﺍﻥ ﻭﺭﻭﺩﻱ ﺧﻮﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﺎﻳﻨﺪ‪.‬‬

‫ﻭﻳﮋﮔـﻲ ﺩﻳﮕـﺮ ‪ DP-V2‬ﻗﺎﺑﻠﻴﺖ ﻫﻤﺰﻣﺎﻥ ﺳﺎﺯﻱ )‪ (Synchronizing‬ﺍﺳﺖ ‪ .‬ﺍﮔﺮ ﻻﺯﻡ ﺑﺎﺷﺪ ﻛﻪ ﺧﺮﻭﺟﻲ ‪ Slave‬ﻫﺎ ﺑﺎ‬
‫ﻳﻜﺪﻳﮕـﺮ ﻫﻤـﺰﻣﺎﻥ ﺷـﻮﻧﺪ ﻣﻴـﺘﻮﺍﻥ ﺁﻧﻬـﺎ ﺭﺍ ﺩﺭ ﺍﻳـﻦ ﺭﻭﺵ ﺩﺭ ﻳﻚ ﺣﺎﻓﻈﻪ ﻣﻮﻗﺖ ﻗﺮﺍﺭ ﺩﺍﺩ ﺳﭙﺲ ﺑﺎ ﻓﺮﻣﺎﻥ ‪ SYNC‬ﺑﻄﻮﺭ‬
‫ﻫﻤـﺰﻣﺎﻥ ﺁﻧﻬـﺎ ﺭﺍ ﺑـﻪ ﺧﺮﻭﺟـﻲ ﻫـﺎ ﺍﺭﺳـﺎﻝ ﻧﻤـﻮﺩ‪.‬ﺑـﺮﺍﻱ ﻭﺭﻭﺩﻱ ﻫﺎﻱ ‪ Slave‬ﻫﺎ ﻧﻴﺰ ﻣﻴﺘﻮﺍﻥ ﻋﻤﻞ ﻫﻤﺰﻣﺎﻥ ﺳﺎﺯﻱ ﺭﺍ ﺷﺒﻴﻪ‬
‫ﺧﺮﻭﺟﻲ ﻫﺎ ﻭﻟﻲ ﺑﺎ ﻓﺮﻣﺎﻥ ‪ FREEZE‬ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪.‬‬
‫ﻓﻘـﻂ ﻭﻗﺘـﻲ ﻓـﺮﻣﺎﻧﻬﺎﻱ ‪ UNSYNC‬ﻭ ‪ UNFREEZE‬ﺍﺯ ﻃـﺮﻑ ‪ Master‬ﺑـﻪ ‪ Slave‬ﻫـﺎ ﺍﻋـﻼﻡ ﺷـﻮﺩ ﺍﺟﺎﺯﻩ ﺩﺍﺭﻧﺪ‬
‫ﻭﺭﻭﺩﻳﻬﺎ ﻭ ﺧﺮﻭﺟﻴﻬﺎﻱ ﺧﻮﺩ ﺭﺍ ‪ Update‬ﻛﻨﻨﺪ‪.‬‬
‫‪ Broadcast‬ﺑﻮﺩﻩ ﻭ ﺑﺎ ﺳﺮﻭﻳﺲ ‪SDN‬‬ ‫ﻓـﺮﻣﺎﻧﻬﺎﻱ ‪ SYNC‬ﻭ ‪ FREEZE‬ﻭ ‪ UNSYNC‬ﻭ ‪ UNFREEZE‬ﺑﺼﻮﺭﺕ‬
‫ﺑﻪ ﺗﻤﺎﻡ ‪ Slave‬ﻫﺎ ﻣﻨﺘﻘﻞ ﻣﻴﺸﻮﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪١٤‬‬

‫ﻣﻜﺎﻧﻴﺴﻢ ﻫﺎﻱ ﺣﻔﺎﻇﺘﻲ‬

‫ﺩﺭ ﺗﻤﺎﻣﻲ ﻧﺴﺨﻪ ﻫﺎﻱ‪ V0‬ﻭ ‪ V1‬ﻭ ‪ V2‬ﻣﻜﺎﻧﻴﺴﻢ ﻫﺎﻱ ﺣﻔﺎﻇﺘﻲ ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻪ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﻳﻜﻲ ﺍﺯ ﺍﻳﻦ‬
‫ﻣﻜﺎﻧﻴﺴﻢ ﻫﺎ ﻣﺎﻧﻴﺘﻮﺭ ﻛﺮﺩﻥ ﺯﻣﺎﻥ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪:‬‬
‫ﺩﺭ ﺳﻤﺖ ‪ Master‬ﺑﺮﺍﻱ ‪ DPM1‬ﺑﻪ ﺍﺯﺍﻱ ﻫﺮ ‪ Slave‬ﻳﻚ ﺗﺎﻳﻤﺮ ﻛﻨﺘﺮﻝ ﺩﻳﺘﺎﻱ ﺟﺪﺍﮔﺎﻧﻪ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬ ‫•‬
‫ﺍﮔﺮ ﺩﺭ ﻃﻮﻝ ﺯﻣﺎﻥ ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺩﻳﺘﺎﻱ ﺻﺤﻴﺢ ﺍﺯ ‪ Slave‬ﺩﺭﻳﺎﻓﺖ ﻧﺸﻮﺩ ﺗﺎﻳﻤﺮ ﻣﺰﺑﻮﺭ ﺩﺳﺘﻮﺭ ﺗﻮﻗﻒ ﻣﻴﺪﻫﺪ‬
‫ﻣﮕﺮ ﺍﻳﻨﻜﻪ ﻣﺪ ‪ Auto-Clear‬ﻓﻌﺎﻝ ﺷﺪﻩ ﺑﺎﺷﺪ ﻛﻪ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ‪ DPM1‬ﺑﻪ ﻛﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﻣﻴﺪﻫﺪ ﻭ‬
‫ﺧﺮﻭﺟﻲ ﻫﺎﻱ ‪ Slave‬ﻣﺬﻛﻮﺭ ﺭﺍ ﺩﺭ ﺣﺎﻟﺖ ‪ Fail Safe‬ﻧﮕﻪ ﻣﻴﺪﺍﺭﺩ‪.‬‬
‫ﺑﺮﺍﻱ ﻫﺮ ‪ Slave‬ﻳﻚ ‪ Watchdog‬ﻣﻨﻈﻮﺭ ﺷﺪﻩ ﻛﻪ ﺧﻄﺎﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Master‬ﻳﺎ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺭﺍ ﺁﺷﻜﺎﺭ‬ ‫•‬

‫‪Watchdog‬‬ ‫ﻣﻲ ﺳﺎﺯﺩ‪ .‬ﺍﮔﺮ ﺩﺭ ﻃﻮﻝ ﺯﻣﺎﻥ ﻛﻨﺘﺮﻝ ﺷﺪﻩ ﺩﻳﺘﺎﻳﻲ ﺑﺎ ‪ Master‬ﺗﺒﺎﺩﻝ ﻧﺸﻮﺩ ﺑﻄﻮﺭ ﺧﻮﺩﻛﺎﺭ‬
‫ﺧﺮﻭﺟﻲ ﻫﺎﻱ ‪ Slave‬ﻣﺰﺑﻮﺭ ﺭﺍ ﺑﻪ ﺣﺎﻟﺖ ‪ Fail Safe‬ﻫﺪﺍﻳﺖ ﻣﻴﻜﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٥‬‬ ‫‪PROFIBUS DP‬‬

‫‪PROFIBUS DP‬‬ ‫‪ ۲-٣-١‬ﺗﻜﻨﻮﻟﻮﮊﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ‬

‫ﺍﻟﻒ ( ﺍﻧﺘﻘﺎﻝ ﺑﺎ ﻛﺎﺑﻞ ﻣﺴﻲ‬
‫ﺩﺭﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﻻﻳﻪ ﻓﻴﺰﻳﻜﻲ ‪ PROFIBUS‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺍﺯ ﺯﻭﺝ ﺳﻴﻢ ﺑﻪ ﻫﻢ ﺗﺎﺑﻴﺪﻩ ﺷﻴﻠﺪ ﺩﺍﺭ ) ‪ ( STP‬ﻣﻄﺎﺑﻖ ﺑﺎ‬
‫ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ EIA RS 485‬ﻣﻮﺳﻮﻡ ﺑﻪ ‪ H2‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫‪Semi-‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ RS485‬ﻳﻚ ﺭﻭﺵ ﺳﺎﺩﻩ ﻭ ﻣﻮﺛﺮ ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺳﺮﻳﻊ ﺩﻳﺘﺎﺳﺖ ﻛﻪ ﺑﺼﻮﺭﺕ ﻳﻚ ﺍﺭﺗﺒﺎﻁ ﺩﻭﺳﻴﻤﻪ‬
‫‪ Duplex‬ﻣﻴﺒﺎﺷﺪ ﻳﻌﻨﻲ ﺍﮔﺮ ﭼﻪ ﭼﻨﺪﻳﻦ ﻭﺳﻴﻠﻪ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻪ ﺁﻥ ﻣﺘﺼﻞ ﺷﻮﺩ )‪ (Multidrop‬ﻭﻟﻲ ﺑﻌﻠﺖ‬
‫ﻭﺟﻮﺩ ﺍﺭﺗﺒﺎﻁ ﻧﻴﻢ ﺩﻭﻃﺮﻓﻪ ﻳﺎ ‪ Half-Duplex‬ﺩﺭ ﻫﺮ ﻟﺤﻈﻪ ﻓﻘﻂ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻴﺘﻮﺍﻧﺪ ﻓﺮﺳﺘﻨﺪﻩ ﺑﺎﺷﺪ ﻧﻪ ﺑﻴﺸﺘﺮ‪ .‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬
‫‪ RS485‬ﭼﻬﺎﺭ ﺳﻴﻤﻪ ﻧﻴﺰ ﺳﻴﺴﺘﻢ ﺭﺍ ﺩﻭﻃﺮﻓﻪ ﻳﺎ ‪ Full Duplex‬ﻧﺨﻮﺍﻫﺪ ﻛﺮﺩ‪.‬ﺯﻳﺮﺍ ﺳﺎﺧﺘﺎﺭ ﺍﻳﻦ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺑﺼﻮﺭﺕ ﻧﻴﻢ‬
‫ﺩﻭﻃﺮﻓﻪ ﺍﺳﺖ‪.‬‬

‫ﺳﻴﮕﻨﺎﻝ‪ RS485‬ﺑﺮﺧﻼﻑ ‪ RS232‬ﻛﻪ ‪ Single_Ended‬ﺍﺳﺖ ﻳﻚ ﺳﻴﮕﻨﺎﻝ ﺗﻔﺎﺿﻠﻲ ﺍﺳﺖ ﻳﻌﻨﻲ ﻧﺴﺒﺖ ﺑﻪ ﺯﻣﻴﻦ‬
‫‪RS232‬‬ ‫ﺳﻨﺠﻴﺪﻩ ﻧﻤﻴﺸﻮﺩ ﺑﻠﻜﻪ ﺳﻄﺢ ﻭﻟﺘﺎﮊ ﺗﻔﺎﺿﻠﻲ ﺑﻴﻦ ﺩﻭﺳﻴﻢ ﺍﺳﺖ ﻛﻪ ﺻﻔﺮ ﻳﺎ ﻳﻚ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪ .‬ﺍﺯﺍﻳﻨﺮﻭ ﺑﺮﺧﻼﻑ‬
‫ﻧﻮﻳﺰ ﺑﺮ ﺁﻥ ﻛﻤﺘﺮ ﺗﺎﺛﻴﺮ ﺩﺍﺭﺩ ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪١٦‬‬

‫ﺩﺭ ﺷﻜﻞ ‪ ١-٦‬ﺩﻭ ﺧﻂ ﺍﻧﺘﻘﺎﻝ ‪ A‬ﻭ ‪B‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻣﻲ ﻛﻨﻴﺪ ‪ .‬ﺍﮔﺮ ﺳﻴﮕﻨﺎﻝ ﺧﻂ ‪ B‬ﻣﺜﺒﺖ ﻭﺳﻴﮕﻨﺎﻝ ﺧﻂ ‪ A‬ﻣﻌﻜﻮﺱ ﺳﻴﮕﻨﺎﻝ‬
‫ﺧﻂ ‪ B‬ﺑﺎﺷﺪ ‪،‬ﺍﻳﻦ ﻭﺿﻌﻴﺖ ﻣﻌﺎﺩﻝ ‪ 1‬ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻪ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ‪:‬‬

‫ﺳﻴﮕﻨﺎﻝ ﺗﻔﺎﺿﻠﻲ ﺑﻴﻦ‪ A‬ﻭ ‪B‬‬ ‫ﻭﺿﻌﻴﺖ‬
‫‪-0.2 to -7 V‬‬ ‫‪ 1‬ﻣﻨﻄﻘﻲ‬
‫‪+0.2 to +12 V‬‬ ‫‪ 0‬ﻣﻨﻄﻘﻲ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺫﻛﺮ ﺷﺪ ﺩﺭ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ RS485‬ﻳﻚ ﺭﺷﺘﻪ ﺳﻴﻢ ﺗﻚ ﺯﻭﺝ ﺷﻴﻠﺪ ﺩﺍﺭ ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﻛﺎﻓﻴﺴﺖ‪ .‬ﺗﻮﺻﻴﻪ‬
‫ﻣﻮﺳﺴﻪ ﺑﻴﻦ ﺍﻟﻤﻠﻠﻲ ‪ PROFIBUS‬ﺑﺮ ﺍﻳﻨﺴﺖ ﻛﻪ ﺍﺯﻛﺎﺑﻞ ﺑﺎ ﻣﺸﺨﺼﺎﺕ ﺯﻳﺮ ﻛﻪ ﻛﺎﺑﻞ ﻧﻮﻉ ‪ A‬ﻧﺎﻣﻴﺪﻩ ﻣﻴﺸﻮﺩ ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﮔﺮﺩﺩ ‪:‬‬
‫‪Cable Type A‬‬
‫‪Impedance‬‬ ‫‪135-165 Ώ‬‬
‫‪Capacity‬‬ ‫‪<= 30 pf/m‬‬
‫‪Loop Resistance‬‬ ‫‪<= 110 Ώ /km‬‬
‫‪Wire Diameter‬‬ ‫‪> 0.64 mm‬‬
‫‪Core Cross-Section‬‬ ‫‪> 0.34 mm2‬‬

‫ﺑﺎ ﺍﻳﻦ ﻛﺎﺑﻞ ﺳﺮﻋﺘﻬﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺑﻴﻦ ‪ 9.6 kb/s‬ﺗﺎ ‪ 12 Mb/s‬ﻗﺎﺑﻞ ﺍﻧﺘﺨﺎﺏ ﺍﺳﺖ‪ .‬ﺣﺪﺍﻛﺜﺮ ﺗﺎ ‪ ٣٢‬ﻭﺳﻴﻠﻪ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﻛﺎﺑﻞ‬
‫ﻓﻮﻕ ﻣﺘﺼﻞ ﻧﻤﻮﺩ ﻛﻪ ﻳﻚ ‪ Segment‬ﺭﺍ ﺗﺸﻜﻴﻞ ﻣﻴﺪﻫﺪ‪ .‬ﻃﻮﻝ ﻣﺠﺎﺯ ﺑﺮﺍﻱ ﻳﻚ ﺳﮕﻤﻨﺖ ﺑﺴﺘﮕﻲ ﺑﻪ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ‬
‫ﺩﻳﺘﺎﻳﻲ ﺩﺍﺭﺩ ﻛﻪ ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﺩﺭ ﺷﺒﻜﻪ‪ PROFIBUS‬ﺑﺮﻗﺮﺍﺭ ﺑﺎﺷﺪ )ﻣﻄﺎﺑﻖ ﺟﺪﻭﻝ ﺯﻳﺮ ( ﻧﻜﺘﻪ ﻣﻬﻢ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺳﺮﻋﺖ‬
‫ﺍﻧﺘﺨﺎﺑﻲ ﺑﺮﺍﻱ ﻳﻚ ‪ Segment‬ﺑﺎﻳﺪ ﺑﻪ ﺗﻤﺎﻣﻲ ﺗﺠﻬﻴﺰﺍﺕ ﻣﺘﺼﻞ ﺑﻪ ﺁﻥ‪ Segment‬ﺍﻋﻤﺎﻝ ﺷﻮﺩ‪.‬‬

‫‪Data transfer rate in kbit/s 9.6 19.2‬‬ ‫‪45.45‬‬ ‫‪93.75 187.5 500‬‬ ‫‪1500‬‬ ‫‪3000‬‬ ‫‪6000‬‬ ‫‪12000‬‬
‫‪Max. segment length in m 1200 1200‬‬ ‫‪1200‬‬ ‫‪1200‬‬ ‫‪1000‬‬ ‫‪400‬‬ ‫‪200‬‬ ‫‪100‬‬ ‫‪100‬‬ ‫‪100‬‬
Techno-Electro.com

١٧ PROFIBUS DP

‫ ﻳﻚ ﻛﺎﻧﻜﺘﻮﺭ‬EN 50 170 ‫ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﻃﺒﻖ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺑﻴﻦ ﺍﻟﻤﻠﻠﻲ‬PROFIBUS‫ﻛﺎﻧﻜـﺘﻮﺭﻱ ﻛـﻪ ﺑـﺮﺍﻱ ﺍﺗﺼﺎﻻﺕ‬
‫ ﺑﺮ ﺭﻭﻱ ﺍﻳﺴﺘﮕﺎﻩ ﻧﺼﺐ ﻣﻲ ﺷﻮﺩ ﻭﻛﺎﺑﻞ ﺷﺒﻜﻪ ﺍﺯ‬Sub D ‫ ﺑـﻪ ﺍﻳـﻦ ﻣـﻨﻈﻮﺭ ﻳـﻚ ﺳـﻮﻛﺖ‬.‫ ﺍﺳـﺖ‬9-Pin Sub D Plug
.‫ ﻣﺸﺨﺼﺎﺕ ﺍﻳﻦ ﻛﺎﻧﻜﺘﻮﺭ ﺁﻣﺪﻩ ﺍﺳﺖ‬١-٤ ‫ﺩﺭ ﺟﺪﻭﻝ‬.‫ ﺑﻪ ﺁﻥ ﻭﺻﻞ ﻣﻲ ﺷﻮﺩ‬Sub D Plug ‫ﻃﺮﻳﻖ ﻛﺎﻧﻜﺘﻮﺭ‬
Pin no. Signal Significance
1 Shield Shield/functional ground
2 M24 Ground for +24 V output voltage
3 RxD/TxD-P Receive/Transmit data – plus (B wire)
4 CNTR-P Repeater control signal (direction control), RTS signal
5 DGND *) Data ground (reference potential for VP)
6 VP *) Supply voltage - plus (P5V)
7 P24 Output voltage +24 V
8 RxD/TxD-N Receive/Transmit data – minus (A wire)
9 CNTR-N Repeater control signal (direction control)
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪١٨‬‬

‫ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎﻱ ﻫﺮ ﺳﮕﻤﻨﺖ ﺑﺎﻳﺪ ﺗﻮﺳﻂ ‪ Terminator‬ﺑﺴﺘﻪ ﺷﻮﺩ ‪ .‬ﺑﺮ ﻃﺒﻖ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ RS 485‬ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﺧﻄﻮﻁ ﺍﻧﺘﻘﺎﻝ‬
‫ﺩﻳﺘﺎ ﻳﻚ ﻣﻘﺎﻭﻣﺖ ‪) Pull-Down‬ﺩﺭ ﻃﺮﻑ ‪ ( DGND‬ﻭ ﻳﻚ ﻣﻘﺎﻭﻣﺖ ‪ Pull-Up‬ﺩﺭ ﻃﺮﻑ ‪)VP‬ﻣﻨﺒﻊ ﺗﻐﺬﻳﻪ( ﻗﺮﺍﺭ ﺩﺍﺩﻩ‬
‫ﻣﻴﺸﻮﺩ ﻛﻪ ﺑﻪ ﺁﻧﻬﺎ ‪ Terminator‬ﻣﻴﮕﻮﻳﻨﺪ‪.‬‬

‫ﺍﻳﻦ ﺩﻭ ﻣﻘﺎﻭﻣﺖ ﺑﺎﻋﺚ ﻣﻲ ﺷﻮﻧﺪ ﺯﻣﺎﻧﻲ ﻛﻪ ﺑﺎﺱ ﺁﺯﺍﺩ ﺍﺳﺖ ﻭﻫﻴﭻ ﻛﺪﺍﻡ ﺍﺯ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﭼﻴﺰﻱ ﺭﻭﻱ ﺑﺎﺱ ﻧﻔﺮﺳﺘﺎﺩﻩ ﺍﻧﺪ‬
‫ﻳﻚ ﻣﻘﺪﺍﺭ ﻭﻟﺘﺎﮊ ﻣﻌﻴﻦ ﺭﻭﻱ ﺑﺎﺱ ﻗﺮﺍﺭ ﮔﻴﺮﺩ ﻭﺍﺯ ﺑﻮﺟﻮﺩ ﺁﻣﺪﻥ ﻭﻟﺘﺎﮊﻫﺎﻱ ﺗﻌﺮﻳﻒ ﻧﺸﺪﻩ ﺑﺮ ﺭﻭﻱ ﺑﺎﺱ ‪،‬ﺟﻠﻮﮔﻴﺮﻱ ﺷﻮﺩ‬
‫ﺍﺳﺘﺎﻧﺪﺍﺭﺩ‪PROFIBUS‬‬ ‫ﻻ ﺗﻮﺳﻂ ﺳﺎﺯﻧﺪﻩ ﺑﺮ ﺭﻭﻱ ﻛﺎﻧﻜﺘﻮﺭﻫﺎﻱ‬
‫‪.‬ﺗﺮﻛﻴﺒﻲ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ ﻣﻌﻤﻮ ﹰ‬
‫ﺗﻌﺒﻴﻪ ﺷﺪﻩ ﻭﺍﻳﻦ ﺍﻣﻜﺎﻥ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﺎ ﻳﻚ ‪ Jumper‬ﻳﺎ ‪ ،Switch‬ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﺑﺎﺱ ‪ Terminator‬ﺭﺍ ﻓﻌﺎﻝ )‪(ON‬ﻳﺎ‬
‫ﻏﻴﺮ ﻓﻌﺎﻝ )‪ (OFF‬ﻛﻨﻴﻢ‪.‬‬
‫ﺍﮔﺮ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺑﻴﺶ ﺍﺯ ‪ 1.5 Mbps‬ﺑﺎﺷﺪ ﺑﺎﻳﺪ ﺍﺯ ‪ Terminator‬ﻫﺎﻳﻲ ﺑﺎ ﺍﻧﺪﻭﻛﺘﺎﻧﺲ ﻃﻮﻟﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻛﻪ ﺑﻪ‬
‫ﺑﺎﺭ ﺧﺎﺯﻧﻲ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻮﺭﺩ ﻧﻈﺮﻭﺻﻞ ﻣﻴﺸﻮﻧﺪ‪.‬ﺍﻳﻦ ﻋﻤﻞ ﺑﺎﻋﺚ ﻣﻲ ﺷﻮﺩ ﺍﺯ ﺍﻧﻌﻜﺎﺱ ﻭﺑﺎﺯﮔﺸﺖ ﻣﻮﺝ ﺩﻳﺘﺎ ﺟﻠﻮﮔﻴﺮﻱ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٩‬‬ ‫‪PROFIBUS DP‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻗﺎﺑﻞ ﺍﺟﺮﺍ ﺑﺎ ﻛﺎﺑﻞ ﻣﺴﻲ‬

‫ﺯﻣﺎﻧـﻲ ﻛـﻪ ﻣﺤـﻴﻂ ﺍﻧﺘﻘﺎﻝ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺍﺳﺖ ﻭﻧﺤﻮﻩ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﻣﻄﺎﺑﻖ ﺑﺎ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ RS485‬ﺍﺳﺖ‪،‬ﺍﻣﻜﺎﻥ ﭘﻴﺎﺩﻩ‬
‫ﺳﺎﺯﻱ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ‪ Star ، Bus‬ﻭ‪ Tree.‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬ﺍﻣﺎ ﻣﺮﺳﻮﻡ ﺗﺮﻳﻦ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻛﻪ ﺑﺎ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ‬
‫ﻣﻲ ﺷﻮﺩ ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ Bus‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﻪ ﺷﺮﺡ ﺁﻥ ﻣﻲ ﭘﺮﺩﺍﺯﻳﻢ‪.‬‬
‫ﻳـﻚ ﺳﻴﺴﺘﻢ ‪ PROFIBUS‬ﻣﺘﺸﻜﻞ ﺍﺯ ﻳﻚ ‪ Bus‬ﻛﻪ ﺩﺭ ﺩﻭ ﺍﻧﺘﻬﺎﻱ ﺁﻥ‪ Terminator‬ﻫﺎﻱ ﻓﻌﺎﻝ ﺗﻌﺒﻴﻪ ﺷﺪﻩ ﺍﺳﺖ ﺭﺍ ﺩﺭ‬
‫ﻼ ﮔﻔﺘﻪ ﺷﺪ ﺑﻪ ﺍﻳﻦ ﺑﺎﺱ ‪،‬ﻳﻚ ﺳﮕﻤﻨﺖ ‪ RS485‬ﮔﻔﺘﻪ ﻣﻲ ﺷﻮﺩ‪.‬ﺑﺮﺍﺳﺎﺱ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ‪RS485‬‬
‫ﻧﻈﺮ ﺑﮕﻴﺮﻳﺪ‪.‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒ ﹰ‬
‫‪،‬ﺗـﺎ ﺣﺪﺍﻛـﺜﺮ ‪ ٣٢‬ﺍﻳﺴﺘﮕﺎﻩ ‪ RS 485‬ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﺑﻪ ﺍﻳﻦ ﺳﮕﻤﻨﺖ ﺭﺍ ﺩﺍﺭﻧﺪ‪.‬ﺑﻪ ﺍﻳﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺩﺭ ﺍﺻﻄﻼﺡ ﺷﺒﻜﻪ‪Node،‬‬

‫ﮔﻔﺘﻪ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﺍﻳـﻦ ‪ Node‬ﭼـﻪ ‪ Master‬ﺑﺎﺷﺪ ﻭﭼﻪ ‪ Slave‬ﻳﻚ ﺑﺎﺭ ﺟﺮﻳﺎﻧﻲ ﺑﺮﺍﻱ ﺳﮕﻤﻨﺖ ﻣﺤﺴﻮﺏ ﻣﻲ ﺷﻮﺩ ‪.‬ﺍﮔﺮ ﺗﻌﺪﺍﺩ ‪ Node‬ﻫﺎ‬
‫ﺑـﻴﺶ ﺍﺯ ﻇﺮﻓﻴـﺖ ﻳـﻚ ﺳﮕﻤﻨﺖ ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﺳﻴﺴﺘﻢ ‪ PROFIBUS‬ﺍﺯ ﺗﻌﺪﺍﺩ ﺑﻴﺶ ﺍﺯ ‪ Node ٣٢‬ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﺑﺎﺷﺪ ﺩﺭ‬
‫ﺍﻳﻨﺼـﻮﺭﺕ ﺑـﺎﻳﺪ ﺑـﻪ ﭼﻨﺪﻳـﻦ ﺳـﮕﻤﻨﺖ ﺗﻘﺴـﻴﻢ ﺷـﻮﺩ‪.‬ﺍﻳـﻦ ﺳـﮕﻤﻨﺖ ﻫﺎﻱ ﺟﺪﺍﮔﺎﻧﻪ ‪،‬ﺗﻮﺳﻂ‪ Repeater‬ﺑﻪ ﻫﻢ ﻣﺘﺼﻞ ﻣﻲ‬
‫ﺷـﻮﻧﺪ‪.‬ﺩﺭ ﻭﺍﻗـﻊ‪ Repeater‬ﻣﺎﻧﻨﺪ ﻳﻚ ﺗﻘﻮﻳﺖ ﻛﻨﻨﺪﻩ ﻋﻤﻞ ﻣﻲ ﻛﻨﺪ ﻭﺳﻄﺢ ﺳﻴﮕﻨﺎﻝ ﺍﻧﺘﻘﺎﻟﻲ ﺭﺍ ﺗﻘﻮﻳﺖ ﻣﻲ ﻧﻤﺎﻳﺪ‪.‬ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﺍﺯ‪ Repeater‬ﺑﺎﻋـﺚ ﺍﻳﺠـﺎﺩ ﺗﺄﺧـﻴﺮ ﻭﺍﺧﺘﻼﻑ ﻓﺎﺯ ﺩﺭ ﺳﻴﮕﻨﺎﻝ ﺍﺭﺳﺎﻟﻲ ﻣﻲ ﺷﻮﺩ‪.‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﻪ ﻋﻠﺖ ﺍﻳﺠﺎﺩ ﺍﻋﻮﺟﺎﺝ ﻭﺗﺄﺧﻴﺮ‬
‫ﺩﺭ ﺳـﻴﮕﻨﺎﻝ ﺍﺭﺳﺎﻟﻲ ‪،‬ﻭﻋﺪﻡ ﺍﻣﻜﺎﻥ ﺑﺎﺯﻳﺎﺑﻲ ﺳﻴﮕﻨﺎﻝ ‪،‬ﺗﻌﺪﺍﺩ‪ Repeater‬ﻫﺎﻳﻲ ﻛﻪ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﻪ ﺻﻮﺭﺕ ﺳﺮﻱ ﺑﻪ ﻛﺎﺭ ﺑﺮﺩﻩ‬
‫ﺷـﻮﻧﺪ ﺑـﺮ ﻃـﺒﻖ ﺍﺳـﺘﺎﻧﺪﺍﺭﺩ ‪ EN 50170‬ﺣـﺪ ﺍﻛﺜﺮ ‪ ٣‬ﻋﺪﺩ ﻣﻲ ﺑﺎﺷﺪ‪ .‬ﺍﻳﻦ ﺗﻌﺪﺍﺩ ‪،Repeater‬ﻓﻘﻂ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﺗﻘﻮﻳﺖ ﻣﻲ‬
‫ﻛﻨﻨﺪ ﻭﺍﺛﺮ ﭼﻨﺪﺍﻧﻲ ﺩﺭ ﺍﻳﺠﺎﺩ ﺍﺧﺘﻼﻝ ﺩﺭ ﺳﻴﮕﻨﺎﻝ ﺍﺭﺳﺎﻟﻲ ﻧﺪﺍﺭﻧﺪ‪.‬‬
‫ﺑﺮﺧـﻲ ﺍﺯ ‪ Repeater‬ﻫـﺎ ﻋﻤـﻞ ﺑﺎﺯﻳﺎﺑﻲ ﺳﻴﮕﻨﺎﻝ )‪ (Signal Referesh‬ﺭﺍ ﻫﻢ ﺑﻪ ﻃﻮﺭ ﻣﺤﺪﻭﺩ ﺍﻧﺠﺎﻡ ﻣﻲ ﺩﻫﻨﺪ ﺍﮔﺮ ﺍﺯ‬
‫ﺍﻳـﻦ ﻧـﻮﻉ ‪ Repeater‬ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ ﺣﺪﺍﻛﺜﺮ ‪ ٩‬ﻋﺪﺩ ‪ Repeater‬ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺳﺮﻱ ﻛﺮﺩ ﻭ ﻃﻮﻝ ﻛﻠﻲ ﺷﺒﻜﻪ ﺗﺎ ‪ ٤‬ﻛﻴﻠﻮﻣﺘﺮ‬
‫ﻗﺎﺑﻞ ﺍﻓﺰﺍﻳﺶ ﺍﺳﺖ‪ Repeater .‬ﺑﺎﻛﺪ ﺳﻔﺎﺭﺵ ‪ 6ES7 971-0A00-0XA0‬ﺳﺎﺧﺖ ﺯﻳﻤﻨﺲ ﺍﺯ ﺍﻳﻦ ﻧﻮﻉ ﺍﺳﺖ‪.‬‬
‫ﺗـﻨﻬﺎ ﺑـﺎ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ‪ Repeater‬ﺍﻣﻜـﺎﻥ ﺩﺳـﺘﻴﺎﺑﻲ ﺑـﻪ ﻣﺎﻛﺰﻳﻤﻢ ﺗﻌﺪﺍﺩ‪ Node‬ﺩﺭﺷﺒﻜﻪ ‪ PROFIBUS‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻭﺗﻨﻬﺎﺑﺎ‬
‫ﺍﺳــﺘﻔﺎﺩﻩ ﺍﺯ ‪ Repeater‬ﻫــﺎ ﺍﺳــﺖ ﻛــﻪ ﻣــﻲ ﺗﻮﺍﻧــﻴﻢ ﺳــﺎﺧﺘﺎﺭﻫﺎﻱ ‪Tree‬ﻭ‪Star‬ﺭﺍ ﺍﻳﺠــﺎﺩ ﻛﻨــﻴﻢ‪.‬ﻫﻤﭽﻨﻴــﻦ ﺑــﺎ ﺑﻜــﺎﺭ ﺑــﺮﺩﻥ‬
‫‪ Repeater‬ﻣﻲ ﺗﻮﺍﻧﻴﻢ ﻳﻚ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ‪ Ground‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﺳﮕﻤﻨﺖ ﻫﺎ ﺍﺯ ﻳﻜﺪﻳﮕﺮ ﺍﻳﺰﻭﻟﻪ ﻫﺴﺘﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪٢٠‬‬

‫ﺑـﻪ ﺍﻳـﻦ ﻧﻜـﺘﻪ ﺗﻮﺟـﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪، RS485‬ﻫﺮ‪ Repeater‬ﻳﻚ ‪ Load،‬ﺟﺮﻳﺎﻧﻲ ﻣﺤﺴﻮﺏ ﻣﻲ ﺷﻮﺩ ﻭﺩﺭ‬
‫ﻧﺘـﻴﺠﻪ ﺩﺭ ﺷـﻤﺎﺭﺵ ‪ Node‬ﻫﺎ ﺑﺎﻳﺪ ﻣﻨﻈﻮﺭ ﮔﺮﺩﻧﺪ‪.‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻫﺮ‪ Repeater‬ﺍﺯ ﺗﻌﺪﺍﺩ‪ Node‬ﻫﺎﻱ ﻣﺠﺎﺯ ﻳﻚ‬
‫ﻋﺪﺩﻛﺎﺳـﺘﻪ ﻣـﻲ ﺷﻮﺩ‪.‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮﭼﻪ ﺩﺭ ﻳﻚ ﺳﮕﻤﻨﺖ ﻣﻲ ﺗﻮﺍﻧﻴﻢ ﺳﻲ ﻭ ﺩﻭ ‪ Node‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﺍﻣﺎ ﺑﺎ ﺑﻜﺎﺭ ﺑﺮﺩﻥ‬
‫ﻳـﻚ‪، Repeater‬ﺣﺪﺍﻛـﺜﺮ ‪ ٣١‬ﺍﻳﺴـﺘﮕﺎﻩ ﻣـﻲ ﺗﻮﺍﻧـﻨﺪ ﺑﻪ ﺍﻳﻦ ﺳﮕﻤﻨﺖ ﻭﺻﻞ ﺷﻮﻧﺪ ‪.‬ﺩﻗﺖ ﺷﻮﺩ ‪ Repeater‬ﺻﺮﻓﹰﺎ ﺍﺯ ﺍﻳﻦ‬
‫ﺟﻬـﺖ ﻳـﻚ ‪ Node‬ﻣﺤﺴـﻮﺏ ﻣـﻲ ﺷـﻮﺩ ﻛـﻪ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ‪ Load‬ﺟﺮﻳﺎﻧﻲ ﻋﻤﻞ ﻣﻲ ﻛﻨﺪ ﻭﮔﺮﻧﻪ ﺩﺭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺒﻜﻪ‬
‫ﺗﺄﺛﻴﺮﻱ ﻧﺪﺍﺭﺩ ﻭﺑﻪ ﺁﻥ ﺁﺩﺭﺳﻲ ﺗﺨﺼﻴﺺ ﺩﺍﺩﻩ ﻧﻤﻲ ﺷﻮﺩ‪.‬‬
‫‪Stub Line‬‬
‫ﺍﺻﻄﻼﺡ ‪ Stub Line‬ﺑﻪ ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻪ ﻣﺤﻞ ﺍﺗﺼﺎﻝ ﺑﺎﺱ ﻣﻲ ﮔﻮﻳﻨﺪ‪.‬‬
‫ﺩﺭ ﺍﺳـﺘﺎﻧﺪﺍﺭﺩ‪ EN 50 170‬ﺑـﺮﺍﻱ ﺩﺳـﺘﻴﺎﺑﻲ ﺑـﻪ ﺳـﺮﻋﺖ ‪ 1.5Mbps‬ﺗﻨﻬﺎ ﺍﺟﺎﺯﻩ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ Stub Line‬ﺑﺎ ﻃﻮﻝ ﺣﺪﺍﻛﺜﺮ‬
‫‪ 6.6m‬ﺩﺭ ﻳﻚ ﺳﮕﻤﻨﺖ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﺩ‪.‬ﺍﻣﺎ ﺑﻬﺘﺮﻳﻦ ﺣﺎﻟﺖ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺍﺯ‪ Stub Line‬ﺍﺳﺘﻔﺎﺩﻩ ﻧﺸﻮﺩ‪.‬ﺗﻨﻬﺎ ﺍﺳﺘﺜﻨﺎ ‪،‬ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﺍﺯ‪ Stub Line‬ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﻣﻮﻗﺘﻲ ﺩﺳﺘﮕﺎﻫﻬﺎﻱ ‪ Programmer‬ﻣﺜﻞ ‪ PG‬ﻭﻳﺎ ﻭﺳﺎﻳﻞ ﻋﻴﺐ ﻳﺎﺑﻲ ﻣﻲ ﺑﺎﺷﺪ‪.‬‬
‫ﺍﻳـﻨﻜﻪ ﺗﻮﺻـﻴﻪ ﻣـﻲ ﺷﻮﺩ ﺍﺯ ‪ Stub Line‬ﺍﺳﺘﻔﺎﺩﻩ ﻧﺸﻮﺩ ﺑﻪ ﺍﻳﻦ ﻋﻠﺖ ﺍﺳﺖ ﻛﻪ ﺑﺴﺘﻪ ﺑﻪ ﻃﻮﻝ ﻭﺗﻌﺪﺍﺩ ‪ Stub Line‬ﻫﺎ‪،‬ﻣﻴﺰﺍﻥ‬
‫ﺍﻧﻌﻜـﺎﺱ ﻭﺑﺎﺯﮔﺸـﺖ ﺳـﻴﮕﻨﺎﻝ ﺍﻃﻼﻋـﺎﺕ ﻭﺍﻳﺠـﺎﺩ ﺧﻄـﺎ ﺩﺭ ﻃـﻮﻝ ﺳـﮕﻤﻨﺖ ﺑﺎﻻ ﻣﻲ ﺭﻭﺩ ﻭ ﺑﻪ ﻫﻤﻴﻦ ﺩﻟﻴﻞ ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ‬
‫ﺳـﺮﻋﺖ ﻫـﺎﻱ ﺑﺎﻻﺗـﺮ ﺍﺯ ‪ 1.5Mbps‬ﺑـﻪ ﻫـﻴﭻ ﻋـﻨﻮﺍﻥ ‪،‬ﺍﻣﻜـﺎﻥ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ‪ Stub Line‬ﻣﻮﺟـﻮﺩ ﻧﻤـﻲ ﺑﺎﺷﺪ‪.‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ‬
‫ﺗﺠﻬﻴﺰﺍﺕ ﻋﻴﺐ ﻳﺎﺑﻲ ﻳﺎ ‪ Programming‬ﺗﻨﻬﺎ ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﺑﻪ ﺻﻮﺭﺕ ﺍﻳﺴﺘﮕﺎﻩ ‪ Active‬ﺭﺍ ﺩﺍﺭﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢١‬‬ ‫‪PROFIBUS DP‬‬

‫ﺏ ( ﺍﻧﺘﻘﺎﻝ ﺑﺎ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﺩﺭ ﻻﻳﻪ ﻓﻴﺰﻳﻜﻲ ‪ PROFIBUS‬ﺍﻣﻜﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﻜﻨﻮﻟﻮﮊﻱ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪.‬ﺍﻳﻦ ﺭﻭﺵ ﺑﺮ ﺍﺳﺎﺱ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻫﺎﻱ‬
‫‪ PNO‬ﻃﺮﺍﺣـﻲ ﺷـﺪﻩ ﺍﺳـﺖ‪ .‬ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲ ﺳﺎﺯﺩ ﻛﻪ ﻓﺎﺻﻠﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺗﺎ‬
‫‪ 15Km‬ﻫﻢ ﺍﻓﺰﺍﻳﺶ ﻳﺎﺑﺪ ﻧﻮﻳﺰ ﻫﺎﻱ ﺍﻟﻜﺘﺮﻭ ﻣﻐﻨﺎﻃﻴﺴﻲ ﺑﺮ ﺭﻭﻱ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﺍﺛﺮ ﻧﻤﻲ ﻛﻨﻨﺪ ‪ .‬ﻭﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﺷﺒﻜﻪ ﺍﺯ ﻧﻈﺮ‬
‫ﻼ ﺍﺯ ﻳﻜﺪﻳﮕﺮ ﺍﻳﺰﻭﻟﻪ ﻫﺴﺘﻨﺪ‪.‬‬
‫ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ ،‬ﻛﺎﻣ ﹰ‬
‫ﺑـﺎ ﺳـﺎﺩﻩ ﺗـﺮ ﺷﺪﻥ ﻧﺼﺐ ﻭﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺗﺠﻬﻴﺰﺍﺕ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺩﺭ ﺳﺎﻟﻬﺎﻱ ﺍﺧﻴﺮ‪،‬ﺍﻳﻦ ﺭﻭﺵ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺍﺯ ﻣﺤﺒﻮﺑﻴﺖ ﺧﺎﺻﻲ‬
‫ﺑـﺮﺧﻮﺭﺩﺍﺭ ﺷـﺪﻩ ﺍﺳـﺖ‪.‬ﺑﻪ ﺧﺼﻮﺹ ﺗﺠﻬﻴﺰﺍﺕ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﭘﻼﺳﺘﻴﻜﻲ ﻛﻪ ﻧﺴﺒﺖ ﺑﻪ ﻧﻮﻉ ﺷﻴﺸﻪ ﺍﻱ ﺳﺎﺩﻩ ﺗﺮ ﻭﺍﺭﺯﺍﻧﺘﺮ ﺍﺳﺖ‬
‫ﻛﺎﺭﺑـﺮﺩ ﺑﻴﺸـﺘﺮﻱ ﭘـﻴﺪﺍ ﻛـﺮﺩﻩ ﺍﻧﺪ‪.‬ﻛﺎﺑﻞ ﻫﺎﻱ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻣﺸﺘﻤﻞ ﺑﺮ ﻓﻴﺒﺮ ﻫﺎﻱ ﭘﻼﺳﺘﻴﻜﻲ ﻭﺷﻴﺸﻪ ﺍﻱ ‪،‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﺤﻴﻂ ﻫﺎﻱ‬
‫ﺍﻧـﺘﻘﺎﻝ ﺗﻜﻨﻮﻟﻮﮊﻱ ﺍﻧﺘﻘﺎﻝ ﻧﻮﺭﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﻧﺪ‪.‬ﻓﺎﺻﻠﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﻛﻪ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ ﺩﺭ ﻧﻮﻉ‬
‫ﺷﻴﺸﻪ ﺍﻱ ﺗﺎ ‪ 15Km‬ﻭﺩﺭ ﻧﻮﻉ ﭘﻼﺳﺘﻴﻜﻲ ‪ 80m‬ﻣﻲ ﺗﻮﺍﻧﺪ ﺍﻓﺰﺍﻳﺶ ﻳﺎﺑﺪ‪.‬‬
‫ﺭﻭﺵ ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪:‬‬

‫ﺭﻭﺵ ﺍﻭﻝ‪ :‬ﺗﻜﻨﻮﻟﻮﮊﻱ‪OLM‬‬

‫ﻣﺸــﺎﺑﻪ ‪ Repeater‬ﻫﺎﻳــﻲ ﻛــﻪ ﺩﺭ ‪ RS485‬ﺍﺳــﺘﻔﺎﺩﻩ ﻣــﻲ ﺷــﻮﻧﺪ ‪ OLM،‬ﺩﻭ ﻛــﺎﺑﻞ‬
‫ﺍﻟﻜﺘﺮﻳﻜـﻲ ﺍﻳﺰﻭـﻟﻪ ﻭﻳـﻚ ﻳـﺎ ﺩﻭ ﻛﺎﻧـﺎﻝ ﻧﻮﺭﻱ ﺩﺍﺭﺩ‪ OLM.‬ﺍﺯ ﻃﺮﻳﻖ ﺧﻂ ‪ RS485‬ﺑﻪ‬
‫ﺍﻳﺴـﺘﮕﺎﻫﻬﺎﻱ ﺷـﺒﻜﻪ ﻳـﺎ ﺳـﮕﻤﻨﺖ ﻫﺎﻱ ﺍﻟﻜﺘﺮﻳﻜﻲ ﻭﺻﻞ ﻣﻲ ﺷﻮﺩ‪ .‬ﺩﺭ ﻭﺍﻗﻊ ‪ OLM‬ﺩﻭ‬
‫ﻛﺎﺭﺑـﺮﺩ ﻣـﻲ ﺗﻮﺍﻧﺪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ‪.‬ﻳﻜﻲ ﺍﻳﻨﻜﻪ ﺑﻪ ﻋﻨﻮﺍﻥ ‪ Repeater‬ﺩﺭ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬
‫ﺍﺳـﺘﻔﺎﺩﻩ ﺷـﻮﺩ‪ ،‬ﺩﻭﻡ ﺍﻳﻨﻜﻪ ﻣﻴﺘﻮﺍﻧﺪ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﻭﺻﻞ‬
‫ﻛﻨﺪ‪.‬‬
‫ﺩﺭ ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ ﻧﺤﻮﻩ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OLM‬ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺁﻣﺪﻩ‬
‫ﺍﺳﺖ ‪.‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺷﻜﻞ ﻣﻲ ﺑﻴﻨﻴﺪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ Master‬ﻭ ‪ Slave‬ﺑﺎ ﻛﺎﺑﻞ‬
‫ﺍﻟﻜﺘﺮﻳﻜﻲ ﺑﻪ ‪ OLM‬ﻭﺻﻞ ﺷﺪﻩ ﺍﻧﺪ ﻭﺑﻴﻦ ﺧﻮﺩ ‪ OLM‬ﻫﺎ‪ ،‬ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻛﺸﻴﺪﻩ ﺷﺪﻩ‬
‫ﺍﺳﺖ ﻛﻪ ﺑﻪ ﻛﻤﻚ ﺍﻳﻦ ﻧﺤﻮﻩ ﺍﺗﺼﺎﻝ ﺣﺪﺍﻛﺜﺮ ﻓﺎﺻﻠﻪ ﻣﺠﺎﺯ ﺑﻴﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻣﻲ ﺗﻮﺍﻧﺪ‬
‫ﺍﻓﺰﺍﻳﺶ ﻳﺎﺑﺪ ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪٢٢‬‬

‫ﻫﺎﻱ ‪) Ring‬ﺣﻠﻘﻪ( ﻭﺳﺘﺎﺭﻩ)‪ (Star‬ﻭﺩﺭﺧﺖ )‪(Tree‬‬ ‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﻜﻨﻮﻟﻮﮊﻱ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺍﻣﻜﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺗﻮﭘﻮﻟﻮﮊﻱ‬
‫ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬
‫ﻣﺪﻭﻟﻬﺎﻱ ﻧﻮﺭﻱ ﻳﻌﻨﻲ ‪ OLM‬ﻫﺎ ﺩﺭ ﺳﺎﺧﺘﺎﺭ ‪ ، Ring‬ﻫﻢ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﻪ ﺻﻮﺭﺕ ﺗﻚ ﺣﻠﻘﻪ ﺍﻱ ﻭ ﻫﻢ ﺑﻪ ﺻﻮﺭﺕ ﺩﻭ ﺣﻠﻘﻪ‬
‫ﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﻧﺪ‪.‬ﺩﺭ ﺣﺎﻟﺖ ﺩﻭﺣﻠﻘﻪ ﺍﻱ ‪،‬ﻳﻜﻲ ﺍﺯ ﺣﻠﻘﻪ ﻫﺎ ﻋﻤﻠﻜﺮﺩ ‪ Redundant‬ﺩﺍﺭﺩ‪.‬ﺑﻪ ﺍﻳﻦ ﻣﻌﻨﻲ ﻛﻪ ﺍﮔﺮ ﺑﺮﺍﻱ ﻳﻚ‬
‫ﺣﻠﻘﻪ ﻣﺸﻜﻞ ﭘﻴﺶ ﺑﻴﺎﻳﺪ ﺣﻠﻘﻪ ﺩﻳﮕﺮ ﻭﺍﺭﺩ ﻋﻤﻞ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﺗﻮﺟﻪ ﺩﺍﺭﻳﺪ ﻛﻪ ﺩﺭ ﺣﺎﻟﺖ ﺗﻚ ﺣﻠﻘﻪ ﺍﻱ ‪،‬ﺍﮔﺮ ﺑﺮﺍﻱ ﻳﻜﻲ ﺍﺯ ‪ OLM‬ﻫﺎ ﻣﺸﻜﻠﻲ ﭘﻴﺶ ﺑﻴﺎﻳﺪ ﻳﺎ ﺣﻠﻘﻪ ﻗﻄﻊ ﺷﻮﺩ‪،‬ﻛﻞ ﺷﺒﻜﻪ‬
‫ﺍﺯﻛﺎﺭ ﻣﻲ ﺍﻓﺘﺪﻭﻟﻲ ﺩﺭ ﺣﺎﻟﺖ ‪ Redundant‬ﺍﮔﺮ ﺑﺮﺍﻱ ﻳﻜﻲ ﺍﺯ ﺣﻠﻘﻪ ﻫﺎ ﻣﺸﻜﻞ ﭘﻴﺶ ﺑﻴﺎﻳﺪ ‪،‬ﺷﺒﻜﻪ ﺑﻪ ﻛﺎﺭ ﺧﻮﺩﺵ ﺍﺩﺍﻣﻪ‬
‫ﻣﻲ ﺩﻫﺪ‪.‬‬
‫ﺣﺪﺍﻛﺜﺮ ﻃﻮﻝ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺑﺮ ﺍﺳﺎﺱ ﻧﻮﻉ ﺁﻥ ﺩﺭ ﺟﺪﻭﻝ ﺯﻳﺮ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٣‬‬ ‫‪PROFIBUS DP‬‬

‫ﺭﻭﺵ ﺩﻭﻡ ‪:‬ﺗﻜﻨﻮﻟﻮﮊﻱ ‪OLP‬‬

‫‪9-Pin‬‬ ‫‪ OLP‬ﻫـﺎ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ Slave‬ﺩﺭ ﺣﻠﻘﻪ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﻭﺻﻞ ﺷﻮﻧﺪ ‪.‬ﺍﻳﻦ ﻛﺎﺭ ﺍﺯ ﻃﺮﻳﻖ ﻳﻚ ﻛﺎﻧﻜﺘﻮﺭ‬
‫‪ Sub D Plug‬ﺩﺭ ﺍﻳﺴـﺘﮕﺎﻩ ‪ Slave‬ﺻـﻮﺭﺕ ﻣـﻲ ﮔـﻴﺮﺩ‪.‬ﺑـﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻱ ‪ Slave‬ﺑﻪ ﺷﻜﻞ ﻓﻴﺒﺮ‬
‫ﻧـﻮﺭﻱ ﻟﺰﻭﻣﻲ ﺑﻪ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‪ OLM‬ﻧﻴﺴﺖ‪ OLP .‬ﺗﻐﺬﻳﻪ ﺧﻮﺩ ﺭﺍ ﺍﺯ ﻃﺮﻳﻖ ﺑﺎﺱ ﻣﺘﺼﻞ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ‪ Slave‬ﺩﺭﻳﺎﻓﺖ ﻣﻲ ﻛﻨﺪ‬
‫ﻭﻧﻴﺎﺯ ﺑﻪ ﻣﻨﺒﻊ ﺗﻐﺬﻳﻪ ﺟﺪﺍﮔﺎﻧﻪ ﻧﺪﺍﺭﺩ ‪.‬ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻣﻨﺒﻊ ﺗﻐﺬﻳﻪ ‪ +5V‬ﺩﺭ ﻛﺎﺑﻞ ‪ RS 485‬ﺑﺎﻳﺪ ﺗﻮﺍﻥ‬
‫ﺟـﺮﻳﺎﻥ ﺩﻫـﻲ ﺣﺪﺍﻗﻞ ‪ 80mA‬ﺭﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ ﺍﺗﺼﺎﻝ ﺍﻳﺴﺘﮕﺎﻩ ‪ Master‬ﺑﻪ‬
‫ﻳﻚ ﺣﻠﻘﻪ ‪ OLP‬ﺑﻪ ﻳﻚ ﻋﺪﺩ ‪ OLM‬ﻧﻴﺎﺯ ﺩﺍﺭﺩ ﻭ ‪ OLP‬ﺗﻨﻬﺎﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ‪ Slave‬ﺑﻪ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﺭﻭﺵ ﺳﻮﻡ ‪:‬ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ﺑﻪ ‪Intergrated Fiber Optic Connection‬‬

‫ﺑﻌﻀـﻲ ﻭﺳـﺎﻳﻞ ﺑـﻪ ﺻـﻮﺭﺕ ﻣﺴـﺘﻘﻴﻢ ﺍﻣﻜـﺎﻥ ﺍﺗﺼـﺎﻝ ﺑﻪ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺭﺍ‬
‫ﺩﺍﺭﻧـﺪ‪ .‬ﻳﻌﻨـﻲ ﻳـﻚ ﭘـﻮﺭﺕ ﺑـﺮﺍﻱ ﺍﺗﺼﺎﻝ ﺑﻪ ﺷﺒﻜﻪ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺩﺍﺭﻧﺪ ﻛﻪ ﺩﺭ‬
‫ﻧﺘـﻴﺠﻪ ﺑـﺮﺍﻱ ﺍﺗﺼـﺎﻝ ﺑـﻪ ﺷـﺒﻜﻪ ﻓﻴـﺒﺮ ﻧـﻮﺭﻱ ﻧـﻴﺎﺯ ﺑﻪ ‪ OLM‬ﻳﺎ ‪ OLP‬ﻧﺪﺍﺭﻧﺪ‪.‬‬
‫ﻻ ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﻧﺎﻡ ﺍﻳﻦ ﻭﺳﺎﻳﻞ ﻋﺒﺎﺭﺕ ‪ (Fiber Optic) FO‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬
‫ﻣﻌﻤﻮ ﹰ‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪٢٤‬‬

‫‪PROFIBUS DP‬‬ ‫‪ ٣-٣-١‬ﺗﻜﻨﻮﻟﻮﮊﻱ ﺍﺭﺗﺒﺎﻃﺎﺕ ﺩﺭ‬

‫ﺑﺮ ﻃﺒﻖ ﻣﺪﻝ ‪ OSI‬ﻧﺤﻮﻩ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ‪، Bus‬ﺍﻣﻨﻴﺖ ﺩﺍﺩﻩ ﻫﺎ‪ ،‬ﭘﺮﺩﺍﺯﺵ ﻧﻤﻮﺩﻥ ﭘﺮﻭﺗﻜﻞ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺍﺯ ﻃﺮﻳﻖ ﻻﻳﻪ ﺩﻭﻡ ﺍﻧﺠﺎﻡ‬
‫ﻣﻲ ﺷﻮﺩ‪.‬ﺩﺭ‪ PROFIBUS‬ﻻﻳﻪ ﺩﻭﻡ‪ ،‬ﻻﻳﺔ ‪ (FieldBus Data Link) FDL‬ﻧﺎﻣﻴﺪﻩ ﻣﻲ ﺷﻮﺩ ‪.‬ﻓﺮﻣﺖ ﺩﻳﺘﺎ ﺩﺭ ﺍﻳﻦ ﻻﻳﻪ‬
‫‪،‬ﺍﻣﻨﻴﺖ ﺑﺎﻻﻳﻲ ﺭﺍ ﺩﺭ ﺍﻧﺘﻘﺎﻝ ﺁﻥ ﻓﺮﺍﻫﻢ ﻣﻲ ﻛﻨﺪ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﻻﻳﻪ ﻛﻨﺘﺮﻝ ﻓﻠﻮﻱ ﺍﻃﻼﻋﺎﺕ ﻭ ﻛﻨﺘﺮﻝ ﺑﺮﻗﺮﺍﺭﻱ ﺍﺭﺗﺒﺎﻁ ﻭ ﺗﺸﺨﻴﺺ ﺧﻄﺎ ﺗﻮﺳﻂ ‪ Logical Link Control‬ﻳﺎ‬
‫‪ LLC‬ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ‪ .‬ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺑﺎﺱ ‪ ،‬ﭼﺮﺧﺶ ‪ Token‬ﺗﻮﺳﻂ ‪(Medium Access Control) MAC‬‬
‫ﺻﻮﺭﺕ ﻣﻴﮕﻴﺮﺩ‪ .‬ﺑﻪ ﺑﺴﺘﻪ ﺍﻃﻼﻋﺎﺕ ‪ Frame‬ﮔﻔﺘﻪ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﺍﻟﻒ ( ﻓﺮﻣﺖ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﻭ ﺍﻣﻨﻴﺖ ﺁﻥ‬

‫ﻧﺤﻮﻩ ﺁﻏﺎﺯ ﻭﭘﺎﻳﺎﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﻭﻗﺮﺍﺭ ﺩﺍﺩﻥ ﺯﻣﺎﻥ ﻣﻨﺎﺳﺐ ﺑﻴﻦ ﺍﺭﺳﺎﻝ ﺑﺴﺘﻪ ﻫﺎﻱ ﺩﻳﺘﺎ ﻭﺑﻪ ﻛﺎﺭ ﺑﺮﺩﻥ ﺑﻴﺖ ‪ Parity‬ﻭﻛﻨﺘﺮﻝ ﺍﺯ‬
‫ﺟﻤﻠﻪ ﻣﺴﺎﺋﻠﻲ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺗﻌﻴﻴﻦ ﺩﻗﺖ ﻭﺍﻣﻨﻴﺖ ﺩﺍﺩﻩ ﻫﺎ ﻣﺆﺛﺮ ﺍﺳﺖ ‪.‬ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﺩﺭ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﻄﺎﺑﻖ ﺑﺎ‬
‫‪UART‬‬ ‫ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ IEC870-5-1‬ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺍﻧﺪ ﻃﺒﻖ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻓﺮﻳﻢ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺯ ﺗﻌﺪﺍﺩﻱ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺍﺯ ﻧﻮﻉ‬
‫‪ Universal Asynchronous Receiver/Transmitter‬ﺗﺸﻜﻴﻞ ﮔﺮﺩﻳﺪﻩ ﺍﺳﺖ ‪ .‬ﺑﺴﺘﻪ ‪ UART‬ﺑﺼﻮﺭﺕ ﺁﺳﻨﻜﺮﻭﻥ‬
‫ﻭ ﺩﺭ ‪ ۱۱‬ﺑﻴﺖ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٥‬‬ ‫‪PROFIBUS DP‬‬

‫‪ ٨‬ﺑﻴﺖ ﺑﺮﺍﻱ ﺩﻳﺘﺎ‬ ‫•‬

‫ﻳﻚ ﺑﻴﺖ ﻛﻪ ﺷﺮﻭﻉ ﺩﻳﺘﺎ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ‪ Start Bit‬ﻭ ﻫﻤﻴﺸﻪ ‪ 0‬ﺍﺳﺖ‬ ‫•‬

‫ﻳﻚ ﺑﻴﺖ ﻛﻪ ﺍﻧﺘﻬﺎﻱ ﺩﻳﺘﺎ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ‪ Stop Bit‬ﻭ ﻫﻤﻴﺸﻪ ‪ 1‬ﺍﺳﺖ‬ ‫•‬

‫ﻳﻚ ﺑﻴﺖ ﻛﻪ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎﻱ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ‪ Parity Bit‬ﻛﻪ ﺯﻭﺝ ﺑﻮﺩﻥ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎ ﺭﺍ‬ ‫•‬
‫ﭼﻚ ﻣﻴﻜﻨﺪ ‪Parity=0 .‬ﻳﻌﻨﻲ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎ ﺯﻭﺝ ﻭ ‪ Parity=1‬ﻳﻌﻨﻲ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎ ﺯﻭﺝ ﻧﻴﺴﺖ‪.‬‬

‫ﺑﺪﻳﻦ ﺗﺮﺗﻴﺐ ﺑﺮﺍﻱ ﻳﻚ ﻛﺎﺭﺍﻛﺘﺮ ﺑﺎ ﻛﻨﺘﺮﻝ ‪ Even Parity‬ﺍﻣﻜﺎﻥ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﻳﻚ ﺧﻄﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﺍﺻﻄﻼﺣﺎ ﮔﻔﺘﻪ‬
‫ﻣﻴﺸﻮﺩ ﻛﻪ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ‪ HD=2‬ﺍﺳﺖ ﺍﻣﺎ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺧﻮﺍﻫﻴﻢ ﺩﻳﺪ ﻳﻚ ﻓﺮﻳﻢ ﺩﻳﺘﺎ ﺻﺮﻓﹰﺎ ﻣﺘﺸﻜﻞ ﺍﺯ ﻳﻚ ﺑﺴﺘﻪ‬
‫‪ UART‬ﻧﻴﺴﺖ ﺑﻠﻜﻪ ﺩﻳﺘﺎﻫﺎﻱ ﺩﻳﮕﺮﻱ ﻧﻴﺰ ﺑﻪ ﺁﻥ ﺍﺿﺎﻓﻪ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺑﺎ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻦ ﺗﻤﺎﻡ ﺣﺎﻻﺕ ﻣﻤﻜﻦ ‪ ،‬ﻣﺸﺨﺺ ﺷﺪﻩ‬
‫ﺍﺳﺖ ﻛﻪ ﻳﻚ ﻓﺮﻳﻢ ﺍﻃﻼﻋﺎﺗﻲ ﺩﺭ ‪ Profibus‬ﺩﺍﺭﺍﻱ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ‪ HD=4‬ﺍﺳﺖ‪ .‬ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﺗﺎ ‪ ٣‬ﺧﻄﺎﻱ ﻣﺘﻮﺍﻟﻲ ﺭﻭﻱ‬
‫ﺑﻴﺘﻬﺎ ﻗﺎﺑﻞ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﻭ ﻳﻚ ﺧﻄﺎ ﻗﺎﺑﻞ ﺍﺻﻼﺡ ﺍﺳﺖ ﺍﺯﺟﻤﻠﻪ ﺧﻄﺎﻫﺎﻳﻲ ﻛﻪ ﻗﺎﺑﻞ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺍﺳﺖ ﻣﻴﺘﻮﺍﻥ ﺑﻪ‬
‫ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪:‬‬
‫ﺧﻄﺎ ﺩﺭ ﺑﻴﺖ ﻫﺎﻱ ﺷﺮﻭﻉ‬ ‫•‬

‫ﺧﻄﺎ ﺩﺭ ﺑﻴﺖ ﻫﺎﻱ ﭘﺎﻳﺎﻥ‬ ‫•‬

‫ﺧﻄﺎ ﺩﺭ ﺑﻴﺖ ﻫﺎﻱ ‪Parity‬‬ ‫•‬

‫ﺧﻄﺎ ﺩﺭ ﺍﻧﺪﺍﺯﻩ ﻓﺮﻳﻢ‬ ‫•‬

‫)‪(FC‬‬ ‫ﺧﻄﺎ ﺩﺭ ﺑﺎﻳﺖ ﻛﻨﺘﺮﻟﻲ‬ ‫•‬

‫ﺩﺭ ﺻﻮﺭﺕ ﻭﻗﻮﻉ ﺧﻄﺎ ﺍﮔﺮ ﭼﻪ ﻣﻴﺘﻮﺍﻥ ﺗﺎ ﻳﻚ ﺧﻄﺎ ﺭﺍ ﺍﺻﻼﺡ ﻛﺮﺩ ﻭﻟﻲ ﺗﺮﺟﻴﺢ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ ﻛﻪ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﻣﺠﺪﺩﹰﺍ ﺍﺭﺳﺎﻝ‬
‫ﮔﺮﺩﺩ ﻭ ﺑﺼﻮﺭﺕ ﺍﺗﻮﻣﺎﺗﻴﻚ‪ ،‬ﺣﺪﺍﻗﻞ ﻳﻚ ﺑﺎﺭ ﺩﻳﮕﺮ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺍﺭﺳﺎﻝ ﻣﻲ ﺷﻮﺩ ‪.‬ﺗﻜﺮﺍﺭ ﺍﺭﺳﺎﻝ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﻗﺎﺑﻞ ﺗﻨﻈﻴﻢ ﺍﺳﺖ‬
‫ﻭﺣﺪﺍﻛﺜﺮ ﻣﻲ ﺗﻮﺍﻧﺪ ﻣﻘﺪﺍﺭ ‪ ٨‬ﺑﺎﺷﺪ ‪.‬ﺍﻳﻦ ﻣﻘﺪﺍﺭ ﺩﺭﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﺑﻪ ﻋﻨﻮﺍﻥ ‪Retry‬ﻣﻌﺮﻓﻲ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺩﺭ ‪ Setting‬ﻫﺎ‬
‫ﺑﺎﻳﺪ ﺁﻥ ﺭﺍ‪ ،‬ﺑﺮﺍﺑﺮ ﻣﻘﺪﺍﺭ ﻣﻄﻠﻮﺏ ﺗﻨﻈﻴﻢ ﻛﻨﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪٢٦‬‬

‫‪UART‬‬ ‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺕ ﻓﻮﻕ ﺍﻛﻨﻮﻥ ﺑﻪ ﺑﺮﺭﺳﻲ ﺳﺎﺧﺘﺎﺭ ﻓﺮﻳﻢ ﺍﻃﻼﻋﺎﺗﻲ ﻣﻲ ﭘﺮﺩﺍﺯﻳﻢ ‪ .‬ﻫﺮ ﺑﺴﺘﻪ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺯ ﺗﻌﺪﺍﺩﻱ ﺑﺴﺘﻪ‬
‫ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﻭ ﺳﺎﺧﺘﺎﺭﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺩﺍﺭﺩ‪ .‬ﻗﺒﻞ ﺍﺯ ﺍﺭﺳﺎﻝ ﺑﺴﺘﻪ ‪ ،‬ﻋﻤﻞ ﺳﻨﻜﺮﻭﻥ ﺳﺎﺯﻱ ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ‪.‬‬

‫‪SYN‬‬ ‫‪SD‬‬ ‫‪DA‬‬ ‫‪SA‬‬ ‫‪FC‬‬ ‫‪DATA‬‬ ‫‪FCS‬‬ ‫‪ED‬‬

‫‪ : SD‬ﺷﺮﻭﻉ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻭ ﻣﻘﺪﺍﺭ ﺁﻥ ﺛﺎﺑﺖ ﻭ ﺑﺮﺍﺑﺮ ‪ A2‬ﻫﮕﺰ ﺍﺳﺖ‪.‬‬
‫‪ : DA‬ﺁﺩﺭﺱ ﻣﻘﺼﺪ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪ : SA‬ﺁﺩﺭﺱ ﻣﺒﺪﺍ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪ : FC‬ﺑﺎﻳﺖ ﻛﻨﺘﺮﻟﻲ ﺍﺳﺖ‪.‬‬
‫‪ : DATA‬ﺑﺴﺘﻪ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﺑﺎﻳﺪ ﺍﺭﺳﺎﻝ ﺷﻮﺩ‪.‬‬
‫‪ : FCS‬ﻭﻗﺘﻲ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺑﻪ ﭼﻨﺪ ﻗﺴﻤﺖ ﺗﻘﺴﻴﻢ ﺷﺪﻩ ﺑﺎﺷﺪ ‪ FCS‬ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ﻛﻪ ﺍﻳﻦ ﺑﺴﺘﻪ ﭼﻨﺪﻣﻴﻦ ﻗﺴﻤﺖ ﺍﺳﺖ‪.‬‬
‫‪ : ED‬ﭘﺎﻳﺎﻥ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ‪.‬‬
‫ﻓﺮﺳﺘﻨﺪﻩ ﺩﻳﺘﺎ ﺭﺍ ﻣﻄﺎﺑﻖ ﺑﺎ ﺍﻟﮕﻮﻱ ﻓﻮﻕ ﺑﺴﺘﻪ ﺑﻨﺪﻱ ﻛﺮﺩﻩ ﻫﻤﺮﺍﻩ ﺑﺎ ‪ Token‬ﺭﻭﻱ ﺑﺎﺱ ﻗﺮﺍﺭ ﻣﻴﺪﻫﺪ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ ﺩﺭ‬
‫ﺣﻠﻘﻪ ‪ Token‬ﺁﻧﺮﺍ ﺑﺮﺩﺍﺷﺘﻪ ﻭ ﺁﺩﺭﺱ ‪ DA‬ﺭﺍ ﺑﺎ ﺁﺩﺭﺱ ﺧﻮﺩﺵ ﺗﻄﺒﻴﻖ ﻣﻴﺪﻫﺪ ﺍﮔﺮ ﻳﻜﺴﺎﻥ ﺑﻮﺩ ﺑﻘﻴﻪ ﭘﻴﺎﻡ ﺭﺍ ﻧﻴﺰ‬
‫ﺑﺎﺯﮔﺸﺎﻳﻲ ﻣﻴﻜﻨﺪ ﻭ ﺍﮔﺮ ﺁﺩﺭﺱ ﻳﻜﻲ ﻧﺒﻮﺩ ﺁﻧﺮﺍ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ ﺩﺭ ﺣﻠﻘﻪ ‪ Token‬ﻣﻴﻔﺮﺳﺘﺪ ﺍﻳﻦ ﻛﺎﺭ ﺍﺩﺍﻣﻪ ﻣﻲ ﻳﺎﺑﺪ ﺗﺎ‬
‫ﭘﻴﺎﻡ ﺑﻪ ﮔﻴﺮﻧﺪﻩ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﺳﺪ‪ .‬ﮔﻴﺮﻧﺪﻩ ﺁﻧﺮﺍ ﺍﺯ ﺭﻭﻱ ﺍﻟﮕﻮﻱ ﻓﻮﻕ ﺑﺎﺯﮔﺸﺎﻳﻲ ﻛﺮﺩﻩ ﻭ ﺩﻳﺘﺎﻱ ﺍﺻﻠﻲ ﺭﺍ ﺍﺯ ﺑﻘﻴﻪ ﺍﻃﻼﻋﺎﺕ‬
‫ﺟﺪﺍ ﻣﻴﺴﺎﺯﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٧‬‬ ‫‪PROFIBUS DP‬‬

‫ﺏ( ﻧﺤﻮﻩ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺑﺎﺱ‬

‫ﻳﻜـﻲ ﺍﺯ ﻣﻬﻤﺘﺮﻳـﻦ ﻣﺴـﺎﺋﻞ ﺩﺭ ﺷﺒﻜﻪ ﻫﺎﻱ ﺻﻨﻌﺘﻲ ﻭ ﺍﺯ ﺟﻤﻠﻪ ‪ PROFIBUS‬ﻧﺤﻮﻩ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ‪ PLC‬ﻫﺎ ﺑﺎ ﻫﻢ ﻭﻳﺎ ﺑﺎ ‪PC‬‬

‫ﻫﺎﺳـﺖ‪.‬ﺑـﺎﻳﺪ ﻫﺮ‪ Node‬ﻓﺮﺻﺖ ﻛﺎﻓﻲ ﺑﺮﺍﻱ ﺍﻧﺠﺎﻡ ﻛﺎﺭﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ﻭﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎﻫﺎ ﺩﺭﺯﻣﺎﻧﻬﺎﻱ ﻣﻌﻴﻦ ﺭﺍﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬ﺍﻧﺘﻘﺎﻝ‬
‫ﺩﻳـﺘﺎ ﺑﻴـﻦ ‪PLC‬ﻭ‪ PC‬ﻫﺎﻭﻳﺎ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎﺍﺯ ‪ Distributed I/O‬ﻫﺎ ﺑﺎﻳﺪ ﺳﺮﻳﻊ ﻭﺩﻗﻴﻖ ﺑﺎﺷﺪ ﻭﺍﻳﻦ ﻧﻴﺎﺯﻣﻨﺪ ﺗﻌﻴﻴﻦ ﻳﻚ ﭘﺮﻭﺗﻜﻞ‬
‫ﺍﺳـﺖ ﻛـﻪ ﺑﺼـﻮﺭﺕ ﺣﺴـﺎﺏ ﺷـﺪﻩ ﺍﻱ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻗﺮﺍﺭ ﺩﻫﺪ ‪.‬ﺑﻪ ﻧﺤﻮﻱ ﻛﻪ ﺿﻤﻦ ﺍﺳﺘﻔﺎﺩﻩ ﺑﻬﻴﻨﻪ ﺍﺯ ﺑﺎﺱ‬
‫‪،‬ﺗﺪﺍﺧﻠﻲ ﻫﻢ ﺑﻴﻦ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺑﻮﺟﻮﺩ ﻧﻴﺎﻳﺪ‪.‬ﺩﺭ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻧﺤﻮﻩ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ‪ ،‬ﺗﻮﺳﻂ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ‬
‫ﺑــﻪ ﺭﻭﺵ ‪ Hybride‬ﺍﺳــﺖ‪.‬ﺍﻳــﻦ ﺭﻭﺵ ﺗﺮﻛﻴﺒــﻲ ﺍﺳ ـﺖ ﺍﺯ ﺭﻭﺵ‪)Token Pass‬ﺍﺭﺗــﺒﺎﻁ ﺑﻴــﻦ ﭼــﻨﺪ ‪ (Master‬ﻭ ﺭﻭﺵ‬
‫‪) Master-Slave‬ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﻳﻚ ‪ Master‬ﻭ‪Slave‬ﻫﺎﻳﺶ( ﻭ ﻣﻄﺎﺑﻖ ﺑﺎ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ EN 50 170‬ﻣﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﺑﺎ ﺭﻭﺵ ﻫﺎﻱ ﺫﻛﺮ ﺷﺪﻩ ﺩﺭ ﻓﻮﻕ ‪،‬ﺗﺮﻛﻴﺐ ﻫﺎﻱ ﺯﻳﺮ ﺭﺍ ﻣﻲ ﺗﻮﺍﻧﻴﻢ ﺍﻳﺠﺎﺩ ﻛﻨﻴﻢ‪:‬‬
‫ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﭼﻨﺪ ‪) Master‬ﺩﺭ ﺭﻭﺵ ‪( Token Pass‬‬ ‫•‬
‫ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﻫﺮ ‪ Master‬ﺑﺎ ‪ Slave‬ﻫﺎﻳﺶ )ﺭﻭﺵ ‪(Master-Slave‬‬ ‫•‬

‫ﺗﺮﻛﻴﺐ ﺩﻭ ﺭﻭﺵ ﻓﻮﻕ ‪،‬ﻳﻌﻨﻲ ﻫﻢ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ‪ Master‬ﻫﺎ ﻭﻫﻢ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ‪ Master‬ﺑﺎ ‪ Slave‬ﻫﺎﻳﺶ )ﺭﻭﺵ‬ ‫•‬

‫‪.(Hybride‬‬
‫ﺗﺬﻛﺮ ‪ :‬ﻧﺤـﻮﻩ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ ‪،‬ﺑﻪ ﻣﺤﻴﻂ ﺍﻧﺘﻘﺎﻝ ﺑﺴﺘﮕﻲ ﻧﺪﺍﺭﺩ ﻭﻓﺮﻗﻲ ﻧﻤﻲ ﻛﻨﺪ ﻛﻪ ﻣﺤﻴﻂ ﺍﻧﺘﻘﺎﻝ ﻛﺎﺑﻞ ﻣﺴﻲ ﺑﺎﺷﺪ‬
‫ﻳﺎ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS DP‬‬ ‫‪٢٨‬‬

‫ﺍﻧﺘﻘﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺑﻴﻦ ‪ Node‬ﻫﺎ ‪،‬ﻧﻴﺎﺯﻣﻨﺪ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺑﻪ ﻫﺮ ‪ Node‬ﻳﻚ ﺁﺩﺭﺱ ﻳﻜﺘﺎ ﺗﺨﺼﻴﺺ ﺩﻫﻴﻢ ‪.‬ﺁﺩﺭﺱ ﻫﺎﻱ ﻳﻚ‬
‫ﺷـﺒﻜﻪ ‪ PROFIBUS‬ﻣـﻲ ﺗﻮﺍﻧـﻨﺪ ﺑﻴـﻦ ﺻـﻔﺮ ﺗـﺎ ‪ ١٢٦‬ﺗﻌﻴﻴﻦ ﺷﻮﻧﺪ ﻳﻌﻨﻲ ﺣﺪﺍﻛﺜﺮ ﻣﻲ ﺗﻮﺍﻧﻴﻢ ‪ ١٢٧‬ﺍﻳﺴﺘﮕﺎﻩ ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬‬
‫ﺍﮔــﺮ ﺑﺨﻮﺍﻫــﻴﻢ ﺑﻴــﻦ ﻳــﻚ ‪ Master‬ﻭ‪Slave‬ﻫــﺎﻳﺶ ﺍﺭﺗــﺒﺎﻁ ﺑﺮﻗــﺮﺍﺭ ﻛﻨــﻴﻢ ﺑــﺎﻳﺪ ﺍﺯ ﺭﻭﺵ ‪ Master-Slave‬ﺍﺳــﺘﻔﺎﺩﻩ‬
‫ﻧﻤﺎﻳـﻴﻢ‪.‬ﻫﻤـﺎﻧﻄﻮﺭ ﻛـﻪ ﮔﻔـﺘﻪ ﺷـﺪ ﻣﺪﻳﺮﻳـﺖ ﺑﺎﺱ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺑﺮ ﻋﻬﺪﻩ ‪ Master‬ﺍﺳﺖ ﻛﻪ ﺗﻌﻴﻴﻦ ﻣﻲ ﻛﻨﺪ ﻛﺪﺍﻡ ‪Slave‬‬

‫ﺍﻃﻼﻋـﺎﺕ ﺭﺍ ﺭﻭﻱ ﺑﺎﺱ ﺑﮕﺬﺍﺭﺩ ﻳﺎ ﺍﺯ ﺭﻭﻱ ﺑﺎﺱ ﺑﺨﻮﺍﻧﺪ‪.‬ﺩﺭ ﻭﺍﻗﻊ ﺑﺎ ﺑﺮﻗﺮﺍﺭﻱ ﺍﺭﺗﺒﺎﻁ ﺭﺋﻴﺲ ﻭ ﻣﺮﺋﻮﺱ ‪،‬ﺗﻀﻤﻴﻦ ﻧﻤﻮﺩﻩ ﺍﻳﻢ‬
‫ﻛﻪ ﻫﻴﭽﮕﺎﻩ ﺗﺪﺍﺧﻞ ﺍﻃﻼﻋﺎﺕ ﺭﻭﻱ ﺑﺎﺱ ﺑﻪ ﻭﺟﻮﺩ ﻧﻤﻲ ﺁﻳﺪ‪.‬‬
‫ﺍﮔﺮ ﺑﺨﻮﺍﻫﻴﻢ ﺑﻴﻦ ﭼﻨﺪ ‪ Master‬ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻛﻨﻴﻢ ﺍﺯ ﺭﻭﺵ ‪ Token Pass‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻳﻚ ﺣﻠﻘﻪ‬
‫ﻣﻨﻄﻘـﻲ )ﻭﻧـﻪ ﻓﻴﺰﻳﻜﻲ( ﺑﻴﻦ ‪ Node‬ﻫﺎ ﺑﺮﻗﺮﺍﺭ ﻣﻲ ﺷﻮﺩ‪.‬ﺟﻬﺖ ﺣﻠﻘﻪ ﺑﺮ ﻃﺒﻖ ﺁﺩﺭﺱ ‪ Node‬ﻫﺎ ﺍﺯ ﺁﺩﺭﺱ ﻛﻤﺘﺮ ﺑﻪ ﺁﺩﺭﺱ‬
‫ﺑﻴﺸـﺘﺮ ﺍﺳـﺖ ‪ Node.‬ﻫـﺎﻱ ﺗﺸـﻜﻴﻞ ﺩﻫـﻨﺪﻩ ﺍﻳـﻦ ﺣﻠﻘـﻪ ‪،‬ﺍﻳﺴـﺘﮕﺎﻫﻬﺎﻱ ‪ Master‬ﻫﺴـﺘﻨﺪ ﻭ ‪ Token‬ﺍﺯ ﻳﻚ ‪ Master‬ﺑﻪ‬
‫‪ Master‬ﺑﺎ ﺁﺩﺭﺱ ﺑﺎﻻﺗﺮ ﻣﻨﺘﻘﻞ ﻣﻲ ﺷﻮﺩ‪ .‬ﻭﺍﺿﺢ ﺍﺳﺖ ﻛﻪ ﺯﻣﺎﻧﻲ ﻛﻪ ‪ Token‬ﺑﻪ ‪ Master‬ﺑﺎ ﺑﺎﻻﺗﺮﻳﻦ ﺁﺩﺭﺱ ﺑﺮﺳﺪ‪،‬ﺁﻥ‬
‫ﺭﺍ ﺑﻪ ‪ Master‬ﺑﺎ ﭘﺎﻳﻴﻦ ﺗﺮﻳﻦ ﺁﺩﺭﺱ ﻣﻨﺘﻘﻞ ﻣﻲ ﻛﻨﺪ ﻭﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﻳﻚ ﺣﻠﻘﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺗﺸﻜﻴﻞ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﻫﻤـﺎﻧﻄﻮﺭ ﻛـﻪ ﺩﺭ ﺷـﻜﻞ ﺩﻳـﺪﻩ ﻣﻴﺸﻮﺩ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﺩﺍﺭﺍﻱ ﻳﻚ ﻟﻴﺴﺖ ‪ LAS‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺁﻥ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﻣﺸﺨﺺ ﺷﺪﻩ‬
‫ﺍﺳﺖ‪:‬‬
‫‪Token‬‬ ‫‪ : NS‬ﺁﺩﺭﺱ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ)‪ (Next Station‬ﺩﺭ ﺣﻠﻘﻪ‬ ‫•‬
‫‪Token‬‬ ‫‪ : PS‬ﺁﺩﺭﺱ ﺍﻳﺴﺘﮕﺎﻩ ﻗﺒﻠﻲ)‪ (Previous Station‬ﺩﺭ ﺣﻠﻘﻪ‬ ‫•‬
‫‪Token‬‬ ‫‪ : TS‬ﺁﺩﺭﺱ ﺍﻳﺴﺘﮕﺎﻩ ﻓﻌﻠﻲ)‪ (This Station‬ﺩﺭ ﺣﻠﻘﻪ‬ ‫•‬
‫ﺑﺮ ﺍﺳﺎﺱ ﺍﻳﻦ ﻟﻴﺴﺖ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻴﺪﺍﻧﺪ ‪ Token‬ﺭﺍ ﺍﺯ ﭼﻪ ﺍﻳﺴﺘﮕﺎﻫﻲ ﺑﮕﻴﺮﺩ ﻭ ﺑﻪ ﭼﻪ ﺍﻳﺴﺘﮕﺎﻫﻲ ﺑﻔﺮﺳﺘﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٩‬‬ ‫‪PROFIBUS DP‬‬

‫ﻓﺮﻳﻢ ‪Token‬‬
‫ﺳﺎﺧﺘﺎﺭ ‪ Token‬ﺩﺭ ‪ Profibus‬ﺑﺼﻮﺭﺕ ﺷﻜﻞ ﺯﻳﺮ ﻭ ﻣﺘﺸﻜﻞ ﺍﺯ ‪ ۳‬ﻗﺴﻤﺖ ﺍﺳﺖ‪:‬‬
‫‪SD‬‬ ‫‪DA‬‬ ‫‪SA‬‬

‫‪ : SD‬ﺷﺮﻭﻉ ﺍﺭﺳﺎﻝ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻭ ﻣﻘﺪﺍﺭ ﺁﻥ ‪ DC‬ﻫﮕﺰ ﺍﺳﺖ‪.‬‬

‫‪ : DA‬ﺁﺩﺭﺱ ﻣﻘﺼﺪ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻳﻌﻨﻲ ‪NS‬‬

‫‪ : SA‬ﺁﺩﺭﺱ ﻣﺒﺪﺍ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻳﻌﻨﻲ ‪TS‬‬

‫ﻭﻗﺘﻲ ﺍﻳﺴﺘﮕﺎﻩ ﻓﻌﻠﻲ )‪(TS‬ﺩﻳﺘﺎﻳﻲ ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ﻧﺪﺍﺭﺩ ‪ Token‬ﺭﺍ ﺗﺤﻮﻳﻞ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ )‪ (NS‬ﻣﻴﺪﻫﺪ‪ .‬ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ‬
‫ﺩﺭﻳﺎﻓﺖ ‪ Token‬ﺭﺍ ‪ Acknowledge‬ﻣﻴﻜﻨﺪ‪ .‬ﺍﮔﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻓﻌﻠﻲ ﭘﺲ ﺍﺯ ﺩﻭ ﺑﺎﺭ ﺍﺭﺳﺎﻝ ‪ Token‬ﺍﺯ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ‬
‫ﺗﺎﻳﻴﺪﻳﻪ ﺩﺭﻳﺎﻓﺖ ﻧﻜﺮﺩ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ‪ NS‬ﺭﺍ ﺍﺯ ﻟﻴﺴﺖ ‪ LAS‬ﺧﻮﺩ ﺣﺬﻑ ﻛﺮﺩﻩ ﻭ ‪ Token‬ﺭﺍ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪ ﺗﺮ‬
‫ﻣﻴﻔﺮﺳﺘﺪ‪.‬ﺑﺎ ﺍﻃﻼﻋﺎﺕ ﻓﻮﻕ ﭼﺮﺧﺶ ‪ Token‬ﺩﺭ ﺣﻠﻘﻪ ﻣﻨﻄﻘﻲ ﺑﺮﺍﺣﺘﻲ ﺍﻧﺠﺎﻡ ﻣﻴﮕﻴﺮﺩ‪ .‬ﻻﺯﻡ ﺑﺬﻛﺮ ﺍﺳﺖ ﺍﮔﺮ ﺳﻴﺴﺘﻢ‬
‫‪TS=NS=PS‬‬ ‫‪ monoMaster‬ﺑﺎﺷﺪ ﭘﺮﭼﻢ ‪ Token‬ﻣﺮﺗﺒﺎ ﺑﻪ ﺧﻮﺩ ﻫﻤﺎﻥ ‪ Master‬ﺑﺮﮔﺮﺩﺍﻧﺪﻩ ﻣﻴﺸﻮﺩ ‪ .‬ﺑﻌﺒﺎﺭﺕ ﺩﻳﮕﺮ‬
‫ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻣﺪﺕ ﺯﻣﺎﻧﻲ ﻛﻪ ﻃﻮﻝ ﻣﻲ ﻛﺸﺪ ﺗﺎ ‪ Token‬ﺣﻠﻘﻪ ﺭﺍ ﺩﻭﺭ ﺯﻧﺪ ﻭﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻫﻤﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻗﺮﺍﺭ ﮔﻴﺮﺩ‬
‫‪Token Rotation Time‬ﻧﺎﻣﻴﺪﻩ ﻣﻲ ﺷﻮﺩ‪.‬ﻣﺎﻛﺰﻳﻤﻢ ﺯﻣﺎﻧﻲ ﻛﻪ‪ Token Rotation Time‬ﻣﻲ ﺗﻮﺍﻧﺪ ﻃﻮﻝ ﺑﻜﺸﺪ ‪،‬‬
‫‪ (Time Target Rotation) Ttr‬ﻧﺎﻣﻴﺪﻩ ﻣﻲ ﺷﻮﺩﻛﻪ ﺍﻳﻦ ﺯﻣﺎﻥ ﻗﺎﺑﻞ ﺗﻨﻈﻴﻢ ﺍﺳﺖ ‪.‬ﻫﻤﭽﻨﻴﻦ ﻣﺎﻛﺰﻳﻤﻢ ﺯﻣﺎﻧﻲ ﻛﻪ ‪Token‬‬

‫ﺑﻪ ﺻﻮﺭﺕ ﺍﺗﻮﻣﺎﺗﻴﻚ ﭘﺲ ﺍﺯ ‪ Configure‬ﻧﻤﻮﺩﻥ ﺳﻴﺴﺘﻢ‪،‬ﺑﺮﺍﻱ ﺍﻳﺴﺘﮕﺎﻩ ﻫﺎﻱ ‪ Master‬ﺑﻪ ﻭﺟﻮﺩ ﻣﻲ ﺁﻳﺪ ﻭﺑﻪ ﺻﻮﺭﺕ‬
‫)‪(List Of Active Stations‬‬ ‫ﺧﻮﺩﻛﺎﺭ ‪،‬ﺁﺩﺭﺱ ﻫﺮ ‪ Node‬ﺩﺭ ﺣﻠﻘﻪ ‪ Token‬ﺗﻌﻴﻴﻦ ﻣﻲ ﺷﻮﺩ ‪.‬ﺍﻳﻦ ﺁﺩﺭﺳﻬﺎ ﺩﺭ ﻗﺴﻤﺖ‬
‫‪ LAS‬ﻗﺮﺍﺭ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS FMS‬‬ ‫‪٣٠‬‬

‫‪PROFIBUS FMS‬‬ ‫‪٤-١‬‬

‫‪ (Field Message Specification) FMS‬ﻻﻳﻪ ﻫﺎﻱ ‪۱‬ﻭ‪۲‬ﻭ‪ ۷‬ﻣﺪﻝ ‪ OSI‬ﺭﺍ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﺪ ‪ .‬ﺩﺭ ﻻﻳﻪ‬
‫‪، Application‬ﺳﺮﻭﻳﺲ ‪ FMS‬ﺑﻪ ﻛﺎﺭ ﻣﻴﺮﻭﺩ‪ .‬ﺳﺮﻭﻳﺲ ﻗﺪﺭﺗﻤﻨﺪ ‪ FMS‬ﺩﺭ ﺭﻧﺞ ﻭﺳﻴﻌﻲ ﺍﺯ ﻛﺎﺭﺑﺮﺩﻫﺎ ‪،‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ‬
‫ﻭﺑﻪ ﺧﺼﻮﺹ ﺯﻣﺎﻧﻲ ﻛﻪ ﺍﺭﺗﺒﺎﻃﺎﺕ ﭘﻴﭽﻴﺪﻩ ﺍﻱ ﺩﺭ ﺷﺒﻜﻪ ﺑﺮﻗﺮﺍﺭ ﺑﺎﺷﺪ ‪،‬ﺳﺮﻭﻳﺲ ‪ FMS‬ﻣﻲ ﺗﻮﺍﻧﺪ ﮔﺰﻳﻨﻪ ﻣﻨﺎﺳﺒﻲ ﺑﺎﺷﺪ‪.‬‬

‫)‪Application Layer Interface (ALI‬‬

‫)‪Application Layer (7‬‬

‫)‪Field Message Spec (FMS‬‬

‫‪Layer 3 to 6 Not Used‬‬

‫)‪Data Link Layer (2‬‬

‫)‪Fieldbus Data Link (FDL‬‬
‫)‪Physical Layer (1‬‬

‫ﻣﺤﻴﻂ ﺍﻧﺘﻘﺎﻝ ﻭﻧﺤﻮﻩ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ ﺩﺭ ‪ FMS‬ﻭ‪ DP‬ﻳﻜﺴﺎﻥ ﻣﻲ ﺑﺎﺷﺪ ﺍﺯ ﺍﻳﻨﺮﻭ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﻪ ﻃﻮﺭ ﻫﻤﺰﻣﺎﻥ ﺩﺭ‬
‫ﻳﻚ ﺷﺒﻜﻪ ﻗﺮﺍﺭ ﮔﻴﺮﻧﺪ ‪ .‬ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﻭﻳﮋﮔﻴﻬﺎﻱ ﻣﻬﻢ ‪ FMS‬ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ‪:‬‬
‫ﺭﻭﺵ ﺍﻧﺘﻘﺎﻝ ‪ :‬ﻛﺎﺑﻞ ﻣﺴﻲ ) ﺑﺎ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ RS485‬ﻭ ﺑﺎ ﺳﺮﻋﺖ ﺣﺪﺍﻛﺜﺮ ‪ (1500Kbps‬ﻳﺎ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬ ‫•‬

‫ﻻﻳﻪ ﻫﺎﻱ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ‪ :‬ﻻﻳﻪ ‪ ١‬ﻭ ‪٢‬ﻭ ‪٧‬‬ ‫•‬

‫‪Token Pass‬‬ ‫ﺭﻭﺵ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺑﺎﺱ ‪:‬‬ ‫•‬

‫ﺳﻴﮕﻨﺎﻟﻴﻨﮓ ‪ :‬ﺁﺳﻨﻜﺮﻭﻥ ﺑﺎ ﺑﺴﺘﻪ ﻫﺎﻱ ‪ ١١‬ﺑﻴﺘﻲ ‪ ) UART‬ﻣﺸﺎﺑﻪ ‪(DP‬‬ ‫•‬

‫‪SRD‬‬ ‫ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ‪ SDA :‬ﻭ ‪ SDN‬ﻭ‬ ‫•‬

‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺕ ﻣﻔﺼﻠﻲ ﻛﻪ ﺩﺭ ﻗﺴﻤﺖ ﻗﺒﻞ ﺭﺍﺟﻊ ﺑﻪ ﻣﻔﺎﻫﻴﻢ ﻓﻮﻕ ﺩﺍﺩﻩ ﺷﺪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺗﻜﺮﺍﺭ ﺁﻧﻬﺎ ﺑﺮﺍﻱ ‪ FMS‬ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ‪.‬‬
‫ﻻ ﺳﺮﻭﻳﺲ ‪ FMS‬ﺭﺍ ﺑﺮﺍﻱ ﺣﺎﻟﺘﻲ ﻛﻪ ﺣﺠﻢ ﺍﻃﻼﻋﺎﺕ ﺑﺎﻻﺳﺖ ﺑﻪ ﻛﺎﺭ ﻣﻲ ﮔﻴﺮﻧﺪ ﻭ ﺟﺎﻳﮕﺎﻩ ﺁﻥ ﺩﺭ ﻫﺮﻡ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ‬
‫ﻣﻌﻤﻮ ﹰ‬
‫ﺑﻴﺸﺘﺮ ﺩﺭ ﺳﻄﺢ ‪ Process‬ﺍﺳﺖ‪ .‬ﺍﻣﺮﻭﺯﻩ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺭﺷﺪ ﺳﺮﻳﻊ ‪ (Industrial Ethernet)IE‬ﻣﻌﻤﻮ ﹰ‬
‫ﻻ ﺩﺭ ﺍﻳﻦ ﺳﻄﺢ ﺑﻪ‬
‫ﺟﺎﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺮﻭﻳﺲ ‪ FMS‬ﺍﺯ ‪ IE‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ ﻭﺩﺭ ﻧﺘﻴﺠﻪ ﺳﺮﻭﻳﺲ ‪ FMS‬ﻛﺎﺭﺑﺮﺩ ﻣﺤﺪﻭﺩﺗﺮﻱ ﭘﻴﺪﺍ ﻛﺮﺩﻩ‬
‫ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٣١‬‬ ‫‪PROFIBUS PA‬‬

‫‪PROFIBUS PA‬‬ ‫‪٥-١‬‬

‫ﻻ ﺑﺮﺍﻱ ﺳﻄﺢ ‪ Fleld‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ‬
‫‪ PROFIBUS PA‬ﺩﺭ ﻭﺍﻗﻊ ﻳﻚ ﻧﻤﻮﻧﻪ ﺗﻜﺎﻣﻞ ﻳﺎﻓﺘﻪ ‪ PROFIBUS DP‬ﺍﺳﺖ ﻭﻣﻌﻤﻮ ﹰ‬
‫ﺷﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪،‬ﺗﻜﻨﻴﻚ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺑﺮﺍﺳﺎﺱ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ IEC 1158-2‬ﻣﻲ ﺑﺎﺷﺪ ﻭﺩﺭ ﻧﺘﻴﺠﻪ ﺑﻪ ﺻﻮﺭﺕ ﺫﺍﺗﻲ ﺩﺭ ﺍﻳﻦ‬
‫ﺭﻭﺵ ﻳﻚ ﺍﻳﻤﻨﻲ ﺑﺎﻻ ﺑﻪ ﺩﺳﺖ ﻣﻲ ﺁﻳﺪﭼﻮﻥ ﺗﻐﺬﻳﻪ ﻋﻨﺎﺻﺮ ﻣﺘﺼﻞ ﺑﻪ ﺍﻳﻦ ﺷﺒﻜﻪ ﻣﺴﺘﻘﻴﻤﹰﺎ ﺍﺯ ﻃﺮﻳﻖ ﺧﻂ ﺍﺭﺗﺒﺎﻃﻲ ﺗﺎﻣﻴﻦ‬
‫ﻣﻴﮕﺮﺩﺩ‪.‬‬

‫ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺑﺮ ﺍﺳﺎﺱ ﭘﺮﻭﺗﻜﻞ ‪ Manchester Coding‬ﺻﻮﺭﺕ ﻣﻴﮕﻴﺮﺩ ﻛﻪ ﺳﻄﺢ ‪ DC‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﻧﺪﺍﺭﺩ ﺍﻳﻦ ﺭﻭﺵ‬
‫‪ MBP‬ﺑﻴﺖ‪0‬‬ ‫ﺑﻪ ‪ MBP‬ﻳﺎ ‪ Manchester Coded Bus Powered‬ﻣﻮﺳﻮﻡ ﻭﻧﺎﻡ ﺩﻳﮕﺮ ﺁﻥ ‪ H1‬ﺍﺳﺖ ‪.‬ﺩﺭ ﭘﺮﻭﺗﻜﻞ‬
‫ﺯﻣﺎﻧﻲ ﺭﺥ ﻣﻴﺪﻫﺪ ﻛﻪ ﻟﺒﻪ ﺑﺎﻻ ﺭﻭﻧﺪﻩ ﺳﻴﮕﻨﺎﻝ ﺟﺮﻳﺎﻧﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ‪.‬ﻭﺑﻴﺖ ‪1‬ﺯﻣﺎﻧﻲ ﺭﺥ ﻣﻲ ﺩﻫﺪ ﻛﻪ ﻟﺒﻪ ﭘﺎﻳﻴﻦ ﺭﻭﻧﺪﻩ‬
‫ﺳﻴﮕﻨﺎﻝ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ‪:‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS PA‬‬ ‫‪٣٢‬‬

‫ﻧﺤـﻮﻩ ﺍﻧـﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺑﻪ ﺍﻳﻦ ﺻﻮﺭﺕ ﺍﺳﺖ ﻛﻪ ﺳﻄﺢ ﺻﻔﺮ ﻭﻳﻚ ﺑﺼﻮﺭﺕ ‪ ±9MA‬ﺑﺮ ﺭﻭﻱ ﺟﺮﻳﺎﻥ ﺑﺎﺱ )‪ (IB‬ﻣﺪﻭﻟﻪ ﻣﻲ‬
‫ﺷﻮﻧﺪ‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺛﺎﺑﺖ ﻭ ﺑﺮﺍﺑﺮ ‪ 31.25kbps‬ﻣﻲ ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﺑﻪ ﻃﻮﻝ ﻛﺎﺑﻞ ﺑﺴﺘﮕﻲ ﻧﺪﺍﺭﺩ ‪.‬ﻣﺤﻴﻂ ﺍﻧﺘﻘﺎﻝ‬
‫ﻣﻴﺘﻮﺍﻧﺪ ﻳﻚ ﻛﺎﺑﻞ ‪ Twisted Pair‬ﺍﺯ ﻧﻮﻉ ﺷﻴﻠﺪ ﺩﺍﺭ )‪ (STP‬ﻳﺎ ﺑﺪﻭﻥ ﺷﻴﻠﺪ )‪ (UTP‬ﺑﺎﺷﺪ‪ .‬ﻣﺸﺨﺼﺎﺕ ﻓﻴﺰﻳﻜﻲ ﻭ‬
‫ﺍﻟﻜﺘﺮﻳﻜﻲ ﺗﻨﻬﺎ ﺑﺮﺍﻱ ﭼﻨﺪ ﻧﻮﻉ ﻛﺎﺑﻞ ﺗﻮﺳﻂ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ DIN 61158-2‬ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺍﻳﻦ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺑﺮﺍﻱ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS PA‬ﻛﺎﺑﻞ ﻫﺎﻱ ﻧﻮﻉ ‪ A‬ﺗﺎ ‪ D‬ﺭﺍ ﭘﻴﺸﻨﻬﺎﺩ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﻣﺸﺨﺼﺎﺕ ﺁﻧﻬﺎ ﺩﺭ ﺟﺪﻭﻝ ﺁﻣﺪﻩ ﺍﺳﺖ ‪.‬‬

‫‪Type A‬‬ ‫‪Type B‬‬ ‫‪Type C‬‬ ‫‪Type D‬‬

‫‪cable design‬‬ ‫‪twisted wire‬‬ ‫‪individual or‬‬ ‫‪several‬‬ ‫‪several not twisted‬‬
‫‪pair,‬‬ ‫‪several twisted‬‬ ‫‪twisted wire‬‬ ‫‪lines, not‬‬
‫‪shielded‬‬ ‫‪wire pairs totally‬‬ ‫‪pairs, not‬‬ ‫‪shielded‬‬
‫‪shielded‬‬ ‫‪shielded‬‬
‫‪wire diameter‬‬ ‫‪0.8 mm2‬‬ ‫‪0.32 mm2‬‬ ‫‪0.13 mm2‬‬ ‫‪1.25 mm2‬‬
‫)‪(AWG 18‬‬ ‫)‪(AWG 22‬‬ ‫)‪(AWG 26‬‬ ‫)‪(AWG 16‬‬

‫‪cable length‬‬ ‫‪1900 m‬‬ ‫‪1200 m‬‬ ‫‪400 m‬‬ ‫‪200 m‬‬
‫‪incl. stub lines‬‬

‫ﻻ ﻳﻚ ﻣﺪﺍﺭ ‪ RC‬ﺑﻌﻨﻮﺍﻥ ‪ Terminator‬ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﻨﺪ‪.‬‬

‫ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎﻱ ﺧﻂ ﺍﻧﺘﻘﺎﻝ ﻣﻌﻤﻮ ﹰ‬
‫‪Techno-Electro.com‬‬

‫‪٣٣‬‬ ‫‪PROFIBUS PA‬‬

‫ﺩﺭ ﺷـﺒﻜﻪ ‪ PROFIBUS PA‬ﺍﻣﻜـﺎﻥ ﺍﺳـﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﺧﺘﺎﺭﻫﺎﻱ ‪ Tree ،Star،.Bus‬ﻭﻳﺎ ﺗﺮﻛﻴﺒﻲ ﺍﺯ ﺁﻧﻬﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﺑﺮﺍﻱ‬
‫ﺍﻓـﺰﺍﻳﺶ ﺗﻮﺍﻧﺎﻳـﻲ ﺳﻴﺴـﺘﻢ ﺍﻣﻜﺎﻥ ﺍﻳﺠﺎﺩ ﻳﻚ ﺳﻴﺴﺘﻢ ‪ Redundant‬ﻧﻴﺰ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬ﺩﺭ ﺣﺎﻟﺖ ﺳﺘﺎﺭﻩ ﻭ ﺩﺭﺧﺘﻲ ﺑﺎﻳﺪ ﺗﻮﺟﻪ‬
‫ﺩﺍﺷﺖ ﻛﻪ ﻃﻮﻝ ﻛﺎﺑﻞ ‪ Stub Line‬ﺑﺎﻳﺪ ﻛﻤﺘﺮ ﺍﺯ ‪ ۳۰‬ﻣﺘﺮ ﺑﺎﺷﺪ‪.‬‬
‫ﺣﺪﺍﻛﺜﺮ ﺗﻌﺪﺍﺩ ‪ Node‬ﻫﺎ ﻛﻪ ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﺑﻪ ﻳﻚ ﺳﮕﻤﻨﺖ ‪ PA‬ﺭﺍ ﺩﺍﺭﻧﺪ ﺑﻪ ﻣﻨﺒﻊ ﺗﻐﺬﻳﻪ ﺑﺎﺱ‪ ،‬ﺟﺮﻳﺎﻥ ﻣﺼﺮﻓﻲ ‪ Node‬ﻫﺎ‬
‫ﻭﻃـﻮﻝ ﻭﺟـﻨﺲ ﻛـﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﺷﺪﻩ ﺑﺴﺘﮕﻲ ﺩﺍﺭﺩ‪.‬ﺩﺭ ﺑﻴﺸﺘﺮﻳﻦ ﺣﺎﻟﺖ ‪ ۳۲،‬ﺍﻳﺴﺘﮕﺎﻩ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻪ ﻳﻚ ﺳﮕﻤﻨﺖ ‪ PA‬ﻭﺻﻞ‬
‫ﺷﻮﻧﺪ‪.‬ﺗﻌﺪﺍﺩ ﻣﺎﻛﺰﻳﻤﻢ ﺑﺎﻳﺪ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﻣﺤﺪﻭﺩﻳﺘﻬﺎﻱ ﺯﻳﺮ ﻣﺤﺎﺳﺒﻪ ﺷﻮﺩ‪:‬‬
‫ﻣﺤﺪﻭﺩﻳﺖ ﻫﺎ ﺩﺭ ﻣﺤﻴﻂ ‪EEx ib‬‬ ‫ﻣﺤﺪﻭﺩﻳﺖ ﻫﺎ ﺩﺭ ﻣﺤﻴﻂ ‪EEx ia‬‬
‫‪Us=14 to 24 V‬‬ ‫‪Us=14 to 20 V‬‬
‫‪Ia=250 mA‬‬ ‫‪Ia=110 mA‬‬
‫‪P=4.2 W‬‬ ‫‪P=1.8 W‬‬
‫ﺑﻌـﻨﻮﺍﻥ ﻣﺜﺎﻝ ﻓﺮﺽ ﻛﻨﻴﺪ ﺳﻴﺴﺘﻤﻲ ﻣﺘﺸﻜﻞ ﺍﺯ ﺗﻌﺪﺍﺩﻱ ‪ Slave‬ﻣﺸﺎﺑﻪ ‪ ،‬ﻗﺮﺍﺭ ﺍﺳﺖ ﺩﺭ ﻣﺤﻴﻂ ‪ EEx ia‬ﺑﻜﺎﺭ ﮔﺮﻓﺘﻪ ﺷﻮﺩ‬
‫ﺍﮔﺮ ﺟﺮﻳﺎﻥ ﻣﺼﺮﻓﻲ ﻫﺮ ‪ Slave‬ﺑﺮﺍﺑﺮ ﺑﺎ ‪ ١٠‬ﻣﻴﻠﻲ ﺁﻣﭙﺮ ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ﺍﺯ ﺭﺍﺑﻄﻪ ﺯﻳﺮ ﺗﻌﺪﺍﺩ ‪ Node‬ﻫﺎ ﺑﺪﺳﺖ ﻣﻴﺂﻳﺪ‪.‬‬
‫ﻣﺎﻛﺰﻳﻤﻢ ﺟﺮﻳﺎﻥ ﻣﺠﺎﺯ = )ﺗﻌﺪﺍﺩ ‪) x (Slave‬ﺟﺮﻳﺎﻥ ‪ + (Slave‬ﺟﺮﻳﺎﻥ ﺳﻴﮕﻨﺎﻝ ﻣﻨﭽﺴﺘﺮ‬
‫‪٩‬‬ ‫‪+‬‬ ‫‪) = ١١٠‬ﺗﻌﺪﺍﺩ ‪(١٠) x (Slave‬‬
‫ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﻣﺎﻛﺰﻳﻤﻢ ﺗﻌﺪﺍﺩ ‪ Slave‬ﺑﺮﺍﺑﺮ ﺑﺎ ‪ ١٠‬ﺑﺪﺳﺖ ﻣﻲ ﺁﻳﺪ‪ .‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺍﮔﺮ ﺟﺮﻳﺎﻥ ‪ Slave‬ﻫﺎ ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﺪ ﺑﺎﻳﺪ‬
‫ﺳﻴﮕﻤﺎ ﺑﻜﺎﺭ ﺑﺮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS PA‬‬ ‫‪٣٤‬‬

‫ﻣﻴـﺘﻮﺍﻥ ‪ PROFIBUS PA‬ﺭﺍ ﺍﺯ ﻃـﺮﻳﻖ ﻛﻮﭘﻠـﺮ ﺑﻪ ‪ PROFIBUS DP‬ﻭﺻﻞ ﻛﺮﺩ‪.‬ﻣﻤﻜﻦ ﺍﺳﺖ ﻋﻤﻼ ﺍﻳﻦ ﻧﻴﺎﺯ ﻭﺟﻮﺩ‬
‫ﺩﺍﺷـﺘﻪ ﺑﺎﺷـﺪ ﺗـﺎ ﺩﻳﺘﺎ ﺍﺯ ﺷﺒﻜﻪ ‪ PA‬ﺑﻪ ‪ DP‬ﻳﺎ ﺑﺮ ﻋﻜﺲ ﻣﻨﺘﻘﻞ ﺷﻮﺩ ‪.‬ﺍﺯ ﺁﻧﺠﺎ ﻛﻪ ﭘﺮﻭﺗﻜﻞ ﺍﺭﺗﺒﺎﻃﻲ ﺍﻳﻨﺪﻭ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ‬
‫ﻧـﻴﺎﺯ ﺑـﻪ ﻭﺍﺳـﻄﻪ ﺍﻱ ﺑـﻪ ﻧـﺎﻡ ﻛﻮﭘﻠـﺮ ﺩﺍﺭﻳﻢ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬ﻧﻜﺘﻪ ﺍﻱ ﻛﻪ ﺑﺎﻳﺪ ﺑﻪ ﺁﻥ ﺗﻮﺟﻪ ﺩﺍﺷﺖ‬
‫ﺍﻳﻨﺴـﺖ ﻛـﻪ ﭘـﺲ ﺍﺯ ﺍﺗﺼـﺎﻝ ﺩﻭ ﺷﺒﻜﻪ ﺑﻪ ﻳﻜﺪﻳﮕﺮ ‪ ،‬ﺁﺩﺭﺱ ‪ Node‬ﻫﺎ ﺩﺭ ﻛﻞ ﺷﺒﻜﻪ ﺑﺎﻳﺪ ﻣﻨﺤﺼﺮ ﺑﻪ ﻓﺮﺩ ﺑﺎﺷﻨﺪ ﺑﻌﻼﻭﻩ‬
‫ﺧﻮﺩ ﻛﻮﭘﻠﺮ ﺩﺍﺭﺍﻱ ﺁﺩﺭﺱ ﻧﻴﺴﺖ‪.‬‬

‫ﻛﻮﭘﻠﺮ ﻣﻌﻤﻮﻻ ﻭﻇﺎﻳﻒ ﺯﻳﺮ ﺭﺍ ﺑﻌﻬﺪﻩ ﺩﺍﺭﺩ‪:‬‬

‫ﺍﻳﺰﻭﻻﺳﻴﻮﻥ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺑﻴﻦ ﺩﻭ ﺷﺒﻜﻪ‬ ‫•‬

‫‪PA‬‬ ‫ﺗﻐﺬﻳﻪ ﻛﺮﺩﻥ ﺷﺒﻜﻪ‬ ‫•‬

‫‪IEC 61158-2‬‬ ‫ﺍﻳﺠﺎﺩ ﺗﻄﺎﺑﻖ ﺑﻴﻦ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻫﺎﻱ ‪ RS485‬ﻭ‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫‪٣٥‬‬ ‫‪PROFIBUS PA‬‬

‫ﺷﻜﻞ ﺯﻳﺮ ﺍﻟﻤﺎﻧﻬﺎﻳﻲ ﻛﻪ ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS PA‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪ .‬ﺟﺎﻳﮕﺎﻩ ‪ Terminator‬ﻫﺎ‬
‫ﻧﻴﺰ ﺩﺭ ﺁﻥ ﻣﺸﺨﺺ ﺍﺳﺖ‪.‬‬
Techno-Electro.com

PROFIBUS PA ٣٦

RS485-IS
‫ ﺍﺳـﺖ ﻭ ﺑـﺮﺍﻱ ﻣﺤﻴﻄﻬﺎﻳـﻲ ﻛـﻪ ﺩﺭﺟـﻪ ﺍﻳﻤﻨـﻲ ﺑـﺎﻻ ﻧﻴﺎﺯ ﺩﺍﺭﻧﺪ ﻳﺎ‬RS485 ‫ ﺍﻧـﺘﺨﺎﺏ ﺟﺪﻳـﺪﻱ ﺍﺯ ﺧـﺎﻧﻮﺍﺩﻩ‬RS485-IS
‫ ﻫﺴـﺘﻨﺪ ﻛﺎﺭﺑـﺮﺩ ﺩﺍﺭﺩ ﻫـﺪﻑ ﺍﺯ ﻃﺮﺍﺣـﻲ ﺁﻥ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺮﻋﺖ ﺑﺎﻻ ﻭ ﺳﺎﻳﺮ ﻭﻳﮋﮔﻴﻬﺎﻱ‬Intrinsically Safe ‫ﺍﺻـﻄﻼﺣﺎ‬
‫ ﺳﻴﻤﻪ ﺍﺳﺖ ﻭ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ‬٤ ‫ ﻛـﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜـﻲ‬RS485-IS ‫ﺩﺭ‬. ‫ ﺩﺭ ﻣﺤـﻴﻂ ﻫـﺎﻱ ﺧﻄـﺮﻧﺎﻙ ﺑـﻮﺩﻩ ﺍﺳـﺖ‬RS485
‫ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺗﺎ‬، ‫ ﻓﻘﻂ ﻳﻜﻲ ﺑﻮﺩ‬MBP-IS ‫ ﻛﻪ ﺩﺭ‬Active Node ‫ ﺍﻓﺰﺍﻳﺶ ﻳﺎﺑﺪ ﺑﻌﻼﻭﻩ ﺗﻌﺪﺍﺩ‬1.5 Mbps ‫ﻣﻴـﺘﻮﺍﻧﺪ ﺗـﺎ‬
.‫ ﻋﺪﺩ ﻗﺎﺑﻞ ﺍﻓﺰﺍﻳﺶ ﺍﺳﺖ‬32

:‫ ﺩﺭ ﺟﺪﻭﻝ ﺯﻳﺮ ﺁﻣﺪﻩ ﺍﺳﺖ‬MBP-IS ‫ ﻭ‬RS485-IS ‫ﻣﻘﺎﻳﺴﻪ ﻭﻳﮋﮔﻴﻬﺎﻱ‬

RS485-IS MBP
Data Transmission Digital , Differential Singnals Digital , bit-
according to RS485 synchronous,Manchester
encoding
Transmission Rate 9.6 to 1500 KBit/s 31.25 KBit/s
Data Security HD=4 , Parity bit , start/end Preamble , error-
delimiter protected,start/end delimiter
Cable STP , 4wire , cable type A STP , 2 wire
Protection Type Intrinsic Safety (EExib) Intrinsic Safety (EExia/ib)
Current / Voltage EEx ib : EEx ia :
Ui=4,2 V Us=14–24 V Us=14–20 V
Ii=4.8 A Ia=250 mA Ia=110 mA
Ic<=149 mA/device P=4.2 W P=1.8 W
Cable Lenght EEx ia : EEx ia :
Max 1000 m 1900 m 1000 m
Topology Line Line , Tree
Number of Station 32 per segment , 32 per segment ,
126 per network 126 per network
Number of Repeater Maximum 9 Maximum 4
with signal refresh
‫‪Techno-Electro.com‬‬

‫‪٣٧‬‬ ‫‪PROFIBUS PA‬‬

‫ﻣﺪﻝ ﻛﻠﻲ ‪ RS485-IS‬ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ‪ RS485-IS‬ﺑﺼﻮﺭﺕ ﻣﻘﺎﻭﻣﺘﻲ ﻭ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺍﺳﺖ‪.‬‬

Techno-Electro.com
Techno-Electro.com

PROFIBUS ‫ﻓﺼﻞ ﺩﻭﻡ – ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬

: ‫ﻣﺸﺘﻤﻞ ﺑﺮ‬

PROFIBUS DP ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ‬ ١-٢

PROFIBUS FMS ‫ ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ‬٢-٢
PROFIBUS ‫ ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬٣-٢
‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬ ‫‪٤٠‬‬

‫ﻣﻘﺪﻣﻪ‬
‫ﺷﻨﺎﺧﺖ ﺍﺟﺰﺍﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﭘﻴﺶ ﻧﻴﺎﺯ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺁﻧﻬﺎ ﺩﺭ ﻣﺤﻴﻂ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪ Step7‬ﺍﺳﺖ ‪ .‬ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻳﻚ ﺷﺒﻜﻪ ﺑﺎﺯ )‪ (Open‬ﻣﻴﺒﺎﺷﺪ ﻭ ﻣﺤﺼﻮﻻﺕ ﻣﺘﻨﻮﻉ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﺘﻠﻒ ﺑﺎ ﻗﺎﺑﻠﻴﺖ ﺍﺗﺼﺎﻝ ﺑﻪ ﺍﻳﻦ ﺷﺒﻜﻪ‬
‫ﻋﺮﺿﻪ ﮔﺮﺩﻳﺪﻩ ﺍﺳﺖ‪ .‬ﺍﺯ ﺍﻳﻨﺮﻭ ﻣﻌﺮﻓﻲ ﺗﻤﺎﻡ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﻧﻪ ﻣﻴﺴﺮ ﺍﺳﺖ ﻭ ﻧﻪ ﺿﺮﻭﺭﻱ‪ .‬ﺩﺭ ﺍﻳﻦ‬
‫ﻗﺴﻤﺖ ﺻﺮﻓﺎ ﺑﺮﺧﻲ ﺍﺯ ﺍﻟﻤﺎﻧﻬﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻛﻪ ﺩﺭ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ Step7‬ﺩﺭ ﻗﺎﻟﺐ ﻳﻚ ﻛﺎﺗﺎﻟﻮﮒ‬
‫ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﻧﺪ ﺑﻪ ﺍﺟﻤﺎﻝ ﻣﻌﺮﻓﻲ ﻣﻴﺸﻮﻧﺪ‪ .‬ﺩﺭﺍﻳﻦ ﺧﺼﻮﺹ ﺑﻪ ﺩﻭ ﻧﻜﺘﻪ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ‪:‬‬
‫ﺍﻳﻦ ﺍﻟﻤﺎﻧﻬﺎ ﻣﺮﺑﻮﻁ ﺑﻪ ﭘﺮﻭﺗﻜﻞ ﻫﺎﻱ ‪ DP‬ﻭ ‪ FMS‬ﻫﺴﺘﻨﺪ‪.‬‬ ‫‪.١‬‬
‫ﺩﺭ ﻣﻮﺭﺩ ﻣﺤﺼﻮﻻﺕ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺩﻳﮕﺮ ) ﺑﺠﺰ ﺯﻳﻤﻨﺲ( ﺻﺮﻓﺎ ﺑﻪ ﻧﺤﻮﻩ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺁﻧﻬﺎ ﻭ ﺁﻧﻬﻢ ﺩﺭ ﺑﺨﺶ ﻫﺎﻱ‬ ‫‪.٢‬‬
‫ﺑﻌﺪﻱ ﺍﺷﺎﺭﻩ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬ ‫‪١-٢‬‬

‫ﺍﺯ ﺁﻧﺠﺎ ﻛﻪ ﻋﻤﻠﻜﺮﺩ ‪DP‬ﺑﺮ ﺭﻭﺵ ‪ Master/Slave‬ﺍﺳﺘﻮﺍﺭ ﺍﺳﺖ ﻟﺬﺍ ﻣﻴﺘﻮﺍﻥ ﺍﺟﺰﺍﻱ ﺍﻳﻦ ﺷﺒﻜﻪ ﺭﺍ ﺑﻪ ﺩﺳﺘﻪ ﺍﺻﻠﻲ ﺗﻘﺴﻴﻢ‬
‫ﻧﻤﻮﺩ‪:‬‬
‫‪DP Master‬‬ ‫•‬
‫‪DP Slave‬‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪٤١‬‬ ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬

‫‪DP Master‬‬ ‫‪١-١-٢‬‬

‫ﺩﻭﻧﻮﻉ ‪ DP Master‬ﺩﺭ ﻣﺠﻤﻮﻋﻪ ‪ S7-300‬ﻭ ‪ S7-400‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬
‫ﻧﻮﻉ ﺍﻭﻝ ‪ :‬ﺑﻌﻀﻲ‪ CPU‬ﻫﺎ ‪ ،‬ﻳﻚ ﭘﻮﺭﺕ ﻣﺨﺼﻮﺹ ‪ PROFIBUS DP‬ﺩﺍﺭﻧﺪ‪ .‬ﻣﻌﻤﻮ ﹰ‬
‫ﻻ )ﻭ ﻧﻪ ﻫﻤﻴﺸﻪ( ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﻧﺎﻡ ﺍﻳﻦ‬
‫‪ CPU‬ﻫﺎ ﻋﺒﺎﺭﺕ ‪ 2DP‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬ﻣﺜﺎﻝ ﻫﺎﻳﻲ ﺍﺯ ﺍﻳﻦ ﻧﻮﻉ ‪ CPU‬ﻫﺎ ﺑﻪ ﺷﺮﺡ ﺯﻳﺮ ﻣﻲ ﺑﺎﺷﺪ‪:‬‬
‫‪ CPU 315-2DP‬ﻭ ‪CPU 318-2DP‬ﻭ ‪ CPU 412-1‬ﻭ ‪ CPU 417-4‬ﻭ‪...‬‬
‫ﻫﻤﻪ ‪ CPU‬ﻫﺎﻱ ‪ S7‬ﺩﺍﺭﺍﻱ ﭘﻮﺭﺕ ‪ MPI‬ﻫﺴﺘﻨﺪ ﻛﻪ ﺑﺮﺍﻱ ‪ PC/PG‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﺩﺭ ﻋﻴﻦ ﺣﺎﻝ ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﺁﻥ ﺑﺮﺍﻱ‬
‫‪CPU‬‬ ‫ﺷﺒﻜﻪ ﻛﺮﺩﻥ ﻧﻴﺰ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺷﺒﻜﻪ ‪ MPI‬ﺧﺎﺹ ﺯﻳﻤﻨﺲ ﺍﺳﺖ ﻭ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺟﻬﺎﻧﻲ ﻧﺪﺍﺭﺩ‪ .‬ﭘﻮﺭﺕ ‪ DP‬ﺭﻭﻱ ﻫﻤﻪ‬
‫ﻫﺎ ﻣﻮﺟﻮﺩ ﻧﻴﺴﺖ‪ .‬ﺍﮔﺮ ‪ CPU‬ﻓﺎﻗﺪ ﭘﻮﺭﺕ ‪ DP‬ﺑﺎﺷﺪ ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ﺁﻥ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﻭ‬
‫ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﺑﺎﻳﺪ ﻛﺎﺭﺕ ‪ CP‬ﺩﺭ ﻛﻨﺎﺭ ‪ CPU‬ﻧﺼﺐ ﮔﺮﺩﺩ‪ .‬ﭘﻮﺭﺗﻬﺎﻱ ﺭﻭﻱ ﺑﺮﺧﻲ ﺍﺯ ‪ CPU‬ﻫﺎﻱ ‪ 300‬ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ‬
‫ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺩﺭ ﺑﺮﺧﻲ ‪ CPU‬ﻫﺎ ﭘﻮﺭﺕ ‪ MPI‬ﻣﻴﺘﻮﺍﻧﺪ‬

‫‪CPU‬‬ ‫ﺑﺼﻮﺭﺕ ‪ DP‬ﻧﻴﺰ ﺗﻨﻈﻴﻢ ﺷﻮﺩ ‪ .‬ﻳﻌﻨﻲ‬
‫ﺑﻌﻨﻮﺍﻥ ‪ DP Master‬ﺭﻭﻱ ﺩﻭ ﺷﺒﻜﻪ ‪ DP‬ﻛﻪ‬
‫ﺍﺯ ﻳﻜﺪﻳﮕﺮ ﻣﺴﺘﻘﻞ ﻫﺴﺘﻨﺪ ﻋﻤﻞ ﻣﻴﻜﻨﺪ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ‬
‫ﺗﻨﻈﻴﻢ ﻛﺎﻓﻴﺴﺖ ﺩﺭ ﺗﻨﻈﻴﻤﺎﺕ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ‬
‫‪ CPU‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Hwconfig‬ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ‬
‫ﺭﻭﻱ ‪ MPI/DP‬ﻗﺴﻤﺖ ‪ Interface‬ﺭﺍ ﻣﺎﻧﻨﺪ‬
‫ﺷﻜﻞ ﺗﻐﻴﻴﺮ ﺩﻫﻴﻢ‪.‬‬
‫ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ‪ PG/PC‬ﺍﺯ ﻃﺮﻳﻖ ﭘﻮﺭﺕ ‪ DP‬ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬ ‫‪٤٢‬‬

‫ﻧﻜﺘﻪ ﺩﻳﮕﺮﻱ ﻛﻪ ﺑﺎﻳﺪ ﺧﺎﻃﺮ ﻧﺸﺎﻥ ﻛﺮﺩ ﺍﻳﻨﺴﺖ ﻛﻪ ﻭﻗﺘﻲ ‪ CPU‬ﺍﺯ ﻃﺮﻳﻖ ﭘﻮﺭﺕ ‪ DP‬ﺷﺒﻜﻪ ﻣﻴﺸﻮﺩ ﻫﻤﺰﻣﺎﻥ ﻣﻴﺘﻮﺍﻥ ﺁﻧﺮﺍ ﺍﺯ‬
‫ﻃﺮﻳﻖ ﭘﻮﺭﺕ ‪ MPI‬ﻧﻴﺰ ﺑﻪ ﺷﺒﻜﻪ ‪ MPI‬ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪ .‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ‪.‬‬

‫‪PROFIBUS‬‬ ‫ﻧﻮﻉ ﺩﻭﻡ ‪ :‬ﺍﮔﺮ ‪ CPU‬ﻓﺎﻗﺪ ﭘﻮﺭﺕ ‪ DP‬ﺑﺎﺷﺪ ﻳﺎ ﺍﮔﺮ ﻻﺯﻡ ﺑﺎﺷﺪ ﻋﻼﻭﻩ ﺑﺮ ﭘﻮﺭﺕ ‪ DP‬ﻛﻪ ﺑﻪ ﻳﻚ ﺷﺒﻜﻪ‬
‫ﻣﺘﺼﻞ ﺍﺳﺖ ‪ ،‬ﺷﺒﻜﻪ ﻳﺎ ﺷﺒﻜﻪ ﻫﺎﻱ ‪ DP‬ﺩﻳﮕﺮﻱ ﻧﻴﺰ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﺩﺭﺍﻳﻨﺼﻮﺭﺕ ﺑﺎﻳﺪ ﺍﺯ ﻛﺎﺭﺗﻬﺎﻱ ﺯﻳﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ‪:‬‬
‫ﻛﺎﺭﺕ ﻫﺎﻱ ‪ CP‬ﺑﺎ ﻗﺎﺑﻠﻴﺖ ﭘﺸﺘﻴﺒﺎﻧﻲ ‪ PROFIBUS DP‬ﻣﺜﻞ ‪ CP 342-5:‬ﻭ ‪CP 343-5‬‬ ‫•‬

‫ﻛﺎﺭﺕ ﻫﺎﻱ ‪ IM‬ﺩﺭ ‪ S7-400‬ﺑﺎ ﻗﺎﺑﻠﻴﺖ ﭘﺸﺘﻴﺒﺎﻧﻲ ‪ PROFIBUS DP‬ﻣﺜﻞ ‪.IM 467‬‬ ‫•‬

‫ﺗﺬﻛﺮ ‪ :‬ﺑﺮﺧﻲ ﺍﺯ ‪ CPU‬ﻫﺎﻱ ‪ S7-400‬ﺩﺍﺭﺍﻱ ﺍﺳﻼﺗﻲ ﺑﺮﺍﻱ ﻧﺼﺐ ﻳﻚ ‪ Submodule‬ﺑﻪ ﻧﺎﻡ ‪ IF‬ﻫﺴﺘﻨﺪﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ﺁﻥ‬
‫ﻣﻴﺘﻮﺍﻥ ﻳﻚ ﺷﺒﻜﻪ ‪ DP‬ﺟﺪﺍﮔﺎﻧﻪ ﻧﻴﺰ ﺍﻳﺠﺎﺩ ﻧﻤﻮﺩ‪ .‬ﻣﺜﻞ ‪ IF 964-DP‬ﺩﺭ ‪.CPU 417-4‬‬

‫‪IF964-DP‬‬ ‫‪IM467‬‬ ‫‪CP 342-5‬‬

‫‪Techno-Electro.com‬‬

‫‪٤٣‬‬ ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬

‫‪DP Slave‬‬ ‫‪٢-١-٢‬‬
‫‪ Dp Slave‬ﻫﺎ ﺩﺭ ﻭﺍﻗﻊ ﺗﺠﻬﻴﺰﺍﺕ ﺟﺎﻧﺒﻲ ﻭﻧﺎ ﻣﺘﻤﺮﻛﺰ ﻫﺴﺘﻨﺪ ﻛﻪ ﺑﺎ ‪ Master‬ﺍﺭﺗﺒﺎﻁ ﻣﻲ ﮔﻴﺮﻧﺪ ‪.‬‬
‫‪ Slave‬ﻫﺎ ﻃﻴﻒ ﮔﺴﺘﺮﺩﻫﺎﻱ ﺍﺯ ﺗﺠﻬﻴﺰﺍﺕ ﺭﺍ ﺷﺎﻣﻞ ﻣﻲ ﺷﻮﻧﺪ‪ .‬ﺑﺮﺧﻲ ﺍﺯ ﻣﻬﻤﺘﺮﻳﻦ ﺁﻧﻬﺎ ﺩﺭ ﺟﺪﻭﻝ ﺯﻳﺮ ﺫﻛﺮ ﺷﺪﻩ ﺍﻧﺪ‪.‬‬
‫ﺷﺮﺡ‬ ‫ﻋﻨﻮﺍﻥ‬
‫‪ PID‬ﻛﻨﺘﺮﻟﺮﻫﺎ‬ ‫‪Closed Loop Controller‬‬
‫ﺩﺭﺍﻳﻮﻫﺎﻱ ‪DC‬‬ ‫‪Simoreg‬‬
‫ﺩﺭﺍﻳﻮﻫﺎﻱ ‪AC‬‬ ‫‪Simovert‬‬
‫ﻋﻤﻠﮕﺮﻫﺎﻱ ﺑﺮﻗﻲ‬ ‫‪Sipos‬‬
‫ﺩﻭﺭﺑﻴﻦ ﻫﺎﻱ ﺻﻨﻌﺘﻲ‬ ‫‪Sensoric‬‬
‫ﻭﺳﻴﻠﻪ ﺗﺸﺨﻴﺺ ﺑﺎﺭﻛﺪ‬ ‫‪Ident‬‬
‫ﭘﺎﻧﻞ ﻫﺎﻱ ﺍﭘﺮﺍﺗﻮﺭﻱ‬ ‫‪IPC‬‬
‫ﺩﺳﺘﮕﺎﻫﻬﺎﻱ ﻛﻨﺘﺮﻝ ﻋﺪﺩﻱ‬ ‫‪NC‬‬
‫ﺩﮊﻧﻜﺘﻮﺭﻫﺎ‬ ‫‪Switching Device‬‬
‫ﺗﺮﻣﻴﻨﺎﻟﻬﺎﻱ ‪Remote I/O‬‬ ‫‪ET‬‬
‫ﺍﻳﻨﻬﺎ ﻫﻤﻪ ﺗﺠﻬﻴﺰﺍﺗﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﺁﻧﻬﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪ .‬ﺍﻣﺎ ﻣﺸﻬﻮﺭﺗﺮﻳﻦ ﻃﻴﻒ ‪DP‬‬

‫‪ Slave‬ﻫﺎ‪ Distributed I/O،‬ﻫﺎ ﻫﺴﺘﻨﺪ ﻭﺩﺭ ﺍﻳﻦ ﻣﻴﺎﻥ ﻣﻌﺮﻭﻓﺘﺮﻳﻦ ‪ Distributed I/O‬ﻫﺎﻱ ﺯﻳﻤﻨﺲ ﺩﺭ ﻭﺍﻗﻊ ﻫﻤﺎﻥ ‪ ET‬ﻫﺎ‬
‫ﻫﺴﺘﻨﺪ‪.‬ﻭﻗﺘﻲ ﺻﺤﺒﺖ ﺍﺯ ‪ Fieldbus‬ﻣﻴﺸﻮﺩ ﻣﻌﻤﻮﻻ ﻣﻬﻤﺘﺮﻳﻦ ﻣﺰﻳﺖ ﺁﻧﺮﺍ ﺣﺬﻑ ﻛﺎﺑﻞ ﻛﺸﻲ ﻫﺎﻱ ﻣﻮﺍﺯﻱ ﻭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬
‫‪ Remote I/O‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺫﻛﺮ ﻣﻴﻜﻨﻨﺪ ‪ .‬ﺍﻳﻦ ﻛﺎﺭ ﺗﻮﺳﻂ ‪ ET‬ﻫﺎ ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ‪ ET .‬ﻫﺎ ﺩﺭ ﺳﻄﺢ ﻓﻴﻠﺪ ﺑﺼﻮﺭﺕ‬
‫ﭘﺮﺍﻛﻨﺪﻩ ﻧﺼﺐ ﻣﻴﺸﻮﻧﺪ ﻭ ﺩﺭ ﻫﺮ ﻣﻨﻄﻘﻪ ﺳﻴﮕﻨﺎﻟﻬﺎﻱ ‪ I/O‬ﺭﺍ ﺟﻤﻊ ﺁﻭﺭﻱ ﻛﺮﺩﻩ ﻭ ﺍﺯ ﻃﺮﻳﻖ ﺷﺒﻜﻪ ﺑﻪ ‪ Master‬ﺍﻧﺘﻘﺎﻝ ﻣﻴﺪﻫﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬ ‫‪٤٤‬‬

‫ﻻ ﺧﻮﺍﻧﻨﺪﻩ ﺑﺎ ﻣﻔﺎﻫﻴﻢ ‪ Compact‬ﻭ ‪Modular‬‬
‫‪ ET‬ﻫﺎ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ‪ Compact‬ﻭ‪ Modular‬ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﻛﺮﺩ‪ .‬ﺍﺣﺘﻤﺎ ﹰ‬
‫ﺁﺷﻨﺎﻳﻲ ﺩﺍﺭﺩ ﺍﻣﺎ ﺑﺮﺍﻱ ﻳﺎﺩﺁﻭﺭﻱ ‪،‬ﻭﻗﺘﻲ ﻛﻪ ﮔﻔﺘﻪ ﻣﻲ ﺷﻮﺩﻛﻪ ﻳﻚ ﻭﺳﻴﻠﻪ ‪ Compact‬ﺍﺳﺖ ﻣﻨﻈﻮﺭ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺳﺎﺧﺘﺎﺭ ﺁﻥ‬
‫ﺛﺎﺑﺖ ﺍﺳﺖ ﻭﺍﻣﻜﺎﻥ ﺍﺿﺎﻓﻪ ﻳﺎ ﻛﻢ ﻛﺮﺩﻥ ﻛﺎﺭﺕ ﻫﺎﻳﻲ ﺭﺍ ﻣﺎﻧﻨﺪ ﻛﺎﺭﺕ ‪ I/O‬ﻧﺪﺍﺭﺩ ﺍﻣﺎ ﺩﺭ ﻧﻮﻉ ‪، Modular‬ﺍﻣﻜﺎﻥ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ‬
‫ﺗﻌﺪﺍﺩﻱ ﻣﺪﻭﻝ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﻳﻚ ﺳﺎﺧﺘﺎﺭ ﻗﺎﺑﻞ ﺍﻧﻌﻄﺎﻑ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻛﺎﺭﺑﺮ ﻗﺮﺍﺭ ﻣﻲ ﮔﻴﺮﺩ‪ .‬ﻣﺸﺨﺼﺎﺕ ﺍﺻﻠﻲ‬
‫ﺑﺮﺧﻲ ﺍﺯ ﻣﻬﻤﺘﺮﻳﻦ ‪ ET‬ﻫﺎﻱ ﺯﻳﻤﻨﺲ ﺩﺭ ﺟﺪﻭﻝ ﺯﻳﺮ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪IP20 -‬‬ ‫‪ - Compact‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺗﻌﺪﺍﺩ ﻣﺤﺪﻭﺩﻱ ﺳﻴﮕﻨﺎﻝ ﺩﻳﺠﻴﺘﺎﻝ‬ ‫‪ET200L‬‬
‫‪- Compact‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺗﻌﺪﺍﺩ ﻣﺤﺪﻭﺩﻱ ﺳﻴﮕﻨﺎﻝ ﺩﻳﺠﻴﺘﺎﻝ ﻭ ﺁﻧﺎﻟﻮﮒ ‪IP20 -‬‬ ‫‪ET200B‬‬
‫‪- Compact‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺗﻌﺪﺍﺩ ﻣﺤﺪﻭﺩﻱ ﺳﻴﮕﻨﺎﻝ ﺩﻳﺠﻴﺘﺎﻝ ﻭ ﺁﻧﺎﻟﻮﮒ ‪IP65-‬‬ ‫‪ET200R‬‬
‫‪- Compact‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺗﻌﺪﺍﺩ ﻣﺤﺪﻭﺩﻱ ﺳﻴﮕﻨﺎﻝ ﺩﻳﺠﻴﺘﺎﻝ ﻭ ﺁﻧﺎﻟﻮﮒ ‪IP67-‬‬ ‫‪ET200C‬‬
‫‪S7-300‬‬ ‫‪-Modular‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺣﺠﻢ ﺯﻳﺎﺩ ‪ - I/O‬ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ‬ ‫‪ET200M‬‬
‫ﺩﺍﺭﺍﻱ ﺍﺳﺘﺎﺭﺗﺮ ﻣﻮﺗﻮﺭ ‪IP20 -‬‬ ‫‪ -Modular‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺣﺠﻢ ﻣﺘﻮﺳﻂ ‪- I/O‬‬ ‫‪ET200S‬‬
‫ﺩﺍﺭﺍﻱ ﺍﺳﺘﺎﺭﺗﺮ ﻣﻮﺗﻮﺭ ﻭ ﻣﺪﻭﻝ ﭘﻨﻮﻣﺎﺗﻴﻚ – ‪IP65‬‬ ‫‪ -Modular‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺣﺠﻢ ﻣﺘﻮﺳﻂ ‪- I/O‬‬ ‫‪ET200X‬‬
‫‪S5-100U‬‬ ‫‪-Modular‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺣﺠﻢ ﺯﻳﺎﺩ ‪ - I/O‬ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ‬ ‫‪ET200U‬‬

‫‪ET200R‬‬ ‫‪ET200L‬‬

‫‪ET200S‬‬ ‫‪ET200M‬‬
‫‪Techno-Electro.com‬‬

‫‪٤٥‬‬ ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬

‫ﻋﻨﺎﻭﻳﻦ ﻓﻮﻕ ﻫﺮ ﻛﺪﺍﻡ ﺑﻪ ﻳﻚ ﺧﺎﻧﻮﺍﺩﻩ ﺍﻃﻼﻕ ﻣﻴﺸﻮﺩ‪ .‬ﻫﺮ ﻳﻚ ﺍﺯ ﺁﻧﻬﺎ ﺑﻪ ﭼﻨﺪﻳﻦ ﻧﻮﻉ ﺑﺎ ﻗﺎﺑﻠﻴﺖ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺗﻘﺴﻴﻢ ﻣﻴﺸﻮﻧﺪ‪.‬‬
‫ﻋﻨﻮﺍﻥ ﻛﺎﺭﺕ ﺍﺭﺗﺒﺎﻃﻲ ﺁﻥ ‪ IM‬ﺍﺳﺖ ﻭ ﺑﺮﺍﻱ ﻫﺮ ‪ ET‬ﭼﻨﺪﻳﻦ ﻣﺪﻝ ﻛﺎﺭﺕ ‪ IM‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬
‫‪ ET‬ﻫﺎﻱ ﻓﻮﻕ ‪ET200M‬‬ ‫ﺍﻧﺘﺨﺎﺏ ‪ ET‬ﻣﻨﺎﺳﺐ ﺗﻮﺳﻂ ﻛﺎﺭﺑﺮ ﺑﺴﺘﻪ ﺑﻪ ﻧﻴﺎﺯ ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ ﻭﻟﻲ ﺑﺎﻳﺪ ﺧﺎﻃﺮ ﻧﺸﺎﻥ ﻛﺮﺩ ﻛﻪ ﺩﺭ ﺑﻴﻦ‬
‫ﭘﺮ ﻛﺎﺭﺑﺮﺩ ﺗﺮ ﺍﺯﺳﺎﻳﺮﻳﻦ ﺍﺳﺖ ﺍﺯ ﺩﻻﻳﻞ ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﻳﻜﺴﺎﻥ ﺑﻮﺩﻥ ﻛﺎﺭﺗﻬﺎﻱ ﺁﻥ ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ ‪S7-300‬ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺫﻛﺮ ﻛﺮﺩ‪.‬‬
‫ﻻﺯﻡ ﺍﺳﺖ ﻳﺎﺩﺁﻭﺭﻱ ﻛﻨﻴﻢ ‪ Distributed I/O‬ﻫﺎﻳﻲ ﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ‪ DP Slave‬ﺑﺮﺍﻱ ‪ DP Master‬ﻓﺮﺍﻫﻢ ﻣﻲ ﺷﻮﻧﺪ ﺩﻗﻴﻘﹰﺎ ﻣﺎﻧﻨﺪ‬
‫‪ I/O‬ﻫﺎﻳﻲ ﻛﻪ ﺑﺼﻮﺭﺕ ‪ Central‬ﻣﺘﺼﻞ ﺑﻪ ‪ Master‬ﻫﺴﺘﻨﺪ ﻋﻤﻞ ﻣﻲ ﻛﻨﻨﺪ‪ .‬ﺗﻨﻬﺎ ﺍﺳﺘﺜﻨﺎ ﺩﺭ ﺍﻳﻦ ﻣﻮﺭﺩ ‪ CP 342-5‬ﺍﺳﺖ‪ .‬ﺍﻳﻦ‬
‫ﻣﻮﺿﻮﻉ ﺩﺭ ﻫﻨﮕﺎﻡ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺗﻮﺳﻂ ‪ Step7‬ﺭﻭﺷﻦ ﺗﺮ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫‪Slave‬‬ ‫‪ Master‬ﺑﺎ ﺍﻣﻜﺎﻥ ﻋﻤﻠﻜﺮﺩ‬

‫ﻧﻜﺘﻪ ﺩﻳﮕﺮﻱ ﻛﻪ ﺩﺭ ﺑﺤﺚ ﺍﻧﻮﺍﻉ ‪ Master‬ﻭ ‪ Slave‬ﻻﺯﻡ ﺑﻪ ﺫﻛﺮ ﺍﺳﺖ ﺍﻳﻨﺴﺖ ﻛﻪ ﺑﻌﻀﻲ ‪DP Interface‬ﻫﺎﻱ ﻣﺘﻌﻠﻖ ﺑﻪ‬
‫‪DP‬‬ ‫ﻣﺠﻤﻮﻋﻪ ‪ S7-300‬ﻣﺎﻧﻨﺪ ‪ CPU 315-2DP‬ﻭﻳﺎ ‪ CP 342-5‬ﻫﻢ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﻪ ﺻﻮﺭﺕ ‪ DP Master‬ﻭ ﻫﻢ ﺑﻪ ﻋﻨﻮﺍﻥ‬
‫‪ Slave‬ﻋﻤﻞ ﻛﻨﻨﺪ‪.‬ﺩﺭ ﺣﺎﻟﺘﻲ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺗﺠﻬﻴﺰﺍﺕ ‪ ،‬ﺣﺎﻟﺖ ‪ DP Slave‬ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﺷﻮﺩ‪ ،‬ﺑﺎﻳﺪ ﺗﻜﻨﻴﻚ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ‬
‫ﺭﺍ ﻫﻢ ﻣﻌﻴﻦ ﻛﻨﻴﻢ‪ .‬ﺩﻭ ﻣﺪ ﺑﺮﺍﻱ ﺗﻜﻨﻴﻚ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ ﻗﺎﺑﻞ ﺗﻌﺮﻳﻒ ﺍﺳﺖ‪:‬‬

‫‪• DP Slave as active node‬‬

‫‪• DP Slave as passive node‬‬

‫ﺍﺯ ﺩﻳﺪﮔﺎﻩ ﭘﺮﻭﺗﻜﻞ ‪ DP‬ﻧﺤﻮﻩ ﺍﺭﺗﺒﺎﻁ ﻭﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺩﺭ ‪ Active DP Slave‬ﻭ ‪ Passive DP Slave‬ﻳﻜﺴﺎﻥ ﺍﺳﺖ ‪ .‬ﺗﻨﻬﺎ‬
‫ﺗﻔﺎﻭﺕ ﺍﻳﻨﺴﺖ ﻛﻪ ‪ Active DP Slave‬ﻋﻼﻭﻩ ﺑﺮ ﺍﺭﺗﺒﺎﻁ ﻋﺎﺩﻱ ﺑﺎ ‪ Master‬ﻣﺮﺑﻮﻃﻪ‪ ،‬ﻳﻚ ‪ Token‬ﻫﻢ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺩﺍﺭﺩ ﻛﻪ ﻣﻲ‬
‫ﺗﻮﺍﻧﺪ ﺑﺎ ﺳﺎﻳﺮ ‪ node‬ﻫﺎ ﺍﺭﺗﺒﺎﻁ ﺑﮕﻴﺮﺩ ﻭﻣﺴﺘﻘﻴﻤﹰﺎ ﺑﻪ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺑﭙﺮﺩﺍﺯﺩ ‪.‬ﺍﻳﻦ ﻛﺎﺭ ﺍﺯ ﻃﺮﻳﻖ ﺳﺮﻭﻳﺲ ‪ FDL‬ﻭ ﺗﻮﺍﺑﻊ ‪ S7‬ﺻﻮﺭﺕ‬
‫ﻣﻲ ﮔﻴﺮﺩ ‪ .‬ﻗﺎﺑﻠﻴﺖ ﻓﻮﻕ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﺭﺍ ﻓﺮﺍﻫﻢ ﻣﻲ ﺳﺎﺯﺩ ﻛﻪ ﺩﺭ ﺣﺎﻟﻲ ﻛﻪ ﺷﺒﻜﻪ ‪ DP‬ﺩﺭ ﺣﺎﻝ ﺗﺒﺎﺩﻝ ﺍﻃﻼﻋﺎﺕ ﻭﺍﻧﺠﺎﻡ ﻛﺎﺭﻫﺎﻱ‬
‫ﻣﺮﺑﻮﻃﻪ ﺍﺳﺖ ‪،‬ﺍﻳﻦ ﻭﺳﺎﻳﻞ ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﻣﺰﺍﺣﻤﺘﻲ ﺑﺮﺍﻱ ﺷﺒﻜﻪ ‪ DP‬ﺍﻳﺠﺎﺩ ﻛﻨﻨﺪ ‪،‬ﺍﺯ ﻃﺮﻳﻖ ﺷﺒﻜﻪ ‪ DP‬ﺑﺎ ﻭﺳﺎﻳﻠﻲ ﻫﻤﭽﻮﻥ ‪، OP‬‬
‫‪ PG‬ﻭ‪ PC‬ﺍﺭﺗﺒﺎﻁ ﺑﮕﻴﺮﻧﺪ‪.‬ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﺩﺭ ﺣﺎﻟﺖ ‪ Passive DP Slave‬ﺍﻳﻦ ‪ Master‬ﺍﺳﺖ ﻛﻪ ﺗﻌﻴﻴﻦ ﻣﻴﻜﻨﺪ ﻛﻪ ﻛﺪﺍﻡ‬
‫‪ Passive DP Slave‬ﺑﺎﺱ ﺭﺍ ﺩﺭﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﺩ ‪.‬ﺍﻣﺎ ﺑﺮﺍﻱ ‪ Active DP Slave‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﻓﻮﻕ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ‬
‫ﺷﺪ‪،‬ﻭﺿﻌﻴﺖ ﻓﺮﻕ ﻣﻲ ﻛﻨﺪ‪.‬‬
‫ﺗﻨﻈﻴﻢ ﻋﻤﻠﻜﺮﺩ ‪ Master‬ﻳﺎ ‪ Slave‬ﺑﺮﺍﻱ ﺍﻳﻦ ﺗﺠﻬﻴﺰﺍﺕ ﺗﻮﺳﻂ ‪ Step7‬ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ ﻛﻪ ﺩﺭ ﺑﺨﺸﻬﺎﻱ ﺑﻌﺪﻱ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ‬
‫ﺧﻮﺍﻫﺪﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS DP‬‬ ‫‪٤٦‬‬

‫‪Inteligent Slave‬‬
‫ﻳﻚ ﻧﻮﻉ ‪ DP Slave‬ﺩﻳﮕﺮ ﻧﻴﺰ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﻪ ﺁﻥ ‪ I-Slave‬ﮔﻔﺘﻪ ﻣﻲ ﺷﻮﺩ ﻭ ﻣﺨﻔﻒ ‪ Intelligent Slave‬ﻣﻲ ﺑﺎﺷﺪ‪ .‬ﺍﻧﻮﺍﻉ‬
‫‪ I-Slave‬ﻫﺎ ﺑﻪ ﺷﺮﺡ ﺯﻳﺮ ﻣﻲ ﺑﺎﺷﻨﺪ‪:‬‬
‫‪CP 341-5 , CPU 318-2 ,‬‬ ‫‪ -١‬ﺍﻧﻮﺍﻉ ‪ DP Master‬ﻫﺎﻳﻲ ﻛﻪ ﻗﺎﺑﻠﻴﺖ ﻋﻤﻞ ﻛﺮﺩﻥ ﺩﺭ ﻣﺪ ‪ Slave‬ﺭﺍ ﻫﻢ ﺩﺍﺭﻧﺪ ﻣﺜﻞ‪:‬‬
‫‪CPU 316-2DP,CPU 315-2DP‬‬
‫‪ ET‬ﻫﺎﻱ ‪ CPU‬ﺩﺍﺭ ﻣﺜﻞ ‪ ET 200 X‬ﻭ‪ET 200S‬‬ ‫‪-٢‬‬
‫ﺩﺭ ﺍﺭﺗﺒﺎﻁ ﻣﻌﻤﻮﻟﻲ ‪ Master‬ﺑﺎ ‪ DP Slave‬ﻫﺎ‪ Master،‬ﻣﺴﺘﻘﻴﻤﹰﺎ ﺑﻪ ﻧﺎﺣﻴﻪ ‪ I/O‬ﺩﺭ ‪ DP Slave‬ﺩﺳﺘﺮﺳﻲ ﺩﺍﺭﺩ ﺍﻣﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬
‫‪ Master‬ﺑﺎ ‪ I-Slave‬ﻫﺎ ‪ Master،‬ﻣﺴﺘﻘﻴﻤﹰﺎ ﺑﻪ ‪ I/O‬ﺩﺳﺘﺮﺳﻲ ﻧﺪﺍﺭﺩ ﺑﻠﻜﻪ ‪ I-Slave‬ﻳﻚ ﭘﺮﺩﺍﺯﺵ ﺍﻭﻟﻴﻪ ﺭﻭﻱ ‪ I/O‬ﺍﻧﺠﺎﻡ ﻣﻲ‬
‫‪I-Slave‬‬ ‫ﺩﻫﺪ ﻭﺳﭙﺲ ﺗﺼﻮﻳﺮ ﺁﻧﻬﺎ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ‪ Master‬ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﺪ ﻭ ‪ Master‬ﺍﺯ ﻃﺮﻳﻖ ﺣﺎﻓﻈﻪ ‪ I-Slave‬ﺑﻪ ‪ I/O‬ﻫﺎﻱ‬
‫ﺩﺳﺘﺮﺳﻲ ﺩﺍﺭﺩ‪.‬‬

‫‪PROFIBUS DP-V2‬‬ ‫ﻗﺎﺑﻠﻴﺖ ﺩﻳﮕﺮ ‪ I-Slave‬ﺍﻣﻜﺎﻥ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎﻱ ﻣﺴﺘﻘﻴﻢ ﺑﺎ ‪ Slave‬ﻫﺎﻱ ﺩﻳﮕﺮ ﺍﺳﺖ ‪ .‬ﻗﺎﺑﻠﻴﺘﻲ ﻛﻪ ﺩﺭ‬
‫ﻣﻨﻈﻮﺭ ﺷﺪﻩ ﺍﺳﺖ‪.‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﻳﻦ ﺭﻭﺵ ﺑﻪ ﺗﻔﺼﻴﻞ ﺑﻴﺎﻥ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٤٧‬‬ ‫ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ ‪PROFIBUS FMS‬‬

‫‪ Slave‬ﺑﺎ ﻗﺎﺑﻠﻴﺖ ﺍﺗﺼﺎﻝ ﺑﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﻧﻴﺰ ﺫﻛﺮ ﺷﺪ ﻛﺎﺭﺗﻬﺎﻳﻲ ﻛﻪ ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﻛﺪ ﺁﻧﻬﺎ ﻛﻠﻤﻪ ‪ FO‬ﻧﻮﺷﺘﻪ ﺷﺪﻩ ﻗﺎﺑﻠﻴﺖ ﺍﺗﺼﺎﻝ ﺑﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺭﺍ‬
‫ﻣﺴﺘﻘﻴﻤﺎ ﺩﺍﺭﻧﺪ‪ .‬ﺩﺭ ﺑﻴﻦ ‪ ET‬ﻫﺎ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺩﺍﺭﺍﻱ ﺍﺗﺼﺎﻝ ﻣﺴﺘﻘﻴﻢ ‪ FO‬ﻫﺴﺘﻨﺪ‪:‬‬
‫‪ ET200M‬ﺑﺎ ﻛﺎﺭﺕ ‪IM153-2 FO‬‬ ‫•‬
‫‪ ET200S‬ﺑﺎ ﻛﺎﺭﺕ ‪IM151-1 FO‬‬ ‫•‬
‫‪X-BM 143 FO‬‬ ‫‪ ET200x‬ﺑﺎ ﻛﺎﺭﺕ‬ ‫•‬

‫‪PROFIBUS FMS‬‬ ‫‪ ٢-٢‬ﺍﺟﺰﺍﻱ ﺍﺻﻠﻲ‬

‫ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺫﻛﺮ ﺷﺪ ﻣﺒﺘﻨﻲ ﺑﺮ ﺗﻜﻨﻴﻚ ‪ Token Pass‬ﻭ ﺑﻴﻦ ﭼﻨﺪ ‪ Master‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻫﺮ‬
‫ﺍﻳﺴﺘﮕﺎﻩ ﻧﻴﺎﺯﻣﻨﺪ ﻛﺎﺭﺕ ﺷﺒﻜﻪ ﺍﻱ ﺍﺳﺖ ﻛﻪ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﺭﺍ ﺳﺎﭘﻮﺭﺕ ﻛﻨﺪ‪.‬ﺑﺎ ﻭﺟﻮﺩ ﺍﻳﻦ ﻛﺎﺭﺕ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺧﺎﺹ ﺩﻳﮕﺮﻱ‬
‫ﻻﺯﻡ ﻧﻴﺴﺖ ﻳﻌﻨﻲ ﻛﺎﺑﻞ ﻛﺎﻧﻜﺘﻮﺭ ﻭ ﺳﺎﻳﺮ ﺍﺟﺰﺍﻳﻲ ﻛﻪ ﺑﺮﺍﻱ ‪ DP‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﻧﺪ ﺭﺍ ﻧﻴﺰ ﻣﻴﺘﻮﺍﻥ ﻣﺸﺘﺮﻛﹰﺎ ﺑﺮﺍﻱ ‪ FMS‬ﻧﻴﺰ ﺑﻜﺎﺭ‬
‫‪FMS‬‬ ‫ﺑﺮﺩ‪ .‬ﺑﺮﺍﻱ ‪ PLC‬ﻫﺎﻱ ‪ S7-300‬ﻛﺎﺭﺕ ‪ CP343-5‬ﻭ ﺑﺮﺍﻱ ‪ PLC‬ﻫﺎﻱ ‪ S7-400‬ﻛﺎﺭﺕ ‪ CP443-5‬ﺩﺍﺭﺍﻱ ﻗﺎﺑﻠﻴﺖ‬
‫ﺍﺳﺖ ‪ .‬ﺑﺎ ﻧﺼﺐ ﻛﺮﺩﻥ ﺁﻧﻬﺎ ﻭ ﺍﺗﺼﺎﻝ ﺑﻪ ‪ PROFIBUS‬ﺗﺒﺎﺩﻝ ﺍﻃﻼﻋﺎﺕ ﺑﺎ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻗﺒﻠﻲ ﺗﻮﺳﻂ ﻓﺎﻧﻜﺸﻦ ﻫﺎﻱ ﺧﺎﺹ ﺍﻧﺠﺎﻡ‬
‫ﻣﻴﺸﻮﺩ‬
‫‪FMS‬‬ ‫‪ PLC‬ﻫﺎﻱ ‪ PG ، S5‬ﻭ ‪ PC‬ﻭ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻫﺎﻱ ﻏﻴﺮ ﺯﻳﻤﻨﺲ ﺭﺍ ﻧﻴﺰ ﺑﺎ ﻛﺎﺭﺕ ﺷﺒﻜﻪ ﻣﻨﺎﺳﺐ ﻣﻴﺘﻮﺍﻥ ﺑﺼﻮﺭﺕ‬
‫ﭘﻴﻜﺮﺑﻨﺪﻱ ﻧﻤﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪RS485‬‬ ‫ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬ ‫‪٤٨‬‬

‫‪PROFIBUS‬‬ ‫‪ ٣-٢‬ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬
‫ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﻣﻬﻢ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﺎ ﺗﻘﺴﻴﻢ ﺑﻨﺪﻱ ﺑﺮ ﺣﺴﺐ ﺭﻭﺵ ﺍﻧﺘﻘﺎﻝ ﺑﺸﺮﺡ ﺯﻳﺮ ﻣﻴﺒﺎﺷﻨﺪ‪:‬‬
‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ‪RS485‬‬ ‫‪١-٣-٢‬‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺑﺼﻮﺭﺕ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺍﺳﺖ‪ .‬ﻛﺎﺑﻞ ‪ ،‬ﻛﺎﻧﻜﺘﻮﺭ ‪ ،‬ﺭﻳﭙﻴﺘﺮ ﺍﺯ ﻋﻤﺪﻩ‬
‫ﺍﺟﺰﺍﻱ ﺍﻳﻦ ﺷﺒﻜﻪ ﻣﺤﺴﻮﺏ ﻣﻴﮕﺮﺩﻧﺪ‪.‬‬
‫‪RS485‬‬ ‫ﻛﺎﺑﻞ ﺷﺒﻜﻪ‬
‫ﻛﺎﺑﻞ ﻣﺴﻲ ﺩﺭ ﺷﺒﻜﻪ ‪ PREOFIBUS‬ﻳﻚ ﻛﺎﺑﻞ ﺩﻭ ﺭﺷﺘﻪ ﺷﻴﻠﺪﺩﺍﺭ ﻳﺎ ‪ STP‬ﺍﺳﺖ‪ .‬ﻣﺸﺨﺼﺎﺕ ﺍﺻﻠﻲ ﺍﻳﻦ ﻛﺎﺑﻞ ﻃﺒﻖ‬
‫ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺩﺭ ﺑﺨﺶ ﻗﺒﻞ ﺫﻛﺮ ﮔﺮﺩﻳﺪ‪.‬ﺍﻣﺮﻭﺯﻩ ﻛﺎﺑﻞ ﻫﺎﻱ ﻣﺘﻨﻮﻋﻲ ﺗﻮﺳﻂ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﺘﻠﻒ ﺟﻬﺖ ﺍﺳﺘﻔﺎﺩﻩ ﺩﺭ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻋﺮﺿﻪ ﻣﻴﺸﻮﺩ‪ .‬ﺑﺮﺧﻲ ﺍﺯ ﺍﻳﻦ ﻛﺎﺑﻠﻬﺎ ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﺧﺎﺹ ﺩﺍﺭﻧﺪ ﺩﺭ ﻣﻘﺎﺑﻞ ﺁﺗﺶ ﺳﻮﺯﻱ ﻳﺎ ﺗﻤﺎﺱ ﺑﺎ ﻣﻮﺍﺩ‬
‫ﺷﻴﻤﻴﺎﻳﻲ ﻣﻘﺎﻭﻡ ﺗﺮ ﻫﺴﺘﻨﺪ‪ .‬ﺑﺴﺘﻪ ﺑﻪ ﻛﺎﺭﺑﺮﺩ ﺑﺎﻳﺪ ﻛﺎﺑﻞ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﻮﺩ‪.‬‬

‫ﻛﺎﻧﻜﺘﻮﺭ ‪RS485‬‬
‫ﻛﺎﻧﻜﺘﻮﺭ ﻫﺎﻱ ‪ PROFIBUS‬ﺑﺼﻮﺭﺕ ‪ ٩‬ﭘﻴﻦ ‪ male‬ﺑﻮﺩﻩ ﻭ ﺩﺍﺭﺍﻱ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻒ ﻫﺴﺘﻨﺪ ﻛﻪ ﻛﺎﺭﺑﺮﺩ ﺁﻧﻬﺎ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ﺑﻴﺸﺘﺮ‬
‫ﺍﻳﻦ ﻛﺎﻧﻜﺘﻮﺭﻫﺎ ﺩﺍﺭﺍﻱ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﻫﺴﺘﻨﺪ ﻭ ﺳﻮﺋﻴﭽﻲ ﺭﻭﻱ ﺁﻧﻬﺎ ﺑﺮﺍﻱ ‪ ON/OFF‬ﻛﺮﺩﻥ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪ .‬ﺑﺮﺧﻲ ﺍﺯ ﺍﻧﻮﺍﻉ‬
‫ﻛﺎﻧﻜﺘﻮﺭ ﻫﺎ ﭘﻮﺭﺗﻲ ﺩﺭ ﭘﺸﺖ ﺩﺍﺭﻧﺪ ﻛﻪ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﺁﻥ ‪ PG‬ﻳﺎ ‪ PC‬ﺭﺍ ﻧﻴﺰ ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪.‬‬

‫ﺷﺪﻩ ﺍﻧﺪ ﻣﺎﻧﻨﺪ ‪ 830-1‬ﻭ ‪830-2‬‬ ‫ﺷﺎﻳﺎﻥ ﺫﻛﺮ ﺍﺳﺖ ﺑﺮﺧﻲ ﺍﺯ ﻛﺎﺑﻠﻬﺎﻱ ﻣﺠﻬﺰﺑﻪ ﻛﺎﻧﻜﺘﻮﺭ ﻧﻴﺰ ﻋﺮﺿﻪ‬
‫‪Techno-Electro.com‬‬

‫‪٤٩‬‬ ‫‪RS485‬‬ ‫ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ‬

‫ﺭﻳﭙﻴﺘﺮ ‪RS485‬‬
‫ﻟﺘﺒﺘﺒﻠﺘﺒﺘﺒﺘﻠﺒﺘﺒﺘﺒﺘﺒﺘﺒﺘﺒﺘﺒﯿﻼﺑﺘﻞ‬ ‫ﻛﺎﺭﺑﺮﺩ ﺭﻳﭙﻴﺘﺮ ﺩﺭ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺍﺳﺖ ‪:‬‬
‫ﻭﻗﺘﻲ ﺑﻴﺶ ﺍﺯ ‪ Node ٣٢‬ﺭﻭﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬‬ ‫•‬

‫ﻭﻗﺘﻲ ﻧﻴﺎﺯ ﺑﺎﺷﺪ ﺳﮕﻤﻨﺖ ﻫﺎﻱ ﺑﺎﺱ ﺍﺯ ﻳﻜﺪﻳﮕﺮ ﺑﺼﻮﺭﺕ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺍﻳﺰﻭﻟﻪ ﺷﻮﻧﺪ‪.‬‬ ‫•‬

‫ﻭﻗﺘﻲ ﺗﻌﺪﺍﺩ ‪ Node‬ﻫﺎ ﻛﻤﺘﺮ ﺍﺯ ‪ ٣٢‬ﻭﻟﻲ ﻃﻮﻝ ﻛﺎﺑﻞ ﺑﻪ ﺣﺪ ﻣﺎﻛﺰﻳﻤﻢ ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺯﻳﺮ ﺭﺳﻴﺪﻩ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﺳﺮﻋﺖ اﻧﺘﻘﺎل‬ ‫ﻣﺎﮐﺰﻳﻤﻢ ﻃﻮل ﮐﺎﺑﻞ در هﺮ ﺳﮕﻤﻨﺖ ﺑﺮ ﺣﺴﺐ ﻣﺘﺮ‬

‫‪9.6 to 93.75 Kbps‬‬ ‫‪1000‬‬
‫‪187.5‬‬ ‫‪Kbps‬‬ ‫‪800‬‬
‫‪500‬‬ ‫‪Kbps‬‬ ‫‪400‬‬
‫‪1.5‬‬ ‫‪Mbps‬‬ ‫‪200‬‬
‫‪3 to 12 Mbps‬‬ ‫‪100‬‬

‫ﺣﺪﺍﻛﺜﺮ ‪ ٩‬ﻋﺪﺩ ﺭﻳﭙﻴﺘﺮ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ Profibus‬ﺳﺮﻱ ﻛﺮﺩ‪ .‬ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ‪ Node‬ﻧﺒﺎﻳﺪ ﺍﺯ ﻣﻘﺎﺩﻳﺮ‬
‫ﻣﻨﺪﺭﺝ ﺯﻳﺮ ﺑﻴﺸﺘﺮ ﺑﺎﺷﺪ‪.‬‬
‫ﺳﺮﻋﺖ انﺘﻘﺎل‬ ‫ﻣﺎﮐﺰﻳﻤﻢ ﻃﻮل ﮐﺎﺑﻞ ﺑﻴﻦ دو ‪ Node‬ﺑﺮ ﺣﺴﺐ ﻣﺘﺮ‬
‫‪9.6 to 93.75‬‬ ‫‪kbps‬‬ ‫‪10000‬‬
‫‪187.5‬‬ ‫‪kbps‬‬ ‫‪8000‬‬
‫‪500‬‬ ‫‪kbps‬‬ ‫‪4000‬‬
‫‪1.5‬‬ ‫‪kbps‬‬ ‫‪2000‬‬
‫‪3 to 12‬‬ ‫‪kbps‬‬ ‫‪1000‬‬

‫ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﻛﻪ ﺑﺎﻳﺪ ﺑﺮﺍﻱ ﺗﻤﺎﻡ ﻋﻨﺎﺻﺮ ﺷﺒﻜﻪ ﻳﻜﺴﺎﻥ ﺍﻧﺘﺨﺎﺏ ﺷﻮﺩ ﺑﺮﺍﻱ ﺭﻳﭙﻴﺘﺮ ﺑﺎ ﺳﻮﺋﻴﭽﻲ ﻛﻪ ﺭﻭﻱ ﺁﻥ ﺗﻌﺒﻴﻪ ﺷﺪﻩ ﺑﻴﻦ‬
‫‪ 9.6 Kbps‬ﺗﺎ ‪ 12 Mbps‬ﻗﺎﺑﻞ ﺍﻧﺘﺨﺎﺏ ﺍﺳﺖ‬
‫ﻻﺯﻡ ﺑﻪ ﺫﻛﺮ ﺍﺳﺖ ﺩﺭ ﻣﺤﻞ ﺍﺗﺼﺎﻝ ﻫﺮ ﺳﮕﻤﻨﺖ ﺑﻪ ﺭﻳﭙﻴﺘﺮ ﻳﻚ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺎﻳﺪ‬
‫ﺁﻧﻬﺎ ﺭﺍ ‪ ON‬ﻳﺎ ‪ OFF‬ﻧﻤﻮﺩ‪ .‬ﺗﻮﺿﻴﺤﺎﺕ ﺑﻴﺸﺘﺮ ﺩﺭ ﺑﺨﺶ ﺑﻌﺪ ﺁﻣﺪﻩ ﺍﺳﺖ‬
‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬ ‫‪٥٠‬‬

‫‪ ٢-٣-٢‬ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬
‫‪Active‬‬ ‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺭﺍ ﻧﻴﺰ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ‪ Active‬ﻭ ‪ Passive‬ﺗﻘﺴﻴﻢ ﻛﺮﺩ‪ OBT .‬ﻭ ‪ OLM‬ﻭ ﺍﺯ ﺍﺟﺰﺍﻱ‬
‫ﻭ ﻛﺎﺑﻞ ﻭ ﻛﺎﻧﻜﺘﻮﺭ ﻧﻮﺭﻱ ﺍﺯ ﺍﺟﺰﺍﻱ ‪ Passive‬ﻫﺴﺘﻨﺪ ﻛﻪ ﺩﺭ ﺯﻳﺮ ﺗﺸﺮﻳﺢ ﺷﺪﻩ ﺍﻧﺪ‪ .‬ﻋﻼﻭﻩ ﺑﺮ ﺍﻳﻨﻬﺎ ﻛﺎﺭﺗﻬﺎﻱ ‪ CP‬ﻭ ‪ IM‬ﻫﺎﻳﻲ‬
‫ﻛﻪ ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﻛﺪ ﺁﻧﻬﺎ ﻛﻠﻤﻪ ‪ FO‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﺍﺯ ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ﻣﺤﺴﻮﺏ ﻣﻴﺸﻮﻧﺪ‪.‬‬

‫‪OBT‬‬
‫‪ OBT‬ﻛﻪ ﻣﺨﻔﻒ ‪ Optical Bus Terminal‬ﺍﺳﺖ ﻭﺳﻴﻠﻪ ﺍﻱ ﺍﺳﺖ ﻛﻪ ﺗﻮﺳﻂ ﺁﻥ ﻣﻴﺘﻮﺍﻥ‬
‫ﻳﻚ ‪ Node‬ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ RS485‬ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪ OBT .‬ﻋﻼﻭﻩ ﺑﺮﺍﻳﻦ‬
‫‪PROFIBUS‬‬ ‫ﺍﺗﺼﺎﻝ ﻧﻘﺶ ﻳﻚ ﺭﻳﭙﻴﺘﺮ ﺭﺍ ﻧﻴﺰ ﺑﺎﺯﻱ ﻣﻴﻜﻨﺪ‪ .‬ﻓﺮﺽ ﻛﻨﻴﺪ ﺷﺒﻜﻪ ﺍﻱ ﻧﻮﺭﻱ ﺑﺮﺍﻱ‬
‫ﺩﺍﺭﻳﻢ ﻛﻪ ﺩﺭ ﺁﻥ ﺑﺮﺧﻲ ﺍﺯ ﺗﺠﻬﻴﺰﺍﺕ ﻣﺴﺘﻘﻴﻤﺎ ﺑﻪ ﺁﻥ ﻣﺘﺼﻞ ﺷﺪﻩ ﺍﻧﺪ‪ .‬ﻭﻟﻲ ﺑﺮﺧﻲ ﺩﻳﮕﺮ‬
‫ﺩﺍﺭﺍﻱ ﺍﺭﺗﺒﺎﻁ ﻧﻮﺭﻱ ﻧﻴﺴﺘﻨﺪ ﻭ ﻓﻘﻂ ﭘﻮﺭﺕ ‪ RS485‬ﺩﺍﺭﻧﺪ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺑﺎ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OBT‬ﺗﺠﻬﻴﺰﺍﺕ ﻓﻮﻕ ﺭﺍ ﺑﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻣﺘﺼﻞ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺍﺗﺼﺎﻝ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺑﻪ ﭘﻮﺭﺕ‬
‫)‪(PCF‬‬ ‫‪ ٩‬ﭘﻴﻦ ‪ RS485‬ﻭﺻﻞ ﻣﻴﺸﻮﺩ ﻭ ﺩﻭ ﻣﺤﻞ ﺍﺗﺼﺎﻝ ﻧﻴﺰ ﺑﺮﺍﻱ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺩﺍﺭﺩ‪.‬ﻓﻘﻂ ﻛﺎﺑﻠﻬﺎﻱ ﻧﻮﺭﻱ ﭘﻼﺳﺘﻴﻜﻲ ﻭ ﭘﻠﻴﻤﺮﻱ‬
‫ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﺍﻳﻦ ﻭﺳﻴﻠﻪ ﻣﺘﺼﻞ ﻛﺮﺩ ﻭ ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺷﻴﺸﻪ ﺍﻱ ﺑﻪ ﺁﻥ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﺍﺯ ﻫﻤﻴﻨﺠﺎ ﻣﺸﺨﺺ ﺍﺳﺖ ﻛﻪ‬
‫‪ OBT‬ﺑﺮﺍﻱ ﻃﻮﻝ ﻣﺤﺪﻭﺩﻱ ﺍﺯ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻜﺎﺭ ﺭﻭﺩ )‪ ٥٠‬ﻣﺘﺮ ﺑﺮﺍﻱ ﻓﻴﺒﺮ ﭘﻼﺳﺘﻴﻜﻲ ﻭ ‪ ٣٠٠‬ﻣﺘﺮ ﺑﺮﺍﻱ ﻓﻴﺒﺮ ‪. ( PCF‬‬
‫‪ OBT‬ﺗﻤﺎﻡ ﺳﺮﻋﺘﻬﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺩﺭ ‪ PROFIBUS‬ﺭﺍ ﺳﺎﭘﻮﺭﺕ ﻣﻴﻜﻨﺪ ﻳﻌﻨﻲ ﺍﺯ ‪ 9.6 Kbps‬ﺗﺎ ‪. 12 Mbps‬‬
‫‪Terminator‬‬ ‫ﻧﻜﺘﻪ ﻣﻬﻢ ﺩﻳﮕﺮ ﻛﻪ ﺑﺎﻳﺪ ﺑﻪ ﺁﻥ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﺍﻳﻨﺴﺖ ﻛﻪ ﺩﻭ ﻃﺮﻑ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﻣﺘﺼﻞ ﺑﻪ ‪ OBT‬ﺑﺎﻳﺪ ﺗﻮﺳﻂ‬
‫ﺑﺴﺘﻪ ﺷﻮﺩ‪.‬‬

‫‪1) Electrical Cable‬‬ ‫‪2)FO Cable‬‬

‫‪Techno-Electro.com‬‬

‫‪٥١‬‬ ‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫‪OLM‬‬
‫‪ OLM‬ﻛﻪ ﻣﺨﻔﻒ ‪Optical Link Module‬ﺍﺳﺖ ﻧﻴﺰﻭﺳﻴﻠﻪ ﺍﻱ ﺍﺳﺖ ﻛﻪ ﺗﻮﺳﻂ ﺁﻥ ﻣﻴﺘﻮﺍﻥ‬
‫ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ RS485‬ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪ .‬ﺑﺮ ﺧﻼﻑ ‪ OBT‬ﻫﺮ ﺳﻪ ﻧﻮﻉ ﻓﻴﺒﺮ‬
‫ﻧﻮﺭﻱ ﭘﻼﺳﺘﻴﻜﻲ‪ ،‬ﭘﻠﻴﻤﺮﻱ ﻭ ﺷﻴﺸﻪ ﺍﻱ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﺁﻥ ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪.‬‬
‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OLM‬ﻣﻴﺘﻮﺍﻥ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺑﺎﺱ ﻭ ﺳﺘﺎﺭﻩ ﻭ ﻫﻤﭽﻨﻴﻦ ﺣﻠﻘﻮﻱ ﺩﻭﺑﻞ ﺑﺮﻗﺮﺍﺭ ﻛﺮﺩ‪.‬‬
‫ﺑﺴﻴﺎﺭﻱ ﺍﺯ ‪ OLM‬ﻫﺎ ﺩﺍﺭﺍﻱ ﻳﻚ ﺧﺮﻭﺟﻲ ﺑﺮﺍﻱ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﺳﻴﮕﻨﺎﻝ ﻫﺴﺘﻨﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺧﺮﻭﺟﻲ‬
‫ﻣﻴﺘﻮﺍﻥ ﻛﻴﻔﻴﺖ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﺭﺍ ﭼﻚ ﻛﺮﺩ ﺧﺮﻭﺟﻲ ﺗﻮﺳﻂ ﻭﻟﺘﻤﺘﺮ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﻣﻴﺸﻮﺩ ﻭ ﺑﺎ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﻨﺤﻨﻲ ﻛﻴﻔﻴﺖ ﺳﻴﮕﻨﺎﻝ ﻛﻪ ﺩﺭ ﺑﺨﺶ ‪ ١٠‬ﺁﻣﺪﻩ ﺍﺳﺖ ﻭﺿﻌﻴﺖ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ‬
‫ﻣﺸﺨﺺ ﻣﻴﮕﺮﺩﺩ‪.‬‬
‫ﻛﺎﻧﻜﺘﻮﺭ ﻱ ﻛﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺭﺍ ﺑﻪ ‪ OLM‬ﻣﺘﺼﻞ ﻣﻴﻜﻨﺪ ﺑﺎﻳﺪ ﺍﺯ ﻧﻮﻉ ‪ BFOC‬ﻛﻪ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ‬
‫ﺫﻛﺮ ﺷﺪﻩ ﺑﺎﺷﺪ‪ OLM .‬ﻫﺎ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻒ ﺩﺍﺭﻧﺪ ﻛﻪ ﻗﺎﺑﻠﻴﺖ ﻫﺎﻱ ﺁﻧﻬﺎ ﺑﺎ ﻫﻢ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ‪.‬‬
‫ﻣﻬﻤﺘﺮﻳﻦ ﻭﻳﮋﮔﻴﻬﺎﻱ ‪ OLM‬ﻫﺎﻱ ﻋﺮﺿﻪ ﺷﺪﻩ ﺗﻮﺳﻂ ﺯﻳﻤﻨﺲ ﺩﺭ ﺟﺪﻭﻝ ﺯﻳﺮ ﻣﻘﺎﻳﺴﻪ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪OLM/‬‬ ‫‪P11‬‬ ‫‪P 12‬‬ ‫‪G11‬‬ ‫‪G12‬‬ ‫‪G11-1300‬‬ ‫‪G12–1300‬‬

‫‪G12-EEC‬‬
‫‪Number of ports‬‬
‫‪– electrical‬‬ ‫‪1‬‬ ‫‪1‬‬ ‫‪1‬‬ ‫‪1‬‬ ‫‪1‬‬ ‫‪1‬‬
‫‪– optical‬‬ ‫‪1‬‬ ‫‪2‬‬ ‫‪1‬‬ ‫‪2‬‬ ‫‪1‬‬ ‫‪2‬‬
‫‪Fiber types‬‬
‫‪– Plastic optical fibers‬‬
‫‪980/1000 µm‬‬ ‫‪80 m‬‬ ‫‪80 m‬‬ ‫–‬ ‫–‬ ‫–‬ ‫–‬
‫‪– PCF optical fibers‬‬
‫‪200/230 µm‬‬ ‫‪400 m‬‬ ‫‪400 m‬‬ ‫–‬ ‫–‬ ‫–‬ ‫–‬
‫‪Quartz glass optical fibers‬‬
‫‪10/125 µm‬‬ ‫–‬ ‫–‬ ‫–‬ ‫–‬ ‫‪15 km‬‬ ‫‪15 km‬‬
‫‪50/125 µm‬‬ ‫–‬ ‫–‬ ‫‪3000 m‬‬ ‫‪3000 m‬‬ ‫‪10 km‬‬ ‫‪10 km‬‬
‫‪62.5/125 µm‬‬ ‫–‬ ‫–‬ ‫‪3000 m‬‬ ‫‪3000 m‬‬ ‫‪10 km‬‬ ‫‪10 km‬‬

‫‪ OLM‬ﻫﺎ ﺗﻤﺎﻡ ﺳﺮﻋﺖ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺩﺭ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺭﺍ ﺳﺎﭘﻮﺭﺕ ﻣﻴﻜﻨﻨﺪ ﻳﻌﻨﻲ ﺍﺯ ‪ 9.6 Kbps‬ﺗﺎ ‪. 12 Kbps‬‬
‫ﻳﻜﻲ ﺩﻳﮕﺮ ﺍﺯ ﻭﻳﮋﮔﻲ ﻫﺎﻱ ﻣﻬﻢ ‪ OLM‬ﺗﻮﺍﻧﺎﻳﻲ ﺟﺪﺍ ﻛﺮﺩﻥ ﺑﺎﺱ ﺩﺭ ﻣﻮﻗﻊ ﺑﺮﻭﺯ ﻓﺎﻟﺖ ﺍﺳﺖ‪ .‬ﻳﻌﻨﻲ ﺑﻤﺤﺾ ﺍﻳﻨﻜﻪ ﺧﻄﺎﻳﻲ ﺭﺍ ﺩﺭ‬
‫ﻛﺎﻧﺎﻟﻲ ﺗﺸﺨﻴﺺ ﺩﻫﺪ ﺁﻥ ﻛﺎﻧﺎﻝ ﺭﺍ ﺑﻠﻮﻛﻪ ﻣﻴﻜﻨﺪ‪ .‬ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖ ﺑﺎﻋﺚ ﻣﻴﺸﻮﺩ ﻛﻪ ﻳﻚ ﺷﺒﻜﻪ ﺣﻠﻘﻮﻱ ﺩﺭ ﺻﻮﺭﺕ ﺑﺮﻭﺯ ﺧﻄﺎ ﺑﻄﻮﺭ‬
‫ﺍﺗﻮﻣﺎﺗﻴﻚ ﺗﺒﺪﻳﻞ ﺑﻪ ﺑﺎﺱ ﺷﺪﻩ ﻭ ﺑﻪ ﻛﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﺩﻫﺪ‪.‬‬
‫ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ RS485‬ﺩﺭ ﻣﻮﻗﻊ ﺍﺗﺼﺎﻝ ﺑﻪ ‪ OLM‬ﻻﺯﻡ ﺍﺳﺖ ﺗﻮﺳﻂ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺑﺴﺘﻪ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬ ‫‪٥٢‬‬

‫‪OLP‬‬
‫‪ OLP‬ﻛﻪ ﻣﺨﻔﻒ ‪Optical Link Plug‬ﺍﺳﺖ ﻛﺎﻧﻜﺘﻮﺭﻱ ﺍﺳﺖ ﻛﻪ ﻣﺴﺘﻘﻴﻤﹰﺎ ﺍﺯ‬
‫ﻳﻜﻄﺮﻑ ﺑﻪ ﭘﻮﺭﺕ ‪ RS485‬ﻭ ﺍﺯ ﻃﺮﻑ ﺩﻳﮕﺮ ﺑﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﭘﻼﺳﺘﻴﻜﻲ ﻣﺘﺼﻞ‬
‫ﻣﻴﮕﺮﺩﺩ‪ OLP .‬ﻣﻴﺘﻮﺍﻧﺪ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ‪ OLM‬ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪ .‬ﺷﺮﺍﻳﻄﻲ ﻛﻪ ﺑﺮﺍﻱ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OLP‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬

‫ﻭﺳﻴﻠﻪ ﻣﻮﺭﺩ ﻧﻈﺮ ﺩﺍﺭﺍﻱ ﭘﻮﺭﺕ ‪ RS485‬ﺑﺼﻮﺭﺕ ﻛﺎﻧﻜﺘﻮﺭ ‪ Female‬ﻧﻪ ﭘﻴﻦ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﺍﺭﺗﺒﺎﻁ ‪ PROFIBUS‬ﺩﺭ ﺁﻥ ﻧﻘﻄﻪ ﺗﻮﺍﻧﺎﻳﻲ ﺗﻐﺬﻳﻪ ‪ 80mA‬ﺭﺍ ﺑﺎ ﻭﻟﺘﺎﮊ ‪ 5‬ﻭﻟﺖ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ )ﭘﻴﻦ ﻫﺎﻱ ‪ ٥‬ﻭ ‪( ٦‬‬ ‫•‬

‫ﻭﺳﻴﻠﻪ ﻣﻮﺭﺩ ﻧﻈﺮ ﻳﻚ ﻭﺳﻴﻠﻪ ‪ Passive‬ﺭﻭﻱ ﺷﺒﻜﻪ ‪ Profibus‬ﺑﺎﺷﺪ‪ ).‬ﻳﻚ ‪ Slave‬ﻣﺎﻧﻨﺪ ‪ (ET200‬ﺍﻟﺒﺘﻪ ﺍﮔﺮ‬ ‫•‬
‫‪ OLP‬ﺑﺼﻮﺭﺕ ﻧﻘﻄﻪ ﺑﻪ ﻧﻘﻄﻪ ﺑﻪ ‪ OLM‬ﻭﺻﻞ ﺷﻮﺩ ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ﻃﺮﻑ ﺩﻳﮕﺮ ﺑﻪ ﻳﻚ ‪ Master‬ﻣﺘﺼﻞ ﺑﺎﺷﺪ‪ .‬ﺟﺪﻭﻝ‬
‫ﺯﻳﺮ ﺍﻣﻜﺎﻥ ﺍﺭﺗﺒﺎﻁ ‪ OLP‬ﺭﺍ ﺑﻪ ﻭﺳﺎﻳﻞ ﻣﺨﺘﻠﻒ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪Device Name‬‬ ‫‪Master Slave‬‬ ‫‪OLP can be used‬‬
‫‪SIMATIC S5‬‬
‫‪IM 308–C‬‬ ‫‪M+S‬‬ ‫‪yes‬‬
‫‪CP 5431 FMS/DP‬‬ ‫‪M‬‬ ‫‪yes‬‬
‫‪S5–95U/DP‬‬ ‫‪M+S‬‬ ‫‪yes‬‬
‫‪SIMATIC S7–300‬‬
‫‪CP 342–5‬‬ ‫‪M+S‬‬ ‫‪yes‬‬
‫‪CPU 314‬‬ ‫‪M‬‬ ‫‪yes‬‬
‫‪CPU 315–2–DP‬‬ ‫‪M+S‬‬ ‫‪yes‬‬
‫‪SIMATIC S7–400‬‬
‫‪CP 343–5‬‬ ‫‪M‬‬ ‫‪yes‬‬
‫‪CP 443–5‬‬ ‫‪M+S‬‬ ‫‪yes‬‬
‫‪CPU 413–2 DP‬‬ ‫‪M‬‬ ‫‪no‬‬
‫‪CPU 414–2 DP‬‬ ‫‪M‬‬ ‫‪no‬‬
‫‪PC Modules‬‬
‫‪CP 5412 A2‬‬ ‫‪M‬‬ ‫‪yes‬‬
‫‪CP 5411‬‬ ‫‪M‬‬ ‫‪yes‬‬
‫‪Distributed I/Os‬‬
‫‪ET 200M, IM 153‬‬ ‫‪S‬‬ ‫‪yes‬‬
‫‪ET 200U, IM 318–C‬‬ ‫‪S‬‬ ‫‪yes‬‬
‫‪ET 200B‬‬ ‫‪S‬‬ ‫‪yes‬‬
‫‪ET 200L‬‬ ‫‪S‬‬ ‫‪no‬‬
‫‪ET 200C‬‬ ‫‪S‬‬ ‫‪no‬‬
‫‪ET 200X‬‬ ‫‪S‬‬ ‫‪no‬‬
‫‪Miscellaneous‬‬
‫‪Repeater RS 485‬‬ ‫–‬ ‫‪yes‬‬
‫‪OLM, channel 1‬‬ ‫–‬ ‫‪no‬‬
‫‪Techno-Electro.com‬‬

‫‪٥٣‬‬ ‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﻛﺎﺑﻞ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﻛﺎﺑﻞ ﻫﺎﻱ ﻧﻮﺭﻱ ﻫﻤﺎﻧﻨﺪ ﻛﺎﺑﻞ ﻫﺎﻱ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺩﺭ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻒ ﻭ ﺗﻮﺳﻂ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﻠﻒ ﻋﺮﺿﻪ ﻣﻴﺸﻮﻧﺪ‪ .‬ﺑﺮﺧﻲ ﺍﺯ ﻭﻳﮋﮔﻲ‬
‫ﻫﺎﻳﻲ ﻛﻪ ﺍﻧﻮﺍﻉ ﻛﺎﺑﻠﻬﺎ ﻱ ﻧﻮﺭﻱ ﺭﺍ ﺍﺯ ﻫﻢ ﻣﺘﻤﺎﻳﺰ ﻣﻴﻜﻨﺪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫ﺟﻨﺲ ﻫﺴﺘﻪ‬ ‫•‬

‫ﺿﺨﺎﻣﺖ ﻫﺴﺘﻪ‬ ‫•‬

‫ﺗﻌﺪﺍﺩ ﺭﺷﺘﻪ‬ ‫•‬

‫ﭘﻮﺷﺶ ﻛﺎﺑﻞ‬ ‫•‬

‫ﺍﻭﻟﻴﻦ ﻓﺎﻛﺘﻮﺭ ﺩﺭ ﺍﻧﺘﺨﺎﺏ ﻛﺎﺑﻞ ﻫﺎﻱ ﻧﻮﺭﻱ ﺟﻨﺲ ﻫﺴﺘﻪ ﺍﺳﺖ ﻛﻪ ﻣﻴﺘﻮﺍﻧﺪ ﭘﻼﺳﺘﻴﻜﻲ ﻳﺎ ﭘﻠﻴﻤﺮﻱ ﻳﺎ ﺷﻴﺸﻪ ﺍﻱ ﺑﺎﺷﺪ ‪ .‬ﻧﻮﻉ‬
‫ﭘﻼﺳﺘﻴﻜﻲ ﺑﺮﺍﻱ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻛﻮﺗﺎﻩ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻭ ﺿﺨﺎﻣﺖ ﻫﺴﺘﻪ ﺁﻥ ﺑﻴﺶ ﺍﺯ ﺳﺎﻳﺮﻳﻦ )‪ ٩٨٠‬ﻣﻴﻜﺮﻭﻣﺘﺮ( ﺍﺳﺖ‪ .‬ﻧﻮﻉ ﺷﻴﺸﻪ ﺍﻱ ﺑﺮﺍﻱ‬
‫ﻣﺴﺎﻓﺘﻬﺎﻱ ﻃﻮﻻﻧﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﻭ ﺿﺨﺎﻣﺖ ﻫﺴﺘﻪ ﺁﻥ ﻛﻤﺘﺮ ﺍﺯ ﺑﻘﻴﻪ ﺍﺳﺖ )‪ ٦٢,٥‬ﻣﻴﻜﺮﻭﻣﺘﺮ(‪ .‬ﻧﻮﻉ ﭘﻠﻴﻤﺮ ﻭﻳﮋﮔﻴﻬﺎﻳﻲ ﺑﻴﻦ ﺍﻧﻮﺍﻉ‬
‫ﭘﻼﺳﺘﻴﻜﻲ ﻭ ﺷﻴﺸﻪ ﺍﻱ ﺩﺍﺭﺩ‪.‬‬

‫ﻛﺎﻧﻜﺘﻮﺭﻫﺎﻱ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫‪ IM467 FO‬ﻭ ‪IM153-2 FO‬‬ ‫ﻛﺎﻧﻜﺘﻮﺭﻫﺎﻱ ﺑﺼﻮﺭﺕ ‪ Simplex‬ﻫﺴﺘﻨﺪ ﻭﻟﻲ ﺑﺮﺧﻲ ﺍﺯ ﺁﻧﻬﺎ ﺑﺮﺍﻱ ﻛﺎﺭﺗﻬﺎﻱ ﺧﺎﺹ ﻣﺎﻧﻨﺪ‬
‫‪Simplex‬‬ ‫ﺑﺎﻳﺪ ﻫﻤﺮﺍﻩ ﺑﻪ ﺁﺩﺍﭘﺘﻮﺭ ﺑﺴﺘﻪ ﺷﻮﻧﺪ‪ .‬ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ﺩﻗﻴﻖ ﻣﺜﻼ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﺩﻭ ‪ OLM‬ﺑﺎ ﻣﺴﺎﻓﺖ ﺯﻳﺎﺩ‪ ،‬ﻛﺎﻧﻜﺘﻮﺭﻫﺎﻱ‬
‫ﻣﻨﺎﺳﺐ ﻧﻴﺴﺘﻨﺪ ﻭ ﺑﺎﻳﺪ ﺍﺯ ﻧﻮﻉ ‪ BFOC‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪.‬‬

‫‪BFOC‬‬ ‫‪Simplex with Adaptor‬‬ ‫‪Simplex‬‬

‫‪Techno-Electro.com‬‬

‫ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ‬ ‫‪٥٤‬‬

‫‪ ٣-٣-٢‬ﺍﺟﺰﺍﻱ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ‬
‫ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ ﻛﻪ ﺑﺮﺍﻱ ‪ PROFIBUS‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﻣﺒﺘﻨﻲ ﺑﺮ‬
‫ﺭﻭﺵ ﺍﻧﺘﻘﺎﻝ ﻧﻮﺭ ﻣﺎﺩﻭﻥ ﻗﺮﻣﺰ ﺍﺳﺖ‪ .‬ﻣﺴﺎﻓﺖ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﺍﻳﻦ‬
‫ﺭﻭﺵ ﻛﻢ ﻭ ﺣﺪﺍﻛﺜﺮ ﺗﺎ ‪ ١٥‬ﻣﺘﺮ ﺍﺳﺖ ﻭ ﺑﺮﺍﻱ ﺩﺳﺘﮕﺎﻫﻬﺎﻱ‬
‫ﻣﺘﺤﺮﻙ ﻳﺎ ﭼﺮﺧﺎﻥ ﺑﺎ ﻓﺎﺻﻠﻪ ﻧﺰﺩﻳﻚ ﻣﻨﺎﺳﺐ ﺍﺳﺖ‪ .‬ﻭﺳﻴﻠﻪ ﺍﻱ ﻛﻪ‬
‫‪Infrared Link‬‬ ‫ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ‪ILM‬ﺩﺍﺭﺩ ﻛﻪ ﻣﺨﻔﻒ‬
‫‪ Module‬ﺍﺳﺖ‪ ILM .‬ﻫﺎ ﺑﺼﻮﺭﺕ ﺟﻔﺘﻲ ﺑﻜﺎﺭ ﻣﻴﺮﻭﻧﺪ ﻭ ﺑﺮﺍﻱ‬
‫ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺑﺎﻳﺪ ﻳﻜﺪﻳﮕﺮ ﺭﺍ ﺑﺒﻴﻨﻨﺪ‪ .‬ﻳﻌﻨﻲ ﻣﺎﻧﻌﻲ ﺑﻴﻦ ﺁﻧﻬﺎ ﻭﺟﻮﺩ‬
‫ﻧﺪﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬ﺍﺻﻮﻝ ﻛﺎﺭ ﺑﺪﻳﻦ ﻧﺤﻮ ﺍﺳﺖ ﻛﻪ ﺳﻴﮕﻨﺎﻝ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ RS485‬ﺗﻮﺳﻂ ﻛﺎﺑﻞ ﺑﻪ ‪ ILM‬ﺍﺭﺳﺎﻝ ﻣﻴﮕﺮﺩﺩ‪ ILM .‬ﺁﻧﺮﺍ ﺑﻪ‬
‫ﻧﻮﺭ ﻣﺎﺩﻭﻥ ﻗﺮﻣﺰ ﺗﺒﺪﻳﻞ ﻛﺮﺩﻩ ﻭ ﺑﻪ ‪ ILM‬ﺩﻳﮕﺮ ﺍﺭﺳﺎﻝ ﻣﻴﺪﺍﺭﺩ‪ ILM .‬ﮔﻴﺮﻧﺪﻩ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﺑﺎﺯ ﻳﺎﺑﻲ ﻛﺮﺩﻩ ﻭ ﻣﺠﺪﺩﺍ ﺑﻪ ﺻﻮﺭﺕ‬
‫ﺍﻟﻜﺘﺮﻳﻜﻲ ﺭﻭﻱ ﻛﺎﺑﻞ ‪ PROFIBUS‬ﻣﻴﻔﺮﺳﺘﺪ‪ .‬ﺭﻭﺵ ﺍﻧﺘﻘﺎﻝ ﺑﺼﻮﺭﺕ ‪ Half Duplex‬ﺍﺳﺖ ‪ .‬ﻳﻌﻨﻲ ﺩﺭ ﻫﺮ ﻟﺤﻈﻪ ﻓﻘﻂ ﻳﻚ‬
‫‪ ILM‬ﻣﻴﺘﻮﺍﻧﺪ ﻓﺮﺳﺘﻨﺪﻩ ﺑﺎﺷﺪ‪.‬ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺑﻴﻦ ‪ 9600 bps‬ﺗﺎ ‪ 1.5 Mbps‬ﻭ ﺗﻮﺳﻂ ﺳﻮﺋﻴﭻ ﻫﺎﻱ ‪ 1,2,3‬ﺭﻭﻱ ‪ ILM‬ﻗﺎﺑﻞ‬
‫ﺗﻨﻈﻴﻢ ﺍﺳﺖ ﻣﻄﺎﺑﻖ ﺷﻜﻞ ﻭ ﺟﺪﻭﻝ ﺯﻳﺮ‪:‬‬
‫‪1‬‬ ‫‪2‬‬ ‫‪3‬‬
‫‪0‬‬ ‫‪0‬‬ ‫‪0‬‬ ‫‪1.5 Mbps‬‬
‫‪1‬‬ ‫‪0‬‬ ‫‪0‬‬ ‫‪500 Kbps‬‬
‫‪0‬‬ ‫‪1‬‬ ‫‪0‬‬ ‫‪187.5 Kbps‬‬
‫‪1‬‬ ‫‪1‬‬ ‫‪0‬‬ ‫‪93.75 Kbps‬‬
‫‪0‬‬ ‫‪0‬‬ ‫‪1‬‬ ‫‪19.2 Kbps‬‬
‫‪0‬‬ ‫‪1‬‬ ‫‪1‬‬ ‫‪9.6 Kbps‬‬
‫ﻫﺮ ‪ ILM‬ﺩﺍﺭﺍﻱ ﻳﻚ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺑﺮﺍﻱ ﺷﺒﻜﻪ‬ ‫)‪ (compact‬ﺑﻮﺩﻩ ﻭ ﺩﺍﺭﺍﻱ ‪ IP65‬ﻣﻴﺒﺎﺷﺪ‪.‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﻣﻜﺎﻧﻴﻜﻲ ‪ ILM‬ﻳﻜﭙﺎﺭﭼﻪ‬
‫ﺍﻟﻜﺘﺮﻳﻜﻲ ﺍﺳﺖ ﻛﻪ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﻮﺋﻴﭻ ﺭﻭﻱ ‪ ILM‬ﻣﻴﺘﻮﺍﻥ ﺁﻧﺮﺍ ‪ ON‬ﻳﺎ ‪ OFF‬ﻛﺮﺩ‪ .‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺍﮔﺮ ‪ ILM‬ﻋﻨﺼﺮ ﺍﺑﺘﺪﺍﻳﻲ‬
‫ﻳﺎ ﺍﻧﺘﻬﺎﻳﻲ ﺑﺎﺱ ‪ RS485‬ﺑﺎﺷﺪ ﻻﺯﻡ ﺍﺳﺖ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺭﻭﻱ ﺁﻥ ﺭﺍ ﻓﻌﺎﻝ ﻧﻤﻮﺩ‪ .‬ﺗﻮﺿﻴﺤﺎﺕ ﺑﻴﺸﺘﺮ ﺭﺍ ﻣﻴﺘﻮﺍﻧﻴﺪ ﺭﻭﻱ ﺷﻜﻠﻬﺎﻱ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ ILM‬ﺩﺭ ﺑﺨﺶ ﺑﻌﺪ ﺑﺒﻴﻨﻴﺪ‪ .‬ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ‪ ILM‬ﻣﻴﺘﻮﺍﻧﺪ ﺑﻴﻦ ‪ 0.5‬ﺗﺎ ‪ 15‬ﻣﺘﺮ ﻣﻄﺎﺑﻖ ﺷﻜﻞ ﺯﻳﺮ ﺑﺎﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﺳﻮﻡ – ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ‪PROFIBUS‬‬

‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫‪ ١-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ‬

‫‪ ٢-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ‬
‫‪ ٣-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ‬
‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪PROFIBUS‬‬ ‫‪٥٦‬‬

‫ﻣﻘﺪﻣﻪ‬
‫ﭘﺲ ﺍﺯ ﺷﻨﺎﺧﺖ ﺍﺟﺰﺍﻱ ﻣﻬﻢ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺁﺷﻨﺎﻳﻲ ﺑﺎ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻛﻪ ﺍﺯ ﺗﺮﻛﻴﺐ ﺍﻳﻦ ﺍﺟﺰﺍ‬
‫ﺑﺪﺳﺖ ﻣﻲ ﺁﻳﺪ ﺿﺮﻭﺭﻱ ﺍﺳﺖ‪ .‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺩﺭ ﻣﺒﺎﺣﺚ ﺯﻳﺮ ﺩﻧﺒﺎﻝ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪ ١-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ‬

‫ﺩﺭ ﺷﺒﻜﻪ ﻫﺎﻱ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ RS485‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻣﻴﺘﻮﺍﻧﺪ ‪ Bus‬ﻳﺎ ‪ Tree‬ﺑﺎﺷﺪ‪ .‬ﺩﺭ ﺣﺎﻟﺖ ﻋﺎﺩﻱ ﺑﺼﻮﺭﺕ ﺑﺎﺱ ﺍﺳﺖ‪.‬‬

‫ﻧﻜﺎﺕ ﻗﺎﺑﻞ ﺗﻮﺟﻪ ‪:‬‬

‫ﺍﺑﺘﺪﺍﻱ ﻭ ﺍﻧﺘﻬﺎﻱ ﺑﺎﺱ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻓﻮﻕ ﻓﻘﻂ ﻳﻚ ﺳﮕﻤﻨﺖ ﺍﺳﺖ ﺑﺎﻳﺪ ﺗﻮﺳﻂ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺑﺴﺘﻪ ﺷﻮﺩ‪ .‬ﭘﺲ‬ ‫•‬

‫ﺩﺭ ﺍﻳﻦ ﺩﻭ ﻧﻘﻄﻪ ﺗﺮﻣﻴﻨﺘﻮﺭ ﺭﺍ ‪ ON‬ﺑﺮﺍﻱ ﺳﺎﻳﺮ ﺍﺟﺰﺍﻱ ﻣﻴﺎﻧﻲ ‪ OFF‬ﻣﻴﻜﻨﻴﻢ‪ .‬ﺍﮔﺮ ﺑﺮﺍﻱ ﻳﻜﻲ ﺍﺯ ﺍﺟﺰﺍﻱ‬
‫ﻣﻴﺎﻧﻲ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ‪ ON‬ﺷﻮﺩ ﺑﺎﺱ ﻛﻮﺗﺎﻫﺘﺮ ﻣﻴﺸﻮﺩ ﻳﻌﻨﻲ ﺍﺟﺰﺍﻳﻲ ﻛﻪ ﺑﻌﺪ ﺍﺯ ﺁﻥ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﻧﺪ ﺍﺯ ﺑﺎﺱ‬
‫ﺧﺎﺭﺝ ﻣﻴﺸﻮﻧﺪ‪.‬‬
‫‪ Tap Line‬ﺑﻪ ﺑﺎﺱ ﻣﺘﺼﻞ ﺷﺪﻩ ﺍﺳﺖ ﻳﻌﻨﻲ ﻛﺎﻧﻜﺘﻮﺭ ﻛﺎﺑﻞ ﺁﻥ ﺑﻪ ﭘﺸﺖ ﻛﺎﻧﻜﺘﻮﺭ ‪S7-300‬‬ ‫‪ PG‬ﺗﻮﺳﻂ‬ ‫•‬

‫ﻣﺘﺼﻞ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﻧﻴﺎﺯﻱ ﺑﻪ ﺑﺴﺘﻦ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺩﺭ ﺳﻤﺖ ‪ PG‬ﻧﻴﺴﺖ‪.‬‬
‫ﺩﺭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ Tap Line‬ﭼﻪ ﺑﺼﻮﺭﺕ ﻓﻮﻕ ﻭ ﭼﻪ ﺗﻮﺳﻂ ‪ Bus Terminal‬ﺍﻳﺠﺎﺩ ﺷﻮﺩ ﺑﺎﻳﺪ ﺑﻪ‬ ‫•‬

‫ﻣﺤﺪﻭﺩﻳﺘﻬﺎﻱ ﻣﻨﺪﺭﺝ ﺩﺭ ﺟﺪﻭﻝ ﺯﻳﺮ ﺗﻮﺟﻪ ﺷﻮﺩ‪:‬‬

‫‪Transmission rate‬‬ ‫ﻣﺎﻛﺰﻳﻤﻢ ﻃﻮﻝ ‪ Tap Line‬ﺩﺭ‬ ‫ﺗﻌﺪﺍﺩ ‪ Node‬ﺑﺎ ‪ Tap Line‬ﺑﻪ ﻃﻮﻝ‬
‫ﻫﺮ ﺳﮕﻤﻨﺖ‬ ‫‪ 1.6 m‬ﻳﺎ ‪1.5 m‬‬ ‫‪3m‬‬

‫‪9.6 – 93.75 Kbps‬‬ ‫‪96 m‬‬ ‫‪32‬‬ ‫‪32‬‬

‫‪187.5 Kbps‬‬ ‫‪75 m‬‬ ‫‪32‬‬ ‫‪25‬‬
‫‪500 Kbps‬‬ ‫‪30 m‬‬ ‫‪20‬‬ ‫‪10‬‬
‫‪Techno-Electro.com‬‬

‫‪٥٧‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪PROFIBUS‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺭﻳﭙﻴﺘﺮ‬

‫ﺍﮔﺮ ﺗﻌﺪﺍﺩ ‪ Node‬ﻫﺎ ﺑﻴﺶ ﺍﺯ ‪ ٣٢‬ﺑﺎﺷﺪ ﺑﻨﺎﭼﺎﺭ ﺑﺮﺍﻱ‬
‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺎﻳﺪ ﺍﺯ ﺭﻳﭙﻴﺘﺮ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺭﻭﺑﺮﻭ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺗﻮﺟﻪ ﺷﻮﺩ ﻛﻪ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﻋﻼﻭﻩ ﺑﺮ ﺍﺑﺘﺪﺍﻱ‬
‫‪ON‬‬ ‫ﺳﮕﻤﻨﺖ ﻫﺎ ﺩﺭ ﻧﻘﺎﻁ ﺍﺗﺼﺎﻝ ﺑﻪ ﺭﻳﭙﻴﺘﺮ ﻧﻴﺰ ﺑﺎﻳﺪ‬
‫ﺷﻮﺩ ‪.‬‬

‫ﺍﮔﺮ ﻃﻮﻝ ﻛﺎﺑﻞ ﺑﻪ ﺣﺪﺍﻛﺜﺮ ﻃﻮﻝ ﻣﺠﺎﺯ ﺑﺮﺳﺪ ﺑﺎﻳﺪ ﺍﺯ‬

‫ﺭﻳﭙﻴﺘﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ‪ .‬ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺳﮕﻤﻨﺖ ﺟﺪﻳﺪﻱ‬
‫ﺗﺸﻜﻴﻞ ﻧﻤﻴﺸﻮﺩ ﺑﻠﻜﻪ ﻫﻤﺎﻥ ﺳﮕﻤﻨﺖ ﺗﻮﺳﻂ ﺭﻳﭙﻴﺘﺮ‬
‫ﺍﺩﺍﻣﻪ ﻣﻲ ﻳﺎﺑﺪ ﻣﺎﻧﻨﺪ ﺳﮕﻤﻨﺖ ‪ ٢‬ﺩﺭ ﺷﻜﻞ ﺭﻭﺑﺮﻭ‪ .‬ﺗﻮﺟﻪ‬
‫ﺷﻮﺩ ﻛﻪ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺑﺮﺍﻱ ﺳﮕﻤﻨﺖ ‪ ٢‬ﺑﺎﻳﺪ ‪ OFF‬ﺑﺎﺷﺪ‪.‬‬

‫ﺷﻜﻞ ﺭﻭﺑﺮﻭ ﻧﻴﺰ ﺩﻭ ﺳﮕﻤﻨﺖ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻛﻪ ﻫﺮ‬

‫ﻛﺪﺍﻡ ﺑﺼﻮﺭﺕ ﺑﺎﺱ ﺑﻮﺩﻩ ﻭ ﺗﻮﺳﻂ ﺭﻳﭙﻴﺘﺮ ﺍﺩﺍﻣﻪ ﭘﻴﺪﺍ‬
‫ﻛﺮﺩﻩ ﺍﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪PROFIBUS‬‬ ‫‪٥٨‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺩﺭﺧﺘﻲ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺭﻳﭙﻴﺘﺮ‬

‫ﺍﻳﺠﺎﺩ ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ Tree‬ﻓﻘﻂ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺭﻳﭙﻴﺘﺮ ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ‪.‬ﺷﻜﻞ ﺯﻳﺮ ‪ ٣‬ﺳﮕﻤﻨﺖ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻛﻪ ﺍﺯ‬
‫ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ‬ ‫ﻃﺮﻳﻖ ﺩﻭ ﺭﻳﭙﻴﺘﺮ ﺳﺎﺧﺘﺎﺭ ﺩﺭﺧﺘﻲ ﭘﻴﺪﺍ ﻛﺮﺩﻩ ﺍﻧﺪ‪ .‬ﺗﻮﺟﻪ ﺷﻮﺩ ﺩﺭ ﻧﻘﺎﻃﻲ ﻛﻪ ﺑﺎ ﻋﻼﻣﺖ‬
‫‪ ON‬ﻣﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﻧﻜﺎﺕ ﻣﻬﻢ ﺯﻳﺮ ﺭﺍ ﻣﺠﺪﺩﹰﺍ ﻳﺎﺩ ﺁﻭﺭﻱ ﻣﻴﻜﻨﻴﻢ‪:‬‬

‫ﻫﺮ ﺳﮕﻤﻨﺖ ﺑﺎﺱ ﺣﺪﺍﻛﺜﺮ ‪ Node ٣٢‬ﻣﻴﺘﻮﺍﻧﺪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﻛﻞ ﺑﺎﺱ ﺟﻤﻌﹰﺎ ‪ Node ١٢٧‬ﻣﻴﺘﻮﺍﻧﺪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﻣﺎﻛﺰﻳﻤﻢ ‪ ٩‬ﻋﺪﺩ ﺭﻳﭙﻴﺘﺮ ﺑﺼﻮﺭﺕ ﺳﺮﻱ ﻣﻴﺘﻮﺍﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪.‬‬ ‫•‬

‫ﺭﻳﭙﻴﺘﺮ ﻫﺎ ﺩﺭ ﻣﺤﺎﺳﺒﻪ ﺗﻌﺪﺍﺩ ‪ Node‬ﻫﺎ ﻧﻴﺰ ﺑﺎﻳﺪ ﻣﻨﻈﻮﺭ ﺷﻮﻧﺪ‪.‬‬ ‫•‬

‫ﺑﺮﺍﻱ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ‪ 1.5 Mbps‬ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﻫﺮ ﺩﻭ ‪ Node‬ﻣﺘﻮﺍﻟﻲ ﻧﺒﺎﻳﺪ ﺍﺯ ﺣﺪﻱ ﻛﻤﺘﺮ ﺑﺎﺷﺪ‪ .‬ﺟﺰﺋﻴﺎﺕ‬ ‫•‬
‫ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬
Techno-Electro.com

٥٩ PROFIBUS ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ‬

1.5 Mbps ‫ﻧﻜﺎﺕ ﺧﺎﺹ ﻣﺮﺑﻮﻁ ﺑﻪ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ‬

‫ﺧﺎﺯﻧﻲ ﺍﻳﺠﺎﺩ ﻣﻴﺸﻮﺩ ﻛﻪ ﺩﺭ ﺳﺮﻋﺘﻬﺎﻱ ﭘﺎﻳﻴﻦ ﺗﺎﺛﻴﺮﻱ ﻧﺪﺍﺭﺩ ﻭﻟﻲ ﺑﺮﺍﻱ ﺳﺮﻋﺖ‬، ‫ ﺑﻪ ﻛﺎﺑﻞ ﺷﺒﻜﻪ‬Node ‫ﺩﺭ ﺍﺗﺼﺎﻝ ﻫﺮ‬
‫ ﺑﺮﺍﻱ ﺟﻠﻮﮔﻴﺮﻱ ﺍﺯﺁﻥ ﺩﺭ ﻃﺮﺍﺣﻲ ﺳﻴﺴﺘﻢ ﺑﺎﻳﺪ ﻧﻜﺎﺕ ﺯﻳﺮ‬. ‫ ﺑﻪ ﺑﺎﻻ ﻣﻤﻜﻦ ﺍﺳﺖ ﻣﺸﻜﻼﺗﻲ ﺍﻳﺠﺎﺩ ﺷﻮﺩ‬1.5 Mbps
. ‫ﻣﻨﻈﻮﺭ ﮔﺮﺩﺩ‬
.‫ ﻣﺘﺮ ﺑﻴﺸﺘﺮ ﺑﺎﺷﺪ ﺷﺒﻜﻪ ﻣﺸﻜﻠﻲ ﻧﺪﺍﺭﺩ‬10 ‫ ﻣﺠﺎﻭﺭ ﺍﺯ‬Node ‫ﺍﮔﺮ ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ‬ •

Node ‫ ﻣﺘﺮ ﻛﻤﺘﺮ ﺑﺎﺷﺪ ﺑﺎﻳﺪ ﻣﺠﻤﻮﻉ ﺍﺭﺯﺵ ﺍﺗﺼﺎﻻﺕ ﺩﻭ‬10 ‫ ﻣﺠﺎﻭﺭ ﺍﺯ‬Node ‫ﺍﮔﺮ ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ‬ •

‫ ﻛﻪ‬PG ‫ ﺳﭙﺲ ﺍﮔﺮ ﺭﺍﺑﻄﻪ ﺯﻳﺮ ﺑﺮﻗﺮﺍﺭ ﺑﻮﺩ ﺷﺒﻜﻪ ﻣﺸﻜﻞ ﻧﺪﺍﺭﺩ‬. ‫ﻣﺠﺎﻭﺭ ﺭﺍ ﺍﺯ ﺟﺪﻭﻝ ﺯﻳﺮ ﻣﺤﺎﺳﺒﻪ ﻛﺮﺩ‬
.‫ ﺑﺎ ﺑﺎﺱ ﻣﺘﺼﻞ ﺍﺳﺖ ﺭﺍ ﻧﻴﺰ ﺑﺎﻳﺪ ﺩﺭ ﻣﺤﺎﺳﺒﺎﺕ ﻣﻨﻈﻮﺭ ﻛﺮﺩ‬Tap Line ‫ﺗﻮﺳﻂ‬
‫ ﺑﺮ ﺣﺴﺐ ﻣﺘﺮ‬Node ‫ﻃﻮﻝ ﻛﺎﺑﻞ ﺑﻴﻦ ﺩﻭ‬ > ‫ ﻣﺠﺎﻭﺭ‬Node ‫ﻣﺠﻤﻮﻉ ﺍﺭﺯﺵ ﺍﺗﺼﺎﻻﺕ ﺩﻭ‬
.‫ﺍﮔﺮ ﺷﺮﺍﻳﻂ ﻓﻮﻕ ﺑﺮﻗﺮﺍﺭ ﻧﺒﻮﺩ ﺑﺎﻳﺪ ﺗﻐﻴﻴﺮﺍﺗﻲ ﺩﺭ ﻃﻮﻝ ﻛﺎﺑﻞ ﻟﺤﺎﻅ ﺷﻮﺩ ﺗﺎ ﺷﺒﻜﻪ ﻣﺸﻜﻞ ﭘﻴﺪﺍ ﻧﻜﻨﺪ‬ •

‫ ﻣﺘﺮ‬5 ‫ ﺩﺭ ﺷﻜﻞ ﺭﻭﺑﺮﻭ ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺠﺎﻭﺭ‬: ‫ﻣﺜﺎﻝ‬

‫ ﻣﺠﻤﻮﻉ ﺍﺭﺯﺷﻬﺎ‬PG ‫ﺍﺳﺖ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺟﺪﻭﻝ ﻭ ﺩﺭﻧﻈﺮ ﮔﺮﻓﺘﻦ‬
1.5+0.1+1 =2.6 : ‫ﺑﺮﺍﺑﺮ ﺍﺳﺖ ﺑﺎ‬
‫ ﺍﺳﺖ ﺍﻳﻦ ﺷﺒﻜﻪ ﺩﺭ‬2.6 ‫ ﻣﺘﺮ ﻭ ﺑﺰﺭﮔﺘﺮ ﺍﺯ‬5 ‫ﭼﻮﻥ ﻃﻮﻝ ﻛﺎﺑﻞ‬
.‫ ﻣﺸﻜﻠﻲ ﻧﺨﻮﺍﻫﺪ ﺩﺍﺷﺖ‬1.5 Mbps ‫ﺳﺮﻋﺖ‬
Product Name Order number Value
(V)
Bus terminal with 1.5 m long tap line (6GK1 500-0AA00) 1.5
Bus terminal with 1.5 m long tap line, with PG interface (6GK1 500-0DA00 1.5
Bus terminal with 3.0 m long tap line (6GK1 500-0BA00) 2.5
Bus connector with 30° cable outlet (6ES7 972-0BA30-0XA0) 0.7
Bus connector with axial cable outlet 6GK1 500-0EA02)
Bus connector with axial cable outlet for FastConnect 6GK1 500-0FC00
Bus connector with 90° cable outlet 6ES7 972-0BA11-0XA0
Bus connector with 90° cable outlet with PG interface 6ES7 972-0BB11-0XA0 0.1
Bus connector with 90° cable outlet for FastConnect 6ES7 972-0BA50-0XA0
Bus connector with 90° cable outlet with PG interface 6ES7 972-0BB50-0XA0
Bus connector with 35° cable outlet 6ES7 972-0BA40-0XA0)
Bus connector with 35° cable outlet with PG interface 6ES7 972-0BB40-0XA0
Bus terminal BT12M 6GK1500-0AA10 0.1
RS-485 repeater (attachment of bus segments) 6ES7 972-0AA01-0XA0) 0.1
PROFIBUS terminator (active RS-485 attachment element) 6ES7 972-0DA01-0AA0 0.1
SIMATIC S5/S7 connecting cable for 12 Mbps PG 6ES7 901-4BD00-0XA0 0.5
attachment to PROFIBUS-DP
‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ‪PROFIBUS‬‬ ‫‪٦٠‬‬

‫‪ ٢-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ‬

‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻟﻤﺎﻧﻬﺎﻱ ﺷﺒﻜﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻣﻴﺘﻮﺍﻥ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺍﻳﺠﺎﺩ ﻛﺮﺩ‪ .‬ﺑﺎ ‪ OBT‬ﻣﻲ ﺗﻮﺍﻥ ﻓﻘﻂ‬
‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﻭ ﺑﺎ ‪ OLM‬ﻣﻴﺘﻮﺍﻥ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺑﺎﺱ ﻭ ﺳﺘﺎﺭﻩ ﻭ ﺭﻳﻨﮓ ﺭﺍ ﺑﻮﺟﻮﺩ ﺁﻭﺭﺩ‪ .‬ﻧﻜﺎﺗﻲ ﻛﻪ ﺑﺎﻳﺪ ﺑﻪ ﺁﻧﻬﺎ‬
‫ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﺍﻳﻨﺴﺖ ﻛﻪ‪:‬‬
‫ﺑﺎ ‪ OBT‬ﻧﻤﻴﺘﻮﺍﻥ ﻓﻴﺒﺮ ﺷﻴﺸﻪ ﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﺣﺪﺍﻛﺜﺮ ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ﻧﻘﻄﻪ ﺑﺎ ﻓﻴﺒﺮ ﭘﻼﺳﺘﻴﻜﻲ ‪ 50m‬ﻭ ﺑﺎ ﻓﻴﺒﺮ‬ ‫•‬

‫‪ 300‬ﻣﺘﺮ ﺍﺳﺖ‪.‬‬ ‫‪PCF‬‬

‫ﺑﺎ ‪ OLM‬ﻫﻤﻪ ﺍﻧﻮﺍﻉ ﻛﺎﺑﻞ ﻫﺎﻱ ﻧﻮﺭﻱ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ﻧﻘﻄﻪ ﺑﺎ ﻛﺎﺑﻞ ﺷﻴﺸﻪ ﺍﻱ ‪ 15 km‬ﻭ‬ ‫•‬

‫ﺑﺎ ﻛﺎﺑﻞ ﭘﻼﺳﺘﻴﻜﻲ ‪ 80 m‬ﺍﺳﺖ‪.‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪OBT‬‬

‫ﺷﻜﻞ ﺯﻳﺮ ﻧﻤﻮﻧﻪ ﺍﻱ ﺍﺯ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﻛﻪ ﺗﻮﺳﻂ ‪ OBT‬ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬ﻛﺎﺑﻞ ﻧﻮﻉ ‪ 1‬ﺍﻟﻜﺘﺮﻳﻜﻲ ﻭ ﻛﺎﺑﻞ‬
‫ﻧﻮﻉ ‪ 2‬ﻧﻮﺭﻱ ﻣﻴﺒﺎﺷﺪ‪ .‬ﺗﻮﺟﻪ ﺷﻮﺩ ﻛﻪ ﺩﺭ ﺩﻭ ﻃﺮﻑ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ‪ ON‬ﻣﻲ ﺑﺎﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٦١‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ‪PROFIBUS‬‬

‫‪OLM‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬

‫ﺷﻜﻞ ﺯﻳﺮ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﻛﻪ ﺗﻮﺳﻂ ‪ OLM‬ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻣﻴﺘﻮﺍﻥ ﺑﻴﻦ ﺩﻭ ‪ OLM‬ﺍﺯ‬
‫ﻓﻴﺒﺮ ﺷﻴﺸﻪ ﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﻣﺴﺎﻓﺖ ﺑﻴﻦ ﺩﻭ ‪ Node‬ﺑﺴﻴﺎﺭ ﺑﻴﺸﺘﺮ ﺍﺯ ﻧﻮﻉ ﻗﺒﻞ )‪ (OBT‬ﻣﻴﺒﺎﺷﺪ‪.‬‬

‫‪OBT‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OLM‬ﻭ‬

‫ﺍﮔﺮ ﻓﺎﺻﻠﻪ ﺑﺮﺧﻲ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺑﻴﺸﺘﺮ ﺍﺯ ﺣﺪ ﻣﺠﺎﺯ ﺍﺳﺘﻔﺎﺩﻩ ‪ OBT‬ﺑﺎﺷﺪ ﻣﻴﺘﻮﺍﻥ ﺑﻴﻦ ﺁﻥ ﻧﻘﺎﻁ ﻓﻘﻂ ﺍﺯ ‪ OLM‬ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﻛﺮﺩ‪ .‬ﺗﻮﺟﻪ ﺷﻮﺩ ﻛﻪ ﺟﺎﻳﮕﺰﻳﻨﻲ ﻫﻤﻪ ‪ OBT‬ﻫﺎ ﺑﺎ ‪ OLM‬ﻣﻤﻜﻦ ﺍﺳﺖ ﻣﻘﺮﻭﻥ ﺑﻪ ﺻﺮﻓﻪ ﻧﺒﺎﺷﺪ ﻭ ﻃﺮﺍﺡ ﺗﺮﺟﻴﺢ ﺩﻫﺪ‬
‫ﺁﻧﻬﺎ ﺭﺍ ﺑﺼﻮﺭﺕ ﺗﺮﻛﻴﺒﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ‪PROFIBUS‬‬ ‫‪٦٢‬‬

‫‪OLM‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺳﺘﺎﺭﻩ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬

‫ﺍﻳﻦ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻓﻘﻂ ﺑﺎ ‪ OLM‬ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ﻭ ﻧﻤﻴﺘﻮﺍﻥ ﺍﺯ ‪ OBT‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺁﺭﺍﻳﺶ ‪ OLM‬ﻫﺎ ﺑﮕﻮﻧﻪ ﺍﻱ ﺍﺳﺖ‬
‫ﻛﻪ ﺍﺯ ﺗﺮﻛﻴﺐ ‪ ٣‬ﻋﺪﺩ ﺍﺯ ﺁﻧﻬﺎ ﻳﻚ ‪ Hub‬ﺍﻳﺠﺎﺩ ﻣﻴﺸﻮﺩ‪ .‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺑﺎ ﺑﺮﻭﺯ ﻣﺸﻜﻞ ﺭﻭﻱ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ‬
‫ﺑﻘﻴﻪ ﺷﺒﻜﻪ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻜﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﺩﻫﺪ‪ .‬ﻣﮕﺮ ﺍﻳﻨﻜﻪ ﺍﺷﻜﺎﻟﻲ ﺩﺭ ‪ Hub‬ﺑﻮﺟﻮﺩ ﺁﻳﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٦٣‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﻧﻮﺭﻱ ‪PROFIBUS‬‬

‫‪OLM‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺣﻠﻘﻮﻱ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬

‫ﺍﻳﻦ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻧﻴﺰ ﻓﻘﻂ ﺑﺎ ‪ OLM‬ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ﻭ ﻧﻤﻴﺘﻮﺍﻥ ﺍﺯ ‪ OBT‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺑﺎ ﺍﺗﺼﺎﻝ ‪ OLM‬ﻫﺎ ﺭﻭﻱ‬
‫ﺷﺒﻜﻪ ﻧﻮﺭﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ Ring‬ﺍﻳﺠﺎﺩ ﻣﻴﺸﻮﺩ ‪ .‬ﺍﻳﻦ ﺳﺎﺧﺘﺎﺭ ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻧﺶ ﻧﺴﺒﺖ ﺑﻪ ﺳﺎﻳﺮﻳﻦ ﺑﻴﺸﺘﺮ‬
‫ﺍﺳﺖ ﺯﻳﺮﺍ ﺑﺎ ﺑﺮﻭﺯ ﻣﺸﻜﻞ ﺭﻭﻱ ﻫﺮ ﻗﺴﻤﺖ ﺍﺯ ﻓﻴﺒﺮ ﻳﺎ ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ‪ OLM‬ﻫﺎ ‪ ،‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﻪ ﺣﺎﻟﺖ ﺑﺎﺱ ﺩﺭ ﻣﻲ ﺁﻳﺪ ﻭ‬
‫ﺷﺒﻜﻪ ﺑﻪ ﻛﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﻣﻴﺪﻫﺪ‪.‬‬

‫ﺍﮔﺮ ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ‪ OLM‬ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎ ﺩﺭ ﺷﻜﻞ ﻓﻮﻕ ﺧﻴﻠﻲ ﺯﻳﺎﺩ ﺑﺎﺷﺪ ﻣﻤﻜﻦ ﺍﺳﺖ ﻣﺸﻜﻞ ﺍﻳﺠﺎﺩ ﺷﻮﺩ ﺯﻳﺮﺍ ﻫﺮ ﻧﻮﻉ‬
‫‪ OLM‬ﺗﺎ ﻓﺎﺻﻠﻪ ﺧﺎﺻﻲ ﺭﺍ ﺳﺎﭘﻮﺭﺕ ﻣﻲ ﻛﻨﺪ‪) .‬ﺑﺮﺧﻲ ﺗﺎ ‪ ٤٠٠‬ﻣﺘﺮ ﻭ ﺑﺮﺧﻲ ﺗﺎ ‪ ٣‬ﻛﻴﻠﻮﻣﺘﺮ ﻭ ﺑﺮﺧﻲ ﺩﻳﮕﺮ ﺗﺎ ‪١٥‬‬
‫ﻛﻴﻠﻮﻣﺘﺮ( ﻟﺬﺍ ﻣﻴﺘﻮﺍﻥ ﺳﺎﺧﺘﺎﺭ ﺭﺍ ﺑﺎ ﺷﻜﻞ ﺯﻳﺮ ﺳﺎﺩﻩ ﺳﺎﺯﻱ ﻛﺮﺩ ﺗﺎ ﻣﺸﻜﻞ ﻓﻮﻕ ﺑﺮﻃﺮﻑ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺷﺒﻜﻪ ﺑﻲ ﺳﻴﻢ ‪PROFIBUS‬‬ ‫‪٦٤‬‬

‫‪ ٣-٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺷﺒﻜﻪ ﺑﺪﻭﻥ ﺳﻴﻢ‬
‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ ILM‬ﻣﻴﺘﻮﺍﻥ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﺪﻭﻥ ﺳﻴﻢ ﺍﻳﺠﺎﺩ ﻛﺮﺩ ﻛﻪ ﺍﻟﺒﺘﻪ ﻣﺎﻛﺰﻳﻤﻢ ﻓﺎﺻﻠﻪ ‪ 15‬ﻣﺘﺮ ﻭ‬
‫ﻣﺎﻛﺰﻳﻤﻢ ﺳﺮﻋﺖ ‪ 1.5 Mbps‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺻﺮﻓﺎ ﺩﻭ ﻧﻮﻉ ﺳﺎﺧﺘﺎﺭ ﻣﻴﺘﻮﺍﻥ ﺑﺮﺍﻱ ‪ ILM‬ﺩﺍﺷﺖ‪.‬‬
‫‪Point to Point -١‬‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪ Subnet‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Slave‬ﻫﺎ ﺑﺎ ‪ Subnet‬ﺩﻳﮕﺮ ﺍﺯ ﻃﺮﻳﻖ ﺩﻭ ‪ ILM‬ﺑﻪ ﻫﻢ ﻟﻴﻨﻚ ﻣﻴﺸﻮﻧﺪ‪.‬‬

‫ﻣﻴﺘﻮﺍﻥ ‪ Subnet‬ﺩﻭﻡ ﺭﺍ ﻧﻴﺰ ﺍﺯ ﻃﺮﻳﻖ ‪ ILM‬ﺩﻳﮕﺮ ﺑﺼﻮﺭﺕ ‪ Cascade‬ﺑﻪ ‪ Subnet‬ﺳﻮﻡ ﻭﺻﻞ ﻛﺮﺩ ‪:‬‬
‫‪Techno-Electro.com‬‬

‫‪٦٥‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺷﺒﻜﻪ ﺑﻲ ﺳﻴﻢ ‪PROFIBUS‬‬

‫‪Point to multipoint -٢‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪ Subnet‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Slave‬ﻫﺎ ﺑﺎ ‪ Subnet‬ﺩﻳﮕﺮ ﺍﺯ ﻃﺮﻳﻖ ﺩﻭ ‪ ILM‬ﺑﻪ ﻫﻢ ﻟﻴﻨﻚ ﻣﻴﺸﻮﻧﺪ‪.‬‬
‫ﺗﻮﺟﻪ ﺷﻮﺩ ﻛﻪ ﭼﻪ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻭ ﭼﻪ ﺩﺭ ﺭﻭﺵ ﻗﺒﻞ ‪ ،‬ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ‪ Subnet‬ﻫﺎ ﺑﺎﻳﺪ ﺩﺭ ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎ ﻓﻌﺎﻝ‬
‫ﺑﺎﺷﻨﺪ‪.‬‬
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﭼﻬﺎﺭﻡ – ﭘﻴﻜﺮﺑﻨﺪﻱ ﺷﺒﻜﻪ ‪ PROFIBUS-DP‬ﺩﺭ ‪STEP7‬‬

‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫ﺑﺨﺶ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻳﻚ ﭘﺮﻭﮊﻩ ‪STEP 7‬‬ ‫‪١-٤‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٢-٤‬‬
‫ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪CP‬‬ ‫‪٣-٤‬‬
‫ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪IM‬‬ ‫‪٤-٤‬‬
‫ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪IF‬‬ ‫‪٥-٤‬‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﭼﻨﺪ ‪ Master System‬ﺑﺼﻮﺭﺕ ﺗﺮﻛﻴﺒﻲ‬ ‫‪٦-٤‬‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎ‬ ‫‪٧-٤‬‬
‫‪Techno-Electro.com‬‬

‫ﻣﻘﺪﻣﻪ‬ ‫‪٦٨‬‬

‫ﻣﻘﺪﻣﻪ‬
‫ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ ﺍﺑﺰﺍﺭﻫﺎﻳﻲ ﻛﻪ ﺩﺭ ‪ STEP 7‬ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻧﻴﺎﺯ ﺍﺳﺖ ﺭﺍ ﻣﻌﺮﻓﻲ‬
‫ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪ .‬ﺍﮔﺮﭼﻪ ﺁﺷﻨﺎﻳﻲ ﻧﺴﺒﻲ ﺧﻮﺍﻧﻨﺪﻩ ﺑﺎ ﻣﺤﻴﻂ ‪ STEP7‬ﭘﻴﺶ ﻓﺮﺽ ﻣﺎ ﺩﺭ ﺗﺪﻭﻳﻦ ﺍﻳﻦ ﻛﺘﺎﺏ ﺑﻮﺩﻩ ﺍﺳﺖ ﺑﺎ ﺍﻳﻦ‬
‫ﻭﺟﻮﺩ ﺑﻤﻨﻈﻮﺭ ﻳﺎﺩ ﺁﻭﺭﻱ ﺑﻪ ﺍﺟﻤﺎﻝ ﻧﮕﺎﻫﻲ ﺑﻪ ﻣﺤﻴﻂ ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﻣﻲ ﺍﻧﺪﺍﺯﻳﻢ‪ .‬ﺍﮔﺮ ﺍﻳﻦ ﻣﻄﺎﻟﺐ ﻣﻘﺪﻣﺎﺗﻲ ﺑﺮﺍﻱ ﺧﻮﺍﻧﻨﺪﻩ‬
‫ﺗﻜﺮﺍﺭﻱ ﺍﺳﺖ ﻣﻴﺘﻮﺍﻧﺪ ﺍﺩﺍﻣﻪ ﺑﺤﺚ ﺷﺒﻜﻪ ﺭﺍ ﺍﺯ ﻗﺴﻤﺖ ‪ ٣-٥‬ﺩﻧﺒﺎﻝ ﻛﻨﺪ‪.‬‬
‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻴﺪﺍﻧﻴﻢ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ STEP 7‬ﻣﺸﺘﻤﻞ ﺑﺮ ﭼﻨﺪﻳﻦ ﻗﺴﻤﺖ ﻛﺎﺭﺑﺮﺩﻱ ﺍﺳﺖ ﻛﻪ ﻫﺮﻛﺪﺍﻡ ﺑﺮﺍﻱ ﭘﻮﺷﺶ ﺩﺍﺩﻥ‬
‫ﻳﻜﻲ ﺍﺯ ﻧﻴﺎﺯﻫﺎﻳﻲ ﻛﻪ ﺩﺭ ﻃﺮﺍﺣﻲ ﻳﺎ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻳﺎ ﻋﻴﺐ ﻳﺎﺑﻲ ﺳﻴﺴﺘﻢ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻣﻄﺮﺡ ﻣﻴﺸﻮﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﮔﺮﺩﺩ‪.‬‬
‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ‪ ،‬ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺒﻜﻪ ﻭ ﺍﺭﺗﺒﺎﻃﺎﺕ ﺍﺯ ﺟﻤﻠﻪ ﺍﻳﻦ ﻧﻴﺎﺯﻫﺎ ﺑﻪ ﺷﻤﺎﺭ ﻣﻴﺮﻭﻧﺪ‪.‬‬
‫ﺑﺮﻧﺎﻣﻪ ﻛﺎﺭﺑﺮﺩﻱ ﻛﻪ ﺍﻳﻦ ﻣﺠﻤﻮﻋﻪ ﺍﺑﺰﺍﺭ ﻫﺎ ﺭﺍ ﺑﻪ ﺻﻮﺭﺕ ﻳﻜﺠﺎ ﻓﺮﺍﻫﻢ ﻧﻤﻮﺩﻩ ﺍﺳﺖ ‪ SIMATIC MANAGER‬ﻧﺎﻣﻴﺪﻩ ﻣﻲ‬
‫ﺷﻮﺩ‪ SIMATIC MANAGER.‬ﻫﻤﻪ ﺍﻃﻼﻋﺎﺕ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﻭﺗﻨﻈﻴﻤﺎﺕ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺭﺍ ﺫﺧﻴﺮﻩ ﻭ ﺩﺭ ﺩﺍﺧﻞ ﻳﻚ ﭘﺮﻭﮊﻩ‬
‫ﮔﺮﺩ ﺁﻭﺭﻱ ﻣﻲ ﻛﻨﺪ ‪ .‬ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﺍﻭﻟﻴﻦ ﻗﺪﻣﻲ ﻛﻪ ﺑﺎﻳﺪ ﺩﺭ ﻃﺮﺍﺣﻲ ﻳﻚ ﺳﻴﺴﺘﻢ ﺟﺪﻳﺪ ﺑﺮﺩﺍﺷﺘﻪ ﺷﻮﺩ ﺍﻳﺠﺎﺩ ﻳﻚ ﭘﺮﻭﮊﻩ‬
‫ﺟﺪﻳﺪ ﺩﺭ ‪ Simatic Manager‬ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٦٩‬‬ ‫ﺑﺨﺶ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻳﻚ ﭘﺮﻭﮊﻩ ‪STEP 7‬‬

‫ﺑﺨﺶ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻳﻚ ﭘﺮﻭﮊﻩ ‪STEP 7‬‬ ‫‪١-٤‬‬

‫ﻳﻚ ﭘﺮﻭﮊﻩ ‪ STEP 7‬ﺍﺯ ﻳﻚ ﻳﺎ ﭼﻨﺪ ‪ Station‬ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﺍﺳﺖ‪.‬ﻣﻨﻈﻮﺭ ﺍﺯ ‪ Station‬ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ ﺍﺳﺖ ﻛﻪ‬
‫ﻣﻴﺘﻮﺍﻧﺪ ﺷﺎﻣﻞ ﺍﺟﺰﺍﻳﻲ ﻣﺎﻧﻨﺪ ‪ Rack‬ﻭ‪ CPU‬ﻭﻛﺎﺭﺕ ﻫﺎﻱ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﺑﺎﺷﺪ‪.‬‬
‫ﻳﻚ ‪ Station‬ﻛﻪ ﺍﺯ ﻗﺒﻞ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺪﻩ ﺑﺎﺷﺪ ﺩﺭ ‪ Simatic Manager‬ﺩﺍﺭﺍﻱ ﺳﺎﺧﺘﺎﺭ ﺳﻠﺴﻠﻪ ﻣﺮﺍﺗﺒﻲ ﻣﺎﻧﻨﺪ ﺷﻜﻞ‬
‫ﺯﻳﺮ ﻣﻴﺒﺎﺷﺪ‪ .‬ﻳﻚ ‪ Folder‬ﻣﺨﺼﻮﺹ ‪ Hardware‬ﻭﻳﻚ ‪ Folder‬ﻣﺨﺼﻮﺹ ﺑﺮﻧﺎﻣﻪ ‪ ) STEP7‬ﺑﻪ ﻧﺎﻡ ‪( S7 Program‬‬
‫ﻣﺠﻤﻮﻋﻪ ﻗﺴﻤﺖ ﻫﺎﻱ ﺍﺻﻠﻲ ﻳﻚ ‪ Station‬ﺭﺍ ﺗﺸﻜﻴﻞ ﻣﻲ ﺩﻫﻨﺪ‬

‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ STEP 7‬ﻳﻚ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺷﻲﺀ ﮔﺮﺍﺳﺖ ‪.‬ﻛﺎﻓﻲ ﺍﺳﺖ ﺑﺮﺍﻱ ﻛﺎﺭ ﺑﺎ ﻫﺮ ﻳﻚ ﺍﺯ ﺍﺟﺰﺍﺀ ﻭﺍﺷﻴﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ‬
‫‪ SIMATIC MANAGER‬ﺑﺮﺭﻭﻱ ﺁﻥ ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ‪.‬ﺩﺭ ﺍﻳﻦ ﺻﻮﺭﺕ ﺍﻃﻼﻋﺎﺕ ﻭﻣﻮﺍﺭﺩ ﻻﺯﻡ ﻭﻣﺮﺗﺒﻂ ﺑﻪ ﺁﻥ ﺷﻲ ﺑﺎ‬
‫ﮔﺮﺍﻓﻴﻚ ﻣﻨﺎﺳﺐ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻛﺎﺭﺑﺮ ﻗﺮﺍﺭ ﺧﻮﺍﻫﺪ ﮔﺮﻓﺖ‪ .‬ﺑﻪ ﺟﺎﻱ ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﺑﺮ ﺭﻭﻱ ﻳﻚ ﺷﻲ ﻣﻲ ﺗﻮﺍﻥ ﺭﺍﺳﺖ ﻛﻠﻴﻚ‬
‫ﻧﻤﻮﺩﻩ ﻭﺳﭙﺲ ‪ Open‬ﻛﻨﻴﻢ‪.‬‬
‫ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﻛﻪ ‪:‬‬
‫ﺍﻃﻼﻋﺎﺕ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺩﺭ ﭘﻮﺷﻪ ‪ Blocks‬ﺫﺧﻴﺮﻩ ﻣﻴﺸﻮﺩ ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﺑﻼﻙ ﻣﻮﺭﺩ ﻧﻈﺮ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ‬ ‫•‬
‫ﺍﻱ ﺑﻪ ﻧﺎﻡ ‪ LAD/STL/FBD‬ﺍﺟﺮﺍ ﻣﻴﮕﺮﺩﺩ ﻛﻪ ﺗﻮﺳﻂ ﺁﻥ ﻣﻴﺘﻮﺍﻥ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪.‬‬
‫ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﺁﻳﻜﻮﻥ ‪ SIMATIC Station‬ﺁﻳﻜﻮﻥ ‪ Hardware‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﻛﻪ ﺑﺎ ﻛﻠﻴﻚ ﺭﻭﻱ‬ ‫•‬

‫ﺁﻥ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ ﺍﻱ ﺑﻪ ﻧﺎﻡ ‪ Hwconfig‬ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺑﺎﺯ ﻣﻲ ﮔﺮﺩﺩ‪.‬‬
‫ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ﺁﻳﻜﻮﻧﻬﺎﻱ ‪ MPI‬ﻳﺎ ‪ PROFIBUS‬ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ ﺍﻱ ﺑﻪ ﻧﺎﻡ ‪ Netpro‬ﻛﻪ‬ ‫•‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺒﻜﻪ ﺍﺳﺖ ﺑﺎﺯ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٧٠‬‬

‫‪ ٢-٤‬ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ‪PROFIBUS -DP‬‬
‫ﺑﺮﺍﻱ ﺍﻳﻨﻜﻪ ﻫﻢ ﻧﺤﻮﻩ ﺍﻳﺠﺎﺩ ﻳﻚ ﭘﺮﻭﮊﻩ ﺩﺭ ‪ STEP 7‬ﺭﺍ ﻳﺎﺩ ﺁﻭﺭﻱ ﻛﺮﺩﻩ ﺑﺎﺷﻴﻢ ﻭﻫﻢ ﺍﻳﺠﺎﺩ ﻳﻚ ﺷﺒﻜﻪ ‪PROFIBUS‬‬

‫ﺭﺍ ﺷﺮﻭﻉ ﺑﻪ ﻓﺮﺍﮔﻴﺮﻱ ﻧﻤﺎﻳﻴﻢ ‪،‬ﻣﺜﺎﻝ ﺯﻳﺮ ﺭﺍ ﻃﺮﺡ ﻭﺩﻧﺒﺎﻝ ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬‬

‫ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﻳﻚ ﭘﺮﻭﮊﻩ ‪ Station S7-400‬ﺍﻳﺠﺎﺩ ﻧﻤﻮﺩﻩ ﻭﺩﺭ ﺁﻥ ﺍﺯ ﻳﻚ ‪ CPU 416-2DP‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ‪.‬ﺩﺭ ﺍﺩﺍﻣﻪ‬
‫ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻳﻚ ﺷﺒﻜﻪ ‪ Master/Slave‬ﻳﻚ ‪ ET 200B‬ﺷﺎﻣﻞ ‪ 16DI‬ﻭ ‪ 16DO‬ﻭﻳﻚ ‪ ET 200M‬ﺑﻪ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻭﺻﻞ ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫‪S7-400‬‬

‫‪PROFIBUS‬‬

‫‪ET200B‬‬ ‫‪ET200M‬‬

‫ﮔﺎﻡ ﺍﻭﻝ‪ :‬ﺍﻳﺠﺎﺩ ﻳﻚ ﭘﺮﻭﮊﻩ ﺟﺪﻳﺪ‬

‫ﺑﺮﻧﺎﻣﻪ ‪ SIMATIC MANAGER‬ﺭﺍ ﺑﺎﺯ ﻛﻨﻴﺪ ﺳﭙﺲ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ SIMATIC MANAGER‬ﺍﺯ ﻗﺴﻤﺖ ‪ File‬ﮔﺰﻳﻨﻪ‬
‫ﻼ‪PROFIBUS DP -‬‬
‫‪ New...‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪.‬ﻳﻚ ﭘﻨﺠﺮﻩ ﻣﻄﺎﺑﻖ ﺷﻜﻞ ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ ‪.‬ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ‪ ،‬ﻧﺎﻡ ﺩﻟﺨﻮﺍﻩ ﻣﺜ ﹰ‬
‫‪Storage‬‬ ‫‪ EXAMPLE‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪.‬ﺩﺭ ﻗﺴﻤﺖ ‪ Type‬ﻫﻢ ﮔﺰﻳﻨﻪ ‪ Project‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪ .‬ﻭﺩﺭ ﻗﺴﻤﺖ‬
‫‪ Location‬ﻣﺴﻴﺮﻱ ﺭﺍ ﻛﻪ ﻣﻲ ﺧﻮﺍﻫﻴﺪ ﭘﺮﻭﮊﻩ ﺩﺭ ﺁﻧﺠﺎ ‪ Save‬ﺷﻮﺩ‪ ،‬ﺗﺎﻳﭗ ﻳﺎ ﺁﻧﺮﺍ ﺑﺪﻭﻥ ﺗﻐﻴﻴﺮ ﺗﺎﻳﻴﺪﻛﻨﻴﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٧١‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫‪PROFIBUS‬‬ ‫ﺣﺎﻝ ﺻﻔﺤﻪ ﺍﺻﻠﻲ ‪ SIMATIC MANAGER‬ﺑﻪ ﺻﻮﺭﺕ ﺷﻜﻞ ﺯﻳﺮﺩﺭ ﺧﻮﺍﻫﺪ ﺁﻣﺪ ﻛﻪ ﺷﺎﻣﻞ ﭘﺮﻭﮊﻩ‬
‫‪ DP -EXAMPLE‬ﺍﺳﺖ‪ .‬ﺩﺭ ﺷﺮﺍﻳﻂ ﻓﻌﻠﻲ ﺩﺭ ﺍﻳﻦ ﭘﺮﻭﮊﻩ ﻓﻘﻂ ﻳﻚ ﺷﻲ ﺑﻪ ﻧﺎﻡ ‪ MPI‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺷﻤﺎ ﺁﻥ ﺭﺍ ﺩﺭ ﻧﻴﻢ‬
‫ﺻﻔﺤﻪ ﺳﻤﺖ ﺭﺍﺳﺖ ﻣﻲ ﺑﻴﻨﻴﺪ ‪.‬ﺍﺭﺗﺒﺎﻁ ‪ MPI‬ﺑﻪ ﺻﻮﺭﺕ ﭘﻴﺶ ﻓﺮﺽ ﺗﻮﺳﻂ ‪ STEP 7‬ﺑﺮﺍﻱ ﺗﻤﺎﻡ ﭘﺮﻭﮊﻩ ﻫﺎ ﺳﺎﺧﺘﻪ ﻣﻲ‬
‫ﻻ ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ‪ PLC‬ﺑﻪ ‪ PG‬ﻳﺎ ‪ PC‬ﺍﺯ ﺁﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ‬
‫ﺷﻮﺩ ‪.‬ﺷﺒﻜﻪ ‪ MPI‬ﻳﻜﻲ ﺍﺯ ﺷﺒﻜﻪ ﻫﺎﻱ ﺯﻳﻤﻨﺲ ﺍﺳﺖ ﻛﻪ ﻣﻌﻤﻮ ﹰ‬
‫ﺷﻮﺩ‪،‬ﻫﺮ ﭼﻨﺪ ﻛﻪ ﺑﺮﺍﻱ ﺷﺒﻜﻪ ﻫﺎﻱ ﺑﺎ ﻃﻮﻝ ﻛﻮﺗﺎﻩ ﻭﺳﺮﻋﺖ ﭘﺎﻳﻴﻦ ﻫﻢ ﻣﻲ ﺗﻮﺍﻥ ﺍﺯ ﺁﻥ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ‪ PLC‬ﻫﺎ ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﻛﺮﺩ ‪.‬ﺷﺒﻜﻪ ‪ MPI‬ﻣﻮﺿﻮﻉ ﺑﺤﺚ ﻣﺎ ﻧﻴﺴﺖ‪.‬‬

‫ﮔﺎﻡ ﺩﻭﻡ ‪:‬ﺍﻳﺠﺎﺩ ﻳﻚ ‪ Station S7-400‬ﺩﺭ ﭘﺮﻭﮊﻩ‬

‫ﺑﺮ ﺭﻭﻱ ﻧﺎﻡ ﭘﺮﻭﮊﻩ ﺩﺭ ﭘﻨﺠﺮﻩ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ ‪ SIMATIC MANAGER‬ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ‪،‬ﮔﺰﻳﻨﻪ‬
‫‪ Insert New Object‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻭﺳﭙﺲ ﻳﻚ ‪ Station‬ﺍﺯ ﻧﻮﻉ ‪ SIMATIC 400‬ﺍﻳﺠﺎﺩ ﻧﻤﺎﻳﻴﺪ‪.‬‬

‫ﺍﻳﻦ ‪ Station‬ﺟﺪﻳﺪ ﻛﻪ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻳﺪ ﺑﻪ ﻋﻨﻮﺍﻥ ﻳﻚ ﺷﻲ ﺩﺭ ﭘﻨﺠﺮﻩ ﺳﻤﺖ ﺭﺍﺳﺖ ﻇﺎﻫﺮ ﻣﻲ ﺷﻮﺩ‪.‬ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺩﺭ ﺻﻮﺭﺕ‬
‫ﻼ ‪ Process1‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪.‬‬
‫ﻟﺰﻭﻡ ‪،‬ﻧﺎﻡ ﺍﻳﻦ ‪ Station‬ﺭﺍ ﻋﻮﺽ ﻛﻨﻴﺪ ﻭﻳﻚ ﻧﺎﻡ ﻣﺘﻨﺎﺳﺐ ﺑﺎ ﻋﻤﻠﻜﺮﺩ ﺍﻳﻦ ‪ Station‬ﻣﺜ ﹰ‬
‫ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭ ﻛﺎﻓﻲ ﺍﺳﺖ ﻛﻪ ﺑﺮ ﺭﻭﻱ ﻧﺎﻡ ‪ Station‬ﻛﻠﻴﻚ ﺭﺍﺳﺖ ﻛﺮﺩﻩ ﻭﮔﺰﻳﻨﻪ ‪ Rename‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٧٢‬‬

‫ﻫﻤﭽﻨﻴﻦ ﺑﺎ ﺭﺍﺳﺖ ﻛﻠﻴﻚ‬

‫‪Station‬‬ ‫ﺑﺮ ﺭﻭﻱ ﻧﺎﻡ ﺍﻳﻦ‬
‫‪Properties‬‬ ‫ﻭﺍﻧﺘﺨﺎﺏ‬
‫ﻳﻚ ﭘﻨﺠﺮﻩ ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻫﻢ‬
‫ﻣﻲ ﺑﻴﻨﻴﺪ ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ‬
‫ﺷﻤﺎ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﻳﻚ ﺳﺮﻱ‬
‫ﻧﺎﻡ‬ ‫ﺷﺎﻣﻞ‬ ‫ﺗﻮﺿﻴﺤﺎﺕ‬
‫‪Author‬‬ ‫‪،‬‬ ‫‪Station‬‬

‫ﻭ‪...‬ﺭﺍﺑﻨﻮﻳﺴﻴﺪ‪.‬‬

‫ﮔﺎﻡ ﺳﻮﻡ‪ :‬ﺍﻳﺠﺎﺩ ﺷﺒﻜﻪ ‪PROFIBUS‬‬

‫ﺗﺎ ﺍﻳﻨﺠﺎ ﺩﺭ ﺍﻳﻦ ﭘﺮﻭﮊﻩ ﻳﻚ ‪ Station 400‬ﺍﻳﺠﺎﺩ ﻛﺮﺩﻩ ﺍﻳﻢ‪.‬ﺣﺎﻝ ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻫﻢ ﺍﺿﺎﻓﻪ ﻛﻨﻴﻢ‬
‫ﺭﺍﻫﻬﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬ﺩﺭ ﺍﻳﻨﺠﺎ ﻳﻚ ﺭﻭﺵ ﺑﺮﺍﻱ ﺷﺮﻭﻉ ﮔﻔﺘﻪ ﻣﻲ ﺷﻮﺩ‪.‬ﺭﻭﺵ‬
‫ﻫﺎﻱ ﺑﻌﺪﻱ ﺑﻪ ﺗﺪﺭﻳﺞ ﺫﻛﺮ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪.‬‬
‫ﺷﺒﻴﻪ ﻧﺤﻮﻩ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻥ ﻳﻚ ‪، Station‬ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻫﻢ ﻣﻲ ﺗﻮﺍﻥ ﺩﺭ ﻗﺴﻤﺖ ﺳﻤﺖ ﭼﭗ ﺻﻔﺤﻪ‬
‫‪ SIMATIC MANAGER‬ﺑﺮ ﺭﻭﻱ ﻧﺎﻡ ﭘﺮﻭﮊﻩ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭﺩﺭ ﻗﺴﻤﺖ ‪ Insert New Object‬ﮔﺰﻳﻨﻪ‬
‫‪ PROFIBUS‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺑﺮﺍﻱ ﺍﻳﻦ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻳﻚ ﻧﺎﻡ ﻫﻢ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻭﮔﺮﻧﻪ ﺑﻪ ﺻﻮﺭﺕ‬
‫ﺧﻮﺩﻛﺎﺭ ﻧﺎﻡ)‪ PROFIBUS (1‬ﺑﺮﺍﻱ ﺁﻥ ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻳﻚ ﺍﺑﺰﺍﺭ ﺑﻪ ﻧﺎﻡ ‪ NetPro‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬ﺑﺮﺍﻱ ﻣﺸﺎﻫﺪﻩ ﻣﺠﻤﻮﻋﻪ ﻛﺎﺭﻫﺎﻳﻲ ﻛﻪ ﺩﺭ‬
‫ﮔﺎﻡ ﻫﺎﻱ ﻳﻚ ﺗﺎ ﺳﻪ ﺍﻧﺠﺎﻡ ﺩﺍﺩﻩ ﺍﻳﺪ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﺭﺍ ﺑﺎﺯ ﻧﻤﻮﺩﻩ ﻭﮔﺮﺍﻓﻴﻚ ﻛﻠﻲ ﻛﺎﺭ ﺭﺍ ﺑﺒﻴﻨﻴﺪ‪.‬ﺑﺮﺍﻱ ﺑﺎﺯ ﻛﺮﺩﻥ ﺍﻳﻦ‬
‫ﺑﺮﻧﺎﻣﻪ ﻳﺎ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺍﺯ ﻣﻨﻮﻱ ‪ Option‬ﮔﺰﻳﻨﻪ ‪ Configure Network‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻳﺎ ﺑﺮ ﺭﻭﻱ ﻛﻠﻴﺪ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ‬
‫‪Techno-Electro.com‬‬

‫‪٧٣‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫ﺍﺳﺖ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ ‪.‬ﺑﺮﻧﺎﻣﻪ ‪ Netpro‬ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ‪.‬‬ ‫ﮔﺰﻳﻨﻪ ﺩﺭ ﻗﺴﻤﺖ ﻧﻮﺍﺭ ﺍﺑﺰﺍﺭ ﺑﺎﻻﻱ ﺻﻔﺤﻪ ﻛﻪ ﺑﻪ ﺷﻜﻞ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻣﻲ ﺑﻴﻨﻴﺪ ﺗﺎ ﺍﻳﻨﺠﺎ ﻳﻚ‪ Station 400‬ﺑﻪ ﻧﺎﻡ )‪ SIMATIC 400(1‬ﻭﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﻪ‬
‫ﺍﺳﺖ‪Station400.‬‬ ‫ﻭﺟﻮﺩ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬ﺷﺒﻜﻪ ‪ MPI‬ﻫﻢ ﻛﻪ ﺑﻪ ﺻﻮﺭﺕ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺗﻮﺳﻂ ﺧﻮﺩ ‪ STEP 7‬ﺍﻳﺠﺎﺩ ﺷﺪﻩ‬
‫ﻫﻨﻮﺯ ﺩﺍﺭﺍﻱ ﻫﻴﭻ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ )‪ (CPU,I/O,...‬ﻧﻴﺴﺖ ﻭﺑﻪ ﻫﻴﭻ ﻛﺪﺍﻡ ﺍﺯ ﺷﺒﻜﻪ ﻫﺎﻱ ‪ MPI‬ﻭ‪ PROFIBUS‬ﻭﺻﻞ‬
‫ﻧﺸﺪﻩ ﺍﺳﺖ‬

‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ ‪ :‬ﺗﻨﻈﻴﻤﺎﺕ ﺷﺒﻜﻪ ‪PROFIBUS‬‬

‫ﺑﺮﺍﻱ ﺍﻧﺠﺎﻡ ﺗﻨﻈﻴﻤﺎﺕ ﺷﺒﻜﻪ ‪، PROFIBUS‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Netpro‬ﺭﻭﻱ ﺧﻂ ﺑﻨﻔﺶ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ PROFIBUS‬ﺭﺍﺳﺖ‬
‫ﻛﻠﻴﻚ ﻛﻨﻴﺪ ﻭﮔﺰﻳﻨﻪ ‪ Object Properties‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪.‬ﭘﻨﺠﺮﻩ ‪ Network Setting‬ﺭﺍ ﺑﺎﺯ ﻛﻨﻴﺪ‪).‬ﺷﻜﻞ ﺻﻔﺤﻪ‬
‫ﺑﻌﺪ( ﻫﻤﭽﻨﻴﻦ ﺑﺮﺍﻱ ﺑﺎﺯ ﻛﺮﺩﻥ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺩﺭ ﺻﻔﺤﻪ ﺍﺻﻠﻲ ‪، SIMATIC MANAGER‬ﺑﺮ ﺭﻭﻱ ﺷﻲ ﻣﺮﺑﻮﻁ‬
‫ﺑﻪ ‪ PROFIBUS‬ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ‪.‬‬
‫ﻼ ﺑﺎ ﻓﺸﺮﺩﻥ ﻛﻠﻴﺪ ‪ ، OK‬ﻛﻠﻴﻪ ﺗﻨﻈﻴﻤﺎﺕ ﭘﻴﺶ ﻓﺮﺽ ﺭﺍ ﺗﺄﻳﻴﺪ ﻛﻨﻴﺪ ‪.‬ﺩﺭ ﺍﺩﺍﻣﻪ ﭘﺎﺭﺍﻣﺘﺮ‬
‫ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Network Setting‬ﻓﻌ ﹰ‬
‫ﻫﺎﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻛﻪ ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﺩﻳﺪﻩ ﺷﺪﻧﺪ ﺭﺍ ﺑﺮﺭﺳﻲ ﻣﻲ ﻛﻨﻴﻢ‪ .‬ﭼﻨﺎﻧﭽﻪ ﺑﺮﺍﻱ ﺍﺩﺍﻣﻪ ﻛﺎﺭ ﻋﺠﻠﻪ ﺩﺍﺭﻳﺪ‪ ،‬ﻣﻲ‬
‫ﺗﻮﺍﻧﻴﺪﺑﺪﻭﻥ ﻣﻄﺎﻟﻌﻪ ﻣﻄﺎﻟﺐ ﺑﻌﺪﻱ‪ ،‬ﺍﺯ ﻗﺴﻤﺖ ‪ ٣-٢-٥‬ﺑﺤﺚ ﺭﺍ ﺩﻧﺒﺎﻝ ﻛﻨﻴﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٧٤‬‬

‫ﭘﺎﺭﺍﻣﺘﺮ ‪Highest PROFIBUS Address‬‬

‫ﺩﺭ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ EN 50 170‬ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﻣﻮﺳﻮﻡ ﺑﻪ ‪ (Highest- Station Address) HSA‬ﻣﻲ ﺑﺎﺷﺪ ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﺑﺮﺍﻱ‬
‫ﺑﻬﻴﻨﻪ ﺳﺎﺯﻱ ﻧﺤﻮﻩ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ ﻭﻣﺪﻳﺮﻳﺖ ﻛﺮﺩﻥ ﺣﻠﻘﻪ ‪، Token‬ﺯﻣﺎﻧﻲ ﻛﻪ ﭼﻨﺪﻳﻦ‪ Master‬ﺑﻪ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻭﺻﻞ ﻫﺴﺘﻨﺪ ﻭﺑﻪ ﻛﺎﺭ ﻣﻲ ﺭﻭﺩ‪.‬ﺍﻳﻦ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺭﺍ ﺩﺭ ﺁﻳﻨﺪﻩ ﻣﻮﺭﺩ ﺑﺮﺭﺳﻲ ﻗﺮﺍﺭ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺩ‪ .‬ﻓﻌ ﹰ‬
‫ﻼ ﺩﺭ ﺍﻳﻦ‬
‫ﻣﺜﺎﻝ ﻳﻚ ‪ Master‬ﺑﻴﺸﺘﺮ ﻧﺪﺍﺭﻳﻢ ﻭﻟﺬﺍ‪،‬ﻣﻘﺪﺍﺭ ﭘﻴﺶ ﻓﺮﺽ ﻳﻌﻨﻲ ‪ ١٢٦‬ﺭﺍ ﺗﻐﻴﻴﺮ ﻧﺪﻫﻴﺪ‪.‬‬
‫ﭘﺎﺭﺍﻣﺘﺮ ‪Transmission‬‬
‫ﺳﺮﻋﺘﻲ ﻛﻪ ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﻛﻨﻴﺪ ﺑﺮﺍﻱ ﺳﺮﺗﺎﺳﺮ ﻃﻮﻝ ﺷﺒﻜﻪ ﻭﻛﻠﻴﻪ ‪ node‬ﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺁﻥ‬
‫ﺍﻋﻤﺎﻝ ﻣﻲ ﺷﻮﺩ‪.‬ﺩﺭ ﻧﺘﻴﺠﻪ ﻛﻠﻴﻪ ﺗﺠﻬﻴﺰﺍﺕ ﻭ‪ Distributed I/O‬ﻫﺎﻳﻲ ﻛﻪ ﺑﻪ ﺍﻳﻦ ﺷﺒﻜﻪ ﻭﺻﻞ ﻣﻲ ﺷﻮﻧﺪ ﺑﺎﻳﺪ ﺭﻭﻱ ﻫﻤﻴﻦ‬
‫ﺳﺮﻋﺖ ﺗﻨﻈﻴﻢ ﺷﻮﻧﺪ‪.‬ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺍﻃﻼﻋﺎﺕ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻴﻦ ‪ 9.6kbps‬ﺗﺎ ‪ 12Mbps‬ﺗﻐﻴﻴﺮ ﻛﻨﺪ‪.‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ‬
‫ﻣﻲ ﺑﻴﻨﻴﺪ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺑﻪ ﺻﻮﺭﺕ ﭘﻴﺶ ﻓﺮﺽ ‪ 1.5Mbps‬ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪ Profile‬ﻫﺎﻱ ‪PROFIBUS‬‬
‫ﺑﺮﺍﻱ ﻛﺎﺭﺑﺮﺩ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻳﻚ ﺳﺮﻱ ﭘﺮﻭﻓﺎﻳﻞ ﻫﺎﻱ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬ﺩﺭ ﻭﺍﻗﻊ ﺍﻳﻦ ﭘﺮﻭﻓﺎﻳﻞ‬
‫ﻫﺎﻣﺠﻤﻮﻋﻪ ﺍﻱ ﺍﺯ ‪ Setting‬ﻫﺎ ﻫﺴﺘﻨﺪ ﻛﻪ ﺑﺮ ﺭﻭﻱ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺍﻧﺠﺎﻡ ﻣﻲ ﺷﻮﻧﺪ‪ .‬ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ‬
‫ﻫﺎ ﺗﻮﺳﻂ ‪ STEP7‬ﻣﺤﺎﺳﺒﻪ ﻭ‪ Set‬ﻣﻲ ﺷﻮﻧﺪ ﻭﻛﺎﻓﻲ ﺍﺳﺖ ﻣﺎ ‪ Profile‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﻢ ‪.‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﻛﻪ ﻣﺎﻧﻨﺪ‬
‫ﻧﺮﺥ ﺍﺭﺳﺎﻝ ‪،‬ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎ ﺑﻪ ﻛﻞ ﻣﺠﻤﻮﻋﻪ ﺷﺒﻜﻪ ﻭﺗﺠﻬﻴﺰﺍﺕ ﻣﺘﺼﻞ ﺑﻪ ﺁﻥ ﺍﻋﻤﺎﻝ ﻣﻲ ﺷﻮﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٧٥‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫ﺩﺭ ﺣﺎﻟﺘﻲ ﻛﻪ ﻧﺨﻮﺍﻫﻴﻢ ﺍﺯ ﭘﺮﻭﻓﺎﻳﻞ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ‪ STEP7‬ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﺎﻳﻴﻢ ﻣﻴﺘﻮﺍﻧﻴﻢ ﮔﺰﻳﻨﻪ ‪ User Defined‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ‬
‫ﻧﻤﻮﺩﻩ ﻭﺳﭙﺲ ﻣﺘﻨﺎﺳﺐ ﺑﺎ ﻛﺎﺭﺑﺮﺩ ﻣﻮﺭﺩ ﻧﻈﺮﻣﺎﻥ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﺭﺍ ﺗﻨﻈﻴﻢ ﻛﻨﻴﻢ‪.‬ﺩﺭ ﻏﻴﺮ ﺍﻳﻦ ﺻﻮﺭﺕ ﻣﻲ ﺑﺎﻳﺴﺖ ﺍﺯ ﻳﻜﻲ‬
‫ﺍﺯ ﭘﺮﻭﻓﺎﻳﻞ ﻫﺎﻱ ‪ Universal(DP/FMS),Standard,DP‬ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫ﺗﻮﺟﻪ ﺍﻳﻨﻜﻪ ‪،‬ﺗﻨﻈﻴﻢ ﺩﺳﺘﻲ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ‪،‬ﻧﻴﺎﺯﻣﻨﺪ ﺗﺠﺮﺑﻪ ﺍﺳﺖ ﻭ ﺗﻨﻬﺎ ﻳﻚ ﻣﻬﻨﺪﺱ ﺷﺒﻜﻪ ﺣﺮﻓﻪ ﺍﻱ ﻣﻲ ﺗﻮﺍﻧﺪ ﺍﺯ ﭘﺲ‬
‫‪Network‬‬ ‫ﺁﻥ ﺑﺮﺁﻳﺪ ﻭﺗﺮﺟﻴﺢ ﺑﺮﺁﻥ ﺍﺳﺖ ﻛﻪ ﺍﺯ ﻳﻜﻲ ﺍﺯ ‪ Profile‬ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪.‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺩﺭ ﭘﻨﺠﺮﻩ‬
‫‪ Setting‬ﺍﮔﺮ ﺣﺎﻟﺖ ‪ User Defined‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﻮﺩﻩ ﻭﺳﭙﺲ ﻛﻠﻴﺪ ‪ Bus Parameters‬ﺭﺍ ﻓﺸﺎﺭ ﺩﻫﻴﺪ ﻳﻚ ﭘﻨﺠﺮﻩ‬
‫ﺟﺪﻳﺪ ﻣﺮﺑﻮﻁ ﺑﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﺎﺯ ﻣﻲ ﺷﻮﺩﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻛﻪ ﺩﺭ ﺿﻤﻴﻤﻪ ‪ ٣‬ﺷﺮﺡ ﻣﺨﺘﺼﺮﻱ ﺭﺍﺟﻊ ﺑﻪ‬
‫ﺁﻧﻬﺎ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ ﻓﻘﻂ ﺑﺮﺍﻱ ﭘﺮﻭﻓﺎﻳﻞ ‪ User Defined‬ﻗﺎﺑﻞ ﺗﻐﻴﻴﺮ ﻫﺴﺘﻨﺪ‪.‬‬

‫ﺩﺭ ﺍﺩﺍﻣﻪ ﺑﻪ ﺑﺮﺭﺳﻲ ﻣﺨﺘﺼﺮ ﭘﺮﻭﻓﺎﻳﻞ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ‪ STEP7‬ﻣﻲ ﭘﺮﺩﺍﺯﻳﻢ‪.‬‬

‫‪DP Profile‬‬
‫ﺯﻣﺎﻧﻲ ﺍﻳﻦ ﭘﺮﻭﻓﺎﻳﻞ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ﻛﻪ ﺳﻴﺴﺘﻢ ﻣﻮﺭﺩ ﻧﻈﺮ ‪،‬ﻓﻘﻂ ﺷﺎﻣﻞ ﺷﺒﻜﻪ‪ PROFIBUS DP‬ﻭ ﺩﺍﺭﺍﻱ ﺳﺎﺧﺘﺎﺭ‬
‫‪ Master-Slave‬ﺑﺎﺷﺪ ﻛﻪ ﺍﺯﻳﻚ ﻳﺎ ﭼﻨﺪ ‪ Master‬ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﻭ ‪ Master‬ﻫﺎ ﻫﻤﮕﻲ ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ SIMATIC S7‬ﻭ‬
‫‪ SIMATIC M7‬ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺑﺎﺷﻨﺪ‪ .‬ﺑﺎ ﺗﻐﻴﻴﺮ ﺩﺭ ‪ node‬ﻫﺎ ﻭﺍﺿﺎﻓﻪ ﺷﺪﻥ ‪ Subnet‬ﻫﺎﻱ ﺟﺪﻳﺪ‪ STEP7 ،‬ﺑﻪ ﺻﻮﺭﺕ‬
‫ﺧﻮﺩﻛﺎﺭ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﺭﺍ ﺑﺎ ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻦ ﺗﻐﻴﻴﺮﺍﺕ ﺟﺪﻳﺪ‪،‬ﻣﺤﺎﺳﺒﻪ ﻣﻲ ﻛﻨﺪ‪ Subnet.‬ﻫﺎﻱ ﺟﺪﻳﺪ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺷﺎﻣﻞ‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪FIBUSPRO -DP‬‬ ‫‪٧٦‬‬

‫ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺑﺎﺷﻨﺪ‪:‬‬

‫‪ PC‬ﻳﺎ‪PG‬‬ ‫•‬

‫ﻭﺍﺣﺪ ‪HMI‬‬ ‫•‬

‫‪S7 node‬‬ ‫•‬
‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﻳﺎ ‪ FMS‬ﻛﻪ ﺑﻪ ﺻﻮﺭﺕ ‪ non-cyclic‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺪﻩ ﺑﺎﺷﻨﺪ‪.‬‬ ‫•‬

‫ﺗﻮﺟﻪ ﺍﻳﻨﻜﻪ ﺗﻨﻬﺎ ﺁﻥ ﺩﺳﺘﻪ ﺍﺯ ‪ node‬ﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﻣﺤﺎﺳﺒﻪ ﭘﺎﺭﺍﻣﺘﺮﻱ ﺑﺎﺱ ﻟﺤﺎﻅ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‬
‫ﻛﻪ ﺑﻪ ﺩﺭﺳﺘﻲ ﺗﻮﺳﻂ ‪ STEP7‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺪﻩ ﺑﺎﺷﻨﺪ‪.‬‬

‫‪StandardProfile‬‬
‫ﺯﻣﺎﻧﻲ ﺍﺯ ﺍﻳﻦ ﭘﺮﻭﻓﺎﻳﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﻴﻢ ﻛﻪ ﺑﺨﻮﺍﻫﻴﻢ ‪ node‬ﻫﺎﻳﻲ ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﺘﺼﻞ ﻛﻨﻴﻢ‪.‬ﻛﻪ ﺗﻮﺳﻂ‬
‫‪ STEP7‬ﻗﺎﺑﻞ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻧﺒﺎﺷﻨﺪ ﻭﻳﺎ ﻣﺘﻌﻠﻖ ﺑﻪ ﭘﺮﻭﮊﻩ ﺟﺎﺭﻱ ﻧﺒﻮﺩﻩ ﻭﺑﻪ ﭘﺮﻭﮊﻩ ﺩﻳﮕﺮﻱ ﺗﻌﻠﻖ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ‪.‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ‬
‫ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Network Setting‬ﺩﺭ ﻗﺴﻤﺖ ‪ Profile‬ﮔﺰﻳﻨﻪ ‪ Standard‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ‪ .‬ﺳﭙﺲ ﻛﻠﻴﺪ ‪ Options..‬ﺭﺍ‬
‫‪Include‬‬ ‫ﻓﺸﺎﺭ ﺩﻫﻴﺪ ﺗﺎ ﭘﻨﺠﺮﻩ ‪ Options‬ﺑﺎﺯ ﺷﻮﺩ ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ‪ Network Stations ،‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﻮﺩﻩ ﻭﮔﺰﻳﻨﻪ‬
‫‪ Network Configuration Below‬ﺭﺍ ﻓﻌﺎﻝ ﻛﻨﻴﺪ ‪.‬ﺩﺭ ﻏﻴﺮ ﺍﻳﻦ ﺻﻮﺭﺕ ﻧﺤﻮﻩ ﻣﺤﺎﺳﺒﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﻫﻤﺎﻧﻨﺪ ﻫﻤﺎﻥ‬
‫ﺍﻟﮕﻮﺭﻳﺘﻢ ﻣﺤﺎﺳﺒﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﺩﺭ ﺣﺎﻟﺖ ‪ DP‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻭ‪ node‬ﻫﺎﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻧﺸﺪﻩ ﺩﺭ ﭘﺮﻭﮊﻩ ﺟﺎﺭﻱ ﺭﺍ ﺩﺭ‬
‫ﻧﻈﺮ ﻧﺨﻮﺍﻫﺪ ﮔﺮﻓﺖ ‪.‬ﺍﻣﺎ ﺍﮔﺮ ﺍﻳﻦ ﮔﺰﻳﻨﻪ ﻓﻌﺎﻝ ﺷﻮﺩ ﻳﻚ ﺍﻟﮕﻮﺭﻳﺘﻢ ﻋﻤﻮﻣﻲ ﺭﺍ ﺑﻪ ﻛﺎﺭ ﺧﻮﺍﻫﺪ ﺑﺮﺩ ﻛﻪ ﺩﺭ ﻧﺘﻴﺠﻪ ‪ node‬ﻫﺎﻱ‬
‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻧﺸﺪﻩ ﺩﺭ ﭘﺮﻭﮊﻩ ﺟﺎﺭﻱ ﺭﺍ ﻫﻢ ﺩﺭ ﻣﺤﺎﺳﺒﺎﺕ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﻟﺤﺎﻅ ﺧﻮﺍﻫﺪ ﻛﺮﺩ‪.‬‬

‫‪Universal (DP/FMS) Profile‬‬

‫ﺯﻣﺎﻧﻲ ﺍﺯ ﺍﻳﻦ ﭘﺮﻭﻓﺎﻳﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﻴﻢ ﻛﻪ ﺩﺭ ﻣﺠﻤﻮﻋﻪ ﺗﺠﻬﻴﺰﺍﺕ ﻣﺘﺼﻞ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺍﺯ ﺗﺠﻬﻴﺰﺍﺕ ﺧﺎﻧﻮﺍﺩﻩ‬
‫ﻼ ‪ CP 5431‬ﻳﺎ ‪ CPU S5-95U‬ﺍﺳﺘﻔﺎﺩﻩ ﺷﺪﻩ ﺑﺎﺷﺪ‪.‬ﻳﺎ ﺯﻣﺎﻧﻲ ﻛﻪ ‪ Station‬ﻫﺎﻱ ‪ SIMATIC S7‬ﻭ‬
‫‪ SIMATIC S5‬ﻣﺜ ﹰ‬
‫‪ SIMATIC S5‬ﺑﻪ ﺻﻮﺭﺕ ﻫﻤﺰﻣﺎﻥ ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ﺑﻪ ﻋﻨﻮﺍﻥ ﺩﻭ ‪ node‬ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﻪ ﻛﺎﺭ ﺭﻓﺘﻪ‬
‫ﺑﺎﺷﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٧٧‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫ﭘﻨﺠﺮﻩ ‪Options‬‬
‫ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Network Setting‬ﺍﮔﺮ ﻛﻠﻴﺪ ‪ Options‬ﺭﺍ ﻓﺸﺎﺭ ﺩﻫﻴﺪ ﻳﻚ ﭘﻨﺠﺮﻩ ﺟﺪﻳﺪ ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺷﺎﻣﻞ ﺩﻭﻗﺴﻤﺖ‬
‫ﻳﻜﻲ ‪ Network Station‬ﻭﺩﻳﮕﺮﻱ ‪ Cables‬ﻣﻲ ﺑﺎﺷﺪ‪.‬‬

‫‪Network Station‬‬
‫ﻼ ﮔﻔﺘﻴﻢ ﻛﻪ ﺩﺭ ﺑﻌﻀﻲ ﻛﺎﺭﺑﺮﺩ ﻫﺎ ‪،‬ﻣﻤﻜﻦ ﺍﺳﺖ ‪ node‬ﻫﺎﻳﻲ ﺑﻪ ﻛﺎﺭ ﺑﺮﻳﻢ ﻛﻪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺁﻧﻬﺎ ﺗﻮﺳﻂ ‪ STEP7‬ﻣﻤﻜﻦ‬
‫ﻗﺒ ﹰ‬
‫ﻼ ﺩﺭ ﭘﺮﻭﻓﺎﻳﻞ ‪ Standard‬ﻫﻢ‬
‫ﻼ ﻳﻚ ‪ S5‬ﺭﺍ ﺑﻪ ﻋﻨﻮﺍﻥ ‪ node‬ﺷﺒﻜﻪ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻩ ﺑﺎﺷﻴﻢ ‪.‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺭﺍ ﻗﺒ ﹰ‬
‫ﻧﺒﺎﺷﺪ‪.‬ﻣﺜ ﹰ‬
‫ﺑﺤﺚ ﻛﺮﺩﻳﻢ ﻭ ﮔﻔﺘﻴﻢ ﻛﻪ ﺑﺮﺍﻱ ﺍﻳﻨﻜﻪ ﺩﺭ ﻣﺤﺎﺳﺒﺎﺕ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ‪ ،‬ﺍﻳﻦ ‪ node‬ﺭﺍ ﻫﻢ ﻟﺤﺎﻅ ﻛﺮﺩﻩ ﺑﺎﺷﻴﻢ ﺑﺎﻳﺪ ﮔﺰﻳﻨﻪ‬
‫‪Include Network Configuration Below‬ﺭﺍ ﻓﻌﺎﻝ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫ﻫﻤﺎﻥ ﻃﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻣﻲ ﺑﻴﻨﻴﺪ ﺩﺭ ﺯﻳﺮ ﺳﺘﻮﻥ ‪ In The Project‬ﻟﻴﺴﺖ ﺗﻌﺪﺍﺩ ‪ node‬ﻫﺎﻳﻲ ﻛﻪ ﺗﻮﺳﻂ ‪، STEP7‬ﭘﻴﻜﺮ‬
‫ﺑﻨﺪﻱ ﺷﺪﻩ ﺍﻧﺪ ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ ﺩﺭ ﻗﺴﻤﺖ ﺳﻤﺖ ﭼﭗ ﺩﺭ ﺯﻳﺮ ﺳﺘﻮﻥ ‪ In The Network‬ﻟﻴﺴﺖ ﺗﻌﺪﺍﺩ ‪ node‬ﻫﺎﻳﻲ‬
‫ﻛﻪ ﺩﺭ ﻣﺤﺎﺳﺒﺎﺕ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﺑﺎﻳﺪ ﻟﺤﺎﻅ ﺷﻮﻧﺪ ﺁﻣﺪﻩ ﺍﺳﺖ ﻛﻪ ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﺑﺎ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﻣﻘﺎﺩﻳﺮ ﻣﻨﺎﺳﺐ ‪ ،‬ﻣﻲ‬
‫ﺗﻮﺍﻧﻴﻢ ﺑﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﻣﻨﺎﺳﺐ ﺩﺳﺖ ﻳﺎﺑﻴﻢ ‪.‬ﺯﻳﺮﺍ ﺣﺎﻻ ﺩﻳﮕﺮ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻳﻲ ﻛﻪ ﺗﻮﺳﻂ ‪ STEP7‬ﻣﺤﺎﺳﺒﻪ ﻣﻲ ﺷﻮﻧﺪ ﺑﺎ‬
‫ﺩﺭ ﻧﻈﺮ ﮔﺮﻓﺘﻦ ﻫﻤﻪ ‪ node‬ﻫﺎﻱ ﺷﺒﻜﻪ ﺍﻋﻢ ﺍﺯ ‪ S7‬ﻭﻏﻴﺮ ‪ S7‬ﺻﻮﺭﺕ ﻣﻲ ﮔﻴﺮﺩ‪.‬ﺍﻳﻦ ﺻﻔﺤﻪ ﺩﺭ ﺣﺎﻟﺘﻲ ﻛﻪ ﭘﺮﻭﻓﺎﻳﻞ ‪ DP‬ﺭﺍ‬
‫ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺍﻳﺪ‪،‬ﻏﻴﺮ ﻓﻌﺎﻝ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٧٨‬‬

‫‪Cables‬‬
‫ﻃﻮﻝ ﻛﺎﺑﻞ ﻫﺎ‪ ،‬ﺗﻌﺪﺍﺩ ‪ Repeater‬ﻫﺎ ﺩﺭ ﺣﺎﻟﺖ ﻛﺎﺑﻞ ﻣﺴﻲ ﻭﺗﻌﺪﺍﺩ ‪ OLM‬ﻫﺎ ﺩﺭ ﺣﺎﻟﺖ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻣﻮﺍﺭﺩ ﺩﻳﮕﺮﻱ ﻫﺴﺘﻨﺪ‬
‫ﻛﻪ ﺩﺭ ﻣﺤﺎﺳﺒﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﻣﺆﺛﺮ ﻫﺴﺘﻨﺪ ‪.‬ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Option‬ﺑﺎ ﺍﻧﺘﺨﺎﺏ ‪، Cables‬ﻣﻄﺎﺑﻖ ﺷﻜﻞ ‪ ٣-١٤‬ﭘﻨﺠﺮﻩ ﺍﻱ‬
‫‪Take into account the following cable‬‬ ‫ﻇﺎﻫﺮ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺷﺎﻣﻞ ﺩﻭ ﻗﺴﻤﺖ ﺍﺳﺖ ‪.‬ﺍﺑﺘﺪﺍ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ﮔﺰﻳﻨﻪ‬
‫‪، configuration‬ﺑﻪ ‪ STEP7‬ﻣﻲ ﮔﻮﻳﻴﻢ ﻛﻪ ﻣﻘﺎﺩﻳﺮ ﻣﺮﺑﻮﻁ ﺑﻪ ﻛﺎﺑﻞ ﻫﺎﻱ ﺷﺒﻜﻪ ﺭﺍ ﺩﺭ ﻣﺤﺎﺳﺒﺎﺕ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﺩﺭ‬
‫ﻧﻈﺮ ﺑﮕﻴﺮﻳﺪ ﺳﭙﺲ ﺩﺭ ﻗﺴﻤﺖ ﭘﺎﻳﻴﻦ ﺍﻳﻦ ﺻﻔﺤﻪ ﻛﻪ ﻣﺸﺘﻤﻞ ﺑﺮ ﺩﻭﻗﺴﻤﺖ ﺍﺳﺖ)ﻳﻜﻲ ﻣﺮﺑﻮﻁ ﺑﻪ ﻛﺎﺑﻞ ﻣﺴﻲ ﻭﺩﻳﮕﺮﻱ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ﻛﺎﺑﻞ ﻧﻮﺭﻱ( ﻣﻘﺎﺩﻳﺮ ﻣﻨﺎﺳﺐ ﺭﺍ ﻭﺍﺭﺩ ﻣﻲ ﻛﻨﻴﻢ‪.‬‬

‫ﮔﺎﻡ ﭘﻨﺠﻢ‪ :‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ ﺑﺎ ﺑﺮﻧﺎﻣﻪ ‪HW Config‬‬
‫‪HW‬‬ ‫ﺩﺭ ﺍﻳﻦ ﻣﺒﺤﺚ ﺗﺎ ﺣﺪﻱ ﻛﻪ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺍﺳﺖ ﺑﻪ ﻣﻮﺿﻮﻉ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺗﻮﺳﻂ‬
‫‪ Config‬ﻣﻲ ﭘﺮﺩﺍﺯﻳﻢ‪ .‬ﻧﻜﺘﻪ ﺍﻱ ﻛﻪ ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺎﻳﺪ ﻣﻄﺮﺡ ﺷﻮﺩ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺑﺮﻧﺎﻣﻪ ‪ HW Config‬ﻭ ﺑﺮﻧﺎﻣﻪ ‪ Net Pro‬ﺍﺯ‬
‫ﺩﻭ ﺟﻨﺒﻪ ﻣﺨﺘﻠﻒ ﺑﻪ ﻳﻚ ﺳﻴﺴﺘﻢ ﻧﻈﺎﺭﺕ ﻣﻲ ﻛﻨﻨﺪ ﺑﻨﺎﺑﺮﺍﻳﻦ ﻭﻗﺘﻲ ﭘﻴﻜﺮﺑﻨﺪﻱ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺩﺭ ﻳﻜﻲ ﺭﺍ ﻣﻴﺨﻮﺍﻫﻴﻢ ﺗﻮﺳﻂ‬
‫ﺩﻳﮕﺮﻱ ﺑﺎﺯ ﻛﻨﻴﻢ ﻗﺒﻞ ﺍﺯ ﺁﻥ ﺣﺘﻤﺎ ﺑﺎﻳﺪ ﻋﻤﻞ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﺍﺩﻩ ﺑﺎﺷﻴﻢ‪.‬‬
‫ﺩﺭ ﻣﺜﺎﻝ ﺫﻛﺮ ﺷﺪﻩ ‪ ،‬ﺑﺎ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺁﻧﭽﻪ ﻛﻪ ﺩﺭ ‪ NetPro‬ﺩﺍﺭﻳﻢ ﺭﻭﻱ ﺁﻳﻜﻮﻥ )‪ SIMATIC 400(1‬ﺩﺭ ﭘﻨﺠﺮﻩ‬
‫‪ NetPro‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻣﻲ ﺑﻴﻨﻴﻢ ﻛﻪ ﺗﻮﺳﻂ ﺑﺮﻧﺎﻣﻪ ‪ HWConfig‬ﺑﺎﺯ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻳﻦ ﻛﺎﺭ ﺍﺯ ﺭﻭﺵ ﻫﺎﻱ ﺩﻳﮕﺮ ﻧﻴﺰ ﺍﻣﻜﺎﻥ‬
‫‪Station‬‬ ‫ﭘﺬﻳﺮ ﺍﺳﺖ‪ .‬ﺍﺯ ﺟﻤﻠﻪ ﺩﺭ ‪ Simatic Manager‬ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﺁﻳﻜﻮﻥ ‪ Hardware‬ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫‪Techno-Electro.com‬‬

‫‪٧٩‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫ﺩﺭ ‪ Hwconfig‬ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻛﺎﺗﺎﻟﻮﮒ ﭘﻨﺠﺮﻩ ﺳﻤﺖ ﺭﺍﺳﺖ ﺍﺯ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ‪ SIMATIC 400‬ﺍﺑﺘﺪﺍ ‪ Rack‬ﻣﻮﺭﺩ‬
‫ﻧﻈﺮ ) ﻣﺜﻼ ‪ (UR2‬ﺭﺍﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺳﭙﺲ ﻣﻨﺒﻊ ﺗﻐﺬﻳﻪ ﻭ ﭘﺲ ﺍﺯ ﺁﻥ ‪ CPU‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﺑﺘﺮﺗﻴﺐ ﺁﻧﻬﺎ ﺭﺍ ﺍﺯ ﺍﺳﻼﺕ‬
‫‪ CPU 416-2 DP‬ﺑﺎ ﻛﺪ ﺳﻔﺎﺭﺵ ‪6E S7 416-2XK00-‬‬ ‫ﺍﻭﻝ ﺑﻪ ﺑﻌﺪ ﻗﺮﺍﺭ ﻣﻴﺪﻫﻴﻢ‪ CPU .‬ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ‬
‫‪ 0AB0‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﭼﻮﻥ ﺍﻳﻦ ‪ CPU‬ﺍﺯ ﻧﻮﻉ ‪ 2-DP‬ﺍﺳﺖ ﻳﻚ ﭘﻮﺭﺕ ﻣﺨﺼﻮﺹ ﺍﺭﺗﺒﺎﻁ ‪ PROFIBUS DP‬ﺩﺍﺭﺩ‪ .‬ﻭﻗﺘﻲ‬
‫ﻛﻪ ﺍﻳﻦ ‪ CPU‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﻛﻨﻴﺪ ﻳﻚ ﭘﻨﺠﺮﻩ ﺑﺎﺯ ﻭ ﺍﺯ ﺷﻤﺎ ﭘﺮﺳﻴﺪﻩ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﭘﻮﺭﺕ ‪ 2-DP‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ ‪ CPU‬ﺭﺍ‬
‫ﻣﻲ ﺧﻮﺍﻫﻴﺪ ﺑﻪ ﻛﺪﺍﻡ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻭﺻﻞ ﻧﻤﺎﻳﻴﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٨٠‬‬

‫ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﻣﻲ ﺗﻮﺍﻧﻴﻢ ﻳﻚ ﺷﺒﻜﻪ ‪ DP‬ﺟﺪﻳﺪ ﺍﻳﺠﺎﺩ ﻛﻨﻴﻢ ﻛﻪ ﺑﺎ ﺯﺩﻥ ﻛﻠﻴﺪ ‪ New‬ﻳﻚ ﺷﺒﻜﻪ‪ PROFIBUS‬ﺟﺪﻳﺪ‬
‫ﻼ ﺑﺮﺍﻱ ﺗﻌﻴﻴﻦ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﺫﻛﺮ ﺷﺪ ﺭﺍ ﺑﺎﻳﺪ ﻃﻲ ﻛﻨﻴﻢ‪.‬ﻭﻟﻲ ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﻨﻈﻮﺭﻣﺎﻥ‬
‫ﺍﻳﺠﺎﺩ ﻧﻤﻮﺩﻩ ﻭﻫﻤﺎﻥ ﻣﺮﺍﺣﻠﻲ ﺭﺍ ﻛﻪ ﻗﺒ ﹰ‬
‫ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺍﻳﻦ ‪ CPU‬ﺭﺍ ﺑﻪ ﻫﻤﺎﻥ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻛﻪ ﻗﺒ ﹰ‬
‫ﻼ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻩ ﺑﻮﺩﻳﻢ ﻭﺻﻞ ﻛﻨﻴﻢ ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﺷﺒﻜﻪ‬
‫)‪ PROFIBUS(1‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬ﺁﺩﺭﺱ ‪ ٢‬ﺑﺮﺍﻱ ﺁﺩﺭﺱ ‪ Station‬ﺭﻭﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﺼﻮﺭﺕ ﭘﻴﺶ‬
‫ﻓﺮﺽ ﺩﺍﺩﻩ ﺷﺪﻩ ﻭ ﻟﺰﻭﻣﻲ ﻧﺪﺍﺭﺩ ﺁﻧﺮﺍ ﺗﻐﻴﻴﺮ ﺩﻫﻴﻢ‪.‬‬

‫ﭘﺲ ﺍﺯ ﻃﻲ ﺍﻳﻦ ﻣﺮﺍﺣﻞ ﻳﻚ ﺷﺒﻜﻪ‪ PROFIBUS‬ﻛﻪ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ‪ Master‬ﺑﻪ ﺁﻥ ﻭﺻﻞ ﺍﺳﺖ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻩ ﺍﻳﻢ‪.‬ﺩﺭ‬
‫ﻣﺮﺍﺣﻞ ﺑﻌﺪﻱ ﺗﻌﺪﺍﺩﻱ ‪ Slave‬ﻫﻢ ﺑﻪ ﺷﺒﻜﻪ ﺍﺿﺎﻓﻪ ﻣﻲ ﻛﻨﻴﻢ‪ .‬ﺑﺮﺍﻱ ﻏﻴﺮﻓﻌﺎﻝ ﻛﺮﺩﻥ ﻳﺎ ﻓﻌﺎﻝ ﻛﺮﺩﻥ ﻣﺠﺪﺩ ﺷﺒﻜﻪ ﻓﻮﻕ‬
‫ﻛﺎﻓﻴﺴﺖ ﺭﻭﻱ ‪ DP‬ﺩﺭ ﺍﺳﻼﺕ ‪ X3‬ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﻭ ﮔﺰﻳﻨﻪ ‪ Disconnect‬ﻳﺎ ‪ Add Master Sytem‬ﺭﺍ‬
‫ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫ﭘﺲ ﺍﺯ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ Hwconfig‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Net Pro‬ﻧﻴﺰ ﻣﻲ ﺗﻮﺍﻥ‪،‬ﻭﺿﻌﻴﺖ ﻣﻮﺟﻮﺩ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻛﺮﺩ‪.‬‬

‫ﮔﺎﻡ ﺷﺸﻢ‪:‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ DP Slave‬ﻫﺎ‬

‫ﺍﻟﻒ‪:‬ﺍﺗﺼﺎﻝ ‪ ET 200B‬ﺑﻪ ﺷﺒﻜﻪ ‪PROFIBUS‬‬
‫ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﺑﺎﻳﺪ ‪ DP Slave‬ﻫﺎ ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ‪ DP‬ﻭﺻﻞ ﻛﻨﻴﻢ‪ .‬ﺍﺑﺘﺪﺍ ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﻳﻚ ‪ ET 200B‬ﺑﻪ ﺷﺒﻜﻪ‬
‫‪DP‬‬ ‫‪PROFIBUS‬ﻭﺻﻞ ﻛﻨﻴﻢ‪ .‬ﺍﻳﻨﻜﺎﺭ ﺑﻪ ﺩﻭ ﺭﻭﺵ ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ‪ .‬ﺭﻭﺵ ﺍﻭﻝ ﺩﺭ ‪ NetPro‬ﺍﺑﺘﺪﺍ ﺭﻭﻱ ﭘﻮﺭﺕ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ‪ SIMATIC 400‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﺳﭙﺲ ﺍﺯ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﻛﻪ ﺩﺭ ﺳﻤﺖ ﺭﺍﺳﺖ ﺑﺮﻧﺎﻣﻪ ﻣﻮﺟﻮﺩ ﺍﺳﺖ ﺍﺯ ﺯﻳﺮ‬
‫ﻣﺠﻤﻮﻋﻪ ‪ PROFIBUS DP‬ﻭ ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ ET200B‬ﺭﻭﻱ ‪ B-16DI/16DO‬ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻣﻴﻜﻨﻴﻢ‪ .‬ﻣﺸﺎﻫﺪﻩ ﻣﻴﻜﻨﻴﻢ‬
‫‪Techno-Electro.com‬‬

‫‪٨١‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫ﻛﻪ ﺍﻳﻦ ﺍﻟﻤﺎﻥ ﺭﻭﻱ ﺷﺒﻜﻪ ﻗﺮﺍﺭ ﻣﻲ ﮔﻴﺮﺩ‪ .‬ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺩﺭ ﺷﻜﻞ ﺭﻭﺑﺮﻭ‬
‫‪NetPro‬‬ ‫ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬ﺑﺎ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ‪ ET200B‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺩﺭ‬
‫ﺷﻜﻠﻲ ﺷﺒﻴﻪ ﺯﻳﺮ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺷﺖ‪ .‬ﺍﻛﻨﻮﻥ ﺍﮔﺮ ﭘﺲ ﺍﺯ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺭﻭﻱ ﺍﻟﻤﺎﻥ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ‪ ET200B‬ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﻣﻲ ﺑﻴﻨﻴﻢ ﻛﻪ ﺳﺎﺧﺘﺎﺭ ﺩﺭ ﻣﺤﻴﻂ‬
‫‪ Hwconfig‬ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﺭﻭﺵ ﺩﻭﻡ ﺁﻧﺴﺖ ﻛﻪ ﺩﺭ ‪ HWConfig‬ﺍﺯ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﻛﻪ ﺷﺒﻴﻪ ﭘﻨﺠﺮﻩ‬

‫‪ ET200B‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻭ ﺭﻭﻱ ﺷﺒﻜﻪ‬ ‫‪ NetPro‬ﻣﻴﺒﺎﺷﺪ‬ ‫ﻛﺎﺗﺎﻟﻮﮒ‬
‫‪ PROFIBUS‬ﻣﺘﺼﻞ ﺑﻪ ‪ Master‬ﻗﺮﺍﺭ ﺩﻫﻴﻢ‪ .‬ﺍﮔﺮ ﭘﺲ ﺍﺯ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺩﺭ‬
‫‪ HWConfig‬ﺑﻪ ‪ Netpro‬ﺑﺮﮔﺮﺩﻳﻢ ﺷﻜﻞ ﺑﺎﻻ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﻢ ﻧﻤﻮﺩ‪ .‬ﻻﺯﻡ‬
‫ﺑﻪ ﺫﻛﺮ ﺍﺳﺖ ﺩﺭ ‪ Net pro‬ﺑﺮﺍﻱ ﻣﺸﺎﻫﺪﻩ ﺷﺒﻜﻪ ﺑﺎ ﻳﺎ ﺑﺪﻭﻥ ‪ Slave‬ﻫﺎ ﺍﺯ ﻣﻨﻮﻱ‬
‫‪ View‬ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﻭ ﺍﻧﺘﺨﺎﺏ ‪ With DP Slaves‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻨﻤﺎﻳﻴﻢ‪.‬‬

‫ﻧﻜﺘﻪ ﻗﺎﺑﻞ ﺫﻛﺮ ﺩﻳﮕﺮ ﺁﺩﺭﺱ ‪ Node‬ﺍﺳﺖ‪ .‬ﺁﺩﺭﺱ ﻫﺎ ﺑﺼﻮﺭﺕ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺗﻮﺳﻂ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺗﻌﻴﻴﻦ ﻣﻴﺸﻮﻧﺪ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ‬
‫ﺩﺭ ﺷﻜﻞ ﻫﺎﻱ ﻓﻮﻕ ﻣﻼﺣﻈﻪ ﻣﻴﺸﻮﺩ ﺁﺩﺭﺱ ‪ 1‬ﺑﻪ ‪ ET200B‬ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ Master .‬ﻧﻴﺰ ﺑﺼﻮﺭﺕ ﭘﻴﺶ‬
‫ﻓﺮﺽ ﺩﺍﺭﺍﻱ ﺁﺩﺭﺱ ‪ 2‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﻛﺎﺭﺑﺮ ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ﺻﻮﺭﺕ ﻟﺰﻭﻡ ﺍﻳﻦ ﺁﺩﺭ ﺳﻬﺎ ﺭﺍ ﺩﺭ ﻗﺴﻤﺖ ‪ Properties‬ﺗﻐﻴﻴﺮ ﺩﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٨٢‬‬

‫ﺩﺭ ‪ Hwconfig‬ﺟﺰﻳﻴﺎﺕ ﺑﻴﺸﺘﺮ ﻣﺮﺑﻮﻁ ﺑﻪ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻴﻬﺎﻱ ‪ ET 200B‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ‪.‬ﺁﺩﺭﺱ ﺁﻧﻬﺎ ﺩﺭ ﻗﺴﻤﺖ‬
‫ﭘﺎﻳﻴﻦ ﺻﻔﺤﻪ ‪ HW Config‬ﻳﻌﻨﻲ ﺩﺭ ‪ Configuration Table‬ﺩﻳﺪﻩ ﻣﻲ ﺷﻮﺩ‪ .‬ﺑﺮﺍﻱ ﺗﻐﻴﻴﺮ ﺍﻳﻦ ﺁﺩﺭﺱ ﻫﺎ ﻛﺎﻓﻴﺴﺖ ﺩﺭ‬
‫ﺍﻳﻦ ﺟﺪﻭﻝ ﺑﺮ ﺭﻭﻱ ﻛﺎﺭﺕ ﻣﺮﺑﻮﻃﻪ ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ‪.‬ﭘﻨﺠﺮﻩ ‪ Properties DP Slave‬ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺩﺭ ﻗﺴﻤﺖ‬
‫‪ Address I/O‬ﻣﻲ ﺗﻮﺍﻧﻴﺪ ‪ Start Address‬ﺭﺍ ﺗﻐﻴﻴﺮ ﺩﻫﻴﺪ‪ .‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺁﺩﺭﺱ ﻭﺭﻭﺩﻱ ﻫﺎ ﺍﺯ ‪ I0.0‬ﺗﺎ ‪ I1.7‬ﻭ ﺁﺩﺭﺱ‬
‫ﺧﺮﻭﺟﻲ ﻫﺎ ﺍﺯ ‪ Q0.0‬ﺗﺎ ‪ Q1.7‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﺁﺩﺭﺳﻬﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ‪ ET‬ﻫﺎ ﻧﺒﺎﻳﺪ ﺑﺎ‬
‫ﺁﺩﺭﺱ ﻛﺎﺭﺗﻬﺎﻱ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻛﻪ ﺭﻭﻱ ﺭﻙ ﺍﺻﻠﻲ ﻳﺎ ﺭﻙ ﺍﺿﺎﻓﻲ ﻧﺼﺐ ﺷﺪﻩ ﺍﻧﺪ ﺗﻼﻗﻲ ﭘﻴﺪﺍ ﻛﻨﺪ‪ .‬ﺁﺩﺭﺳﻬﺎﻳﻲ‬
‫ﻛﻪ ﺧﻮﺩ ﺳﻴﺴﺘﻢ ﺗﻌﻴﻴﻦ ﻣﻴﻜﻨﺪ ﺗﻼﻗﻲ ﻧﺪﺍﺭﻧﺪ ﻭﻟﻲ ﺩﺭ ﺻﻮﺭﺗﻲ ﻛﻪ ﻛﺎﺭﺑﺮ ﺑﺨﻮﺍﻫﺪ ﺁﻧﻬﺎ ﺭﺍ ﺗﻐﻴﻴﺮ ﺩﻫﺪ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺑﻪ ﻣﻮﺿﻮﻉ‬
‫ﻓﻮﻕ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺍﮔﺮ ﺩﺭ ﺻﻔﺤﻪ ﺍﺻﻠﻲ ‪ HW Config‬ﺑﺮ ﺭﻭﻱ ‪ ET 200B‬ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ‪.‬ﭘﻨﺠﺮﻩ ‪ Properties DP Slave‬ﺑﺎﺯ ﻣﻲ‬
‫ﺷﻮﺩ )ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ( ﺩﺭ ﺍﻳﻦ ﺻﻔﺤﻪ ﻳﻚ ﺳﺮﻱ ﺍﻃﻼﻋﺎﺕ ﻣﺎﻧﻨﺪ ‪ ، Order Number‬ﻣﺸﺨﺼﺎﺕ ‪ ET 200B‬ﺷﺎﻣﻞ‬
‫ﻧﻮﻉ ﻭﺗﻌﺪﺍﺩ ‪ I/O‬ﻫﺎ ﻭﻳﻚ ﺳﺮﻱ ﻣﺸﺨﺼﺎﺕ ﻣﻬﻢ ﺩﻳﮕﺮ ﺭﺍ ﻣﻲ ﺑﻴﻨﻴﺪ ﻛﻪ ﺩﺭ ﺍﺩﺍﻣﻪ ﺩﺭ ﻣﻮﺭﺩ ﺁﻧﻬﺎ ﺑﺤﺚ ﻣﻲ ﻛﻨﻴﻢ‪.‬‬
‫‪Diagnostic Address‬‬
‫ﭼﻨﺎﻧﭽﻪ ﺍﻳﻦ ‪ DP Slave‬ﻣﺸﻜﻠﻲ ﭘﻴﺪﺍ ﻛﻨﺪ ﺑﻪ ‪ CPU‬ﺍﻃﻼﻉ ﻣﻲ ﺩﻫﺪ ﻭﺍﻳﻦ ﺁﺩﺭﺱ ﺭﺍ ﺑﻪ ‪ CPU‬ﺑﺮ ﻣﻲ ﮔﺮﺩﺍﻧﺪ‪.‬ﺑﻪ ﺍﻳﻦ‬
‫ﺗﺮﺗﻴﺐ ﺍﻳﻦ ﺁﺩﺭﺱ ﻣﺸﺨﺺ ﻛﻨﻨﺪﻩ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﻛﺪﺍﻡ ‪ DP Slave‬ﻣﺸﻜﻞ ﭘﻴﺪﺍ ﻛﺮﺩﻩ ﺍﺳﺖ‪.‬ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ‪ OB 86‬ﺻﺪﺍ‬
‫ﺯﺩﻩ ﻣﻲ ﺷﻮﺩ ﻭﺁﺩﺭﺱ‪ Diagnostic‬ﺍﻳﻦ ‪) DP Slave‬ﺩﺭ ﺍﻳﻦ ﻣﺜﺎﻝ ‪ (16376‬ﺑﻪ ‪ OB 86‬ﻓﺮﺳﺘﺎﺩﻩ ﻣﻲ ﺷﻮﺩ ﻭﻣﺎ ﻣﻲ‬
‫ﺗﻮﺍﻧﻴﻢ ﺑﺎ ﺑﺮﻧﺎﻣﻪ ﺭﻳﺰﻱ ﻣﻨﺎﺳﺐ ﺍﻳﻦ ‪ ،OB‬ﻣﺘﻮﺟﻪ ﺷﻮﻳﻢ ﻛﻪ ﻛﺪﺍﻡ ‪) DP Slave‬ﺩﺭ ﺻﻮﺭﺕ ﻭﺟﻮﺩ ﭼﻨﺪﻳﻦ ‪(DP Slave‬‬
‫ﻭﺑﻪ ﭼﻪ ﺩﻟﻴﻞ ﻣﺸﻜﻞ ﭘﻴﺪﺍ ﻛﺮﺩﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٨٣‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫‪Node/Master System‬‬
‫ﺷﺒﻜﻪ ﺍﻳﻦ ‪DP Slave‬‬ ‫ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﻳﻚ ﺳﺮﻱ ﺍﻃﻼﻋﺎﺕ ﺭﺍﺟﻊ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻭﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺁﻥ ﻭﺁﺩﺭﺱ‬
‫ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺍﮔﺮ ﻛﺎﺭﺑﺮ ﺑﺨﻮﺍﻫﺪ ﺁﺩﺭﺱ ‪ Node‬ﺭﺍ ﻋﻮﺽ ﻛﻨﺪ ﻳﺎ ﺳﺮﻋﺖ ﺩﻳﮕﺮﻱ ﺑﺠﺰ ‪ 1.5 Mbps‬ﺍﻧﺘﺨﺎﺏ ﻛﻨﺪ‬
‫ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﻛﻠﻴﺪ ‪ PROFIBUS‬ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ﭘﻨﺠﺮﻩ ﺑﻌﺪﻱ ﺍﻳﻨﻜﺎﺭ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﺪ‪.‬‬
‫‪Parameter Assignment‬‬
‫ﺍﮔﺮ ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Properties‬ﺑﻪ ﺟﺎﻱ‪ Parameter Assignment ,General‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪،‬ﻳﻚ ﺳﺮﻱ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ ‪ DP Slave‬ﺭﺍ ﻣﻲ ﺑﻴﻨﻴﺪ ﻛﻪ ﻧﺤﻮﻩ ﺗﻨﻈﻴﻢ ﺁﻧﻬﺎ ﺩﺭ ﻛﺎﺗﺎﻟﻮﮒ ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻫﺮ ‪ DP Slave‬ﺁﻣﺪﻩ‬
‫ﺍﺳﺖ‪.‬ﺧﻮﺷﺒﺨﺘﺎﻧﻪ ‪ ،‬ﺑﺮﺍﻱ ‪ DP Slave‬ﻫﺎﻱ ﻣﺘﻌﻠﻖ ﺑﻪ ﺧﺎﻧﻮﺍﺩﻩ ‪ SIMATIC S7‬ﻧﻴﺎﺯﻱ ﻧﻴﺴﺖ ﻛﻪ ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮﻫﺎ ﺭﺍ ﺗﻨﻈﻴﻢ‬
‫ﻛﻨﻴﺪ ﻭﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮﻫﺎ ﺗﻮﺳﻂ ‪ HW Confing‬ﺑﻪ ﻃﻮﺭ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺗﻨﻈﻴﻢ ﻣﻲ ﺷﻮﻧﺪ‪.‬‬

‫ﺗﺎ ﺍﻳﻨﺠﺎ ﺗﻨﻈﻴﻤﺎﺕ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻛﻪ ﺑﺎﻳﺪ ﺩﺭ ﺷﺒﻜﻪ ‪ Master / Slave‬ﺑﺮﺍﻱ ‪ ET200B‬ﺍﻧﺠﺎﻡ ﺷﻮﺩ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪ‪.‬‬
‫ﺍﻣﺎ ﻳﻚ ﺗﻨﻈﻴﻢ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻧﻴﺰ ﺭﻭﻱ ﺧﻮﺩ ‪ ET200B‬ﻻﺯﻡ ﺍﺳﺖ ﺍﻧﺠﺎﻡ ﺷﻮﺩ‪ .‬ﺁﺩﺭﺳﻲ ﻛﻪ ﺭﻭﻱ ﺷﺒﻜﻪ ﺑﺮﺍﻱ ﺁﻥ ﻣﻨﻈﻮﺭ‬
‫ﺷﺪﻩ ﻭ ﺩﺭ ﺍﻳﻦ ﻣﺜﺎﻝ ‪ 1‬ﻣﻴﺒﺎﺷﺪ ﻻﺯﻡ ﺍﺳﺖ ﺗﻮﺳﻂ ‪ Dip Switch‬ﻫﺎﻱ ﺭﻭﻱ ﺧﻮﺩ ‪ ET‬ﻧﻴﺰ ﺗﻨﻈﻴﻢ ﮔﺮﺩﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬ ‫‪٨٤‬‬

‫ﺏ ‪:‬ﺍﺗﺼﺎﻝ ‪ ET 200M‬ﺑﻪ ﺷﺒﻜﻪ ‪PROFIBUS‬‬

‫ﺑﺮﺍﻱ ﺗﻜﻤﻴﻞ ﺑﺤﺚ ‪،‬ﻣﻄﺎﺑﻖ ﺑﺎ ﻣﺜﺎﻝ ﺫﻛﺮ ﺷﺪﻩ ﺩﺭ ﺍﺑﺘﺪﺍﻱ ﺍﻳﻦ ﺑﺨﺶ ‪،‬ﻳﻚ ‪ ET 200M‬ﻧﻴﺰ ﺑﻪ ﺷﺒﻜﻪ ﻣﺘﺼﻞ ﻣﻲ‬
‫ﻛﻨﻴﻢ‪.‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻲ ﺩﺍﻧﻴﺪ ‪ ET 200M‬ﺑﺮﺧﻼﻑ ‪ ET200B‬ﻣﺪﻭﻻﺭ ﺍﺳﺖ ﻭ ﻣﻲ ﺗﻮﺍﻥ ﺗﻌﺪﺍﺩﻱ ﻛﺎﺭﺕ ‪ I/O‬ﺑﻪ ﺁﻥ‬
‫ﺍﺿﺎﻓﻪ ﻛﺮﺩ‪.‬‬
‫ﺑﻪ ﻫﻤﺎﻥ ﺷﻴﻮﻩ ﻛﻪ ‪ ET 200B‬ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻭﺻﻞ ﻛﺮﺩﻳﻢ ﺩﺭ ﺍﻳﻨﺠﺎ ﻧﻴﺰ‬
‫‪ ET 200M‬ﺭﺍ ﺑﺎ ﺍﻧﺘﺨﺎﺏ ﻧﻮﻉ‪ IM 153-2‬ﺑﻪ ﺷﺒﻜﻪ ﻣﺘﺼﻞ ﻣﻴﻜﻨﻴﻢ ﻭﺩﺭ ﭘﻨﺠﺮﻩ ﺍﻱ ﻛﻪ‬
‫ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ ﺁﺩﺭﺱ ﺷﺒﻜﻪ ﺍﻳﻦ ‪ DP Slave‬ﺭﺍ ‪ 3‬ﻗﺮﺍﺭ ﻣﻴﺪﻫﻴﻢ‪ .‬ﺍﻳﻦ ﺗﻨﻈﻴﻢ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ‬
‫‪IM‬‬ ‫ﺑﺮﺍﻱ ‪ ET200B‬ﻧﻴﺰ ﮔﻔﺘﻪ ﺷﺪ ﺭﻭﻱ ﺧﻮﺩ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻧﻴﺰ ﺑﺎﻳﺪ ﺍﻧﺠﺎﻡ ﺷﻮﺩ‪ .‬ﺭﻭﻱ‬
‫ﺗﻌﺪﺍﻱ ‪ DIP Switch‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺩﺭ ﻛﻨﺎﺭ ﺁﻧﻬﺎ ﺍﻋﺪﺍﺩﻱ ﻧﻮﺷﺘﻪ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺁﺩﺭﺱ‬
‫ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺑﺎﻳﺪ ﺑﺎ ﺗﺮﻛﻴﺐ ﺍﻋﺪﺍﺩ ﻓﻮﻕ ﺑﺴﺎﺯﻳﻢ ﻭ ﺳﻮﺋﻴﭻ ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﺁﻥ ﺍﻋﺪﺍﺩ ﺭﺍ‬
‫ﺩﺭ ﻭﺿﻌﻴﺖ ‪ ON‬ﻗﺮﺍﺭ ﺩﻫﻴﻢ‪ .‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺮﺍﻱ ﺳﺎﺧﺘﻦ ﺁﺩﺭﺱ ‪ 3‬ﺑﺎﻳﺪ ﺍﺯ ‪ 1+2‬ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﻛﻨﻴﻢ ﭘﺲ ﻫﻤﺎﻧﻨﺪ ﺷﻜﻞ ﺳﻮﺋﻴﭻ ﻫﺎﻱ ‪ 1‬ﻭ ‪ 2‬ﺭﺍ ‪ ON‬ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫ﭘﺲ ﺍﺯ ﻗﺮﺍﺭ ﺩﺍﺩﻥ ‪ IM153-2‬ﺭﻭﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﻴﺒﻴﻨﻴﻢ ﻛﻪ ‪ 11‬ﺍﺳﻼﺕ‬
‫‪ ET200M‬ﺭﺍ ﺑﺎ ﻳﻚ ‪Station 300‬‬ ‫ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪ .‬ﺍﺯ ﻫﻤﻴﻦ ﺟﺎ ﺧﻮﺍﻧﻨﺪﻩ ﺑﺎﻳﺪ ﺷﺒﺎﻫﺖ‬
‫ﺩﺭ ﻧﻈﺮ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻨﺠﺎ ‪ CPU‬ﻧﺪﺍﺭﻳﻢ‪ .‬ﻛﺎﺭﺗﻬﺎﻱ ﻣﺨﺘﻠﻒ ﻭﺭﻭﺩﻱ ﻭ‬
‫ﺧﺮﻭﺟﻲ ﺁﻧﺎﻟﻮﮒ ﻭ ﺩﻳﺠﻴﺘﺎﻝ ‪ ،‬ﻛﺎﺭﺗﻬﺎﻱ ﺷﺒﻜﻪ ﻭ ﻛﺎﺭﺗﻬﺎﻱ ‪ FM‬ﻣﻴﺘﻮﺍﻧﻨﺪ ﺩﺭ‬
‫ﻛﺎﺗﺎﻟﻮﮒ ﺍﺯ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ‪ IM153-2‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺭﻭﺑﺮﻭ ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﻭ ﺩﺭ‬
‫ﺍﺳﻼﺗﻬﺎﻱ ‪ 4‬ﺗﺎ ‪ 11‬ﻗﺮﺍﺭ ﮔﻴﺮﻧﺪ‪.‬ﺗﻨﻈﻴﻤﺎﺕ ﺯﻳﺎﺩﻱ ﻣﺎﻧﻨﺪ ﺗﻨﻈﻴﻢ ﺁﺩﺭﺱ ﻫﺎ ﻭ ﻓﻌﺎﻝ‬
‫ﻛﺮﺩﻥ ﻭﻗﻔﻪ ﻫﺎ ﺑﺮﺍﻱ ﺍﻳﻦ ﻛﺎﺭﺗﻬﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻭﻟﻲ ﭘﺮﺩﺍﺧﺘﻦ ﺑﻪ ﺁﻧﻬﺎ ﺍﺯ ﺣﻮﺻﻠﻪ ﺍﻳﻦ‬
‫ﻛﺘﺎﺏ ﺧﺎﺭﺝ ﺍﺳﺖ ﻭ ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﻣﻴﺘﻮﺍﻧﺪ ﺟﺰﺋﻴﺎﺕ ﻣﻮﺿﻮﻉ ﺭﺍ ﺩﺭ ﺗﻨﻈﻴﻤﺎﺕ‬
‫ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ‪ S7-300‬ﺩﺭ ﻛﺘﺎﺏ ﺭﺍﻫﻨﻤﺎﻱ ﺟﺎﻣﻊ ‪ Step7‬ﻣﻼﺣﻈﻪ ﻧﻤﺎﻳﺪ‪.‬‬
‫ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ Master/Slave‬ﺭﺍ ﻛﻪ ﺷﺎﻣﻞ ﻳﻚ ‪ Master‬ﻭﺩﻭ ‪ Slave‬ﻣﻲ ﺑﺎﺷﺪ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﺍﺩﻳﻢ‪ .‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ‬
‫‪Techno-Electro.com‬‬

‫‪٨٥‬‬ ‫ﺍﻳﺠﺎﺩ ﭘﺮﻭﮊﻩ ﺷﺎﻣﻞ ﺷﺒﻜﻪ ‪PROFIBUS -DP‬‬

‫‪ HW Confing‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺭﺍ ‪ Save‬ﻧﻤﺎﻳﻴﺪ‪ .‬ﺍﮔﺮ ﻧﺘﻴﺠﻪ ﻛﺎﺭ ﺭﺍ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ NetPro‬ﺑﺒﻴﻨﻴﻢ ﺷﻜﻠﻲ ﺑﺼﻮﺭﺕ‬
‫ﺯﻳﺮ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺷﺖ‪.‬‬

‫ﺑﺎﺯ ﺗﺄﻛﻴﺪ ﻣﻲ ﻛﻨﻴﻢ ﻛﻪ ﻣﺪﻭﻟﻬﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ‪ DP Slave‬ﻋﻴﻨﹰﺎ ﻫﻤﺎﻧﻨﺪ ﻣﺪﻭﻟﻬﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ‪ Master‬ﻋﻤﻞ ﻣﻲ ﻛﻨﻨﺪ ﻳﻌﻨﻲ‬
‫ﻻ ﺑﻪ ﻟﺤﺎﻅ ﻧﻮﻉ ﭘﺬﻳﺮﺵ ﻭﻗﻔﻪ ﻫﺎ ﻭﻋﻤﻠﻜﺮﺩ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺗﻔﺎﻭﺗﻲ ﺑﻴﻦ ﺍﻳﻦ ﻣﺪﻭﻟﻬﺎ ﻭ ﻣﺪﻭﻟﻬﺎﻱ ‪ Central‬ﻭﺟﻮﺩ‬
‫ﺍﻭ ﹰ‬
‫ﻧﺪﺍﺭﺩ‪،‬ﺛﺎﻧﻴﹰﺎ ﻧﺤﻮﻩ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﻣﺪﻭﻟﻬﺎ ﻋﻴﻨﹰﺎ ﺷﺒﻴﻪ ﻣﺪﻭﻟﻬﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ‪ Master‬ﺍﺳﺖ‪ .‬ﺑﺮﺍﻱ ﺭﻭﺷﻦ ﺷﺪﻥ ﻣﻮﺿﻮﻉ ﻓﺮﺽ‬
‫ﻛﻨﻴﺪ ﻳﻚ ﻛﺎﺭﺕ ‪ DI‬ﻣﺘﻌﻠﻖ ﺑﻪ ﻳﻚ ‪ ET‬ﺑﺎ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ‪ ٢٥٦‬ﺩﺍﺭﻳﻢ‪.‬ﺍﻳﻦ ﺁﺩﺭﺱ ﺑﻪ ﺻﻮﺭﺕ ﺧﻮﺩﻛﺎﺭ ﺩﺭ ﺯﻣﺎﻥ ﭘﻴﻜﺮ‬
‫ﺑﻨﺪﻱ ﺗﻮﺳﻂ ‪ STEP7‬ﺑﻪ ﺍﻳﻦ ﻛﺎﺭﺕ ﺗﺨﺼﻴﺺ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ ﻭﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﻳﺪﻳﺪ ﻣﻲ ﺗﻮﺍﻥ ﺍﻳﻦ ﺁﺩﺭﺱ ﺭﺍ ﺩﺭﻗﺴﻤﺖ‬
‫ﭘﺎﻳﻴﻦ ﺻﻔﺤﻪ ‪ HW Confing‬ﻣﺸﺎﻫﺪﻩ ﻭ ﺩﺭ ﺻﻮﺭﺕ ﻟﺰﻭﻡ ﺗﻐﻴﻴﺮ ﺩﺍﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﺷﺮﺍﻳﻂ ﺑﺮﺍﻱ ﺧﻮﺍﻧﺪﻥ ﺳﻴﮕﻨﺎﻝ ﺍﺯ ﺍﻳﻦ‬
‫ﻭﺭﻭﺩﻱ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺯ ﺩﺳﺘﻮﺭ ﺯﻳﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪:‬‬
‫‪A I 256.0‬‬
‫ﻧﻮﺷﺘﻪ ﻣﻲ ﺷﻮﺩ ﻭﺍﺯ ﻃﺮﻳﻖ ﺍﻳﻦ ‪ CPU‬ﺑﻪ‬ ‫ﻼ ﺩﺭ ﺑﻼﻙ ‪OB1‬‬
‫‪ Master CPU‬ﻣﺜ ﹰ‬ ‫ﺩﺳﺘﻮﺭ ﻓﻮﻕ ‪،‬ﺩﺭ ﻳﻜﻲ ﺍﺯ ﺑﻼﻛﻬﺎﻱ‬
‫ﺳﺎﺩﮔﻲ ﺑﻪ ‪ Distributed I/O‬ﺩﺳﺘﺮﺳﻲ ﭘﻴﺪﺍ ﻣﻲ ﻛﻨﻴﻢ‪.‬ﻳﻌﻨﻲ ﺩﻗﻴﻘﹰﺎ ﻣﺜﻞ ‪ I/O‬ﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ‪ Master‬ﺑﺎ ﺁﻧﻬﺎ ﺭﻓﺘﺎﺭ ﻣﻲ‬
‫ﻛﻨﻴﻢ‪ .‬ﻓﺮﺿﹰﺎ ﺍﮔﺮ ﻗﺮﺍﺭ ﺑﻮﺩ ﺑﻪ ﻳﻚ ﻛﺎﺭﺕ ‪ DI‬ﺑﺎ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ‪ ٢٥٦‬ﺑﺮﺭﻭﻱ ﺧﻮﺩ ‪ Master‬ﻫﻢ ﺩﺳﺘﺮﺳﻲ ﭘﻴﺪﺍ ﻛﻨﻴﻢ ﺑﺎﺯ ﻫﻢ‬
‫ﻣﻲ ﻧﻮﺷﺘﻴﻢ‪ A I 256.0‬ﻭﺩﺭ ﻧﺤﻮﻩ ﻛﺎﺭ ﺗﻐﻴﻴﺮﻱ ﺍﻳﺠﺎﺩ ﻧﻤﻲ ﺷﺪ‪.‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺑﺮﺍﻱ ﺳﻴﮕﻨﺎﻟﻬﺎﻱ ﺁﻧﺎﻟﻮﮒ ﻧﻴﺰ ﺷﺒﻴﻪ ﺣﺎﻟﺖ‬
‫‪ Central‬ﺑﺎﻳﺪ ﺍﺯ ﺁﺩﺭﺱ ﺩﻫﻲ ‪ Peripheral I/O‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ ﻣﺎﻧﻨﺪ ‪:‬‬
‫‪L‬‬ ‫‪PIW0‬‬
‫ﻳﺎ‬
‫‪T PQW0‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪CP‬‬ ‫‪٨٦‬‬

‫‪DP‬‬ ‫ﺩﺭ ﻣﺜﺎﻝ ﻗﺒﻠﻲ ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ‪ Master‬ﺑﻪ ﺷﺒﻜﻪ ﺍﺯ ﭘﻮﺭﺕ ‪ DP‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ CPU‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻳﻢ‪ .‬ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﺷﺒﻜﻪ‬
‫ﻼ ﮔﻔﺘﻪ ﺷﺪ ﻣﻲ ﺗﻮﺍﻥ ﺍﺯ ﻣﺪﻭﻟﻬﺎﻱ ‪ IM،CP‬ﻳﺎ ‪ IF‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪.‬‬
‫ﻭﺍﺗﺼﺎﻝ ‪ Master‬ﺑﻪ ﺁﻥ‪ ،‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒ ﹰ‬
‫‪ ٣-٤‬ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ﺷﺒﻜﻪ‬
‫ﺍﻟﻒ( ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪CP‬‬
‫ﺑﺮﺍﻱ ﺣﺎﻟﺖ ‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪ ،CP‬ﻳﻚ ‪ Station 300‬ﺍﻳﺠﺎﺩﻛﻨﻴﺪ ﻭﺍﺯ ﻳﻚ ‪ CPU‬ﻣﻌﻤﻮﻟﻲ ﻛﻪ ﻓﺎﻗﺪ ﭘﻮﺭﺕ ‪ DP‬ﺍﺳﺖ‬
‫ﻼ ‪ CPU 312‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﺪ ﻭﺑﻪ ﺁﻥ ﻣﺪﻭﻝ ‪ CP 342-5‬ﺭﺍ ﺍﺿﺎﻓﻪ ﻛﻨﻴﺪ ﻭﻗﺘﻲ ﺍﻳﻦ‪ CP‬ﺭﺍ ﺑﻪ ‪ Rack‬ﺍﺿﺎﻓﻪ ﻣﻲ ﻛﻨﻴﺪ‬
‫ﻣﺜ ﹰ‬
‫ﻫﻤﺎﻥ ﭘﻨﺠﺮﻩ ﺷﻜﻞ ‪ ٣-١٨‬ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ ﻛﻠﻴﺪ ‪ New‬ﺭﺍ ﻓﺸﺎﺭ ﺩﻫﻴﺪ ﻭﻧﺎﻡ )‪ PROFIBUS (1‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ ‪.‬ﺳﭙﺲ‬
‫ﺑﺮﺭﻭﻱ ﻛﺎﺭﺕ ‪ CP‬ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ ﻭﺩﺭ ﻗﺴﻤﺖ ‪ Operating Mode‬ﺣﺎﻟﺖ ‪ DP Master‬ﺭﺍﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ‪.‬‬

‫ﺍﺩﺍﻣﻪ ﻛﺎﺭ ﺷﺒﻴﻪ ﺁﻧﭽﻪ ﻗﺒﻼ ﺫﻛﺮ ﺷﺪ ﻣﻴﺒﺎﺷﺪ‪ .‬ﻣﻴﺘﻮﺍﻥ ‪ Slave‬ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺭﻭﻱ ﺷﺒﻜﻪ ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﻗﺮﺍﺭ ﺩﺍﺩ ﻭ ﺁﻧﻬﺎ ﺭﺍ‬
‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻛﺮﺩ‪ .‬ﺍﮔﺮﭼﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ﻛﺎﺭﺕ ‪ CP‬ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﺑﺮﺧﻲ ﺍﺯ ‪ Slave‬ﻫﺎ ﻭﺟﻮﺩ ﻧﺪﺍﺷﺘﻪ‬
‫ﻳﺎﺷﺪ‪.‬ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺩﺭ ‪ Netpro‬ﺷﻜﻞ ‪ Station 300‬ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺍﺳﺖ ﻭ ﻣﺸﺎﻫﺪﻩ ﻣﻴﺸﻮﺩ ﻛﻪ ﺍﺗﺼﺎﻝ ﺑﻪ‬
‫‪ PROFIBUS‬ﺍﺯ ﻃﺮﻳﻖ ‪ CP‬ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٨٧‬‬ ‫ﺍﻳﺠﺎﺩ ‪ Master‬ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ ‪ IM‬ﻭ ‪IF‬‬

‫‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪IM‬‬ ‫ﺏ(‬

‫ﺑﺮﺧﻲ ﺍﺯ ﻛﺎﺭﺗﻬﺎﻱ ‪ IM‬ﻭ ﺁﻧﻬﻢ ﺻﺮﻓﺎ ﺑﺮﺍﻱ ‪ S7-400‬ﻣﻴﺘﻮﺍﻧﻨﺪ ﻧﻘﺶ ‪ Master‬ﺭﺍ ﺍﻳﻔﺎ ﻛﻨﻨﺪ‪ .‬ﻛﺎﺭﺕ ‪ IM467‬ﺍﺯ ﺍﻳﻦ‬
‫ﺟﻤﻠﻪ ﺍﺳﺖ‪ .‬ﺷﻜﻞ ﺯﻳﺮ ﻳﻚ ‪ Station 400‬ﺭﺍ ﺑﺎ ﻛﺎﺭﺕ ‪ IM467‬ﺑﻌﻨﻮﺍﻥ ‪ Master‬ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬

‫‪ Master‬ﺑﺎ ﻣﺪﻭﻝ ‪IF‬‬ ‫ﺝ(‬

‫‪CPU‬‬ ‫ﻣﺪﻭﻝ ‪ IF‬ﻧﻴﺰ ﺧﺎﺹ ‪ S7-400‬ﺍﺳﺖ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻌﻨﻮﺍﻥ ﻳﻚ ‪ Master‬ﻣﺴﺘﻘﻞ ﺍﺯ ‪ CPU‬ﻋﻤﻞ ﻛﻨﺪ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ‬
‫‪ 417-4‬ﺩﺍﺭﺍﻱ ﻗﺎﺑﻠﻴﺖ ﻧﺼﺐ ﻛﺎﺭﺕ ‪ IF‬ﺑﺎﺷﺪ ﺍﮔﺮ ﻧﻮﻉ‪ V1.1‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ ‪.‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻣﻲ ﺑﻴﻨﻴﺪ ﺍﻳﻦ‬
‫‪ CPU‬ﺩﻭ ﻋﺪﺩ ‪ IF‬ﺭﺍ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲ ﻛﻨﺪ‪.‬ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻳﻚ ﻋﺪﺩ ﻣﺪﻭﻝ ‪ IF 964-DP‬ﻛﻪ ﺩﺭ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺩﺭ ﺯﻳﺮ‬
‫ﻣﺠﻤﻮﻋﻪ ‪ CPU‬ﻣﺮﺑﻮﻃﻪ ﻗﺮﺍﺭ ﺩﺍﺭﺩ ﺑﻪ ﺍﺳﻼﺕ ﻣﺮﺑﻮﻃﻪ‪ ،‬ﻛﻨﺎﺭ ‪ CPU‬ﺍﺿﺎﻓﻪ ﺷﺪﻩ ﻭ ‪ Master System‬ﺟﺪﻳﺪﻱ ﺍﻳﺠﺎﺩ‬
‫ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﻣﺪﻭﻝ ‪ IF‬ﺭﻭﻱ ﺧﻮﺩ ‪ CPU‬ﻧﺼﺐ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪ Master System‬ﺑﺼﻮﺭﺕ ﺗﺮﻛﻴﺒﻲ‬ ‫‪٨٨‬‬

‫‪ ٤-٤‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﭼﻨﺪ ‪ Master System‬ﺑﺼﻮﺭﺕ ﺗﺮﻛﻴﺒﻲ‬

‫ﻣﻴﺘﻮﺍﻥ ﺩﺭ ﻳﻚ ‪ Station‬ﺗﺮﻛﻴﺒﻲ ﺍﺯ ‪ Master‬ﻫﺎﻱ ﻓﻮﻕ ﺭﺍ ﻗﺮﺍﺭ ﺩﺍﺩ ﻭ ﻫﺮﻛﺪﺍﻡ ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ ﺟﺪﺍﮔﺎﻧﻪ ﺍﻱ ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪.‬‬
‫ﺷﺎﻳﺪ ﺑﺘﻮﺍﻥ ﮔﻔﺖ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺑﺎﻻﺗﺮ ﺍﺳﺖ ﻭ ﺩﺭ ﺻﻮﺭﺕ ﻗﻄﻊ ﺷﺪﻥ ﻳﻚ ﺷﺒﻜﻪ ﺳﺎﻳﺮ ﺷﺒﻜﻪ ﻫﺎ ﻣﻴﺘﻮﺍﻧﻨﺪ‬
‫ﺑﻜﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﺩﻫﻨﺪ‪ .‬ﺷﻜﻞ ﺯﻳﺮ ﺗﺮﻛﻴﺒﻲ ﺍﺯ ‪ Master‬ﻫﺎ ﺭﺍ ﺑﺮﺍﻱ ﻳﻚ ‪ Station 400‬ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬

‫ﺗﺬﻛﺮ ﻣﻬﻢ‪:‬‬
‫ﭼﻪ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Hwconfig‬ﻭ ﭼﻪ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Netpro‬ﭘﺲ ﺍﺯ ﺗﻜﻤﻴﻞ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺑﺎﻳﺪ ﭼﻚ ﺳﺎﺯﮔﺎﺭﻱ‬
‫ﺍﺟﺰﺍ )‪(Consistency Check‬ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﻴﻢ‪ .‬ﺩﺭ ‪ HWconfig‬ﺍﺯ ﻣﻨﻮﻱ ‪ Station‬ﻭ ﺩﺭ ‪ Netpro‬ﺍﺯ ﻣﻨﻮﻱ‬
‫‪ Network‬ﺑﺮﺍﻱ ﺍﻳﻨﻜﺎﺭ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪.‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﺭ ‪ Hwconfig‬ﺍﮔﺮ ‪ ET‬ﻣﺪﻭﻻﺭ ﺑﻪ ﺷﺒﻜﻪ ﻣﺘﺼﻞ ﻛﺮﺩﻩ ﻭﻟﻲ‬
‫ﻫﻴﭽﮕﻮﻧﻪ ﻛﺎﺭﺗﻲ ﺩﺭ ﺁﻥ ﻗﺮﺍﺭ ﻧﺪﻫﻴﻢ ﺍﻳﻦ ﻳﻚ ﺍﺷﻜﺎﻝ ﺍﺳﺖ ﻛﻪ ﺑﺎ ﺍﺟﺮﺍﻱ ﭼﻚ ﺗﻮﺳﻂ ﺑﺮﻧﺎﻣﻪ ﭘﻴﻐﺎﻡ ﺷﻜﻞ ﺯﻳﺮ ﺭﺍ ﻣﺸﺎﻫﺪﻩ‬
‫ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩﻳﺎ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﺭ ‪ Netpro‬ﺍﮔﺮ ﺁﺩﺭﺱ ‪ Node‬ﻫﺎ ﺗﻼﻗﻲ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﺍﻋﻼﻡ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٨٩‬‬ ‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎ‬

‫‪ ٥-٤‬ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎ‬
‫‪ DP Slave‬ﻫﺎ ﻣﻨﺤﺼﺮ ﺑﻪ ‪ ET‬ﻫﺎ ﻧﻴﺴﺘﻨﺪ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒﻼ ﺫﻛﺮ ﺷﺪ ﺩﺭ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ ‪ Net Pro‬ﻭ‬
‫‪ Hwconfig‬ﻣﺤﺼﻮﻻﺕ ﻣﺘﻨﻮﻋﻲ ﺍﺯ ﺯﻳﻤﻨﺲ ﺭﺍ ﻣﻴﺒﻴﻨﻴﻢ ﻛﻪ ﻗﺎﺑﻠﻴﺖ ﺍﺗﺼﺎﻝ ﺑﻪ ﺷﺒﻜﻪ ‪ DP‬ﺭﺍ ﺩﺍﺭﻧﺪ‪ .‬ﻋﻼﻭﻩ ﺑﺮ ﺍﻳﻨﻬﺎ ﻣﻤﻜﻦ‬
‫ﺍﺳﺖ ﻻﺯﻡ ﺑﺎﺷﺪ ﻣﺤﺼﻮﻻﺕ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺩﻳﮕﺮ ﺭﺍ ﻧﻴﺰ ﺑﻪ ﺷﺒﻜﻪ ﺍﺿﺎﻓﻪ ﻛﻨﻴﻢ ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﺩﺭ ﺯﻳﺮ ﻣﻮﺭﺩ ﺑﺤﺚ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﻧﺪ‪:‬‬

‫ﺍﻟﻒ( ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎﻱ ﺯﻳﻤﻨﺲ‬

‫ﻧﺤﻮﻩ ﻗﺮﺍﺭﺩﺍﺩﻥ ﺍﻳﻦ ﺗﺠﻬﻴﺰﺍﺕ ﺭﻭﻱ ﺷﺒﻜﻪ ‪ DP‬ﺑﻪ ﻫﻤﺎﻥ ﺭﻭﺵ ﺫﻛﺮ ﺷﺪﻩ ﺑﺮﺍﻱ ‪ ET‬ﻫﺎ ﻣﻴﺒﺎﺷﺪ‪ .‬ﻳﻌﻨﻲ ﺍﺯ ﭘﻨﺠﺮﻩ‬
‫ﻛﺎﺗﺎﻟﻮﮒ ﺩﺭ ‪ Hwconfig‬ﺁﻧﻬﺎ ﺭﺍ ﺑﺮﺩﺍﺷﺘﻪ ﻭ ﺭﻭﻱ ﺧﻂ ﺷﺒﻜﻪ ‪ DP‬ﻗﺮﺍﺭ ﻣﻴﺪﻫﻴﻢ‪ .‬ﻧﻜﺘﻪ ﺍﻱ ﻛﻪ ﺑﺎﻳﺪ ﺑﻪ ﺁﻥ ﺗﻮﺟﻪ ﺩﺍﺷﺖ‬
‫ﺍﻳﻨﺴﺖ ﻛﻪ ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ﺗﺠﻬﻴﺰ ﻣﻤﻜﻦ ﺍﺳﺖ ﻻﺯﻡ ﺑﺎﺷﺪ ﻛﻪ ﻛﺎﺭﺕ ﺍﻳﻨﺘﺮﻓﻴﺲ ﻣﺮﺑﻮﻁ ﺑﻪ ﺁﻥ ﺭﺍ ﻧﻴﺰ ﺑﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻣﻌﺮﻓﻲ‬
‫ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫ﺑﺮﺍﻱ ﺭﻭﺷﻦ ﺷﺪﻥ ﻣﻮﺿﻮﻉ ﻣﺜﺎﻟﻲ ﺭﺍ ﻣﻄﺮﺡ ﻣﻲ ﻛﻨﻴﻢ ‪.‬‬
‫ﺧﻮﺍﻧﻨﺪﻩ ﻋﺰﻳﺰ ﺑﺎ ﺩﺭﻙ ﻣﻮﺿﻮﻉ ﻣﻴﺘﻮﺍﻧﺪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬
‫‪ DP Slave‬ﻫﺎﻱ ﺯﻳﻤﻨﺲ ﺭﺍ ﺷﺨﺼﺎ ﺩﺭ‬ ‫ﺳﺎﻳﺮ‬
‫‪ STEP7‬ﺗﺴﺖ ﻛﻨﺪ‪.‬‬
‫ﻓﺮﺽ ﻛﻨﻴﺪ ﺩﺭﺍﻳﻮ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺍﺯ ﻧﻮﻉ ‪ Simovert‬ﻛﻪ‬
‫ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﺩﻭﺭ ﻣﻮﺗﻮﺭﻫﺎﻱ ‪ AC‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﺭﺍ‬
‫ﻗﺮﺍﺭ ﺍﺳﺖ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﺘﺼﻞ ﻧﻤﺎﻳﻴﻢ ‪ .‬ﺩﺭ‬
‫‪ Hwconfig‬ﺍﺯ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺁﻧﺮﺍ ﺑﺎ ﻣﺎﻭﺱ‬
‫ﺑﺮﺩﺍﺷﺘﻪ ﻭ ﺭﻭﻱ ﺷﺒﻜﻪ ‪ DP‬ﻗﺮﺍﺭ ﻣﻴﺪﻫﻴﻢ‪ .‬ﻭﻟﻲ ﺍﻳﻦ ﻛﺎﺭ‬
‫ﺑﻪ ﺗﻨﻬﺎﻳﻲ ﻛﺎﻓﻲ ﻧﻴﺴﺖ‪.‬‬
‫ﺍﮔﺮ ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ‪ Consistency Check‬ﺭﺍ ﺍﺟﺮﺍ ﻛﻨﻴﻢ ﺑﺎ ﺧﻄﺎﻳﻲ ﺷﺒﻴﻪ ﺁﻧﭽﻪ ﺩﺭ ﺻﻔﺤﻪ ﻗﺒﻞ ﺫﻛﺮ ﺷﺪ ﻣﻮﺍﺟﻪ‬
‫ﻣﻴﺸﻮﻳﻢ‪.‬ﻻﺯﻡ ﺍﺳﺖ ﻛﺎﺭﺕ ﺍﻳﻨﺘﺮﻓﻴﺲ ﻣﺮﺑﻮﻃﻪ ﺭﺍ ﻧﻴﺰ ﺩﺭ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺍﺯ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ‪ Simovert‬ﺑﺮﺩﺍﺷﺘﻪ ﻭ ﺩﺭ‬
‫ﺍﺳﻼﺕ ﻣﺮﺑﻮﻃﻪ ﻗﺮﺍﺭ ﺩﻫﻴﻢ‪.‬‬
‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﺻﻔﺤﻪ ﺑﻌﺪ ﻣﺸﺎﻫﺪﻩ ﻣﻲ ﺷﻮﺩ ﻛﺎﺭﺕ ‪ Universal‬ﺩﺭ ﺍﺳﻼﺕ ﻣﺮﺑﻮﻃﻪ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﺳﺖ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻦ‬
‫ﻛﺎﺭﺕ ﻛﻪ ﺩﺭ ﺑﺮﺧﻲ ‪ DP Slave‬ﻫﺎﻱ ﺩﻳﮕﺮ ﻧﻴﺰ ﻣﺸﺎﻫﺪﻩ ﻣﻴﺸﻮﺩ ﻻﺯﻡ ﺍﺳﺖ ﺁﺩﺭﺱ ﻫﺎﻱ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﺭﺍ ﺗﻌﻴﻴﻦ‬
‫ﻛﻨﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎ‬ ‫‪٩٠‬‬

‫ﺑﺮﺍﻱ ﺗﻨﻈﻴﻢ ﺁﺩﺭﺱ ﻫﺎ ﻛﺎﻓﻴﺴﺖ ﺭﻭﻱ ﻛﺎﺭﺕ ‪ Universal‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ﺩﺭ ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺁﻧﻬﺎ ﺭﺍ ﺗﻌﻴﻴﻦ‬
‫ﻧﻤﺎﻳﻴﻢ‪ .‬ﺑﺮﺧﻲ ﺍﺯ ﻛﺎﺭﺗﻬﺎﻱ ﺍﻳﻨﺘﺮﻓﻴﺲ ﻗﺒﻼ ﺑﺎ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻱ ﻣﺸﺨﺼﻲ ﺗﻨﻈﻴﻢ ﺷﺪﻩ ﺍﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٩١‬‬ ‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺳﺎﻳﺮ ‪ DP Slave‬ﻫﺎ‬

‫ﺏ( ‪ DP Slave‬ﻫﺎﻱ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺩﻳﮕﺮ‬

‫ﺑﺮﺍﻱ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ‪ DP Slave‬ﻫﺎﻱ ﺳﺎﺯﻧﺪﮔﺎﻥ ﺩﻳﮕﺮ‬
‫ﻻﺯﻡ ﺍﺳﺖ ﻓﺎﻳﻞ ‪ GSD‬ﻭﺳﻴﻠﻪ ﻣﺮﺑﻮﻃﻪ ﺩﺭ ﺩﺳﺘﺮﺱ‬
‫ﺑﺎﺷﺪ‪.‬ﺍﻳﻦ ﻓﺎﻳﻞ ﺭﺍ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Hwconfig‬ﺗﻮﺳﻂ ﻣﻨﻮﻱ‬
‫‪ Option > Install New GSD‬ﺑﻪ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﺑﺎﺭ‬
‫ﻣﻴﻜﻨﻴﻢ‪ .‬ﭘﺲ ﺍﺯ ﺁﻥ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ ﻛﻪ ﺗﺠﻬﻴﺰ‬
‫ﻣﺮﺑﻮﻃﻪ ﺑﻪ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺍﺿﺎﻓﻪ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺳﻌﻲ ﺷﻮﺩ‬
‫‪STEP7‬‬ ‫ﺩﺭ ﻫﻨﮕﺎﻡ ﻧﺼﺐ ‪ GSD‬ﺳﺎﻳﺮ ﺯﻳﺮﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ‬
‫ﺑﺴﺘﻪ ﺑﺎﺷﺪ ﺗﺎ ﭘﻴﻐﺎﻡ ﺧﻄﺎ ﻇﺎﻫﺮ ﻧﮕﺮﺩﺩ‪.‬‬

‫ﺷﻜﻞ ﺯﻳﺮ ‪ DP Slave‬ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺭﺍ ﺍﺯ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻏﻴﺮ ﺯﻳﻤﻨﺲ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻛﻪ ﺭﻭﻱ ﺷﺒﻜﻪ ‪ DP‬ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫‪ S7-300‬ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﻧﺪ‪ .‬ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﻫﺮﻛﺪﺍﻡ ﺍﺯ ﺍﻳﻦ ﺗﺠﻬﻴﺰﺍﺕ ﻣﻲ ﺑﻴﻨﻴﻢ ﻛﻪ ﺍﺳﻼﺗﻬﺎﻱ ﺧﺎﻟﻲ ﺩﺭ ﭘﺎﻳﻴﻦ‬
‫ﺑﺮﻧﺎﻣﻪ ‪ Hwconfig‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﺍﺳﻼﺗﻬﺎ ﺑﺎﻳﺪ ﻛﺎﺭﺗﻬﺎﻱ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻣﻮﺭﺩ ﻧﻴﺎﺯ ﺭﺍﺍﺯ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ﺗﺠﻬﻴﺰ‬
‫ﻣﺰﺑﻮﺭ ﺩﺭ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﻗﺮﺍﺭ ﺩﺍﺩ‪.‬‬
Techno-Electro.com
Techno-Electro.com
Techno-Electro.com

STEP7 ‫ ﺩﺭ‬Intelligent Slaves ‫ﻓﺼﻞ ﭘﻨﺠﻢ – ﭘﻴﻜﺮﺑﻨﺪﻱ‬

: ‫ﻣﺸﺘﻤﻞ ﺑﺮ‬

I-Slave ‫ ﺑﺎ‬Master ‫ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬١-٥

DP Slave ‫ ﺑﺎ‬I-Slave ‫ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬٢-٥
‫ ﻫﺎﻱ ﻣﺨﺘﻠﻒ‬DP Master ‫ ﻣﺮﺑﻮﻁ ﺑﻪ‬DP Slave ‫ ﺑﺎ‬I-Slave ‫ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬٣-٥
DP Master ‫ ﺑﺎ‬I-Slave ‫ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬٤-٥
‫‪Techno-Electro.com‬‬

‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬ ‫‪٩٤‬‬

‫ﻣﻘﺪﻣﻪ ‪:‬‬
‫‪DP‬‬ ‫ﺩﺭ ﺑﺨﺶ ﻫﺎﻱ ﻗﺒﻠﻲ ﺗﻮﺿﻴﺤﺎﺗﻲ ﺩﺭ ﻣﻮﺭﺩ ﻣﻔﺎﻫﻴﻢ ‪ I-Slave‬ﻭﺍﻧﻮﺍﻉ ﺁﻥ ﺩﺍﺩﻳﻢ‪ .‬ﺑﻪ ﻃﻮﺭ ﺧﻼﺻﻪ ﮔﻔﺘﻴﻢ ‪ I-Slave‬ﻳﻚ‬
‫‪ Slave‬ﻫﻮﺷﻤﻨﺪ ﺍﺳﺖ ﺍﺯ ﺍﻳﻨﺮﻭ ﭘﺮﺩﺍﺯﺵ ﺍﻭﻟﻴﻪ ﺍﻱ ﺭﻭﻱ ‪ Distributed I/O‬ﻫﺎ ﺍﻧﺠﺎﻡ ﺩﺍﺩﻩ ﻭ ﺩﺭ ﺻﻮﺭﺕ ﻟﺰﻭﻡ ﻓﺮﻣﺎﻥ ﻫﺎﻱ‬
‫ﻣﺤﻠﻲ ﺭﺍ ﺑﻪ ﺧﺮﻭﺟﻲ ﻫﺎ ﺍﺭﺳﺎﻝ ﻣﻲ ﻛﻨﺪ‪.‬ﺗﺠﻬﻴﺰﺍﺕ ﺯﻳﺮ ﻣﻴﺘﻮﺍﻧﻨﺪ ﺑﻌﻨﻮﺍﻥ ‪ I-Slave‬ﻋﻤﻞ ﻛﻨﻨﺪ ‪:‬‬
‫‪ ET200S‬ﺩﺍﺭﺍﻱ ‪CPU‬‬ ‫•‬

‫‪ T200X‬ﺩﺍﺭﺍﻱ ‪CPU‬‬ ‫•‬

‫‪ CPU‬ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ S7-300‬ﻛﻪ ﻗﺎﺑﻠﻴﺖ ‪ Slave‬ﺭﺍ ﻧﻴﺰ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫‪ CPU‬ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ S7-400‬ﻛﻪ ﻗﺎﺑﻠﻴﺖ ‪ Slave‬ﺭﺍ ﻧﻴﺰ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﻛﺎﺭﺕ ‪ CP‬ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ S7-300‬ﻛﻪ ﻗﺎﺑﻠﻴﺖ ‪ Slave‬ﺭﺍ ﻧﻴﺰ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬
‫ﻛﺎﺭﺕ ‪ CP‬ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ S7-400‬ﻛﻪ ﻗﺎﺑﻠﻴﺖ ‪ Slave‬ﺭﺍ ﻧﻴﺰ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫‪ ١-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺍﺯ ﻳﻚ ‪ DP Master‬ﻫﻤﺮﺍﻩ ﺑﺎ ﻳﻚ ﻳﺎ ﭼﻨﺪ ‪ I-Slave‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺩﺭ ﻋﻴﻦ ﺣﺎﻝ ﻣﻴﺘﻮﺍﻥ ﻫﻤﺮﺍﻩ ﺑﺎ ﺁﻧﻬﺎ‬
‫‪ DP Slave‬ﻧﻴﺰ ﺭﻭﻱ ﺷﺒﻜﻪ ﻗﺮﺍﺭ ﺩﺍﺩ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪:‬‬

‫ﺑﺮﻧﺎﻣﻪ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺑﻪ ﺗﻌﺪﺍﺩﻱ ‪ Subtask‬ﺗﻘﺴﻴﻢ ﺷﺪﻩ ﻭ ﻫﺮ ﻗﺴﻤﺖ ﺩﺭ ﻳﻜﻲ ﺍﺯ ‪ I-slave‬ﻫﺎ ﻗﺮﺍﺭ ﺩﺍﺭﺩ‪.‬‬ ‫•‬

‫‪ DP Master‬ﻓﻘﻂ ﻛﻨﺘﺮﻝ ﻭ ﻧﻈﺎﺭﺕ ﻛﻠﻲ ﺑﺮ ‪ I-slave‬ﻫﺎ ﺩﺍﺭﺩ ‪ .‬ﭘﺮﺩﺍﺯﺵ ﻣﺤﻠﻲ ﺑﻌﻬﺪﻩ ‪ I-Slave‬ﻫﺎﺳﺖ‪.‬‬ ‫•‬

‫‪ DP master‬ﺑﻪ ‪ I/O‬ﻫﺎﻱ ‪ I-Slave‬ﻫﺎ ﻣﺴﺘﻘﻴﻤﹰﺎ ﺩﺳﺘﺮﺳﻲ ﻧﺪﺍﺭﺩ‪ .‬ﻭ ﻓﻘﻂ ﺑﻪ ‪ CPU‬ﻫﺎﻱ ‪ I-Slave‬ﻫﺎ ﻭ‬ ‫•‬

‫ﺁﻧﻬﻢ ﺻﺮﻓﹰﺎ ﺁﺩﺭﺱ ﻫﺎﻳﻲ ﻛﻪ ﺍﺯ ﻗﺒﻞ ﺩﺭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺗﻌﺮﻳﻒ ﺷﺪﻩ )ﺻﺮﻓﺎ ﺟﺪﺍﻭﻝ ‪ PII‬ﻭ ‪ (PIQ‬ﺩﺳﺘﺮﺳﻲ ﺩﺍﺭﺩ ‪.‬‬
‫‪ I-Slave‬ﻫﺎ ﺭﺍ ﻧﻤﻲ ﺗﻮﺍﻥ ﻫﻤﺎﻧﻨﺪ ‪ DP Slave‬ﻫﺎ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﺘﺼﻞ ﻧﻤﻮﺩ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻨﻜﺎﺭ ﺭﻭﺵ‬ ‫•‬
‫ﺧﺎﺻﻲ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪ .‬ﮔﺎﻡ ﻫﺎﻳﻲ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺑﺎﻳﺪ ﺑﺮﺩﺍﺷﺘﻪ ﺷﻮﺩ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٩٥‬‬ ‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫ﮔﺎﻣﻬﺎﻳﻲ ﻛﻪ ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﻴﺴﺘﻢ ‪ Master<>I-Slave‬ﺑﺎﻳﺪ ﺑﺮﺩﺍﺷﺖ‪:‬‬
‫‪ DP Master‬ﻭ ﻓﻌﺎﻝ ﻛﺮﺩﻥ ﺁﻥ ﺩﺭ ‪Hwconfig‬‬ ‫ﮔﺎﻡ ﺍﻭﻝ ‪ :‬ﺍﻳﺠﺎﺩ‬

‫‪Station 300‬‬ ‫ﮔﺎﻡ ﺩﻭﻡ ‪ :‬ﺍﺟﺮﺍﻱ ‪ NetPro‬ﻭ ﻭﺍﺭﺩ ﻛﺮﺩﻥ‬

‫ﮔﺎﻡ ﺳﻮﻡ ‪ :‬ﺭﻭﻱ ‪ Station 300‬ﺩﺭ ﻣﺤﻴﻂ ‪ Netpro‬ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﺗﺎ ﺗﻮﺳﻂ ‪ Hwconfig‬ﺑﺎﺯ ﺷﻮﺩ‪.‬‬
‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ‪ :‬ﺑﺎ ﺑﺎﺯﺷﺪﻥ ﺑﺮﻧﺎﻣﻪ ‪ Hwconfig‬ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ‪ I-Slave‬ﻳﻜﻲ ﺍﺯ ﻛﺎﺭﻫﺎﻱ ﺯﻳﺮ ﺭﺍ ﺍﻧﺠﺎﻡ ﻣﻴﺪﻫﻴﻢ‪:‬‬
‫ﺍﻟﻒ( ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ CPU 300‬ﺑﺎ ﻗﺎﺑﻠﻴﺖ ‪ Slave‬ﻣﺎﻧﻨﺪ ‪ CPU315-2DP‬ﺑﺎ ﻛﺪ ﺳﻔﺎﺭﺵ‪ 315-2AF82-0AB0‬ﻻﺯﻡ‬
‫ﺑﻪ ﺫﻛﺮ ﺍﺳﺖ ﻗﺎﺑﻠﻴﺖ ‪ Slave‬ﺷﺪﻥ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺩﺭ ﺗﻮﺿﻴﺤﺎﺕ ﭘﺎﻳﻴﻦ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﭼﻚ ﻛﺮﺩ‪ .‬ﭘﺲ ﺍﺯ ﻭﺍﺭﺩ ﻛﺮﺩﻥ‬
‫ﺭﻙ ﻭ ‪ CPU‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﻭﻱ ﺍﺳﻼﺕ ‪ DP‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ﺩﺭ ﭘﻨﺠﺮﻩ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻣﺪ ‪ Slave‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬ ‫‪٩٦‬‬

‫‪ Slave‬ﺷﺪﻥ ﻣﺎﻧﻨﺪ ﻛﺎﺭﺕ ‪CP342-5‬‬ ‫ﺏ( ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻛﺎﺭﺕ ‪ CP‬ﺑﺎ ﻗﺎﺑﻠﻴﺖ ‪ DP‬ﻭ ﺍﻣﻜﺎﻥ ‪ Master‬ﻳﺎ‬

‫ﺝ( ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ ET200X‬ﻳﺎ ‪ ET200S‬ﺩﺭﺍﻳﻨﺤﺎﻟﺖ ﺩﺭ‬

‫ﭘﻨﺠﺮﻩ ﺧﺎﻟﻲ ‪ Hwconfig‬ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﺭﻙ ﻭﺍﺭﺩ ﻛﻨﻴﻢ ﺍﺯ‬
‫‪ET‬‬ ‫ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺭﻭﺑﺮﻭ ﺭﻭﻱ ﻳﻜﻲ ﺍﺯ‬
‫ﻫﺎﻱ ﻓﻮﻕ ﻛﻪ ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﻧﺎﻡ ﺁﻥ ﻛﻠﻤﻪ ‪ CPU‬ﻧﻮﺷﺘﻪ ﺷﺪﻩ‬
‫ﺩﻭﺑﺎﺭﻛﻠﻴﻚ ﻣﻴﻜﻨﻴﻢ ﺗﺎ ﻭﺍﺭﺩ ‪ Hwconfig‬ﺷﻮﺩ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻧﻴﺰ ﺭﻭﻱ ‪ DP‬ﺩﺭ ﺍﺳﻼﺕ ﻣﺮﺑﻮﻃﻪ ﺩﺍﺑﻞ‬

‫ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﻭ ﺳﭙﺲ ﻣﺪ ‪ DP Slave‬ﺭﺍ ﺑﺮﺍﻱ ﺁﻥ‬
‫ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫ﺩﺭ ﺗﻤﺎﻡ ﺣﺎﻻﺕ ﺍﻟﻒ ﻭ ﺏ ﻭ ﺝ ﻻﺯﻡ ﺍﺳﺖ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺭﺍ ﺫﺧﻴﺮﻩ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٩٧‬‬ ‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫ﮔﺎﻡ ﭘﻨﺠﻢ ‪ :‬ﺑﺎﺯ ﻛﺮﺩﻥ ‪ DP Master‬ﺩﺭ ‪ HWconfig‬ﺑﺎ ﺩﻭ ﺑﺎﺭ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﺁﻥ ﺩﺭ ‪. Netpro‬‬
‫ﮔﺎﻡ ﺷﺸﻢ ‪ :‬ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻛﺎﺗﺎﻟﻮﮒ ‪ DP‬ﻗﺴﻤﺖ‬
‫‪ Configured Station‬ﺭﺍ ﺑﺎﺯ ﻛﺮﺩﻩ ﻭ ﺑﺴﺘﻪ ﺍﻳﻨﻜﻪ‬
‫ﻛﺪﺍﻡ ‪ I-Slave‬ﻣﺪ ﻧﻈﺮ ﺍﺳﺖ ﺗﺠﻬﻴﺰ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ‬
‫‪DP‬‬ ‫ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﺭﻭﻱ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ‬
‫‪X-BM‬‬ ‫‪ Master‬ﻗﺮﺍﺭ ﻣﻴﺪﻫﻴﻢ‪ .‬ﺑﺮﺍﻱ ‪ ET200X‬ﺍﺯ‬
‫‪ 147/CPU‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪ .‬ﻣﺸﺎﻫﺪﻩ ﻣﻴﻜﻨﻴﻢ ﻛﻪ‬
‫ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺑﺎﺯ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﮔﺎﻡ ﻫﻔﺘﻢ ‪ :‬ﺩﺭ ﭘﻨﺠﺮﻩ ﻓﻮﻕ ﺭﻭﻱ ‪ Connect‬ﻛﻠﻴﻚ ﻣﻴﻜﻨﻴﻢ ﺑﺎ ﺑﺮﻗﺮﺍﺭﻱ ﺍﺗﺼﺎﻝ ﺗﺠﻬﻴﺰ ﺳﻄﺮ ﻣﺮﺑﻮﻃﻪ ﺍﺯ ﭘﻨﺠﺮﻩ ﺣﺬﻑ‬
‫ﻣﻴﺸﻮﺩ‪ .‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺍﮔﺮ ﭼﻨﺪﻳﻦ ‪ Station 300‬ﺑﺼﻮﺭﺕ ‪ Slave‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺪﻩ ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻦ ﻟﻴﺴﺖ ﭼﻨﺪ ﺍﻧﺘﺨﺎﺏ‬
‫ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬ ‫‪٩٨‬‬

‫ﮔﺎﻡ ﻫﺸﺘﻢ ‪ :‬ﺩﺭ ﭘﻨﺠﺮﻩ ﻗﺒﻞ ﺭﻭﻱ ‪ Configuration‬ﺳﭙﺲ ﺭﻭﻱ ‪ New‬ﻛﻠﻴﻚ ﻣﻴﻜﻨﻴﻢ‬

‫‪Slave‬‬ ‫ﮔﺎﻡ ﻧﻬﻢ ‪ :‬ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺑﺎﺯ ﻣﻴﺸﻮﺩ ﻛﻪ ﺳﻤﺖ ﭼﭗ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Master‬ﻭ ﺳﻤﺖ ﺭﺍﺳﺖ ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫ﺍﺳﺖ‪ .‬ﻧﻮﺍﺣﻲ ﺁﺩﺭﺱ ﻫﺎ ﺭﺍ ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺎﻳﺪ ﻣﺸﺨﺺ ﻧﻤﻮﺩ‪ .‬ﺍﮔﺮ ﺩﺭ ﻳﻜﻄﺮﻑ ‪ Input‬ﺍﻧﺘﺨﺎﺏ ﺷﻮﺩ ﺩﺭ ﺳﻤﺖ ﺩﻳﮕﺮ ﺑﺎﻳﺪ‬
‫‪ Output‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﻮﺩ‪ .‬ﺩﺭ ‪ Address‬ﻧﻘﻄﻪ ﺷﺮﻭﻉ ﺭﺍ ﻣﻴﻨﻮﻳﺴﻴﻢ‪ .‬ﻃﻮﻝ ﺩﻳﺘﺎ ﺭﺍ ﺩﺭ ﻗﺴﻤﺖ ‪ Length‬ﻣﺸﺨﺺ ﻣﻴﻜﻨﻴﻢ‬
‫ﻛﻪ ﭼﻨﺪ ﺑﺎﻳﺖ ﻳﺎ ﭼﻨﺪ ‪ Word‬ﺑﺎﺷﺪ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮ ﺁﺩﺭﺱ ﻭﺭﻭﺩﻱ ‪ 0‬ﻭ ﻃﻮﻝ ﺩﻳﺘﺎ ‪ 2‬ﺑﺎﻳﺖ ﺑﺎﺷﺪ ﻳﻌﻨﻲ ‪ IB0‬ﻭ ‪.IB1‬‬
‫ﺩﺭ ﺿﻤﻦ ﻻﺯﻡ ﻧﻴﺴﺖ ﻛﻪ ﺁﺩﺭﺳﻬﺎﻱ ﺩﻭﻃﺮﻑ ﻫﺮﺩﻭ ﺍﺯ ﻳﻚ ﻋﺪﺩ ﺷﺮﻭﻉ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٩٩‬‬ ‫‪ Master‬ﺑﺎ ‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫ﺩﺭ ﭘﻨﺠﺮﻩ ﻗﺒﻠﻲ ﭘﺲ ﺍﺯ ﺗﻜﻤﻴﻞ ﻛﺎﺭ ﻭ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ‪ OK‬ﻣﺸﺎﻫﺪﻩ ﻣﻴﻜﻨﻴﻢ ﻛﻪ ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Configuration‬ﻳﻚ‬
‫ﺳﻄﺮ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﻣﻴﮕﺮﺩﺩ‪ .‬ﻣﻨﻈﻮﺭ ﺍﺯ ﻣﺪ ‪ MS‬ﺩﺭ ﺍﻳﻦ ﺳﻄﺮ ﻫﻤﺎﻥ ﻣﻔﻬﻮﻡ ‪ Maser/Slave‬ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻦ ﺳﻄﺮ‬
‫ﻣﺸﺨﺺ ﺍﺳﺖ ﻛﻪ ﻧﺎﺣﻴﻪ ‪ PIQ‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺣﺎﻓﻈﻪ ‪ Master‬ﺍﺯ ﺁﺩﺭﺱ ‪ 0‬ﺑﺎ ﻧﺎﺣﻴﻪ ‪ PII‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺣﺎﻓﻈﻪ ‪ Slave‬ﺍﺯ‬
‫ﺩﺭ ﺗﻤﺎﺱ ﺍﺳﺖ ﻭ ﺩﻳﺘﺎﻫﺎﻳﻲ ﺑﺎ ﺣﺠﻢ ‪ ۲‬ﺑﺎﻳﺖ ﻭ ﺑﺎ ﺁﺩﺭﺱ ﻫﺎﻱ ﺷﺮﻭﻉ ﻓﻮﻕ ﺍﻟﺬﻛﺮ ﺑﻴﻦ ﺁﻧﻬﺎ ﺗﺒﺎﺩﻝ ﻣﻴﺸﻮﺩ‪.‬‬ ‫ﺁﺩﺭﺱ ‪۲‬‬
‫ﺑﻬﻤﻴﻦ ﺭﻭﺵ ﻣﻴﺘﻮﺍﻥ ﺳﻄﺮ ﺩﻳﮕﺮﻱ ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺑﻴﻦ ﻧﺎﺣﻴﻪ ﻭﺭﻭﺩﻱ ‪ Master‬ﻭ ﻧﺎﺣﻴﻪ ﺧﺮﻭﺟﻲ ‪ Slave‬ﺑﻪ ﺍﻳﻦ‬
‫ﺟﺪﻭﻝ ﺍﺿﺎﻓﻪ ﻛﺮﺩ ‪.‬‬

‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻳﻦ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺑﻪ ﺳﻬﻮﻟﺖ ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ‪ .‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Master‬ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﺁﺩﺭﺱ ﻫﺎﻱ‬
‫ﺗﻌﺮﻳﻒ ﺷﺪﻩ ﻓﻮﻕ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ‪ .‬ﻣﺎﻧﻨﺪ‪:‬‬
‫‪L QB0‬‬ ‫‪ T QB0‬ﻳﺎ‬

‫ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﻣﻴﺘﻮﺍﻧﺪ ﺷﺒﻴﻪ ﺁﻧﭽﻪ ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﺑﺮﺍﻱ ﻋﻤﻠﻜﺮﺩ ‪ CPU‬ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ ‪ S7-300‬ﺑﻌﻨﻮﺍﻥ ‪ Slave‬ﺫﻛﺮ ﺷﺪ‬
‫ﺭﺍ ﺑﺮﺍﻱ ﺳﺎﻳﺮ ‪ I-Slave‬ﻫﺎ ﺍﻧﺠﺎﻡ ﺩﺍﺩﻩ ﻭ ﻧﺘﻴﺠﻪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻧﻤﺎﻳﺪ‪.‬‬
‫ﺗﺬﻛﺮ ‪:‬‬
‫‪Master‬‬ ‫ﻭﻗﺘﻲ ﻳﻚ ‪ I-Slave‬ﺭﺍ ﺑﺎ ﻳﻚ ‪ Master‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻣﻴﻜﻨﻴﻢ ﻧﻤﻴﺘﻮﺍﻥ ﺍﺯ ﺁﻥ ‪ I-Slave‬ﺑﺮﺍﻱ‬ ‫•‬

‫ﺩﻳﮕﺮﻱ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻣﮕﺮ ﺍﻳﻨﻜﻪ ﺁﻧﺮﺍ ﺍﺯ ‪ Master‬ﺍﻭﻝ ‪ Disconnect‬ﻛﻨﻴﻢ‪.‬‬

‫ﺭﻭﻱ ﻳﻚ ﺷﺒﻜﻪ ‪PROFIBUS‬ﻣﻴﺘﻮﺍﻥ ﭼﻨﺪ ‪ Master‬ﻭ ﭼﻨﺪ ‪ I-slave‬ﺭﺍ ﺑﮕﻮﻧﻪ ﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻛﺮﺩ‬ ‫•‬
‫‪DP Slave‬‬ ‫ﻛﻪ ﻫﺮ ‪ I-Slave‬ﺑﺎ ‪ Master‬ﺧﺎﺹ ﺧﻮﺩﺵ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ﺑﺎﺷﺪ‪ .‬ﺍﻳﻦ ﻛﺎﺭ ﺷﺒﻴﻪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬
‫ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺑﺎ ‪ Master‬ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻣﻴﺒﺎﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺑﺎ ‪DP Slave‬‬ ‫‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬ ‫‪١٠٠‬‬

‫‪DP Slave‬‬ ‫‪ ٢-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ I-Slave‬ﺑﺎ‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪ I-Slave‬ﺑﺎ ‪ DP Slave‬ﺍﺭﺗﺒﺎﻁ ﻣﺴﺘﻘﻴﻢ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ ﻛﻪ ﺑﻪ ‪ Direct Data Exchange‬ﻣﻌﺮﻭﻑ‬
‫ﺍﺳﺖ ﻭ ﺑﺎ ﺍﺭﺗﺒﺎﻁ ‪ DX‬ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬
‫ﺍﺭﺗﺒﺎﻁ ‪ DX‬ﻗﺎﺑﻠﻴﺘﻲ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﻧﺴﺨﻪ ‪ DP-V2‬ﺑﻪ ‪ PROFIBUS‬ﺍﺿﺎﻓﻪ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻻﺯﻡ ﻧﻴﺴﺖ ﻛﻪ‬
‫ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺑﻴﻦ ﺩﻭ ‪ Slave‬ﭘﺎﻱ ‪ Master‬ﻧﻴﺰ ﺩﺭ ﻣﻴﺎﻥ ﺑﺎﺷﺪ‪.‬ﺑﻨﺎﺑﺮ ﺍﻳﻦ ﺳﺮﻋﺖ ﺗﺒﺎﺩﻝ ﺑﻴﺸﺘﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬

‫ﮔﺎﻣﻬﺎﻳﻲ ﻛﻪ ﺑﺮﺍﻱ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﻴﺴﺘﻢ ‪ DP Slave<>I-Slave‬ﺑﺎﻳﺪ ﺑﺮﺩﺍﺷﺖ‪:‬‬

‫ﮔﺎﻡ ﺍﻭﻝ ‪ :‬ﺍﻳﺠﺎﺩ ‪ DP Master‬ﻭ ﻓﻌﺎﻝ ﻛﺮﺩﻥ ﺁﻥ ﺩﺭ ‪ Hwconfig‬ﻣﺸﺎﺑﻪ ﺁﻧﭽﻪ ﺑﺮﺍﻱ ‪ Master<>Islave‬ﺑﻴﺎﻥ ﺷﺪ‪.‬‬
‫ﺗﻨﻬﺎ ﻧﻜﺘﻪ ﻣﻬﻤﻲ ﻛﻪ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﺍﻳﻨﺴﺖ ﻛﻪ ‪ Master‬ﻗﺎﺑﻠﻴﺖ ‪ DX‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺍﻳﻦ ﻗﺎﺑﻠﻴﺖ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺩﺭ‬
‫ﻭﻳﮋﮔﻴﻬﺎﻳﻲ ﻛﻪ ﺩﺭ ﺯﻳﺮ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﭼﻚ ﻛﺮﺩ‪.‬‬
‫‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﻳﻚ‬ ‫‪Hwconfig‬‬ ‫ﮔﺎﻡ ﺩﻭﻡ ‪ :‬ﺍﻧﺘﺨﺎﺏ ‪ DP Slave‬ﻭﻗﺮﺍﺭ ﺩﺍﺩﻥ ﺁﻥ ﺭﻭﻱ ﺷﺒﻜﻪ ‪ DP Master‬ﺩﺭ‬
‫‪ ET200M‬ﺭﺍ ﺩﺭ ﻧﻈﺮ ﺑﮕﻴﺮﻳﺪ ﻛﻪ ﺭﻭﻱ ﺷﺒﻜﻪ ﻗﺮﺍﺭ ﺩﺍﺩﻩ ﺷﺪﻩ ﻭ ﻛﺎﺭﺗﻬﺎﻱ ﻣﺮﺑﻮﻃﻪ ﻧﻴﺰ ﺩﺭ ﺍﺳﻼﺗﻬﺎﻱ ﺁﻥ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﻧﺪ‪.‬‬
‫ﮔﺎﻡ ﺳﻮﻡ ‪ :‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻳﻚ ‪ I-Slave‬ﺑﻪ ﺭﻭﺵ ﺫﻛﺮ ﺷﺪﻩ ﺩﺭ ﻗﺴﻤﺖ ﻗﺒﻞ ﻭ ﻗﺮﺍﺭ ﺩﺍﺩﻥ ﺁﻥ ﺭﻭﻱ ﺷﺒﻜﻪ‬

‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ ‪ :‬ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ‪ I-Slave‬ﺗﺎ ﭘﻨﺠﺮﻩ ‪ Configuration‬ﺷﺒﻴﻪ ﮔﺎﻡ ﻫﺸﺘﻢ ﺫﻛﺮ ﺷﺪﻩ ﻗﺒﻠﻲ ﺑﺎﺯﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٠١‬‬ ‫ﺑﺎ ‪DP Slave‬‬ ‫‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬

‫ﮔﺎﻡ ﭘﻨﺠﻢ ‪ :‬ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Configurataion‬ﺭﻭﻱ ‪ New‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﺗﺎ ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺑﺎﺯ ﺷﻮﺩ ﺩﺭ ﺍﻳﻦ‬
‫ﭘﻨﺠﺮﻩ ‪:‬‬
‫ﺍﺑﺘﺪﺍ ﺑﺎﻳﺪ ﻣﺪ ‪ DX‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩ‪.‬‬ ‫•‬

‫ﺍﮔﺮ ﺑﻴﺶ ﺍﺯ ﻳﻚ ‪ DP Slave‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﺩﺭ ﻗﺴﻤﺖ ﺳﻤﺖ ﭼﭗ ﺁﺩﺭﺱ ‪ Node‬ﺑﺮﺍﻱ ‪ Slave‬ﻣﻮﺭﺩ ﻧﻈﺮ‬ ‫•‬
‫ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﻴﻢ )ﺩﺭ ﺟﻠﻮﻱ ‪(DP Address‬‬
‫ﺁﺩﺭﺳﻬﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ DP Slave‬ﻛﻪ ﺑﺎﻳﺪ ﺩﺭ ﺩﺳﺘﺮﺱ ‪ I-Slave‬ﻗﺮﺍﺭ ﮔﻴﺮﻧﺪ ﺭﺍ ﻗﺴﻤﺖ ﺳﻤﺖ ﭼﭗ ﺩﺭ‬ ‫•‬

‫ﻻ ﺑﺮ ﺍﺳﺎﺱ ﺁﻧﭽﻪ ﺑﺮﺍﻱ ‪ DP Slave‬ﺩﺭ‬

‫ﺟﻠﻮﻱ ‪ Address‬ﻣﺸﺨﺺ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺍﻳﻦ ﺁﺩﺭﺱ ﻫﺎ ﻣﻌﻤﻮ ﹲ‬
‫‪ HWcofig‬ﺗﻨﻈﻴﻢ ﺷﺪﻩ ﻇﺎﻫﺮ ﻣﻴﮕﺮﺩﺩ‪.‬‬
‫ﺩﺭ ﻗﺴﻤﺖ ﺳﻤﺖ ﺭﺍﺳﺖ ﻧﻴﺰ ﺁﺩﺭﺱ ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ I-Slave‬ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﻴﻢ‪.‬‬ ‫•‬

‫ﺍﻧﺪﺍﺯﻩ ﺩﻳﺘﺎ ﺭﺍ ﺷﺒﻴﻪ ﻗﺒﻞ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ Length‬ﻭ ‪ Unit‬ﻣﺸﺨﺺ ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫ﺑﺎ ‪ Slave‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ DP Master‬ﻫﺎﻱ ﻣﺨﺘﻠﻒ‬ ‫‪I-Slave‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬ ‫‪١٠٢‬‬

‫ﮔﺎﻡ ﺷﺸﻢ ‪ :‬ﭘﺲ ﺍﺯ ‪ Apply‬ﻛﺮﺩﻥ ﻣﻴﺒﻴﻨﻴﻢ ﻛﻪ ﺍﺭﺗﺒﺎﻁ ‪ DX‬ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Configuration‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ I-slave‬ﻣﺎﻧﻨﺪ‬
‫ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺩﺭ ﺻﻮﺭﺕ ﺍﻳﺠﺎﺩ ﭼﻨﺪ ﺍﺭﺗﺒﺎﻁ ‪ DX‬ﻳﺎ ‪ MS‬ﺁﺩﺭﺳﻬﺎ ﻧﺒﺎﻳﺪ ﺗﺪﺍﺧﻞ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ‪ .‬ﺍﻳﻦ ﻛﺎﺭ‬
‫ﺗﻮﺳﻂ ﺧﻮﺩ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻧﻴﺰ ﻛﻨﺘﺮﻝ ﻣﻴﺸﻮﺩ‪.‬‬

‫‪ ٣-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ I-Slave‬ﺑﺎ ‪ DP Slave‬ﻛﻪ ﺩﺍﺭﺍﻱ ‪ DP Master‬ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻫﺴﺘﻨﺪ‬

‫‪DP‬‬ ‫ﺩﺭ ﺣﺎﻟﺖ ﻗﺒﻞ ‪ I-Slave‬ﻭ ‪ DP Slave‬ﻛﻪ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﺍﺭﺗﺒﺎﻁ ‪ DX‬ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﺮﺩﻧﺪ ﻫﺮ ﺩﻭ ﺩﺍﺭﺍﻱ ﻳﻚ‬
‫‪ Master‬ﺑﻮﺩﻧﺪ‪ .‬ﺍﻛﻨﻮﻥ ﺣﺎﻟﺘﻲ ﺭﺍ ﺩﺭ ﻧﻈﺮ ﺑﮕﻴﺮﻳﺪ ﻛﻪ ﻫﺮ ﻛﺪﺍﻡ ﻣﺘﻌﻠﻖ ﺑﻪ ﻳﻚ ‪ DP Master‬ﺟﺪﺍﮔﺎﻧﻪ ﺑﺎﺷﻨﺪ ﻭﻟﻲ‬
‫ﻣﺠﻤﻮﻋﻪ ﺁﻧﻬﺎ ﺭﻭﻱ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺑﺎﺷﺪ‪ .‬ﺍﻳﻦ ﺳﺎﺧﺘﺎﺭ ﻧﻴﺰ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺭﺍ ﺳﺮﻋﺖ‬
‫‪DP Master2‬‬ ‫ﻣﻴﺒﺨﺸﺪ ‪ .‬ﺯﻳﺮﺍ ﺍﮔﺮ ﭼﻨﻴﻦ ﺍﻣﻜﺎﻧﻲ ﻭﺟﻮﺩ ﻧﺪﺍﺷﺖ ﻻﺯﻡ ﺑﻮﺩ ﺩﺭ ﻣﺜﺎﻝ ﺷﻜﻞ ﺯﻳﺮ ﺍﺑﺘﺪﺍ ‪ I-Slave23‬ﺑﺎ‬
‫ﮔﻔﺘﮕﻮ ﻛﻨﺪ ﺳﭙﺲ ‪ DP Master2‬ﺑﺎ ‪ DP Master1‬ﻭ ﻧﻬﺎﻳﺘﺎ ﺩﻳﺘﺎ ﺍﺯ ‪ DP Master1‬ﺑﻪ ‪ DP Slave23‬ﺩﺍﺩﻩ ﺷﻮﺩ‪.‬‬
‫ﺍﻳﻨﺮﺍﻩ ﻃﻮﻻﻧﻲ ﺑﺎ ﺍﻣﻜﺎﻥ ‪ DX‬ﻓﻮﻕ ﺑﺴﻴﺎﺭ ﻛﻮﺗﺎﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪DP-Master‬‬ ‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﺑﺮﺍﻱ ﺭﻭﺷﻬﺎﻱ ﻗﺒﻠﻲ ﺩﺍﺩﻩ ﺷﺪ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﻳﻦ ﺭﻭﺵ ﻧﻴﺰ ﺳﺎﺩﻩ ﺍﺳﺖ‪ .‬ﻛﺎﻓﻲ ﺍﺳﺖ ﺩﻭ‬
‫ﺟﺪﺍﮔﺎﻧﻪ ﻛﻪ ﻫﺮ ﺩﻭ ﺍﻣﻜﺎﻥ ‪ DX‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﺭﻭﻱ ﻳﻚ ﺑﺎﺱ ﻣﺸﺘﺮﻙ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻩ ﺭﻭﻱ ﻳﻜﻲ ‪ I-slave‬ﻭ ﺭﻭﻱ‬
‫ﺩﻳﮕﺮﻱ ‪ DP Slave‬ﻗﺮﺍﺭ ﺩﻫﻴﻢ‪ .‬ﺳﭙﺲ ﺭﻭﻱ ‪ I- Slave‬ﻭ ﺁﺩﺭﺱ ‪ Node‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ DP Slave‬ﺭﺍ ﺩﺭ ﭘﻨﺠﺮﻩ‬
‫‪ Configuration‬ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ ‪ .‬ﺑﻘﻴﻪ ﻛﺎﺭﻫﺎ ﺷﺒﻴﻪ ﻗﺒﻞ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٠٣‬‬ ‫‪DP Master‬‬ ‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ I-Slave‬ﺑﺎ‬

‫‪DP Master‬‬ ‫‪ ٤-٥‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ I-Slave‬ﺑﺎ‬

‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻳﻚ ‪ I-Slave‬ﺑﺎ ‪ DP Master‬ﻏﻴﺮ ﺍﺯ ‪ DP Master‬ﺧﻮﺩﺵ ﺍﺭﺗﺒﺎﻁ ﻣﺴﺘﻘﻴﻢ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ‪.‬‬

‫‪ DP Master‬ﺑﺎﻳﺪ ﺍﻣﻜﺎﻥ ‪ DX‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪ .‬ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺑﺠﺎﻱ ﺍﻳﻨﻜﻪ ﺭﻭﻱ ‪ I-Slave‬ﺩﺭ ﭘﻨﺠﺮﻩ ‪ HWconfig‬ﻛﻠﻴﻚ‬
‫ﻛﻨﻴﻢ ﺭﻭﻱ ﺍﺳﻼﺕ ‪ DP‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ DP Master‬ﻛﻠﻴﻚ ﻣﻴﻜﻨﻴﻢ ﺗﺎ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﭘﻨﺠﺮﻩ ‪ Configuration‬ﺑﺎﺯ ﺷﻮﺩ‪.‬‬

‫ﺷﺒﻴﻪ ﻗﺒﻞ ﺑﺎ ﻛﻠﻴﻚ ﺭﻭﻱ ‪ New‬ﭘﻨﺠﺮﻩ ‪ Cofiguration‬ﺑﺎﺯ ﻣﻴﺸﻮﺩ ﻛﻪ ﺩﺭ ﺁﻥ ﺁﺩﺭﺱ ‪ Node‬ﻭ ﺁﺩﺭﺱ ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫ﺣﺎﻓﻈﻪ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ‬
‫ﺗﻮﺟﻪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﺪ ﺍﺯ ﺳﻤﺖ ‪ DP Master1‬ﻣﻴﺘﻮﺍﻧﻴﻢ ﺁﺩﺭﺱ ‪ Node‬ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Slave‬ﻫﺎﻱ ‪ DP Master2‬ﺭﺍ‬
‫ﺑﺒﻴﻨﻴﻢ ﻛﻪ ‪ I-Slave‬ﻳﻜﻲ ﺍﺯ ﺁﻧﻬﺎﺳﺖ‪ .‬ﻫﻤﻴﻨﻄﻮﺭ ﺍﺯ ﺳﻤﺖ ‪ DP Master 2‬ﻣﻴﺘﻮﺍﻧﻴﻢ ﺁﺩﺭﺱ ‪ Node‬ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫‪DP‬‬ ‫‪ Slave‬ﻫﺎﻱ ‪ DP Master1‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻛﻨﻴﻢ ﻭ ﺑﻴﻦ ﺁﻧﻬﺎ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻛﻨﻴﻢ‪ .‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﻪ ﺍﻳﻦ ﻃﺮﻳﻖ ﻳﻚ‬
‫‪ Master‬ﻧﻪ ﺗﻨﻬﺎ ﺑﺎ ‪ I-Slave‬ﻛﻪ ﺑﺎ ‪ DP-Slave‬ﻫﺎﻱ ‪ Master‬ﻫﺎﻱ ﺩﻳﮕﺮ ﻧﻴﺰ ﻣﻴﺘﻮﺍﻧﺪ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﺷﺸﻢ – ﺳﺎﺧﺘﺎﺭﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ‪STEP7‬‬

‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ‬ ‫‪١-٦‬‬

‫‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﭼﻨﺪ ﺷﺒﻜﻪ‬ ‫‪٢-٦‬‬
‫‪ PROFIBUS‬ﺩﺭ ﭼﻨﺪ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ‬ ‫‪٣-٦‬‬
‫‪Techno-Electro.com‬‬

‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ‬ ‫‪١٠٦‬‬

‫ﻣﻘﺪﻣﻪ ‪:‬‬
‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﻨﻈﻮﺭ ﺍﺯ‬ ‫ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ ﺑﻪ ﺳﺎﺧﺘﺎﺭﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ‪ STEP7‬ﻣﻲ ﭘﺮﺩﺍﺯﻳﻢ‬
‫‪ PROFIBUS‬ﺻﺮﻓﺎ ﭘﺮﻭﺗﻜﻞ ‪ DP‬ﻧﻴﺴﺖ ﻭ ‪ FMS‬ﺭﺍ ﻧﻴﺰ ﺷﺎﻣﻞ ﻣﻴﺸﻮﺩ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻴﺪﺍﻧﻴﻢ ﺍﻳﻦ ﺩﻭ ﭘﺮﻭﺗﻜﻞ ﻣﻴﺘﻮﺍﻧﻨﺪ‬
‫ﺑﻄﻮﺭ ﻫﻤﺰﻣﺎﻥ ﺭﻭﻱ ﻳﻚ ﺷﺒﻜﻪ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﻧﺪ‪ .‬ﺳﺎﺧﺘﺎﺭﻫﺎﻳﻲ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﺑﺤﺚ ﻣﻴﺸﻮﻧﺪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫ﻳﻚ ﺷﺒﻜﻪ ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ‬ ‫•‬

‫ﺩﻭ ﻳﺎ ﭼﻨﺪ ﺷﺒﻜﻪ ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ‬ ‫•‬

‫ﻳﻚ ﺷﺒﻜﻪ ﺩﺭ ﭼﻨﺪ ﭘﺮﻭﮊﻩ‬ ‫•‬

‫‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫‪ ١-٦‬ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ‬

‫ﺍﻳﻦ ﺳﺎﺧﺘﺎﺭ ﺳﺎﺩﻩ ﺗﺮﻳﻦ ﺣﺎﻟﺖ ﺍﺳﺖ ‪ .‬ﺑﺎ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﺗﺎﻛﻨﻮﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﻛﺎﺭﺑﺮ ﺑﺎ ﺍﻳﻦ ﺳﺎﺧﺘﺎﺭ ﺑﺨﻮﺑﻲ ﺁﺷﻨﺎﺳﺖ‪.‬‬
‫‪ Station‬ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻛﻪ ﻣﻴﺘﻮﺍﻧﻨﺪ ‪ Master‬ﻳﺎ ‪ I-Slave‬ﺑﺎﺷﻨﺪ ﺩﺭ ﻫﻨﮕﺎﻡ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻫﻤﮕﻲ ﺑﻪ ﻳﻚ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻣﺘﺼﻞ ﻣﻴﺸﻮﻧﺪ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ‪:‬‬

‫ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Simatic Manager‬ﺍﻟﻤﺎﻧﻬﺎﻳﻲ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺷﺖ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﺸﺨﺺ ﺍﺳﺖ‬
‫ﻓﻘﻂ ﻳﻚ ﺍﻟﻤﺎﻥ ﺑﺮﺍﻱ ‪ PROFIBUS‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٠٧‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ‬

‫ﻧﻜﺘﻪ ﺍﻱ ﻛﻪ ﺩﺭ ﻫﻤﻴﻦ ﺟﺎ ﻻﺯﻡ ﺍﺳﺖ ﺧﺎﻃﺮ ﻧﺸﺎﻥ ﺷﻮﺩ ﻧﺤﻮﻩ ﻗﺮﺍﺭﺩﺍﺩﻥ ﻳﻚ ‪ Station‬ﺭﻭﻱ ﺷﺒﻜﻪ ﺍﺳﺖ ﻛﻪ ﺍﺯ ﺧﺎﻧﻮﺍﺩﻩ‬
‫‪ S7‬ﻧﺒﺎﺷﺪ‪ .‬ﺍﻳﻨﻜﺎﺭ ﻫﻢ ﺍﺯ ﻃﺮﻳﻖ ‪ Simatic Manager‬ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ﻭ ﻫﻢ ﺍﺯ ﻃﺮﻳﻖ ‪.NetPro‬‬
‫ﺩﺭ ‪ Simatic Manager‬ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻣﻨﻮﻱ ‪ Insert > Station‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺑﺮﺍﻱ ‪ S5‬ﺍﺯ ‪ Simatic S5‬ﻭ‬
‫ﺑﺮﺍﻱ ‪ PC‬ﺍﺯ ‪ Simatic PC Station‬ﻭ ﺑﺮﺍﻱ ﻣﺤﺼﻮﻻﺕ ﻏﻴﺮ ﺯﻳﻤﻨﺲ ﺍﺯ ‪ Other Station‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪.‬‬

‫ﻣﻲ ﺑﻴﻨﻴﻢ ﻛﻪ ﺁﻳﻜﻮﻥ ﻣﺮﺑﻮﻃﻪ ﺩﺭ ﭘﻨﺠﺮﻩ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ﺍﻳﻦ ﺁﻳﻜﻮﻧﻬﺎﻱ ﭘﻨﺠﺮﻩ ﺍﻱ ﺑﺎﺯ‬
‫ﻣﻴﺸﻮﺩ ﻛﻪ ﺩﺭ ﺑﺨﺶ ‪ Interface‬ﺁﻥ ﺑﺎﻳﺪ ﻧﻮﻉ ﺍﺭﺗﺒﺎﻁ ﺭﺍ ﺗﻌﻴﻴﻦ ﻛﺮﺩ‪ .‬ﺑﺎ ﺍﻧﺘﺨﺎﺏ ‪ PROFIBUS‬ﻭ ‪ OK‬ﻛﺮﺩﻥ ﺍﻣﻜﺎﻥ‬
‫ﺍﺗﺼﺎﻝ ﺍﻳﻦ ‪ Station‬ﺑﻪ ﺷﺒﻜﻪ ﻣﻮﺭﺩ ﻧﻈﺮ ﻓﺮﺍﻫﻢ ﺷﺪﻩ ﻭ ﺁﺩﺭﺳﻲ ﺑﺮﺍﻱ ﺍﻳﻦ ‪ Node‬ﺗﻮﺳﻂ ﺳﻴﺴﺘﻢ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ‬ ‫‪١٠٨‬‬

‫ﺑﺮﺍﻱ ﺍﺗﺼﺎﻝ ‪ PC‬ﻧﻴﺰ ﺍﺯ ﻣﻨﻮﻱ ‪ Insert > Station > SIMATIC PC Station‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺑﺎ ﻛﻠﻴﻚ ﺭﻭﻱ‬
‫ﺁﻳﻜﻮﻥ ﺁﻥ ‪ ،‬ﺑﺮﻧﺎﻣﻪ ‪ HWConfig‬ﺑﺎﺯ ﻣﻴﺸﻮﺩ ﻭ ﻻﺯﻡ ﺍﺳﺖ ﺍﺯ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﻛﺎﺭﺕ ﺍﺭﺗﺒﺎﻃﻲ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﺯ ﺯﻳﺮ‬
‫ﻣﺠﻤﻮﻋﻪ ‪ SIMATIC PC Station‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩﻩ ﻭ ﺩﺭ ﻳﻜﻲ ﺍﺯ ﺍﺳﻼﺗﻬﺎﻱ ﻇﺎﻫﺮ ﺷﺪﻩ ﻗﺮﺍﺭ ﻣﻴﺪﻫﻴﻢ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺍﺗﻤﺎﻡ ﻛﺎﺭ ﻭ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺍﮔﺮ ﺑﺮﻧﺎﻣﻪ ‪ NetPro‬ﺭﺍ ﺍﺟﺮﺍ ﻛﻨﻴﻢ ﺷﻜﻠﻲ ﺷﺒﻴﻪ ﺯﻳﺮ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺷﺖ‪:‬‬
‫‪Techno-Electro.com‬‬

‫‪١٠٩‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﭼﻨﺪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ‬

‫‪ PROFIBUS‬ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫‪ ٢-٦‬ﺳﺎﺧﺘﺎﺭ ﭼﻨﺪ ﺷﺒﻜﻪ‬

‫ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ﻣﻴﺘﻮﺍﻥ ﭼﻨﺪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺍﻳﺠﺎﺩ ﻛﺮﺩ ﻛﻪ ﻛﺎﻣﻼ ﺍﺯ ﻳﻜﺪﻳﮕﺮ ﻣﺴﺘﻘﻞ ﺑﺎﺷﻨﺪ ﻭ ﻫﺮ ﻛﺪﺍﻡ ﺩﺍﺭﺍﻱ‬
‫‪Master System‬‬ ‫‪ Master‬ﻭ ‪ Slave‬ﻫﺎﻱ ﺧﺎﺹ ﺧﻮﺩ ﺑﺎﺷﻨﺪ‪ .‬ﺍﻳﻨﻜﺎﺭ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺩﺭ ‪ Hwconfig‬ﻫﻨﮕﺎﻡ ﻣﻌﺮﻓﻲ‬
‫ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪ .‬ﺭﻭﺵ ﺩﻳﮕﺮ ﻧﻴﺰ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ NetPro‬ﻭ ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﭼﻨﺪ ‪ Subnet‬ﻭ ﺳﭙﺲ ﺍﺗﺼﺎﻝ ‪ Station‬ﻫﺎ ﺑﻪ‬
‫‪ Subnet‬ﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺍﺳﺖ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ﺍﮔﺮ ﺑﻪ ‪ Simatic Manager‬ﺑﺎﺯ ﮔﺮﺩﻳﻢ ﺁﻳﻜﻮﻥ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Subnet‬ﻫﺎﻱ ﻓﻮﻕ ﺭﺍ ﺩﺭ ﭘﻨﺠﺮﻩ‬
‫ﺁﻥ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪:‬‬
‫‪Techno-Electro.com‬‬

‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﭼﻨﺪ ﭘﺮﻭﮊﻩ‬ ‫‪١١٠‬‬

‫‪ PROFIBUS‬ﺩﺭ ﭼﻨﺪ ﭘﺮﻭﮊﻩ ‪Step7‬‬ ‫‪ ٣-٦‬ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ‬

‫ﺩﺭ ﻃﺮﺍﺣﻲ ﻣﻤﻜﻦ ﺍﺳﺖ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻳﻚ ﻛﺎﺭﮔﺎﻩ ﺑﻪ ﭼﻨﺪ ﭘﺮﻭﮊﻩ ﺗﻘﺴﻴﻢ ﺷﻮﺩ ﻭﻟﻲ ﺩﺭ ﻫﻤﻪ ﺁﻧﻬﺎ ﻳﻚ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﺑﺎﻳﺪ ﻳﻚ ‪ Multiproject‬ﺍﻳﺠﺎﺩ ﻛﺮﺩ ﺳﭙﺲ ﺷﺒﻜﻪ ﻫﺎﻱ ﭘﺮﻭﮊﻩ ﻫﺎ ﺭﺍ ﺑﺎﻫﻢ ﺗﺮﻛﻴﺐ )‪ (Merge‬ﻧﻤﻮﺩ‪.‬‬
‫ﮔﺎﻣﻬﺎﻱ ﺯﻳﺮ ﻻﺯﻡ ﺍﺳﺖ ﺑﺘﺮﺗﻴﺐ ﺑﺮﺩﺍﺷﺘﻪ ﺷﻮﻧﺪ‪:‬‬
‫ﮔﺎﻡ ﺍﻭﻝ ‪ :‬ﺩﺭ ‪ Simatic Manager‬ﭘﺮﻭﮊﻩ ﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻩ ﻭ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺁﻧﻬﺎ ﺭﺍ ﭘﻴﻜﺮ‬
‫ﺑﻨﺪﻱ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫‪Multiproject‬‬ ‫ﮔﺎﻡ ﺩﻭﻡ ‪ :‬ﺩﺭ ‪ Simatic Manager‬ﺍﺯ ﻣﻨﻮﻱ ‪ File > New‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻩ ﻭ ﺩﺭ ﭘﻨﺠﺮﻩ ﺩﺭ ﻗﺴﻤﺖ‬
‫ﺍﺳﻢ ﺩﻟﺨﻮﺍﻩ ﺭﺍ ﻭﺍﺭﺩ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١١١‬‬ ‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﭼﻨﺪ‬

‫ﮔﺎﻡ ﺳﻮﻡ ‪ :‬ﺭﻭﻱ ﺍﺳﻢ ﭘﺮﻭﮊﻩ ﺑﺎ ﻛﻠﻴﻚ ﺭﺍﺳﺖ ﻣﺎﻭﺱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ‪ Add to Multiproject‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ ‪.‬‬
‫ﻟﻴﺴﺖ ﭘﺮﻭﮊﻩ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪ .‬ﺍﺯ ﺍﻳﻦ ﻟﻴﺴﺖ ﭘﺮﻭﮊﻩ ﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻭ ﺑﻪ ﭘﻨﺠﺮﻩ ﻭﺍﺭﺩ ﻣﻴﻜﻨﻴﻢ‪.‬‬

‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ ‪ :‬ﺍﺯ ﻣﻨﻮﻱ ‪ File>Multiproject‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻩ ﻭ ‪ Adjust Projects‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ‬
‫‪PROFIBUS‬‬ ‫ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﺑﺮﺍﻱ ‪ Merge‬ﻛﺮﺩﻥ ﺍﻧﻮﺍﻉ ‪ Subnet‬ﻫﺎ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻭ ﺍﺧﺘﺼﺎﺹ ﺑﻪ‬
‫ﻧﺪﺍﺭﺩ‪ .‬ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﺎ ‪ PROFIBUS‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ ﺳﭙﺲ ﺭﻭﻱ ‪ Execute‬ﻛﻠﻴﻚ ﻣﻴﻜﻨﻴﻢ‪.‬‬

‫ﮔﺎﻡ ﭘﻨﺠﻢ ‪ :‬ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺑﺎﻻﻱ ﺻﻔﺤﻪ ﺑﻌﺪ ﺑﺎﺯ ﻣﻴﺸﻮﺩ ﻛﻪ ﺩﺭ ﺁﻥ ﻟﻴﺴﺖ ﺷﺒﻜﻪ ﻫﺎﻱ ‪ PROFIBUS‬ﻣﻮﺟﻮﺩ‬
‫‪ OK‬ﻭ ‪Save‬‬ ‫ﺩﺭ ﭘﺮﻭﮊﻩ ﻫﺎ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﻫﺮ ﻛﺪﺍﻡ ﻛﻪ ﻣﺪ ﻧﻈﺮ ﺍﺳﺖ ﺭﺍ ﺑﻪ ﺳﻤﺖ ﺭﺍﺳﺖ ﻣﻨﺘﻘﻞ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺳﭙﺲ‬
‫ﻣﻴﻨﻤﺎﻳﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺳﺎﺧﺘﺎﺭ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﭼﻨﺪ ﭘﺮﻭﮊﻩ‬ ‫‪١١٢‬‬

‫ﺩﺭ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ‪ Merge‬ﻛﺮﺩﻥ ﺷﺒﻜﻪ ﻫﺎ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺍﺳﺖ ‪ .‬ﺑﺮﺍﻱ ‪ Unmerge‬ﻛﺮﺩﻥ ﻧﻴﺰ ﻫﻤﻴﻦ ﻣﺴﻴﺮ ﺭﺍ ﺩﻧﺒﺎﻝ ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫ﻧﺘﻴﺠﻪ ﺗﺮﻛﻴﺐ ﺷﺒﻜﻪ ﻫﺎ ﺭﺍ ﻣﻴﺘﻮﺍﻧﻴﻢ ﺩﺭ ‪ NetPro‬ﺑﺒﻴﻨﻴﻢ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ ﻛﻪ ﺍﺻﻄﻼﺡ ‪ PROFIBUS-wide‬ﺑﺮﺍﻱ‬
‫ﺷﺒﻜﻪ ﻛﻠﻲ ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﻧﻜﺎﺕ ﻗﺎﺑﻞ ﺗﻮﺟﻪ ‪:‬‬

‫‪Merge‬‬ ‫ﺗﻮﺳﻂ ﺑﺮﻧﺎﻣﻪ ‪ NetPro‬ﺍﺯ ﻣﻨﻮﻱ ‪ Edit>merge/Unmerge Subnetwork‬ﻧﻴﺰ ﻣﻴﺘﻮﺍﻥ ﻋﻤﻞ‬ ‫•‬

‫ﻭ ‪ Unmerge‬ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪ .‬ﺭﻭﺵ ﻛﺎﺭ ﻭ ﭘﻨﺠﺮﻩ ﻫﺎﻱ ﻣﺮﺑﻮﻃﻪ ﺑﻪ ﻫﻤﺎﻥ ﺻﻮﺭﺕ ﺍﺳﺖ ﻛﻪ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪ‪.‬‬
‫‪ NetPro‬ﭼﻚ ﺳﺎﺯﮔﺎﺭﻱ ﺍﺟﺰﺍ ﻭ ﻋﺪﻡ ﺗﺪﺍﺧﻞ ﺁﺩﺭﺳﻬﺎﻱ ‪Node‬‬ ‫ﭘﺲ ﺍﺯ ‪ Merge‬ﻛﺮﺩﻥ ﻻﺯﻡ ﺍﺳﺖ ﺩﺭ‬ ‫•‬

‫ﻫﺎ ﺍﺯ ﻣﻨﻮﻱ ‪ Network > Check Interproject Consistency‬ﺍﻧﺠﺎﻡ ﺷﻮﺩ‪.‬‬

‫ﻋﻤﻞ ‪ Merge‬ﻛﺮﺩﻥ ﻧﻤﻴﺘﻮﺍﻧﺪ ﺑﺮﺍﻱ ﭼﻨﺪ ﺷﺒﻜﻪ ﻛﻪ ﺩﺍﺧﻞ ﻳﻚ ﭘﺮﻭﮊﻩ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ ﺍﻧﺠﺎﻡ ﺷﻮﺩ‪ .‬ﺩﺭ ﻭﺍﻗﻊ ﻧﻴﺎﺯﻱ‬ ‫•‬

‫ﻫﻢ ﺑﻪ ﺍﻳﻦ ﻛﺎﺭ ﻧﻴﺴﺖ ﺯﻳﺮﺍ ﻛﺎﺭﺑﺮ ﻣﻴﺘﻮﺍﻧﺪ ﺑﺴﺎﺩﮔﻲ ﺗﻤﺎﻡ ﺍﺟﺰﺍ ﺭﺍ ﺑﻪ ﻳﻚ ﺷﺒﻜﻪ ﻣﺘﺼﻞ ﻧﻤﺎﻳﺪ‪.‬‬
Techno-Electro.com

PROFIBUS-DP ‫ﻓﺼﻞ ﻫﻔﺘﻢ – ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

: ‫ﻣﺸﺘﻤﻞ ﺑﺮ‬

Master / Slave ‫ ﺑﺮﺍﻱ‬DP ‫ ﺳﺮﻭﻳﺲ‬١-٧

Master / I-Slave ‫ ﺑﺮﺍﻱ‬DP ‫ ﺳﺮﻭﻳﺲ‬٢-٧
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ‫‪١١٤‬‬

‫ﻣﻘﺪﻣﻪ‬
‫ﺩﺭ ﺑﺨﺶ ﻫﺎﻱ ﻗﺒﻞ ﺣﺎﻟﺖ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ Master / Slave‬ﺩﺭ ‪ Profibus‬ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ‬
‫ﻧﺤﻮﻩ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ‪ DP‬ﺗﺸﺮﻳﺢ ﻣﻴﺸﻮﺩ‪ .‬ﻧﺤﻮﻩ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﺎﻧﻜﺸﻦ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ﻭﻗﺘﻲ ﺍﺯ ﻛﺎﺭﺕ ‪ CP‬ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﺷﻮﺩ ﻫﻤﺮﺍﻩ ﺑﺎ ﻣﺜﺎﻝ ﻣﻮﺭﺩ ﺑﺤﺚ ﻗﺮﺍﺭ ﻣﻲ ﮔﻴﺮﻧﺪ‪.‬‬

‫‪Master / Slave‬‬ ‫‪ ١-٧‬ﺳﺮﻭﻳﺲ ‪ DP‬ﺑﺮﺍﻱ‬

‫ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﻧﻴﺎﺯ ﺑﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺧﺎﺻﻲ ﻧﺪﺍﺭﺩ‪ .‬ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎ ﺷﺒﻴﻪ ﻛﺎﺭﺗﻬﺎﻱ ‪ I/O‬ﻛﻪ ﺩﺭ ﻛﻨﺎﺭ ‪ CPU‬ﻗﺮﺍﺭ‬
‫ﻣﻴﮕﻴﺮﻧﺪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻣﻴﺸﻮﻧﺪ ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﻓﺮﺽ ﻛﻨﻴﺪ ﺁﺩﺭﺳﻲ ﻛﻪ ﺩﺭ ‪ Hwconfig‬ﺑﺮﺍﻱ ﻳﻚ ﻭﺭﻭﺩﻱ ﺩﻳﺠﻴﺘﺎﻝ‬
‫‪ ET200M‬ﺩﺍﺩﻩ ﺷﺪﻩ ﺁﺩﺭﺱ ‪ 4‬ﻭ ﺁﺩﺭﺳﻲ ﻛﻪ ﺑﺮﺍﻱ ﻭﺭﻭﺩﻱ ﺁﻧﺎﻟﻮﮒ ﺩﺍﺩﻩ ﺷﺪﻩ ﺁﺩﺭﺱ ‪ 254‬ﺑﺎﺷﺪ‪ .‬ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ﺩﺭ‬
‫ﺑﺮﻧﺎﻣﻪ ‪ CPU‬ﺍﻳﻦ ﻭﺭﻭﺩﻱ ﻫﺎ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﻧﺪ‪:‬‬
‫ﺑﺮﺍﻱ ﺧﻮﺍﻧﺪﻥ ﻳﻚ ﺑﻴﺖ ﺩﻳﺠﻴﺘﺎﻝ ﻭﺭﻭﺩﻱ ﻣﺜﻼ ﻛﺎﻧﺎﻝ ﺍﻭﻝ‬ ‫‪A‬‬ ‫‪I 4.0‬‬

‫ﺑﺮﺍﻱ ﺧﻮﺍﻧﺪﻥ ﻳﻚ ﻭﺭﻭﺩﻱ ﺁﻧﺎﻟﻮﮒ‬ ‫‪L PIW 254‬‬

‫ﭘﺲ ﺑﻌﺒﺎﺭﺕ ﺩﻳﮕﺮ ‪:‬‬

‫ﻣﺰﻳﺖ ﺍﻳﻦ ﺭﻭﺵ ﺁﻧﺴﺖ ﻛﻪ ﺁﺩﺭﺱ ﺩﻫﻲ ﺷﺒﻴﻪ ﺣﺎﻟﺖ ‪ Central‬ﺑﺎ ﻫﻤﺎﻥ ﻓﺮﻣﺖ ﻭ ﻫﻤﺎﻥ ﺩﺳﺘﻮﺭﺍﺕ ﺍﺳﺖ‪..‬‬ ‫•‬
‫ﻋﻴﺐ ﺍﻳﻦ ﺭﻭﺵ ﺁﻧﺴﺖ ﻛﻪ ﺑﺎ ﺩﺳﺘﻮﺭﺍﺕ ‪ Load‬ﻭ ‪ Transfer‬ﻫﺮ ﺑﺎﺭ ﻣﺎﻛﺰﻳﻤﻢ ﭼﻬﺎﺭ ﺑﺎﻳﺖ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺍﺭﺳﺎﻝ‬ ‫•‬

‫ﻳﺎ ﺩﺭﻳﺎﻓﺖ ﻛﺮﺩ‪.‬‬

‫‪System‬‬ ‫ﺑﺮﺍﻱ ﺭﻓﻊ ﻋﻴﺐ ﻓﻮﻕ ﺍﻟﺬﻛﺮ ﻓﺎﻧﻜﺸﻦ ﻫﺎﻳﻲ ﺗﻮﺳﻂ ﺯﻳﻤﻨﺲ ﺗﻌﺒﻴﻪ ﺷﺪﻩ ﻛﻪ ﻣﻴﺘﻮﺍﻥ ﺁﻧﻬﺎ ﺭﺍ ﺩﺭ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ‬
‫‪ Function‬ﭘﻨﺠﺮﻩ ‪ Program Element‬ﺑﺮﻧﺎﻣﻪ ‪ LAD/STL/FBD‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻣﺸﺎﻫﺪﻩ ﻭ ﺩﺭ ﺻﻮﺭﺕ ﻧﻴﺎﺯ ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﻛﺮﺩ‪ .‬ﺍﺯ ﺟﻤﻠﻪ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻫﺎ ‪ SFC14‬ﻭ ‪ SFC15‬ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﻧﺎﻡ ﺑﺮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١١٥‬‬ ‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

‫‪ SFC14‬ﺑـﺎ ﻧـﺎﻡ ﺳـﻤﺒﻠﻴﻚ ‪ DPRD-DAT‬ﺑﺮﺍﻱ ﺩﺭﻳﺎﻓﺖ ﺩﻳﺘﺎ ﻭ ‪ SFC15‬ﺑﺎ ﻧﺎﻡ ﺳﻤﺒﻠﻴﻚ ‪ DPWR-DAT‬ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ‪.‬‬

‫ﺁﻧﭽـﻪ ﺩﺭ ﺍﻳـﻦ ﺑـﻼﻙ ﻫـﺎ ﺗﺤـﺖ ﻋـﻨﻮﺍﻥ ‪ LADDR‬ﻇﺎﻫـﺮ ﻣﻲ ﺷﻮﺩ ﺁﺩﺭﺱ ﻣﻘﺼﺪ ﺍﺳﺖ ﻛﻪ ﺩﻳﺘﺎ ﺑﺎﻳﺪ ﺑﻪ ﺁﻥ ﺍﺭﺳﺎﻝ ﻳﺎ ﺍﺯ ﺁﻥ‬
‫ﺩﺭﻳﺎﻓﺖ ﺷﻮﺩ‪ .‬ﻭ ﺑﺎﻳﺪ ﺑﻪ ﻓﺮﻣﺖ ‪ Hex‬ﻧﻮﺷﺘﻪ ﺷﻮﺩ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺁﺩﺭﺱ ‪ Diagnostic=100‬ﺗﺒﺪﻳﻞ ﺑﻪ ‪LADDR=W#16#64‬‬

‫ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬

‫ﺣﺠﻢ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﺑﺎﻳﺪ ﺍﺭﺳﺎﻝ ﻳﺎ ﺩﺭﻳﺎﻓﺖ ﺷﻮﺩ ﺗﻮﺳﻂ ﺁﺩﺭﺳﻲ ﻛﻪ ﺑﺼﻮﺭﺕ ‪ Pointer‬ﺩﺭ ﺟﻠﻮﻱ ‪ Record‬ﻧﻮﺷﺘﻪ ﻣﻴﺸﻮﺩ‬
‫ﻣﺸﺨﺺ ﻣﻴﮕﺮﺩﺩ‪.‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮ ﻗﺮﺍﺭ ﺑﺎﺷﺪ ﺍﺯ ﻳﻚ ﻛﺎﺭﺕ ﻭﺭﻭﺩﻱ ﻛﻪ ﺭﻭﻱ ﻳﻚ ‪ DP Slave‬ﻣﺪﻭﻻﺭ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﻛﻞ‬
‫ﻫﺸﺖ ﺑﺎﻳﺖ ﺑﺎ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ﺻﻔﺮ ﺭﺍ ﺑﺨﻮﺍﻧﺪ ﺩﺭﻳﻨﺼﻮﺭﺕ ﺩﺭ ‪ SFC14‬ﺩﺭ ﺟﻠﻮﻱ ‪ Record‬ﺑﺎﻳﺪ ﻣﻘﺪﺍﺭ‬
‫‪ P#I0.0 byte 8‬ﺭﺍ ﻗﺮﺍﺭ ﺩﺍﺩ‪.‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﺑﺮﺍﻱ ‪ DP Slave‬ﻫﺎﻱ ﻣﺪﻭﻻﺭ ﺩﺭ ﻫﺮ ‪ Call‬ﻓﻘﻂ ﻣﻲ ﺗﻮﺍﻥ ﺍﺩﺭﺱ ﻳﻚ‬
‫ﻣﺪﻭﻝ ﺭﺍ ﺗﺒﺎﺩﻝ ﻛﺮﺩ‪.‬‬
‫‪ SFC‬ﻫﺎﻱ ﻓﻮﻕ ﺍﻟﺬﻛﺮ ﻋﻼﻭﻩ ﺑﺮ ‪ DP Slave‬ﻫﺎﻱ ﻣﻌﻤﻮﻟﻲ ﺑﺮﺍﻱ ‪ Intelligent Slave‬ﻫﺎ ﻧﻴﺰ ﻛﺎﺭﺑﺮﺩ ﺩﺍﺭﻧﺪ‪ .‬ﻛﻪ ﺩﺭ‬
‫ﻗﺴﻤﺖ ﺑﻌﺪ ﺗﺸﺮﻳﺢ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ‫‪١١٦‬‬

‫‪Master / I-Slave‬‬ ‫‪ ٢-٧‬ﺳﺮﻭﻳﺲ ‪ DP‬ﺑﺮﺍﻱ‬

‫ﺩﺭ ﻓﺼﻞ ﻗﺒﻞ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ‪ Master‬ﻭ ‪ I-Slave‬ﻣﻮﺭﺩ ﺑﺤﺚ ﻗﺮﺍﺭ ﮔﺮﻓﺖ ﻭ ﺣﺎﻟﺖ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺁﻥ ﺑﻴﺎﻥ ﺷﺪ‪.‬‬
‫ﺩﺭ ﺭﻭﺷﻲ ﻛﻪ ﺫﻛﺮ ﺷﺪ ﺩﻳﺘﺎ ﺍﺯ ﻳﻚ ‪ CPU‬ﺑﻪ ‪ CPU‬ﺩﻳﮕﺮ ﻣﻨﺘﻘﻞ ﺷﺪﻩ ﻭ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺑﺎ ﺩﺳﺘﻮﺭﺍﺕ ﻣﻌﻤﻮﻝ ﺍﺯ ﺁﻥ‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺍﻣﺎ ﺩﻭ ﺭﻭﺵ ﺩﻳﮕﺮ ﻧﻴﺰ ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪ .‬ﻳﻚ ﺭﻭﺵ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ‬
‫‪ SFC‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺻﻔﺤﻪ ﻗﺒﻞ ﺁﻧﻬﺎ ﺭﺍ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ‪ Master‬ﺑﺎ ‪ DP-Slave‬ﺗﻮﺿﻴﺢ ﺩﺍﺩﻳﻢ‪ .‬ﺍﺻﻮﻝ ﻛﺎﺭ ﺩﺭ ﺍﻳﻨﺠﺎ ﻧﻴﺰ‬
‫ﻣﺸﺎﺑﻪ ﺍﺳﺖ‪ .‬ﺗﻨﻬﺎ ﺗﻔﺎﻭﺗﻲ ﻛﻪ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﺍﻳﻨﺴﺖ ﻛﻪ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻨﻬﺎ ﺩﺭ ﺩﻭﻃﺮﻑ ﻣﻴﺘﻮﺍﻧﻨﺪ ‪ Call‬ﺷﻮﻧﺪ ﻣﺜﺎﻝ ﺯﻳﺮ ﺍﻳﻦ ﻣﻮﺿﻮﻉ‬
‫ﺭﺍ ﺑﻬﺘﺮ ﻣﻌﺮﻓﻲ ﻣﻴﻜﻨﺪ‪.‬‬
‫‪In the DP Slave CPU‬‬ ‫‪In the DP Master CPU‬‬
‫‪L2‬‬ ‫‪Data‬‬
‫‪T MB 6‬‬ ‫‪preprocessing in‬‬
‫‪L IB 0‬‬ ‫‪DP slave‬‬
‫‪T MB 7‬‬

‫‪L MW 6‬‬ ‫‪Forward data‬‬

‫‪T PQW 310‬‬ ‫‪To DP master‬‬

‫‪L PIB 222‬‬ ‫‪Postprocess‬‬

‫‪T MB 50‬‬ ‫‪receive data in‬‬
‫‪L PIB 223‬‬ ‫‪DP master‬‬
‫‪L B#16#3‬‬
‫‪+I‬‬
‫‪T MB 51‬‬

‫‪L 10‬‬ ‫‪Data Processing‬‬

‫‪+3‬‬ ‫‪in DP master‬‬
‫‪T MB 60‬‬

‫‪CALL SFC 15‬‬ ‫‪Send data to DP‬‬

‫‪LADDR:= W#16#0‬‬ ‫‪slave‬‬
‫‪RECORD:= P#M60.0‬‬
‫‪Byte20‬‬
‫‪RET_VAL:=MW 22‬‬

‫‪CALL SFC 14‬‬ ‫‪Receive data‬‬

‫‪LADDR:=W#16#D‬‬ ‫‪from DP master‬‬
‫‪RET_VAL:=MW 20‬‬
‫‪RECORD:=P#M30.0‬‬
‫‪Byte20‬‬
‫‪L MB 30‬‬ ‫‪Postprocess‬‬
‫‪L MB 7‬‬ ‫‪receive data‬‬
‫‪+I‬‬
‫‪T MW 100‬‬
‫‪Techno-Electro.com‬‬

‫‪١١٧‬‬ ‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

‫ﺭﻭﺵ ﺩﻳﮕﺮﻱ ﻛﻪ ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﺁﻥ ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺑﻴﻦ ‪ Master‬ﻭ ‪ I-Slave‬ﺍﺯ ﺁﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﻮﺩ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﺎﻧﻜﺸﻦ ﻫﺎﻱ‬
‫ﺧﺎﺹ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺳﺖ‪ .‬ﺍﻳﻦ ﺭﻭﺵ ﻓﻘﻂ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺍﺯ ﻃﺮﻳﻖ ﻛﺎﺭﺕ ‪ CP‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ‪ .‬ﮔﺎﻣﻬﺎﻳﻲ ﻛﻪ ﺩﺭ ﺍﻳﻦ‬
‫ﺭﻭﺵ ﺑﺎﻳﺪ ﺑﺮﺩﺍﺷﺘﻪ ﺷﻮﺩ ﻫﻤﺮﺍﻩ ﺑﺎ ﻳﻚ ﻣﺜﺎﻝ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﻣﺜﺎﻝ ﻳﻚ ‪ S7-300‬ﺑﺎ ‪ CPU314‬ﺑﻌﻨﻮﺍﻥ‬
‫‪ Master‬ﺑﺎ ﻛﺎﺭﺕ ‪ CP342-5‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ‪ I-Slave .‬ﻧﻴﺰ ﻳﻚ ‪ S7-300‬ﺑﺎ ﻫﻤﺎﻥ ‪ CPU‬ﻭ ﻫﻤﺎﻥ ﻛﺎﺭﺕ ‪ CP‬ﻣﻴﺒﺎﺷﺪ‪.‬‬
‫‪Operating Mode‬‬ ‫ﻼ ﺑﻪ ﺗﻔﺼﻴﻞ ﺑﻴﺎﻥ ﺷﺪ ﻭ ﻧﻴﺎﺯﻱ ﺑﻪ ﺗﻜﺮﺍﺭ ﻧﺪﺍﺭﺩ ‪ .‬ﻓﻘﻂ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ‬
‫ﺭﻭﺵ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻗﺒ ﹰ‬
‫ﺑﺮﺍﻱ ‪ Master‬ﺭﻭﻱ ﻛﺎﺭﺕ ‪ CP‬ﺑﻌﻨﻮﺍﻥ ‪ DP Master‬ﺍﻧﺘﺨﺎﺏ ﻣﻴﺸﻮﺩ‪ .‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺍﻳﻦ ﺗﻨﻈﻴﻢ ﺑﺮﺍﻱ ﻛﺎﺭﺕ ‪ CP‬ﺭﻭﻱ‬
‫‪ I-Slave‬ﺑﺼﻮﺭﺕ ‪ DP Slave‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺍﺻﻮﻝ ﻛﻠﻲ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ‫‪١١٨‬‬

‫ﺑﻠﻮﻙ ﺩﻳﺎﮔﺮﺍﻡ ﺑﺮﻧﺎﻣﻪ ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﺷﺪﻩ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻼﺣﻈﻪ ﻣﻴﺸﻮﺩ‪:‬‬
‫• ﺩﺭ ﺳﻤﺖ ‪ Master‬ﻭ ‪ Slave‬ﭘﺲ ﺍﺯ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺩﻳﺘﺎ ﺑﻼﻛﻬﺎﻱ ‪ DB10‬ﻭ ‪ DB11‬ﺗﻮﺳﻂ ‪ OB100‬ﺍﻳﺠﺎﺩ ﻣﻴﺸﻮﻧﺪ‪.‬‬
‫• ﺩﺭ ﺳﻤﺖ ‪ Master‬ﺩﻳﺘﺎ ﺍﺯ ‪ DB11‬ﺗﻮﺳﻂ ﻓﺎﻧﻜﺸﻦ ‪ DP_SEND‬ﺑﻪ ‪ Slave‬ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ‪.‬‬
‫• ‪ Slave‬ﺩﻳﺘﺎﻱ ﻓﻮﻕ ﺭﺍ ﺑﺎ ﻓﺎﻧﻜﺸﻦ ‪ DP_RECV‬ﺩﺭﻳﺎﻓﺖ ﻛﺮﺩﻩ ﻭ ﺩﺭ ‪ DB10‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺧﻮﺩ ﺫﺧﻴﺮﻩ ﻣﻴﻜﻨﺪ‪.‬‬
‫• ﺩﺭ ﺳﻤﺖ ‪ Master‬ﻓﺎﻧﻜﺸﻦ ‪ FC29‬ﻛﻪ ﺗﻮﺳﻂ ﻛﺎﺭﺑﺮ ﻧﻮﺷﺘﻪ ﺷﺪﻩ ﺍﺟﺮﺍ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺩﻳﺘﺎﻱ ‪ DB11‬ﺭﺍ ﻫﺮ‬
‫ﺳﻪ ﺛﺎﻧﻴﻪ ﻳﻜﺒﺎﺭ ﺍﻓﺰﺍﻳﺶ ﻳﺎ ﻛﺎﻫﺶ ﻣﻴﺪﻫﺪ‪.‬‬
‫• ﺩﺭ ﺳﻤﺖ ‪ Slave‬ﺩﻳﺘﺎ ﺍﺯ ‪ DB11‬ﺗﻮﺳﻂ ﻓﺎﻧﻜﺸﻦ ‪ DP_SEND‬ﺑﻪ ‪ Master‬ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ‪.‬‬
‫• ‪ Master‬ﺩﻳﺘﺎﻱ ﻓﻮﻕ ﺭﺍ ﺑﺎ ﻓﺎﻧﻜﺸﻦ ‪ DP_RECV‬ﺩﺭﻳﺎﻓﺖ ﻣﻴﻜﻨﺪ ﻭ ﺩﺭ ‪ DB11‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺧﻮﺩ ﺫﺧﻴﺮﻩ ﻣﻴﻨﻤﺎﻳﺪ‪.‬‬

‫ﺑﺮﻧﺎﻣﻪ ﺑﻼﻛﻬﺎﻱ ﻓﻮﻕ ﺍﻟﺬﻛﺮ ﺩﺭ ﺻﻔﺤﺎﺕ ﺑﻌﺪ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪Techno-Electro.com‬‬

‫‪١١٩‬‬ ‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

‫‪Master‬‬ ‫ﺑﺮﻧﺎﻣﻪ ‪ OB100‬ﺩﺭ ﺳﻤﺖ‬

‫ﻻ ﺑﺮﺍﻱ ﺗﻤﺎﻡ ‪ CPU‬ﻫﺎﻱ ﺧﺎﻧﻮﺍﺩﻩ ‪ S7-300‬ﺑﺼﻮﺭﺕ ﭘﻴﺶ‬
‫‪ OB100‬ﺑﺮﺍﻱ ‪ Warm Restart‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻛﻪ ﻣﻌﻤﻮ ﹰ‬
‫ﻓﺮﺽ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ‪ .‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Master‬ﺑﺎ ﻫﺮ ﺑﺎﺭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺗﻮﺳﻂ ‪ OB100‬ﺩﻳﺘﺎ ﺑﻼﻛﻬﺎﻱ ‪ DB10‬ﻭ ‪ DB11‬ﺍﻳﺠﺎﺩ‬
‫‪CREAT_DB‬‬ ‫ﻣﻴﺸﻮﻧﺪ‪ .‬ﻓﺎﻧﻜﺸﻨﻲ ﻛﻪ ﻛﺎﺭ ﺍﻳﺠﺎﺩ ﺩﻳﺘﺎ ﺑﻼﻙ ﺭﺍ ﺍﻧﺠﺎﻡ ﻣﻴﺪﻫﺪ ‪ SFC22‬ﻧﺎﻡ ﺩﺍﺭﺩ ﻛﻪ ﻧﺎﻡ ﺳﻤﺒﻠﻴﻚ ﺁﻥ‬
‫ﻣﻴﺒﺎﺷﺪ‪ .‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﺍﻳﻦ ﺩﻳﺘﺎ ﺑﻼﻛﻬﺎ ﺩﺭ ﺣﺎﻓﻈﻪ ‪ CPU‬ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﻭ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﻧﺪ ﻭ ﺩﺭ ﭘﺮﻭﮊﻩ‬
‫‪ Offline‬ﻇﺎﻫﺮ ﻧﺨﻮﺍﻫﻨﺪ ﺷﺪ‪.‬‬

‫ﻭﺭﻭﺩﻱ ﻫﺎﻱ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬

‫ﺷﻤﺎﺭﻩ ﺍﻭﻟﻴﻦ ﺩﻳﺘﺎ ﺑﻼﻙ ﻛﻪ ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﻋﺪﺩ ‪ ١٠‬ﻣﻴﺒﺎﺷﺪ‪.‬‬ ‫‪LOW_LIMIT‬‬

‫ﺷﻤﺎﺭﻩ ﺁﺧﺮﻳﻦ ﺩﻳﺘﺎ ﺑﻼﻙ ﻛﻪ ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﻋﺪﺩ ‪ ١١‬ﻣﻴﺒﺎﺷﺪ‪.‬‬ ‫‪UP_LIMIT‬‬

‫ﻣﻘﺪﺍﺭ ﺑﺎﻳﺖ ﺭﺯﺭﻭ ﺷﺪﻩ ﺑﺮﺍﻱ ﺩﻳﺘﺎ ﺑﻼﻙ ﻛﻪ ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ‪ ٣٠٠‬ﻣﻨﻈﻮﺭ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬ ‫‪COUNT‬‬

‫ﺧﺮﻭﺟﻲ ﻫﺎﻱ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬

‫ﻳﻚ ﻋﺪﺩ ﺻﺤﻴﺢ ﺑﺮﻣﻴﮕﺮﺩﺍﻧﺪ ﻛﻪ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﻭﺟﻮﺩ ﻳﺎ ﻋﺪﻡ ﻭﺟﻮﺩ ﺧﻄﺎ ﺩﺭ ﺍﺟﺮﺍﺳﺖ‪.‬‬ ‫‪RET_VAL‬‬

‫ﻳﻚ ‪ word‬ﻛﻪ ﺷﻤﺎﺭﻩ ﺍﻭﻟﻴﻦ ﺩﻳﺘﺎﺑﻼﻙ ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬ ‫‪DB_NUMBER‬‬

‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺕ ﻓﻮﻕ ﺑﺮﻧﺎﻣﻪ ‪ OB100‬ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪:‬‬

‫‪L 10‬‬
‫‪T MW 20‬‬
‫‪L 11‬‬
‫‪T MW 22‬‬
‫‪L 300‬‬
‫‪T MW 24‬‬
‫‪CALL SFC 22‬‬
‫‪LOW_LIMIT:=MW20‬‬
‫‪UP_LIMIT :=MW22‬‬
‫‪COUNT :=MW24‬‬
‫‪RET_VAL :=MW26‬‬
‫‪DB_NUMBER:=MW28‬‬
‫‪BE‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ‫‪١٢٠‬‬

‫‪Slave‬‬ ‫ﺑﺮﻧﺎﻣﻪ ‪ OB100‬ﺩﺭ ﺳﻤﺖ‬
‫ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﻧﻴﺰ ﻣﺸﺎﺑﻪ ﺑﺮﻧﺎﻣﻪ ﻓﻮﻕ ﻣﻴﺒﺎﺷﺪ‪.‬‬
‫‪Master‬‬ ‫ﻓﺎﻧﻜﺸﻦ ‪ DP_SEND‬ﺩﺭ ﺳﻤﺖ‬
‫ﻓﺎﻧﻜﺸﻦ ﻓﻮﻕ ﻛﻪ ﻧﺎﻡ ﺍﺻﻠﻲ ﺁﻥ ‪ FC1‬ﺍﺳﺖ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﻣﺴﻴﺮ‬
‫‪Program‬‬ ‫ﺭﻭﺑﺮﻭ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ LAD/STL/FBD‬ﺍﺯ ﭘﻨﺠﺮﻩ‬
‫‪DP_SEND‬‬ ‫‪ Element‬ﻭﺍﺭﺩ ﻛﺮﺩ ﻭ ﺁﻧﺮﺍ ﺻﺪﺍ ﺯﺩ‪ .‬ﻓﺎﻧﻜﺸﻦ‬
‫ﻣﻘﺪﺍﺭ ﻣﺸﺨﺼﻲ ﺩﻳﺘﺎ ﺑﺎ ﺁﺩﺭﺱ ﻣﺸﺨﺺ ﺷﺪﻩ ﺭﺍ ﺍﺭﺳﺎﻝ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﻭﻗﺘﻲ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺻﺪﺍ ﺯﺩﻩ ﻣﻴﺸﻮﺩ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻴﻬﺎﻱ ﺁﻥ‬
‫ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺧﻮﺍﻫﻨﺪ ﺑﻮﺩ‪.‬‬

‫ﭘﺎﺭﺍﻣﺘﺮ ‪CPLADDR‬‬
‫ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﻭﺭﻭﺩﻱ ﺍﺳﺖ ﻭ ﺑﺎﻳﺪ ﺩﺭ ﺟﻠﻮﻱ ﺁﻥ ﺁﺩﺭﺱ ﺑﻴﺲ ﻛﺎﺭﺕ ‪ CP‬ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺭﺍ ﺑﻪ ﻓﺮﻣﺖ ‪ Hex‬ﻧﻮﺷﺖ ‪ .‬ﺍﻳﻦ‬
‫ﺁﺩﺭﺱ ﺑﺼﻮﺭﺕ ﻋﺪﺩ ﺻﺤﻴﺢ ﺩﺭ ‪ Hwconfig‬ﺑﻌﻨﻮﺍﻥ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ﻭﺭﻭﺩﻱ ﺫﻛﺮ ﻣﻴﺸﻮﺩ ‪.‬‬

‫ﺩﺭ ﺷﻜﻞ ﻓﻮﻕ ﺍﻳﻦ ﺁﺩﺭﺱ ‪ ٢٧٢‬ﺍﺳﺖ ﻛﻪ ﻣﻌﺎﺩﻝ ﻫﮕﺰ ﺁﻥ ‪ 0110‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﺑﻨﺎﺑﺮﺍﻳﻦ ﺩﺭ ﺟﻠﻮﻱ ﺍﻳﻦ ﻭﺭﻭﺩﻱ ﺑﺎﻳﺪ‬
‫ﻧﻮﺷﺖ‪:‬‬
‫‪CPLADDR:= W#16#0110‬‬
‫ﭘﺎﺭﺍﻣﺘﺮ ‪SEND‬‬
‫ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ﻭ ﻣﻴﺰﺍﻥ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﻗﺮﺍﺭ ﺍﺳﺖ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ‪١٠‬‬
‫ﺑﺎﻳﺖ ﺍﺯ ﺁﺩﺭﺱ ﺻﻔﺮ ﺩﻳﺘﺎ ﺑﻼﻙ ﺷﻤﺎﺭﻩ ‪ ١١‬ﻣﻴﻨﻮﻳﺴﻴﻢ‪:‬‬
‫‪SEND :=P#DB11.DBX0.0 BYTE 10‬‬
‫ﻃﻮﻝ ﺁﺩﺭﺱ ﻧﺒﺎﻳﺪ ﺍﺯ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺑﻴﺸﺘﺮ ﺑﺎﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٢١‬‬ ‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

‫ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ‪DONE , ERROR , STATUS‬‬

‫ﺍﻳﻦ ﺧﺮﻭﺟﻲ ﻫﺎ ﻭﺿﻌﻴﺖ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﺭﺍ ﻣﻄﺎﺑﻖ ﺑﺎ ﺣﺎﻻﺕ ﺯﻳﺮ ﻧﻤﺎﻳﺶ ﻣﻲ ﺩﻫﻨﺪ‪:‬‬
‫ﺣﺎﻟﺖ ﺍﻭﻝ ‪ :‬ﺍﺭﺳﺎﻝ ﺑﺪﻭﻥ ﺧﻄﺎ ﻛﺎﻣﻞ ﺷﺪﻩ ﺍﺳﺖ‬
‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻭﺿﻌﻴﺖ ﺳﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻓﻮﻕ ﻣﻄﺎﺑﻖ ﺟﺪﻭﻝ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪:‬‬
‫‪DONE := 1‬‬
‫‪ERROR := 0‬‬
‫‪STATUS := 0‬‬

‫ﺣﺎﻟﺖ ﺩﻭﻡ ‪ :‬ﺍﺭﺳﺎﻝ ﻫﻨﻮﺯ ﻛﺎﻣﻞ ﻧﺸﺪﻩ ﻭ ‪ Job‬ﻓﻌﺎﻝ ﺍﺳﺖ‬

‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻭﺿﻌﻴﺖ ﺳﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻓﻮﻕ ﻣﻄﺎﺑﻖ ﺟﺪﻭﻝ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪:‬‬
‫‪DONE := 0‬‬
‫‪ERROR := 0‬‬
‫‪STATUS := 8180‬‬

‫ﺣﺎﻟﺖ ﺳﻮﻡ ‪ :‬ﺍﺭﺳﺎﻝ ﺑﺪﻟﻴﻞ ﻭﺟﻮﺩ ﺍﺷﻜﺎﻝ ﻗﻄﻊ ﺷﺪﻩ ﺍﺳﺖ‬

‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﻭﺿﻌﻴﺖ ﺳﻪ ﭘﺎﺭﺍﻣﺘﺮ ﻓﻮﻕ ﻣﻄﺎﺑﻖ ﺟﺪﻭﻝ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪:‬‬
‫‪DONE := 0‬‬
‫‪ERROR := 1‬‬
‫‪STATUS := x‬‬
‫ﻼ ﻛﺪ ‪ 80D2‬ﻫﮕﺰ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﻏﻠﻂ ﺑﻮﺩﻥ‬
‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻛﺪ ‪ x‬ﻣﻘﺎﺩﻳﺮ ﻣﺘﻔﺎﻭﺗﻲ ﺭﺍ ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ﺍﺷﻜﺎﻝ ﺑﺮﻣﻴﮕﺮﺩﺍﻧﺪ ﻣﺜ ﹰ‬
‫ﺁﺩﺭﺱ ﺑﻴﺲ ﻛﺎﺭﺕ ‪ CP‬ﺍﺳﺖ ﻓﺮﺿﹰﺎ ﻛﺎﺭﺕ ‪ CP‬ﺭﺍ ﺩﺭ ‪HWcofig‬ﻋﻮﺽ ﻛﺮﺩﻩ ﻭﻟﻲ ﺁﺩﺭﺱ ﺁﻧﺮﺍ ﺗﻨﻈﻴﻢ ﻧﻜﺮﺩﻩ ﺍﻳﺪ‪.‬‬
‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺟﺪﻭﻝ ﺻﻔﺤﻪ ﺑﻌﺪ ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬

‫‪Slave‬‬ ‫ﻓﺎﻧﻜﺸﻦ ‪ DP_SEND‬ﺩﺭ ﺳﻤﺖ‬

‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﺑﺮﺍﻱ ‪ Master‬ﺩﺍﺩﻩ ﺷﺪ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻧﻴﺰ ﻧﻴﺎﺯ ﺑﻪ ﺷﺮﺡ ﺍﺿﺎﻓﻲ ﻧﺪﺍﺭﺩ‪ .‬ﻃﻮﻝ ﺁﺩﺭﺳﻲ ﻛﻪ ﺩﺭ ﺟﻠﻮﻱ‬
‫ﭘﺎﺭﺍﻣﺘﺮ ‪ SEND‬ﻧﻮﺷﺘﻪ ﻣﻴﺸﻮﺩ ﻧﺒﺎﻳﺪ ﺍﺯ ‪ ٨٦‬ﺑﺎﻳﺖ ﺑﻴﺸﺘﺮ ﺑﺎﺷﺪ‪.‬‬
Techno-Electro.com

PROFIBUS-DP ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ١٢٢

DONE ERROR STATUS Meaning
No configuration or the DP service has not yet started on
0 1 8183H
the PROFIBUS CP
0 1 8184H System error or bad parameter type.
0 1 8F22H Area length error reading a parameter (e.g. DB too short).
0 1 8F23H Area length error writing a parameter (e.g. DB too short).
0 1 8F24H Area error reading a parameter.
0 1 8F25H Area error writing a parameter.
0 1 8F28H Alignment error reading a parameter.
0 1 8F29H Alignment error writing a parameter.
0 1 8F30H Parameter is in the write-protected 1st act. data block.
0 1 8F31H Parameter is in the write-protected 2nd act. data block.
0 1 8F32H Parameter contains a DB number that is too high.
0 1 8F33H DB number error.
0 1 8F3AH Destination area not loaded (DB).
0 1 8F42H Timeout reading a parameter from the I/O area.
0 1 8F43H Timeout writing a parameter to the I/O area.

Address of the parameter to be read is disabled in the

0 1 8F44H
access track
Address of the parameter to be written is disabled in
0 1 8F45H
the access track
0 1 8F7FH Internal error, e.g. illegal ANY reference.
0 1 8090H No module with this address exists.
0 1 8091H Logical base address not at a double word boundary.
0 1 80A1H Negative acknowledgment writing to the module.
0 1 80B0H The module does not recognize the data record.
0 1 80B1H The specified data record length is incorrect.
0 1 80C0H The data record cannot be read.
The specified data record is currently being
0 1 80C1H
processed.
0 1 80C2H There are too many jobs pending.
0 1 80C3H Resources occupied (memory).
Communication error (occurs temporarily, it is usually
0 1 80C4H
best to
repeat the job in the user program).
0 1 80D2H Logical base address incorrect.
‫‪Techno-Electro.com‬‬

‫‪١٢٣‬‬ ‫‪PROFIBUS-DP‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

‫‪Master‬‬ ‫ﻓﺎﻧﻜﺸﻦ ‪ DP_RECV‬ﺩﺭ ﺳﻤﺖ‬
‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻛﻪ ﻧﺎﻡ ﺍﺻﻠﻲ ﺁﻥ ‪ FC2‬ﺍﺳﺖ ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﻫﻤﺎﻥ ﺭﻭﺷﻲ ﻛﻪ ﺑﺮﺍﻱ ‪ DP_SEND‬ﺫﻛﺮ ﺷﺪ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﺻﺪﺍ‬
‫ﺯﺩ‪ .‬ﭘﺲ ﺍﺯ ﺁﻥ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺁﻥ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﻣﻴﮕﺮﺩﻧﺪ‪:‬‬

‫ﭘﺎﺭﺍﻣﺘﺮ ‪ : CPLADDR‬ﺁﺩﺭﺱ ﺑﻴﺲ ﻛﺎﺭﺕ ‪ CP‬ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ‪.‬‬

‫ﭘﺎﺭﺍﻣﺘﺮ ‪ : RECV‬ﺁﺩﺭﺱ ﻭ ﻣﻘﺪﺍﺭ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﺑﺎﻳﺪ ﺫﺧﻴﺮﻩ ﺷﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺑﺮﺍﻱ ﺫﺧﻴﺮﻩ ﺳﺎﺯﻱ ‪١٠‬‬
‫ﺑﺎﻳﺖ ﺩﺭ ﺩﻳﺘﺎ ﺑﻼﻙ ﺷﻤﺎﺭﻩ ‪ ١٠‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Slave‬ﺑﺎ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ﺻﻔﺮ ﻣﻴﻨﻮﻳﺴﻴﻢ‪:‬‬
‫‪RECV :=P#DB10.DBX0.0 BYTE 10‬‬
‫ﻣﺎﻛﺰﻳﻤﻢ ﻣﻘﺪﺍﺭ ﺩﻳﺘﺎ ﻳﺮﺍﻱ ‪ Slave‬ﺑﺮﺍﺑﺮ ﺑﺎ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺍﺳﺖ‬
‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ‪ : NDR , ERROR ,STATUS‬ﺷﺒﻴﻪ ﺁﻧﭽﻪ ﺑﺮﺍﻱ ‪ DP_SEND‬ﮔﻔﺘﻪ ﺷﺪ ﻋﻤﻞ ﻣﻴﻜﻨﻨﺪ‪ NDR .‬ﺑﺮﺍﻱ‬
‫‪ RECV‬ﻣﺸﺎﺑﻪ ‪ DONE‬ﺑﺮﺍﻱ ‪ SEND‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﻳﻌﻨﻲ ﺍﮔﺮ ‪ 1‬ﺷﺪ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ ﻛﻪ ﺩﺭﻳﺎﻓﺖ ﺑﺪﻭﻥ ﺧﻄﺎ ﻛﺎﻣﻞ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫ﺩﺭ ﺣﺎﻟﺘﻲ ﻛﻪ ‪ ERROR‬ﻳﻚ ﺷﻮﺩ ‪ STATUS‬ﻛﺪﺧﻄﺎ ﺭﺍ ﻃﺒﻖ ﺟﺪﻭﻝ ﺻﻔﺤﻪ ﺑﻌﺪ ﺑﺮﻣﻴﮕﺮﺩﺍﻧﺪ‪.‬‬
‫ﭘﺎﺭﺍﻣﺘﺮ ‪ : DPSTATUS‬ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﻳﻚ ﺑﺎﻳﺖ ﺍﺳﺖ ﻛﻪ ﻭﺿﻌﻴﺖ ‪ DP‬ﺭﺍ ﻣﻄﺎﺑﻖ ﺟﺪﻭﻝ ﺯﻳﺮ ﺑﺮﻣﻴﮕﺮﺩﺍﻧﺪ‪:‬‬

‫‪Bit‬‬ ‫‪Meaning‬‬
‫‪7‬‬ ‫‪not used‬‬
‫‪6‬‬ ‫‪1: received data overflow‬‬
‫‪5,4‬‬ ‫‪Values for DP STATUS of the DP master:‬‬
‫‪00 RUN 01 CLEAR 10 STOP 11 OFFLINE‬‬
‫‪3‬‬ ‫‪1:Cyclic synchronization is active.‬‬
‫‪2‬‬ ‫‪0: no new diagnostic data exist‬‬
‫‪1: evaluation of diagnostic list useful; at least one station has new diagnostic‬‬
‫‪data‬‬
‫‪1‬‬ ‫‪0: all DP slaves in the data transfer phase‬‬
‫‪1: evaluation of the station list useful‬‬
‫‪0‬‬ ‫‪DP Mode‬‬
‫‪0: DP master mode‬‬
Techno-Electro.com

PROFIBUS-DP ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ١٢٤

Slave ‫ ﺩﺭ ﺳﻤﺖ‬DP_RECV ‫ﻓﺎﻧﻜﺸﻦ‬
‫ ﻣﻴﺒﺎﺷﺪ ﻓﻘﻂ ﻃﻮﻝ ﺁﺩﺭﺳﻲ ﻛﻪ‬Master ‫ ﺳﻤﺖ‬DP_RECV ‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻧﻴﺎﺯ ﺑﻪ ﺷﺮﺡ ﺍﺿﺎﻓﻲ ﻧﺪﺍﺭﺩ ﻭ ﻣﺸﺎﺑﻪ ﻓﺎﻧﻜﺸﻦ‬
.‫ ﺑﺎﻳﺖ ﺑﻴﺸﺘﺮ ﺑﺎﺷﺪ‬٨٦ ‫ ﻧﻮﺷﺘﻪ ﻣﻴﺸﻮﺩ ﻧﺒﺎﻳﺪ ﺍﺯ‬SEND ‫ﺩﺭ ﺟﻠﻮﻱ ﭘﺎﺭﺍﻣﺘﺮ‬
NDR ERROR STATUS MEANING
0 1 8183H No configuration or the DP service has not yet started on Profibus
0 1 8184H System error or bad parameter type.
0 1 8F22H Area length error reading a parameter (e.g. DB too short).
0 1 8F23H Area length error writing a parameter (e.g. DB too short).
0 1 8F24H Area error reading a parameter.
0 1 8F25H Area error writing a parameter.
0 1 8F28H Alignment error reading a parameter.
0 1 8F29H Alignment error writing a parameter.
0 1 8F30H Parameter is in the write-protected 1st act. data block.
0 1 8F31H Parameter is in the write-protected 2nd act. data block.
0 1 8F32H Parameter contains a DB number that is too high.
0 1 8F33H DB number error.
0 1 8F3AH Destination area not loaded (DB).
0 1 8F42H Timeout reading a parameter from the I/O area.
0 1 8F43H Timeout writing a parameter to the I/O area.
0 1 8F44H Address of the parameter to be read is disabled in the access track.
0 1 8F45H Address of the parameter to be read is disabled in the access track.
0 1 8F7FH Internal error, e.g. illegal ANY reference.
0 1 8090H No module with this address exists.
0 1 8091H Logical base address not at a double word boundary.
0 1 80A0H Negative acknowledgment writing to the module.
0 1 80B0H The module does not recognize the data record.
0 1 80B1H The specified data record length is incorrect.
0 1 80C0H The data record cannot be read.
0 1 80C1H The specified data record is currently being processed.
0 1 80C2H There are too many jobs pending.
0 1 80C3H Resources occupied (memory).
Communication error (occurs temporarily, it is usually best to repeat
0 1 80C4H
the job in the user program)
0 1 80D2H Logical base address incorrect.
Techno-Electro.com

١٢٥ PROFIBUS-DP ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬

Slave ‫ ﻭ‬Master ‫ ﺑﺮﺍﻱ‬OB1 ‫ ﺩﺍﺩﻩ ﺷﺪ ﺑﺮﻧﺎﻣﻪ‬DP_RECV ‫ ﻭ‬DP_SEND ‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﺩﺭ ﻣﻮﺭﺩ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ‬
٣ ‫ ﻧﻴﺰ ﺍﺳﺘﻔﺎﺩﻩ ﺷﺪﻩ ﻛﻪ ﻫﺮ‬FC29 ‫ ﺍﺯ ﻳﻚ‬Master ‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﺸﺨﺺ ﺍﺳﺖ ﺩﺭ ﺑﺮﻧﺎﻣﻪ‬. ‫ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‬
‫ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﺁﻭﺭﺩﻩ‬FC29 ‫ ﺑﺮﻧﺎﻣﻪ‬.‫ﺛﺎﻧﻴﻪ ﻳﻜﺒﺎﺭ ﻣﻘﺪﺍﺭ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﻗﺮﺍﺭ ﺍﺳﺖ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﺭﺍ ﺍﻓﺰﺍﻳﺶ ﻳﺎ ﻛﺎﻫﺶ ﻣﻴﺪﻫﺪ‬
.‫ﺷﺪﻩ ﺍﺳﺖ‬
OB1 in Master

CALL "DP_SEND
CPLADDR:=W#16#110
SEND :=P#DB11.DBX 0.0 BYTE 10
DONE :=M1.2
ERROR :=M1.3
STATUS :=MW206

CALL FC 29

CALL "DP_RECV"
CPLADDR :=W#16#110
RECV :=P#DB10.DBX 0.0 BYTE 10
NDR :=M1.0
ERROR :=M1.1
STATUS :=MW200
DPSTATUS:=MB202
BE

OB1 in Slave

CALL "DP_RECV"
CPLADDR :=W#16#110
RECV :=P#DB10.DBX 0.0 BYTE 10
NDR :=M1.0
ERROR :=M1.1
STATUS :=MW200
DPSTATUS:=MB202

L DB10.DBW 0
T DB11.DBW 0 // data for confirmation

CALL "DP_SEND"
CPLADDR:=W#16#110
SEND :=P#DB11.DBX 0.0 BYTE 10
DONE :=M1.2
ERROR :=M1.3
STATUS :=MW104
BE
Techno-Electro.com

PROFIBUS-DP ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻃﺎﺕ‬ ١٢٦

FC29 in Master

A T 4 // time downwards hoch: A M 40.3

JC runt L S5T#100MS
st_1: A M 40.1 //Start Timer 3 SE T 1
L S5T#3S // LED upwards 3 sec. A T 1
SE T 3 R M 40.3
A T 3 A T 1
R M 40.1 JC weit
JC hoch // Jump to upwards AN T 1
AN T 3 S M 40.3
S M 40.1 L MW 70
S M 40.2 L 0
runt: A M 40.2 //Start Timer 4 <>D
L S5T#3S // LED downwards 3 sec. JC los2
SE T 4 TAK
A T 4 + L#32768
R M 40.2 T MW 70
AN T 4 T DB11.DBW 0
S M 40.2 BEU
JC st_1 los2: L MW 70
A M 40.0 L 2
L S5T#100MS /D
SE T 1 T MW 70
A T 1 T DB11.DBW 0
R M 40.0 L 1
A T 1 <>D
JC weit BEC
AN T 1 L 0
S M 40.0 T MW 70
L MW 70 BE
L 0
<>D
JC los1
TAK
+ 1
T MW 70
T DB11.DBW 0
BEU
los1: L MW 70
L 2
*D
T MW 70
T DB11.DBW 0
L L#32768
<>D
BEC
L 0
T MW 70
weit: BEU
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﻫﺸﺘﻢ –ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫‪PROFIBUS‬‬
‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﻴﻦ ‪ PLC‬ﻫﺎﻱ ‪S7‬‬ ‫‪١-٨‬‬

‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﻴﻦ ‪ PLC‬ﻫﺎﻱ ‪ S7‬ﻭ‪S5‬‬ ‫‪٢-٨‬‬
‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ ‪Multiproject‬‬ ‫‪٣-٨‬‬
‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﺎ ‪Unknown Project‬‬ ‫‪٤-٨‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٢٨‬‬

‫ﻣﻘﺪﻣﻪ ‪:‬‬
‫‪ Profibus‬ﺗﺸﺮﻳﺢ ﺷﺪ‪,‬‬ ‫ﺩﺭ ﺑﺨﺶ ﻫﺎﻱ ﻗﺒﻞ ﺣﺎﻟﺖ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪ Master / Slave‬ﺩﺭ‬
‫ﻭﻟﻲ ‪ DP‬ﺗﻨﻬﺎ ﺳﺮﻭﻳﺲ ﺍﺭﺗﺒﺎﻃﻲ ﻧﻴﺴﺖ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ﺩﻳﮕﺮﻱ ﻧﻴﺰ ﺗﻮﺳﻂ ﺯﻳﻤﻨﺲ ﺑﺮﺍﻱ ‪ PROFIBUS‬ﺍﺭﺍﺋﻪ‬
‫ﺷﺪﻩ ﺍﺳﺖ ﺷﺎﻣﻞ‪:‬‬
‫ﺳﺮﻭﻳﺲ ‪FDL‬‬ ‫•‬

‫ﺳﺮﻭﻳﺲ ‪FMS‬‬ ‫•‬

‫‪S7 Function‬‬ ‫ﺳﺮﻭﻳﺲ‬ ‫•‬

‫ﺍﻳﻦ ﺳﺮﻭﻳﺴﻬﺎ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﭼﻨﺪ ‪ Master‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﻧﺪ ﻭ ﺍﺯ ﺭﻭﺵ ‪ Token Pass‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻨﺪ‪.‬‬
‫ﺩﺭ ﺭﻭﺵ ‪ Master/Slave‬ﺭﺍﺑﻄﻪ ﺭﺋﻴﺲ ﻭ ﻣﺮﺋﻮﺱ ﺑﺮﻗﺮﺍﺭ ﺑﻮﺩ ﻭﻫﻴﭽﮕﺎﻩ ﻣﺸﻜﻠﻲ ﺑﺮﺍﻱ ﻧﺤﻮﻩ ﺍﺭﺗﺒﺎﻁ ﻭﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ‬
‫ﺑﺎﺱ ﺍﺣﺴﺎﺱ ﻧﻤﻲ ﺷﺪ‪ .‬ﺯﻳﺮﺍ ﺩﺭ ﺁﻧﺠﺎ ﺍﻳﻦ ﺭﺋﻴﺲ )‪ (Master‬ﺑﻮﺩ ﻛﻪ ﻫﻤﻪ ﺍﺭﺗﺒﺎﻁ ﻫﺎ ﺭﺍ ﻣﺪﻳﺮﻳﺖ ﻣﻲ ﻛﺮﺩ ﻭﺗﻌﻴﻴﻦ ﻣﻲ ﻛﺮﺩ‬
‫ﻛﻪ ﭼﻪ ﻛﺴﻲ ﺑﺎﺱ ﺭﺍ ﺩﺭﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﺩ‪ .‬ﻭﻟﻲ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﭼﻨﺪﻳﻦ ‪ Master‬ﺩﻳﮕﺮ ﻧﻈﺎﻡ ﺭﺋﻴﺲ ﻭﻣﺮﺋﻮﺱ ﺑﺮﺍﻱ ﺩﺭ ﺍﺧﺘﻴﺎﺭ‬
‫ﮔﺮﻓﺘﻦ ﺑﺎﺱ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﻣﮕﺮ ﺍﻳﻨﻜﻪ ﺍﺯ ﻃﺮﻳﻖ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ﺷﻴﻮﻩ ‪ Token Pass‬ﺭﺍ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻧﻤﺎﻳﻴﻢ‪ .‬ﺍﻟﺒﺘﻪ‬
‫ﺍﺯ ﻃﺮﻳﻖ ﺗﻮﺍﺑﻌﻲ ﻛﻪ ﺳﻴﺴﺘﻢ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻛﺎﺭﺑﺮ ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﺪ‪،‬ﻧﻴﺎﺯﻱ ﻧﻴﺴﺖ ﻛﻪ ﺑﻪ ﻃﻮﺭ ﻛﺎﻣﻞ ﺩﺭ ﺟﺮﻳﺎﻥ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺷﻴﻮﻩ‬
‫‪ Token Pass‬ﻗﺮﺍﺭ ﮔﻴﺮﻳﻢ‪ STEP 7 .‬ﺧﻮﺩﺵ ﺣﻠﻘﻪ ‪ Token‬ﺭﺍ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻭﻣﺪﻳﺮﻳﺖ ﻣﻲ ﻛﻨﺪ ﻭ ﻛﺎﻓﻲ ﺍﺳﺖ ﻛﻪ‬
‫ﻛﺎﺭﺑﺮ ﺗﻮﺍﺑﻊ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺭﺍ ﺑﻪ ﻧﺤﻮ ﺻﺤﻴﺢ ﺻﺪﺍ ﺑﺰﻧﺪ ﻭﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻫﺎﻳﺶ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﺩﻫﺪ‪.‬‬
‫ﺩﺭ ﻳﻚ ﻧﮕﺎﻩ ﻛﻠﻲ ﺑﻪ ﺳﺮﻭﻳﺴﻬﺎﻱ ﻓﻮﻕ ﻣﻴﺘﻮﺍﻥ ﮔﻔﺖ‪:‬‬
‫• ﺳﺮﻭﻳﺲ ‪ FDL‬ﺍﺯ ﻻﻳﻪ ‪ ٢‬ﻣﺪﻝ ‪ OSI‬ﭘﻴﺮﻭﻱ ﻣﻴﻜﻨﺪ‪.‬ﺑﺎ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﺧﺎﺹ ﺗﺎ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺭﺍ ﺟﺎﺑﺠﺎ ﻣﻴﻜﻨﺪ‪.‬‬
‫• ﺳﺮﻭﻳﺲ‪ FMS‬ﺍﺯ ﻻﻳﻪ ‪ ٧‬ﻣﺪﻝ ‪ OSI‬ﭘﻴﺮﻭﻱ ﻣﻴﻜﻨﺪ ‪ .‬ﺑﺎ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﺧﺎﺹ ﺣﺠﻢ ﺩﻳﺘﺎﻱ ﺑﻴﺸﺘﺮﻱ ﺭﺍ ﻣﻴﺘﻮﺍﻧﺪ ﺟﺎﺑﺠﺎ ﻛﻨﺪ‪.‬‬
‫• ﺳﺮﻭﻳﺲ ‪ S7 Function‬ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﺳﻴﺴﺘﻢ ﺗﺎ ‪ ٦٤‬ﺑﺎﻳﺖ ﺭﺍ ﺟﺎﺑﺠﺎ ﻣﻴﻜﻨﺪ‪.‬‬

‫• ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺭ ﺍﻳﻦ ﺳﺮﻭﻳﺴﻬﺎ ﻻﺯﻡ ﺍﺳﺖ ﻛﺎﺭﺕ ‪ CP‬ﺧﺎﺹ ﺩﺭ ‪ PLC‬ﻧﺼﺐ ﺷﻮﺩ‪.‬‬
‫• ﺭﻭﻱ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﻓﻮﻕ ﺑﻄﻮﺭ ﻫﻤﺰﻣﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺩﺭ ﺟﺪﻭﻝ ﺻﻔﺤﻪ ﺑﻌﺪ‬
‫ﺳﺮﻭﻳﺴﻬﺎﻱ ﻣﻤﻜﻦ ﺑﺮﺍﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺍﺭﺍﺋﻪ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫ﺳﺮﻭﻳﺲ ‪ FDL‬ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ ﻭ ﺩﻭ ﺳﺮﻭﻳﺲ ﺩﻳﮕﺮ ﺩﺭ ﺑﺨﺸﻬﺎﻱ ﺑﻌﺪﻱ ﻣﻮﺭﺩ ﺑﺤﺚ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﻧﺪ‪.‬‬
Techno-Electro.com

١٢٩ PROFIBUS ‫ ﺩﺭ‬FDL ‫ﺍﺭﺗﺒﺎﻁ‬

System Modules Services

S5 95U CPU 95U FDL, DP (M or S)

S5115/135/155U CP 5431 FMS, FDL, DP (M)

IM 308-B/C DP (M or S)

S7-200 CPU 215 DP (S)

S7-300 CPU 315-2 DP DP (M or S)

CP 342-5 S7 functions, FDL, DP (M or S)

CP 343-5 S7 functions, FDL, FMS

S7-400 CPU 413-2 DP DP (M)

CPU 414-2 DP DP (M)

CPU 416-2 DP DP (M)

IM 467 DP (M or S), (M and S)

CP 443-5 Basic S7 functions, FDL, FMS

CP 443-5 S7 functions, FDL, DP (M or S)

Extended
M7-300/400 IFM submodule S7 functions, DP (M or S)

C7 CPU 626-DP DP

OP OP 5, OP 7, OP S7 functions
15,
OP 17; OP 25, OP S7 functions
35,
OP 37 S7 functions

PC/PG CP 5613 S7 functions, FDL, FMS

CP 5614 S7 functions, FDL, FMS

M = Master S = Slave

‫ ﻭ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺁﻧﻬﺎ‬Profibus ‫ﻛﺎﺭﺗﻬﺎﻱ ﺷﺒﻜﻪ‬

‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٣٠‬‬

‫‪ ١-٨‬ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﻴﻦ ‪ PLC‬ﻫﺎﻱ ‪S7‬‬

‫ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﺎﻳﺪ ﺍﺯ ﻳﻚ ‪ CP‬ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﺎﻳﻴﻢ ﻛﻪ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺭﺍ ﭘﺸﺘﻴﺒﺎﻧﻲ ﻛﻨﺪ‪ .‬ﺩﺭ ﻣﺸﺨﺼﺎﺕ ﺍﻳﻦ ‪ CP‬ﺑﺎﻳﺪ‬
‫ﻼ ‪ CP 342-5‬ﺍﻳﻦ ﻭﻳﮋﮔﻲ ﺭﺍ ﺩﺍﺭﺍﺳﺖ‪.‬‬
‫ﻣﺸﺨﺼﻪ ‪ SEND/RECEIVE Interface‬ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬ﻣﺜ ﹰ‬

‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺍﻳﻦ ﻛﺎﺭﺕ ﮔﺎﻣﻬﺎﻳﻲ ﻛﻪ ﺑﻪ ﺗﺮﺗﻴﺐ ﺑﺎﻳﺪ ﺑﺮﺩﺍﺷﺘﻪ ﺷﻮﺩ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫ﮔﺎﻡ ﺍﻭﻝ‪:‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺑﺎ ﻛﺎﺭﺕ ‪CP‬‬
‫ﺍﺑﺘﺪﺍ ﭼﻨﺪﻳﻦ ‪ Station 300,400‬ﺑﺎ ‪ CP‬ﻣﻨﺎﺳﺐ ﺍﻳﺠﺎﺩ ﻧﻤﻮﺩﻩ ﺳﭙﺲ ﺑﺎ ﺗﻨﻈﻴﻢ ﻣﺪ ﻛﺎﺭﻱ ﻛﺎﺭﺕ ‪ CP‬ﻫﻤﻪ ﺍﻳﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ‬
‫ﺭﺍ ﺩﺭ ﻣﺪ ‪ Master‬ﭘﻴﻜﺮﺑﻨﺪﻱ ﻣﻴﻨﻤﺎﻳﻴﻢ‪.‬ﻧﺘﻴﺠﻪ ﺍﻳﻦ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺭﺍ ﻣﻲ ﺗﻮﺍﻥ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ NetPro‬ﻧﻴﺰ ﻣﺸﺎﻫﺪﻩ ﻛﺮﺩ‪ .‬ﺗﻮﺟﻪ‬
‫ﺷﻮﺩ ﻛﻪ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺍﮔﺮ ‪ CPU‬ﺩﺍﺭﺍﻱ ﭘﻮﺭﺕ ‪ DP‬ﺑﺎﺷﺪ ﻭ ﺑﻪ ﻫﻤﻴﻦ ﺷﺒﻜﻪ ﻧﻴﺰ ﻣﺘﺼﻞ ﺷﻮﺩ ﺍﺷﻜﺎﻟﻲ ﻧﺪﺍﺭﺩ‪ .‬ﺯﻳﺮﺍ ﺍﺭﺗﺒﺎﻁ‬
‫‪ FDL‬ﻣﻴﺘﻮﺍﻧﺪ ﻫﻤﺰﻣﺎﻥ ﺑﺎ ‪ DP‬ﺭﻭﻱ ﻳﻚ ﺷﺒﻜﻪ ﺑﻜﺎﺭ ﺭﻭﺩ ﺍﮔﺮﭼﻪ ﺍﻳﻨﺪﻭ ﻣﺴﺘﻘﻞ ﻋﻤﻞ ﻣﻴﻜﻨﻨﺪ ﻭ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﺗﺪﺍﺧﻞ‬
‫ﻧﺪﺍﺭﻧﺪ‪.‬‬

‫ﮔﺎﻡ ﺩﻭﻡ‪ :‬ﺗﺸﻜﻴﻞ ‪Connection Table‬‬

‫ﺟﺪﻭﻝ ﺍﺗﺼﺎﻻﺕ ﻳﺎ ‪ Connection Table‬ﺍﻣﻜﺎﻥ ﺍﺗﺼﺎﻝ ﭼﻨﺪ ‪ Master‬ﺭﺍ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ‪ Token Pass‬ﻓﺮﺍﻫﻢ‬
‫ﻣﻴﺴﺎﺯﺩ‪ .‬ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ DP‬ﺣﺘﻲ ﺩﺭ ﻣﻮﺍﺭﺩﻱ ﻛﻪ ﺍﺯ ﻛﺎﺭﺕ ‪ CP‬ﻭ ﻓﺎﻧﻜﺸﻦ ﺟﻬﺖ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﺪ ﻧﻴﺎﺯﻱ ﺑﻪ ﺍﻳﺠﺎﺩ‬
‫ﺍﻳﻦ ﺟﺪﻭﻝ ﻧﺒﻮﺩ ﻭﻟﻲ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﻭ ‪ FMS‬ﻭﺟﻮﺩ ﺍﻳﻦ ﺟﺪﻭﻝ ﺿﺮﻭﺭﻱ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٣١‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﺟﺪﻭﻝ ﻣﺰﺑﻮﺭ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ NetPro‬ﺩﺭ ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ‪ Station‬ﻫﺎ ﺍﮔﺮ ﺑﺮ ﺭﻭﻱ ﻗﺴﻤﺖ ‪ CPU‬ﻳﻜﺒﺎﺭ ﻛﻠﻴﻚ ﻛﻨﻴﻢ‬
‫‪ Connection Table‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ‪:‬‬

‫ﺗﻮﺟﻪ ﺷﻮﺩ ﺭﻭﻱ ﻫﺮ ‪ CPU‬ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﻳﻚ ﺟﺪﻭﻝ ﺟﺪﺍﮔﺎﻧﻪ ﺑﺮﺍﻱ ﺁﻥ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ‪ .‬ﺗﻮﺳﻂ ﺍﻳﻦ ﺟﺪﻭﻝ ﻣﻴﺘﻮﺍﻥ‬
‫ﺍﺭﺗﺒﺎﻃﺎﺕ ﻫﺮ ‪ CPU‬ﺭﺍﻣﺸﺎﻫﺪﻩ ﻭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻧﻤﻮﺩ‪.‬‬

‫ﮔﺎﻡ ﺳﻮﻡ‪ :‬ﺍﻳﺠﺎﺩ ﺍﺭﺗﺒﺎﻁ ﺩﺭ ‪Connection Table‬‬

‫ﺩﺭ ﺟﺪﻭﻝ ﻓﻮﻕ ﺑﺮ ﺭﻭﻱ ﻳﻜﻲ ﺍﺯ ﺳﻄﺮ ﻫﺎ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻧﻤﻮﺩﻩ ﮔﺰﻳﻨﻪ ‪ Insert New Connection‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻛﻨﻴﺪ‪ .‬ﺩﺭ‬
‫ﺍﻳﻦ ﺣﺎﻟﺖ ﭘﻨﺠﺮﻩ ‪ Insert New Connection‬ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٣٢‬‬

‫ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﻟﻴﺴﺖ ‪ Master‬ﻫﺎﻳﻲ ﻛﻪ ﻣﻴﺘﻮﺍﻧﻨﺪ ﺑﺎ ﺍﻳﻦ ‪ CPU‬ﺍﺭﺗﺒﺎﻁ ﺑﮕﻴﺮﻧﺪ ﻗﺎﺑﻞ ﻣﺸﺎﻫﺪﻩ ﺍﺳﺖ ‪ .‬ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﺟﺪﻭﻝ‬
‫‪ Connection‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ CPU315‬ﻣﻲ ﺑﺎﺷﺪ ﺍﺯ ﺍﻳﻨﺮﻭ ﺩﺭ ﭘﻨﺠﺮﻩ ﻣﺰﺑﻮﺭ ﻣﻴﺘﻮﺍﻥ ﺩﻭ ‪ CPU‬ﺩﻳﮕﺮ ﻳﻌﻨﻲ ‪ CPU314‬ﻭ‬
‫‪ CPU 412-1‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻭ ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩ‪ .‬ﺑﻪ ﻫﺮ ﺣﺎﻝ ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﻓﻘﻂ ﻳﻚ ﻣﻮﺭﺩ ﻗﺎﺑﻞ ﺍﻧﺘﺨﺎﺏ ﺍﺳﺖ‪.‬‬
‫ﻧﻜﺘﻪ ﺩﻳﮕﺮ ﺍﻳﻨﻜﻪ ﺩﺭ ﭘﺎﻳﻴﻦ ﭘﻨﺠﺮﻩ ﻓﻮﻕ ﺑﺎﻳﺪ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺍﺯ ﻟﻴﺴﺖ ‪ ، Type‬ﮔﺰﻳﻨﻪ ‪ FDL Connection‬ﺍﻧﺘﺨﺎﺏ ﮔﺮﺩﺩ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﻣﻮﺍﺭﺩ ﻓﻮﻕ ﻭ ‪ OK‬ﻛﺮﺩﻥ ﭘﻨﺠﺮﻩ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Property‬ﻫﺎﻱ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ)ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ (‬
‫‪ STEP7‬ﺑﻪ ﺻﻮﺭﺕ ﺧﻮﺩﻛﺎﺭ ﺑﻪ ﺍﻳﻦ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ﻳﻚ ‪ ID‬ﺗﺨﺼﻴﺺ ﻣﻲ ﺩﻫﺪ‪ .‬ﺍﻳﻦ ‪ ID‬ﺩﺭ ﺷﻜﻞ ﻣﻘﺪﺍﺭ ‪ 1‬ﺩﺍﺭﺩ‪.‬‬
‫ﻫﻤﭽﻨﻴﻦ ﻳﻚ ﻧﺎﻡ ﻫﻢ ﺑﻪ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﺩﻛﻪ ﺩﺭ ﻗﺴﻤﺖ ‪ Name‬ﻣﻴﺘﻮﺍﻥ ﺁﻧﺮﺍ ﺩﻳﺪ‪.‬ﺍﮔﺮ ﺩﺭﺍﻳﻦ ‪Station‬ﭼﻨﺪﻳﻦ‬
‫‪ CP‬ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺩﺭ ﻗﺴﻤﺖ ‪ Via CP‬ﺑﺎﻳﺪ ﻣﺸﺨﺺ ﻛﻨﻴﻢ ﻛﻪ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺍﺯ ﻃﺮﻳﻖ ﻛﺪﺍﻡ ‪ CP‬ﺑﺮﻗﺮﺍﺭ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﻫﻤﭽﻨﻴﻦ ﻳﻚ ﭘﺎﺭﺍﻣﺘﺮ ﺩﻳﮕﺮ ﺑﻪ ﻧﺎﻡ ‪ LADDR‬ﺑﻪ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺗﺨﺼﻴﺺ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺩﺭ ﻭﺍﻗﻊ ﺍﻳﻦ ﺁﺩﺭﺱ ‪ ،‬ﺁﺩﺭﺱ‬
‫ﺷﺮﻭﻉ ﻣﺪﻭﻝ ‪ CP‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺯﻣﺎﻥ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ‪،‬ﻳﻌﻨﻲ ﺯﻣﺎﻧﻲ ﻛﻪ ‪ CP‬ﺭﺍ ﺩﺭ ‪ Rack‬ﻗﺮﺍﺭ ﺩﺍﺩﻩ ﺍﻳﺪ‪،‬ﺑﻪ ﺁﻥ‬
‫ﻧﺴﺒﺖ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬ﺩﻭﭘﺎﺭﺍﻣﺘﺮ ‪ ID‬ﻭ‪ LADDR‬ﺑﻌﺪﹰﺍ ﺩﺭ ﻗﺴﻤﺖ ﻣﺮﺑﻮﻁ ﺑﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺑﻪ ﻛﺎﺭ ﻣﻲ ﺁﻳﻨﺪ ﻛﻪ‬
‫ﺩﺭ ﺍﺩﺍﻣﻪ ﻧﺤﻮﻩ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺁﻧﻬﺎ ﻭﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺧﻮﺍﻫﺪ ﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٣٣‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﭘﺲ ﺍﺯ ﺍﻧﺠﺎﻡ ﻣﺮﺍﺣﻞ ﻓﻮﻕ ﻳﻚ ﺳﻄﺮ ﺩﺭ ﺟﺪﻭﻝ‪ Connection Table‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﻛﻪ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ﺑﺎ‬
‫‪ ID‬ﻭ ‪ LADDR‬ﻣﻌﻴﻦ ﺑﻴﻦ ﺍﻳﻦ ‪ CPU‬ﻭ ‪ CPU‬ﻣﻮﺭﺩ ﻧﻈﺮ )ﻛﻪ ﺩﺭ ﺍﻳﻦ ﻣﺜﺎﻝ ‪ (CPU412-1‬ﺑﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﺑﺎ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺧﻮﺍﻫﻴﻢ ﺩﻳﺪ ﻣﻴﺘﻮﺍﻥ ﺗﻮﺳﻂ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﺧﺎﺹ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺗﺎ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺭﺍ ﺍﺯ‬
‫‪ CPU315‬ﺑﻪ ‪ CPU412‬ﺍﺭﺳﺎﻝ ﻛﺮﺩ ﻳﺎ ﺍﺯ ﺁﻥ ﺩﺭﻳﺎﻓﺖ ﻧﻤﻮﺩ‪ .‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﻛﺮﺩ ﺑﺪﻭﻥ ﺍﻳﺠﺎﺩ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﻧﻤﻴﺘﻮﺍﻥ ﺻﺮﻓﺎ ﺑﺎ‬
‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻭ ﻓﺮﺍﺧﻮﺍﻧﻲ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ‪ SEND‬ﻭ ‪ RECV‬ﺑﻪ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﭘﺮﺩﺍﺧﺖ‪ .‬ﺍﻳﻦ ﻳﻚ ﺗﻔﺎﻭﺕ ﻣﻬﻢ ﺑﻴﻦ ‪ FDL‬ﺑﺎ‬
‫ﺑﺎ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺁﻥ ﺩﺭ ﺑﺨﺶ ﻗﺒﻞ ﺁﺷﻨﺎ ﺷﺪﻳﺪ ‪.‬‬ ‫‪ DP‬ﺍﺳﺖ ﻛﻪ‬
‫‪CPU‬‬ ‫ﺍﮔﺮ ﺭﻭﻱ ﺳﻄﺮ ﺩﻭﻡ ﺟﺪﻭﻝ ‪ Connection‬ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﻣﺠﺪﺩﹰﺍ ﻣﻴﺘﻮﺍﻧﻴﻢ ﺍﺭﺗﺒﺎﻁ ﺟﺪﻳﺪﻱ ﺑﺎﺯ ﺑﺎ ﻫﻤﺎﻥ‬
‫ﻗﺒﻠﻲ ﻳﺎ ﺑﺎ ‪ CPU‬ﺩﻳﮕﺮﻱ ﺍﻳﺠﺎﺩ ﻛﻨﻴﻢ ‪ .‬ﺍﺭﺗﺒﺎﻃﻲ ﻛﻪ ﺑﺎ ﺁﻥ ﻣﻴﺘﻮﺍﻥ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺩﻳﮕﺮ ﺭﺍ ﺗﺒﺎﺩﻝ ﻧﻤﻮﺩ‪ .‬ﺍﻳﻦ ﺍﺗﺼﺎﻻﺕ ﺟﺪﻳﺪ‬
‫ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮﺩﺍﺭﺍﻱ ‪ ID‬ﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺧﻮﺍﻫﻨﺪ ﺑﻮﺩ‪.‬‬
‫ﺩﺭ ﺳﻤﺖ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﮔﻴﺮﻧﺪﻩ ﻧﻴﺰ ﭼﻨﻴﻦ ﺟﺪﻭﻟﻲ ﺭﺍ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺷﺖ‬

‫ﺑﺮﺍﻱ ﺗﻐﻴﻴﺮ ﺗﻨﻈﻴﻤﺎﺕ ﻗﺒﻠﻲ ﻛﺎﻓﻴﺴﺖ ﺭﻭﻱ ﺳﻄﺮ ﻣﻮﺭﺩ ﻧﻈﺮ ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﺗﺎ ﭘﻨﺠﺮﻩ ‪ Properties‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﭘﺎﻳﻴﻦ‬
‫ﺻﻔﺤﻪ ﻗﺒﻞ ﺑﺎﺯ ﺷﻮﺩ‪ .‬ﺩﺭ ﻋﻤﻞ ﺗﻐﻴﻴﺮﻱ ﻻﺯﻡ ﻧﻴﺴﺖ ﺩﺭ ﺗﻨﻈﻴﻤﺎﺕ ﭘﻴﺶ ﻓﺮﺽ ﺑﺪﻫﻴﻢ‪ .‬ﻓﻘﻂ ﻻﺯﻡ ﺍﺳﺖ ﻣﻘﺎﺩﻳﺮ ‪ ID‬ﻭ‬
‫‪ LADDR‬ﺭﺍ ﻳﺎﺩﺩﺍﺷﺖ ﻛﻨﻴﻢ ﺗﺎ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺑﻜﺎﺭ ﺑﺒﺮﻳﻢ‪.‬‬
‫ﻼ ﺩﺭ ﺑﺨﺶ ‪Address‬‬
‫ﻧﻤﺎﻳﺶ ﻣﻴﺪﻫﻨﺪ‪ .‬ﻣﺜ ﹰ‬ ‫ﺑﺨﺸﻬﺎﻱ ﺩﻳﮕﺮ ﭘﻨﺠﺮﻩ ‪ Properties‬ﺍﻃﻼﻋﺎﺕ ﺩﻳﮕﺮﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﺭﺗﺒﺎﻁ ﺭﺍ‬
‫ﻣﻴﺘﻮﺍﻥ ﺁﺩﺭﺱ ‪ Node‬ﻫﺎﻱ ﺩﻭ ﺍﻳﺴﺘﮕﺎﻩ ﺭﺍ ﻫﻤﺮﺍﻩ ﺑﺎ ‪ LSAP‬ﻣﺸﺎﻫﺪﻩ ﻧﻤﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٣٤‬‬

‫ﻛﻪ ﺍﺻﻄﻼﺣﹰﺎ ‪Specified Station‬‬ ‫ﺁﻧﭽﻪ ﺗﺎﻛﻨﻮﻥ ﺫﻛﺮ ﺷﺪ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺑﺎ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺸﺨﺺ ﺩﻳﮕﺮ ﺑﻮﺩ‬
‫ﻧﺎﻣﻴﺪﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺷﻜﻞ ﻛﻠﻲ ﺍﻳﻦ ﻧﻮﻉ ﺍﺭﺗﺒﺎﻁ ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺍﺳﺖ‪:‬‬

‫ﻋﻼﻭﻩ ﺑﺮ ﺍﻳﻦ ﻧﻮﻉ ﺍﺭﺗﺒﺎﻁ ﺍﻧﻮﺍﻉ ﺩﻳﮕﺮﻱ ﻧﻴﺰ ﺩﺭ ﭘﻨﺠﺮﻩ ‪ New Connection‬ﻣﺸﺎﻫﺪﻩ ﻣﻴﺸﻮﻧﺪ ﻛﻪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬

‫‪Unspecified Station‬‬
‫‪Remote‬‬ ‫ﻼ ﻳﻚ ﻧﻮﺩ‬
‫ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻘﺎﺑﻞ ﻛﻪ ﻗﺮﺍﺭ ﺍﺳﺖ ﺑﺎ ﺁﻥ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﺷﻮﺩ ﺩﺭ ﻟﻴﺴﺖ ﻇﺎﻫﺮ ﻧﻤﻴﺸﻮﺩ ‪ .‬ﻣﺜ ﹰ‬
‫ﺍﺳﺖ ﻛﻪ ﻓﻘﻂ ﺁﺩﺭﺱ ‪ Node‬ﺁﻥ ﻣﻌﻠﻮﻡ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺎﻳﺪ ﺁﺩﺭﺱ ﻣﺰﺑﻮﺭ ﺭﺍ ﺩﺭ ﺯﻳﺮ ‪ Remote‬ﺍﺯ ﺑﺨﺶ ﺁﺩﺭﺱ‬
‫ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﻭﺍﺭﺩ ﻛﺮﺩ‪ .‬ﺍﻳﻦ ﺁﺩﺭﺱ ﺩﺭ ﺣﺎﻟﺖ ﻗﺒﻞ ﻏﻴﺮ ﻓﻌﺎﻝ ﺑﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٣٥‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﺷﻜﻞ ﻛﻠﻲ ﺍﺭﺗﺒﺎﻁ ‪ Unspecified‬ﺑﺼﻮﺭﺕ ﺯﻳﺮ ﺍﺳﺖ‪ .‬ﺩﺭ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﻣﺎﻛﺰﻳﻤﻢ ‪ ٢٣٦‬ﺑﺎﻳﺖ ﻣﻴﺘﻮﺍﻥ ﺍﺭﺳﺎﻝ ﻛﺮﺩ ﻳﻌﻨﻲ ‪٤‬‬
‫ﺑﺎﻳﺖ ﻛﻤﺘﺮ ﺍﺯ ﻧﻮﻉ ‪ .Specified‬ﺩﺭ ﻭﺍﻗﻊ ﺍﻳﻦ ‪ ٤‬ﺑﺎﻳﺖ ﺑﺮﺍﻱ ﺍﻃﻼﻋﺎﺕ ﺍﺿﺎﻓﻲ ‪ Job header‬ﻛﻪ ﺁﺩﺭﺱ ‪ Local‬ﺭﺍ‬
‫ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ﺭﺯﺭﻭ ﻣﻴﮕﺮﺩﺩ‪.‬‬

‫‪Broadcast Stations‬‬
‫ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺩﻳﺘﺎ ﺍﺯ ﻓﺮﺳﺘﻨﺪﻩ ﻫﻤﺰﻣﺎﻥ ﺑﻪ ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻳﻲ ﻛﻪ ﺭﻭﻱ ﺑﺎﺱ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ ﺍﻳﻦ ﺳﺮﻭﻳﺲ‬
‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻴﺪﺍﻧﻴﻢ ‪ SDN‬ﺍﺳﺖ ﻳﻌﻨﻲ ﺗﺎﻳﻴﺪﻳﻪ ﺩﺭﻳﺎﻓﺖ ﺍﺯ ﮔﻴﺮﻧﺪﻩ ﺑﻪ ﻓﺮﺳﺘﻨﺪﻩ ﺍﺭﺳﺎﻝ ﻧﻤﻴﺸﻮﺩ‪.‬‬

‫ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﺩﻳﺘﺎ ﻣﺎﻛﺰﻳﻤﻢ ‪ ٢٣٦‬ﺑﺎﻳﺖ ﺍﺳﺖ‪ .‬ﺁﺩﺭﺱ ﻧﻮﺩﻫﺎﻱ ﮔﻴﺮﻧﺪﻩ ﻭ ‪ LSAP‬ﺁﻧﻬﺎ ﻧﻴﺰ ﺩﺭ ﭘﻨﺠﺮﻩ ﻏﻴﺮ ﻓﻌﺎﻝ ﺍﺳﺖ‪.‬‬
‫ﺗﻮﺟﻪ ﺷﻮﺩ ﻛﻪ ﺩﺭ ‪ Connection Table‬ﻓﻘﻂ ﻳﻚ ﺍﺭﺗﺒﺎﻁ ‪ Broadcast‬ﺑﺮﺍﻱ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻴﺘﻮﺍﻧﻴﻢ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬‬

‫‪Properties‬‬ ‫ﻧﻜﺘﻪ ﺩﻳﮕﺮﻱ ﻛﻪ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ Broadcast‬ﺑﺎﻳﺪ ﺑﻪ ﺁﻥ ﺗﻮﺟﻪ ﻛﺮﺩﺍﻳﻨﺴﺖ ﻛﻪ ﺩﺭ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٣٦‬‬

‫ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺩﺭ ﺑﺨﺶ ‪ Network Setting‬ﺍﻧﺘﺨﺎﺑﻲ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺑﻄﻮﺭ ﭘﻴﺶ ﻓﺮﺽ ﻏﻴﺮ‬
‫ﻓﻌﺎﻝ ﺍﺳﺖ‪.‬ﺍﮔﺮ ﻓﻌﺎﻝ ﺷﻮﺩ ﻣﺮﺗﺒﺎ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﺩﺭ ﻫﺮ ﺳﻴﻜﻞ ﺑﺼﻮﺭﺕ ‪ Broadcast‬ﺑﻪ ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺍﺭﺳﺎﻝ‬
‫ﻣﻴﮕﺮﺩﺩ‪ .‬ﺑﺮﺍﻱ ﺟﻠﻮﮔﻴﺮﻱ ﺍﺯ ﺍﻳﺠﺎﺩ ﺗﺪﺍﺧﻞ ﺑﻴﻦ ﺍﻳﻦ ﺑﺴﺘﻪ ﻫﺎ ﻭ ﺑﺴﺘﻪ ﻫﺎﻳﻲ ﻛﻪ ﺗﻮﺳﻂ ‪ Connection Table‬ﺑﺼﻮﺭﺕ‬
‫‪ Broadcast‬ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﻧﺪ ﺑﻬﺘﺮ ﺍﺳﺖ ﮔﺰﻳﻨﻪ ﻓﻮﻕ ﻓﻌﺎﻝ ﻧﺸﻮﺩ ﻳﺎ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﺑﺴﺘﻪ ﻫﺎﻳﻲ ﺑﺎ ‪ LSAP > 56‬ﺭﺍ ﺩﺭ ﻧﻈﺮ‬
‫ﻧﮕﻴﺮﺩ‪.‬‬

‫‪Multicast Stations‬‬
‫ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺩﻳﺘﺎ ﺍﺯ ﻓﺮﺳﺘﻨﺪﻩ ﻫﻤﺰﻣﺎﻥ ﺑﻪ ﮔﺮﻭﻫﻲ ﺍﺯ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻛﻪ ﺭﻭﻱ ﺑﺎﺱ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﻧﻴﺰ‬
‫ﺑﺼﻮﺭﺕ ‪ SDN‬ﺍﺳﺖ ‪.‬ﻣﻘﺪﺍﺭ ﺩﻳﺘﺎ ‪ ٢٣٦‬ﺑﺎﻳﺖ ﺍﺳﺖ ‪ .‬ﺑﺮﺍﻱ ﻣﺸﺨﺺ ﻛﺮﺩﻥ ﮔﺮﻭﻩ ‪ Multicast‬ﻻﺯﻡ ﺍﺳﺖ ﺁﺩﺭﺱ‬
‫‪ LSAP‬ﺑﺮﺍﻱ ‪ Local‬ﻭ ﺗﻤﺎﻡ ‪ Remote‬ﻫﺎ ﻫﻤﮕﻲ ﻳﻜﺴﺎﻥ ﺑﺎﺷﺪ ﻣﺜﻼﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﺍﻳﻦ ﺁﺩﺭﺱ ﺑﺮﺍﻱ ﺗﻤﺎﻡ ﺍﻋﻀﺎﻱ‬
‫ﮔﺮﻭﻩ ﺑﺎﻳﺪ ‪ 21‬ﺑﺎﺷﺪ‪ .‬ﺑﻪ ﻋﺒﺎﺭﺕ ﺩﻳﮕﺮ ﺑﺮﺍﻱ ﻳﻜﺎﻳﻚ ‪ CPU‬ﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﻳﻚ ﺍﺭﺗﺒﺎﻁ ‪ Multicast‬ﺗﻌﺮﻳﻒ ﻛﺮﺩﻩ ﻭ‬
‫ﺁﺩﺭﺱ ﻫﻤﻪ ﺁﻧﻬﺎ ﺭﺍ ‪ 21‬ﺍﻧﺘﺨﺎﺏ ﻣﻴﻜﻨﻴﻢ‪.‬‬

‫ﺩﺭ ﭘﻨﺠﺮﻩ ﻓﻮﻕ ﺁﺩﺭﺱ ﺑﺮﺍﻱ ‪ Local‬ﻣﻴﺘﻮﺍﻧﺪ ‪ ١‬ﺗﺎ ‪ ٥٦‬ﺑﺎﺷﺪ‪ .‬ﻫﺮ ﺁﺩﺭﺳﻲ ﺑﺮﺍﻱ ‪ Local‬ﺍﻧﺘﺨﺎﺏ ﺷﻮﺩ ﻣﻴﺒﻴﻨﻴﻢ ﻛﻪ ﺑﻄﻮﺭ‬
‫ﺍﺗﻮﻣﺎﺗﻴﻚ ﺁﺩﺭﺱ ‪ Remote‬ﻧﻴﺰ ﻫﻤﺎﻥ ﻣﻘﺪﺍﺭ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٣٧‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﺗﺎ ﺍﻳﻦ ﻣﺮﺣﻠﻪ ﮔﺎﻣﻬﺎﻳﻲ ﻛﻪ ﺑﺮﺩﺍﺷﺘﻪ ﺷﺪ ﺑﺮﺍﻱ ﺗﻌﻴﻴﻦ ﺍﺗﺼﺎﻻﺕ ﺩﺭ ﺟﺪﻭﻝ ‪ Connection Table‬ﺑﻮﺩ ‪ .‬ﭘﺲ ﺍﺯ ﺍﺗﻤﺎﻡ ﻛﺎﺭ‬
‫ﻻﺯﻡ ﺍﺳﺖ‪:‬‬
‫ﭼﻚ ﺳﺎﺯﮔﺎﺭﻱ ﺍﺯ ﻣﻨﻮﻱ ‪ Network‬ﺩﺭ ‪ Netpro‬ﺍﺟﺮﺍ ﺷﺪﻩ ﻭ ‪ Error‬ﻫﺎﻱ ﺍﺣﺘﻤﺎﻟﻲ ﺭﻓﻊ ﺷﻮﻧﺪ‪.‬‬ ‫•‬
‫ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ﺟﺪﺍﻭﻝ ‪ Connection‬ﺑﻪ ‪ CPU‬ﻣﺮﺑﻮﻃﻪ ‪ Download‬ﺷﻮﻧﺪ‪.‬‬ ‫•‬

‫ﺗﺬﻛﺮ ‪:‬‬
‫ﺍﮔﺮ ﺑﻌﺪ ﺍﺯ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ Connection Table‬ﺩﺭ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺗﻐﻴﻴﺮ ﺑﺪﻫﻴﻢ ﭼﻪ ﺍﺗﻔﺎﻗﻲ ﻣﻲ ﺍﻓﺘﺪ؟ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮ‬
‫ﻛﺎﺭﺕ ‪ CP‬ﺭﺍ ﺑﺎ ﻧﻮﻉ ﺩﻳﮕﺮ ﺗﻌﻮﻳﺾ ﻛﻨﻴﻢ‪ .‬ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ‬
‫‪ Connection Table‬ﺑﺎﻗﻲ ﻣﻴﻤﺎﻧﺪ‪.‬‬ ‫•‬

‫‪ ID‬ﺑﻄﻮﺭ ﺍﺗﻮﻣﺎﺗﻴﻚ ‪ Update‬ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫‪ LADDR‬ﺭﺍ ﺑﺎﻳﺪ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺁﺩﺭﺱ ﺑﻴﺲ ﻛﺎﺭﺕ ﺗﻐﻴﻴﺮ ﺩﺍﺩ‪.‬‬ ‫•‬

‫ﻭ ﻧﻬﺎﻳﺘﹰﺎ ﺑﺎﻳﺪ ‪ Connection Table‬ﺭﺍ ﻣﺠﺪﺩﹰﺍ ‪ Download‬ﻛﺮﺩ‪.‬‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٣٨‬‬

‫ﮔﺎﻡ ﺳﻮﻡ ‪ :‬ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺳﺮﻭﻳﺲ ‪FDL‬‬
‫ﺑﺮﺍﻱ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪ FDL‬ﺑﺎﻳﺪ ﺩﻭ ﺗﺎﺑﻊ ﻳﻜﻲ ﺑﺮﺍﻱ ﻓﺮﺳﺘﺎﺩﻥ ﺍﻃﻼﻋﺎﺕ )‪ (SEND‬ﺩﺭ ﺳﻤﺖ ﺍﻳﺴﺘﮕﺎﻩ ﻓﺮﺳﺘﻨﺪﻩ ﻭﻳﻜﻲ ﺑﺮﺍﻱ‬
‫ﮔﺮﻓﺘﻦ ﺍﻃﻼﻋﺎﺕ )‪ (RECIVE‬ﺩﺭ ﺳﻤﺖ ﺍﻳﺴﺘﮕﺎﻩ ﮔﻴﺮﻧﺪﻩ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ ﻛﺎﺭﺑﺮ‪،‬ﻗﺮﺍﺭ ﮔﻴﺮﺩ‪.‬‬
‫ﺩﺭ ﻗﺴﻤﺖ ﻫﺎﻱ ﻗﺒﻞ ﻳﻚ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ‪ FDL‬ﺑﻴﻦ ﺍﻳﺴﺘﮕﺎﻩ )‪ SIMATIC 300(1‬ﻭ)‪ SIMATIC 400(1‬ﺑﺮﻗﺮﺍﺭ ﺷﺪ‬
‫ﺍﻛﻨﻮﻥ ﺍﺯ ﻃﺮﻳﻖ ﺁﻥ ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﻳﻚ ﺳﺮﻱ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﻣﺒﺎﺩﻟﻪ ﻛﻨﻴﻢ‪.‬ﺗﻮﺟﻪ ﺍﻳﻨﻜﻪ ﺩﺭ‪ Connection Table‬ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫ﺍﻳﻦ ﺷﺒﻜﻪ ﻣﻲ ﺗﻮﺍﻧﺴﺘﻴﻢ ﻟﻴﻨﻚ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ﺩﻳﮕﺮﻱ ﻫﻢ ﺑﻴﻦ ‪ Station‬ﻫﺎﻱ ﺩﻳﮕﺮ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺻﻮﺭﺕ ﻫﺮ‬
‫ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ‪،‬ﻳﻚ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻣﺠﺰﺍ ﺩﺭ ﻫﺮ ﺩﻭﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﻭﮔﻴﺮﻧﺪﻩ ﻧﻴﺎﺯ ﺩﺍﺭﺩ‪.‬‬
‫ﻧﻜﺎﺕ ﻗﺎﺑﻞ ﺗﻮﺟﻪ‪:‬‬
‫• ﺑﺮﺍﻱ ﻓﺮﺳﺘﺎﺩﻥ ﺍﻃﻼﻋﺎﺕ ﺍﺯ ﺗﺎﺑﻌﻲ ﺑﻪ ﻧﺎﻡ ‪ AG_SEND‬ﻭ ﺑﺮﺍﻱ ﺩﺭﻳﺎﻓﺖ ﺁﻥ ﺍﺯ ﺗﺎﺑﻊ ‪ AG_RECV‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫• ﻟﺰﻭﻣﻲ ﻧﺪﺍﺭﺩ ﻛﻪ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻫﺎ ﺣﺘﻤﹰﺎ ﺩﺭ ‪ OB1‬ﺻﺪﺍ ﺯﺩﻩ ﺷﻮﻧﺪ ﻣﻴﺘﻮﺍﻥ ﺁﻧﻬﺎ ﺭﺍ ﺩﺭ ﺳﺎﻳﺮ ‪ OB‬ﻫﺎ ﻳﺎ ﺑﻼﻛﻬﺎ ﺻﺪﺍ ﺯﺩ‪.‬‬
‫• ﺑﺮﺍﻱ ﺗﺒﺎﺩﻝ ﺳﻴﻜﻠﻲ ﺑﻬﺘﺮﻳﻦ ﺭﻭﺵ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OB‬ﻫﺎﻱ ‪ Cyclic Interrupt‬ﺍﺳﺖ‪.‬‬
‫• ﺯﻣﺎﻧﻲ ﻛﻪ ﺻﺮﻑ ﻣﻴﺸﻮﺩ ﺩﻳﺘﺎ ﺍﺯ ﻃﺮﻳﻖ ﻛﺎﺭﺕ ‪ CP‬ﻭ ﺷﺒﻜﻪ ﺍﺭﺳﺎﻝ ﻭ ﺟﻮﺍﺏ ﺩﺭﻳﺎﻓﺖ ﺷﻮﺩ ﺟﺪﺍ ﺍﺯ ﺳﻴﻜﻞ ﺍﺳﻜﻦ ﺍﺳﺖ‬
‫ﻭ ﺑﻪ ‪ Transmission Time‬ﻣﻌﺮﻭﻑ ﺍﺳﺖ‪.‬‬
‫• ﺍﺯ ﺁﻧﺠﺎ ﻛﻪ ﺳﻴﻜﻞ ﺍﺳﻜﻦ ﺳﺮﻳﻌﺘﺮ ﺍﺯ ‪ Transmission Time‬ﺍﺳﺖ ﺍﮔﺮ ﻗﺒﻞ ﺍﺯ ﺗﻜﻤﻴﻞ ﺍﺭﺳﺎﻝ ﻗﺒﻠﻲ ﻣﺠﺪﺩﺍ ﻋﻤﻞ‬
‫ﺍﺭﺳﺎﻝ ﺍﺗﻔﺎﻕ ﺑﻴﻔﺘﺪ ﺩﻳﺘﺎﻱ ﺟﺪﻳﺪ ﺍﺭﺳﺎﻝ ﻧﻤﻴﺸﻮﺩ ﺗﺎ ﺍﺭﺳﺎﻝ ﻗﺒﻠﻲ ﻛﺎﻣﻞ ﺷﻮﺩ‪.‬‬
‫• ﻣﻴﺘﻮﺍﻥ ﺩﺭ ﺑﻼﻙ ‪ OB‬ﭼﻨﺪﻳﻦ ﺑﺎﺭ ﺍﺯ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﻓﻮﻕ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻭ ﻫﺮﺑﺎﺭ ﺩﻳﺘﺎ ﺭﺍ ﺑﻪ ﺁﺩﺭﺱ ﺟﺪﺍﮔﺎﻧﻪ ﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺍﺩ‪.‬‬
‫• ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﻓﻮﻕ ﺷﺒﻴﻪ ‪ DP_SEND‬ﻭ ‪ DP_RECV‬ﺩﺭ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ‪ Libraries>Simatic Net‬ﺩﺭ ﭘﻨﺠﺮﻩ‬
‫‪ Program Element‬ﺑﺮﻧﺎﻣﻪ ‪ LAD/STL/FBD‬ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ ﻭ ﺍﺯ ﺍﻳﻦ ﻣﺴﻴﺮ ﺑﺎﻳﺪ ‪ Drag‬ﺷﺪﻩ ﻭ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻗﺮﺍﺭ‬
‫ﮔﻴﺮﻧﺪ‪.‬‬
‫• ﺑﺮﺍﻱ ‪ S7-300‬ﻭ ‪ S7-400‬ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ﻣﺰﺑﻮﺭ ﻣﺘﻔﺎﻭﺗﻨﺪ ﻭ ﺩﺭ ‪ Folder‬ﻫﺎﻱ ﺟﺪﺍﮔﺎﻧﻪ ﺩﺭ ﺁﺩﺭﺱ ﻓﻮﻕ ﻗﺮﺍﺭ ﺩﺍﺭﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٣٩‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﻓﺎﻧﻜﺸﻦ ‪AG_SEND‬‬
‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻛﻪ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ ﺁﻥ ‪ FC5‬ﺍﺳﺖ ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺷﻜﻞ ﺯﻳﺮ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺭﺍ‬
‫ﺑﺼﻮﺭﺕ ﺑﻼﻙ ‪ FBD‬ﻫﻤﺮﺍﻩ ﺑﺎ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻳﺶ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬

‫ﻭﺭﻭﺩﻱ ﻫﺎ ‪:‬‬
‫ﺍﮔﺮ ‪ ACT=1‬ﺑﺎﺷﺪ ‪ LEN‬ﺑﺎﻳﺖ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ‪.‬‬ ‫‪ACT‬‬

‫ﺍﮔﺮ ‪ ACT=0‬ﺑﺎﺷﺪ ﻫﺮ ﺳﻪ ﺧﺮﻭﺟﻲ ‪ update‬ﻣﻴﺸﻮﻧﺪ‪.‬‬

‫ﻋﺪﺩ ﺻﺤﻴﺢ ﻛﻪ ﺩﺭ ‪ Connection Table‬ﻣﺸﺨﺺ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬ ‫‪ID‬‬

‫ﻛﺪ ﻫﮕﺰ ﻛﻪ ﺩﺭ ‪ Connection Table‬ﻣﺸﺨﺺ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬ ‫‪LADDR‬‬

‫ﺁﺩﺭﺱ ﺣﺎﻓﻈﻪ ﻭ ﻣﻘﺪﺍﺭ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﺑﺎﻳﺪ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ‪ .‬ﺍﻳﻦ ﺁﺩﺭﺱ ﻣﺮﺑﻮﻁ ﺑﻪ ﺣﺎﻓﻈﻪ‬ ‫‪SEND‬‬

‫ﻓﺮﺳﺘﻨﺪﻩ ﺍﺳﺖ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ‪ I‬ﻭ ‪ Q‬ﻭ ‪ M‬ﻭ ‪ DB‬ﺑﺎﺷﺪ‪ .‬ﻣﺎﻧﻨﺪ ﻣﺜﺎﻟﻬﺎﻱ ﺯﻳﺮ ‪:‬‬
‫•‬ ‫‪P#DB1.DBX0.0 BYTE 240‬‬
‫•‬ ‫‪P#M0.0 BYTE 100‬‬
‫•‬ ‫‪P#I0.0 BYTE 200‬‬
‫ﻣﻘﺪﺍﺭ ﺑﺎﻳﺘﻲ ﻛﻪ ﺑﺎﻳﺪ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻴﻦ ‪ 1‬ﺗﺎ ‪ 240‬ﺑﺎﺷﺪ‪.‬‬ ‫‪LEN‬‬

‫ﺧﺮﻭﺟﻲ ﻫﺎ ‪:‬‬
‫ﺳﻪ ﺧﺮﻭﺟﻲ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻭﺿﻌﻴﺖ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﻨﺪ ﻣﻄﺎﺑﻖ ﺟﺪﻭﻝ ﺯﻳﺮ‬
‫‪STATUS‬‬ ‫‪ERROR‬‬ ‫‪DONE‬‬

‫ﺍﺭﺳﺎﻝ ﺑﺪﻭﻥ ﺧﻄﺎ ﻛﺎﻣﻞ ﺷﺪﻩ ﺍﺳﺖ‬ ‫‪0‬‬ ‫‪0‬‬ ‫‪1‬‬

‫‪ Job‬ﻫﻨﻮﺯ ﻓﻌﺎﻝ ﺍﺳﺖ‬ ‫‪8181‬‬ ‫‪0‬‬ ‫‪0‬‬

‫‪ Job‬ﺩﺭ ﺣﺎﻝ ﺍﺟﺮﺍ ﻧﻴﺴﺖ )ﺩﻳﺘﺎﻳﻲ ﺍﺭﺳﺎﻝ ﻧﺸﺪﻩ ﺍﺳﺖ(‬ ‫‪0000‬‬ ‫‪0‬‬ ‫‪0‬‬

‫ﻗﻄﻊ ﺷﺪﻥ ﺍﺭﺳﺎﻝ ﺑﺪﻟﻴﻞ ﻭﺟﻮﺩ ﺧﻄﺎ ﺑﺎ ﻛﺪ ‪) x‬ﺗﻮﺿﻴﺢ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ(‬ ‫‪x‬‬ ‫‪1‬‬ ‫‪0‬‬
Techno-Electro.com

PROFIBUS ‫ ﺩﺭ‬FDL ‫ﺍﺭﺗﺒﺎﻁ‬ ١٤٠

DONE ERROR STATUS Meaning

This code is only possible with an S7-400; the FC was called with ACT=0; the job
0 1 7000H is however not processed
0 1 8183H No configuration or the FDL service has not yet started on the PROFIBUS CP.
0 1 8184H Illegal data type specified for the SEND parameter.
FDL connection without job buffer: system error.
FDL connection with job buffer: parameter LEN<4 or illegal job header
0 1 8185H LEN parameter longer than SEND source area.
0 1 8186H ID parameter invalid. ID!=1,2 to 15,16.
0 1 8301H SAP not activated on destination station.
0 1 8302H No receive resources on the destination station; the receiving
station cannot process received data quickly enough or has not
prepared any receive resources.
0 1 8303H The PROFIBUS service (SDA Send Data with Acknowledge) is not supported
on this SAP of the destination station.
0 1 8304H The FDL connection is not established.
0 1 8311H The destination station is not obtainable at the specified
PROFIBUS address or the service is not possible for the
specified PROFIBUS address.
0 1 8312H PROFIBUS error on the CP; for example bus short circuit, local
station not in the ring.
0 1 8315H Internal parameter error on an FDL connection with job header:
Parameter LEN<4 or illegal parameter in the job header (with free
layer 2 access).
0 1 8F22H Source area invalid, for example: Area does not exist in the DB
LEN parameter < 0
0 1 8F24H Area error reading a parameter.
0 1 8F28H Alignment error reading a parameter.
0 1 8F32H Parameter contains a DB number that is too high.
0 1 8F33H DB number error.
0 1 8F3AH Area not loaded (DB).
0 1 8F42H Timeout reading a parameter from the I/O area.
0 1 8F44H Address of the parameter to be read is disabled in the access track
0 1 8F7FH Internal error, e.g. illegal ANY reference. e.g. parameter LEN=0
0 1 8090H No module with this base address exists.
The FC being used does not match the system family being
used (remember to use different FC for S7-300 and S7-400).
0 1 8091H Logical base address not at a double word boundary.
0 1 8092H In the ANY reference, a type other than BYTE is specified. (S7-400 only)
0 1 80A4H The communication bus connection between the CPU and CP is not established
0 1 80B0H The module does not recognize the data record.
0 1 80B1H Destination area invalid. for example, destination area > 240 bytes.
0 1 80B2H The communication bus connection between the CPU and CP is not established
0 1 80C0H The data record cannot be read.
0 1 80C1H The specified data record is currently being processed.
0 1 80C2H There are too many jobs pending.
0 1 80C3H Resources occupied (memory).
0 1 80C4H Communication error (occurs temporarily, it is usually best to repeat the job)
0 1 80D2H Module base address incorrect
‫‪Techno-Electro.com‬‬

‫‪١٤١‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﺍﻳﺴﺘﮕﺎﻩ )‪SIMATIC 400(1‬‬ ‫ﻣﺜﺎﻝ ‪ :‬ﻣﻲ ﺧﻮﺍﻫﻴﻢ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺍﺯ ﺁﺩﺭﺱ ﺷﺮﻭﻉ ‪ DB 100‬ﺩﺭ )‪ SIMATIC 300(2‬ﺑﻪ‬
‫ﻼ ﺩﻳﺪﻳﺪ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ﻛﻪ ﺑﻴﻦ ﺩﻭ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﻗﺮﺍﺭ ﻛﺮﺩﻳﻢ ﺑﻪ ﻣﺸﺨﺼﺎﺕ ‪ID = 1‬‬
‫ﺍﺭﺳﺎﻝ ﻛﻨﻴﻢ ‪.‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻗﺒ ﹰ‬
‫ﻭ ‪ LADDR = W#16#0100‬ﺑﻮﺩ ﺍﻳﻦ ﺩﻭ ﭘﺎﺭﺍﻣﺘﺮ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ‪،‬ﺑﻪ ﻛﺎﺭ ﻣﻲ ﺁﻳﻨﺪ‪.‬‬
‫ﺳﺎﺩﻩ ﺗﺮﻳﻦ ﻓﺮﻡ ﻣﻤﻜﻦ ﺑﺮﺍﻱ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ ﺍﺭﺗﺒﺎﻁ ﺑﻪ ﺻﻮﺭﺕ ﺯﻳﺮ ﺍﺳﺖ‪.‬ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﺭﺍ ﺩﺭ ﻗﺴﻤﺖ ‪ OB 1‬ﺩﺭ‬
‫)‪ SIMATIC 300(2‬ﻣﻲ ﻧﻮﻳﺴﻴﻢ‪.‬‬
‫‪CALL AG-SEND‬‬
‫‪ACT: = M0.0‬‬
‫‪ID: = 1‬‬
‫‪LADDR: =W#16#0100‬‬
‫‪SEND: = P#DB100.DBX0 BYTE 240‬‬
‫‪LEN: =240‬‬
‫‪DONE: =M0.1‬‬
‫‪ERROR: =M0.2‬‬
‫‪STATUS: =MW20‬‬

‫ﺍﻳﻦ ﻛﻪ ﭼﺮﺍ ‪ ACT‬ﺭﺍ ﻣﺴﺘﻘﻴﻤﹰﺎ ﻣﻘﺪﺍﺭ ﻗﺮﺍﺭ ﻧﺪﺍﺩﻩ ﺍﻳﻢ ﺑﻪ ﺍﻳﻦ ﺩﻟﻴﻞ ﺍﺳﺖ ﻛﻪ ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﻛﻨﺘﺮﻝ‬
‫ﻛﻨﻴﻢ‪.‬ﺍﮔﺮ ‪ ACT‬ﺭﺍ ‪ 1‬ﺑﮕﺬﺍﺭﻳﻢ ﭼﻮﻥ ﺑﺮﻧﺎﻣﻪ ﺑﻪ ﺻﻮﺭﺕ ﺳﻴﻜﻠﻲ ﺍﺟﺮﺍ ﻣﻲ ﺷﻮﺩ ﻫﺮ ﺑﺎﺭ ﻛﻪ ﺑﻪ ﺧﻂ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺑﺮﺳﺪ‬
‫‪،‬ﺻﺮﻑ ﻧﻈﺮ ﺍﺯ ﺍﻳﻨﻜﻪ ﺍﺭﺳﺎﻝ ﻗﺒﻠﻲ ﺩﺭ ﭼﻪ ﻭﺿﻌﻴﺘﻲ ﻗﺮﺍﺭ ﺩﺍﺭﺩ ﻭﺁﻳﺎ ﺩﻳﺘﺎﻱ ﻗﺒﻠﻲ ﺑﻪ ﺳﻼﻣﺖ ﺭﺳﻴﺪﻩ ﺍﺳﺖ ﻳﺎﻧﻪ‪ ،‬ﺩﻳﺘﺎﻱ ﺟﺪﻳﺪ‬
‫ﺭﺍ ﺍﺭﺳﺎﻝ ﻣﻲ ﻛﻨﺪ‪.‬ﺩﺭ ﺣﺎﻟﻴﻜﻪ ﺍﻳﻦ ﺍﻣﻜﺎﻥ ﻓﺮﺍﻫﻢ ﺍﺳﺖ ﻛﻪ ﺑﺎ ﺑﺮﺭﺳﻲ ﻣﻘﺎﺩﻳﺮ ‪ DONE‬ﻭ ‪ ERROR‬ﻭ ‪ STATUS‬ﺑﻪ‬
‫ﺻﻮﺭﺕ ﻫﻮﺷﻤﻨﺪﺍﻧﻪ ﺍﻱ‪،‬ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺍﺭﺳﺎﻝ ﻛﻨﻴﻢ‪.‬‬
‫ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﻛﻪ ﺩﺭ ﺍﺑﺘﺪﺍﻱ ﻛﺎﺭ ﻳﻚ ﺑﺎﺭ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﻣﻲ ﻓﺮﺳﺘﻴﻢ ‪.‬ﺩﺭ ﻭﺍﻗﻊ ﺩﺭ ‪ OB 100‬ﻛﻪ ‪ OB‬ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺍﺳﺖ‬
‫ﻣﻘﺪﺍﺭ ‪ ACT‬ﺭﺍ ‪ 1‬ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﻴﻢ‪.‬ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﺯﻣﺎﻧﻲ ﻛﻪ ‪ CPU‬ﺑﻪ‪ OB1‬ﻣﻲ ﺭﺳﺪ ﭼﻮﻥ ‪ ACT‬ﻳﻚ ﺍﺳﺖ ‪،‬ﻳﻚ ﺑﺎﺭ‬
‫ﺍﺭﺳﺎﻝ ﺭﺍ ﺍﻧﺠﺎﻡ ﻣﻲ ﺩﻫﺪ‪.‬ﭘﺲ ﺍﺯ ﺍﺭﺳﺎﻝ ‪ ،‬ﻣﻘﺪﺍﺭ ‪ ACT‬ﺭﺍ ﺻﻔﺮ ﻣﻲ ﻛﻨﻴﻢ ﻭﺷﺮﻭﻉ ﺑﻪ ﺍﺭﺯﻳﺎﺑﻲ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﻣﻲ ﻛﻨﻴﻢ‬
‫ﺍﮔﺮ ﻣﻘﺪﺍﺭ ‪ DONE‬ﺑﺮﺍﺑﺮ ‪ 1‬ﺑﺎﺷﺪ ﻛﻪ ﺍﺭﺳﺎﻝ ﺑﻪ ﻃﻮﺭ ﻛﺎﻣﻞ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ‪،‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﻣﺠﺪﺩﹰﺍ ‪ ACT‬ﺭﺍ ‪ 1‬ﻣﻲ ﻛﻨﻴﻢ ﺗﺎ ﺍﺭﺳﺎﻝ‬
‫ﺍﻧﺠﺎﻡ ﺷﻮﺩ ﻭﻟﻲ ﺍﮔﺮﻣﻘﺪﺍﺭ ‪ 1، DONE‬ﻧﺒﻮﺩ ﻭ ‪ ERROR‬ﻳﻚ ﺷﻮﺩ ﻳﻌﻨﻲ ﺩﺭ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺧﻄﺎﻳﻲ ﺭﺥ ﺩﺍﺩﻩ ﺍﺳﺖ ﻣﻲ‬
‫ﺗﻮﺍﻧﻴﻢ ﻳﻚ ‪ TAG‬ﺭﺍ ﻳﻚ ﻛﻨﻴﻢ ﺗﺎ ﺑﻪ ﺳﻴﺴﺘﻢ ﻣﻮﻧﻴﺘﻮﺭﻳﻨﮓ ﺧﺒﺮ ﺩﺍﺩﻩ ﺷﻮﺩﻳﺎ ﺍﻳﻨﻜﻪ ﻣﻲ ﺗﻮﺍﻧﻴﻢ ‪ ACT‬ﺭﺍ ﻳﻚ ﻛﻨﻴﻢ ﻭ ﺑﻪ‬
‫ﺍﻧﺘﻬﺎﻱ ﺑﺮﻧﺎﻣﻪ ‪ Jump‬ﻛﻨﻴﻢ ﺑﻪ ﺍﻳﻦ ﺗﺮﺗﻴﺐ ﻭﻗﺘﻲ ‪ CPU‬ﺑﻪ ﺍﺑﺘﺪﺍﻱ ﺳﻴﻜﻞ ‪ OB1‬ﻣﻲ ﺭﺳﺪ ﻣﺠﺪﺩﹰﺍ ﻫﻤﺎﻥ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺍﺭﺳﺎﻝ‬
‫ﻣﻲ ﻛﻨﺪ ﻭﺧﻼﺻﻪ ﺍﻳﻨﻜﻪ ﻫﺮ ﺗﺪﺑﻴﺮ ﺩﻳﮕﺮﻱ ﻣﺘﻨﺎﺳﺐ ﺑﺎ ﺧﻄﺎ ﺭﺥ ﺩﺍﺩﻩ ﻣﻲ ﺗﻮﺍﻧﻴﺪ ﺩﺭ ﻧﻈﺮ ﺑﮕﻴﺮﻳﺪ ﻭﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﻧﻤﺎﻳﻴﺪ‪.‬ﺩﺭ‬
‫ﺍﻳﻨﺠﺎ ﺍﮔﺮ ﺧﻄﺎﻳﻲ ﺩﺭ ﺍﺭﺳﺎﻝ ﻳﻚ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺭﺥ ﺩﻫﺪ ‪،‬ﻣﻲ ﺧﻮﺍﻫﻴﻢ ﺧﺎﻧﻪ ﺣﺎﻓﻈﻪ ‪ M100.0‬ﻳﻚ ﺷﻮﺩ‪ .‬ﺍﮔﺮ ‪ DONE‬ﺻﻔﺮ‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٤٢‬‬

‫ﺑﺎﺷﺪ ﻭ‪ ERROR‬ﻫﻢ ﺻﻔﺮ ﺑﺎﺷﺪ‪،‬ﺩﺭ ﻭﺍﻗﻊ ﺳﻴﺴﺘﻢ ﺩﺭ ﺣﺎﻝ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺍﺳﺖ‪ ،‬ﭘﺲ ﻛﺎﺭ ﺧﺎﺻﻲ ﻧﺒﺎﻳﺪ ﺍﻧﺠﺎﻡ ﺩﻫﻴﻢ ﻭ‬
‫‪ ACT‬ﺑﺎﻳﺪ ﻣﻘﺪﺍﺭ ﺻﻔﺮ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﻭﺍﻳﻦ ﻭﺿﻌﻴﺖ ﺍﺩﺍﻣﻪ ﻣﻲ ﻳﺎﺑﺪ ﺗﺎ ﺍﻳﻨﻜﻪ ﻭﺿﻌﻴﺖ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﻣﺸﺨﺺ ﺷﻮﺩ‪.‬‬
‫ﺑﺮﻧﺎﻣﻪ ﻓﻮﻕ ﺑﻪ ﺻﻮﺭﺕ ﺯﻳﺮ ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺷﺪﻩ ﺍﺳﺖ‪:‬‬

‫‪OB100:‬‬
‫‪SET‬‬
‫‪=M0.0‬‬

‫‪OB1:‬‬
‫‪CALL AG_SEND‬‬
‫‪ACT:=M0.0‬‬
‫‪ID:=1‬‬
‫‪LADDR:=W#16#0100‬‬
‫‪SEND:=P#DB100.DBX0.0 BYTE 240‬‬
‫‪LEN:=240‬‬
‫‪DONE:=M0.1‬‬
‫‪ERROR:=M0.2‬‬
‫‪STATUS:=MW20‬‬

‫‪R M0.0‬‬
‫‪SET‬‬
‫‪A M0.1‬‬
‫‪JC A001‬‬
‫‪SET‬‬
‫‪A M0.2‬‬
‫‪JC A002‬‬
‫‪JU NEXT‬‬
‫‪A001: S M0.0‬‬
‫‪JU NEXT‬‬
‫‪A002: S M100.0‬‬
‫‪NEXT :‬‬
‫ﺍﺩﺍﻣﻪ ﺑﺮﻧﺎﻣﻪ ﻣﻮﺭﺩ ﻧﻈﺮ‬
‫‪BE‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﭘﺲ ﺍﺯ ﺍﺗﻤﺎﻡ ﻛﺎﺭ ﺑﺎﻳﺪ ﺗﻤﺎﻡ ﺑﻼﻛﻬﺎ ﺭﺍ ﺑﻪ ‪ PLC‬ﺩﺍﻧﻠﻮﺩ ﻛﺮﺩ‪ .‬ﭘﺲ ﻻﺯﻡ ﺍﺳﺖ ﺩﻳﺘﺎ ﺑﻼﻙ ﻧﻴﺰ ﻗﺒ ﹰ‬
‫ﻼ ﺍﻳﺠﺎﺩ ﺷﺪﻩ‬
‫ﺑﺎﺷﺪ ﺗﺎ ﺑﺘﻮﺍﻥ ﺁﻧﺮﺍ ﺩﺍﻧﻠﻮﺩ ﻛﺮﺩ‪ .‬ﺍﺯ ﺁﻧﺠﺎ ﻛﻪ ﺍﻳﺠﺎﺩ ﺩﻳﺘﺎ ﺑﻼﻙ ﻭ ﻣﻌﺮﻓﻲ ‪ ٢٤٠‬ﺑﺎﻳﺖ ﺁﺩﺭﺱ ﺩﺭ ﺁﻥ ﻛﻤﻲ ﻭﻗﺖ ﮔﻴﺮ ﺍﺳﺖ‬
‫ﻣﻴﺘﻮﺍﻥ ﺑﺎ ﺭﻭﺷﻲ ﻛﻪ ﺩﺭ ﻓﺼﻞ ﻗﺒﻞ ﺑﺮﺍﻱ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪ DP‬ﮔﻔﺘﻪ ﺷﺪ ﺗﻮﺳﻂ ‪ SFC22‬ﺑﻄﻮﺭ ﺍﺗﻮﻣﺎﺗﻴﻚ ﺁﻧﺮﺍ ﺩﺭ ﻫﻨﮕﺎﻡ‬
‫ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ) ﻳﻌﻨﻲ ﺗﻮﺳﻂ ‪ (OB100‬ﺍﻳﺠﺎﺩ ﻧﻤﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٤٣‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﻓﺎﻧﻜﺸﻦ ‪AG_RECV‬‬
‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﻛﻪ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ ﺁﻥ ‪ FC6‬ﺍﺳﺖ ﺑﺮﺍﻱ ﺩﺭﻳﺎﻓﺖ ﺩﻳﺘﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺷﻜﻞ ﺯﻳﺮ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺭﺍ‬
‫ﺑﺼﻮﺭﺕ ﺑﻼﻙ ‪ FBD‬ﻫﻤﺮﺍﻩ ﺑﺎ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻳﺶ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬

‫ﺑﺎ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﺩﺭ ﻣﻮﺭﺩ ‪ AG_SEND‬ﺩﺍﺩﻩ ﺷﺪ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ‪ AG_RECV‬ﻧﻴﺰ ﻣﺸﺨﺺ ﺍﺳﺖ‪.‬ﻓﻘﻂ‬

‫ﻧﻜﺎﺕ ﺯﻳﺮ ﻗﺎﺑﻞ ﺗﻮﺟﻪ ﺍﺳﺖ‪:‬‬

‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻧﻴﺰ ‪ ID‬ﻭ‪ LADDR‬ﻫﻤﺎﻥ ﻣﻌﺎﻧﻲ ﺑﺨﺶ ﻗﺒﻞ ﺭﺍ ﻣﻲ ﺩﻫﺪ ﻭﻟﻲ ﺑﺮﺍﻱ ‪ Connection‬ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ‪.‬‬ ‫•‬
‫ﺩﺭ ‪ AG-RECV‬ﭘﺎﺭﺍﻣﺘﺮﻱ ﺑﻪ ﺍﺳﻢ ‪ ACT‬ﻧﺪﺍﺭﻳﻢ‪ .‬ﺩﺭ ﻭﺍﻗﻊ ﺍﻳﻦ ﺗﺎﺑﻊ ﻫﻤﻴﺸﻪ ﻣﻨﺘﻈﺮ ﺩﺭﻳﺎﻓﺖ ﺍﺳﺖ ﻧﻴﺎﺯﻱ ﺑﻪ‬ ‫•‬

‫ﻓﻌﺎﻝ ﻛﺮﺩﻥ ﻧﺪﺍﺭﺩ‪.‬‬

‫‪ RECV‬ﺁﺩﺭﺱ ﻣﺤﻞ ﺫﺧﻴﺮﻩ ﻭﻃﻮﻝ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﻗﺮﺍﺭ ﺍﺳﺖ ﺩﺭﻳﺎﻓﺖ ﺷﻮﺩ ﺭﺍ ﺑﻴﺎﻥ ﻣﻲ ﻛﻨﺪ‪ .‬ﻓﺮﻣﺖ ﺁﻥ ﺷﺒﻴﻪ‬ ‫•‬
‫‪ SEND‬ﺍﺳﺖ‬
‫‪ LEN‬ﺗﻌﺪﺍﺩ ﺑﺎﻳﺖ ﻫﺎﻱ ﺩﺭﻳﺎﻓﺘﻲ ﺭﺍ ﻣﺸﺨﺺ ﻣﻲ ﻛﻨﺪ‪.‬‬ ‫•‬

‫‪ NDR‬ﻫﻤﺎﻧﻨﺪ ‪ DONE‬ﺩﺭ ‪ AG_SEND‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﺍﮔﺮ ‪ ١‬ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﺩﺭﻳﺎﻓﺖ ﻛﺎﻣﻞ ﻭﺑﺪﻭﻥ ﺧﻄﺎ ﺍﻧﺠﺎﻡ‬ ‫•‬

‫ﺷﺪﻩ ﺍﺳﺖ ﻭﺍﮔﺮ ﺻﻔﺮ ﺑﺎﺷﺪ‪ ،‬ﻳﺎ ﺳﻴﺴﺘﻢ ﺩﺭ ﺣﺎﻝ ﺩﺭﻳﺎﻓﺖ ﺍﻃﻼﻋﺎﺕ ﺍﺳﺖ ﻭﻳﺎ ﺩﺭﻳﺎﻓﺖ ﺍﻃﻼﻋﺎﺕ ﺑﺎ ﻣﺸﻜﻞ‬
‫ﻣﻮﺍﺟﻪ ﺷﺪﻩ ﺍﺳﺖ‬
‫ﺍﮔﺮ ‪ NDR‬ﺻﻔﺮ ﺑﺎﺷﺪ ﻭ ‪ ERROR‬ﻳﻚ ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﺩﺭ ﺩﺭﻳﺎﻓﺖ ﺍﻃﻼﻋﺎﺕ ﺧﻄﺎﻳﻲ ﺭﺥ ﺩﺍﺩﻩ ﺍﺳﺖ ﻛﻪ ﺧﻄﺎﻱ‬ ‫•‬
‫ﺭﺥ ﺩﺍﺩﻩ ﺍﺯ ﻣﻘﺪﺍﺭ ‪ STATUS‬ﻗﺎﺑﻞ ﺍﺳﺘﺨﺮﺍﺝ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٤٤‬‬

‫ﻣﺜﺎﻝ ‪ :‬ﺑﺮﻧﺎﻣﻪ ﺍﻱ ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﻳﻌﻨﻲ ﺍﻳﺴﺘﮕﺎﻩ )‪ SIMATIC 400(1‬ﺑﻨﻮﻳﺴﻴﺪ ﻛﻪ ‪ ٢٤٠‬ﺑﺎﻳﺘﻲ ﺭﺍ ﻛﻪ ﺩﺭ ﻗﺴﻤﺖ ﻗﺒﻞ‬
‫ﺍﺭﺳﺎﻝ ﻛﺮﺩﻩ ﺍﻳﻢ ﺭﺍ ﺩﺭﻳﺎﻓﺖ ﻧﻤﻮﺩﻩ ﻭﺩﺭ ‪ DB 20‬ﺑﺮﻳﺰﺩ‪.‬‬
‫‪CALL AG-RECV‬‬
‫‪ACT: = M0.0‬‬
‫‪ID: = 1‬‬
‫‪LADDR: =W#16#0100‬‬
‫‪SEND: = P#DB20.DBX0.0 BYTE 240‬‬
‫‪NDR: =M0.0‬‬
‫‪ERROR: =M0.1‬‬
‫‪STATUS: =MW100‬‬
‫‪LEN=240‬‬

‫ﺷﻜﻞ ﺯﻳﺮ ﻧﺘﻴﺠﻪ ﺑﺤﺚ ﺭﺍ ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ﻭ ﺩﺭﻳﺎﻓﺖ ﺩﻳﺘﺎ ﺗﻮﺳﻂ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺭﺍ ﻧﺸﺎﻥ ﻣﻲ ﺩﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٤٥‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﻴﻦ ‪ PLC‬ﻫﺎﻱ ‪ S7‬ﻭ‪S5‬‬ ‫‪٢-٨‬‬

‫ﮔﺎﻡ ﺍﻭﻝ ‪ :‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﺳﻴﺴﺘﻢ‬
‫‪SIMATIC‬‬ ‫ﺩﺭ ﻳﻚ ﭘﺮﻭﮊﻩ ﺟﺪﻳﺪ ﻳﻚ ‪ Station 300‬ﻭﻳﻚ ‪ Station S5‬ﺍﺯ ﻧﻮﻉ ‪ DP Master‬ﺍﻳﺠﺎﺩ ﻛﻨﻴﺪ‪.‬ﺩﺭ‬
‫‪ MANAGER‬ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻳﻚ ‪ Station S5‬ﺩﺭ ﺷﺒﻜﻪ ‪، PROFIBUS‬ﺑﺎﻳﺪ ﺍﻳﻦ ﺍﻳﺴﺘﮕﺎﻩ ﺭﺍ ﺩﺭ ﺯﻣﺎﻥ ﭘﻴﻜﺮ ﺑﻨﺪﻱ‬
‫ﺩﺭ ﻧﻈﺮ ﺑﮕﻴﺮﻳﻢ ﻭ ﺩﺭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺷﺒﻜﻪ ﻟﺤﺎﻅ ﻛﻨﻴﻢ‪ .‬ﺍﻟﺒﺘﻪ ﺟﺰﺋﻴﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ S5‬ﺗﻮﺳﻂ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ STEP5‬ﺻﻮﺭﺕ‬
‫ﻣﻲ ﮔﻴﺮﺩ ﻭﺩﺭ ‪ STEP7‬ﺗﻨﻬﺎ ﺁﻥ ﺑﺨﺶ ﺍﺯ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ S5‬ﻛﻪ ﻣﺮﺑﻮﻁ ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺍﺳﺖ ﺍﻧﺠﺎﻡ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﻳﻚ ‪ Station S5‬ﺩﺭ ﺻﻔﺤﻪ ﺍﺻﻠﻲ ‪ SIMATIC MANAGER‬ﺑﺮ ﺭﻭﻱ ﻧﺎﻡ ﭘﺮﻭﮊﻩ ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻧﻤﻮﺩﻩ‬
‫ﻭﺍﺯ ﻗﺴﻤﺖ ‪ Insert New Object‬ﮔﺰﻳﻨﻪ ‪ SIMATIC S5‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ‪ .‬ﺩﺭ ﺻﻔﺤﻪ ﺳﻤﺖ ﺭﺍﺳﺖ ﺑﺮﺭﻭﻱ‬
‫)‪ SIMATIC S5(1‬ﺭﺍﺳﺖ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ ﻭﺩﺭ ﻗﺴﻤﺖ ‪ ، Interface‬ﻛﻠﻴﺪ ‪ New‬ﺭﺍ ﻓﺸﺎﺭ ﺩﻫﻴﺪ‪ .‬ﻳﻚ ﺻﻔﺤﻪ ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ‬
‫ﻭﺷﺒﻜﻪ ﻫﺎﻳﻲ ﻛﻪ ﺗﻮﺳﻂ ‪ S5‬ﭘﺸﺘﻴﺒﺎﻧﻲ ﻣﻲ ﺷﻮﻧﺪ ‪ ،‬ﻧﻤﺎﻳﺶ ﺩﺍﺩﻩ ﻣﻲ ﺷﻮﻧﺪ‪.‬ﮔﺰﻳﻨﻪ ‪ PROFIBUS‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﻮﺩﻩ ﻭ‪Ok‬‬

‫ﻛﻨﻴﺪ‪ .‬ﻳﻚ ﭘﻨﺠﺮﻩ ﺑﺎﺯ ﻣﻲ ﺷﻮﺩ ‪ New،‬ﺭﺍ ﺑﺰﻧﻴﺪ ﺗﺎ ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺑﻪ ﻧﺎﻡ )‪ PROFIBUS(1‬ﺍﻳﺠﺎﺩ ﺷﻮﺩ‪.‬‬

‫ﻼ ‪ CPU 314‬ﻭ ‪ CP 342-5‬ﺭﺍ‬

‫ﺑﺮﺍﻱ ‪ Station 300‬ﻳﻚ ‪ CP 300‬ﺑﺎ ﻗﺎﺑﻠﻴﺖ ‪ SEND/RECEIVE‬ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ‪.‬ﻣﺜ ﹰ‬
‫ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ ﻭﺁﻥ ﺭﺍ ﺑﻪ ﺷﺒﻜﻪ )‪ PROFIBUS(1‬ﻛﻪ ﺩﺭ ﻗﺴﻤﺖ ﻗﺒﻞ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻳﺪ ﺍﺿﺎﻓﻪ ﻧﻤﺎﻳﻴﺪ‪.‬ﻳﺎﺩﺁﻭﺭﻱ ﺍﻳﻨﻜﻪ ﺑﺮﺍﻱ‬
‫‪DP‬‬ ‫ﺍﺗﺼﺎﻝ ‪ CP‬ﺑﻪ ﺷﺒﻜﻪ )‪ PROFIBUS(1‬ﺑﺮ ﺭﻭﻱ ﺁﻥ ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ ﻭﺩﺭ ﻗﺴﻤﺖ ‪ Operating Mode‬ﮔﺰﻳﻨﻪ‬
‫‪ Master‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ ﻭﺳﭙﺲ ‪ Save‬ﻛﻨﻴﺪ ‪.‬ﻧﺘﻴﺠﻪ ﻛﺎﺭ ﺭﺍ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ NetPro‬ﻫﻢ ﺑﺒﻴﻨﻴﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٤٦‬‬

‫ﮔﺎﻡ ﺩﻭﻡ‪ :‬ﺍﻳﺠﺎﺩ ‪Connection Table‬‬

‫ﻣﺎﻧﻨﺪ ﻗﺒﻞ ﺑﺎﻳﺪ ﻳﻚ ﻟﻴﻨﻚ ‪ FDL‬ﺑﻴﻦ ﺍﻳﻦ ﺩﻭ ‪ Station‬ﺍﻳﺠﺎﺩ ﻧﻤﺎﻳﻴﺪ‪ .‬ﺑﺮ ﺭﻭﻱ‪ CPU 300‬ﻛﻠﻴﻚ ﻧﻤﺎﻳﻴﺪ ﺗﺎ ﺩﺭ ﭘﺎﻳﻴﻦ‬
‫ﺻﻔﺤﻪ ﺟﺪﻭﻝ ‪ Connection Table‬ﻣﺸﺎﺑﻪ ﻗﺒﻞ ﺑﻪ ﻭﺟﻮﺩ ﺑﻴﺎﻳﺪ‪ .‬ﺑﺮ ﺭﻭﻱ ﻳﻜﻲ ﺍﺯ ﺳﻄﺮ ﻫﺎﻱ ﺍﻳﻦ ﺟﺪﻭﻝ ﺩﺍﺑﻞ ﻛﻠﻴﻚ‬
‫ﻧﻤﺎﻳﻴﺪ ﻣﺎﻧﻨﺪ ﻗﺴﻤﺖ ﻗﺒﻞ ﺩﺭ ﻗﺴﻤﺖ‪ Type‬ﮔﺰﻳﻨﻪ ‪ FDL Connection‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﺎﻳﻴﺪ ﻭﺳﭙﺲ ‪ OK‬ﻛﻨﻴﺪ ﺗﺎ ‪ ID‬ﻭ‬
‫‪ LADDR‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻧﻤﺎﻳﻴﺪ‪ .‬ﺩﺭ ﺿﻤﻦ ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﺩﺭ ﻗﺴﻤﺖ ‪ Address‬ﺩﻭ ﭘﺎﺭﺍﻣﺘﺮ‬
‫‪ LSAP Docal‬ﻭ ‪ LSAP Remote‬ﺭﺍ ﻳﺎﺩﺩﺍﺷﺖ ﻧﻤﺎﻳﻴﺪ ﻛﻪ ﺩﺭ ﺑﺨﺶ ﺑﻌﺪ ﻣﻮﺭﺩ ﺍﺳﺘﻔﺎﺩﻩ ﻗﺮﺍﺭ ﺧﻮﺍﻫﻨﺪ ﮔﺮﻓﺖ‪.‬‬

‫ﮔﺎﻡ ﺳﻮﻡ ‪ :‬ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪ FDL‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﺭﺗﺒﺎﻁ ‪ S7‬ﻭ ‪S5‬‬

‫ﻫﻤﺎﻧﻨﺪ ﻗﺒﻞ ﺑﺎﻳﺪ ﺩﺭﺩﻭﺳﻮﻱ ﺍﻳﻦ ﻟﻴﻨﻚ ﺍﺭﺗﺒﺎﻃﻲ ﻳﻌﻨﻲ ﻫﻢ ﺩﺭ ﺳﻤﺖ ‪ S7‬ﻭﻫﻢ ﺩﺭ ﺳﻤﺖ ‪ S5‬ﺑﺮﻧﺎﻣﻪ ﻣﺮﺑﻮﻁ ﺑﻪ ﺩﺭﻳﺎﻓﺖ ﻭ‬
‫ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺑﻨﻮﻳﺴﻴﺪ‪ .‬ﺩﺭ ﺳﻤﺖ ‪ S7‬ﻛﻪ ﻫﻤﺎﻥ ﺗﻮﺍﺑﻊ ‪ AG_SEND‬ﻭ ‪ AG_RECV‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﻧﺪ‪.‬ﺍﻣﺎ ﺩﺭ‬
‫‪CPU115 U‬‬ ‫ﺳﻤﺖ ‪ S5‬ﺍﺯ ﺗﻮﺍﺑﻊ ‪ HDB-RECEIVE‬ﻭ ‪ HDB-SEND‬ﺑﺎﻳﺪ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺩﺭ ‪ Station S5‬ﻳﻚ‬
‫ﻭﻳﻚ ‪ CP‬ﻛﻪ ﻗﺎﺑﻠﻴﺖ ﭘﺸﺘﻴﺒﺎﻧﻲ ‪ SEND/RECEIVE‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺑﻪ ﻛﺎﺭ ﻣﻲ ﺑﺮﻳﻢ‪.‬‬
‫ﺣﺎﻝ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ STEP 5‬ﺑﺮﻧﺎﻣﻪ‪ Com PROFIBUS‬ﺭﺍ ﺍﺟﺮﺍ ﻧﻤﺎﻳﻴﺪ ﻭﺗﻨﻈﻴﻤﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﺗﺼﺎﻝ ‪ Station S5‬ﺑﻪ‬
‫ﺷﺒﻜﻪ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﻫﻴﺪ ﻭ ﺑﻪ ‪ CPU‬ﻣﺮﺑﻮﻃﻪ ‪ Download‬ﻧﻤﺎﻳﻴﺪ‪.‬ﺗﺬﻛﺮ ﺍﻳﻨﻜﻪ ﺍﻳﻦ ﺗﻨﻈﻴﻤﺎﺕ ﺍﺯ ﺟﻤﻠﻪ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ‪ ،‬ﺁﺩﺭﺱ‬
‫ﺷﺒﻜﻪ ﻭ‪ ..‬ﺑﺎﻳﺪ ﻫﻤﺎﻥ ﻣﻘﺎﺩﻳﺮﻱ ﺭﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﻛﻪ ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ STEP 7‬ﺑﻪ ﺍﻳﻦ ‪ Station‬ﻧﺴﺒﺖ ﺩﺍﺩﻩ ﺑﻮﺩﻳﻢ‪.‬ﺩﺭ ﺿﻤﻦ ﺩﺭ‬
‫ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ‪ LSAP Remote‬ﻭ ‪ LSAP Local‬ﺑﻪ ﻧﺎﻡ ﻫﺎﻱ ‪ SSAP‬ﻭ ‪ DSAP‬ﺷﻨﺎﺧﺘﻪ ﻣﻲ ﺷﻮﻧﺪ ﻟﺬﺍ‪:‬‬
‫)‪DSAP(S5) = LSAP Local (S7‬‬
‫)‪SSAP(S5) = LSAP Remote(S7‬‬
‫‪Techno-Electro.com‬‬

‫‪١٤٧‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫ﺩﺭ ﻣﻮﺭﺩ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Station S5‬ﻧﻴﺰ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﮔﻔﺘﻴﻢ ﺍﺯ ﺗﻮﺍﺑﻊ ‪ HDB-RECEIVE‬ﺑﺎ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ‬
‫‪ FB101‬ﻭ‪ HDB-SEND‬ﺑﺎ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ ‪ FB10‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ STEP5‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﻨﻴﻢ‪.‬‬
‫ﺷﻜﻞ ﺯﻳﺮ ﻣﺜﺎﻟﻲ ﺭﺍ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ‪ S7‬ﻭ ‪ S5‬ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٤٨‬‬

‫‪ ٣-٨‬ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ ‪Multiproject‬‬

‫ﺁﻧﭽﻪ ﺗﺎ ﺍﻳﻨﺠﺎ ﺩﺭ ﻣﻮﺭﺩ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﮔﻔﺘﻪ ﺷﺪ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Station‬ﻫﺎﻱ ﺩﺍﺧﻞ ﻳﻚ ﭘﺮﻭﮊﻩ ﺑﻮﺩ‪ .‬ﻣﻴﺘﻮﺍﻥ ﺍﺭﺗﺒﺎﻁ ﻓﻮﻕ ﺭﺍ‬
‫ﺑﻴﻦ ﭘﺮﻭﮊﻩ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﻛﻪ ﺑﺼﻮﺭﺕ ‪ Multiproject‬ﻫﺴﺘﻨﺪ ﺗﻌﺮﻳﻒ ﻧﻤﻮﺩ‪ .‬ﺑﺮﺍﻱ ﺍﻳﻨﻜﺎﺭ ‪:‬‬
‫ﮔﺎﻡ ﺍﻭﻝ ‪ :‬ﺑﻪ ﺭﻭﺷﻲ ﻛﻪ ﺩﺭ ﺑﺨﺶ ﻗﺒﻞ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪ ﻳﻚ ‪ Multiproject‬ﺷﺎﻣﻞ ﭼﻨﺪ ﭘﺮﻭﮊﻩ ﻛﻪ ﻫﻤﮕﻲ ﺩﺍﺭﺍﻱ‬
‫ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ Master‬ﻭ ﺑﻪ ‪ Profibus‬ﻣﺘﺼﻞ ﻫﺴﺘﻨﺪ ﺍﻳﺠﺎﺩ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫ﮔﺎﻡ ﺩﻭﻡ ‪ :‬ﺩﺭ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ Master‬ﻛﺎﺭﺕ ‪ CP‬ﻣﻨﺎﺳﺐ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﻴﻢ‬
‫ﮔﺎﻡ ﺳﻮﻡ ‪ :‬ﺩﺭ ﺑﺮﻧﺎﻣﻪ ‪ Netpro‬ﺑﺮﺍﻱ ﻳﻜﻲ ﺍﺯ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺭﻭﻱ ﺳﻄﺮ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Connection Table‬ﻛﻠﻴﻚ ﻛﺮﺩﻩ‬
‫ﺗﺎ ﭘﻨﺠﺮﻩ ﺯﻳﺮ ﺑﺎﺯ ﺷﻮﺩ‪.‬‬

‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ ‪ :‬ﺍﺯ ﻗﺴﻤﺖ ‪ In the multiproject‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻩ ﻭ ﺍﺯ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ﺁﻥ ﭘﺮﻭﮊﻩ ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻧﺘﺨﺎﺏ‬
‫ﻛﺮﺩﻩ ﺳﭙﺲ ﺩﺭ ﺁﻥ ﭘﺮﻭﮊﻩ ‪ Station‬ﻣﻮﺭﺩ ﻧﻈﺮ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬‬
‫ﮔﺎﻡ ﭘﻨﺠﻢ‪ :‬ﭘﻨﺠﺮﻩ ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Properties‬ﺑﺎﺯ ﻣﻴﺸﻮﺩ ‪ .‬ﺷﺒﻴﻪ ﺭﻭﺍﻝ ﻗﺒﻞ ‪ ID‬ﻭ ‪ LADRR‬ﺭﺍ ﺩﺭ ﺻﻮﺭﺕ ﻟﺰﻭﻡ ﺗﻨﻈﻴﻢ‬
‫ﺳﭙﺲ ﻳﺎﺩﺩﺍﺷﺖ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫‪CPU‬‬ ‫ﮔﺎﻡ ﺷﺸﻢ ‪ :‬ﺍﻛﻨﻮﺍﻥ ﺍﮔﺮ ﺩﺭ ‪ NetPro‬ﭘﺮﻭﮊﻩ ﻣﻮﺭﺩ ﻧﻈﺮ ) ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﭘﺮﻭﮊﻩ ‪ (830427‬ﺭﺍ ﺑﺎﺯ ﻛﻨﻴﻢ ﻭ ﺭﻭﻱ‬
‫ﻛﻠﻴﻚ ﻛﺮﺩﻩ ﺗﺎ ﺟﺪﻭﻝ ‪ Connection‬ﺑﺎﺯ ﺷﻮﺩ ﻣﻲ ﺑﻴﻨﻴﻢ ﻛﻪ ﻳﻚ ﺳﻄﺮ ﺩﺭ ﺁﻥ ﺍﻳﺠﺎﺩ ﺷﺪﻩ ﺍﺳﺖ ﻭ ﺑﺎ ﻛﻠﻴﻚ ﺭﻭﻱ ﺁﻥ‬
‫‪ ID‬ﻭ ‪ LADRR‬ﻣﺸﺨﺺ ﺍﺳﺖ‪.‬‬
‫ﺍﺩﺍﻣﻪ ﻛﺎﺭ ﺑﺮﺍﻱ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺷﺒﻴﻪ ﻗﺒﻞ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٤٩‬‬ ‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬

‫‪ ٤-٨‬ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺑﺎ ‪Unknown Project‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺑﺪﻭﻥ ﺍﻳﻨﻜﻪ ﻻﺯﻡ ﺑﺎﺷﺪ ﺁﺩﺭﺱ ‪ Node‬ﻭ ‪ LSAP‬ﺍﻳﺴﺘﮕﺎﻩ ﻣﻘﺎﺑﻞ ﺭﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﺻﺮﻓﹰﺎ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬
‫ﻳﻚ ﻧﺎﻡ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺭﺍ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺍﻳﻦ ﻛﺎﺭ ﺩﺭ ﺩﺍﺧﻞ ﻳﻚ ‪ Multiproject‬ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ‪ .‬ﺩﺭ ﻭﺍﻗﻊ ﺑﻪ ﺍﻳﻦ ﺭﻭﺵ‬
‫ﺍﺗﺼﺎﻝ ﻓﻮﻕ ﺭﺍ ﺑﺮﺍﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺑﻌﺪﻱ ﺭﺯﺭﻭ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫ﺑﺮﺍ ﻱ ﺍﻳﻦ ﻛﺎﺭ ﻣﺎﻧﻨﺪ ﺭﻭﺵ ﺫﻛﺮ ﺷﺪﻩ ﺩﺭ ﺻﻔﺤﻪ ﻗﺒﻞ ﮔﺎﻡ ﻫﺎﻱ ﺍﻭﻝ ﻭ ﺩﻭﻡ ﻭ ﺳﻮﻡ ﺭﺍ ﺑﺮ ﻣﻴﺪﺍﺭﻳﻢ ﺳﭙﺲ‪:‬‬
‫‪ In Unknown Project‬ﺭﺍ ﺍﻧﺘﺨﺎﺏ‬ ‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ ‪ :‬ﺩﺭ ﭘﻨﺠﺮﻩ ‪) Connection Partner‬ﺷﻜﻞ ﺻﻔﺤﻪ ﻗﺒﻞ(‬
‫ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫ﮔﺎﻡ ﭘﻨﺠﻢ ‪ :‬ﭘﺲ ﺍﺯ ‪ OK‬ﻛﺮﺩﻥ ﺩﺭ ﭘﻨﺠﺮﻩ ‪ Properties‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻳﻚ ﻧﺎﻡ ‪ Reference‬ﺑﺪﻟﺨﻮﺍﻩ ﻭﺍﺭﺩ‬
‫ﻣﻴﻜﻨﻴﻢ ) ﻣﺜﻼ ‪ (Ali‬ﺍﻳﻦ ﻧﺎﻡ ﻛﻠﻴﺪ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﺍﻳﻦ ﭘﺮﻭﮊﻩ ﻭ ﭘﺮﻭﮊﻩ ﺑﻌﺪﻱ ﺍﺳﺖ‪ .‬ﺗﻮﺟﻪ ﺷﻮﺩ ﺍﮔﺮ ﺩﺭ ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﺑﻪ ﺑﺨﺶ‬
‫‪ Address‬ﻣﺮﺍﺟﻌﻪ ﻛﻨﻴﻢ ﺧﻮﺍﻫﻴﻢ ﺩﻳﺪ ﻛﻪ ﺁﺩﺭﺱ ‪ Remote‬ﻓﻌ ﹰ‬
‫ﻼ ﺧﺎﻟﻲ ﻭ ﻏﻴﺮ ﻓﻌﺎﻝ ﺍﺳﺖ‪.‬‬

‫ﮔﺎﻡ ﺷﺸﻢ ‪ :‬ﺑﺮﺍﻱ ﭘﺮﻭﮊﻩ ﺩﻳﮕﺮ ﻧﻴﺰ ﮔﺎﻡ ﭼﻬﺎﺭﻡ ﻭ ﭘﻨﺠﻢ ﺭﺍ ﺑﺮﺩﺍﺷﺘﻪ ﻭ ﺍﺳﻢ ﺩﻟﺨﻮﺍﻫﻲ ) ﻣﺎﻧﻨﺪ ‪ ( Reza‬ﺑﻪ ﻋﻨﻮﺍﻥ‬
‫‪ reference‬ﺍﺭﺗﺒﺎﻁ ﻣﻌﺮﻓﻲ ﻣﻴﻜﻨﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪PROFIBUS‬‬ ‫ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ‬ ‫‪١٥٠‬‬

‫ﮔﺎﻡ ﻫﻔﺘﻢ ‪ :‬ﺩﺭ ‪ NetPro‬ﺍﺯﻣﻨﻮﻱ ‪ Edit > Merge Connection‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩﻩ ﺗﺎ ﭘﻨﺠﺮﻩ ﺯﻳﺮ ﺑﺎﺯ ﺷﻮﺩ‪ .‬ﺩﺭ ﺩﻭﻃﺮﻑ‬
‫ﺍﻳﻦ ﭘﻨﺠﺮﻩ ﺩﻭ ﻧﺎﻡ ‪ reference‬ﺭﺍ ﻣﻴﺒﻴﻨﻴﻢ‪ .‬ﺑﺎ ﻛﻠﻴﺪ ‪ Assign‬ﺁﻧﻬﺎ ﺭﺍ ﺑﻪ ﻫﻢ ﻣﺮﺑﻮﻁ ﻣﻲ ﻛﻨﻴﻢ‪.‬ﭘﺲ ﺍﺯ ﺁﻥ ﻣﻴﺒﻴﻨﻴﻢ ﻛﻪ ﺳﻄﺮ‬
‫ﺟﺪﻳﺪﻱ ﺩﺭ ﭘﻨﺠﺮﻩ ﭘﺎﻳﻴﻨﻲ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﺑﺎ ﻛﻠﻴﻚ ﺭﻭﻱ ﺁﻥ ﻭ ﺳﭙﺲ ﻛﻠﻴﻚ ﺭﻭﻱ ‪ Merge‬ﺍﻳﻦ ﺩﻭ ﺍﺗﺼﺎﻝ ﺭﺍ ﺑﻪ ﻫﻢ ﻟﻴﻨﻚ‬
‫ﻣﻲ ﻧﻤﺎﻳﻴﻢ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺍﺗﻤﺎﻡ ‪ Merge‬ﻛﺮﺩﻥ ﺍﮔﺮ ﺑﻪ ﺟﺪﻭﻝ ‪ Connection‬ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ‪ CPU‬ﻫﺎ ﺑﺮ ﮔﺮﺩﻳﻢ ﺧﻮﺍﻫﻴﻢ ﺩﻳﺪ ﻛﻪ ﺩﺭ‬
‫ﺑﺨﺶ ‪ Address‬ﺑﻪ ‪ Remote‬ﺁﺩﺭﺱ ﺍﺧﺘﺼﺎﺹ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺍﺩﺍﻣﻪ ﻛﺎﺭ ﺑﺮﺍﻱ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺷﺒﻴﻪ ﻗﺒﻞ ﺍﺳﺖ‪.‬‬

‫ﺗﺬﻛﺮ‪:‬‬
‫ﺩﺭ ﺗﻤﺎﻡ ﻣﻮﺍﺭﺩ ﭘﺲ ﺍﺯ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ‪ FDL‬ﭼﻚ ﺳﺎﺯﮔﺎﺭﻱ ﺍﺟﺰﺍ ﻭ ﺩﺍﻧﻠﻮﺩ ﺑﻪ ‪ PLC‬ﻫﺎ ﻧﺒﺎﻳﺪ ﻓﺮﺍﻣﻮﺵ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﻧﻬﻢ – ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺷﺒﻜﻪ ‪PROFIBUS FMS‬‬

‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫ﺷﻨﺎﺧﺖ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١-٩‬‬

‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪٢-٩‬‬
‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪۳-۹‬‬
‫ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪ ۴-۹‬ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ‬
‫‪Techno-Electro.com‬‬

‫ﺷﻨﺎﺧﺖ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١٥٢‬‬

‫ﻣﻘﺪﻣﻪ‬
‫ﺩﺭ ﻣـﻮﺭﺩ ‪ FMS‬ﻭ ﻭﻳﮋﮔـﻴﻬﺎﻱ ﺁﻥ ﻗـﺒ ﹰ‬
‫ﻼ ﺑـﻪ ﺍﺧﺘﺼـﺎﺭ ﻣﻄﺎﻟﺒـﻲ ﺑـﻴﺎﻥ ﺷـﺪ‪ .‬ﺩﺭ ﺍﻳـﻦ ﺑﺨـﺶ ﺑـﻪ ﻧﺤـﻮﻩ ﭘـﻴﻜﺮ ﺑـﻨﺪﻱ ﻭ ﺑﺮﻧﺎﻣﻪ‬
‫ﻧﻮﻳﺴــﻲ ﺷــﺒﻜﻪ ‪ FMS‬ﺗﻮﺳــﻂ‪ STEP7‬ﻣــﻲ ﭘــﺮﺩﺍﺯﻳﻢ‪ .‬ﻗــﺒﻞ ﺍﺯ ﻫــﺮ ﭼــﻴﺰ ﺑــﺎﻳﺪ ﺗﻮﺟــﻪ ﺩﺍﺷــﺖ ﻛــﻪ ﺑــﺮﺍﻱ ﺍﺭﺗــﺒﺎﻁ ‪ FMS‬ﻧــﻴﺎﺯ‬
‫ﺑــﻪ ﻛــﺎﺭﺕ ‪ CP‬ﺩﺍﺭﻳــﻢ ﻭﻻﺯﻡ ﺍﺳــﺖ ﺍﻳــﻦ ﻛــﺎﺭﺕ ﺭﺍ ﺍﺯ ﺯﻳــﺮ ﻣﺠﻤﻮﻋــﻪ ﻛﺎﺭﺗﻬــﺎﻱ ‪ PROFIBUS‬ﺩﺭ ‪ Station‬ﻣــﻮﺭﺩ‬
‫ﻧﻈــﺮ ﺍﻧــﺘﺨﺎﺏ ﻛــﺮﺩﻩ ﻭﺩﺭ ﺭﻙ ﻣــﺮﺑﻮﻃﻪ ﺩﺭ ‪ Hwconfig‬ﻗــﺮﺍﺭ ﺩﻫــﻴﻢ ‪ .‬ﺍﻳــﻦ ﻛــﺎﺭﺕ ‪ CP‬ﺑــﺎﻳﺪ ﻗﺎﺑﻠﻴــﺖ ‪ FMS‬ﺭﺍ ﺩﺍﺷــﺘﻪ‬
‫ﺑﺎﺷــﺪ ﻛــﻪ ﺍﻳــﻦ ﻣﻮﺿــﻮﻉ ﺑــﺎ ﻛﻠــﻴﻚ ﻛــﺮﺩﻥ ﺭﻭﻱ ﻛــﺎﺭﺕ ﺩﺭ ﭘــﻨﺠﺮﻩ ﻛﺎﺗــﺎﻟﻮﮒ ﻭ ﻣﺸــﺎﻫﺪﻩ ﺗﻮﺿــﻴﺤﺎﺕ ﺯﻳــﺮ ﭘــﻨﺠﺮﻩ‬
‫ﻣﺸﺨﺺ ﻣﻲ ﮔﺮﺩﺩ‪.‬‬
‫ﻛﺎﺭﺗﻬﺎﻳﻲ ﻛﻪ ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﻗﺎﺑﻞ ﺍﻧﺘﺨﺎﺏ ﻫﺴﺘﻨﺪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫‪CP343-5‬‬ ‫‪ S7-300‬ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ‬ ‫•‬

‫‪CP443-5 Basic‬‬ ‫‪ S7-400‬ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ‬ ‫•‬

‫‪ S5‬ﺑﺎ ﻛﺎﺭﺕ ‪CP 5431‬‬ ‫•‬

‫‪ CP5613‬ﻭ ‪CP5614‬‬ ‫‪ PC‬ﺑﺎ ﻛﺎﺭﺗﻬﺎﻱ‬ ‫•‬

‫‪ ET200U‬ﺑﺎ ‪IM318C‬‬ ‫•‬

‫ﻭﺳــﺎﻳﻞ ﺳــﺎﺯﻧﺪﮔﺎﻥ ﺩﻳﮕــﺮ ﺑــﻪ ﺟــﺰ ﺯﻳﻤــﻨﺲ ﻛــﻪ ﻗﺎﺑﻠﻴــﺖ ‪ FMS‬ﺩﺍﺷــﺘﻪ ﺑﺎﺷــﻨﺪ ﺑــﺎ ﻭﺍﺭﺩ ﻛــﺮﺩﻥ ﻓــﺎﻳﻞ ‪ GSD‬ﻳــﺎ ‪ GSE‬ﺑــﻪ‬
‫ﻼ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪ ﺑﻪ ﭘﻨﺠﺮﻩ ﻛﺎﺗﺎﻟﻮﮒ ﺍﺿﺎﻓﻪ ﻣﻲ ﺷﻮﻧﺪ ﻭﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﻫﺴﺘﻨﺪ‪.‬‬
‫ﺑﺮﻧﺎﻣﻪ ﻣﻄﺎﺑﻖ ﺭﻭﺍﻟﻲ ﻛﻪ ﻗﺒ ﹰ‬

‫‪ ١-٩‬ﺷﻨﺎﺧﺖ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫ﺍﺗﺼــﺎﻝ ‪ FMS‬ﺍﺭﺗــﺒﺎﻁ ﺑﻴــﻦ ‪ Master‬ﺭﺍ ﺍﺯ ﻃــﺮﻳﻖ ﺗﻜﻨــﻴﻚ ‪ TokenPass‬ﻓــﺮﺍﻫﻢ ﻣــﻲ ﻛــﻨﺪ‪ FMS .‬ﻭ ‪ DP‬ﻣﻴﺘﻮﺍﻧــﻨﺪ‬
‫ﺭﻭﻱ ﻳـﻚ ‪ Media‬ﻗـﺮﺍﺭ ﮔـﻴﺮﻧﺪ ﻳﻌﻨـﻲ ﺑـﺎﺱ ﺷـﺒﻜﻪ ﻣـﻲ ﺗﻮﺍﻧـﺪ ﺑـﺮﺍﻱ ﻫـﺮ ﺩﻭﻱ ﺁﻧﻬـﺎ ﻣﺸـﺘﺮﻙ ﺑﺎﺷـﺪ ‪ .‬ﺑـﻪ ﻫﻤـﺎﻥ ﺻﻮﺭﺕ‬
‫ﻛﻪ ﺍﺭﺗﺒﺎﻁ ‪ DP‬ﻭ ‪ FDL‬ﺭﺍ ﻫﻤﺰﻣﺎﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﻛﺮﺩﻳﻢ‪.‬‬

‫ﻧﻜﺘﻪ ﺍﻱ ﻛﻪ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﺑﺎﻳﺪ ﻣﺪ ﻧﻈﺮ ﻗﺮﺍﺭ ﮔﻴﺮﺩ ﻣﻔﻬﻮﻡ ﺩﻭ ﻛﻠﻤﺔ ‪ Client‬ﻭ ‪ Server‬ﺍﺳﺖ‪ Client.‬ﻋﻀﻮﻱ ﺍﺳﺖ ﻛﻪ‬
‫ﺩﺭﺧﻮﺍﺳﺖ ﺳﺮﻭﻳﺲ ﻣﻲ ﻛﻨﺪ ﻭ ‪ Server‬ﻋﻀﻮﻱ ﺍﺳﺖ ﻛﻪ ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﺭﺍ ﺍﺭﺍﺋﻪ ﻣﻲ ﺩﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٥٣‬‬ ‫ﺷﻨﺎﺧﺖ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫‪Client‬‬ ‫‪Server‬‬

‫‪Master‬‬ ‫ﻣﻘﻬﻮﻡ ‪ Client/Server‬ﺑﺎ ﻣﻔﻬﻮﻡ ‪ Master/ Slave‬ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ﺩﺭ ‪ Master/Slave‬ﺍﮔﺮ ﭼﻪ‬

‫ﺩﺭﺧﻮﺍﺳﺖ ﻣﻲ ﻛﻨﺪ ﻭ ‪ Slave‬ﭘﺎﺳﺦ ﻣﻲ ﺩﻫﺪ ﻭﻟﻲ ﺑﺎﺱ ﻫﻤﻴﺸﻪ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ‪ Master‬ﺍﺳﺖ ﻭ ‪ Slave‬ﺑﺪﻭﻥ ﺍﺟﺎﺯﺓ‬
‫‪ Master‬ﻧﻤﻲ ﺗﻮﺍﻧﺪ ﺁﻥ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭﺑﮕﻴﺮﺩ ‪ .‬ﻭﻟﻲ ﺩﺭ ‪ Client/Server‬ﻫﻢ ‪ Client‬ﻭ ﻫﻢ ‪ Server‬ﺣﻖ ﻣﺴﺎﻭﻱ ﺑﺮﺍﻱ‬
‫ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻦ ﺑﺎﺱ ﺩﺍﺭﻧﺪ ﺍﮔﺮ ﭼﻪ ﺑﻴﺸﺘﺮ ‪ Client‬ﺑﻪ ﺍﻳﻦ ﻛﺎﺭ ﻣﺒﺎﺩﺭﺕ ﻣﻲ ﻛﻨﺪ ‪ .‬ﺩﺭ ‪ FMS‬ﺩﻭ ﻭﺳﻴﻠﻪ ﺍﻱ ﻛﻪ ﺑﺎ ﻫﻢ ﺍﺭﺗﺒﺎﻁ‬
‫ﺑﺮﻗﺮﺍﺭ ﻣﻲ ﻛﻨﻨﺪ ﺑﻪ ﻋﻨﻮﺍﻥ ‪ (Virtual Field Device ) VFD‬ﺷﻨﺎﺧﺘﻪ ﻣﻲ ﺷﻮﻧﺪ‪.‬ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﻭ ‪ PLC‬ﺷﻜﻞ ﺯﻳﺮ ﻛﻪ‬
‫ﻳﻜﻲ ‪ S7-300‬ﻭ ﺩﻳﮕﺮﻱ ‪ S7-400‬ﺍﺳﺖ ﻫﺮ ﺩﻭ ‪ VFD‬ﻫﺴﺘﻨﺪ‪:‬‬

‫ﺩﺭ ﺍﺗﺼﺎﻝ ‪ FMS‬ﻛﺎﺭﺕ ‪ CP‬ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﺮﺍﻱ ﻫﺮ ‪ job‬ﺣﺪﺍﻛﺜﺮ ‪ ۲۴۱‬ﺑﺎﻳﺖ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﻣﻨﺘﻘﻞ ﻛﻨﺪ ﻛﻪ ﺑﻪ ﺍﻳﻦ ﻳﻚ ﺑﺴﺘﺔ‬
‫‪ (Protocol Data Unit) PDU‬ﻣﻲ ﮔﻮﻳﻨﺪ ‪ .‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﺍﮔﺮ ﭼﻪ ﺑﺎ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺷﺒﻴﻪ ﺍﺳﺖ ﻭﻟﻲ ﻳﻚ ﻓﺮﻕ ﺍﺳﺎﺳﻲ ﺑﻴﻦ‬
‫‪ FDL‬ﻭ ‪ FMS‬ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻭﺁﻥ ﺍﻳﻨﻜﻪ ﺩﺭ ‪ FMS‬ﺩﺭ ﺳﻤﺖ ‪ Server‬ﻳﻚ ﺩﻳﺘﺎ ﺑﻼﻙ ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﻨﺒﻊ ﺍﻃﻼﻋﺎﺗﻲ ﺑﺮﺍﻱ ﺧﻮﺍﻧﺪﻥ‬
‫ﻭﻧﻮﺷﺘﻦ ﻣﻌﺮﻓﻲ ﻣﻲ ﮔﺮﺩﺩ ﻭ ‪ Client‬ﺍﺭ ﺁﻥ ﻣﻲ ﺧﻮﺍﻧﺪ ﻳﺎ ﺩﺭ ﺁﻥ ﻣﻲ ﻧﻮﻳﺴﺪ‪ .‬ﺩﺭ ﺳﻤﺖ ‪ Client‬ﻧﻴﺰ ﺩﻳﺘﺎ ﺑﻼﻙ ﻫﺎﻳﻲ ﻭﺟﻮﺩ‬
‫ﺩﺍﺭﺩ ﻭﻟﻲ ﺑﻪ ﻃﻮﺭ ﻣﻌﻤﻮﻝ ‪ Server‬ﻧﻴﺎﺯﻱ ﺑﻪ ﻧﻮﺷﺘﻦ ﻳﺎ ﺧﻮﺍﻧﺪﻥ ﺁﻧﻬﺎ ﻧﺪﺍﺭﺩ ﺍﮔﺮ ﭼﻪ ﺍﻳﻦ ﺍﻣﺮ ﺑﺮﺍﻳﺶ ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ﺍﺯ ﺍﻳﻦ‬
‫ﻻ ﻧﻴﺎﺯﻱ ﺑﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻧﺪﺍﺭﻳﻢ ﻭ ﺑﺮﻧﺎﻣﻪ ﻓﻘﻂ ﺩﺭ ﺳﻤﺖ ‪ Client‬ﻧﻮﺷﺘﻪ ﻣﻲ ﺷﻮﺩ ‪.‬ﺩﺭ ﺣﺎﻟﻴﻜﻪ‬
‫ﺭﻭ ﺩﺭ ﺳﻤﺖ ‪ Server‬ﻣﻌﻤﻮ ﹰ‬
‫ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺭ ﻫﺮ ﺩﻭﻃﺮﻑ ﻧﻴﺎﺯ ﺑﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺩﺍﺭﻳﻢ ‪ .‬ﺩﺭ ‪ FMS‬ﺩﺭ ﺳﻤﺖ ‪ Server‬ﺻﺮﻓﹰﺎ ﻻﺯﻡ ﺍﺳﺖ ﺩﻳﺘﺎ ﺑﻼﻙ‬
‫ﻣﺮﺟﻊ ﺭﺍ ﺑﻪ ﺷﻜﻠﻲ ﻛﻪ ﺍﺻﻄﻼﺣﹰﺎ ﺑﻪ ﺁﻥ ﺍﻳﻨﺪﻛﺲ ﻛﺮﺩﻥ ﻣﻲ ﮔﻮﻳﻨﺪ ﻣﺸﺨﺺ ﻛﻨﻴﻢ ﺗﺎ ﺩﺭ ﺳﻤﺖ ‪ Client‬ﻗﺎﺑﻞ ﺷﻨﺎﺳﺎﻳﻲ ﺑﺎﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١٥٤‬‬

‫ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﻛﺎﺭﺕ ‪ CP‬ﻭﻇﺎﻳﻒ ﺯﻳﺮ ﺭﺍ ﺑﻌﻬﺪﻩ ﺩﺍﺭﺩ‪:‬‬

‫ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺩﺭﻳﺎﻓﺖ ﺩﻳﺘﺎ ﺍﺯ ‪ CPU‬ﻭ ﺗﺒﺪﻳﻞ ﺁﻥ ﺍﺯ ﻓﺮﻣﺖ ‪ S7‬ﺑﻪ ﻓﺮﻣﺖ ‪ FMS‬ﻭ ﺍﺭﺳﺎﻝ ﺑﻪ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ‪.‬‬ ‫‪.١‬‬
‫ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﺩﺭﻳﺎﻓﺖ ﺩﻳﺘﺎ ﺍﺯ ﺷﺒﻜﻪ ﭘﺮﻭﻓﻲ ﺑﺎﺱ ﻭ ﺗﺒﺪﻳﻞ ﺁﻥ ﺍﺯ ﻓﺮﻣﺖ ‪ FMS‬ﺑﻪ ﻓﺮﻣﺖ ﺧﺎﺹ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ‬ ‫‪.٢‬‬
‫ﺑﺮﺍﻱ ﻭﺳﻴﻠﻪ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮ ﮔﻴﺮﻧﺪﻩ ﻳﻚ ‪ PLC‬ﺍﺯ ﻧﻮﻉ ‪ S7‬ﺑﺎﺷﺪ ﻛﺪﻫﺎﻱ ﻣﺰﺑﻮﺭ ﺑﻪ ﻓﺮﻣﺖ ‪ S7‬ﺗﺒﺪﻳﻞ ﻣﻲ ﺷﻮﺩ ‪.‬‬
‫ﻧﺤﻮﻩ ﺗﺒﺪﻳﻞ ﻓﺮﻣﺘﻬﺎﻱ ‪ S7‬ﻭ ‪ FMS‬ﺑﻪ ﻳﻜﺪﻳﮕﺮ ﺩﺭ ﺿﻤﻴﻤﻪ ‪ ٤‬ﺁﻣﺪﻩ ﺍﺳﺖ ‪.‬‬

‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪٢-٩‬‬

‫ﻼ ﺩﺭ ﻣﻮﺭﺩ ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺍﺩﻩ ﺷﺪ ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻪ ﺳﻬﻮﻟﺖ ﻧﺴﺒﺖ ﺑﻪ ﭘﻴﻜﺮ‬
‫ﺑـﺎ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﻗﺒ ﹰ‬
‫ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﺍﻗﺪﺍﻡ ﻛﻨﺪ ‪ .‬ﺭﻭﺵ ﻛﺎﺭ ﻣﺸﺎﺑﻪ ‪ FDL‬ﺍﺳﺖ ﺑﻨﺎﺑﺮﺍﻳﻦ ﺍﺯ ﺗﻮﺿﻴﺤﺎﺕ ﺗﻜﺮﺍﺭﻱ ﺧﻮﺩﺩﺍﺭﻱ ﻣﻲ ﻛﻨﻴﻢ ﻭﺻﺮﻓﹰﺎ ﺑﻪ‬
‫ﻋﻨﺎﻭﻳﻦ ﺁﻧﻬﺎ ﺍﺷﺎﺭﻩ ﻣﻲ ﻛﻨﻴﻢ ‪ ،‬ﮔﺎﻣﻬﺎﻳﻲ ﻛﻪ ﺑﺎﻳﺪ ﺑﺮﺩﺍﺷﺘﻪ ﺷﻮﺩ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ‪:‬‬
‫ﮔﺎﻡ ﺍﻭﻝ‪:‬‬
‫ﺍﻳﺠﺎﺩ ‪ Station‬ﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﻭ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻛﺎﺭﺕ ﻫﺎﻱ ﺁﻥ ﺗﻮﺳﻂ ‪. Hwconfig‬ﺑﻬﺘﺮ ﺍﺳﺖ ﺩﺭ ﻧﺎﻡ ‪ Station‬ﻫﺎ ﺍﺯ‬
‫ﻛﻠﻤﺎﺕ ‪ Server‬ﻭ ‪ Client‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ ﺗﺎ ﺳﺮﻳﻌﺘﺮ ﻭ ﺑﺪﻭﻥ ﺧﻄﺎ ﺑﺘﻮﺍﻥ ﻣﺮﺍﺣﻞ ﺑﻌﺪﻱ ﺭﺍ ﺍﻧﺠﺎﻡ ﺩﺍﺩ‪.‬‬

‫ﮔﺎﻡ ﺩﻭﻡ‪:‬‬
‫ﻭﺍﺭﺩ ﻛﺮﺩﻥ ﻛﺎﺭﺕ ‪ CP‬ﻣﻨﺎﺳﺐ ﺑﺎ ﻗﺎﺑﻠﻴﺖ ‪ FMS‬ﺩﺭ ‪ Station‬ﻫﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺗﻮﺳﻂ ‪.Hwconfig‬‬

‫ﮔﺎﻡ ﺳﻮﻡ‪:‬‬
‫ﺍﺟﺮﺍﻱ ‪ Netpro‬ﻭﺍﺗﺼﺎﻝ ﻛﺎﺭﺗﻬﺎﻱ ‪ CP‬ﺑﻪ ﺷﺒﻜﻪ ‪. PROFIBUS‬‬

‫ﮔﺎﻡ ﭼﻬﺎﺭﻡ‪:‬‬
‫ﺩﺍﺑﻞ ﻛﻠﻴﻚ ﺭﻭﻱ ﺳﻄﺮ ‪ Connection table‬ﻳﻜﻲ ﺍﺯ ‪ Station‬ﻫﺎ ﻭﺍﻧﺘﺨﺎﺏ ﺍﺭﺗﺒﺎﻁ ﺍﺯ ﻧﻮﻉ ‪FMS‬‬
‫‪Techno-Electro.com‬‬

‫‪١٥٥‬‬ ‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫ﮔﺎﻡ ﭘﻨﺠﻢ‪:‬‬
‫ﻳﺎﺩﺩﺍﺷـﺖ ﻛـﺮﺩﻥ ‪ ID‬ﺩﺍﺩﻩ ﺷـﺪﻩ ﺩﺭ ﭘـﻨﺠﺮﺓ ‪ FMS Connection‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﺸﺎﻫﺪﻩ ﻣﻲ ﺷﻮﺩ ﺩﺭ‬
‫ﺍﻳﻨﺠﺎ ‪ ID‬ﻳﻚ ‪ DoubleWord‬ﺍﺳﺖ ﻛﻪ ﺍﺯ ﺗﺮﻛﻴﺐ ‪ CREF+LADDR‬ﺑﺪﺳﺖ ﻣﻲ ﺁﻳﺪ‪ .‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ‪LADDR‬‬

‫ﻣﻌـﺎﺩﻝ ﻫﮕﺰ ﺁﺩﺭﺱ ﺑﻴﺲ ﻛﺎﺭﺕ ‪ CP‬ﺩﺭ ‪ S7-300‬ﺍﺳﺖ‪ .‬ﺑﺮﺍﻱ ‪ S7-400‬ﺑﻪ ﺟﺎﻱ ‪ LADDR‬ﻛﻠﻤﺔ ‪ KBUSID‬ﻇﺎﻫﺮ ﻣﻲ‬
‫ﺷﻮﺩ ﻛﻪ ﻫﻤﺎﻥ ﺁﺩﺭﺱ ﭘﺎﻳﻪ ﻛﺎﺭﺕ ﺍﺳﺖ‪.‬‬

‫ﺍﮔـﺮ ﺭﻭﻱ ‪ Option‬ﺩﺭ ﭘـﻨﺠﺮﻩ ﻓـﻮﻕ ﻛﻠـﻴﻚ ﻛﻨـﻴﻢ ﭘﻨﺠﺮﺓ ﺩﻳﮕﺮﻱ ﻇﺎﻫﺮ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺩﺭ ﺑﺨﺶ ‪ Communication‬ﺩﺭ‬
‫ﻗﺴـﻤﺖ ‪ Type Of Connection‬ﻧـﻮﻉ ﺍﺭﺗـﺒﺎﻁ ﻛﻠﻤﺔ ‪ MMAC‬ﻳﺎ ﻛﻠﻤﺔ ﺩﻳﮕﺮﻱ ﻣﺎﻧﻨﺪ ‪ MSAC,MSCY,BRCT‬ﻇﺎﻫﺮ‬
‫ﻣﻲ ﺷﻮﺩ ﻛﻪ ﻣﻔﻬﻮﻡ ﺁﻥ ﺩﺭﺷﻜﻞ ﺯﻳﺮ ﻭ ﺟﺪﻭﻝ ﺻﻔﺤﻪ ﺑﻌﺪ ﺁﻭﺭﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١٥٦‬‬

‫ﺍﺭﺗـﺒﺎﻁ ﺩﻭﻃـﺮﻓﻪ ﺑﻴـﻦ ﺩﻭ ‪ Master‬ﻳﻌﻨـﻲ‬

‫‪ Write‬ﻭ ‪ Read‬ﺩﺭ ﻫـﺮ ﺩﻭ ﺟﻬـﺖ ﻭ ﺑـﺎ‬
‫‪MMAC‬‬
‫‪ Acknowledge‬ﺍﻣﻜــﺎﻥ ﭘﺬﻳــﺮ ﺍﺳــﺖ‪.‬‬
‫‪Master-Master‬‬
‫‪ Report‬ﻧـﻴﺰ ﺑﺮﺍﻱ ﻫﺮﺩﻭ ﻋﻀﻮ ﻭﺑﺼﻮﺭﺕ‬ ‫‪Acyclic‬‬
‫‪Connection‬‬
‫ﺳﺮﻭﻳﺲ ‪ SDN‬ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ‪.‬‬

‫ﺩﺭ ﺍﻳﻨﺤﺎﻟــﺖ ﻓﻘــﻂ ‪ Master‬ﺍﺳــﺖ ﻛــﻪ‬

‫‪MSAC‬‬
‫ﺍﺟـــﺎﺯﻩ ‪ Write,Read,Report‬ﺭﺍ ﺩﺍﺭﺩ‪.‬‬
‫ﺗﻨﻈـﻴﻢ ﺍﻳـﻦ ﺍﺭﺗـﺒﺎﻁ ﻳﻜﻄـﺮﻓﻪ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ‬ ‫‪Master-Slave‬‬
‫‪Acyclic‬‬
‫‪Connection‬‬
‫ﺁﻣﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺍﻳﻨﺤﺎﻟــﺖ ﻧــﻴﺰ ﺷــﺒﻴﻪ ‪ MSAC‬ﺍﺳــﺖ ﻭﻟــﻲ‬

‫‪Master‬‬ ‫‪ Slave‬ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ﺻﻮﺭﺗﻲ ﻛﻪ‬ ‫‪MSAC-SI‬‬

‫ﺑﻪ ﺍﻭ ﺍﺟﺎﺯﻩ ﺑﺪﻫﺪ ‪ Report‬ﺑﻔﺮﺳﺘﺪ‪.‬‬ ‫‪Master-Slave‬‬

‫‪Acyclic‬‬
‫‪Connection with‬‬
‫‪Slave Initiative‬‬

‫ﺍﻳﻨﺤﺎﻟﺖ ﺷﺒﻴﻪ ‪ MSAC‬ﺍﺳﺖ ﺑﺎ ﺍﻳﻦ ﺗﻔﺎﻭﺕ‬

‫‪MSCY‬‬
‫‪Master-Slave‬‬
‫ﻛﻪ ﺍﺭﺗﺒﺎﻁ ﺳﻴﻜﻠﻲ ﺍﺳﺖ‪.‬‬
‫‪cyclic Connection‬‬
‫‪without‬‬
‫‪Slave Initiative‬‬

‫‪ Report‬ﺍﺯ ﻃـﺮﻑ ‪ Master‬ﺑـﻪ ﺗﻤـﺎﻡ‬

‫ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺑﺼﻮﺭﺕ‪ SDN‬ﺍﺭﺳﺎﻝ ﻣﻴﮕﺮﺩﺩ‪.‬‬ ‫‪BRCT‬‬

‫‪Broadcast‬‬
‫‪Techno-Electro.com‬‬

‫‪١٥٧‬‬ ‫ﻧﺤﻮﺓ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫‪Type of Communication‬‬ ‫ﻧﻜﺎﺕ ﻗﺎﺑﻞ ﺗﻮﺟﻪ ﺩﺭ ﻣﻮﺭﺩ‬
‫‪ BRCT‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪.‬‬ ‫• ﺍﮔﺮ ﺍﺯ ﺍﺑﺘﺪﺍ ﺩﺭ ﺟﺪﻭﻝ ﺍﺭﺗﺒﺎﻃﺎﺕ ﻧﻮﻉ ‪ All Broadcast Station‬ﺍﻧﺘﺨﺎﺏ ﺷﺪﻩ ﺑﺎﺷﺪ ﻛﺪ‬
‫• ﺑﻄﻮﺭ ﻣﻌﻤﻮﻝ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﺩﻭ ﺳﻴﺴﺘﻢ ﻧﻮﻉ ‪ MMAC‬ﺍﻧﺘﺨﺎﺏ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Properties‬‬ ‫• ﺍﮔﺮ ﺍﺭﺗﺒﺎﻁ ﻫﺎﻱ ﻧﻮﻉ ‪ MSAC‬ﻳﺎ ‪ MSAC-SI‬ﻳﺎ ‪ MSCY‬ﻣﺪ ﻧﻈﺮ ﺑﺎﺷﺪ ﻻﺯﻡ ﺍﺳﺖ ﺍﺑﺘﺪﺍ ﺩﺭ ﭘﻨﺠﺮﻩ‬
‫ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻧﻮﻉ ‪ General FMS Slave‬ﺭﺍ ﺑﺮﺍﻱ ﻃﺮﻑ ﻣﻘﺎﺑﻞ )‪ (Partner‬ﺍﻧﺘﺨﺎﺏ ﻛﺮﺩ‪.‬‬

‫ﭘﺲ ﺍﺯ ﺍﻧﺘﺨﺎﺏ ﻓﻮﻕ ﺍﮔﺮ ﺭﻭﻱ ‪Options‬ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﻣﻲ ﺗﻮﺍﻧﻴﻢ ﻳﻜﻲ ﺍﺯ ﺳﻪ ﺣﺎﻟﺖ ﺫﻛﺮ ﺷﺪﻩ ﺭﺍ ﺑﺮﺍﻱ ‪ Slave‬ﺍﻧﺘﺨﺎﺏ‬
‫ﻧﻤﺎﻳﻴﻢ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ‪:‬‬
‫‪Techno-Electro.com‬‬

‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١٥٨‬‬

‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪۳-۹‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺫﻛﺮ ﺷﺪ ﺑﻄﻮﺭ ﻣﻌﻤﻮﻝ ﻣﺎ ﺩﺭ ﺳﻤﺖ ‪ Server‬ﻧﻴﺎﺯ ﺑﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻧﺪﺍﺭﻳﻢ‪ Server .‬ﺻﺮﻓﹰﺎﺩﻳﺘﺎ ﺑﻼﻙ ﺧﻮﺩ ﺭﺍ‬
‫ﺩﺭ ﺍﺧﺘﻴﺎﺭ ‪ Client‬ﻗﺮﺍﺭ ﻣﻲ ﺩﻫﺪ‪.‬ﺑﻨﺎﺑﺮﺍﻳﻦ‪:‬‬
‫ﻗﺪﻡ ﺍﻭﻝ‪:‬‬
‫ﺩﺭ ﺳﻤﺖ ‪ Server‬ﻳﻚ ﺩﻳﺘﺎ ﺑﻼﻙ ﺑﺎ ﺳﻄﺮ ﻫﺎﻱ ﺩﻟﺨﻮﺍﻩ ﻭ ﺑﺎ ﻧﻮﻉ ﻣﺘﻐﻴﺮ ﻫﺎﻱ ﺩﻟﺨﻮﺍﻩ ﺍﻳﺠﺎﺩ ﻣﻲ ﻛﻨﻴﻢ‪.‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﺍﺯ‬
‫ﺁﻧﺠﺎ ﻛﻪ ﺍﺯ ﺳﻤﺖ ‪ Client‬ﻧﻴﺰﺩﻳﺘﺎ ﺍﺯ ﺩﻳﺘﺎ ﺑﻼﻛﻲ ﺍﺭﺳﺎﻝ ﻳﺎ ﺩﺭﻳﺎﻓﺖ ﻣﻲ ﺷﻮﺩﺑﺎﻳﺪ ﺑﻪ ﺳﺎﺧﺘﺎﺭ ﺁﻥ ﺩﻗﺖ ﻛﺮﺩ ﺗﺎ ﻣﺸﺎﺑﻪ ﺳﺎﺧﺘﺎﺭ‬
‫ﺳﻤﺖ ‪ Server‬ﺑﺎﺷﺪ‪ .‬ﺷﻜﻞ ﺯﻳﺮ‪:‬‬
‫‪Techno-Electro.com‬‬

‫‪١٥٩‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫ﻗﺪﻡ ﺩﻭﻡ ‪:‬‬

‫ﺩﺭ ﺳﻤﺖ ‪ Server‬ﺟﺪﻭﻝ ﺳﻤﺒﻠﻬﺎ ‪ Symbols Table‬ﺭﺍ ﺑﺎﺯ ﻛﺮﺩﻩ ﻭ ‪ DB‬ﺭﺍ ﺑﺎ ﻧﺎﻡ ﺳﻤﺒﻠﻴﻚ ﺩﻟﺨﻮﺍﻩ ﻣﻌﺮﻓﻲ ﻣﻲ ﻛﻨﻴﻢ‪.‬‬

‫ﺳ ـﭙﺲ ﺍﺯ ﻃــﺮﻳﻖ ﻣــﻨﻮﻱ ‪ Edit > Special Object Properties > Communication‬ﭘــﻨﺠﺮﻩ ﺍﻱ‬
‫ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺭﺍ ﺑﺎﺯ ﻛﺮﺩﻩ ﻭ ﮔﺰﻳﻨﻪ‪ Use Symbol as Communication Partner‬ﺭﺍ ﻓﻌﺎﻝ ﻣﻴﻜﻨﻴﻢ‪.‬‬

‫ﻗﺪﻡ ﭼﻬﺎﺭﻡ‪:‬‬
‫ﺩﺭ ﺑﺨـﺶ ‪ Struct‬ﺍﺯ ﭘـﻨﺠﺮﻩ ﻓـﻮﻕ ﺭﻓـﺘﻪ ﻭﻣﺸـﺎﻫﺪﻩ ﻣـﻲ ﻛﻨﻴﻢ ﻛﻪ ﻳﻚ ﺷﻤﺎﺭﻩ ‪ Index‬ﺑﻪ ﺩﻳﺘﺎ ﺑﻼﻙ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺍﻳﻦ‬
‫ﺷـﻤﺎﺭﻩ ﺭﺍ ﻳﺎﺩﺩﺍﺷـﺖ ﻛـﺮﺩﻩ ﺗـﺎ ﺩﺭ ﺳـﻤﺖ ‪ Client‬ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺑﺎ ‪ DB‬ﺍﺯ ﺁﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ‪.‬ﺍﻳﻦ ﺷﻤﺎﺭﻩ ﺩﺭ ﻣﺜﺎﻝ ﺷﻜﻞ ﺑﺎﻻﻱ‬
‫ﺻﻔﺤﻪ ﺑﻌﺪ ‪ 103‬ﻣﻴﺒﺎﺷﺪ‪.‬‬
‫ﻣـﻲ ﺗﻮﺍﻧـﻴﻢ ﺩﺭ ﺳـﻤﺖ ‪ Server‬ﭼـﻨﺪ ﺩﻳـﺘﺎ ﺑﻼﻙ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ‪ ،‬ﺭﻭﺵ ﺍﻳﺠﺎﺩ ﻛﺮﺩﻥ ﺁﻧﻬﺎ ﺑﻪ ﻫﻤﻴﻦ ﻧﺤﻮ‬
‫ﺍﺳﺖ ﻭ ﺩﺭ ﺁﺧﺮ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ ﻛﻪ ﻫﺮﻛﺪﺍﻡ ﻳﻚ ﺷﻤﺎﺭﻩ ﺍﻳﻨﺪﻛﺲ ﻣﻨﺤﺼﺮ ﺑﻪ ﻓﺮﺩ ﺩﺍﺭﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬ ‫‪١٦٠‬‬

‫ﺷﻤﺎﺭﻩ ‪ Index‬ﻛﻞ ‪ DB‬ﻭ ﺷﻤﺎﺭﻩ ‪ Subindex‬ﻳﻚ ﺳﻄﺮ ﺍﺯ ‪ DB‬ﺭﺍ ﻣﻌﺮﻓﻲ ﻣﻴﻜﻨﺪ ﻣﻴﺘﻮﺍﻧﻴﻢ ﺑﺴﺘﻪ ﺑﻪ ﻧﻴﺎﺯ ﺩﺭ ﺑﺮﻧﺎﻣﻪ‬
‫ﻧﻮﻳﺴﻲ ﻛﻞ ‪ DB‬ﻳﺎ ﺳﻄﺮ ﺧﺎﺻﻲ ﺍﺯ ﺁﻥ ﺭﺍ ﺁﺩﺭﺱ ﺑﺪﻫﻴﻢ ﺗﺎ ﺩﻳﺘﺎ ﺍﺯ ﺁﻧﺠﺎ ﺧﻮﺍﻧﺪﻩ ﻳﺎ ﺩﺭ ﺁﻧﺠﺎ ﻧﻮﺷﺘﻪ ﺷﻮﺩ‪.‬‬

‫ﻗﺪﻡ ﭘﻨﺠﻢ‬
‫ﺩﺭ ﺳـﻤﺖ ‪ Client‬ﻧـﻴﺎﺯ ﺑـﻪ ﺑـﺮﻧﺎﻣﻪ ﻧﻮﻳﺴـﻲ ﺩﺍﺭﻳـﻢ ﺭﻭﺵ ﻛـﺎﺭ ﺷـﺒﻴﻪ ﺁﻧﭽـﻪ ﺑﺮﺍﻱ ‪ FDL‬ﮔﻔﺘﻪ ﺷﺪ ﻣﻴﺒﺎﺷﺪ ﻭﻟﻲ ﻓﺎﻧﻜﺸﻦ ﻫﺎ‬
‫ﻣﺘﻔﺎﻭﺗﻨﺪ‪.‬ﭘﺲ ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﺑﻪ ﻧﻜﺎﺕ ﻣﺸﺘﺮﻙ ﺍﺷﺎﺭﻩ ﻣﻴﻜﻨﻴﻢ‪:‬‬
‫ﺑـﺮﻧﺎﻣﻪ ﺍﺻﻠﻲ ﻣﻴﺘﻮﺍﻧﺪ ﺩﺭ ‪ OB3x‬ﻳﻌﻨﻲ ﻭﻗﻔﻪ ﻫﺎﻱ ﺳﻴﻜﻠﻲ ﻧﻮﺷﺘﻪ ﺷﻮﺩ‪ .‬ﺍﺯ ﺁﻧﺠﺎ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﻭﻗﻔﻪ ﻫﺎ ﺯﻣﺎﻥ ﺍﺟﺮﺍﻱ‬ ‫•‬

‫ﺑﻼﻙ ﻗﺎﺑﻞ ﺗﻨﻈﻴﻢ ﺍﺳﺖ ﻧﺴﺒﺖ ﺑﻪ ‪ OB1‬ﺑﺮﺍﻱ ﻛﺎﺭ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﻣﺰﻳﺖ ﺩﺍﺭﻧﺪ‪.‬‬
‫‪Program‬‬ ‫ﺩﺭ ‪ OB‬ﻣـﺮﺑﻮﻃﻪ ﻓﺎﻧﻜﺸـﻦ ﺑـﻼﻙ ﻫـﺎﻱ ﺧﻮﺍﻧﺪﻥ )‪ (FB3‬ﻭ ﻧﻮﺷﺘﻦ )‪ (FB6‬ﺭﺍ ﺍﺯ ﻣﺴﻴﺮ ﺯﻳﺮ ﺩﺭ‬ ‫•‬

‫‪ Element‬ﻭﺍﺭﺩ ﺑﺮﻧﺎﻣﻪ ﻣﻴﻜﻨﻴﻢ‪.‬‬

‫‪LAD/STL/FBD > Program Element > Libraries> Simatic Net CP‬‬
‫‪CPU‬‬ ‫ﺑـﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﻓﺎﻧﻜﺸﻨﻬﺎﻱ ‪ 300‬ﻭ ‪ 400‬ﺍﮔﺮﭼﻪ ﻫﻢ ﻧﺎﻡ ﻫﺴﺘﻨﺪ ﻭﻟﻲ ﻣﺘﻔﺎﻭﺕ ﻣﻴﺒﺎﺷﻨﺪ ﻭ ﺑﺴﺘﻪ ﺑﻪ‬ ‫•‬

‫ﺑﺎﻳﺪ ‪ FB‬ﻣﺮﺑﻮﻃﻪ ﺭﺍ ﺍﻧﺘﺨﺎﺏ ﻧﻤﻮﺩ‪.‬‬

‫ﻣﻌﻤﻮﻻ ﺩﺭ ﺳﻤﺖ ‪ Server‬ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻻﺯﻡ ﻧﻴﺴﺖ ‪ .‬ﺑﺎ ﺍﻳﻦ ﻭﺟﻮﺩ ﻣﻴﺘﻮﺍﻥ ﻣﺮﺍﺣﻞ ﻓﻮﻕ ﺭﺍ ﺩﺭ ﺳﻤﺖ‬ ‫•‬

‫‪ Server‬ﻧﻴﺰ ﺩﻧﺒﺎﻝ ﻧﻤﻮﺩ‪.‬‬

‫ﺑﻼﻙ ﻫﺎﻱ ‪ Read‬ﻭ ‪ Write‬ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٦١‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫‪Write‬‬ ‫ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ‬

‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ ﻛﻪ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ ﺁﻥ ‪ FB6‬ﺍﺳﺖ ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺷﻜﻞ ﺯﻳﺮ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺭﺍ‬
‫ﺑﺼﻮﺭﺕ ﺑﻼﻙ ‪ FBD‬ﻫﻤﺮﺍﻩ ﺑﺎ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻳﺶ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬

‫ﻭﺭﻭﺩﻱ ﻫﺎ ‪:‬‬
‫‪REQ‬‬ ‫ﻳﻚ ﺑﻴﺖ ﺍﺳﺖ ﻛﻪ ﮔﺮ ‪ 1‬ﺑﺎﺷﺪ ﺩﻳﺘﺎ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ ﻭ ﺍﮔﺮ ‪ 0‬ﺑﺎﺷﺪ ﺧﺮﻭﺟﻴﻬﺎ ‪ update‬ﻣﻴﺸﻮﻧﺪ‪ .‬ﺍﻳﻦ ﺑﻴﺖ‬
‫ﺭﺍ ﻣﻌﻤﻮﻻ ﺑﻪ ﻳﻚ ﻣﺘﻐﻴﺮ ﺣﺎﻓﻈﻪ ﻣﺎﻧﻨﺪ ‪ M0.0‬ﻣﻴﺪﻫﻴﻢ ﺗﺎ ﺑﺘﻮﺍﻥ ﻛﺎﺭ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﺭﺍ ﻛﻨﺘﺮﻝ ﻛﻨﻴﻢ‪.‬‬
‫‪ID‬‬ ‫ﻋﺪﺩ ‪ DWord‬ﻛﻪ ﺩﺭ ‪ Connection Table‬ﻫﻨﮕﺎﻡ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻣﺸﺨﺺ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪DW#16#00010001‬‬ ‫ﻣﺜﺎﻝ ‪:‬‬
‫‪VAR_1‬‬ ‫‪ Server‬ﺭﺍ ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺎﻳﺪ ﺩﺍﺩ ﻭﻟﻲ ﻣﺴﺘﻘﻴﻤﺎ ﻧﻤﻴﺘﻮﺍﻥ ﻧﻮﺷﺖ ﻣﺜﻼ ‪103‬‬ ‫ﺁﺩﺭﺱ ‪ index‬ﺩﻳﺘﺎ ﺑﻼﻙ ﺳﻤﺖ‬
‫ﺑﻠﻜﻪ ﺑﺎﻳﺪ ﺁﻧﺮﺍ ﺩﺭ ﻳﻚ ‪ DB‬ﺩﺭ ﺳﻤﺖ ‪ Client‬ﺍﺯ ﻧﻮﻉ ‪ String‬ﻣﻌﺮﻓﻲ ﻛﺮﺩﻩ ﻭ ﺁﺩﺭﺱ ﺳﻄﺮ ‪ DB‬ﺭﺍ ﺩﺭ‬
‫‪DB10.test‬‬ ‫ﻼ‬
‫ﺍﻳﻨﺠﺎ ﻭﺍﺭﺩ ﻧﻤﺎﻳﻴﻢ ﻣﺜ ﹲ‬

‫‪SD_1‬‬ ‫ﺁﺩﺭﺱ ﺩﻳﺘﺎ ﺑﻼﻙ ﺳﻤﺖ ‪ Client‬ﻭ ﻣﻘﺪﺍﺭ ﺩﻳﺘﺎﻳﻲ ﻛﻪ ﺑﺎﻳﺪ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﺭﺍ ﻣﺸﺨﺺ ﻣﻴﻜﻨﺪ‪ .‬ﺍﻳﻦ ﺁﺩﺭﺱ‬
‫‪DB1.DBW0‬‬ ‫ﻣﻴﺘﻮﺍﻧﺪ ﻛﻞ ‪ DB‬ﻳﺎ ﺁﺩﺭﺱ ﺧﺎﺻﻲ ﺍﺯ ﻳﻚ ‪ DB‬ﺑﺎﺷﺪ‪ .‬ﻣﺎﻧﻨﺪ‬

‫ﺧﺮﻭﺟﻲ ﻫﺎ ‪:‬‬
‫ﻋﻤﻠﻜﺮﺩ ﺳﻪ ﺧﺮﻭﺟﻲ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ ﺷﺒﻴﻪ ﺧﺮﻭﺟﻲ ﻫﺎﻱ ﻓﺎﻧﻜﺸﻦ ‪ AG_SEND‬ﺍﺳﺖ ﻛﻪ ﺩﺭ ‪ FDL‬ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ‬
‫ﺷﺪﻭﻟﻲ ﻛﺪ ﺧﻄﺎﻱ ﺑﺮﮔﺸﺘﻲ ﻭ ﺗﻔﺴﻴﺮ ﺁﻥ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ‪ .‬ﺍﻳﻦ ﻛﺪﻫﺎ ﺑﺪﻟﻴﻞ ﺗﻨﻮﻉ ﻭ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩ ﺩﺭ ﺿﻤﻴﻤﻪ ‪ ٥‬ﺁﻭﺭﺩﻩ ﺷﺪﻩ ﺍﻧﺪ‪.‬‬
Techno-Electro.com

FMS ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬ ١٦٢

Read ‫ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ‬

‫ ﺷﻜﻞ ﺯﻳﺮ ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺭﺍ‬.‫ ﺍﺳﺖ ﺑﺮﺍﻱ ﺧﻮﺍﻧﺪ ﺩﻳﺘﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‬FB3 ‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ ﻛﻪ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ ﺁﻥ‬
.‫ ﻫﻤﺮﺍﻩ ﺑﺎ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻳﺶ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‬FBD ‫ﺑﺼﻮﺭﺕ ﺑﻼﻙ‬

‫ ﻭﺭﻭﺩﻱ‬.‫ ﻧﻴﺎﺯﻱ ﺑﻪ ﺗﻮﺿﻴﺢ ﻣﻜﺮﺭ ﻧﻴﺴﺖ‬FB6 ‫ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺷﺒﺎﻫﺖ ﺑﺴﻴﺎﺭﻱ ﺍﺯ ﻭﺭﻭﺩﻱ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎ ﻱ ﺍﻳﻦ ﺑﻼﻙ ﺑﺎ ﺑﻼﻙ‬
‫ ﺭﺍ ﻣﻴﮕﻴﺮﺩ ﻛﻪ ﻗﺮﺍﺭ ﺍﺳﺖ ﺩﺭ ﺁﻧﺠﺎ ﺩﻳﺘﺎ ﺫﺧﻴﺮﻩ‬Client ‫ ﺍﻳﻦ ﺑﻼﻙ ﺁﺩﺭﺱ ﻣﺤﻠﻲ ﺍﺯ ﺩﻳﺘﺎ ﺑﻼﻙ ﺳﻤﺖ‬RD_1
FDL ‫ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﺭﺗﺒﺎﻁ‬AG_RECV ‫ﺩﺭ‬ ‫( ﻣﺸﺎﺑﻪ ﺍﻳﻦ ﺧﺮﻭﺟﻲ‬New Data Received) NDR ‫ﺧﺮﻭﺟﻲ‬..‫ﺷﻮﺩ‬
.‫ﻣﻴﺒﺎﺷﺪ‬
:‫ ﺩﺭ ﺯﻳﺮ ﺁﻭﺭﺩﻩ ﺷﺪﻩ ﺍﺳﺖ‬FB ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺻﺪﺍ ﺯﺩﻥ ﺍﻳﻦ‬

//READ block call with instance DB CALL FB 3, DB 29

//Signal edge change to execute the FB REQ := M 1.0
//compared with configuration of FMS ID := DW#16#10001
//addresses K variable that will be read VAR_1 := “SLAVE2”.INDEX
//addresses data area as destination RD_1 := “PROCESS”.IMAGE
//confirmation of execution NDR := M 1.1
//indicates incorrect execution ERROR := M 1.2
//detailed error decoding STATUS := MW 20
‫‪Techno-Electro.com‬‬

‫‪۱۶۳‬‬ ‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

‫‪Report‬‬ ‫ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ‬

‫ﺍﻳﻦ ﻓﺎﻧﻜﺸﻦ ﺑﻼﻙ ﻛﻪ ﻧﺎﻡ ﻏﻴﺮ ﺳﻤﺒﻠﻴﻚ ﺁﻥ ‪ FB4‬ﺍﺳﺖ ﺷﺒﻴﻪ ‪ Write‬ﻋﻤﻞ ﻣﻴﻜﻨﺪ ﻭﻟﻲ ﻣﻨﺘﻈﺮ ﺗﺎﻳﻴﺪ ﻧﻤﻲ ﻣﺎﻧﺪ‪.‬‬

‫ﻭﺭﻭﺩﻱ ﻫﺎ ﻭ ﺧﺮﻭﺟﻲ ﻫﺎﻱ ﺍﻳﻦ ﺑﻼﻙ ﺷﺒﻴﻪ ‪ Write‬ﺍﺳﺖ‪ .‬ﻭﻟﻲ ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﺑﺮﺍﻱ ﺷﻤﺎﺭﻩ ﺍﻳﻨﺪﻛﺲ ﺑﺎﻳﺪ ﺍﺯ ﻋﺪﺩ‬
‫ﻣﻮﺟﻮﺩ ﺩﺭ ‪ Structure‬ﻣﺮﺑﻮﻁ ﺑﻪ ‪ Symbol Table‬ﻣﻄﺎﺑﻖ ﺷﻜﻞ ﺯﻳﺮ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪:‬‬
Techno-Electro.com

FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬ ۱۶۴

FMS ‫ﺍﺭﺗﺒﺎﻁ‬ ‫ ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ‬۴-۹

‫ ﻧﻮﺷﺘﻪ ﺷﺪﻩ ﻭ ﺩﺭ‬Client ‫ ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﺩﺭ ﺳﻤﺖ‬.‫ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‬STL Source ‫ ﺭﺍ ﺑﺼﻮﺭﺕ‬FMS ‫ﺍﻳﻦ ﻣﺜﺎﻝ ﺑﺮﻧﺎﻣﻪ ﺍﺭﺗﺒﺎﻁ‬
.‫ ﻫﻴﭽﮕﻮﻧﻪ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺑﻜﺎﺭ ﻧﺮﻓﺘﻪ ﺍﺳﺖ‬Server ‫ﺳﻤﺖ‬

FUNCTION FC 100 : VOID

TITLE =CALL_READ
//This function illustrates an FMS communication job with the READ (FB3)
//block. A variable of the type integer is accessed.
VERSION : 0.1
BEGIN
NETWORK
TITLE =Read variable with index 100.
//Read data access:
//A variable with index 100 is read and entered in the destination data
//DB500).
//Call parameters in DB 100.
//Job handling /job coordination:
//This job is only started when all other jobs have been completed. This
// means that access to the variable is synchronized.
//The job is triggered by a signal edge at the REQ input. REQ is reset
// when the job is completed or an error occurred. Following this, the //
signal is set again.
//If an error occurred, the error number can be read from the status word.
//Only execute job when no other job is active.
O DB200.DBX 0.0; // REQ=1, WRITE /active
O DB101.DBX 0.0; // REQ=1, READ /active
O DB201.DBX 0.0; // REQ=1, WRITE /active
O DB102.DBX 0.0; // REQ=1, READ /active
O DB202.DBX 0.0; // REQ=1, WRITE /active
JC ende;
//Calling the READ job:
CALL FB 3 , DB 300 (
REQ := DB100.DBX 0.0,
ID := DB100.DBD 2,
VAR_1 := DB100.Read_VAR_Index,
RD_1 := DB500.DBW 0,
NDR := DB100.DBX 13.0,
ERROR := DB100.DBX 13.1,
STATUS := DB100.DBW 14);
// /Query job status
A DB100.DBX 0.0; // REQ=1 =>
// REQ=1 => Job active, query errors
JC fehl;
AN DB100.DBX 0.0; // REQ=1 =>
// REQ=1 => Job completed
S DB100.DBX 0.0; // / Set REQ again
JU ende;
Techno-Electro.com

۱۶۵ FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬

// Error handling
fehl: AN DB100.DBX 13.1; // Error=0 =>
// Error=0 => No error occurred
JC ok;
A DB100.DBX 13.1; // Error=1 =>
// Error=1 => Error occurred
L DB100.DBW 14; // / Load error status
T DB100.DBW 16; // // Save in buffer
R DB100.DBX 0.0; // / Reset REQ
JU ende; // / Query job status

ok: AN DB100.DBX 13.0; // Done=0 =>

// Done=0 => Job still active
JC ende;

A DB100.DBX 13.0; // Done=1 =>

// Done=1 => Job complete without error
R DB100.DBX 0.0; // / Reset REQ

ende: BE ;
END_FUNCTION

FUNCTION FC 101 : VOID

TITLE =CALL_READ
//The function illustrates an FMS communication job with the READ(FB3)
// function block. A variable of the type array is accessed.
VERSION : 0.1
BEGIN
NETWORK
TITLE = Read variable with index 101.
//Read data access:
//The variable with index 101 is read and entered in the destination data
//area (here DB501). Call parameters in DB101.
//
//Job handling /job coordination:
//This job is only started when all other jobs have been completed. This
//means that access to the variable is synchronized.
//The job is triggered by a signal edge at the REQ input. REQ is reset
//when the job is completed or an error occurred. Following this, the.
//signal is set again If an error occurred, the error number can be read
//from the status word.
// Only execute job when no other job is active.
O DB200.DBX 0.0; // REQ=1, WRITE / active
O DB100.DBX 0.0; // REQ=1, READ / active
O DB201.DBX 0.0; // REQ=1, WRITE / active
O DB102.DBX 0.0; // REQ=1, READ / active
O DB202.DBX 0.0; // REQ=1, WRITE / active
JC ende;
Techno-Electro.com

FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬ ١٦٦

//Calling the READ job:

CALL FB 3 , DB 301 (
REQ := DB101.DBX 0.0,
ID := DB101.DBD 2,
VAR_1 := DB101.Read_VAR_Index,
RD_1 := DB501.Index_101,
NDR := DB101.DBX 13.0,
ERROR := DB101.DBX 13.1,
STATUS := DB101.DBW 14);
// Query job status
A DB101.DBX 0.0; // REQ=1 =>
// REQ=1 => Job active, query errors
JC fehl;

AN DB101.DBX 0.0; // REQ=0 =>

// REQ=1 => Job completed
S DB101.DBX 0.0; // / Set REQ again
JU ende;
// Error handling

fehl: AN DB101.DBX 13.1; // Error=0 =>

// Error=0 => No error occurred
JC ok;
A DB101.DBX 13.1; // Error=1 =>
// Error=1 => Error occurred

L DB101.DBW 14; //load error status

T DB101.DBW 16; // Save in buffer
R DB101.DBX 0.0; // Reset REQ
JU ende;
// / Query job status
ok: AN DB101.DBX 13.0; // Done=0 =>
// Done=0 => Job still active
JC ende;
A DB101.DBX 13.0; // Done=1 =>
// Done=1 => Job complete without error
R DB101.DBX 0.0; // Reset REQ
ende: BE ;
END_FUNCTION
Techno-Electro.com

۱۶۷ FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬

FUNCTION FC 102 : VOID

TITLE =CALL_READ
//This function illustrates an FMS communication job with the READ (FB3)
// function block. A variable of the type STRUCT is accessed.
VERSION : 0.1
BEGIN
NETWORK
TITLE =Variable mit dem Index 102 lesen. Read variable with index 102.
//Read data access:
//A variable with index 102 is read and entered in the destination data
// area (here
//DB502). Call parameters in DB 100.
//Job handling /job coordination:
//This job is only started when all other jobs have been completed. This
// means that access to the variable is synchronized.
//The job is triggered by a signal edge at the REQ input. REQ is reset
// when the job is completed or an error occurred. Following this, the
// signal is set again.If an error occurred, the error number can be read
//from the status word.
// Query whether other jobs still active
O DB100.DBX 0.0; // REQ=1, READ /active
O DB200.DBX 0.0; // REQ=1, WRITE /active
O DB101.DBX 0.0; // REQ=1, READ /active
O DB201.DBX 0.0; // REQ=1, WRITE /active
O DB202.DBX 0.0; // REQ=1, WRITE /active
JC ende;
/// Calling the READ job
CALL FB 3 , DB 302 (
REQ := DB102.DBX 0.0,
ID := DB102.DBD 2,
VAR_1 := DB102.Read_VAR_Index,
RD_1 := DB502.Index_102,
NDR := DB102.DBX 13.0,
ERROR := DB102.DBX 13.1,
STATUS := DB102.DBW 14);
// /Query the job status
A DB102.DBX 0.0; // REQ=1 =>
// REQ=1 => Job active, query errors
JC fehl;

AN DB102.DBX 0.0; // REQ=1 =>

// REQ=1 => Job completed
S DB102.DBX 0.0; // / Set REQ again
JU ende;
// / Error handling
fehl: AN DB102.DBX 13.1; // Error=0 =>
// Error=0 => No error occurred
JC ok;
Techno-Electro.com

FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬ ١٦٨

A DB102.DBX 13.1; // Error=1 =>

// Error=1 => Error occurred
L DB102.DBW 14; // / Load error status
T DB102.DBW 16; // // Save in buffer
R DB102.DBX 0.0; // / Reset REQ
JU ende;
// / Query job status
ok: AN DB102.DBX 13.0; // Done=0 =>
// Done=0 => Job still active
JC ende;
A DB102.DBX 13.0; // Done=1 =>
// Done=1 => Job complete without error
R DB102.DBX 0.0; // / Reset REQ
ende: BE ;
END_FUNCTION

FUNCTION FC 200 : VOID

TITLE =CALL_WRITE
//This function illustrates an FMS communication job with the WRITE (FB6)
//function
//block. A variable of the type integer is accessed.
VERSION : 0.1
BEGIN
NETWORK
TITLE =Variable mit dem Index 100 schreiben. Write var. with index 100
//Write data access:
//A variable with index 100 is written. It is taken from the source data
// area (here DB600). Call parameters in DB200.
//Job handling /job coordination:
//This job is only started when all other jobs have been completed. This
// means that access to the variable is synchronized.
//The job is triggered by a signal edge at the REQ input. REQ is reset
// when the job is completed or an error occurred. Following this, the.
// signal is set again If an error occurred, the error number can be read
// from the status word.
// / Query whether other jobs active
O DB100.DBX 0.0; // REQ=1, WRITE /active
O DB101.DBX 0.0; // REQ=1, READ /active
O DB201.DBX 0.0; // REQ=1, WRITE /active
O DB102.DBX 0.0; // REQ=1, READ /active
O DB202.DBX 0.0; // REQ=1, WRITE /active
JC ende;
// / Calling the write job
CALL FB 6 , DB 400 (
REQ := DB200.DBX 0.0,
ID := DB200.DBD 2,
VAR_1 := DB200.Write_VAR_Index,
SD_1 := DB600.DBW 0,
DONE := DB200.DBX 13.0,
ERROR := DB200.DBX 13.1,
STATUS := DB200.DBW 14);
Techno-Electro.com

۱۶۹ FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬

A DB200.DBX 0.0; // REQ=1 =>

// REQ=1 => Job active, query errors
JC fehl;
AN DB200.DBX 0.0; // REQ=0 =>
// REQ=1 => Job completed
S DB200.DBX 0.0; // / Set REQ again
JU ende;
// / Error handling
fehl: AN DB200.DBX 13.1; // Error=0 =>
// Error=0 => No error occurred
JC ok;
A DB200.DBX 13.1; // Error=1 =>
// Error=1 => Error occurred
L DB200.DBW 14; // / Load error status
T DB200.DBW 16; // // Save in buffer
R DB200.DBX 0.0; // / Reset REQ
JU ende;

// / Query job status

ok: AN DB200.DBX 13.0; // Done=0 =>

// Done=0 => Job still active
JC ende;
A DB200.DBX 13.0; // Done=1 =>
// Done=1 => Job complete without error
R DB200.DBX 0.0; // / Reset REQ
ende: BE ;
END_FUNCTION

FUNCTION FC 201 : VOID

TITLE =CALL_WRITE
//This function illustrates an FMS communication job with the WRITE (FB6)
//function
//block. A variable of the type ARRAY is accessed.
VERSION : 0.1
BEGIN
NETWORK
TITLE =Variable mit dem Index 101 schreiben. Write var with index 101.
//Write data access:
//A variable with index 100 is written. It is taken from the source data
// area (here DB601). Call parameters in DB201.
//Job handling /job coordination:
//This job is only started when all other jobs have been completed. This
// means that access to the variable is synchronized.
//The job is triggered by a signal edge at the REQ input. REQ is reset
// when the job is completed or an error occurred. Following this, the
// signal is set again.
//If an error occurred, the error number can be read from the status word.
// / Query whether other jobs still active
Techno-Electro.com

FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬ ١٧٠

O DB100.DBX 0.0; // REQ=1, WRITE /active

O DB200.DBX 0.0; // REQ=1, WRITE /active
O DB101.DBX 0.0; // REQ=1, READ /active
O DB102.DBX 0.0; // REQ=1, READ /active
O DB202.DBX 0.0; // REQ=1, WRITE /active
JC ende;
// / Calling the write job
CALL FB 6 , DB 401 (
REQ := DB201.DBX 0.0,
ID := DB201.DBD 2,
VAR_1 := DB201.Write_VAR_Index,
SD_1 := DB601.Index_101,
DONE := DB201.DBX 13.0,
ERROR := DB201.DBX 13.1,
STATUS := DB201.DBW 14);
// / Query job status
A DB201.DBX 0.0; // REQ=1 =>
// REQ=1 => Job active, query errors
JC fehl;

AN DB201.DBX 0.0; // REQ=0 =>

// REQ=1 => Job completed
S DB201.DBX 0.0; // / Set REQ again
JU ende;
// / Error handling
fehl: AN DB201.DBX 13.1; // Error=0 =>
// Error=0 => No error occurred
JC ok;
A DB201.DBX 13.1; // Error=1 =>
// Error=1 => Error occurred
L DB201.DBW 14; // / Load error status
T DB201.DBW 16; // Save in buffer
R DB201.DBX 0.0; // / Reset REQ
JU ende;
// / Query job status
ok: AN DB201.DBX 13.0; // Done=0 =>
// Done=0 => Job still active
JC ende;
A DB201.DBX 13.0; // Done=1 =>
// Done=1 => Job complete without error
R DB201.DBX 0.0; // / Reset REQ
ende: BE ;
END_FUNCTION
Techno-Electro.com

١٧١ FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬

FUNCTION FC 202 : VOID

TITLE =CALL_WRITE.
//This function illustrates an FMS communication job with the WRITE (FB6)
//function
//block. A variable of the type STRUCT is accessed.
VERSION : 0.1
BEGIN
NETWORK
TITLE =Variable mit dem Index 102 schreiben. Write var with index 102.
//Write data access:
//A variable with index 102 is written. It is taken from the source data
// area (here DB602). Call parameters in DB202.
//
//Job handling /job coordination:
//This job is only started when all other jobs have been completed. This
// means that access to the variable is synchronized.
//The job is triggered by a signal edge at the REQ input. REQ is reset
// when the job is completed or an error occurred. Following this, the
// signal is set again.If an error occurred, the error number can be read
// from the.status word
// / Query whether other jobs active
O DB100.DBX 0.0; // REQ=1, READ /active
O DB200.DBX 0.0; // REQ=1, WRITE /active
O DB101.DBX 0.0; // REQ=1, REA /active
O DB201.DBX 0.0; // REQ=1, WRITE /active
O DB102.DBX 0.0; // REQ=1, REA /active
JC ende;
// / Calling the write job
CALL FB 6 , DB 402 (
REQ := DB202.DBX 0.0,
ID := DB202.DBD 2,
VAR_1 := DB202.Write_VAR_Index,
SD_1 := DB602.Index_102,
DONE := DB202.DBX 13.0,
ERROR := DB202.DBX 13.1,
STATUS := DB202.DBW 14);
A DB202.DBX 0.0; // REQ=1 =>
// REQ=1 => Job active, query errors
JC fehl;

AN DB202.DBX 0.0; // REQ=0 =>

// REQ=1 => Job completed
S DB202.DBX 0.0; // / Set REQ again
JU ende;
Techno-Electro.com

FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬ ١٧٢

// / Error handling
fehl: AN DB202.DBX 13.1; // Error=0 =>
// Error=0 => No error occurred
JC ok;
A DB202.DBX 13.1; // Error=1 =>
// Error=1 => Error occurred
L DB202.DBW 14; // / Load error status
T DB202.DBW 16; // // Save in buffer
R DB202.DBX 0.0; // / Reset REQ
JU ende;
// / Query job status

ok: AN DB202.DBX 13.0; // Done=0 =>

// Done=0 => Job still active
JC ende;
A DB202.DBX 13.0; // Done=1 =>
// Done=1 => Job complete without error
R DB202.DBX 0.0; // / Reset REQ
ende: BE ;
END_FUNCTION

FUNCTION FC 300 : VOID

TITLE =
//This function simulates a signal or value change and checks the write or
// read function via the FMS connection.
VERSION : 0.1
BEGIN
NETWORK
TITLE =
//After writing and reading index 100, the values are compared to check
// that they match. Afterwards the variable is incremented by one.
L DB500.DBW 0;
L DB600.DBW 0;
==I ;
JC inkr;
// Set memory bit 0.0 if the source and destination do not match.
S M 0.0;
// Increment variable with index 100 by one
inkr: L DB600.DBW 0;
+ 1;
T DB600.DBW 0;
R M 0.0;
BE ;
END_FUNCTION
Techno-Electro.com

١٧٣ FMS ‫ﻣﺜﺎﻟﻲ ﺍﺯ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﺍﺭﺗﺒﺎﻁ‬

ORGANIZATION_BLOCK OB 1
TITLE =
//Functions (FC100..FC300) in which FMS communication jobs are sent are
// called in this block. The FCs are designed so that a coordinated
// sequence is guaranteed .(For the symbolic declaration, refer to the
// entries in the symbol table for this CPU.)
VERSION : 0.1

VAR_TEMP
END_VAR
BEGIN
NETWORK
TITLE =
//Write and read jobs are called sequentially.
CALL FC 100 ;

CALL FC 300 ;

CALL FC 200 ;

CALL FC 101 ;

CALL FC 201 ;

CALL FC 102 ;

CALL FC 202 ;
END_ORGANIZATION_BLOCK

ORGANIZATION_BLOCK OB 100
TITLE =
VERSION : 0.1
VAR_TEMP
END_VAR

BEGIN
NETWORK
TITLE =

L 0;
T DB500.DBW 0;
BE ;
END_ORGANIZATION_BLOCK
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﻓﺼﻞ ﺩﻫﻢ – ﻋﻴﺐ ﻳﺎﺑﻲ ﻭ ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ ﺩﺭ ‪PROFIBUS‬‬

‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬ ‫‪١-١٠‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪Step7‬‬ ‫‪٢-١٠‬‬
‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪Step7‬‬ ‫‪ ٣-١٠‬ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ‬
‫‪Techno-Electro.com‬‬

‫ﻭ ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ ﺩﺭ ‪Profibus‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ‬ ‫‪١٧٦‬‬

‫ﻣﻘﺪﻣﻪ‬
‫‪ Troubleshooting‬ﻭ ‪ Diagnostic‬ﺍﺯ ﻣﻘﻮﻟﻪ ﻫﺎﻳﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﻛﺎﺭﺑﺮﺍﻥ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﺻﻨﻌﺘﻲ ﺑﻮﻳﮋﻩ ﭘﺮﺳﻨﻞ ﻛﻪ ﻭﻇﻴﻔﻪ‬
‫ﺁﻧﻬﺎ ﻧﮕﻬﺪﺍﺭﻱ ﻭ ﺗﻌﻤﻴﺮﺍﺕ ﺍﻳﻦ ﺳﻴﺴﺘﻤﻬﺎﺳﺖ ﺑﺎ ﺁﻧﻬﺎ ﺑﻪ ﻭﻓﻮﺭ ﺳﺮﻭ ﻛﺎﺭ ﺩﺍﺭﻧﺪ‪ .‬ﺩﺭ ﻣﻮﻗﻊ ﺑﺮﻭﺯ ﺧﻄﺎ ﺷﻨﺎﺳﺎﻳﻲ ﻋﻴﺐ ﻭ‬
‫ﺭﻓﻊ ﺁﻥ ﺩﺭ ﺣﺪﺍﻗﻞ ﺯﻣﺎﻥ ﻣﻤﻜﻦ ﻫﺪﻓﻲ ﺍﺳﺖ ﻛﻪ ﺑﺎﻳﺪ ﻣﺤﻘﻖ ﺷﻮﺩ ﺗﺎ ﺧﺴﺎﺭﺍﺕ ﻧﺎﺷﻲ ﺍﺯ ﺗﻮﻗﻒ ﺗﻮﻟﻴﺪ ﻭ ﺍﻣﺜﺎﻝ ﺁﻥ ﺑﻪ‬
‫ﺣﺪﺍﻗﻞ ﻛﺎﻫﺶ ﻳﺎﺑﺪ‪ .‬ﺍﺯ ﺍﻳﻨﺮﻭ ﻣﺘﺨﺼﺼﻴﻦ ﺍﺗﻮﻣﺎﺳﻴﻮﻥ ﻻﺯﻡ ﺍﺳﺖ ﺍﺑﺰﺍﺭﻫﺎﻳﻲ ﺭﺍ ﺗﺪﺍﺭﻙ ﺑﺒﻴﻨﻨﺪ ﺗﺎ ﺑﺘﻮﺍﻧﺪ ﺍﻫﺪﺍﻑ ﻓﻮﻕ ﺭﺍ‬
‫ﺑﺮﺁﻭﺭﺩﻩ ﺳﺎﺯﺩ‪ .‬ﺍﻳﻦ ﺍﺑﺰﺍﺭﻫﺎ ﻫﻤﺎﻧﮕﻮﻧﻪ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﺑﺨﺶ ﺧﻮﺍﻫﻴﻢ ﺩﻳﺪ ﺻﺮﻓﹰﺎ ﺍﺑﺰﺍﺭﻫﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻧﻴﺴﺘﻨﺪ ﺑﻠﻜﻪ ﺍﺳﺘﻔﺎﺩﻩ‬
‫ﺍﺯ ﻗﺎﺑﻠﻴﺖ ﻫﺎﻱ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻭ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻣﻨﺎﺳﺐ ﻧﻴﺰ ﺍﺯ ﺍﻳﻦ ﺟﻤﻠﻪ ﺑﺸﻤﺎﺭ ﻣﻲ ﺁﻳﻨﺪ‪.‬‬
‫ﺩﺭ ﻟﺤﻈﻪ ﺍﻭﻝ ﺑﺮﻭﺯ ﻋﻴﺐ ﺭﻭﻱ ﺷﺒﻜﻪ ‪ Profibus‬ﻛﺎﺭﺑﺮ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺎ ﺗﻮﻗﻒ ‪ CPU‬ﺑﺎ ﺭﻭﺷﻦ ﺷﺪﻥ ﭼﺮﺍﻍ ‪ SF‬ﻭ ﺑﻄﻮﺭ‬
‫ﻫﻤﺰﻣﺎﻥ ﭼﺸﻤﻚ ﺯﺩﻥ ﭼﺮﺍﻍ ‪ BF‬ﻳﺎ ‪ Bus Fault‬ﺭﻭﻱ ﺁﻥ ﻣﻮﺍﺟﻪ ﺷﻮﺩ‪ .‬ﻭ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻴﺪﺍﻧﻴﻢ ﻗﺪﻡ ﺍﻭﻝ ﺍﺭﺗﺒﺎﻁ ﺑﺎ‬
‫‪ PLC‬ﻭ ﻣﺮﺍﺟﻌﻪ ﺑﻪ ‪ Diagnostic Buffer‬ﻭ ﻧﻴﺰ ﺩﻳﺪﻥ ﻭﺿﻌﻴﺖ ﺷﺒﻜﻪ ﺑﺼﻮﺭﺕ ‪ Online‬ﺍﺳﺖ ﺗﺎ ﺍﻃﻼﻋﺎﺕ ﺑﻴﺸﺘﺮﻱ‬
‫ﻧﺴﺒﺖ ﺑﻪ ﺧﻄﺎ ﻛﺴﺐ ﮔﺮﺩﺩ ﮔﺮﭼﻪ ﺑﻌﻀﹰﺎ ﺍﻃﻼﻋﺎﺕ ﻓﻮﻕ ﻧﻴﺰ ﺑﻄﻮﺭ ﺭﻭﺷﻦ ﻋﻴﺐ ﺭﺍ ﻣﺸﺨﺺ ﻧﻤﻲ ﻧﻤﺎﻳﺪ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ‬
‫‪Bus Access‬‬ ‫ﺑﺮﺍﻱ ﻳﻚ ‪ CPU‬ﻛﻪ ﺍﺯ ﻃﺮﻳﻖ ﭘﻮﺭﺕ ‪ DP‬ﺑﻪ ﺷﺒﻜﻪ ‪ Profibus‬ﻣﺘﺼﻞ ﺍﺳﺖ ﺍﺷﻜﺎﻻﺕ ﺯﻳﺮ ﺑﺎ ﻋﻨﻮﺍﻥ‬
‫‪ Error‬ﻇﺎﻫﺮ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪.‬‬
‫ﻗﻄﻊ ﺷﺪﻥ ﻛﺎﺑﻞ ﺷﺒﻜﻪ‬ ‫•‬
‫ﺑﺎﺯ ﺑﻮﺩﻥ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺍﻧﺘﻬﺎﻱ ﺑﺎﺱ‬ ‫•‬
‫‪ DP‬ﺭﻭﻱ ‪PLC‬‬ ‫ﻗﻄﻊ ﺑﻮﺩﻥ ﻛﺎﻧﻜﺘﻮﺭ‬ ‫•‬

‫ﻋﺪﻡ ﺗﻄﺎﺑﻖ ﺑﻴﻦ ﺷﺒﻜﻪ ﺩﺍﻧﻠﻮﺩ ﺷﺪﻩ ﺑﻪ ‪ CPU‬ﺑﺎ ﺁﻧﭽﻪ ﺩﺭ ﻋﻤﻞ ﻭﺟﻮﺩ ﺩﺍﺭﺩ‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪١٧٧‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬

‫‪ ١-١٠‬ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬

‫ﻭﺳﺎﻳﻞ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻣﺨﺘﻠﻒ ﺗﻮﺳﻂ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﺘﻠﻒ ﺑﺮﺍﻱ ﻋﻴﺐ ﻳﺎﺑﻲ ﺷﺒﻜﻪ ﻫﺎ ﻃﺮﺍﺣﻲ ﺷﺪﻩ ﺍﻧﺪ ﻭﻟﻲ ﺁﻧﭽﻪ ﺩﺭ‬
‫ﺍﻳﻨﺠﺎ ﻋﻨﻮﺍﻥ ﻣﻴﺸﻮﺩ ﺻﺮﻓﹰﺎ ﻭﺳﺎﻳﻠﻲ ﺍﺳﺖ ﻛﻪ ﺯﻳﻤﻨﺲ ﺩﺭ ﻣﺪﺍﺭﻙ ﺧﻮﺩ ﺑﻪ ﺁﻧﻬﺎ ﺍﺷﺎﺭﻩ ﻧﻤﻮﺩﻩ ﺍﺳﺖ‪.‬‬

‫‪ ١-١-١٠‬ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ ﺩﺭ ﺷﺒﻜﻪ ﻫﺎﻱ ﺍﻟﻜﺘﺮﻳﻜﻲ‬

‫‪BT200‬‬ ‫ﺍﻟﻒ(‬
‫ﺍﻳﻦ ﻭﺳﻴﻠﻪ ﻛﻪ ﺗﻮﺳﻂ ﭘﻮﺭﺕ ‪ ٩‬ﭘﻴﻦ ﺭﻭﻱ ﺁﻥ ﺑﻪ ‪ Profibus‬ﻣﺘﺼﻞ ﻣﻴﮕﺮﺩﺩ‬
‫ﻗﺎﺩﺭ ﺍﺳﺖ ﻋﻴﻮﺏ ﺯﻳﺮ ﺭﺍ ﺩﺭ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺗﺸﺨﻴﺺ ﺩﻫﺪ‪:‬‬
‫ﺍﺗﺼﺎﻝ ﻛﻮﺗﺎﻩ ﺑﻴﻦ ﺳﻴﻢ ﺩﻳﺘﺎ ﻭ ﺷﻴﻠﺪ‬ ‫•‬

‫ﻗﻄﻊ ﺷﺪﻥ ﺧﻄﻮﻁ ﺩﻳﺘﺎ‬ ‫•‬

‫ﻗﻄﻊ ﺷﺪﻥ ﺷﻴﻠﺪ‬ ‫•‬

‫ﭘﻼﺭﻳﺘﻪ ﺑﺮ ﻋﻜﺲ ﺧﻄﻮﻁ ‪ A‬ﻭ ‪B‬‬ ‫•‬

‫ﺑﺎﺯﺗﺎﺏ ﻫﺎﻱ ﺳﻴﮕﻨﺎﻝ ﻛﻪ ﻣﻨﺠﺮ ﺑﻪ ﺧﻄﺎ ﻣﻴﺸﻮﻧﺪ‪.‬‬ ‫•‬

‫ﭼﻚ ﻛﺮﺩﻥ ﺗﺮﻣﻴﻨﻴﺘﻮﺭﻫﺎﻱ ﻓﻌﺎﻝ‬ ‫•‬

‫ﺩﺭ ﺷﺒﻜﻪ ﺍﻱ ﻛﻪ ﻗﺮﺍﺭ ﺍﺳﺖ ﺗﺴﺖ ﺷﻮﺩ‪ BT200‬ﺭﺍ ﺑﺼﻮﺭﺕ ﺷﻜﻞ ﺯﻳﺮ ﻫﻤﺮﺍﻩ ﺑﺎ ﻳﻚ ‪ Test Plug‬ﻣﻴﺒﻨﺪﻳﻢ‪ .‬ﻫﻤﺎﻧﻄﻮﺭ‬
‫‪Test Plug‬‬ ‫ﻛﻪ ﻣﺸﺎﻫﺪﻩ ﻣﻴﺸﻮﺩ ‪ BT200‬ﺩﺭ ﻳﻜﻄﺮﻑ ﻭ ‪ Test Plug‬ﺩﺭ ﺳﻤﺖ ﺩﻳﮕﺮ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﺩ‪ .‬ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﺭﻭﻱ‬
‫ﺭﺍ ‪ ON‬ﻭ ﺳﺎﻳﺮ ﺗﺮﻣﻴﻨﻴﺘﻮﺭ ﻫﺎ ﺭﺍ ‪ OFF‬ﻣﻲ ﻛﻨﻴﻢ‪ BT200 .‬ﺭﺍ ﺭﻭﺷﻦ ﻛﺮﺩﻩ ﻭ ﻛﻠﻴﺪ ‪ Test‬ﺭﺍ ﻓﺸﺎﺭ ﻣﻴﺪﻫﻴﻢ ﺍﮔﺮ ﻫﻤﻪ ﭼﻴﺰ‬
‫ﺩﺭﺳﺖ ﺑﺎﺷﺪ ﭘﻴﻐﺎﻡ ‪ Cabling O.K.‬ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ﻭﻟﻲ ﺍﮔﺮ ﺍﺷﻜﺎﻟﻲ ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﭘﻴﻐﺎﻡ ﻣﺮﺗﺒﻂ ﺭﻭﻱ ﺻﻔﺤﻪ ﻧﻤﺎﻳﺶ‬
‫ﻇﺎﻫﺮ ﻣﻲ ﮔﺮﺩﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬ ‫‪١٧٨‬‬

‫‪Diagnostic Repeater‬‬ ‫ﺏ(‬

‫ﺍﻳﻦ ﺭﻳﭙﻴﺘﺮ ﻋﻼﻭﻩ ﺑﺮ ﺍﻳﻦ ﻛﻪ ﻛﺎﺭ ﺗﻘﻮﻳﺖ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﺭﻭﻱ ﺷﺒﻜﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ‪ RS485‬ﺍﻧﺠﺎﻡ ﻣﻴﺪﻫﺪ ﻗﺎﺩﺭ ﺍﺳﺖ ﺍﺷﻜﺎﻻﺕ‬
‫ﺳﮕﻤﻨﺖ ﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺧﻮﺩ ﺭﺍ ﺁﺷﻜﺎﺭ ﺳﺎﺧﺘﻪ ﻭ ‪ CPU‬ﺭﺍ ﺍﺯ ﺑﺮﻭﺯ ﻋﻴﺐ ﺑﻄﻮﺭ ﺩﻗﻴﻖ ﻣﻄﻠﻊ ﻧﻤﺎﻳﺪ‪.‬‬

‫‪BT200‬‬ ‫ﻫﻤﻪ ﺧﻄﺎﻫﺎﻳﻲ ﻛﻪ ﺗﻮﺳﻂ ‪ BT200‬ﺷﻨﺎﺳﺎﻳﻲ ﻣﻴﺸﺪ ﺗﻮﺳﻂ ﺍﻳﻦ ﺭﻳﭙﻴﺘﺮ ﻧﻴﺰ ﻗﺎﺑﻞ ﺗﺸﺨﻴﺺ ﺍﺳﺖ ﻭﻟﻲ ﺗﻔﺎﻭﺕ ﺁﻥ ﺑﺎ‬
‫ﺩﺭ ﺍﻳﻨﺴﺖ ﻛﻪ ﺍﻳﻦ ﺭﻳﭙﻴﺘﺮ ﻫﻤﻴﺸﻪ ﺑﺼﻮﺭﺕ ‪ On Line‬ﺑﻪ ﺑﺎﺱ ﻣﺘﺼﻞ ﺍﺳﺖ ﺩﺭ ﺣﺎﻟﻴﻜﻪ ﻛﻪ ‪ BT200‬ﻓﻘﻂ ﺩﺭ ﻣﻮﻗﻊ‬
‫ﺍﻧﺠﺎﻡ ﺗﺴﺖ ﺑﻪ ﺑﺎﺱ ﻭﺻﻞ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻫﻢ ﻣﻮﺍﺭﺩ ﻗﺎﺑﻞ ﺁﺷﻜﺎﺭ ﺗﻮﺳﻂ ﺍﻳﻦ ﻭﺳﻴﻠﻪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫ﻗﻄﻊ ﺷﺪﻥ ﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ﺧﻄﻮﻁ‬ ‫•‬

‫ﺍﺗﺼﺎﻝ ﻛﻮﺗﺎﻩ ﺑﻴﻦ ﺧﻄﻮﻁ ﻳﺎ ﺧﻄﻮﻁ ﺑﺎ ﺷﻴﻠﺪ‬ ‫•‬

‫ﭘﻼﺭﻳﺘﻪ ﺑﺮ ﻋﻜﺲ ﺧﻄﻮﻁ ‪ A‬ﻭ ‪B‬‬ ‫•‬

‫ﺁﺩﺭﺱ ‪ Node‬ﻣﺸﻜﻞ ﺩﺍﺭ ﻫﻤﺮﺍﻩ ﺑﺎ ﻋﻠﺖ ﺍﺷﻜﺎﻝ‬ ‫•‬

‫ﻭﺿﻌﻴﺖ ﺗﺮﻣﻴﻨﻴﺘﻮﺭﻫﺎ‬ ‫•‬

‫ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ‬ ‫•‬

‫ﻓﺎﺻﻠﻪ ﺗﺎ ﻧﻘﻄﻪ ﺑﺮﻭﺯ ﺧﻄﺎ‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫‪١٧٩‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬

‫‪ ٢-١-١٠‬ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ ﺩﺭ ﺷﺒﻜﻪ ﻫﺎﻱ ﻧﻮﺭﻱ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺑﺤﺚ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺍﺷﺎﺭﻩ ﺷﺪ ﻧﺼﺐ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻧﺴﺒﺖ ﺑﻪ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺣﺴﺎﺱ ﺗﺮ ﻭ ﺁﺳﻴﺐ ﭘﺬﻳﺮﺗﺮ‬
‫ﺍﺳﺖ‪ .‬ﺍﺯ ﺟﻤﻠﻪ ﺍﺷﻜﺎﻻﺗﻲ ﻛﻪ ﺩﺭ ﺣﻴﻦ ﻧﺼﺐ ﻣﻤﻜﻦ ﺍﺳﺖ ﭘﻴﺶ ﺑﻴﺎﻳﺪ ﺑﻪ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﻣﻴﺘﻮﺍﻥ ﺍﺷﺎﺭﻩ ﻛﺮﺩ‪:‬‬
‫ﻛﺸﻴﺪﻥ ﻓﻴﺒﺮ ﺗﺤﺖ ﻛﺸﺶ ﻭ ﺍﺳﺘﺮﺱ ﺯﻳﺎﺩ‬ ‫•‬
‫ﺧﻢ ﻛﺮﺩﻥ ﻓﻴﺒﺮ ﺑﻴﺶ ﺍﺯ ﺣﺪ ﻣﺠﺎﺯ‬ ‫•‬

‫ﺍﺷﻜﺎﻝ ﺩﺭ ﺍﺗﺼﺎﻝ ﻛﺎﻧﻜﺘﻮﺭ ﺑﻪ ﻓﻴﺒﺮ ﺩﺭ ﻧﻘﺎﻁ ﺍﺗﺼﺎﻝ ﺑﻪ ﺩﺳﺘﮕﺎﻩ‬ ‫•‬

‫ﻋﺪﻡ ﺩﻗﺖ ﺩﺭ ﺍﻳﺠﺎﺩ ‪ Splice‬ﻫﺎ ﻭ ﻭﺟﻮﺩ ﺍﺷﻜﺎﻻﺗﻲ ﻣﺎﻧﻨﺪ ﺯﻳﺮ ﺩﺭ ﻣﺤﻞ ﺍﺗﺼﺎﻝ‬ ‫•‬

‫ﻋﻮﺍﻣﻞ ﻓﻮﻕ ﻣﻨﺠﺮ ﺑﻪ ﻣﻴﺮﺍﻳﻲ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﻣﻴﺸﻮﻧﺪ‪ .‬ﺑﻮﻳﮋﻩ ﺩﺭ ﻧﻘﺎﻁ ﺍﺗﺼﺎﻝ ﺩﻭ ﻛﺎﺑﻞ ﺑﻪ ﻳﻜﺪﻳﮕﺮ ﺑﺎﻳﺪ ﺩﻗﺖ ﻛﺎﻓﻲ ﺭﺍ‬
‫ﺑﻜﺎﺭ ﺑﺮﺩ ﻭ ﺣﺘﻲ ﺍﻟﻤﻘﺪﻭﺭ ﺑﺠﺎﻱ ‪ Splice‬ﻣﻜﺎﻧﻴﻜﻲ ﺍﺯ ‪ Splice‬ﺟﻮﺷﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬ ‫‪١٨٠‬‬

‫ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺗﻮﺿﻴﺤﺎﺕ ﻓﻮﻕ ﺣﺘﻲ ﺑﺎ ﻭﺟﻮﺩ ﺩﻗﺖ ﺩﺭ ﻣﺮﺍﺣﻞ ﻧﺼﺐ ‪ ،‬ﻣﻴﺮﺍﻳﻲ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻋﻮﺍﻣﻞ ﺩﻳﮕﺮﻱ ﻧﻴﺰ‬
‫ﻣﺎﻧﻨﺪ ﻃﻮﻝ ﻛﺎﺑﻞ ﻭ ﺟﻨﺲ ﻛﺎﻧﻜﺘﻮﺭﻫﺎ ﺑﻄﻮﺭ ﺍﺟﺘﻨﺎﺏ ﻧﺎﭘﺬﻳﺮ ﻣﻨﺠﺮ ﺑﻪ ﻣﻴﺮﺍﻳﻲ ﺳﻴﮕﻨﺎﻝ ﻣﻴﺸﻮﻧﺪ ﺷﻜﻞ ﺯﻳﺮ‪.‬‬

‫ﺑﻨﺎﺑﺮﺍﻳﻦ ﻳﻜﻲ ﺍﺯ ﻣﺴﺎﻳﻞ ﻣﻬﻢ ﻛﻪ ﺑﻌﺪ ﺍﺯ ﺍﺗﻤﺎﻡ ﻧﺼﺐ ﺑﺎﻳﺪ ﺑﺪﺍﻥ ﺗﻮﺟﻪ ﺷﻮﺩ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﻣﻴﺰﺍﻥ ﻣﻴﺮﺍﻳﻲ ﺑﺮﺍﺳﺎﺱ ﻛﻴﻔﻴﺖ‬
‫ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﺍﺳﺖ ﻛﻪ ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺯ ﻭﺳﺎﻳﻞ ﻣﺨﺘﻠﻔﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻳﻦ ﻭﺳﺎﻳﻞ ﺧﺎﺹ ﺩﻭﺭﺍﻥ ﻧﺼﺐ‬
‫ﻭ ‪ Commissioning‬ﻧﻴﺴﺘﻨﺪ ﺑﻠﻜﻪ ﺩﺭ ﻫﻨﮕﺎﻡ ﺑﻬﺮﻩ ﺑﺮﺩﺍﺭﻱ ﺍﺯ ﺳﻴﺴﺘﻢ ﻧﻴﺰ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﻪ ﺁﻧﻬﺎ ﻧﻴﺎﺯ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ‪.‬‬

‫‪Power Source & Meter‬‬ ‫ﺍﻟﻒ (‬

‫ﺍﻳﻦ ﻭﺳﻴﻠﻪ ﻣﺘﺸﻜﻞ ﺍﺯ ﻣﻨﺒﻊ ﻓﺮﺳﺘﻨﺪﻩ ﻧﻮﺭ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﻳﻚ ﻃﺮﻑ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﻗﺮﺍﺭ ﻣﻴﮕﻴﺮﺩ ﻭ ﮔﻴﺮﻧﺪﻩ ﺍﻱ ﺩﺍﺭﺩ ﻛﻪ ﺩﺭ‬
‫ﺳﻤﺖ ﺩﻳﮕﺮ ﻓﻴﺒﺮ ﺑﺴﺘﻪ ﻣﻴﺸﻮﺩ‪ .‬ﺑﺎ ﺍﺭﺳﺎﻝ ﻧﻮﺭ ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﺩﺭﻳﺎﻓﺖ ﺁﻥ ﺗﻮﺳﻂ ﮔﻴﺮﻧﺪﻩ ﻣﻴﺰﺍﻥ ﻣﻴﺮﺍﻳﻲ ﺳﻴﮕﻨﺎﻝ ﺍﻧﺪﺍﺯﻩ‬
‫ﮔﻴﺮﻱ ﻣﻴﺸﻮﺩ‪ .‬ﺍﮔﺮ ﻧﺘﻴﺠﻪ ﺭﺿﺎﻳﺖ ﺑﺨﺶ ﻧﺒﻮﺩ ﻻﺯﻡ ﺍﺳﺖ ﺑﺎ ﻭﺳﻴﻠﻪ ﺩﻳﮕﺮﻱ ﺑﻨﺎﻡ ‪ OTDR‬ﻋﻠﺖ ﺍﺷﻜﺎﻝ ﺑﺮﺭﺳﻲ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٨١‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬

‫ﺏ ( ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪ OLM‬ﺑﺮﺍﻱ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﻛﻴﻔﻴﺖ ﺳﻴﮕﻨﺎﻝ‬

‫ﺑﺎ ‪ OLM‬ﺩﺭ ﺑﺨﺸﻬﺎﻱ ﻗﺒﻞ ﺁﺷﻨﺎ ﺷﺪﻳﻢ ﻭ ﺩﻳﺪﻳﻢ ﻛﻪ ﺑﺮﺍﻱ ﺍﻳﺠﺎﺩ ﺷﺒﻜﻪ ‪ Profibus‬ﺑﺎ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺩﺭ ﻣﺴﺎﻓﺖ ﻫﺎﻱ ﻃﻮﻻﻧﻲ‬
‫ﺑﺎﻳﺪ ﺍﺯ ﺍﻳﻦ ﻭﺳﻴﻠﻪ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ‪ .‬ﺩﺭ ﺑﺮﺧﻲ ‪ OLM‬ﻫﺎ )ﻧﻮﻉ ‪ (V3‬ﺍﻣﻜﺎﻥ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﻛﻴﻔﻴﺖ ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﻣﺤﻞ ﻓﺮﺍﻫﻢ‬
‫ﺷﺪﻩ ﺍﺳﺖ‪.‬‬

‫ﺑﺎ ﺍﺗﺼﺎﻝ ﻳﻚ ﻭﻟﺘﻤﺘﺮ ﺑﻪ ‪ OLM‬ﻣﻴﺘﻮﺍﻥ ﻣﻌﺎﺩﻝ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﺭﺍ ﺩﺭ ﺁﻥ ﻧﻘﻄﻪ ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﻧﻤﻮﺩ ﺳﭙﺲ ﺑﺎ‬
‫ﺗﻮﺟﻪ ﺑﻪ ﻣﻨﺤﻨﻲ ﺯﻳﺮ ﻭﺿﻌﻴﺖ ﻛﻴﻔﻴﺖ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﺑﺮﺁﻭﺭﺩ ﻧﻤﻮﺩ‪ .‬ﻧﻘﻄﻪ ﺑﺤﺮﺍﻧﻲ ‪ ١٠٠‬ﻣﻴﻠﻲ ﻭﻟﺖ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬ ‫‪١٨٢‬‬

‫ﺝ ( ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ‪OTDR‬‬

‫‪ OTDR‬ﻳﺎ ‪ Optical Time Domain Reflectometer‬ﻭﺳﻴﻠﻪ ﺍﻱ ﺍﺳﺖ ﻛﻪ ﺗﻮﺳﻂ ﺁﻥ ﻣﻴﺘﻮﺍﻥ ﺩﻗﻴﻘﺘﺮﻳﻦ ﺍﻃﻼﻋﺎﺕ ﺭﺍ‬
‫ﺩﺭ ﻣﻮﺭﺩ ﺍﺷﻜﺎﻻﺕ ﻓﻴﺒﺮ ﺑﺪﺳﺖ ﺁﻭﺭﺩ‪.‬‬

‫ﺭﻭﺵ ﻛﺎﺭ ‪ OTDR‬ﺑﻪ ﺍﻳﻦ ﺻﻮﺭﺕ ﺍﺳﺖ ﻛﻪ ﻧﻮﺭﻱ ﺑﺎ ﻃﻮﻝ ﻣﻮﺝ ‪ ٨٥٠‬ﻳﺎ ‪ ١٣٠٠‬ﻧﺎﻧﻮﻣﺘﺮ ﺍﺭﺳﺎﻝ ﻛﺮﺩﻩ ﻭ ﺑﺎﺯ ﺗﺎﺏ ﺁﻥ ﺭﺍ‬
‫ﺍﻧﺪﺍﺯﻩ ﮔﻴﺮﻱ ﻣﻴﻨﻤﺎﻳﺪ‪ .‬ﺳﭙﺲ ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺷﻜﻞ ﻣﻮﺝ ﺳﻴﮕﻨﺎﻝ ﻛﻪ ﻧﻤﻮﻧﻪ ﺍﻱ ﺍﺯ ﺁﻥ ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﺁﻣﺪﻩ ﺍﺳﺖ ﻋﻴﻮﺏ ﻓﻴﺒﺮ ﺭﺍ‬
‫ﺁﻧﺎﻟﻴﺰ ﻛﺮﺩﻩ ﻭ ﮔﺰﺍﺭﺵ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٨٣‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻭﺳﺎﻳﻞ ﺗﺸﺨﻴﺺ ﻋﻴﺐ‬

‫ﺑﺮ ﺍﺳﺎﺱ ﺍﻳﻦ ﺷﻜﻞ ﻣﻮﺝ ﻣﻮﺍﺭﺩ ﻣﺨﺘﻠﻒ ﻗﺎﺑﻞ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺍﺳﺖ ﺍﺯ ﺟﻤﻠﻪ ‪:‬‬
‫ﻧﻘﻄﻪ ﺍﻱ ﺍﺯ ﻓﻴﺒﺮ ﻛﻪ ﺁﺳﻴﺐ ﺩﻳﺪﻩ ﺍﺳﺖ ) ﺩﺭ ﺍﺛﺮ ﻋﻮﺍﻣﻠﻲ ﻫﻤﭽﻮﻥ ﻛﺸﺶ ﻳﺎ ﺧﻤﺶ ﻏﻴﺮ ﻣﺠﺎﺯ (‬ ‫•‬

‫ﻓﺎﺻﻠﻪ ﻧﻘﻄﻪ ﺁﺳﻴﺐ ﺩﻳﺪﻩ‬ ‫•‬

‫ﻭﺿﻌﻴﺖ ‪ Splice‬ﻫﺎ‬ ‫•‬

‫ﻭﺿﻌﻴﺖ ﻛﺎﻧﻜﺘﻮﺭﻫﺎ‬ ‫•‬

‫ﻭ ﻧﻬﺎﻳﺘﺎ ﻣﻴﺰﺍﻥ ﻣﻴﺮﺍﻳﻲ ﺳﻴﮕﻨﺎﻝ‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪Step7‬‬ ‫‪١٨٤‬‬

‫‪ ٢-١٠‬ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‬

‫ﻫﻤﺎﻧﻨﺪ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ‪ ،‬ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻫﺎﻱ ﻣﺘﻨﻮﻋﻲ ﻧﻴﺰ ﺗﻮﺳﻂ ﺳﺎﺯﻧﺪﮔﺎﻥ ﻣﺨﺘﻠﻒ ﺟﻬﺖ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﻋﻴﻮﺏ ﺷﺒﻜﻪ ﻃﺮﺍﺣﻲ‬
‫ﻭ ﻋﺮﺿﻪ ﺷﺪﻩ ﺍﺳﺖ‪ .‬ﺯﻳﻤﻨﺲ ﻧﻴﺰ ﻋﻼﻭﻩ ﺑﺮ ‪ Step7‬ﻛﻪ ﺍﻣﻜﺎﻥ ﺗﺸﺨﻴﺺ ﻋﻴﻮﺏ ﺷﺒﻜﻪ ﺭﺍ ﺩﺭ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ ﺧﻮﺩ ﺩﺍﺭﺩ‬
‫ﻧﺮﻡ ﺍﻓﺰﺍﺭ ﻫﺎﻱ ﻛﻤﻜﻲ ﺩﻳﮕﺮﻱ ﺭﺍ ﺟﻬﺖ ﺗﺴﺖ ﻭ ﺧﻄﺎ ﻳﺎﺑﻲ ﺷﺒﻜﻪ ﻣﻌﺮﻓﻲ ﻧﻤﻮﺩﻩ ﺍﺳﺖ ﻛﻪ ﺍﺯ ﺍﻳﻦ ﺟﻤﻠﻪ ﻣﻴﺘﻮﺍﻥ ﺑﻪ ﻧﺮﻡ‬
‫ﺍﻓﺰﺍﺭ ‪ AMPROLIZER‬ﺍﺷﺎﺭﻩ ﻛﺮﺩ ﻭﻟﻲ ﺁﻧﭽﻪ ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﻮﺭﺩ ﺑﺤﺚ ﻣﺎﺳﺖ ﺻﺮﻓﹰﺎ ﺧﻄﺎ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ‪ Step7‬ﻭ ﺯﻳﺮ‬
‫ﺑﺮﻧﺎﻣﻪ ﻫﺎﻱ ﺁﻥ ﻣﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ ‪Diagnostics‬‬ ‫ﺍﻟﻒ(‬

‫ﺍﻳﻦ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ ﭘﺲ ﺍﺯ ﻧﺼﺐ ‪ Step7‬ﺩﺭ ﺯﻳﺮ ﻣﺠﻤﻮﻋﻪ ‪ NCM S7 PROFIBUS‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﺗﻮﺳﻂ ﺍﻳﻦ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ ﻣﻴﺘﻮﺍﻥ ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻳﻲ ﻛﻪ ﺗﻮﺳﻂ ﻛﺎﺭﺕ ‪ CP‬ﺑﻪ ﺷﺒﻜﻪ ‪ Profibus‬ﻣﺘﺼﻞ ﺷﺪﻩ ﺍﻧﺪ ﺭﺍ ﺑﺎ‬
‫ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻖ ﻣﺸﺎﻫﺪﻩ ﻛﺮﺩ‪ .‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﻛﺎﺭﺑﺮﺩ ﻣﻬﻢ ﺁﻥ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﻭ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﺍﺳﺖ ﻭ ﺍﺯ ﺍﻳﻨﺮﻭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ‬
‫ﺍﻳﻦ ﺑﺮﻧﺎﻣﻪ ﺭﻭﻱ ﻛﺎﻣﭙﻴﻮﺗﺮ ﻭﻗﺘﻲ ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ﻛﻪ ﺩﺍﺭﺍﻱ ﻛﺎﺭﺕ ‪ CP‬ﻣﻨﺎﺳﺐ ﺑﺎﺷﺪ‪.‬‬
‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﺑﺎﻻﻱ ﺻﻔﺤﻪ ﺑﻌﺪ ﻣﺸﺎﻫﺪﻩ ﻣﻴﺸﻮﺩ ﭘﺲ ﺍﺯ ﺍﺭﺗﺒﺎﻁ ‪ On Line‬ﺑﺎ ﺷﺒﻜﻪ ﻣﻴﺘﻮﺍﻥ ﻣﻮﺍﺭﺩ ﺯﻳﺮ ﺭﺍ ﺑﺎ‬
‫ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻖ ﻣﺸﺎﻫﺪﻩ ﻛﺮﺩ‪:‬‬
‫ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻳﻲ ﻛﻪ ﺍﺭﺗﺒﺎﻁ ‪ FDL‬ﺩﺍﺭﻧﺪ‬ ‫•‬

‫ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻳﻲ ﻛﻪ ﺍﺭﺗﺒﺎﻁ ‪ FMS‬ﺩﺍﺭﻧﺪ‬ ‫•‬

‫‪ Node‬ﻫﺎﻱ ﺷﺒﻜﻪ‬ ‫•‬

‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ‬ ‫•‬

‫‪Diagnostic Buffer‬‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪١٨٥‬‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪Step7‬‬

‫ﺷﻜﻞ ﺯﻳﺮ ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻖ ﻣﺮﺑﻮﻁ ﺑﻪ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ‪ FMS‬ﺭﺍ ﺑﺎ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺁﻥ ﺩﺭ ﺣﺎﻟﺖ ‪ OnLine‬ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪.‬‬

‫ﻭﻗﺘﻲ ﺭﻭﻱ ﻳﻜﻲ ﺍﺯ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﭘﻨﺠﺮﻩ ﻓﻮﻕ ﻛﻠﻴﻚ ﻛﻨﻴﻢ ﺷﺎﺧﻪ ﻫﺎﻱ ﺩﻳﮕﺮﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﻣﻴﺸﻮﺩ ‪ .‬ﺩﺭ ﺍﻳﻦ‬
‫ﭘﻨﺠﺮﻩ ﺷﻤﺎﺭﻩ ﺩﻳﺘﺎﺑﻼﻙ ﺍﻳﻨﺪﻛﺲ ﺷﺪﻩ ﺑﺮﺍﻱ ‪ Report‬ﻭ ﻣﻴﺰﺍﻥ ﺩﻳﺘﺎﻱ ﺩﺭﻳﺎﻓﺖ ﺷﺪﻩ ﻧﺸﺎﻥ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺍﺯ ﻃﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪Step7‬‬ ‫‪١٨٦‬‬

‫ﺏ( ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ ‪ Step7‬ﺑﺮﺍﻱ ﻣﺸﺎﻫﺪﻩ ﻭﺿﻌﻴﺖ‬

‫ﻭﻗﺘﻲ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻭ ﺷﺒﻜﻪ ﺍﻱ ﺗﻮﺳﻂ ‪ Step7‬ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻭ ﺑﻪ ﺁﻥ ﺩﺍﻧﻠﻮﺩ ﺷﺪﻩ ﺑﺎﺷﺪ ﺍﮔﺮ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺯﻳﺮ ﺑﺮﻧﺎﻣﻪ‬
‫‪ Hwconfig‬ﺗﻮﺳﻂ ﻣﻨﻮﻱ ‪ Station > Open Online‬ﭘﻨﺠﺮﻩ ‪ OnLine‬ﺭﺍ ﻣﺸﺎﻫﺪﻩ ﻛﻨﻴﻢ ﻭﺿﻌﻴﺖ ﻛﺎﺭﺗﻬﺎ ﻭ ﻣﺪﻭﻝ‬
‫ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺭﺍ ﻫﻤﺮﺍﻩ ﺑﺎ ﻋﻼﺋﻤﻲ ﻣﺎﻧﻨﺪ ﺯﻳﺮ ﻣﺸﺎﻫﺪﻩ ﺧﻮﺍﻫﻴﻢ ﻛﺮﺩ‪.‬‬

‫ﺍﻳﻦ ﻋﻼﻣﺖ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﺁﻧﺴﺖ ﻛﻪ ‪ CPU‬ﻛﺎﺭﺕ ﻳﺎ ﻣﺪﻭﻝ ﺭﺍ ﻧﺸﻨﺎﺧﺘﻪ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ‬ ‫•‬
‫ﺁﻧﭽﻪ ﺑﻪ ‪ CPU‬ﺩﺍﻧﻠﻮﺩ ﺷﺪﻩ ﺑﺎ ﺁﻧﭽﻪ ﺩﺭ ﻋﻤﻞ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻳﻜﻲ ﻧﻴﺴﺖ‪.‬‬
‫ﺍﻳﻦ ﻋﻼﻣﺖ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﻭﺟﻮﺩ ﺍﺷﻜﺎﻝ ﺩﺭ ﻣﺪﻭﻝ ﺍﺳﺖ ﻳﻌﻨﻲ ‪ CPU‬ﻣﺪﻭﻝ ﺭﺍ ﺷﻨﺎﺧﺘﻪ‬ ‫•‬

‫ﻭﻟﻲ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﻧﻤﻴﺘﻮﺍﻧﺪ ﺍﺯ ﺁﻥ ﺩﻳﺘﺎ ﺑﮕﻴﺮﺩ ﻳﺎ ﺑﻪ ﺁﻥ ﺩﻳﺘﺎ ﺑﻔﺮﺳﺘﺪ‪.‬‬

‫ﻛﺎﺭﺕ ﻳﺎ ﻣﺪﻭﻝ ﻗﺎﺑﻠﻴﺖ ‪ Diagnostic‬ﻧﺪﺍﺭﺩ ﻭ ‪ CPU‬ﻧﻤﻴﺘﻮﺍﻧﺪ ﻭﺿﻌﻴﺖ ﺁﻧﺮﺍ ﺑﺼﻮﺭﺕ‬ ‫•‬
‫‪ Online‬ﻧﺸﺎﻥ ﺩﻫﺪ‪.‬‬

‫ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻛﺎﺭﺕ ‪ AI‬ﺩﭼﺎﺭ ﺍﺷﻜﺎﻝ ﺍﺳﺖ ﻭ ﺩﺭ ﻋﻴﻦ ﺣﺎﻝ ‪ CPU‬ﻧﺘﻮﺍﻧﺴﺘﻪ ‪ ET200‬ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺭﻭﻱ‬
‫ﺷﺒﻜﻪ ‪ DP‬ﺭﺍ ﺑﺸﻨﺎﺳﺪ ‪ .‬ﺩﺭ ﭼﻨﻴﻦ ﻣﻮﺍﺭﺩﻱ ﻣﻌﻤﻮﻻ ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﻣﺪﻭﻝ ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻘﺘﺮﻱ ﺍﺭﺍﺋﻪ ﺧﻮﺍﻫﻨﺪ ﺷﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٨٧‬‬ ‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪Step7‬‬ ‫ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ‬

‫ﺑﺮﺍﻱ ﻣﺸﺎﻫﺪﻩ ﻭﺿﻌﻴﺖ ﻛﻠﻲ ‪ Node‬ﻫﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺷﺒﻜﻪ ﻣﻴﺘﻮﺍﻥ ﺍﺯ ‪ Quick View‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻭﻫﻤﻪ ﺁﻧﻬﺎ ﺭﺍ ﺩﺭ‬
‫ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺯﻳﺮ ﻣﺸﺎﻫﺪﻩ ﻧﻤﻮﺩ ﺳﭙﺲ ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻖ ﺭﺍ ﺑﺎ ﻛﻠﻴﻚ ﻛﺮﺩﻥ ﺭﻭﻱ ﻭﺳﻴﻠﻪ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺪﺳﺖ ﺁﻭﺭﺩ‪.‬‬

‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪Step7‬‬ ‫‪ ٣-١٠‬ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻴﺪﺍﻧﻴﻢ ﺩﺭ ﻣﻮﻗﻊ ﺑﺮﻭﺯ ﺧﻄﺎ ﻛﺎﺭ ﺑﺮﻧﺎﻣﻪ ﺍﺻﻠﻲ ‪ CPU‬ﻳﻌﻨﻲ ‪ OB1‬ﺗﻮﺳﻂ ﻭﻗﻔﻪ ﺍﻱ ﻛﻪ ﺑﻪ ﺳﻴﺴﺘﻢ ﺍﻋﻤﺎﻝ‬
‫ﻣﻴﺸﻮﺩ ﻗﻄﻊ ﺷﺪﻩ ﻭ ﺍﻛﺜﺮﹰﺍ ‪ CPU‬ﺑﻪ ﻣﺪ ‪ Stop‬ﺭﻓﺘﻪ ﭼﺮﺍﻍ ‪ SF‬ﺭﻭﻱ ﺁﻥ ﺭﻭﺷﻦ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺩﺭ ﭼﻨﻴﻦ‬
‫ﺷﺮﺍﻳﻄﻲ ﺍﺗﺼﺎﻝ ﺑﻪ ‪ PLC‬ﻭ ﻣﺸﺎﻫﺪﻩ ﻣﺤﺘﻮﻳﺎﺕ ‪ Diagnostic Buffer‬ﺁﻥ ﻣﻴﺘﻮﺍﻧﺪ ﺗﺎ ﺣﺪﻱ ﺑﻪ ﺗﺸﺨﻴﺺ ﻭ ﺭﻓﻊ ﻋﻴﺐ‬
‫ﻛﻤﻚ ﻛﻨﺪ ﻛﻪ ﺍﻟﺒﺘﻪ ﻣﺴﺘﻠﺰﻡ ﺻﺮﻑ ﺯﻣﺎﻥ ﺍﺳﺖ ‪ .‬ﺯﻣﺎﻧﻲ ﻛﻪ ﻫﺮ ﺛﺎﻧﻴﻪ ﺁﻥ ﺩﺭ ﻓﺮﺁﻳﻨﺪ ﺍﺭﺯﺷﻤﻨﺪ ﻭ ﮔﺮﺍﻧﺒﻬﺎﺳﺖ ‪ .‬ﺭﻭﺵ‬
‫ﺑﻬﺘﺮ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺭﺍﻫﻜﺎﺭﻫﺎﻱ ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ ﺗﻮﺳﻂ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ﻭﻗﻔﻪ ﻫﺎﺳﺖ ﻛﺎﺭﻱ ﻛﻪ ﻻﺯﻡ ﺍﺳﺖ ﻗﺒﻞ ﺍﺯ ﺍﻳﺠﺎﺩ ﺧﻄﺎ‬
‫ﺍﻧﺠﺎﻡ ﺷﻮﺩ ﺗﺎ ﺩﺭ ﺻﻮﺭﺕ ﺑﺮﻭﺯ ﺁﻥ ‪ ،‬ﺳﻴﺴﺘﻢ ﺑﻪ ﻣﺴﻴﺮ ﺻﺤﻴﺤﻲ ﻫﺪﺍﻳﺖ ﺷﺪﻩ ﻭ ﺩﺭ ﻛﻤﺘﺮﻳﻦ ﺯﻣﺎﻥ ﻣﻤﻜﻦ ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻖ‬
‫ﺧﻄﺎ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻛﺎﺭﺑﺮ ﻗﺮﺍﺭ ﮔﻴﺮﺩ‪.‬‬
‫ﺍﻳﻦ ﺑﺤﺚ ﻛﻠﻲ ﺍﺳﺖ ﻭ ﺍﺧﺘﺼﺎﺹ ﺑﻪ ﺷﺒﻜﻪ ﻧﺪﺍﺭﺩ ‪ Step7 .‬ﺑﻼﻙ ﻫﺎﻳﻲ ﺭﺍ ﺗﺤﺖ ﻋﻨﻮﺍﻥ ‪ OB‬ﻫﺎﻱ ﺧﺎﺹ ﺑﺮﺍﻱ ﺍﻳﻦ‬
‫‪HMI‬‬ ‫ﻣﻨﻈﻮﺭ ﺗﻌﺒﻴﻪ ﻛﺮﺩﻩ ﺍﺳﺖ ﻳﻚ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺲ ﺣﺮﻓﻪ ﺍﻱ ‪،‬ﺑﺎﻳﺪ ﺑﺘﻮﺍﻧﺪ ﺍﺯ ﺍﻳﻦ‪ OB‬ﻫﺎ ‪،‬ﺑﺮﺍﻱ ﻟﻴﻨﻚ ﺑﺎ ﻗﺴﻤﺖ‬
‫)ﻣﻮﻧﻴﺘﻮﺭﻳﻨﮓ( ﻭﺳﺎﻳﺮ ﻛﺎﺭﺑﺮﺩﻫﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﺎﻳﺪ‪ .‬ﻏﺎﻟﺐ ﺍﻳﻦ ‪ OB‬ﻫﺎ ‪،‬ﺑﻪ ﮔﻮﻧﻪ ﺍﻱ ﻫﺴﺘﻨﺪ ﻛﻪ ﺍﮔﺮ ﺻﺪﺍ ﺯﺩﻩ ﺷﻮﻧﺪ ﻭ‬
‫‪OB‬‬ ‫‪ Program‬ﻧﺸﺪﻩ ﺑﺎﺷﻨﺪ‪ CPU،‬ﺑﻪ ﻣﺪ ‪ STOP‬ﻣﻲ ﺭﻭﺩ ﻭ ﺍﻳﻦ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﺎﻋﺚ ﺳﺮﺩﺭﮔﻤﻲ ﻛﺎﺭﺑﺮ ﺷﻮﺩ‪ .‬ﻟﺬﺍ ﻛﺎﺭ ﺑﺎ‬
‫ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺟﺰﻭ ﻣﻠﺰﻭﻣﺎﺕ ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪ S7‬ﺩﺭ ﺗﻤﺎﻣﻲ ﺳﻄﻮﺡ ﻣﻲ ﺑﺎﺷﺪ‪ .‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ‪ OB‬ﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ‬
‫ﺧﻄﺎ ﻫﺎ ﺑﻴﺸﺘﺮﻳﻦ ﺩﺭﺟﻪ ﺍﻭﻟﻮﻳﺖ ﺭﺍ ﺩﺍﺭﻧﺪ ﻭ ﺑﻪ ﺍﻳﻦ ﻋﻠﺖ ﻣﻴﺘﻮﺍﻧﻨﺪ ﻛﺎﺭ ‪ OB1‬ﻳﺎ ﺳﺎﻳﺮ ‪ OB‬ﻫﺎ ﺭﺍ ﻗﻄﻊ ﻛﻨﻨﺪ‪ .‬ﺟﺰﺋﻴﺎﺕ‬
‫ﻣﺮﺑﻮﻁ ﺑﻪ ﻧﺤﻮﻩ ﻛﺎﺭ ﺑﺎ ﺍﻳﻦ ‪ OB‬ﻫﺎ ﺭﺍ ﺑﺎﻳﺪ ﺩﺭ ﻣﺮﺍﺟﻊ ﺩﻳﮕﺮ ﺟﺴﺘﺠﻮ ﻛﺮﺩ ﺩﺭ ﺍﻳﻨﺠﺎ ﻣﺎ ﺻﺮﻓﺎ ﺑﻪ ‪ OB‬ﻫﺎﻱ ﻣﺮﺗﺒﻂ ﺑﺎ‬
‫ﺧﻄﺎﻫﺎﻱ ﺷﺒﻜﻪ ﻣﻲ ﭘﺮﺩﺍﺯﻳﻢ ﻭ ﺑﺮﺍﻱ ﺗﻜﻤﻴﻞ ﻣﻄﻠﺐ ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﺭﺍ ﺑﻪ ﻛﺘﺎﺏ ﺭﺍﻫﻨﻤﺎﻱ ﺟﺎﻣﻊ ‪ Step7‬ﺟﻠﺪ ﺍﻭﻝ ﺗﺎﻟﻴﻒ‬
‫ﻣﺤﻤﺪ ﺭﺿﺎ ﻣﺎﻫﺮ ﺍﺭﺟﺎﻉ ﻣﻴﺪﻫﻴﻢ‪ .‬ﺑﺴﻴﺎﺭﻱ ﺍﺯ ‪ OB‬ﻫﺎﻱ ﺑﺤﺚ ﺷﺪﻩ ﺩﺭ ﻛﺘﺎﺏ ﻣﺰﺑﻮﺭ ﺩﺭ ﺷﺒﻜﻪ ‪ Profibus‬ﻧﻴﺰ ﻛﺎﺭﺑﺮﺩ‬
‫ﺩﺍﺭﻧﺪ ‪ .‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺻﺮﻓﺎ ﺑﻪ ﺩﻭ ‪ OB‬ﺑﺮﺍ ﻱ ﺷﻨﺎﺳﺎﻳﻲ ﺧﻄﺎ ﻫﻤﺮﺍﻩ ﺑﺎ ﻣﺜﺎﻝ ﺍﺷﺎﺭﻩ ﻣﻲ ﻛﻨﻴﻢ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪Step7‬‬ ‫ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ‬ ‫‪١٨٨‬‬

‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪) OB86‬ﺧﻄﺎﻱ ‪( DP Slave‬‬

‫‪ OB86‬ﺑﺮﺍﻱ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺧﻄﺎﻫﺎﻳﻲ ﻣﺎﻧﻨﺪ ﻧﺒﻮﺩ ﻣﺪﻭﻝ ‪ IM‬ﻳﺎ ﺧﺮﺍﺑﻲ ﻳﺎ ﻗﻄﻊ ﺷﺪﻥ ﻛﺎﺑﻞ ﺁﻥ ﻭﺧﻄﺎﻱ ‪ DP Slave‬ﺩﺭ‬
‫‪Profibus‬‬ ‫ﺭﻭﻱ ﺑﺎﺱ ‪ DP‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻓﺮﺽ ﻛﻨﻴﺪ ﭘﺮﻭﮊﻩ ﺍﻱ ﺑﺎ ‪ CPU315-2DP‬ﺩﺍﺭﻳﻢ ﻛﻪ ﺩﻭ ‪ ET 200M‬ﺗﻮﺳﻂ‬
‫ﺑﻪ ﺁﻥ ﻣﺘﺼﻞ ﻫﺴﺘﻨﺪ‪ .‬ﺁﺩﺭﺱ ‪ Diagnostic‬ﺍﻳﻦ ﺗﺠﻬﻴﺰﺍﺕ ﺭﺍ ﺑﺎ ﻛﻠﻴﻚ ﺭﺍﺳﺖ ﻣﺎﻭﺱ ﺩﺭ ﺑﺨﺶ ‪ Properties‬ﻣﻴﺘﻮﺍﻥ‬
‫‪ 1020 ,1022‬ﻣﻴﺒﺎﺷﻨﺪ‪.‬‬ ‫ﺩﻳﺪ ﻛﻪ ﺩﺭ ﺍﻳﻦ ﻣﺜﺎﻝ ﺍﻳﻦ ﺁﺩﺭﺳﻬﺎ‬

‫ﺍﻛﻨﻮﻥ ‪ OB86‬ﺭﺍ ﺩﺭ ﭘﻮﺷﻪ ‪ Blocks‬ﺍﻳﺠﺎﺩ ﻛﺮﺩﻩ ﻭ ﺁﻧﺮﺍ ﺑﺎﺯ ﻣﻴﻜﻨﻴﻢ ﺳﭙﺲ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺩﻳﺘﺎﻱ ﻣﺤﻠﻲ‬
‫‪ OB86_MDL_ADDR‬ﻛﻪ ﺩﺭ ﺟﺪﻭﻝ ‪ Local Data‬ﺩﺭ ﺑﺎﻻﻱ ﺑﻼﻙ ﻣﻌﺮﻓﻲ ﺷﺪﻩ ﻣﻴﺘﻮﺍﻧﻴﻢ ﺑﺮﻧﺎﻣﻪ ﺯﻳﺮ ﺭﺍ ﺑﻨﻮﻳﺴﻴﻢ ﺗﺎ‬
‫ﺩﺭ ﺻﻮﺭﺕ ﺑﺮﻭﺯ ﺧﻄﺎ ﺩﺭﻫﺮ ﻛﺪﺍﻡ ﺍﺯ ‪ ET‬ﻫﺎ ﺑﻴﺘﻬﺎﻱ ﺟﺪﺍﮔﺎﻧﻪ ﺍﻱ ﺭﺍ ﺩﺭ ﺩﻳﺘﺎ ﺑﻼﻙ ﺳﺖ ﻛﻨﺪ‪ .‬ﺍﻳﻦ ﺑﻴﺖ ﻫﺎ ﻣﻴﺘﻮﺍﻧﻨﺪ ﺑﻪ‬
‫‪ Tag‬ﺩﺭ ﺳﻴﺴﺘﻢ ‪ HMI‬ﻣﺘﺼﻞ ﺷﺪﻩ ﻭ ﻛﺎﺭﺑﺮ ﺭﺍ ﺍﺯ ﻭﺿﻌﻴﺖ ﺁﮔﺎﻩ ﺳﺎﺯﺩ‪.‬‬
‫‪L OB86_MDL_ADDR‬‬
‫‪L 1022‬‬
‫‪==I‬‬
‫‪S DB1.DBX0.0‬‬

‫‪L OB86_MDL_ADDR‬‬
‫‪L 1021‬‬
‫‪==I‬‬
‫‪S DB1.DBX0.1‬‬
‫‪Techno-Electro.com‬‬

‫‪١٨٩‬‬ ‫ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻧﺮﻡ ﺍﻓﺰﺍﺭ‪Step7‬‬ ‫ﻣﺪﻳﺮﻳﺖ ﺧﻄﺎ‬

‫ﺑﺮﻧﺎﻣﻪ ﻧﻮﻳﺴﻲ ‪) OB122‬ﺧﻄﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ‪(I/O‬‬

‫‪ OB122‬ﺑﺮﺍﻱ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺧﻄﺎﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ‪ I/O‬ﻫﺎ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﭼﻪ ﺍﻳﻦ ﺧﻄﺎ ﻧﺎﺷﻲ ﺍﺯ ﺧﺮﺍﺏ ﺑﻮﺩﻥ ﻣﺪﻭﻝ ﺑﺎﺷﺪ‬
‫ﭼﻪ ﺍﺷﻜﺎﻝ ﺩﺭ ﺷﻨﺎﺧﺘﻪ ﻧﺸﺪﻥ ﺁﺩﺭﺱ ﺗﻮﺳﻂ ‪ CPU‬ﺑﺎﺷﺪ‪.‬‬
‫ﺍﮔﺮ ﺑﺮﺍﻱ ﺁﺩﺭﺳﻬﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﻳﻜﻲ ﺍﺯ ‪ ET‬ﻫﺎﻱ ﻣﺜﺎﻝ ﻗﺒﻠﻲ ﺑﺨﻮﺍﻫﻴﻢ ‪ OB122‬ﺭﺍ ﺑﻨﻮﻳﺴﻴﻢ ﻣﻴﺘﻮﺍﻥ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺩﻳﺘﺎﻱ‬
‫ﻣﺤﻠﻲ ‪ OB122_MEM_ADDR‬ﻛﻪ ﺩﺭ ﺟﺪﻭﻝ ‪ Local Data‬ﺩﺭ ﺑﺎﻻﻱ ﺑﻼﻙ ﻣﻌﺮﻓﻲ ﺷﺪﻩ ﺑﺮﻧﺎﻣﻪ ﺯﻳﺮ ﺭﺍ ﺑﻨﻮﻳﺴﻴﻢ ﺗﺎ‬
‫ﺩﺭ ﺻﻮﺭﺕ ﺑﺮﻭﺯ ﺧﻄﺎ ﺩﺭ ﻭﺭﻭﺩﻱ ‪ ET‬ﻫﺎ ﻓﻼﮔﻲ ﺳﺖ ﺷﻮﺩ‪ .‬ﺑﻪ ﺁﺩﺭﺱ ﻛﺎﺭﺗﻬﺎﻱ ‪ I/O‬ﺩﺭ ﭘﺎﻳﻴﻦ ﺷﻜﻞ ﺻﻔﺤﻪ ﻗﺒﻞ ﺩﻗﺖ‬
‫ﺷﻮﺩ‪.‬‬

‫‪L OB122_MEM_ADDR‬‬
‫‪L 256‬‬
‫‪>=I‬‬
‫(‪A‬‬
‫‪L OB122_MEM_ADDR‬‬
‫‪L 268‬‬
‫‪<=I‬‬
‫)‬
‫”‪S “Err‬‬
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﺿﻤﻴﻤﻪ ‪۱‬‬

‫ﻣﺮﻭﺭﻱ ﺑﺮ ﻣﻔﺎﻫﻴﻢ ﻭ ﺍﺻﻄﻼﺣﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﺻﻨﻌﺘﻲ‬

‫ﻣﺸﺘﻤﻞ ﺑﺮ ‪:‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬ ‫•‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬ ‫•‬
‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬ ‫•‬
‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ ‪OSI‬‬ ‫•‬
‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬ ‫‪١٩٢‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬

‫ﺁﺭﺍﻳﺶ ﻓﻴﺰﻳﻜﻲ ﺍﺟﺰﺍﻱ ﻳﻚ ﺷﺒﻜﻪ ﻭ ﻧﺤﻮﻩ ﺍﺗﺼﺎﻝ ﺁﻧﻬﺎ ﺑﻪ ﻳﻜﺪﻳﮕﺮ ﺭﺍ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺷﺒﻜﻪ ﻣﻴﮕﻮﻳﻨﺪ ﻭ ﺑﻪ ﺳﻪ ﺩﺳﺘﻪ ﺍﺻﻠﻲ ‪ BUS‬ﻭ‬
‫‪ Ring‬ﻭ ‪ Star‬ﺗﻘﺴﻴﻢ ﻣﻴﺸﻮﺩ ﺑﺎ ﺗﺮﻛﻴﺐ ﺍﻳﻦ ﺳﻪ ﺩﺳﺘﻪ ﻣﻴﺘﻮﺍﻥ ﺁﺭﺍﻳﺶ ﻫﺎﻱ ﺩﻳﮕﺮﻱ ﻣﺎﻧﻨﺪ ‪ Mesh‬ﻭ ‪ Tree‬ﺩﺍﺷﺖ ﭘﺲ ﺑﻄﻮﺭ‬
‫ﻛﻠﻲ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺷﺒﻜﻪ ﻣﻴﺘﻮﺍﻧﺪ ﻳﻜﻲ ﺍﺯ ﺍﻧﻮﺍﻉ ﺯﻳﺮ ﺑﺎﺷﺪ‪:‬‬
‫‪Line‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ Bus‬ﻳﺎ‬ ‫‪.١‬‬
‫ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Ring‬‬ ‫‪.٢‬‬
‫ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Star‬‬ ‫‪.٣‬‬
‫ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Mesh‬‬ ‫‪.٤‬‬
‫ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Tree‬‬ ‫‪.٥‬‬

‫‪ -١‬ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Bus‬‬
‫ﻣﺘﺪﺍﻭﻟﺘﺮﻳﻦ ﻭ ﺳﺎﺩﻩ ﺗﺮﻳﻦ ﺷﻜﻞ ﺷﺒﻜﻪ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﻧﺼﺐ ﺁﻥ ﺭﺍﺣﺖ ﻭ ﻫﺰﻳﻨﻪ ﺍﺵ ﻛﻤﺘﺮ ﺍﺯ ﺳﺎﻳﺮ ﺍﻧﻮﺍﻉ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﺑﺮﺍﺣﺘﻲ ﻗﺎﺑﻞ ﺗﻮﺳﻌﻪ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﺩﻭﻃﺮﻑ ﻛﺎﺑﻞ ) ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎ ( ﻻﺯﻡ ﺍﺳﺖ ﺑﺎ ﻣﻘﺎﻭﻣﺖ ‪ Terminator‬ﺑﺴﺘﻪ ﺷﻮﺩ ﺗﺎ ﺍﺯ ﺑﺎﺯﺗﺎﺏ ﺳﻴﮕﻨﺎﻝ‬ ‫•‬

‫ﺟﻠﻮﮔﻴﺮﻱ ﮔﺮﺩﺩ‪.‬‬
‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺁﻥ ﻣﺸﻜﻞ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺁﻥ ﺑﺎﻻ ﻧﻴﺴﺖ ﺯﻳﺮﺍ ﺑﺴﺘﻪ ﺑﻪ ﻧﻮﻉ ﺁﻥ ﺑﺎ ﻗﻄﻊ ﺷﺪﻥ ﻛﺎﺑﻞ ﻳﺎ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻤﻜﻦ ﺍﺳﺖ ﻛﻞ‬ ‫•‬

‫ﺷﺒﻜﻪ ﺍﺯ ﻛﺎﺭ ﺑﻴﻔﺘﺪ‪.‬‬

‫ﺑﺎﺱ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺼﻮﺭﺗﻬﺎﻱ ﻣﺨﺘﻠﻔﻲ ﺑﺴﺘﻪ ﺷﻮﺩ‪ .‬ﺳﻪ ﻧﻮﻉ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺩﺭ ﺯﻳﺮ ﻣﻮﺭﺩ ﻣﻘﺎﻳﺴﻪ ﻗﺮﺍﺭ ﮔﺮﻓﺘﻪ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪١٩٣‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬

‫‪Tap and Drop‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺼﻮﺭﺕ‬

‫ﺩﺭ ﺍﻳﻦ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻣﺸﺎﻫﺪﻩ ﻣﻴﺸﻮﺩ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﺗﻮﺳﻂ ﻛﺎﻧﻜﺘﻮﺭﻫﺎﻱ ‪ T‬ﺷﻜﻞ ﺑﻪ ﺑﺎﺱ ﻣﺘﺼﻞ ﺷﺪﻩ‬
‫ﺍﺳﺖ‪ .‬ﻛﺎﺑﻠﻲ ﻛﻪ ﺍﺭﺗﺒﺎﻁ ﺍﻳﺴﺘﮕﺎﻩ ﺑﺎ ﺑﺎﺱ ﺭﺍ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ ﻛﺎﺑﻞ ‪ Drop‬ﻧﺎﻣﻴﺪﻩ ﻣﻴﺸﻮﺩ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ‪:‬‬
‫ﺍﮔﺮ ﻛﺎﺑﻞ ‪ Drop‬ﻗﻄﻊ ﺷﻮﺩ ﻳﺎ ﺍﻳﺴﺘﮕﺎﻫﻲ ﻣﺸﻜﻞ ﭘﻴﺪﺍ ﻛﻨﺪ ﻓﻘﻂ ﻫﻤﺎﻥ ﺍﻳﺴﺘﮕﺎﻩ ﺍﺯ ﺷﺒﻜﻪ ﺧﺎﺭﺝ ﻣﻴﺸﻮﺩ ﻭﻟﻲ ﻛﻞ‬ ‫•‬

‫ﺷﺒﻜﻪ ﻗﻄﻊ ﻧﻤﻴﺸﻮﺩ‪.‬‬

‫ﺍﮔﺮ ﻛﺎﺑﻞ ﺍﺻﻠﻲ ﺷﺒﻜﻪ ) ‪ ( Trunk‬ﻗﻄﻊ ﺷﻮﺩ ﻛﻞ ﺷﺒﻜﻪ ﺍﺯ ﻛﺎﺭ ﻣﻲ ﺍﻓﺘﺪ‪.‬‬ ‫•‬

‫ﻃﻮﻝ ﻛﺎﺑﻞ ‪ Drop‬ﻧﺒﺎﻳﺪ ﺍﺯ ﺣﺪﻱ ﺑﻴﺸﺘﺮ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﻓﺎﺻﻠﻪ ﺑﻴﻦ ﺩﻭ ‪ Tap‬ﻧﺒﺎﻳﺪ ﺍﺯ ﺣﺪﻱ ﻛﻤﺘﺮ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫‪ Termination‬ﺑﺴﺘﻪ ﺷﻮﺩ‪.‬‬ ‫ﺑﺎﺱ ﺑﺎﻳﺪ ﺑﺎ ﻣﻘﺎﻭﻣﺖ‬ ‫•‬

‫‪Daisy Chain‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺼﻮﺭﺕ‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻛﺎﺑﻞ ‪ Drop‬ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ ﺑﺎﺱ ﺷﺒﻜﻪ ﺍﺯ ﻫﻤﺎﻥ ﻧﻘﻄﻪ ﺍﺗﺼﺎﻝ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﺍﺩﺍﻣﻪ ﻣﻲ ﻳﺎﺑﺪ ﺑﻌﺒﺎﺭﺕ ﺩﻳﮕﺮ ﺍﻳﻦ ﺍﺗﺼﺎﻝ‬
‫ﺩﺭ ﻛﺎﻧﻜﺘﻮﺭ ﻣﺘﺼﻞ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﺑﺮﻗﺮﺍﺭ ﻣﻴﺸﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ‪:‬‬
‫ﺍﮔﺮ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺸﻜﻞ ﭘﻴﺪﺍ ﻛﻨﺪ ﺷﺒﻜﻪ ﻗﻄﻊ ﻧﻤﻲ ﺷﻮﺩ‪.‬‬ ‫•‬

‫ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﻛﺎﺑﻞ ‪ Drop‬ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ‪.‬ﺍﮔﺮ ﻛﺎﺑﻞ ﺍﺻﻠﻲ ﺩﺭ ﻧﻘﻄﻪ ﺍﻱ ﻗﻄﻊ ﺷﻮﺩ ﻛﻞ ﺷﺒﻜﻪ ﺍﺯ ﻛﺎﺭ ﻣﻲ ﺍﻓﺘﺪ‪.‬‬ ‫•‬

‫ﺑﺎﺱ ﺑﺎﻳﺪ ﺑﺎ ﻣﻘﺎﻭﻣﺖ ‪ Termination‬ﺑﺴﺘﻪ ﺷﻮﺩ‪.‬‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬ ‫‪١٩٤‬‬

‫‪Regenerative‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺑﺼﻮﺭﺕ‬
‫ﺩﺭﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻛﺎﺑﻞ ﻭﺭﻭﺩﻱ ﺑﻪ ﻳﻚ ﭘﻮﺭﺕ ﻭ ﻛﺎﺑﻞ ﺧﺮﻭﺟﻲ ﺑﻪ ﭘﻮﺭﺕ ﺩﻳﮕﺮﺩﺳﺘﮕﺎﻩ ﻣﺘﺼﻞ ﻣﻴﺸﻮﺩ‪.‬ﺑﻨﺎﺑﺮ ﺍﻳﻦ‬
‫ﺑﺮﺧﻼﻑ ﺩﻭ ﻧﻮﻉ ﻗﺒﻠﻲ ﺩﺭ ﺍﻳﻨﺠﺎ ﺑﺎﺱ ﻳﻚ ﭘﺎﺭﭼﻪ ﻧﻴﺴﺖ ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺍﮔﺮ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺧﺮﺍﺏ ﺷﻮﺩ ﻛﻞ ﺷﺒﻜﻪ ﺍﺯ ﻛﺎﺭ ﻣﻲ‬
‫ﺍﻓﺘﺪ ﻭﻟﻲ ﺍﮔﺮ ﻛﺎﺑﻞ ﻗﻄﻊ ﺷﻮﺩ ﻣﺎﺑﻘﻲ ﺷﺒﻜﻪ ﻣﻴﺘﻮﺍﻧﺪ ﻛﺎﺭ ﻛﻨﺪ‪.‬‬

‫‪ -٢‬ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Ring‬‬
‫ﺍﮔﺮ ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎﻱ ﺷﺒﻜﻪ ﺑﺎ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺭﺍ ﺑﺼﻮﺭﺕ ﻣﻨﺎﺳﺐ ﺑﻬﻢ ﻣﺘﺼﻞ ﻛﻨﻴﻢ ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ Ring‬ﺑﻮﺟﻮﺩ ﻣﻲ‬ ‫•‬

‫ﺁﻳﺪ‪.‬ﺩﺭ ﻭﺍﻗﻊ ﻫﺮ ‪ Node‬ﺑﺎ ﺩﻭ ‪ Node‬ﺩﺭ ﺩﻭ ﻃﺮﻑ ﺧﻮﺩ ﺑﺼﻮﺭﺕ ‪ Point To Point‬ﻣﺮﺗﺒﻂ ﺍﺳﺖ‪.‬‬
‫ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺁﻥ ﺑﻴﺸﺘﺮ ﺍﺯ ﻧﻮﻉ ﺑﺎﺱ ﺍﺳﺖ‪.‬ﺩﺭ ﺑﺮﺧﻲ ﻛﺎﺭﺑﺮﺩﻫﺎ ﺷﺒﻜﻪ ‪ Ring‬ﺩﺭ ﺻﻮﺭﺕ ﻗﻄﻊ ﺷﺪﻥ ﻛﺎﺑﻞ ﺍﺭﺗﺒﺎﻃﻲ‬ ‫•‬

‫ﺑﺼﻮﺭﺕ ﺑﺎﺱ ﺑﻪ ﻛﺎﺭ ﺧﻮﺩ ﺍﺩﺍﻣﻪ ﻣﻴﺪﻫﺪ‪.‬ﺍﮔﺮ ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺧﻴﻠﻲ ﺑﺎﻻ ﻧﻴﺎﺯ ﺑﺎﺷﺪ ﻣﻴﺘﻮﺍﻥ ﺑﺎ ﺳﺨﺖ ﺍﻓﺰﺍﺭ ﻣﻨﺎﺳﺐ ﺩﻭ‬
‫‪ Redundant‬ﻛﺎﺭ ﻛﻨﻨﺪ‪.‬‬ ‫‪ Ring‬ﺍﻳﺠﺎﺩ ﻛﺮﺩ ﻛﻪ ﺑﺼﻮﺭﺕ‬
‫‪Star‬‬ ‫‪ -٣‬ﺗﻮﭘﻮﻟﻮﮊﻱ‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﺑﺎ ﻛﺎﺑﻞ ﻣﺠﺰﺍ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺮﻛﺰﻱ ﻛﻪ ﻣﻴﺘﻮﺍﻧﺪ ﻳﻚ ‪ Hub‬ﺑﺎﺷﺪ ﻣﺘﺼﻞ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﺍﮔﺮ ﻛﺎﺑﻞ ﺑﻴﻦ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺗﺎ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺮﻛﺰﻱ ﻗﻄﻊ ﺷﻮﺩ ﻓﻘﻂ ﻫﻤﺎﻥ ﺍﻳﺴﺘﮕﺎﻩ ﻛﻨﺎﺭ ﻣﻴﺮﻭﺩ ﭘﺲ ﻧﺴﺒﺖ ﺑﻪ ‪ Bus‬ﻭ‬ ‫•‬

‫‪ Ring‬ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺑﺎﻻﺗﺮﻱ ﺩﺍﺭﺩ ﻭﻟﻲ ﺍﮔﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺮﻛﺰﻱ ﻗﻄﻊ ﺷﻮﺩ ﻛﻞ ﺷﺒﻜﻪ ﺍﺯ ﻛﺎﺭ ﻣﻲ ﺍﻓﺘﺪ‪.‬‬
‫ﭘﻴﺎﺩﻩ ﺳﺎﺯﻱ ﺁﻥ ﺍﮔﺮﭼﻪ ﺳﺎﺩﻩ ﺍﺳﺖ ﻭﻟﻲ ﻧﺴﺒﺖ ﺑﻪ ‪ Bus‬ﻭ ‪ Ring‬ﻛﺎﺑﻞ ﻛﺸﻲ ﺑﻴﺸﺘﺮﻱ ﻧﻴﺎﺯ ﺩﺍﺭﺩ‪.‬‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪١٩٥‬‬ ‫ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﻣﺨﺘﻠﻒ ﺷﺒﻜﻪ‬

‫‪ -٤‬ﺗﻮﭘﻮﻟﻮﮊﻱ ‪Tree‬‬
‫ﺍﻳﻦ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻛﻪ ﺷﻜﻞ ﺩﺭﺧﺘﻲ ﺩﺍﺭﺩ ﺗﺮﻛﻴﺒﻲ ﺍﺳﺖ ﺍﺯ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﻭ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺳﺘﺎﺭﻩ ﻭ ﻣﺰﺍﻳﺎﻱ ﺁﻥ ﺩﻭ ﺭﺍ ﺑﺎ‬ ‫•‬
‫ﻫﻢ ﺩﺍﺭﺍﺳﺖ‪.‬‬

‫‪Hybrid‬‬ ‫‪ -٥‬ﺗﻮﭘﻮﻟﻮﮊﻱ ‪ Mesh‬ﻳﺎ‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﺍﺯ ﻃﺮﻳﻖ ﻛﺎﺑﻞ ﻣﺴﺘﻘﻠﻲ ﺍﺭﺗﺒﺎﻁ ﺩﺍﺭﻧﺪ‪.‬‬ ‫•‬

‫ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ ﺁﻥ ﺑﺴﻴﺎﺭ ﺑﺎﻻﺳﺖ‪.‬‬ ‫•‬

‫ﻋﻴﺐ ﻳﺎﺑﻲ ﺁﻥ ﻣﺸﻜﻞ ﻭ ﺍﻧﻌﻄﺎﻑ ﭘﺬﻳﺮﻱ ﺁﻥ ﻛﻢ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﺩﺭ ﻋﻤﻞ ﺑﻨﺪﺭﺕ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﻣﻘﺎﻳﺴﻪ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ﺳﻪ ﮔﺎﻧﻪ ﺍﺻﻠﻲ‬

‫ﺟﺪﻭﻝ ﺯﻳﺮ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻫﺎﻱ ‪ BUS‬ﻭ ‪ Star‬ﻭ ‪ Ring‬ﺭﺍ ﺍﺯ ﺑﺮﺧﻲ ﺟﻨﺒﻪ ﻫﺎ ﻣﻮﺭﺩ ﻣﻘﺎﻳﺴﻪ ﻗﺮﺍﺭ ﺩﺍﺩﻩ ﺍﺳﺖ‪:‬‬
‫‪Bus‬‬ ‫‪Ring‬‬ ‫‪Star‬‬
‫ﺑﺎﻻ‬ ‫ﭘﺎﻳﻴﻦ‬ ‫ﭘﺎﻳﻴﻦ‬ ‫ﺍﻧﻌﻄﺎﻑ ﭘﺬﻳﺮﻱ‬
‫ﻛﻢ‬ ‫ﻣﺘﻮﺳﻂ‬ ‫ﺯﻳﺎﺩ‬ ‫ﻫﺰﻳﻨﻪ‬
‫ﻣﺸﻜﻞ‬ ‫ﻣﺸﻜﻞ‬ ‫ﺭﺍﺣﺖ ﺗﺮ‬ ‫ﻋﻴﺐ ﻳﺎﺑﻲ‬
‫ﻛﻢ‬ ‫ﻣﺘﻮﺳﻂ‬ ‫ﺯﻳﺎﺩ‬ ‫ﻗﺎﺑﻠﻴﺖ ﺍﻃﻤﻴﻨﺎﻥ‬
‫‪Techno-Electro.com‬‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬ ‫‪١٩٦‬‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ )‪ (Transmission Media‬ﻭﺳﺎﻳﻞ ﻭ ﻋﻮﺍﻣﻞ ﻓﻴﺰﻳﻜﻲ ﻫﺴﺘﻨﺪ ﻛﻪ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ﺟﺎﺑﺠﺎ ﻣﻴﻜﻨﻨﺪ‬
‫ﻣﺎﻧﻨﺪ ﻳﻚ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ‪ .‬ﺷﻜﻞ ﺯﻳﺮ ﺩﺳﺘﻪ ﺑﻨﺪﻱ ﺭﻭﺷﻬﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺭﺍ ﻧﺸﺎﻥ ﻣﻴﺪﻫﺪ‪ .‬ﺩﺭ ﻫﻤﻪ ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﺩﺭ ﺳﻤﺖ‬
‫ﻓﺮﺳﺘﻨﺪﻩ ﺩﻳﺘﺎ ﺑﻪ ﺍﻧﺮﮊﻱ )ﺍﻟﻜﺘﺮﻳﺴﻴﺘﻪ ﻭ ﻧﻮﺭ ﻭ ‪ (..‬ﻭ ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ‪ ،‬ﺍﻧﺮﮊﻱ ﺑﻪ ﺩﻳﺘﺎ ﺗﺒﺪﻳﻞ ﻣﻴﮕﺮﺩﺩ‪.‬‬

‫‪ -١‬ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺑﻪ ﺭﻭﺵ ﺍﻟﻜﺘﺮﻳﻜﻲ‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺍﺯ ﻛﺎﺑﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﻣﺴﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﻛﻪ ﺩﺍﺭﺍﻱ ﺩﻭ ﺩﺳﺘﻪ ﻛﻠﻲ ﺯﻳﺮ ﺍﺳﺖ ﻳﻜﻲ ﺯﻭﺝ ﺳﻴﻢ ﺑﻬﻢ ﺗﺎﺑﻴﺪﻩ ﻭ‬
‫ﺩﻳﮕﺮﻱ ﻛﻮﺍﻛﺴﻴﺎﻝ‪.‬‬
‫ﻛﺎﺑﻞ ﺑﺎ ﺯﻭﺝ ﺳﻴﻢ ﺑﻬﻢ ﺗﺎﺑﻴﺪﻩ )‪(TP‬‬ ‫‪.I‬‬
‫ﻛﺎﺑﻞ ﺑﺎ ﺯﻭﺝ ﺳﻴﻢ ﺑﻪ ﻫﻢ ﺗﺎﺑﻴﺪﻩ ﻳﺎ ‪ Twisted Pair‬ﺍﺯ ﺭﺷﺘﻪ ﺳﻴﻢ ﻫﺎﻱ ﺭﻭﻛﺶ ﺩﺍﺭ ﻣﺴﻲ ﺗﺸﻜﻴﻞ ﺷﺪﻩ‬ ‫•‬

‫ﻛﻪ ﻫﺮ ﺟﻔﺖ ﺁﻥ ﺑﻪ ﻫﻢ ﺗﺎﺑﻴﺪﻩ ﺷﺪﻩ ﺍﻧﺪ‪.‬‬

‫ﺗﺎﺑﻴﺪﻩ ﺷﺪﻥ ﺟﻔﺖ ﺳﻴﻢ ﺗﺎ ﺣﺪ ﺯﻳﺎﺩﻱ ﭘﺪﻳﺪﻩ ﺗﺪﺍﺧﻞ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺑﺎ ﺟﻔﺖ ﺳﻴﻢ ﻫﺎﻱ ﻣﺠﺎﻭﺭ ﻛﻪ ﺑﻪ ﭘﺪﻳﺪﻩ‬ ‫•‬

‫‪ Crosstalk‬ﻣﻮﺳﻮﻡ ﺍﺳﺖ ﺭﺍ ﻛﺎﻫﺶ ﻣﻴﺪﻫﺪ ﺷﻜﻞ ﺯﻳﺮ‪:‬‬

‫‪ Crosstalk‬ﺩﺭ ﻛﺎﺑﻞ ﺑﺎ ﺯﻭﺝ ﺳﻴﻢ ﺑﻬﻢ ﺗﺎﺑﻴﺪﻩ )‪(TP‬‬

‫‪Techno-Electro.com‬‬

‫‪١٩٧‬‬ ‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬

‫ﻛﺎﺑﻞ ﻫﺎﻱ ‪ TP‬ﺑﻪ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ﺑﺪﻭﻥ ﺷﻴﻠﺪ )‪ (UTP‬ﻭ ﺷﻴﻠﺪ ﺩﺍﺭ )‪ (STP‬ﺗﻘﺴﻴﻢ ﻣﻴﺸﻮﻧﺪ‪.‬‬ ‫•‬

‫ﻧﻮﻉ ﺑﺪﻭﻥ ﺷﻴﻠﺪ ‪ UTP‬ﻳﺎ ) ‪ (Unshielded Twisted Pair‬ﺩﺍﺭﺍﻱ ﻇﺮﻓﻴﺖ ﻣﺤﺪﻭﺩﺗﺮﻱ ﺍﺳﺖ ﻭ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ‬ ‫•‬

‫ﺩﺭ ﺁﻥ ﻛﻤﺘﺮ ﺍﺯ ﻧﻮﻉ ﺷﻴﻠﺪ ﺩﺍﺭ ﺍﺳﺖ ﻭ ﺩﺭ ﻣﻘﺎﺑﻞ ﻧﻮﻳﺰ ﺁﺳﻴﺐ ﭘﺬﻳﺮ ﺗﺮ ﺍﺳﺖ ‪.‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻛﺎﺑﻞ ‪ UTP‬ﻭ ‪STP‬‬

‫ﻧـﻮﻉ ﺷـﻴﻠﺪ ﺩﺍﺭ ‪ STP‬ﻳﺎ )‪ (Shielded Twisted Pair‬ﺩﺍﺭﺍﻱ ﺍﻧﻮﺍﻉ ﻣﺨﺘﻠﻔﻲ ﺍﺳﺖ ﻣﻤﻜﻦ ﺍﺳﺖ ﻛﻞ‬ ‫•‬
‫ﺯﻭﺟﻬـﺎ ﻓﻘـﻂ ﻳﻚ ﺷﻴﻠﺪ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻨﺪ ﻭ ﻣﻤﻜﻦ ﺍﺳﺖ ﻫﺮ ﺯﻭﺝ ﻳﻚ ﺷﻴﻠﺪ ﻣﺠﺰﺍ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﺍﺯ ﺍﻳﻨﺮﻭ ﺑﻪ ﺩﺳﺘﻪ‬
‫ﻫـﺎ ﻳـﺎ ﺍﺻـﻄﻼﺣﹰﺎ ‪ Category‬ﻫـﺎﻱ ﻣﺨﺘﻠﻔـﻲ ﺗﻘﺴـﻴﻢ ﻣـﻴﮕﺮﺩﺩ ﻛﻪ ﺳﺮﻋﺖ ﻭ ﻇﺮﻓﻴﺖ ﺍﻧﺘﻘﺎﻝ ﺁﻧﻬﺎ ﻣﺘﻔﺎﻭﺕ‬
‫ﺍﺳﺖ‪.‬‬
‫‪ Category 1‬ﻓﻘﻂ ﺑﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺻﻮﺗﻲ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻭ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺁﻥ ﻛﻤﺘﺮ ﺍﺯ ‪ 1 Mbps‬ﺍﺳﺖ‪.‬‬ ‫•‬
‫‪ Category 2‬ﺑﺮﺍﻱ ﺩﻳﺘﺎ ﻭﻟﻲ ﺑﺎ ﺳﺮﻋﺖ ﻛﻢ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻜﺎﺭ ﺭﻭﺩ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺁﻥ ‪ 4 Mbps‬ﺍﺳﺖ‪.‬‬ ‫•‬
‫‪ Category 3‬ﻣﻴﺘﻮﺍﻧﺪ ﺑﺮﺍﻱ ﺷﺒﻜﻪ ﻫﺎﻱ ﻛﺎﻣﭙﻴﻮﺗﺮﻱ ﺑﻜﺎﺭ ﺭﻭﺩ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺁﻥ ‪ 10 Mbps‬ﺍﺳﺖ‪.‬‬ ‫•‬
‫‪ Category 4‬ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺑﺎ ﺳﺮﻋﺖ ‪ 20 Mbps‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬
‫‪ Category 5‬ﺑـﺮﺍﻱ ﺍﻧـﺘﻘﺎﻝ ﺩﻳـﺘﺎ ﺑـﺎ ﺳﺮﻋﺖ ‪ 100 Mbps‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻭ ﺩﺭ ﺷﺒﻜﻪ ﻫﺎﻱ ﻣﺤﻠﻲ ‪LAN‬‬ ‫•‬
‫ﻣﺮﺳﻮﻡ ﺍﺳﺖ‪.‬‬
‫‪ Category 5E‬ﻛـﻪ ﺯﻭﺝ ﺳـﻴﻢ ﻫـﺎ ﺩﺭ ﺁﻥ ﻧﺴﺒﺖ ﺑﻪ ‪ Cate 5‬ﺑﻴﺸﺘﺮ ﺑﻪ ﻫﻢ ﺗﺎﺑﻴﺪﻩ ﺷﺪﻩ ﺍﻧﺪ ﻣﻴﺘﻮﺍﻧﺪ ﺑﺮﺍﻱ‬ ‫•‬
‫ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺑﺎ ﺳﺮﻋﺖ ‪ 1000 Mbps‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬ ‫‪١٩٨‬‬

‫‪ Category 6‬ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ ﺩﺭ ﺁﻥ ‪ ٦‬ﺑﺮﺍﺑﺮ ‪ Cate 5‬ﺍﺳﺖ‪.‬‬ ‫•‬

‫‪ Category 7‬ﺩﺍﺭﺍﻱ ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ ﺗﺎ ﺣﺪ ﻳﻚ ﮔﻴﮕﺎ ﺑﻴﺖ ﻣﻴﺒﺎﺷﺪ‬ ‫•‬

‫‪Coaxial‬‬ ‫‪ . II‬ﻛﺎﺑﻞ‬
‫ﻛﺎﺑﻞ ﻛﻮﺁﻛﺴﻴﺎﻝ ﻳﻜﻲ ﺍﺯ ﺍﻭﻟﻴﻦ ﺍﻧﻮﺍﻉ ﻭﺍﺳﻂ ﻫﺎﻳﻲ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺷﺒﻜﻪ ‪ LAN‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﻣﻌﻤﻮﻻ ﺑﺮﺍﻱ ﺷﺒﻜﻪ ﺍﺗﺮﻧﺖ ﺑﺎ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﺍﻳﻦ ﻛﺎﺑﻞ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﺍﺯﺩﻭ ﺭﺷﺘﻪ ﻫﻢ ﻣﺮﻛﺰ ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﻛﻪ ﻳﻜﻲ ﻧﻘﺶ ﺷﻴﻠﺪ ﺭﺍ ﻧﻴﺰ ﺩﺍﺭﺩ‪.‬‬ ‫•‬

‫ﺷﻴﻠﺪ ﻛﺎﺑﻞ ﻣﻘﺎﻭﻣﺖ ﺁﻥ ﺭﺍ ﺩﺭ ﻣﻘﺎﺑﻞ ﻧﻮﻳﺰ ﭘﺬﻳﺮﻱ ﺯﻳﺎﺩ ﻣﻴﻜﻨﺪ‪.‬‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫‪١٩٩‬‬ ‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬

‫‪ -٢‬ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺗﻮﺳﻂ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺍﺯ ﻛﺎﺑﻞ ﻧﻮﺭﻱ )‪ (Fiber Optic‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻭﻟﻴﻦ ﺍﻧﻮﺍﻉ ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺍﺯ ﺣﺪﻭﺩ ‪ ١٩٧٦‬ﺩﺭ ﺁﻣﺮﻳﻜﺎ ﺑﻜﺎﺭ‬
‫ﮔﺮﻓﺘﻪ ﺷﺪ‪ .‬ﺩﺭ ﺍﺑﺘﺪﺍ ﺗﻠﻔﺎﺕ ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﺁﻥ ﺯﻳﺎﺩ ﺑﻮﺩ ﻭ ﺑﺮﺍﻱ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻛﻮﺗﺎﻩ ﺑﻜﺎﺭ ﻣﻴﺮﻓﺖ ﺑﺎ ﺑﻬﺒﻮﺩ ﻣﺘﺮﻳﺎﻝ ﻭ ﺗﻜﻨﻮﻟﻮﮊﻱ ﺳﺎﺧﺖ‬
‫‪،‬ﻛﺎﺭﺑﺮﺩ ﺁﻥ ﺑﺘﺪﺭﻳﺞ ﺗﻮﺳﻌﻪ ﭘﻴﺪﺍ ﻛﺮﺩ ﻭ ﻣﺴﺎﻓﺖ ﻫﺎﻳﻲ ﺩﺭ ﺣﺪ ﭼﻨﺪﻳﻦ ﻛﻴﻠﻮﻣﺘﺮ ﺭﺍ ﭘﻮﺷﺶ ﺩﺍﺩ‪.‬‬
‫‪ .I‬ﺳﺎﺧﺘﺎﺭ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬
‫ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺍﺯ ﻳﻚ ﻫﺴﺘﻪ )‪ (Core‬ﻛﻪ ﺍﺯ ﺟﻨﺲ ﺷﻴﺸﻪ ﻳﺎ ﭘﻼﺳﺘﻴﻚ ﺍﺳﺖ ﻭ ﻳﻚ ﭘﻮﺷﺶ ‪ Cladding‬ﻛﻪ ﻫﺴﺘﻪ ﺭﺍ‬
‫ﺍﺣﺎﻃﻪ ﻛﺮﺩﻩ ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﺍﺳﺖ ﻫﺴﺘﻪ ﻧﻮﺭ ﺭﺍ ﺍﻧﺘﻘﺎﻝ ﻣﻴﺪﻫﺪ ﻭ ‪ Cladding‬ﺑﺎﺯﺗﺎﺏ ﻧﻮﺭ ﺭﺍ ﺩﺭ ﻃﻮﻝ ﻓﻴﺒﺮ ﻓﺮﺍﻫﻢ‬
‫ﻣﻴﺴﺎﺯﺩ‪.‬ﻓﻴﺒﺮ ﺩﺍﺭﺍﻱ ﻳﻚ ﭘﻮﺷﺶ ﻧﻬﺎﻳﻲ ﺍﺳﺖ ﻛﻪ ‪ Jacket‬ﻧﺎﻣﻴﺪﻩ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﺳﻄﺢ ﻣﻘﻄﻊ ﻛﻠﻲ ﻳﻚ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﺑﻤﻨﻈﻮﺭ ﺍﺳﺘﺤﻜﺎﻡ ﻣﻜﺎﻧﻴﻜﻲ ﻓﻴﺒﺮ ﭘﻮﺷﺶ ﺩﻳﮕﺮﻱ ﻧﻴﺰ ﺑﻨﺎﻡ ‪ Kevlar‬ﺑﻴﻦ ‪ Cladding‬ﻭ ‪ Jacket‬ﻗﺮﺍﺭ ﻣﻴﺪﻫﻨﺪ‪.‬‬
‫ﻛﺎﺑﻞ ﻓﻴﺒﺮ ﻫﻤﻴﺸﻪ ﺗﻚ ﺭﺷﺘﻪ ﻧﻴﺴﺖ ﻭ ﻣﻤﻜﻦ ﺍﺳﺖ ﺩﺍﺭﺍﻱ ﭼﻨﺪﻳﻦ ﺭﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺑﺎ ﺩﻭ ﺭﺷﺘﻪ ﻓﻴﺒﺮ‬ ‫ﻛﺎﺑﻞ ﻧﻮﺭﻱ ﺑﺎ ﻳﻚ ﺭﺷﺘﻪ ﻓﻴﺒﺮ‬

‫‪Techno-Electro.com‬‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬ ‫‪٢٠٠‬‬

‫ﺍﺻﻮﻝ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬ ‫‪.II‬‬

‫ﺍﺻﻮﻝ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺑﺮ ﺍﺳﺎﺱ ﺑﺎﺯﺗﺎﺏ ﻧﻮﺭ ﺩﺭ ﺁﻥ ﺍﺳﺖ‪ .‬ﻳﻚ ﻣﻨﺒﻊ ﻧﻮﺭﻱ ﻛﻪ ﻣﻴﺘﻮﺍﻧﺪ ﻳﻚ ‪ LED‬ﺑﺎﺷﺪ‬
‫ﻧﻮﺭ ﺭﺍ ﺑﻪ ﺩﺍﺧﻞ ﻓﻴﺒﺮ ﻣﻲ ﺗﺎﺑﺎﻧﺪ‪ .‬ﻧﻮﺭ ﭘﺲ ﺍﺯ ﺑﺎﺯﺗﺎﺏ ﻫﺎﻱ ﻣﺘﻮﺍﻟﻲ ﺑﻪ ﮔﻴﺮﻧﺪﻩ ﻛﻪ ﻣﻴﺘﻮﺍﻧﺪ ﻳﻚ ﻓﺘﻮﺩﻳﻮﺩ ﺑﺎﺷﺪ ﻣﻴﺮﺳﺪ‪.‬‬
‫ﻭﺟﻮﺩ ﻧﻮﺭ ﺑﻌﻨﻮﺍﻥ ‪ 1‬ﻭ ﻋﺪﻡ ﻭﺟﻮﺩﺁﻥ ﺑﻌﻨﻮﺍﻥ ‪ 0‬ﻣﻨﻄﻘﻲ ﺗﻠﻘﻲ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﺷﻜﻞ ﻣﻼﺣﻈﻪ ﻣﻴﺸﻮﺩ‬
‫ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺳﻴﮕﻨﺎﻝ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺑﻪ ﻧﻮﺭ ﺗﺒﺪﻳﻞ ﻣﻴﮕﺮﺩﺩ ﻭ ﺩﺭﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﻋﻤﻞ ﻋﻜﺲ ﻳﻌﻨﻲ ﺗﺒﺪﻳﻞ ﻧﻮﺭ ﺑﻪ‬
‫ﺳﻴﮕﻨﺎﻝ ﺍﻟﻜﺘﺮﻳﻜﻲ ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﻋﻠﺖ ﺑﺎﺯﺗﺎﺏ ﻧﻮﺭ ﺩﺭ ﻓﻴﺒﺮ ﺁﻧﺴﺖ ﻛﻪ ﺿﺮﻳﺐ ﺍﻧﻜﺴﺎﺭ ﻣﺤﻴﻂ ‪ Cladding‬ﻛﻤﺘﺮ ﺍﺯ ﺿﺮﻳﺐ ﺍﻧﻜﺴﺎﺭ ﻫﺴﺘﻪ ﺍﺳﺖ ﻭ ﺍﻳﻦ‬
‫ﻃﺒﻖ ﻗﺎﻧﻮﻥ ‪ Snell‬ﻣﻮﺟﺐ ﺑﺎﺯﺗﺎﺏ ﻧﻮﺭ ﺑﻪ ﺩﺍﺧﻞ ﻓﻴﺒﺮ ﻣﻴﺸﻮﺩ‪.‬ﺿﺮﻳﺐ ﺍﻧﻜﺴﺎﺭ ﺑﺎ ﺣﺮﻑ ‪ n‬ﺩﺭ ﻓﺮﻣﻮﻝ ﺯﻳﺮ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ‪:‬‬
‫‪n1 sinθ1 = n2 sinθ2‬‬
‫ﺿﺮﻳﺐ ﺍﻧﻜﺴﺎﺭ ﻳﻚ ﻣﺎﺩﻩ ﺑﺮﺍﺑﺮ ﺍﺳﺖ ﺑﺎ ﺳﺮﻋﺖ ﻧﻮﺭ ﺩﺭ ﺧﻼ ﺗﻘﺴﻴﻢ ﺑﺮ ﺳﺮﻋﺖ ﻧﻮﺭ ﺩﺭ ﺁﻥ ﻣﺎﺩﻩ ﺍﻳﻦ ﺿﺮﻳﺐ ﺑﺮﺍﻱ ﻫﻮﺍ‬
‫‪ 1.0003‬ﻭ ﺑﺮﺍﻱ ‪ Cladding‬ﺣﺪﻭﺩ ‪ 1.46‬ﻭ ﺑﺮﺍﻱ ﻫﺴﺘﻪ ﻓﻴﺒﺮ ﺣﺪﻭﺩ ‪ 1.48‬ﻣﻴﺒﺎﺷﺪ‪.‬‬
‫ﭘﺲ ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺑﺮ ﺍﺳﺎﺱ ﺑﺎﺯﺗﺎﺏ ﻛﻠﻲ ﺩﺍﺧﻠﻲ ﻳﺎ ‪ (Total Internal Reflection) TIR‬ﺍﺳﺘﻮﺍﺭ‬
‫ﺍﺳﺖ‪.‬‬

‫‪TIR‬‬

‫ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺷﻜﻠﻬﺎﻱ ﺻﻔﺤﻪ ﺑﻌﺪ ﻣﻴﺒﻴﻨﻴﻢ ﻛﻪ ﺯﺍﻭﻳﻪ ﺗﺎﺑﺶ ﻣﻬﻢ ﺍﺳﺖ ‪ .‬ﺍﮔﺮ ﺯﺍﻭﻳﻪ ﺗﺎﺑﺶ ﺍﺯ ﺣﺪﻱ ﻛﻪ ﺣﺪ ﺑﺤﺮﺍﻧﻲ ﻧﺎﻣﻴﺪﻩ‬
‫ﻣﻴﺸﻮﺩ ﻛﻤﺘﺮ ﺑﺎﺷﺪ ﺑﻪ ﺩﺍﺧﻞ ﻓﻴﺒﺮ ﺑﺎﺯﺗﺎﺏ ﭘﻴﺪﺍ ﻧﻤﻴﻜﻨﺪ ﻭ ﺩﺭ ﻣﺤﻴﻂ ‪ Cladding‬ﺟﺬﺏ ﻣﻴﺸﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٠١‬‬ ‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬

‫ﺗﺎﺑﺶ ﺑﺎ ﺯﺍﻭﻳﻪ ﺍﻱ ﺑﺮﺍﺑﺮ ﺑﺎ ﺯﺍﻭﻳﻪ ﺑﺤﺮﺍﻧﻲ‬ ‫ﺗﺎﺑﺶ ﺑﺎ ﺯﺍﻭﻳﻪ ﻛﻤﺘﺮ ﺍﺯ ﺯﺍﻭﻳﻪ ﺑﺤﺮﺍﻧﻲ‬

‫ﭘﺲ ﺑﺮﺍﻱ ﺯﺍﻭﻳﻪ ﺗﺎﺑﺶ ﻣﻨﺎﺳﺐ ﻣﺤﺪﻭﺩﻩ ﺧﺎﺻﻲ ﻭﺟﻮﺩ‬

‫ﺩﺍﺭﺩ‪ .‬ﻧﻜﺘﻪ ﻗﺎﺑﻞ ﺗﻮﺟﻪ ﺩﻳﮕﺮ ﺁﻧﺴﺖ ﻛﻪ ﺍﮔﺮ ﺯﺍﻭﻳﻪ ﺗﺎﺑﺶ‬
‫ﻣﻨﺎﺳﺐ ﺩﺍﺭﻱ ﺷﻴﺐ ﺗﻨﺪ ﺑﺎﺷﺪ )ﻳﻌﻨﻲ ﻧﺰﺩﻳﻚ ﺑﻪ ﺣﺪ‬
‫ﺑﺤﺮﺍﻧﻲ( ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ﺗﻌﺪﺍﺩ ﺩﻓﻌﺎﺕ ﺑﺎﺯ ﺗﺎﺏ ﺑﻴﺸﺘﺮ‬
‫ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻭ ﻧﻮﺭ ﺑﺎﻳﺪ ﻣﺴﺎﻓﺖ ﺑﻴﺸﺘﺮﻱ ﺭﺍ ﻃﻲ ﻛﻨﺪ ﺍﺯ‬
‫ﺍﻳﻨﺮﻭ ﺳﻴﮕﻨﺎﻝ ﺁﻫﺴﺘﻪ ﺗﺮ ﺍﻧﺘﻘﺎﻝ ﻣﻲ ﻳﺎﺑﺪ‪.‬‬
‫ﺗﺎﺑﺶ ﺑﺎ ﺯﺍﻭﻳﻪ ﺑﻴﺸﺘﺮ ﺍﺯ ﺯﺍﻭﻳﻪ ﺑﺤﺮﺍﻧﻲ‬
‫ﻣﺰﺍﻳﺎﻱ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬
‫ﻇﺮﻓﻴﺖ ﻭ ﭘﻬﻨﺎﻱ ﺑﺎﻧﺪ ﺑﺴﻴﺎﺭ ﺑﺎﻻ )ﺑﻴﺶ ﺍﺯ ‪ 2 Gb/s‬ﺑﺮﺍﻱ ﺩﻫﻬﺎ ﻛﻴﻠﻮﻣﺘﺮ(‬ ‫•‬

‫ﻣﻴﺮﺍﻳﻲ ) ‪ (Attenuation‬ﻛﻢ ﺳﻴﮕﻨﺎﻝ ﺩﺭ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻃﻮﻻﻧﻲ‬ ‫•‬

‫ﻛﺎﻫﺶ ﺳﺎﻳﺰ ﻭ ﻭﺯﻥ ﻧﺴﺒﺖ ﺑﻪ ﺳﻴﻢ ﻣﺴﻲ) ﺣﺪﻭ‪.‬ﺩ ‪ ٩٠‬ﺩﺭﺻﺪ ﻛﺎﻫﺶ(‬ ‫•‬

‫‪Cross-talk‬‬ ‫ﺍﻧﺘﻘﺎﻝ ﻣﻄﻤﺌﻦ ﺩﻳﺘﺎ ﺑﺪﻭﻥ ﻭﺟﻮﺩ‬ ‫•‬

‫ﺍﻳﻤﻦ ﺍﺯ ﻧﻈﺮ ﺗﺪﺍﺧﻞ ﺭﺍﺩﻳﻮﻳﻲ ‪(Radio Frequency Interference) RFI‬‬ ‫•‬

‫ﺍﻳﻤﻦ ﺍﺯ ﻧﻈﺮ ﺗﺪﺍﺧﻞ ﺍﻣﻮﺍﺝ ﺍﻟﻜﺘﺮﻭﻣﻐﻨﺎﻃﻴﺴﻲ ‪(Electro Magnetic Interference ) EMI‬‬ ‫•‬

‫)‪ElectroStatic Discharge (ESD‬‬ ‫ﺍﻳﻤﻦ ﺍﺯ ﻧﻈﺮ ﺗﺨﻠﻴﻪ ﺍﻟﻜﺘﺮﻭﺳﺘﺎﺗﻴﻜﻲ‬ ‫•‬

‫ﻣﻌﺎﻳﺐ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬

‫ﭘﺮ ﻫﺰﻳﻨﻪ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﻧﺼﺐ ﻭ ﺭﺍﻩ ﺍﻧﺪﺍﺯﻱ ﺁﻥ ﻧﺴﺒﺖ ﺑﻪ ﺍﻟﻜﺘﺮﻳﻜﻲ ﭘﻴﭽﻴﺪﻩ ﺗﺮ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﺍﺯ ﻧﻈﺮ ﻓﻴﺰﻳﻜﻲ ﺁﺳﻴﺐ ﭘﺬﻳﺮ ﺍﺳﺖ ﻭ ﻧﻴﺎﺯ ﺑﻪ ﻣﺤﺎﻓﻈﺖ ﺩﺍﺭﺩ‪.‬‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬ ‫‪٢٠٢‬‬

‫ﺩﻭ ‪category‬ﺍﺻﻠﻲ ﻓﻴﺒﺮ ﻧﻮﺭﻱ‬
‫‪Singlemode -١‬‬

‫ﺿﺨﺎﻣﺖ ﻫﺴﺘﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﻧﺎﺯﻙ ﺍﺳﺖ )‪ ١٢,٥‬ﻣﻴﻜﺮﻭﻥ(‬ ‫•‬

‫ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﺩﺭ ﻓﻴﺒﺮ ﻓﻘﻂ ﺑﺎ ﻳﻚ ﺯﺍﻭﻳﻪ ﺍﻧﻌﻜﺎﺱ ﻣﻲ ﻳﺎﺑﺪ ‪.‬‬ ‫•‬

‫ﺑﻪ ﺁﻥ ‪ monomode‬ﻧﻴﺰ ﮔﻔﺘﻪ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﺍﻳﻦ ﺭﻭﺵ ﺳﻴﮕﻨﺎﻝ ﺑﺮﺍﻱ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻃﻮﻻﻧﻲ ﺑﻬﺘﺮ ﻣﻨﺘﻘﻞ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﺍﺯ ‪ LED‬ﺑﻌﻨﻮﺍﻥ ﻣﻨﺒﻊ ﻧﻮﺭ ﺩﺭ ﺁﻥ ﻧﻤﻴﺘﻮﺍﻥ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻭ ﻧﻴﺎﺯ ﺑﻪ ‪ Laser‬ﺩﺍﺭﺩ‪.‬‬ ‫•‬

‫ﻛﻮﭘﻞ ﻛﺮﺩﻥ ﻓﻴﺒﺮ ﺑﺎ ﭼﺸﻤﻪ ﻧﻮﺭ ﻣﺸﻜﻞ ﺗﺮ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﻫﺰﻳﻨﻪ ﺍﺵ ﺑﻴﺸﺘﺮ ﺍﺳﺖ‪.‬‬ ‫•‬

‫‪Multimode -٢‬‬

‫ﺿﺨﺎﻣﺖ ﻫﺴﺘﻪ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺩﺭ ﺁﻥ ﺿﺨﻴﻢ ﺗﺮ ﺍﺳﺖ )‪ ٦٢,٥‬ﻣﻴﻜﺮﻭﻥ(‬ ‫•‬

‫ﭼﻨﺪﻳﻦ ﺳﻴﮕﻨﺎﻝ ﻧﻮﺭﻱ ﻛﻪ ﻫﺮ ﻛﺪﺍﻡ ﺯﺍﻭﻳﻪ ﺑﺎﺯﺗﺎﺏ ﻣﺘﻔﺎﻭﺕ ﺩﺭ ﻫﺴﺘﻪ ﺩﺍﺭﻧﺪ ﺭﺍ ﻣﻴﺘﻮﺍﻧﺪ ﻣﻨﺘﻘﻞ ﻛﻨﺪ‪.‬‬ ‫•‬

‫ﺑﺮﺍﻱ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻧﺴﺒﺘﺎ ﻛﻮﺗﺎﻫﺘﺮ ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﺯﻳﺮﺍ ﺩﺭ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻃﻮﻻﻧﻲ ﻣﻨﺠﺮ ﺑﻪ ‪ Dispersion‬ﺳﻴﮕﻨﺎﻝ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﭼﺸﻤﻪ ﻧﻮﺭ ﺩﺭ ﺁﻥ ﻣﻴﺘﻮﺍﻧﺪ ‪ LED‬ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫‪ Multimode‬ﺧﻮﺩ ﺑﻪ ﺩﻭ ﺩﺳﺘﻪ ‪ Step- index‬ﻭ ‪ Graded-index‬ﺗﻘﺴﻴﻢ ﻣﻴﮕﺮﺩﺩ‪.‬‬ ‫•‬

‫‪Cladding‬‬ ‫ﻧﻮﻉ ‪ Step-index‬ﻫﻤﺎﻥ ﻧﻮﻉ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻓﻴﺒﺮ ﻧﻮﺭﻱ ﺍﺳﺖ ﻭ ﻗﺴﻤﺖ ﺍﻧﺘﻘﺎﻝ ﺁﻥ ﺷﺎﻣﻞ ﺩﻭ ﻻﻳﻪ ‪ Core‬ﻭ‬ ‫•‬

‫ﺍﺳﺖ‪.‬‬
‫ﺩﺭ ﻧﻮﻉ ‪ Graded-index‬ﻓﻴﺒﺮ ﭼﻨﺪ ﻻﻳﻪ ﺩﺍﺭﺩ ﻛﻪ ﺿﺮﻳﺐ ﺍﻧﻌﻜﺎﺱ ﺁﻧﻬﺎ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ‪ .‬ﺍﻳﻦ ﺍﻣﺮ ﻣﻮﺟﺐ ﻣﻴﺸﻮﺩ ﻛﻪ‬ ‫•‬

‫ﻧﻮﺭﺑﺘﻮﺍﻧﺪ ﺑﺎ ﺳﺮﻋﺘﻬﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺍﺯ ﻫﺴﺘﻪ ﺑﮕﺬﺭﺩ‪.‬‬

‫‪Techno-Electro.com‬‬

‫‪٢٠٣‬‬ ‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬

‫‪ -٣‬ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ ﺑﺼﻮﺭﺕ ﺑﻲ ﺳﻴﻢ‬
‫ﺍﻧﺘﻘﺎﻝ ﺑﺪﻭﻥ ﺳﻴﻢ ﺑﻪ ﺩﻭ ﺭﻭﺵ ﺍﻣﻜﺎﻥ ﭘﺬﻳﺮ ﺍﺳﺖ ﻳﻜﻲ ﻣﺎﺩﻭﻥ ﻗﺮﻣﺰ ﻭ ﺩﻳﮕﺮﻱ ﺭﺍﺩﻳﻮﻳﻲ‪.‬‬
‫ﺗﻮﺳﻂ ﻧﻮﺭ ﻣﺎﺩﻭﻥ ﻗﺮﻣﺰ ) ‪( Infrared‬‬ ‫‪.I‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻧﻴﺎﺯ ﺑﻪ ﻣﺤﻴﻂ ﻓﻴﺰﻳﻜﻲ ﺧﺎﺻﻲ ﻧﻴﺴﺖ‪.‬‬ ‫•‬

‫ﻧﻴﺎﺯ ﺑﻪ ﺩﻳﺪ ﻣﺴﺘﻘﻴﻢ ﺑﻴﻦ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﮔﻴﺮﻧﺪﻩ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﺍﺯ ﻣﻮﺍﻧﻊ ﻭ ﺩﻳﻮﺍﺭﻫﺎ ﻧﻤﻴﮕﺬﺭﺩ‪.‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﻣﻤﻜﻦ ﺍﺳﺖ ﺩﺭ ﺑﺮﺧﻲ ﺣﺎﻻﺕ ﺑﻌﻨﻮﺍﻥ ﺣﺴﻦ ﻭ ﻧﻪ ﻋﻴﺐ ﺗﻠﻘﻲ ﺷﻮﺩ ﺯﻳﺮﺍ‬ ‫•‬

‫ﺩﺭ ﻳﻚ ﻣﺠﻤﻮﻋﻪ ﺑﺴﺘﻪ ﺍﺯ ﺗﺪﺍﺧﻞ ﺳﻴﮕﻨﺎﻝ ﺑﺎ ﺳﻴﮕﻨﺎﻟﻬﺎﻱ ﺑﻴﺮﻭﻧﻲ ﺟﻠﻮﮔﻴﺮﻱ ﻣﻴﻜﻨﺪ‪.‬‬

‫ﭘﻬﻨﺎﻱ ﺑﺎﻧﺪ ﺁﻥ ﻭﺳﻴﻊ ﻧﻴﺴﺖ ) ‪ 100 Kbps‬ﺗﺎ ‪( 16 Mbps‬‬ ‫•‬

‫ﻣﺰﻳﺖ ﺁﻥ ﻋﺪﻡ ﻧﻴﺎﺯ ﺑﻪ ﺳﻴﻢ ﻛﺸﻲ ﺍﺳﺖ ﻭﻟﻲ ﺧﻮﺩ ﺳﻴﺴﺘﻢ ﻫﺰﻳﻨﻪ ﺯﻳﺎﺩ ﺩﺍﺭﺩ‪.‬‬ ‫•‬

‫ﻣﻴﺮﺍﻳﻲ ﺳﻴﮕﻨﺎﻝ ﺑﺴﺘﮕﻲ ﺑﻪ ﻛﻴﻔﻴﺖ ﻧﻮﺭ ﻭ ﺷﺮﺍﻳﻂ ﺍﺗﻤﺴﻔﺮﻱ ﻣﺤﻴﻂ ﺩﺍﺭﺩ‪.‬‬ ‫•‬

‫ﺗﺪﺍﺧﻞ ﻧﻮﻳﺰ ﺁﻥ ﻛﻢ ﺍﺳﺖ ﺑﺎ ﺍﻳﻦ ﻭﺟﻮﺩ ﻧﻮﺭﻫﺎﻳﻲ ﻧﺰﺩﻳﻚ ﺑﻪ ﺁﻥ ﺍﺯ ﻧﻈﺮ ﻃﻮﻝ ﻣﻮﺝ ﻣﻴﺘﻮﺍﻧﻨﺪ ﺗﺪﺍﺧﻞ ﺍﻳﺠﺎﺩ ﻛﻨﻨﺪ‪.‬‬ ‫•‬

‫ﺍﺭﺗﺒﺎﻁ ﻣﻴﺘﻮﺍﻧﺪ ﻧﻘﻄﻪ ﺑﻪ ﻧﻘﻄﻪ ) ‪ ( Point to Point‬ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﻳﻚ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﻳﻚ ﮔﻴﺮﻧﺪﻩ‪.‬‬ ‫•‬

‫ﺍﺭﺗﺒﺎﻁ ﻣﻴﺘﻮﺍﻧﺪ ﻧﻘﻄﻪ ﺑﻪ ﭼﻨﺪ ﻧﻘﻄﻪ ) ‪ ( Point to multiPoint‬ﺑﺎﺷﺪ ﻳﻌﻨﻲ ﻳﻚ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﭼﻨﺪ ﮔﻴﺮﻧﺪﻩ‪.‬‬ ‫•‬

‫ﻳﻜﻲ ﺍﺯ ﻛﺎﺭﺑﺮﺩﻫﺎﻱ ﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﻣﺘﺤﺮﻙ )‪(Mobile Equipment‬ﺍﺳﺖ ﻛﻪ ﻓﺎﺻﻠﻪ ﺁﻧﻬﺎ ﺗﺎ‬ ‫•‬

‫ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﺩﻳﮕﺮ ﺯﻳﺎﺩ ﻧﻴﺴﺖ‪.‬‬

‫‪Techno-Electro.com‬‬

‫ﻭﺍﺳﻂ ﻫﺎﻱ ﺍﻧﺘﻘﺎﻝ ﺩﺭ ﺷﺒﻜﻪ‬ ‫‪٢٠٤‬‬

‫ﺗﻮﺳﻂ ﺍﻣﻮﺍﺝ ﺭﺍﺩﻳﻮﻳﻲ‬ ‫‪.II‬‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺍﺯ ﺍﻣﻮﺍﺝ ﺭﺍﺩﻳﻮﻳﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﺸﻮﺩ ﻛﻪ ﺍﺯ ﻣﻮﺍﻧﻊ ﻭ ﺩﻳﻮﺍﺭﻫﺎ ﻧﻴﺰ ﻣﻴﮕﺬﺭﻧﺪ‪.‬‬ ‫•‬

‫ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﮔﻴﺮﻧﺪﻩ ﺭﻭﻱ ﻓﺮﻛﺎﻧﺲ ﺧﺎﺻﻲ ﺗﻨﻈﻴﻢ ﻣﻴﺸﻮﻧﺪ‪.‬‬ ‫•‬

‫ﺑﺮﺩ ﺳﻴﮕﻨﺎﻝ ﺑﺴﺘﮕﻲ ﺑﻪ ﻗﺪﺭﺕ ﺁﻥ ﺩﺍﺭﺩ‪ .‬ﺍﮔﺮ ﺑﺎ ﺗﻮﺍﻥ ﺑﺎﻻ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﺑﺮﺍﻱ ﻣﺴﺎﻓﺘﻬﺎﻱ ﻃﻮﻻﻧﻲ ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﻣﻘﺎﻳﺴﻪ ﻭﺳﺎﻳﻞ ﺍﻧﺘﻘﺎﻝ ﺳﻴﮕﻨﺎﻝ‬

‫ﻛﺎﺑﻞ ‪TP‬‬ ‫ﻛﺎﺑﻞ ﻛﻮﺁﻛﺴﻴﺎﻝ‬ ‫ﻛﺎﺑﻞ ﻧﻮﺭﻱ‬ ‫ﺑﻴﺴﻴﻢ ‪ -‬ﻣﺎﺩﻭﻥ ﻗﺮﻣﺰ‬

‫ﺧﻴﻠﻲ ﺳﺎﺩﻩ‬ ‫ﺳﺎﺩﻩ‬ ‫ﭘﻴﭽﻴﺪﻩ‬ ‫ﺳﺎﺩﻩ‬ ‫ﺁﻣﺎﺩﻩ ﺳﺎﺯﻱ ﻭ ﻧﺼﺐ‬
‫ﺯﻳﺎﺩ ﺑﺮﺍﻱ‬ ‫ﻛﻢ‬ ‫ﻧﺪﺍﺭﺩ‬ ‫ﻛﻢ‬ ‫ﻧﻮﻳﺰ ﭘﺬﻳﺮﻱ‬
‫‪UTP‬‬
‫ﺧﻮﺏ‬ ‫ﺧﻮﺏ‬ ‫ﻋﺎﻟﻲ‬ ‫ﻣﺘﻮﺳﻂ‬ ‫ﺳﺮﻋﺖ ﺍﻧﺘﻘﺎﻝ‬
‫ﻛﻢ‬ ‫ﻣﺘﻮﺳﻂ‬ ‫ﺯﻳﺎﺩ‬ ‫ﻣﺘﻮﺳﻂ‬ ‫ﻫﺰﻳﻨﻪ‬
‫‪Techno-Electro.com‬‬

‫‪٢٠٥‬‬ ‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬

‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬

‫ﺗﻜﻨﻴﻚ ﺩﺳﺘﺮﺳﻲ )‪ (Access Technique‬ﻳﻌﻨﻲ ﺭﻭﺷﻲ ﻛﻪ ﺗﻮﺳﻂ ﺁﻥ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻴﺘﻮﺍﻧﺪ ﺑﺎﺱ ﺷﺒﻜﻪ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﺩ ﻭ‬
‫ﺩﻳﺘﺎ ﺑﮕﻴﺮﺩ ﻳﺎ ﺑﻔﺮﺳﺘﺪ ﻭ ﺑﻪ ﺳﻪ ﻧﻮﻉ ﺯﻳﺮ ﺗﻘﺴﻴﻢ ﻣﻴﺸﻮﺩ‪:‬‬
‫‪Mastrer / Slave‬‬ ‫‪.١‬‬
‫‪Token Pass‬‬ ‫‪.٢‬‬
‫‪CSMA‬‬ ‫‪.٣‬‬
‫ﺗﻜﻨﻴﻚ ﺩﺳﺘﺮﺳﻲ ﻳﻚ ﭘﻴﻜﺮ ﺑﻨﺪﻱ ﻣﻨﻄﻘﻲ )‪ (Logic‬ﺍﺳﺖ ﻭ ﻧﺒﺎﻳﺪ ﺁﻥ ﺭﺍ ﺑﺎ ﺗﻮﭘﻮﻟﻮﮊﻱ ﻓﻴﺰﻳﻜﻲ ﺍﺷﺘﺒﺎﻩ ﻛﺮﺩ ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﻣﻤﻜﻦ‬
‫ﺍﺳﺖ ﻳﻚ ﺷﺒﻜﻪ ﺑﺎ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﺍﺯ ﺗﻜﻨﻴﻚ ‪ Master / Slave‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﺪ ﻭ ﺷﺒﻜﻪ ﺩﻳﮕﺮﻱ ﺑﺎ ﻫﻤﺎﻥ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ‬
‫ﺗﻜﻨﻴﻚ ‪ Token‬ﺭﺍ ﺑﻜﺎﺭ ﺑﺒﺮﺩ‪.‬‬
‫‪ -١‬ﺗﻜﻨﻴﻚ ‪ Master / Slave‬ﻳﺎ ﺭﺋﻴﺲ ﻣﺮﺋﻮﺱ‬
‫ﻓﻘﻂ ﺩﺍﺭﺍﻱ ﻳﻚ ‪) Master‬ﻭﺍﺣﺪ ﻓﻌﺎﻝ( ﺍﺳﺖ‪.‬‬ ‫•‬

‫ﺳﺎﻳﺮ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺑﺼﻮﺭﺕ ‪ ) Slave‬ﻭﺍﺣﺪ ﻏﻴﺮ ﻓﻌﺎﻝ( ﻫﺴﺘﻨﺪ‪.‬‬ ‫•‬

‫ﺑﺎﺱ ﻫﻤﻮﺍﺭﻩ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ‪Master‬ﺍﺳﺖ ﻭ ‪ Slave‬ﻫﺎ ﺍﺟﺎﺯﻩ ﻧﺪﺍﺭﻧﺪ ﺁﻧﺮﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﻧﺪ‪.‬‬ ‫•‬

‫‪ Master‬ﺍﺳﺖ ﻛﻪ ﺑﻪ ‪ Slave‬ﻫﺎ ﺍﺟﺎﺯﻩ ﻣﻴﺪﻫﺪ ﺩﻳﺘﺎ ﺑﮕﻴﺮﻧﺪ ﻳﺎ ﺩﻳﺘﺎ ﺑﻔﺮﺳﺘﻨﺪ‪.‬‬ ‫•‬

‫‪ Master‬ﺑﺼﻮﺭﺕ ﺳﻴﻜﻠﻲ ﺑﺎ ‪ Slave‬ﻫﺎ ﻳﻜﻲ ﭘﺲ ﺍﺯ ﺩﻳﮕﺮﻱ ﺍﺭﺗﺒﺎﻁ ﺑﺮﻗﺮﺍﺭ ﻣﻴﻜﻨﺪ‪.‬‬ ‫•‬

‫ﺍﺭﺗﺒﺎﻁ ﻣﺴﺘﻘﻴﻢ ﺑﻴﻦ ‪ Slave‬ﻫﺎ ﻭﺟﻮﺩ ﻧﺪﺍﺭﺩ‪.‬‬ ‫•‬

‫ﻫﺮ ‪ Slave‬ﺁﺩﺭﺱ ﺧﻮﺩ ﺭﺍ ﻣﻴﺸﻨﺎﺳﺪ ﻭ ﺍﮔﺮ ﭼﻪ ﺗﻤﺎﻡ ﭘﻴﺎﻡ ﻫﺎﻱ ‪ Master‬ﺭﺍ ﺩﺭﻳﺎﻓﺖ ﻣﻴﻜﻨﺪ ﻭﻟﻲ ﺗﻨﻬﺎ ﺑﻪ ﭘﻴﺎﻡ ﻫﺎﻱ‬ ‫•‬
‫ﻣﺨﺼﻮﺹ ﺑﻪ ﺧﻮﺩ ﭘﺎﺳﺦ ﻣﻴﺪﻫﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬ ‫‪٢٠٦‬‬

‫‪ -٢‬ﺗﻜﻨﻴﻚ ‪ Token‬ﻳﺎ ﺍﻧﺘﻘﺎﻝ ﻋﻼﻣﺖ‬

‫ﺑﺮ ﺧﻼﻑ ﺭﻭﺵ ‪ Master / Slave‬ﻣﻴﺘﻮﺍﻧﺪ ﭼﻨﺪﻳﻦ ‪ ) Master‬ﻳﺎ ﻋﻨﺼﺮ ‪ (Active‬ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬ ‫•‬

‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻳﻚ ﻧﺸﺎﻧﻪ )‪ (Token‬ﺑﻴﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺩﺍﺧﻞ ﻳﻚ ﺣﻠﻘﻪ ﻣﻴﭽﺮﺧﺪ‪.‬‬ ‫•‬

‫ﺑﻪ ﺣﻠﻘﻪ ﻓﻮﻕ ‪ Token Ring‬ﻣﻴﮕﻮﻳﻨﺪ ﻭ ﻳﻚ ﺣﻠﻘﻪ ﻣﻨﻄﻘﻲ ﺍﺳﺖ ﻧﻪ ﻳﻚ ﺣﻠﻘﻪ ﻓﻴﺰﻳﻜﻲ‪.‬‬ ‫•‬

‫ﻧﺸﺎﻧﻪ ﻣﺎﻧﻨﺪ ﻳﻚ ﭘﺎﻛﺖ ﺧﺎﻟﻲ ﺑﻴﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﻣﻴﭽﺮﺧﺪ‪.‬‬ ‫•‬

‫ﺍﻳﻦ ﭘﺎﻛﺖ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻫﻲ ﺑﺎﺷﺪ ﻗﺎﺩﺭ ﺍﺳﺖ ﺍﻃﻼﻋﺎﺕ ﺧﻮﺩ ﺭﺍ ﺍﺭﺳﺎﻝ ﻛﻨﺪ‪.‬‬ ‫•‬

‫ﻭﻗﺘﻲ ﭘﺎﻛﺖ ﻳﻌﻨﻲ ﻧﺸﺎﻧﻪ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﻗﺮﺍﺭ ﮔﺮﻓﺖ ﺳﺎﻳﺮﻳﻦ ﻧﻤﻴﺘﻮﺍﻧﻨﺪ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﻧﺪ‪.‬‬ ‫•‬

‫ﺑﺪﻟﻴﻞ ﻭﻳﮋﮔﻲ ﻓﻮﻕ ﻋﻤﻼ ﻫﻴﭻ ﺗﺪﺍﺧﻠﻲ ﺑﻴﻦ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺭﺥ ﻧﻤﻲ ﺩﻫﺪ‪.‬‬ ‫•‬

‫ﺍﻳﺴﺘﮕﺎﻩ ﭘﺲ ﺍﺯ ﻗﺮﺍﺭ ﺩﺍﺩﻥ ﺍﻃﻼﻋﺎﺕ ﺩﺭ ﭘﺎﻛﺖ ﻭ ﻣﺸﺨﺺ ﻛﺮﺩﻥ ﮔﻴﺮﻧﺪﻩ ﺁﻧﺮﺍ ﺩﺭ ﺣﻠﻘﻪ ﺭﻫﺎ ﻣﻲ ﻛﻨﺪ‪.‬‬ ‫•‬

‫ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻭﻗﺘﻲ ﭘﺎﻛﺖ ﺑﻪ ﺍﻭ ﺭﺳﻴﺪ ﺁﺩﺭﺱ ﺁﻧﺮﺍ ﭼﻚ ﻣﻲ ﻛﻨﺪ ﺍﮔﺮ ﺑﻪ ﺍﻭ ﻣﺮﺑﻮﻁ ﺑﻮﺩ ﺁﻥ ﺭﺍ ﺑﺮ ﻣﻴﺪﺍﺭﺩ ﻭ ﭘﺎﻛﺖ‬ ‫•‬

‫ﺧﺎﻟﻲ ﺭﺍ ﺩﺭ ﺣﻠﻘﻪ ﺭﻫﺎ ﻣﻴﻜﻨﺪ ﻭ ﺍﮔﺮ ﺑﻪ ﺍﻭ ﻣﺮﺑﻮﻁ ﻧﺒﻮﺩ ﭘﺎﻛﺖ ﺭﺍ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻌﺪﻱ ﻣﻴﻔﺮﺳﺘﺪ ﻭﺳﻴﻜﻞ ﺑﻪ ﻫﻤﻴﻦ ﺷﻜﻞ‬
‫ﺗﻜﺮﺍﺭ ﻣﻴﺸﻮﺩ‪.‬‬
‫ﺟﻬﺖ ﭼﺮﺧﺶ ﻣﻌﻤﻮﻻ ﻳﻚ ﻃﺮﻓﻪ ﺍﺳﺖ ﻣﻌﻤﻮﻻ ﻧﺸﺎﻧﻪ ﺍﺯ ﺁﺩﺭﺱ ﺑﺎ ﺷﻤﺎﺭﻩ ﻛﻤﺘﺮ ﺷﺮﻭﻉ ﻭ ﺑﻪ ﺁﺩﺭﺱ ﻫﺎﻳﻲ ﻛﻪ‬ ‫•‬

‫ﺩﺍﺭﺍﻱ ﺷﻤﺎﺭﻩ ﺑﺰﺭﮔﺘﺮ ﻫﺴﺘﻨﺪ ﺗﺤﻮﻳﻞ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ‪ .‬ﻭﻗﺘﻲ ﺑﻪ ﺑﺰﺭﮔﺘﺮﻳﻦ ﺁﺩﺭﺱ ﺭﺳﻴﺪ ﻣﺠﺪﺩﺍ ﺗﺤﻮﻳﻞ ﻛﻮﭼﻜﺘﺮﻳﻦ‬
‫ﺁﺩﺭﺱ ﻣﻴﺸﻮﺩ‪.‬‬
‫ﺍﮔﺮ ﻋﻀﻮﻱ ﺍﺯ ﺣﻠﻘﻪ ﺧﺎﺭﺝ ﺷﺪ ﻳﺎ ﻋﻀﻮ ﺟﺪﻳﺪﻱ ﻭﺍﺭﺩ ﺣﻠﻘﻪ ﺷﺪ ﺳﻴﺴﺘﻢ ﻧﻮﺑﺖ ﺩﻫﻲ ﺟﺪﻳﺪ ﺑﺮﻗﺮﺍﺭ ﻣﻴﺸﻮﺩ‪.‬‬ ‫•‬

‫ﺩﺭ ﺗﻮﭘﻮﻟﻮﮊﻱ ﺑﺎﺱ ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﺭﻭﺵ ‪ Token‬ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻛﻪ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ﺑﻪ ﺁﻥ ‪ Token Bus‬ﮔﻔﺘﻪ ﻣﻴﺸﻮﺩ ‪.‬‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪٢٠٧‬‬ ‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬

‫‪Hybrid‬‬ ‫ﻣﻴﺘﻮﺍﻥ ﺭﻭﺷﻬﺎﻱ ‪ Master / Slave‬ﻭ ‪ Token‬ﺭﺍ ﺑﺎ ﻫﻢ ﺗﺮﻛﻴﺐ ﻭ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻛﻪ ﺑﻪ ﺁﻥ ﺗﻜﻨﻴﻚ‬ ‫•‬
‫ﻣﻴﮕﻮﻳﻨﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻭﻗﺘﻲ ﻧﺸﺎﻧﻪ ﺑﻪ ﻳﻚ ‪ Master‬ﺭﺳﻴﺪ ﺍﺟﺎﺯﻩ ﺩﺍﺭﺩ ﺑﺎ ‪ Slave‬ﻫﺎﻳﺶ ﺻﺤﺒﺖ ﻛﻨﺪ ﻳﺎ ﺑﻪ‬
‫‪ Master‬ﻫﺎﻱ ﺩﻳﮕﺮ ﺩﻳﺘﺎ ﺑﻔﺮﺳﺘﺪ‪.‬‬
‫‪Slave‬‬ ‫‪ Token‬ﻣﻴﺘﻮﺍﻧﺪ ﻫﻤﺰﻣﺎﻥ ﺑﺎ ‪ Master / Slave‬ﺑﻜﺎﺭ ﺭﻭﺩ‪ .‬ﺩﺭ ﺷﻜﻞ ﺯﻳﺮ ﻋﻼﻭﻩ ﺑﺮ ﺍﻳﻨﻜﻪ ﻫﺮ ‪ Master‬ﺑﺎ‬ ‫•‬

‫ﻫﺎﻱ ﺧﻮﺩﺵ ﺻﺤﺒﺖ ﻣﻴﻜﻨﺪ ﺑﺎ ﺳﺎﻳﺮ ‪ Master‬ﻫﺎ ﻧﻴﺰ ﺑﻪ ﺭﻭﺵ ‪ Token‬ﻣﻲ ﻧﻮﺍﻧﺪ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬‬

‫ﺩﺭ ﺻﻔﺤﻪ ﺑﻌﺪ ﻣﺜﺎﻝ ﺳﺎﺩﻩ ﺍﻱ ﺍﺯ ﭼﺮﺧﺶ ﻋﻼﻣﺖ ﺑﻴﻦ ﺩﻭ ‪ Master‬ﺩﺭ ﺭﻭﺵ ‪ Hybrid‬ﺗﺮﺳﻴﻢ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬ ‫‪٢٠٨‬‬

‫ﻭﺿﻌﻴﺖ ‪: ١‬‬
‫‪Master1‬‬ ‫ﻧﺸﺎﻧﻪ ﺩﺭ ﺍﺧﺘﻴﺎﺭ‬
‫‪Slave‬‬ ‫ﺍﺳﺖ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﺑﺎ‬
‫ﻫﺎﻳﺶ ﺻﺤﺒﺖ ﻛﻨﺪ‪ .‬ﺩﺭ ﺍﻳﻦ‬
‫‪Slave‬‬ ‫ﺣﺎﻟﺖ ‪ Master2‬ﺑﻪ‬
‫ﻫﺎﻳﺶ ﺩﺳﺘﺮﺳﻲ ﻧﺪﺍﺭﺩ‪.‬‬

‫ﻭﺿﻌﻴﺖ ‪: ٢‬‬
‫‪ Master1‬ﻧﺸﺎﻧﻪ ﺭﺍ ﺑﻪ‬
‫‪ Master2‬ﻣﻴﻔﺮﺳﺘﺪ ﺩﺭ ﺍﻳﻦ‬
‫‪Master‬‬ ‫ﻣﺮﺣﻠﻪ ﻫﻴﭽﻜﺪﺍﻡ ﺍﺯ‬
‫‪ Slave‬ﻫﺎﻳﺸﺎﻥ‬ ‫ﻫﺎ ﺑﻪ‬
‫ﺩﺳﺘﺮﺳﻲ ﻧﺪﺍﺭﻧﺪ‪.‬‬

‫ﻭﺿﻌﻴﺖ ‪: ٣‬‬
‫‪Master 2‬‬ ‫ﻧﺸﺎﻧﻪ ﺩﺭ ﺍﺧﺘﻴﺎﺭ‬
‫‪Slave‬‬ ‫ﺍﺳﺖ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﺑﺎ‬
‫ﻫﺎﻳﺶ ﺻﺤﺒﺖ ﻛﻨﺪ‪ .‬ﺩﺭ ﺍﻳﻦ‬
‫‪Slave‬‬ ‫ﺣﺎﻟﺖ ‪ Master 1‬ﺑﻪ‬
‫ﻫﺎﻳﺶ ﺩﺳﺘﺮﺳﻲ ﻧﺪﺍﺭﺩ‪.‬‬

‫ﻭﺿﻌﻴﺖ ‪: ٤‬‬
‫‪ Master2‬ﻧﺸﺎﻧﻪ ﺭﺍ ﺑﻪ‬
‫‪ Master1‬ﻣﻴﻔﺮﺳﺘﺪ ﺩﺭ ﺍﻳﻦ‬
‫‪Master‬‬ ‫ﻣﺮﺣﻠﻪ ﻫﻴﭽﻜﺪﺍﻡ ﺍﺯ‬
‫‪ Slave‬ﻫﺎﻳﺸﺎﻥ‬ ‫ﻫﺎ ﺑﻪ‬
‫ﺩﺳﺘﺮﺳﻲ ﻧﺪﺍﺭﻧﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٠٩‬‬ ‫ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ‬

‫‪ -٣‬ﺗﻜﻨﻴﻚ ‪ CSMA‬ﻳﺎ ﺭﻭﺵ ﮔﻮﺵ ﺩﺍﺩﻥ ﺑﻪ ﺧﻂ‬
‫ﺩﺭ ﺭﻭﺵ ‪ (Carrier Sense Multiple Instance) CSMA‬ﻫﺮ ﻭﻗﺖ ﺑﺎﺱ ﺧﺎﻟﻲ ﺑﺎﺷﺪ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻫﻲ ﻣﻴﺘﻮﺍﻧﺪ‬ ‫•‬

‫ﺁﻧﺮﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﺩ‪.‬‬

‫ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺮﺗﺒﺎ ﺑﻪ ﺑﺎﺱ ﮔﻮﺵ ﻣﻴﺪﻫﺪ ﺗﺎ ﺍﺯ ﺧﺎﻟﻲ ﺷﺪﻥ ﺁﻥ ﺍﻃﻼﻉ ﺣﺎﺻﻞ ﻛﻨﺪ‪.‬‬ ‫•‬

‫ﻣﻤﻜﻦ ﺍﺳﺖ ﺩﻭ ﺍﻳﺴﺘﮕﺎﻩ ﻫﻤﺰﻣﺎﻥ ﺷﺮﻭﻉ ﺑﻪ ﺻﺤﺒﺖ ﻛﻨﻨﺪ ﻛﻪ ﻣﻨﺠﺮ ﺑﻪ ﺗﺼﺎﺩﻡ ﻣﻴﺸﻮﺩﻭ ﺍﻳﻦ ﻋﻴﺐ ﺭﻭﺵ ﻓﻮﻕ‬ ‫•‬

‫ﺍﺳﺖ‪.‬‬
‫‪Collision Detection‬‬ ‫ﺑﺮﺍﻱ ﺭﻓﻊ ﻣﺸﻜﻞ ﻓﻮﻕ ﺭﻭﺵ ‪ CSMA/CD‬ﺑﻜﺎﺭ ﻣﻴﺮﻭﺩ ﻛﻪ ﺩﺭ ﺁﻥ ‪ CD‬ﻣﺨﻔﻒ‬ ‫•‬

‫ﻳﻌﻨﻲ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺗﺼﺎﺩﻡ ﺍﺳﺖ‪.‬‬

‫ﺩﺭ ﺭﻭﺵ ‪ CSMA/CD‬ﺗﺼﺎﺩﻡ ﺑﺎ ﺗﻐﻴﻴﺮ ﺳﻄﺢ ﻭﻟﺘﺎﮊ ﻣﺴﺘﻘﻴﻢ ﺁﺷﻜﺎﺭ ﻣﻴﺸﻮﺩ ﻭ ﺗﻤﺎﻡ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﺷﺒﻜﻪ ﺍﺯ‬ ‫•‬

‫ﺟﻤﻠﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﻛﻪ ﺩﻳﺘﺎﻱ ﺁﻧﻬﺎ ﺑﺎ ﻫﻢ ﺑﺮﺧﻮﺭﺩ ﻛﺮﺩﻩ ﻣﺘﻮﺟﻪ ﻣﻮﺿﻮﻉ ﻣﻴﺸﻮﻧﺪ‪.‬‬

‫ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﻓﺮﺳﺘﻨﺪﻩ ﭘﺲ ﺍﺯ ﻭﻗﻮﻉ ﺗﺼﺎﺩﻡ ﻫﺮﺩﻭ ﺳﺎﻛﺖ ﺷﺪﻩ ﻭ ﺑﺎﺯ ﻃﻲ ﺯﻣﺎﻥ ﻧﺎﻣﺸﺨﺼﻲ ﻛﻪ ﺑﻄﻮﺭ ﺭﻧﺪﻭﻡ‬ ‫•‬

‫ﺑﺮﺍﻱ ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻣﺤﺎﺳﺒﻪ ﻣﻴﺸﻮﺩ ﺍﻗﺪﺍﻡ ﺑﻪ ﺍﺭﺳﺎﻝ ﭘﻴﺎﻡ ﻣﻴﻜﻨﻨﺪ‪.‬‬

‫ﺩﺭ ﻃﻮﻝ ﻣﺪﺕ ﺍﻧﺘﻈﺎﺭ )ﺑﻌﺪ ﺍﺯ ﻭﻗﻮﻉ ﺗﺼﺎﺩﻡ( ﻫﻴﭻ ﺍﻳﺴﺘﮕﺎﻩ ﺩﻳﮕﺮﻱ ﻧﻤﻴﺘﻮﺍﻧﺪ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﺩ ‪.‬‬ ‫•‬

‫ﺍﮔﺮ ﺑﺮﺧﻮﺭﺩﻫﺎﻱ ﻣﺘﻌﺪﺩ ﺩﺭ ﻳﻚ ﺷﺒﻜﻪ ﺻﻮﺭﺕ ﮔﻴﺮﺩ ﺍﻳﺴﺘﮕﺎﻫﻬﺎ ﺯﻣﺎﻥ ﺍﻧﺘﻈﺎﺭ ﺑﻌﺪ ﺍﺯ ﺑﺮﺧﻮﺭﺩ ﺭﺍ ﺩﻭ ﺑﺮﺍﺑﺮ‬ ‫•‬

‫ﻣﻴﻜﻨﻨﺪ‪.‬‬
‫ﺯﻣﺎﻥ ﻫﺎﻱ ﺍﻧﺘﻈﺎﺭ ﺑﻌﺪ ﺍﺯ ﺑﺮﺧﻮﺭﺩ ﺳﺮﻋﺖ ﻣﻮﺛﺮ ﺷﺒﻜﻪ ﺭﺍ ﺷﺪﻳﺪﹲﺍ ﻛﺎﻫﺶ ﻣﻴﺪﻫﺪ‪.‬‬ ‫•‬

‫ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﺑﺎﻳﺪ ﮔﻔﺖ ﺭﻭﺵ ‪ CSMA/CD‬ﺩﺭ ﺷﺮﺍﻳﻂ ﻋﺎﺩﻱ ﻛﺎﺭﺍﻳﻲ ﺑﺴﻴﺎﺭ ﺧﻮﺑﻲ ﺩﺍﺭﺩ ﻭﻟﻲ ﺩﺭ ﺗﺮﺍﻓﻴﻚ‬ ‫•‬

‫ﺑﺎﻻ ﻛﺎﺭﺍﻳﻲ ﺳﻴﺴﺘﻢ ﺑﺪﻟﻴﻞ ﻭﺟﻮﺩ ﺗﺼﺎﺩﻡ ﻛﻢ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﺍﺷﻜﺎﻝ ﻣﺰﺑﻮﺭ ﺩﺭ ﺭﻭﺵ ‪ CSMA/CD‬ﻣﻨﺠﺮ ﺑﻪ ﺍﺑﺪﺍﻉ ﺭﻭﺵ ﺩﻳﮕﺮﻱ ﺑﻪ ﻧﺎﻡ ‪ CSMA/CA‬ﺷﺪﻩ ﻛﻪ ﺩﺭﺁﻥ‬ ‫•‬

‫‪ CA‬ﻣﺨﻔﻒ ‪ Collision Avoided‬ﻳﺎ ﺍﺟﺘﻨﺎﺏ ﺍﺯ ﺗﺼﺎﺩﻡ ﺍﺳﺖ‪.‬‬

‫ﺩﺭ ﺭﻭﺵ ‪ CSMA/CD‬ﻫﺮ ﺍﻳﺴﺘﮕﺎﻩ ﻳﻚ ﺩﺭﺟﻪ ﺍﻭﻟﻮﻳﺖ ﺩﺍﺭﺩ‪ .‬ﺍﮔﺮ ﺗﺼﺎﺩﻡ ﺍﺗﻔﺎﻕ ﺍﻓﺘﺎﺩ ﺁﻧﻜﻪ ﺩﺭﺟﻪ ﺍﺵ ﺑﺎﻻﺗﺮ‬ ‫•‬

‫ﺍﺳﺖ ﺍﺟﺎﺯﻩ ﺩﺍﺭﺩ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﺑﮕﻴﺮﺩ‪.‬‬

‫‪Techno-Electro.com‬‬

‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬ ‫‪٢١٠‬‬

‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ ‪OSI‬‬

‫ﺗﺎ ﺍﻳﻨﺠﺎ ﺑﺎ ﺳﺎﺧﺘﺎﺭ ﻓﻴﺰﻳﻜﻲ ﺷﺒﻜﻪ ﻭ ﻭﺳﺎﻳﻞ ﺍﻧﺘﻘﺎﻝ ﻭ ﺗﻜﻨﻴﻚ ﻫﺎﻱ ﺩﺳﺘﺮﺳﻲ ﺑﻪ ﺷﺒﻜﻪ ﺁﺷﻨﺎ ﺷﺪﻳﻢ ﺍﻣﺎ ﺑﺤﺚ ﺍﺻﻠﻲ ﻧﺤﻮﻩ ﺍﻧﺘﻘﺎﻝ‬
‫ﺍﻃﻼﻋﺎﺕ ﺍﺳﺖ‪ .‬ﻣﻴﺪﺍﻧﻴﻢ ﺍﻃﻼﻋﺎﺕ ﺑﺼﻮﺭﺕ ﺩﻳﺠﻴﺘﺎﻝ ﻳﻌﻨﻲ ﺻﻔﺮ ﻭ ﻳﻚ ﻣﻨﺘﻘﻞ ﻣﻴﺸﻮﻧﺪ ﻳﻌﻨﻲ ﻳﻚ ﺑﺴﺘﻪ ﺍﻃﻼﻋﺎﺗﻲ ﺷﺎﻣﻞ ﺗﻌﺪﺍﺩ‬
‫ﺯﻳﺎﺩﻱ ﺻﻔﺮ ﻭ ﻳﻚ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﺩﺭ ﺍﻳﻨﺠﺎ ﺳﻮﺍﻻﺗﻲ ﻣﻄﺮﺡ ﻣﻴﺸﻮﺩ ﻣﺎﻧﻨﺪ ‪:‬‬
‫ﺍﮔﺮ ﺣﺠﻢ ﺍﻃﻼﻋﺎﺕ ﺯﻳﺎﺩ ﺑﺎﺷﺪ ﭼﮕﻮﻧﻪ ﻣﻴﺘﻮﺍﻥ ﺁﻥ ﺭﺍ ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺑﻪ ﺑﺴﺘﻪ ﻫﺎﻱ ﻛﻮﭼﻜﺘﺮ ﺷﻜﺴﺖ ﻭ ﭼﮕﻮﻧﻪ‬ ‫‪.١‬‬
‫ﻣﻴﺘﻮﺍﻥ ﺍﻳﻦ ﺑﺴﺘﻪ ﻫﺎ ﺭﺍ ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﺑﻬﻢ ﭘﻴﻮﻧﺪ ﺯﺩ ﺗﺎ ﻛﻞ ﺍﻃﻼﻋﺎﺕ ﻗﺎﺑﻞ ﺷﻨﺎﺳﺎﻳﻲ ﺑﺎﺷﺪ؟‬
‫ﺍﮔﺮ ﺍﻃﻼﻋﺎﺕ ﺭﻭﻱ ﺷﺒﻜﻪ ﺍﻱ ﻛﻪ ﺗﻌﺪﺍﺩ ﺯﻳﺎﺩﻱ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻪ ﺁﻥ ﻣﺘﺼﻞ ﻫﺴﺘﻨﺪ ﺍﺭﺳﺎﻝ ﺷﻮﺩ ﭼﮕﻮﻧﻪ ﻣﻴﺘﻮﺍﻥ ﺁﺩﺭﺱ‬ ‫‪.٢‬‬
‫ﮔﻴﺮﻧﺪﻩ ﺭﺍ ﻫﻤﺮﺍﻩ ﺑﺎ ﺍﻃﻼﻋﺎﺕ ﺍﺭﺳﺎﻝ ﻧﻤﻮﺩ ﺗﺎ ﺑﻪ ﻣﻘﺼﺪ ﻣﻮﺭﺩ ﻧﻈﺮ ﺑﺮﺳﺪ؟‬
‫ﭼﮕﻮﻧﻪ ﻣﻴﺘﻮﺍﻥ ﺁﺩﺭﺱ ﻓﺮﺳﺘﻨﺪﻩ ﺭﺍ ﻫﻤﺮﺍﻩ ﺑﺎ ﺁﻥ ﺍﺭﺳﺎﻝ ﻧﻤﻮﺩ ﺗﺎ ﮔﻴﺮﻧﺪﻩ ﭘﺎﺳﺦ ﺧﻮﺩ ﺭﺍ ﺑﻪ ﺁﻥ ﺁﺩﺭﺱ ﺑﻔﺮﺳﺘﺪ؟‬ ‫‪.٣‬‬
‫ﺍﮔﺮ ﺑﻪ ﺩﻟﻴﻠﻲ ﻣﺎﻧﻨﺪ ﻧﻮﻳﺰ ﻳﺎ ﺍﺷﻜﺎﻝ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﺻﻔﺮ ﻭ ﻳﻚ ﺩﺍﺧﻞ ﺑﺴﺘﻪ ﺍﻃﻼﻋﺎﺕ ﺗﻐﻴﻴﺮ ﻛﺮﺩ ﭼﮕﻮﻧﻪ ﻣﻴﺘﻮﺍﻥ ﺍﺯ‬ ‫‪.٤‬‬
‫ﻭﻗﻮﻉ ﺍﻳﻦ ﺧﻄﺎ ﻣﻄﻠﻊ ﺷﺪ ﻭ ﭼﮕﻮﻧﻪ ﻣﻴﺘﻮﺍﻥ ﺁﻥ ﺭﺍ ﺗﺼﺤﻴﺢ ﻛﺮﺩ؟‬

‫ﺍﻳﻦ ﻣﻮﺍﺭﺩ ﻭ ﺳﻮﺍﻻﺕ ﺩﻳﮕﺮﻱ ﺍﺯ ﺍﻳﻦ ﺩﺳﺖ ﭘﺎﺳﺨﻲ ﺟﺰ ﺍﻳﻦ ﻧﺪﺍﺭﺩ ﻛﻪ ﺍﺭﺳﺎﻝ ﺑﺴﺘﻪ ﺍﻃﻼﻋﺎﺗﻲ ﺑﻪ ﺗﻨﻬﺎﻳﻲ ﻛﺎﻓﻲ ﻧﻴﺴﺖ ﻭ ﻫﻤﺮﺍﻩ ﺑﺎ‬
‫ﺁﻥ ﻛﺪﻫـﺎﻱ ﺩﻳﮕـﺮﻱ ﻧﻴﺰ ﺑﺎﻳﺪ ﺍﺭﺳﺎﻝ ﮔﺮﺩﺩ‪ .‬ﺑﺮﺍﺳﺎﺱ ﺍﻳﻦ ﻧﻴﺎﺯ ﺗﻮﺳﻂ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ‪ ISO‬ﻳﻚ ﻣﺪﻝ ﻻﻳﻪ ﺍﻱ ﺑﺮﺍﻱ ﺷﺒﻜﻪ ﻃﺮﺍﺣﻲ ﻭ‬
‫ﺍﺭﺍﺋﻪ ﺷﺪ ﻛﻪ ﺑﻪ ﻣﺪﻝ )‪ OSI ( Open System Interconnection‬ﻣﻌﺮﻭﻑ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢١١‬‬ ‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬

‫ﺍﻳﻦ ﻣﺪﻝ ﺍﺯ ‪ ٧‬ﻻﻳﻪ ﺗﺸﻜﻴﻞ ﺷﺪﻩ ﺍﺳﺖ ‪ .‬ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺍﺻﻞ ﭘﻴﺎﻡ ﺑﻪ ﻻﻳﻪ ‪ ٧‬ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ ﻭ ﺍﺯ ﺍﻳﻦ ﻻﻳﻪ ﺑﺘﺪﺭﻳﺞ ﺑﻪ ﻻﻳﻪ ﻫﺎﻱ‬
‫ﭘﺎﻳﻴﻦ ﺗﺮ ﺍﻧﺘﻘﺎﻝ ﻣﻲ ﻳﺎﺑﺪ‪ .‬ﻫﺮ ﻻﻳﻪ ﻛﺪﻫﺎﻳﻲ ﺭﺍ ﺑﻪ ﺑﺴﺘﻪ ﺍﺿﺎﻓﻪ ﻣﻴﻜﻨﺪ ﺗﺎ ﺟﻮﺍﺑﮕﻮﻱ ﻧﻴﺎﺯﻫﺎﻳﻲ ﻣﺎﻧﻨﺪ ﺁﻧﭽﻪ ﺩﺭ ﭘﺮﺳﺶ ﻫﺎﻱ ﺻﻔﺤﻪ‬
‫ﻗﺒﻞ ﻣﻄﺮﺡ ﺷﺪ ﺑﺎﺷﺪ ﺗﺎ ﻧﻬﺎﻳﺘﹰﺎ ﺑﻪ ﻻﻳﻪ ‪ ١‬ﻛﻪ ﻣﺤﻴﻂ ﺍﻧﺘﻘﺎﻝ ﺍﺳﺖ ﻣﻴﺮﺳﺪ ﻭ ﺍﻳﻦ ﻻﻳﻪ ﺑﺴﺘﻪ ﻫﺎ ﺭﺍ ﺑﺼﻮﺭﺕ ﺻﻔﺮ ﻭ ﻳﻚ ﺑﻪ ﺳﻤﺖ‬
‫ﮔﻴﺮﻧﺪﻩ ﺍﺭﺳﺎﻝ ﻣﻴﻜﻨﺪ‪.‬‬

‫ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﺗﺮﺗﻴﺐ ﻋﻤﻠﻴﺎﺕ ﺑﺮﻋﻜﺲ ﺍﺳﺖ‪ .‬ﻳﻌﻨﻲ ﺑﺴﺘﻪ ﺍﺯ ﻻﻳﻪ ‪ ١‬ﺩﺭﻳﺎﻓﺖ ﻣﻴﺸﻮﺩ ﻭ ﺑﺘﺪﺭﻳﺞ ﺑﻪ ﻻﻳﻪ ﻫﺎﻱ ﺑﺎﻻﺗﺮ ﺍﻧﺘﻘﺎﻝ ﻣﻲ‬
‫ﻳﺎﺑﺪ‪ .‬ﻫﺮ ﻻﻳﻪ ﻛﺪﻫﺎﻱ ﺍﺿﺎﻓﻲ ﺭﺍ ﺷﻨﺎﺳﺎﻳﻲ ﻭ ﺍﺯ ﺑﺴﺘﻪ ﺟﺪﺍ ﻣﻴﻜﻨﺪ ﺗﺎ ﺍﻳﻨﻜﻪ ﺍﺻﻞ ﭘﻴﺎﻡ ﺩﺭ ﺑﺎﻻﺗﺮﻳﻦ ﻻﻳﻪ ﻳﻌﻨﻲ ﻻﻳﻪ ‪ ٧‬ﺷﻨﺎﺳﺎﻳﻲ‬
‫ﻣﻴﮕﺮﺩﺩ‪.‬‬

‫ﺍﺻﻮﻝ ﻛﺎﺭ ﺷﺒﻴﻪ ﺁﻧﺴﺖ ﻛﻪ ﻣﺪﻳﺮ ﺩﻭ ﺳﺎﺯﻣﺎﻥ ﻣﺨﺘﻠﻒ ﺑﺨﻮﺍﻫﻨﺪ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﻣﻜﺎﺗﺒﻪ ﻛﻨﻨﺪ ‪ .‬ﻣﺪﻳﺮ ﺳﺎﺯﻣﺎﻥ ﺍﻭﻝ ﭘﻴﺎﻡ ﺭﺍ ﻣﻴﻨﻮﻳﺴﺪ ﻭ‬
‫‪Techno-Electro.com‬‬

‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬ ‫‪٢١٢‬‬

‫ﺑﻪ ﻗﺴﻤﺖ ﺩﺑﻴﺮﺧﺎﻧﻪ ﻭ ﺍﺩﺍﺭﻱ ﺧﻮﺩ ﻣﻴﺪﻫﺪ ﺩﺭ ﺍﻳﻦ ﻗﺴﻤﺖ ﺍﻃﻼﻋﺎﺕ ﺩﻳﮕﺮ ﻣﺎﻧﻨﺪ ﺷﻤﺎﺭﻩ ﻭ ﺗﺎﺭﻳﺦ ﻭ ﺁﺩﺭﺱ ﮔﻴﺮﻧﺪﻩ ﻭ ﻓﺮﺳﺘﻨﺪﻩ ﺑﻪ‬
‫ﭘﻴﺎﻡ ﺍﺿﺎﻓﻪ ﺷﺪﻩ ﺳﭙﺲ ﻧﺎﻣﻪ ﺑﻪ ﺳﺎﺯﻣﺎﻥ ﺩﻭﻡ ﺍﺭﺳﺎﻝ ﻣﻴﮕﺮﺩﺩ‪ .‬ﺩﺭ ﺳﺎﺯﻣﺎﻥ ﺩﻭﻡ ﻋﻤﻠﻴﺎﺕ ﻋﻜﺲ ﺍﻧﺠﺎﻡ ﻣﻴﺸﻮﺩ ﻳﻌﻨﻲ ﻧﺎﻣﻪ ﺗﺤﻮﻳﻞ‬
‫ﺩﺑﻴﺮﺧﺎﻧﻪ ﻭ ﭘﺲ ﺍﺯ ﺛﺒﺖ ﻭ ﺍﻧﺠﺎﻡ ﻣﺮﺍﺣﻞ ﺍﺩﺍﺭﻱ ﺗﺤﻮﻳﻞ ﻣﺪﻳﺮﻳﺖ ﺳﺎﺯﻣﺎﻥ ﻣﻴﮕﺮﺩﺩ‪.‬‬
‫ﭘﺲ ﺑﻄﻮﺭ ﻛﻠﻲ ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺗﺮﺗﻴﺐ ﺍﺯ ﻻﻳﻪ ﺑﺎﻻﺗﺮ ﺑﻪ ﻻﻳﻪ ﭘﺎﻳﻴﻦ ﺗﺮ ﻭ ﺩﺭ ﺳﻤﺖ ﮔﻴﺮﻧﺪﻩ ﺗﺮﺗﻴﺐ ﺑﺮﻋﻜﺲ ﺍﺳﺖ‪.‬‬
‫ﺩﺭ ﺍﻳﻨﺠﺎ ﻫﺮ ﻳﻚ ﺍﺯ ﻻﻳﻪ ﻫﺎﻱ ﻣﺪﻝ ‪ OSI‬ﺭﺍ ﺑﻪ ﺍﺧﺘﺼﺎﺭ ﻣﻌﺮﻓﻲ ﻣﻴﻜﻨﻴﻢ‪:‬‬
‫ﻻﻳﻪ ‪ - ۱‬ﻳﺎ ﻻﻳﻪ ﻓﻴﺰﻳﻜﻲ‬
‫ﺍﻳﻦ ﻻﻳﻪ ﻛﻪ ﭘﺎﻳﻴﻦ ﺗﺮﻳﻦ ﻻﻳﻪ ﻣﺪﻝ ‪ OSI‬ﻣﻴﺒﺎﺷﺪ ﺑﺎ ﻣﺸﺨﺼﺎﺕ ﺍﻟﻜﺘﺮﻳﻜﻲ ﻭ ﻣﻜﺎﻧﻴﻜﻲ ﻣﺤﻴﻂ ﺍﻧﺘﻘﺎﻝ ﺳﺮﻭ ﻛﺎﺭ ﺩﺍﺭﺩ ﻭ ﺩﺭ ﻭﺍﻗﻊ‬
‫ﺑﺴﺘﺮ ﻣﻨﺎﺳﺐ ﺭﺍ ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﻓﺮﺍﻫﻢ ﻣﻴﻜﻨﺪ‪ .‬ﻭﻇﻴﻔﻪ ﺍﺭﺳﺎﻝ ﻭ ﺩﺭﻳﺎﻓﺖ ﺑﻴﺖ ﻫﺎﻱ ﺑﺴﺘﻪ ﻫﺎﻱ ﺩﻳﺘﺎ ﺑﻌﻬﺪﻩ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ ﻳﻌﻨﻲ ﺍﮔﺮ‬
‫ﻓﺮﺳﺘﻨﺪﻩ ‪ ۱‬ﺑﻔﺮﺳﺘﺪ ﮔﻴﺮﻧﺪﻩ ﻧﻴﺰ ﺑﺎﻳﺪ ‪ 1‬ﺩﺭﻳﺎﻓﺖ ﻛﻨﺪ ﻧﻪ ‪ . 0‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﺍﻳﻦ ﺑﻴﺖ ﻫﺎ ﺩﺭ ﺍﻳﻦ ﻻﻳﻪ ﻫﻴﭻ ﻣﻔﻬﻮﻡ ﺧﺎﺻﻲ ﻧﺪﺍﻧﺪ‪.‬‬
‫ﺑﻌﺒﺎﺭﺕ ﺩﻳﮕﺮ ﺍﻳﻦ ﻻﻳﻪ ﻧﻤﻴﺪﺍﻧﺪ ﺁﻧﭽﻪ ﺍﺭﺳﺎﻝ ﻳﺎ ﺩﺭﻳﺎﻓﺖ ﻣﻴﺸﻮﺩ ﺍﺻﻞ ﭘﻴﺎﻡ ﺍﺳﺖ ﻳﺎ ﺑﻴﺖ ﻫﺎﻱ ﻛﻨﺘﺮﻟﻲ ﺍﺳﺖ ﺻﺮﻓﺎ ﺍﺭﺗﺒﺎﻁ ﺭﺍ‬
‫ﻓﺮﺍﻫﻢ ﻣﻴﻜﻨﺪ‪ .‬ﻧﺤﻮﻩ ﺍﺭﺗﺒﺎﻁ ﺩﺭ ﺍﻳﻦ ﻻﻳﻪ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﺼﻮﺭﺕ ﺳﺮﻱ ) ﻳﻚ ﺑﻴﺖ ﺩﺭ ﻟﺤﻈﻪ( ﺑﺎﺷﺪ ﻣﺎﻧﻨﺪ ‪ . RS232‬ﻫﻤﻴﻨﻄﻮﺭ‬
‫ﻣﻤﻜﻦ ﺍﺳﺖ ﻧﺤﻮﻩ ﺍﺭﺗﺒﺎﻁ ﺑﺼﻮﺭﺕ ﻣﻮﺍﺯﻱ ) ﭼﻨﺪ ﺑﻴﺖ ﺩﺭ ﻟﺤﻈﻪ( ﺑﺎﺷﺪ ﻣﺎﻧﻨﺪ ‪ .RS485‬ﻗﺮﺍﺭﺩﺍﺩﻫﺎﻱ ﻣﺮﺑﻮﻁ ﺑﻪ ﺳﻄﻮﺡ ﻭﻟﺘﺎﮊ ﻭ‬
‫ﺷﻜﻞ ﻣﻮﺝ ﻫﺎﻱ ﻭﻟﺘﺎﮊ ﻭ ﺟﺮﻳﺎﻥ ﺩﺭ ﺧﻂ ‪ ،‬ﻧﻮﻉ ﻣﺪﻭﻻﺳﻴﻮﻥ ﻭ ﻓﺮﻛﺎﻧﺲ ﻛﺎﺭ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ‪.‬‬
‫‪Data Link‬‬ ‫ﻻﻳﻪ ‪ ۲‬ﻳﺎ ﻻﻳﻪ‬
‫ﺍﻳﻦ ﻻﻳﻪ ﺩﻳﮕﺮ ﺑﺎ ﺑﻴﺖ ﻫﺎ ﺳﺮﻭ ﻛﺎﺭ ﻧﺪﺍﺭﺩ ﺑﻠﻜﻪ ﺍﻃﻼﻋﺎﺕ ﺭﺍ ﺑﺼﻮﺭﺕ ﺑﺴﺘﻪ ﻳﺎ ‪ Frame‬ﻣﻲ ﺷﻨﺎﺳﺪ‪ .‬ﺍﻳﻦ ﻻﻳﻪ ﺩﺭ ﺳﻤﺖ ﻓﺮﺳﺘﻨﺪﻩ‬
‫ﻻ( ﭼﻨﺪ ﺻﺪ ﺑﺎﻳﺘﻲ ﺗﻘﺴﻴﻢ ﻛﻨﺪ‪ .‬ﺳﭙﺲ ﺍﻳﻦ ﺑﺴﺘﻪ ﻫﺎ ﺭﺍ ﺑﻪ‬
‫ﻻﻳﻪ ﺑﺎﻻﺗﺮ ﺧﻮﺩ ﺭﺍ ﻣﺠﺒﻮﺭ ﻣﻴﻜﻨﺪ ﺗﺎ ﺩﺍﺩﻩ ﻫﺎ ﺭﺍ ﺑﻪ ﺗﻌﺪﺍﺩﻱ ﺑﺴﺘﻪ )ﻣﻌﻤﻮ ﹲ‬
‫ﺗﺮﺗﻴﺐ ﺑﺮﺍﻱ ﮔﻴﺮﻧﺪﻩ ﻣﻴﻔﺮﺳﺘﺪ‪.‬ﺗﺸﺨﻴﺺ ﻣﺤﺪﻭﺩﻩ ﺑﺴﺘﻪ ﻫﺎ ﺑﺎ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ ﻭ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺫﻛﺮ ﺷﺪ ﻻﻳﻪ ﻓﻴﺰﻳﻜﻲ ﺍﻳﻦ ﻣﺤﺪﻭﺩﻩ‬
‫ﺭﺍ ﺗﺸﺨﻴﺺ ﻧﻤﻲ ﺩﻫﺪ‪.‬‬
‫ﻭﻇﺎﻳﻒ ﻣﻬﻢ ﻻﻳﻪ ‪ ۲‬ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ‪:‬‬
‫ﺗﺸﺨﻴﺺ ﻣﺤﺪﻭﺩﻩ ﺑﺴﺘﻪ ﻫﺎ‬ ‫•‬

‫ﺁﺷﻜﺎﺭﺳﺎﺯﻱ ﻭﺗﺼﺤﻴﺢ ﺧﻄﺎ‬ ‫•‬

‫ﺑﺮﻗﺮﺍﺭﻱ ﺳﺮﻭﻳﺴﻬﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ‬ ‫•‬

‫ﻛﻨﺘﺮﻝ ﺟﺮﻳﺎﻥ ﺍﻧﺘﻘﺎﻝ ﺩﻳﺘﺎ‬ ‫•‬

‫ﺍﻟﻒ( ﺗﺸﺨﻴﺺ ﻣﺤﺪﻭﺩﻩ ﺑﺴﺘﻪ ﻫﺎ‬
‫ﺑﺮﺍﻱ ﺗﺸﺨﻴﺺ ﻣﺤﺪﻭﺩﻩ ﺑﺴﺘﻪ ﻫﺎ ﺭﻭﺵ ﻫﺎﻱ ﻣﺨﺘﻠﻔﻲ ﻣﻴﺘﻮﺍﻧﺪ ﺍﺳﺘﻔﺎﺩﻩ ﺷﻮﺩ‪:‬‬
‫ﺩﺭﺝ ﻓﻮﺍﺻﻞ ﺯﻣﺎﻧﻲ ﺑﻴﻦ ﺑﺴﺘﻪ ﻫﺎ‬ ‫‪.١‬‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻓﺮﺳﺘﻨﺪﻩ ﭘﺲ ﺍﺯ ﺍﺭﺳﺎﻝ ﻳﻚ ﺑﺴﺘﻪ ﻣﺪﺗﻲ ﺻﺒﺮ ﻛﺮﺩﻩ ﺳﭙﺲ ﺑﺴﺘﻪ ﺑﻌﺪﻱ ﺭﺍ ﻣﻴﻔﺮﺳﺘﺪ‪ .‬ﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﺻﻮﺭﺗﻲ ﻣﻔﻴﺪ‬
‫ﻼ ﺑﺎ ﻫﻢ ﺍﺯ ﻧﻈﺮ ﺯﻣﺎﻧﻲ ﺳﻨﻜﺮﻭﻥ ﺑﺎﺷﻨﺪ ‪.‬‬
‫ﺍﺳﺖ ﻛﻪ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﮔﻴﺮﻧﺪﻩ ﻛﺎﻣ ﹲ‬
‫‪Techno-Electro.com‬‬

‫‪٢١٣‬‬ ‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬

‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺑﻴﺖ ﺷﺮﻭﻉ ﻭ ﭘﺎﻳﺎﻥ ﺑﺮﺍﻱ ﻫﺮ ﺑﺎﻳﺖ ﺍﺯ ﺑﺴﺘﻪ ﺩﻳﺘﺎ‬ ‫‪.٢‬‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﻛﻪ ﺑﻪ ﺁﺳﻨﻜﺮﻭﻥ ﻣﻌﺮﻭﻑ ﺍﺳﺖ ﻫﺮ ﻛﺎﺭﺍﻛﺘﺮ ﺑﺎ ﻳﻚ ﺑﻴﺖ ﻛﻪ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﺁﻏﺎﺯ ﺍﺳﺖ ﺷﺮﻭﻉ ﻣﻴﮕﺮﺩﺩ ﻭ ﺑﺎ ﻳﻚ‬
‫ﺑﻴﺖ ﺩﻳﮕﺮ ﻛﻪ ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﭘﺎﻳﺎﻥ ﺍﺳﺖ ﺧﺎﺗﻤﻪ ﻣﻲ ﻳﺎﺑﺪ‪.‬‬

‫ﭘﺲ ﺑﺮﺍﻱ ﻫﺮ ﺑﺎﻳﺖ ﺍﺯ ﺩﻳﺘﺎ ﺣﺪﺍﻗﻞ ‪ ٢‬ﺑﻴﺖ ﺩﻳﮕﺮ ﺑﺎﻳﺪ ﺍﺿﺎﻓﻪ ﻛﻨﻴﻢ ﻛﻪ ﺍﻳﻦ ﻛﺎﺭ ﻣﻮﺟﺐ ﺍﻓﺰﺍﻳﺶ ﺑﺎﻻﺳﺮﻱ )‪ (overhead‬ﺳﻴﮕﻨﺎﻝ‬
‫ﻣﻴﮕﺮﺩﺩ‪.‬‬
‫ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻳﻚ ﺑﺎﻳﺖ ﻣﺸﺨﺺ ﺩﺭ ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎﻱ ﺑﺴﺘﻪ ﺩﻳﺘﺎ‬ ‫‪.٣‬‬
‫ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺑﺠﺎﻱ ﺁﻧﻜﻪ ﺑﺮﺍﻱ ﻫﺮ ﺑﺎﻳﺖ ﻛﺪﻫﺎﻱ ﺷﺮﻭﻉ ﻭ ﭘﺎﻳﺎﻥ ﺭﺍ ﺑﻜﺎﺭ ﺑﺒﺮﻳﻢ ﺑﺮﺍﻱ ﻛﻞ ﺑﺴﺘﻪ ﺍﻃﻼﻋﺎﺗﻲ ﺍﺯ ﻛﺎﺭﺍﻛﺘﺮ ﺧﺎﺻﻲ ﻛﻪ‬
‫ﻧﺸﺎﻥ ﺩﻫﻨﺪﻩ ﺷﺮﻭﻉ ﺑﺴﺘﻪ ﺍﺳﺖ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺍﻳﻦ ﻛﺎﺭﺍﻛﺘﺮ ﻫﻤﻮﺍﺭﻩ ﻣﻘﺪﺍﺭ ﻣﺸﺨﺺ ﻭ ﺛﺎﺑﺘﻲ ﺍﺳﺖ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﺭ ﭘﺮﻭﺗﻜﻞ‬
‫‪ HDLC‬ﺍﺯ ﻛﺪ ‪ 01111110‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﮕﺮﺩﺩ‪.‬ﺑﺪﻳﻬﻲ ﺍﺳﺖ ﮔﻴﺮﻧﺪﻩ ﺩﺭ ﺍﺑﺘﺪﺍ ﺑﺎﻳﺪ ﺑﻪ ﺩﻧﺒﺎﻝ ﺍﻳﻦ ﻛﺪ ﺑﮕﺮﺩﺩ ﻭ ﭘﺲ ﺍﺯ ﻳﺎﻓﺘﻦ ﺁﻥ‬
‫‪ ،‬ﺍﻃﻼﻋﺎﺕ ﻣﻮﺟﻮﺩ ﺩﺭ ﺑﺴﺘﻪ ﺭﺍ ﺑﺨﻮﺍﻧﺪ‪.‬ﺍﻳﻦ ﺭﻭﺵ ﻧﺴﺒﺖ ﺑﻪ ﺭﻭﺵ ﻗﺒﻠﻲ ﺑﺎﻻﺳﺮﻱ ﻛﻤﺘﺮﻱ ﺭﺍ ﺑﻪ ﺳﻴﮕﻨﺎﻝ ﺗﺤﻤﻴﻞ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﻣﻴﺘﻮﺍﻥ ﺍﺯ ﺗﺮﻛﻴﺐ ﺍﻳﻦ ﺭﻭﺷﻬﺎ ﺍﺳﺘﻔﺎﺩﻩ ﻛﺮﺩ ﻣﺜﻼ ﻫﺮ ﺑﺎﻳﺖ ﺩﺍﺭﺍﻱ ﺑﻴﺖ ﺷﺮﻭﻉ ﻭ ﭘﺎﻳﺎﻥ ﺑﺎﺷﺪ ﻭ ﻛﻞ ﺑﺴﺘﻪ ﻛﺎﺭﺍﻛﺘﺮ ﺷﺮﻭﻉ ﻭ ﭘﺎﻳﺎﻥ‬
‫ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ‪.‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻣﺪﻝ‪ OSI‬ﺻﺮﻓﹲﺎ ﻭﻇﺎﻳﻒ ﻻﻳﻪ ‪ ۲‬ﺭﺍ ﻣﺸﺨﺺ ﻛﺮﺩﻩ ﺍﺳﺖ ﻭ ﺩﺭﻣﻮﺭﺩ ﺍﻳﻨﻜﻪ ﻧﺤﻮﻩ ﺗﺸﺨﻴﺺ ﺑﺴﺘﻪ‬
‫ﺩﻳﺘﺎ ﭼﮕﻮﻧﻪ ﺑﺎﺷﺪ ﺩﺧﺎﻟﺘﻲ ﻧﻤﻴﻜﻨﺪ ‪ .‬ﻃﺮﺍﺡ ﻣﻴﺘﻮﺍﻧﺪ ﺍﺯﭘﺮﻭﺗﻜﻞ ﻫﺎﻱ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﺑﺮﺍﻱ ﺍﻳﻦ ﻣﻨﻈﻮﺭ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﺪ‪.‬‬
‫ﺏ( ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﻭ ﺗﺼﺤﻴﺢ ﺧﻄﺎ‬
‫ﻭﻇﻴﻔﻪ ﺩﻳﮕﺮ ﻻﻳﻪ ﺩﻭﻡ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺧﻄﺎ ﻣﻴﺒﺎﺷﺪ‪.‬ﺧﻄﺎﻫﺎﻳﻲ ﻣﺎﻧﻨﺪ ‪:‬‬
‫ﮔﻢ ﺷﺪﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ‬ ‫•‬
‫ﺧﺮﺍﺏ ﺷﺪﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ‬ ‫•‬
‫ﮔﻢ ﺷﺪﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ‬
‫ﻣﻨﻈﻮﺭ ﺍﺯ ﮔﻢ ﺷﺪﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺍﻳﻨﺴﺖ ﻛﻪ ﻛﻪ ﺑﺪﻟﻴﻞ ﻭﻗﻮﻉ ﺍﺷﻜﺎﻝ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﮔﻴﺮﻧﺪﻩ ﻧﺘﻮﺍﻧﺪ ﺑﺴﺘﻪ ﺭﺍ ﺗﺤﻮﻳﻞ ﺑﮕﻴﺮﺩ‪ .‬ﺑﺮﺍﻱ‬
‫ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺍﻳﻦ ﺧﻄﺎ ﻓﺮﺳﺘﻨﺪﻩ ﺑﺎ ﺍﺭﺳﺎﻝ ﻫﺮ ﺑﺴﺘﻪ ﺗﺎﻳﻤﺮ ﺧﺎﺻﻲ ﺭﺍ ﻓﻌﺎﻝ ﻣﻴﻜﻨﺪ ﺍﮔﺮ ﺩﺭ ﻃﻮﻝ ﺯﻣﺎﻥ ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺗﺎﻳﻴﺪﻳﻪ ﺍﺯ ﻃﺮﻑ‬
‫‪Techno-Electro.com‬‬

‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬ ‫‪٢١٤‬‬

‫ﮔﻴﺮﻧﺪﻩ ﻧﺮﺳﻴﺪ ﻓﺮﺳﺘﻨﺪﻩ ﻣﺠﺪﺩﺍ ﺍﻗﺪﺍﻡ ﺑﻪ ﺍﺭﺳﺎﻝ ﻫﻤﺎﻥ ﺑﺴﺘﻪ ﻣﻴﻜﻨﺪ ﻭ ﺍﻳﻨﻜﺎﺭ ﺭﺍ ﺑﻪ ﺗﻌﺪﺍﺩ ﺩﻓﻌﺎﺕ ﻣﺸﺨﺼﻲ ﻛﻪ ﺍﺯﻗﺒﻞ ﺑﺮﺍﻳﺶ‬
‫ﺗﻌﺮﻳﻒ ﺷﺪﻩ ﺗﻜﺮﺍﺭ ﻣﻴﻜﻨﺪ‪ .‬ﺑﺎﻳﺪ ﺗﻮﺟﻪ ﺩﺍﺷﺖ ﻛﻪ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﺑﺴﺘﻪ ﺑﺎ ﻫﻤﺎﻥ ﺷﻤﺎﺭﻩ ﺍﺭﺳﺎﻝ ﻣﻴﮕﺮﺩﺩ ﻭ ﻻﻳﻪ ﺩﻭﻡ ﮔﻴﺮﻧﺪﻩ ﻛﻨﺘﺮﻝ‬
‫ﻣﻴﻜﻨﺪ ﻛﻪ ﺍﮔﺮ ﺷﻤﺎﺭﻩ ﺑﺴﺘﻪ ﺗﻜﺮﺍﺭﻱ ﺑﺎﺷﺪ ﺑﻪ ﻻﻳﻪ ﺑﺎﻻﺗﺮ ﺗﺤﻮﻳﻞ ﺩﺍﺩﻩ ﻧﺸﻮﺩ‪.‬‬

‫ﺧﺮﺍﺏ ﺷﺪﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ‬

‫ﻣﻨﻈﻮﺭ ﺍﺯ ﺧﺮﺍﺏ ﺷﺪﻥ ﺑﺴﺘﻪ ﺩﻳﺘﺎ ﺍﻳﻨﺴﺖ ﻛﻪ ﺩﺭ ﺍﻳﻨﺤﺎﻟﺖ ﮔﻴﺮﻧﺪﻩ ﺑﺴﺘﻪ ﺍﻱ ﺩﺭﻳﺎﻓﺖ ﻛﺮﺩﻩ )ﭘﺲ ﺑﺮﺧﻼﻑ ﺣﺎﻟﺖ ﻗﺒﻞ ﺑﺴﺘﻪ ﮔﻢ‬
‫ﻧﺸﺪﻩ ﺍﺳﺖ( ﻭﻟﻲ ﭼﮕﻮﻧﻪ ﻣﻴﺘﻮﺍﻥ ﺍﻃﻤﻴﻨﺎﻥ ﺩﺍﺷﺖ ﻛﻪ ﺍﻳﻦ ﺑﺴﺘﻪ ﺩﺭ ﺣﻴﻦ ﺍﺭﺳﺎﻝ ﺩﭼﺎﺭ ﺍﺷﻜﺎﻝ ﻧﺸﺪﻩ ﺍﺳﺖ‪ .‬ﻣﻴﺪﺍﻧﻴﻢ ﻋﻮﺍﻣﻠﻲ ﻣﺎﻧﻨﺪ‬
‫ﻧﻮﻳﺰ ﻭ ﺗﻀﻌﻴﻒ ﻣﻴﺘﻮﺍﻧﻨﺪ ﻣﻨﺠﺮ ﺑﻪ ﺧﺮﺍﺏ ﺷﺪﻥ ﺑﻴﺖ ﻫﺎﻱ ﺍﺭﺳﺎﻟﻲ ﺷﻮﻧﺪ‪ .‬ﭘﺲ ﺑﻪ ﻧﺤﻮﻱ ﺑﺎﻳﺪ ﺍﻳﻦ ﺧﻄﺎ ﺭﺍ ﻛﻨﺘﺮﻝ ﻧﻤﻮﺩ‪.‬‬
‫ﻳﻚ ﺭﻭﺵ ﺑﺮﺍﻱ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺧﻄﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺑﻴﺖ ‪ Parity‬ﻫﻤﺮﺍﻩ ﺑﺎ ﺩﻳﺘﺎ ﻣﻴﺒﺎﺷﺪ‪ .‬ﺩﺭ ﺍﻳﻦ ﺭﻭﺵ ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﻫﺮ ﺑﺎﻳﺖ ﺍﺯ ﺩﻳﺘﺎ‬
‫ﻳﻚ ﺑﻴﺖ ﺑﻪ ﻧﺎﻡ ‪ Parity‬ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺻﻔﺤﻪ ﻗﺒﻞ ﺍﺿﺎﻓﻪ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﻣﻴﺘﻮﺍﻧﺪ ﻳﻜﻲ ﺍﺯ ﺩﻭ ﻧﻮﻉ ﺯﻳﺮ ﺑﺎﺷﺪ‪:‬‬
‫‪ : Even Parity‬ﺍﮔﺮ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺑﺎﻳﺖ ﺩﻳﺘﺎ ﺑﺎ ﺍﺣﺘﺴﺎﺏ ﺧﻮﺩ ﺑﻴﺖ ‪ Parity‬ﺯﻭﺝ ﺑﺎﺷﺪ ﺍﻳﻦ ﺑﻴﺖ ‪۱‬‬ ‫•‬
‫ﻣﻴﺸﻮﺩ‪ .‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮ ﺑﺎﻳﺖ ﺑﺼﻮﺭﺕ ‪ 01110011‬ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ﺗﻌﺪﺍﺩ ﻳﻜﻬﺎ ﺑﺎ ﺍﺣﺘﺴﺎﺏ ﺧﻮﺩ ‪ Parity‬ﺯﻭﺝ‬
‫ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﻭ ﻛﺪ ﺍﺭﺳﺎﻟﻲ ﺑﺼﻮﺭﺕ ‪011100111‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪ .‬ﻳﺎ ﺍﮔﺮ ﻣﺜﻼ ﺑﺎﻳﺖ ﺑﺼﻮﺭﺕ ‪ 11101101‬ﺑﺎﺷﺪ ﺩﺭ‬
‫ﺍﻳﻨﺼﻮﺭﺕ ﻛﺪ ﺍﺭﺳﺎﻟﻲ ﺑﺼﻮﺭﺕ ‪ 111011010‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬
‫‪:Odd Parity‬ﺍﮔﺮ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﺑﺎﻳﺖ ﺩﻳﺘﺎ ﻓﺮﺩ ﺑﺎﺷﺪ ﺑﻴﺖ ‪ Parity‬ﻳﻚ ﺧﻮﺍﻫﺪ ﺑﻮﺩ‪.‬‬ ‫•‬

‫ﻭﻳﮋﮔﻲ ﺁﺷﻜﺎﺭ ﺳﺎﺯﻱ ﺧﻄﺎ ﺑﻪ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ) ‪ ( HD‬ﺁﻥ ﺑﺴﺘﮕﻲ ﺩﺍﺭﺩ‪.‬ﻣﻨﻈﻮﺭ ﺍﺯ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﺗﻌﺪﺍﺩ ﺑﻴﺖ ﻫﺎﻱ ﻣﺘﻔﺎﻭﺕ ﺩﺭ‬
‫ﺩﻭ ﺩﻳﺘﺎﻱ ﻣﺘﻮﺍﻟﻲ ﻣﻴﺒﺎﺷﺪ ‪.‬ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﻭ ﻣﻘﺪﺍﺭ ‪ 110010‬ﻭ ‪ 110100‬ﻛﻪ ﺗﺮﻛﻴﺐ ﺩﻳﺘﺎ ﻫﻤﺮﺍﻩ ﺑﺎ ﻛﺪ ‪ Parity‬ﻫﺴﺘﻨﺪ ﺩﺍﺭﺍﻱ‬
‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ‪ ۲‬ﻣﻴﺒﺎﺷﻨﺪ ﺯﻳﺮﺍ ﺩﻭ ﺑﻴﺖ ﺁﻧﻬﺎ ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ‬

‫ﺍﮔﺮ ﺧﻮﺍﻧﻨﺪﻩ ﻣﺤﺘﺮﻡ ﻧﻴﺎﺯ ﺑﻪ ﺍﻃﻼﻋﺎﺕ ﺩﻗﻴﻘﺘﺮﻱ ﺩﺭ ﻣﻮﺭﺩ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﺩﺍﺭﺩ ﻣﻴﺘﻮﺍﻥ ﻣﻮﺿﻮﻉ ﺭﺍ ﺩﺭ ﺍﻧﺘﻬﺎﻱ ﺍﻳﻦ ﺿﻤﻴﻤﻪ ﻣﻄﺎﻟﻌﻪ‬
‫ﻧﻤﺎﻳﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢١٥‬‬ ‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬

‫ﺝ ( ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ‬
‫ﺍﺯ ﺟﻤﻠﻪ ﻭﻇﺎﻳﻒ ﺩﻳﮕﺮ ﻻﻳﻪ ‪ ٢‬ﺑﺮﻗﺮﺍﺭﻱ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺍﺭﺗﺒﺎﻃﻲ ﺍﺳﺖ‪ .‬ﻛﻪ ﻋﺒﺎﺭﺗﻨﺪ ﺍﺯ ‪:‬‬
‫‪SDA‬‬ ‫ﺳﺮﻭﻳﺲ‬
‫ﺗﻮﺳﻂ ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﺩﻳﺘﺎ ﺍﺯ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻪ ﺍﻳﺴﺘﮕﺎﻩ ﺩﻳﮕﺮ )‪ ( Peer to Peer‬ﻣﻨﺘﻘﻞ ﺷﺪﻩ ﻭ ﭘﺲ ﺍﺯ ﺍﺗﻤﺎﻡ ﺍﺭﺳﺎﻝ ﺗﺎﻳﻴﺪ‬
‫ﺩﺭﻳﺎﻓﺖ ﺍﺯ ﻃﺮﻑ ﮔﻴﺮﻧﺪﻩ ﺑﻪ ﻓﺮﺳﺘﻨﺪﻩ ﺍﻋﻼﻡ ﻣﻴﺸﻮﺩ‪ .‬ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﺩﺭ ‪ DP‬ﻛﺎﺭﺑﺮﺩ ﻧﺪﺍﺭﺩ‪.‬‬

‫‪SDN‬‬ ‫ﺳﺮﻭﻳﺲ‬
‫ﺗﻮﺳﻂ ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﺩﻳﺘﺎ ﺍﺯ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ‬
‫ﺑﻪ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺩﻳﮕﺮ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ )‪( Peer to Peer‬‬
‫ﺑﻪ ﭼﻨﺪ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻮﺭﺩ ﻧﻈﺮ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ ﻛﻪ ﺑﻪ ﺁﻥ ‪ Multicast‬ﻣﻴﮕﻮﻳﻨﺪ‬
‫ﺑﻪ ﻫﻤﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﻣﺘﺼﻞ ﺑﻪ ﺑﺎﺱ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ ﻛﻪ ﺑﻪ ﺁﻥ ‪ Broadcast‬ﻣﻴﮕﻮﻳﻨﺪ‬
‫ﭘﺲ ﺍﺯ ﺍﺗﻤﺎﻡ ﺍﺭﺳﺎﻝ ‪ ،‬ﻓﺮﺳﺘﻨﺪﻩ ﭘﻴﻐﺎﻣﻲ ﻣﺒﻨﻲ ﺑﺮ ﺍﺗﻤﺎﻡ ﺍﺭﺳﺎﻝ ﺩﺭﻳﺎﻓﺖ ﻣﻴﻜﻨﺪ ﻭﻟﻲ ﺍﺯ ﺍﻳﻨﻜﻪ ﺍﻳﺴﺘﮕﺎﻩ ﻳﺎ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ﻣﻮﺭﺩ ﻧﻈﺮ ﺩﻳﺘﺎ‬
‫ﺭﺍ ﺩﺭﻳﺎﻓﺖ ﻛﺮﺩﻩ ﺍﻧﺪ ﻳﺎ ﻧﻪ ﻣﻄﻠﻊ ﻧﻤﻴﺸﻮﺩ ﺯﻳﺮﺍ ﺩﺭﻳﺎﻓﺖ ﺩﻳﺘﺎ ‪ Acknowledge،‬ﻧﻤﻲ ﺷﻮﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬ ‫‪٢١٦‬‬

‫‪SRD‬‬ ‫ﺳﺮﻭﻳﺲ‬
‫ﺗﻮﺳﻂ ﺍﻳﻦ ﺳﺮﻭﻳﺲ ﺩﻳﺘﺎ ﺍﺯ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺑﻪ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺩﻳﮕﺮ ﻣﻨﺘﻘﻞ ﺷﺪﻩ ﻭ ﺑﻼﻓﺎﺻﻠﻪ ﺍﺯ ﺁﻥ ﺍﻳﺴﺘﮕﺎﻩ ﺩﻳﺘﺎ ﺩﺭﺧﻮﺍﺳﺖ ﻣﻴﺸﻮﺩ‪.‬‬
‫ﻓﺮﻣﺎﻥ ‪ Request‬ﺍﺯ ﻗﺒﻞ ﺁﻣﺎﺩﻩ ﺷﺪﻩ ﻭ ﺑﺪﻧﺒﺎﻝ ﻓﺮﻣﺎﻥ ‪ Send‬ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﺩ ‪ .‬ﺍﻳﻦ ﻛﺎﺭ ﺳﺮﻋﺖ ﻋﻤﻠﻜﺮﺩ ﺳﻴﺴﺘﻢ ﺭﺍ ﺑﺎﻻ ﻣﻴﺒﺮﺩ‪.‬‬
‫ﺍﮔﺮ ﺩﺭ ﺣﻴﻦ ﻛﺎﺭ ﺧﻄﺎﻳﻲ ﺭﺥ ﺩﻫﺪ ﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺗﻜﺮﺍﺭ ﻣﻴﺸﻮﺩ‪.‬‬

‫ﺍﺯ ﺳﺮﻭﻳﺲ ﻫﺎﻱ ﺳﻪ ﮔﺎﻧﻪ ﻓﻮﻕ ‪:‬‬

‫ﭘﺮﻭﻓﻲ ﺑﺎﺱ ‪ DP‬ﻓﻘﻂ ﺍﺯ ﺳﺮﻭﻳﺴﻬﺎﻱ ‪ SRD‬ﻭ ‪ SDN‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﭘﺮﻭﻓﻲ ﺑﺎﺱ ‪ PA‬ﻓﻘﻂ ﺍﺯ ﺳﺮﻭﻳﺴﻬﺎﻱ ‪ SRD‬ﻭ ‪ SDN‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﺪ‪.‬‬
‫ﭘﺮﻭﻓﻲ ﺑﺎﺱ ‪ FMS‬ﺍﺯ ﻫﺮ ﺳﻪ ﺳﺮﻭﻳﺲ ‪ SDA‬ﻭ ‪ SDN‬ﻭ ‪ SRD‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﺪ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢١٧‬‬ ‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬

‫‪Flow Control‬‬ ‫ﺝ( ﻛﻨﺘﺮﻝ ﺟﺮﻳﺎﻥ‬

‫ﺍﺯ ﻭﻇﺎﻳﻒ ﺩﻳﮕﺮ ﻻﻳﻪ ‪ ٢‬ﻛﻨﺘﺮﻝ ﺟﺮﻳﺎﻥ ﺍﺭﺳﺎﻝ ﺑﺴﺘﻪ ﻫﺎﻳﻲ ﺍﺳﺖ ﻛﻪ ﺑﺪﻧﺒﺎﻝ ﻫﻢ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﻧﺪ‪.‬ﺍﮔﺮ ﺑﻪ ﺩﻟﻴﻠﻲ ﻣﺎﻧﻨﺪ ﻋﺪﻡ ﺗﻄﺎﺑﻖ‬
‫ﺳﺮﻋﺖ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﮔﻴﺮﻧﺪﻩ ‪ ،‬ﺑﺎﻓﺮ ﻣﻮﺟﻮﺩ ﺩﺭ ﮔﻴﺮﻧﺪﻩ ﭘﺮ ﺷﻮﺩ ﺑﺎﻳﺪ ﺑﻪ ﻧﺤﻮﻱ ﻓﺮﺳﺘﻨﺪﻩ ﺭﺍ ﻣﻄﻠﻊ ﻛﻨﺪ ﺗﺎ ﺍﺯ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎﻱ ﺟﺪﻳﺪ‬
‫ﺧﻮﺩﺩﺍﺭﻱ ﻧﻤﺎﻳﺪ‪ .‬ﺍﻳﻦ ﻣﻮﺿﻮﻉ ﻣﻴﺘﻮﺍﻧﺪ ﺑﻄﺮﻳﻖ ﻧﺮﻡ ﺍﻓﺰﺍﺭﻱ ﺗﻮﺳﻂ ﺳﻴﮕﻨﺎﻝ ‪ Xoff‬ﻳﺎ ﺍﻳﻨﻜﻪ ﺑﺼﻮﺭﺕ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻣﺜﻼ ﺑﺎ‬
‫ﺳﻴﮕﻨﺎﻟﻬﺎﻱ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ‪ RTS,CTS‬ﺩﺭ ‪ RS232‬ﺑﻪ ﻓﺮﺳﺘﻨﺪﻩ ﺍﻃﻼﻉ ﺩﺍﺩﻩ ﺷﻮﺩ‪.‬‬

‫ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺗﻮﺿﻴﺤﺎﺗﻲ ﻛﻪ ﺩﺭ ﻣﻮﺭﺩ ﻻﻳﻪ ‪ ٢‬ﺩﺍﺩﻩ ﺷﺪ ﺑﻄﻮﺭ ﺧﻼﺻﻪ ﻣﻴﺘﻮﺍﻥ ﮔﻔﺖ‪ :‬ﻭﻇﻴﻔﻪ ﻻﻳﻪ ‪ ٢‬ﺑﺮﻗﺮﺍﻱ ﺍﺭﺗﺒﺎﻁ ﺳﺎﻟﻢ ﻭ ﺑﺪﻭﻥ‬
‫ﺧﻄﺎ ﺑﻴﻦ ﺩﻭ ﺍﻳﺴﺘﮕﺎﻩ ﺍﺳﺖ‪.‬‬

‫ﻻﻳﻪ ‪ ٣‬ﻳﺎ ﻻﻳﻪ ‪Network‬‬

‫ﺭﻓﻊ ﺗﺮﺍﻓﻴﻚ ﻭ ﺗﺮﺍﻛﻢ ﺑﺴﺘﻪ ﻫﺎ ﻭ ﺟﻠﻮﮔﻴﺮﻱ ﺍﺯ ﺑﻮﺟﻮﺩ ﺁﻣﺪﻥ ﺍﻳﻦ ﻣﺸﻜﻞ ﺩﺭ ﺷﺒﻜﻪ ﺑﻌﻬﺪﻩ ﻻﻳﻪ ‪ ۳‬ﻣﻴﺒﺎﺷﺪ‪ .‬ﺍﮔﺮ ﺩﺭ ﻣﺴﻴﺮ ﺑﺴﺘﻪ‬
‫ﺩﻳﺘﺎ ﺷﺒﻜﻪ ﺟﺪﻳﺪﻱ ﻭﺟﻮﺩ ﺩﺍﺷﺘﻪ ﺑﺎﺷﺪ ﻛﻪ ﺍﺯ ﻧﻈﺮ ﭘﺮﻭﺗﻜﻞ ﺑﺎ ﺷﺒﻜﻪ ﺍﻭﻝ ﻓﺮﻕ ﻛﻨﺪ ﺍﻳﺠﺎﺩ ﺗﻄﺎﺑﻖ ﺑﻌﻬﺪﻩ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ‪.‬‬
‫ﺑﻄﻮﺭ ﺧﻼﺻﻪ ‪ :‬ﻭﻇﻴﻔﻪ ﺍﻳﻦ ﻻﻳﻪ ﻣﺴﻴﺮ ﻳﺎﺑﻲ ﻭ ﻫﺪﺍﻳﺖ ﺻﺤﻴﺢ ﺑﺴﺘﻪ ﻫﺎ ﺩﺭ ﺷﺒﻜﻪ ﺍﺳﺖ‪.‬‬

‫ﻻﻳﻪ ‪ ۴‬ﻳﺎ ﻻﻳﻪ‪Transport‬‬

‫ﺗﻘﺴﻴﻢ ﺩﺍﺩﻩ ﻫﺎ ﺑﻪ ﺑﺴﺘﻪ ﻫﺎﻱ ﻛﻮﭼﻜﺘﺮ ﻛﻪ ﻗﺎﺑﻞ ﺍﻧﺘﻘﺎﻝ ﺑﺎﺷﺪ ﺑﻌﻬﺪﻩ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ‪.‬‬

‫ﻻﻳﻪ ‪ ۵‬ﻳﺎ ﻻﻳﻪ ‪Session‬‬

‫ﺗﻮﺳﻂ ﺍﻳﻦ ﻻﻳﻪ ﺍﻣﻜﺎﻥ ﺍﻳﺠﺎﺩ ﺍﺭﺗﺒﺎﻁ ﻣﺸﺘﺮﻙ ﺑﻴﻦ ﭼﻨﺪ ﻛﺎﺭﺑﺮ ﻣﺘﻔﺎﻭﺕ ﺩﺭ ﺷﺒﻜﻪ ﻓﺮﺍﻫﻢ ﻣﻴﺸﻮﺩ‪ .‬ﻣﺪﻳﺮﻳﺖ ﻛﻨﺘﺮﻝ ﺍﺭﺗﺒﺎﻃﺎﺕ‬
‫ﺑﻌﻬﺪﻩ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﺭ ﺭﻭﺵ ‪ CSMA‬ﺟﻠﻮﮔﻴﺮﻱ ﺍﺯ ﻫﻤﺰﻣﺎﻧﻲ ﺷﺮﻭﻉ ﺑﻌﻬﺪﻩ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ‪ .‬ﺍﺯ ﻭﻇﺎﻳﻒ ﺩﻳﮕﺮ ﺍﻳﻦ‬
‫ﻻﻳﻪ ﻫﻤﺰﻣﺎﻥ ﺳﺎﺯﻱ ﻭ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﻳﻚ ﺳﺮﻱ ﻧﻘﺎﻁ ‪ Check Point‬ﺍﺳﺖ ﺗﺎ ﺩﺭ ﺻﻮﺭﺗﻲ ﻛﻪ ﺩﺭ ﻭﺳﻂ ﻛﺎﺭ ﺍﺭﺗﺒﺎﻁ ﻗﻄﻊ ﺷﺪ‬
‫ﻻﺯﻡ ﻧﺒﺎﺷﺪ ﺩﻳﺘﺎﻫﺎ ﺍﺯ ﺍﻭﻝ ﺍﺭﺳﺎﻝ ﺷﻮﻧﺪ ﺑﻠﻜﻪ ﺍﺯ ﺟﺎﻳﻲ ﻛﻪ ﻗﻄﻊ ﺷﺪﻩ ﺍﺩﺍﻣﻪ ﻣﻴﺪﻫﺪ‪ .‬ﺍﻳﻦ ﻭﻳﮋﮔﻲ ﺑﺮﺍﻱ ﺍﻧﺘﻘﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺣﺠﻴﻢ‬
‫ﺑﺴﻴﺎﺭ ﻣﻔﻴﺪ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬ ‫‪٢١٨‬‬

‫ﻻﻳﻪ ‪ ۶‬ﻳﺎ ﻻﻳﻪ ‪Presentation‬‬

‫ﻭﻇﻴﻔﻪ ﺍﺻﻠﻲ ﺍﻳﻦ ﻻﻳﻪ ﻓﺮﻣﺖ ﺑﻨﺪﻱ ﻭ ﻛﺪﮔﺬﺍﺭﻱ ﺑﺎ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ ﻣﺸﺨﺼﻲ ﺭﻭﻱ ﺩﻳﺘﺎ ﻫﺎﺳﺖ ﺗﺎ ﺍﻃﻼﻋﺎﺕ ﺩﺭﻳﺎﻓﺘﻲ ﺗﻮﺳﻂ ﮔﻴﺮﻧﺪﻩ‬
‫ﻗﺎﺑﻞ ﺍﺳﺘﻔﺎﺩﻩ ﺑﺎﺷﺪ‪ .‬ﻓﺸﺮﺩﻩ ﺳﺎﺯﻱ ﻭ ﺭﻣﺰ ﮔﺬﺍﺭﻱ ﺑﻤﻨﻈﻮﺭ ﺣﻔﺎﻇﺖ ﺍﻃﻼﻋﺎﺕ ﻧﻴﺰ ﺑﻌﻬﺪﻩ ﺍﻳﻦ ﻻﻳﻪ ﺍﺳﺖ‪.‬‬

‫ﻻﻳﻪ ‪ ۷‬ﻳﺎ ﻻﻳﻪ ‪Application‬‬

‫ﺍﻳﻦ ﻻﻳﻪ ﻛﻪ ﺑﺎﻻﺗﺮﻳﻦ ﻻﻳﻪ ﺍﺳﺖ ﻭﺍﺳﻂ ﺍﺭﺗﺒﺎﻃﻲ ﺑﻴﻦ ﻛﺎﺭﺑﺮ ) ﺑﺮﺍﻱ ﺍﺭﺳﺎﻝ ﻳﺎ ﺩﺭﻳﺎﻓﺖ( ﺑﺎ ﺳﺎﻳﺮ ﻻﻳﻪ ﻫﺎﺳﺖ‪ .‬ﺳﺎﺧﺘﺎﺭ ﺍﻳﻦ ﻻﻳﻪ ﺑﻪ‬
‫‪FTP‬‬ ‫ﻧﻮﻉ ﺳﻴﺴﺘﻢ ﻋﺎﻣﻞ ﺑﺴﺘﮕﻲ ﺩﺍﺭﺩ‪ .‬ﺧﺪﻣﺎﺕ ﻣﺮﺑﻮﻁ ﺑﻪ ﺍﻧﺘﻘﺎﻝ ﻓﺎﻳﻞ ‪ ،‬ﭘﺴﺖ ﺍﻟﻜﺘﺮﻭﻧﻴﻜﻲ ﺩﺭ ﺍﻳﻦ ﻻﻳﻪ ﻗﺮﺍﺭﺩﺍﺭﺩ ‪ .‬ﭘﺮﻭﺗﻜﻞ ﻫﺎﻱ‬
‫ﻭ ‪ HTTP‬ﺭﺍ ﻣﻴﺘﻮﺍﻥ ﺑﺮﺍﻱ ﺍﻳﻦ ﻻﻳﻪ ﻣﺜﺎﻝ ﺯﺩ‪.‬‬

‫ﻻﻳﻪ ﻫﺎﻱ ‪ OSI‬ﺩﺭ ﻓﻴﻠﺪﺑﺎﺱ‬

‫ﻻﻳﻪ ﻫﺎﻱ ﻣﺪﻝ ‪ OSI‬ﻛﻪ ﺩﺭ ﺻﻔﺤﺎﺕ ﻗﺒﻞ ﺫﻛﺮ ﺷﺪ ﻣﻤﻜﻦ ﺍﺳﺖ ﻫﻤﮕﻲ ﺩﺭ ﻳﻚ ﺳﻴﺴﺘﻢ ﺑﻜﺎﺭ ﮔﺮﻓﺘﻪ ﻧﺸﻮﻧﺪ‪ .‬ﻓﻴﻠﺪ ﺑﺎﺱ ﻧﻴﺰ‬
‫ﺍﺯﺟﻤﻠﻪ ﺍﻳﻦ ﺳﻴﺴﺘﻢ ﻫﺎﺳﺖ‪.‬‬
‫ﻓﻴﻠﺪﺑﺎﺱ ﺩﺭ ﻣﺪﻝ ﺧﻮﺩ ﺻﺮﻓﹲﺎ ﺍﺯ ﻻﻳﻪ ﻫﺎﻱ ‪۱‬ﻭ‪۲‬ﻭ‪ ۷‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﺪ‪ .‬ﺑﻌﺒﺎﺭﺕ ﺩﻳﮕﺮ ﻻﻳﻪ ﻫﺎﻱ ﻣﻴﺎﻧﻲ ﺣﺬﻑ ﺷﺪﻩ ﺍﻧﺪ ﻭ ﻭﻇﻴﻔﻪ ﺁﻧﻬﺎ‬
‫ﻋﻤﺪﺗﺎ ﺑﻪ ﻻﻳﻪ ﺩﻭﻡ ﻣﺤﻮﻝ ﺷﺪﻩ ﺍﺳﺖ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢١٩‬‬ ‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬

‫ﻭﺳﺎﻳﻞ ﺗﻄﺒﻴﻖ ﺩﻫﻨﺪﻩ ﻻﻳﻪ ﻫﺎ‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺫﻛﺮ ﺷﺪ ‪ OSI‬ﻳﻚ ﻣﺪﻝ ﺍﺳﺖ ﻧﻪ ﻳﻚ ﺍﺳﺘﺎﻧﺪﺍﺭﺩ‪ .‬ﺍﺯ ﺍﻳﻨﺮﻭ ﻣﻤﻜﻦ ﺍﺳﺖ ﻓﺮﺳﺘﻨﺪﻩ ﻭ ﮔﻴﺮﻧﺪﻩ ﺍﮔﺮﭼﻪ ﻫﺮﺩﻭ ﺍﺯﻣﺪﻝ‬
‫‪ OSI‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻨﺪ ﻭﻟﻲ ﺍﺳﺘﺎﻧﺪﺍﺭﺩﻫﺎﻱ ﻣﺘﻔﺎﻭﺗﻲ ﺭﺍ ﺩﺭ ﻻﻳﻪ ﻫﺎﻱ ﺧﻮﺩ ﺑﺮﺍﻱ ﻛﺪ ﮔﺬﺍﺭﻱ ﻭ ﺑﺴﺘﻪ ﺑﻨﺪﻱ ﺩﻳﺘﺎﻫﺎ ﺑﻜﺎﺭ ﺑﺒﺮﻧﺪ‪ .‬ﺩﺭ‬
‫ﺍﻳﻦ ﺣﺎﻻﺕ ﺑﺮﺍﻱ ﺍﻣﻜﺎﻥ ﺍﺭﺗﺒﺎﻁ ﺑﻴﻦ ﺩﻭ ﺷﺒﻜﻪ ﺑﺎﻳﺪ ﺍﺯ ﻭﺳﺎﻳﻞ ﺗﻄﺒﻴﻖ ﺩﻫﻨﺪﻩ ﻛﻪ ﺳﺨﺖ ﺍﻓﺰﺍﺭﻱ ﻫﺴﺘﻨﺪ ﺍﺳﺘﻔﺎﺩﻩ ﻛﻨﻴﻢ‪ .‬ﺍﻳﻦ ﻭﺳﺎﻳﻞ‬
‫ﺑﺘﺮﺗﻴﺐ ﺩﺭ ﺯﻳﺮ ﺫﻛﺮ ﺷﺪﻩ ﺍﻧﺪ‪:‬‬
‫ﻭﻗﺘﻲ ﻻﻳﻪ ﻫﺎ ﻣﺸﺎﺑﻪ ﺑﺎﺷﻨﺪ ﺑﺮﺍﻱ ﺗﻘﻮﻳﺖ ﺳﻴﮕﻨﺎﻝ ﺍﺯ ‪ Repeater‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‪ .‬ﺩﺭﺍﻳﻨﺤﺎﻟﺖ ‪ Repeater‬ﺑﻴﺸﺘﺮ ﻧﻘﺶ‬ ‫•‬

‫ﺗﻘﻮﻳﺖ ﻛﺮﺩﻥ ﺩﺍﺭﺩ ﺗﺎ ﻧﻘﺶ ﺗﻄﺒﻴﻖ ﺩﺍﺩﻥ‪.‬‬

‫ﻭﻗﺘﻲ ﻻﻳﻪ ‪ ۱‬ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﺪ ﺍﺯ ‪ Bridge‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‬ ‫•‬

‫‪Techno-Electro.com‬‬

‫‪OSI‬‬ ‫ﻻﻳﻪ ﻫﺎﻱ ﺷﺒﻜﻪ ﻭ ﻣﺪﻝ‬ ‫‪٢٢٠‬‬

‫ﻭﻗﺘﻲ ﻻﻳﻪ ﻫﺎﻱ ‪۱‬ﻭ‪ ۲‬ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﻨﺪ ﺍﺯ ‪ Router‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‬ ‫•‬

‫ﻭﻗﺘﻲ ﻻﻳﻪ ﻫﺎﻱ ﺑﺎﻻﺗﺮ ﻧﻴﺰ ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﻨﺪ ﺍﺯ ‪ Gateway‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻴﻜﻨﻴﻢ‬ ‫•‬
‫‪Techno-Electro.com‬‬

‫‪٢٢١‬‬ ‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﻭ ﻧﻘﺶ ﺁﻥ ﺩﺭ ﺗﺸﺨﻴﺺ ﻭ ﺍﺻﻼﺡ ﺧﻄﺎ‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ) ‪ ( Hamming Distance‬ﭼﻴﺴﺖ؟‬

‫ﻣﻲ ﺩﺍﻧﻴﻢ ﻳﻚ ﻛﺪ ﺩﻳﺠﻴﺘﺎﻝ ﺑﺼﻮﺭﺕ ﺗﻌﺪﺍﺩﻱ ﺍﺯ ﺻﻔﺮ ﻭ ﻳﻚ ﻇﺎﻫﺮ ﻣﻲ ﺷﻮﺩ ﻣﺎﻧﻨﺪ ‪10111001‬‬ ‫•‬
‫ﻭ ﻣﻴﺪﺍﻧﻴﻢ ﻛﻪ ﺩﺭ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﻛﺪﻫﺎ ﺑﺼﻮﺭﺕ ﺭﺷﺘﻪ ﻫﺎﻱ ﺟﺪﺍ ﺟﺪﺍ ﻭ ﺑﺪﻧﺒﺎﻝ ﻫﻢ ﺍﺭﺳﺎﻝ ﻣﻲ‬ ‫•‬
‫ﺷﻮﻧﺪ ‪:‬‬
‫‪ 10010010‬ﺭﺷﺘﻪ ﺍﻭﻝ‬
‫‪ 1010000‬ﺭﺷﺘﻪ ﺩﻭﻡ‬
‫ﺩﺭ ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ ﺗﻌﺪﺍﺩ ﻣﻮﻗﻌﻴﺘﻬﺎﻳﻲ ﺍﺯ ﺑﻴﺘﻬﺎ ﻛﻪ ﺑﺎ ﻳﻜﺪﻳﮕﺮ ﻣﺘﻔﺎﻭﺗﻨﺪ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﺧﻮﺍﻧﺪﻩ ﻣﻲ‬ ‫•‬
‫ﺷﻮﺩ‬
‫ﻣﺜﺎﻝ‬
‫‪10010010‬‬ ‫‪10010010‬‬ ‫‪10010010‬‬ ‫ﻛﺪ ﺍﻭﻝ‬

‫‪10011100‬‬ ‫‪10010001‬‬ ‫‪10010000‬‬ ‫ﻛﺪ ﺩﻭﻡ‬

‫‪HD=3‬‬ ‫‪HD=2‬‬ ‫‪HD=1‬‬ ‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫‪Techno-Electro.com‬‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬ ‫‪٢٢٢‬‬

‫ﺍﮔﺮ ﻛﺪﻫﺎﻱ ﻣﺘﻮﺍﻟﻲ ﻛﻪ ﺑﺪﻧﺒﺎﻝ ﻫﻢ ﺍﺭﺳﺎﻝ ﻣﻲ ﺷﻮﻧﺪ ﺩﺍﺭﺍﻱ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﻨﺪ ﻛﻤﺘﺮﻳﻦ‬ ‫•‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﺑﻌﻨﻮﺍﻥ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﻫﻤﻪ ﺁﻧﻬﺎ ﻣﺤﺴﻮﺏ ﺧﻮﺍﻫﺪ ﺷﺪ ﻣﺜﺎﻝ‪:‬‬

‫‪00000000‬‬
‫‪HD=1‬‬

‫‪00000001‬‬

‫‪HD=2‬‬
‫‪00000010‬‬

‫‪HD=1‬‬
‫‪00000011‬‬

‫‪HD=3‬‬

‫‪HD=1‬‬ ‫‪00000100‬‬

‫‪HD=1‬‬

‫‪00000101‬‬

‫‪HD=2‬‬

‫‪00000110‬‬

‫‪HD=1‬‬

‫‪00000111‬‬

‫‪HD=4‬‬
‫‪00001000‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٢٣‬‬ ‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﭼﮕﻮﻧﻪ ﻣﺤﺎﺳﺒﻪ ﻣﻲ ﺷﻮﺩ ؟‬
‫ﺑﺎ ﺍﻋﻤﺎﻝ ‪ XOR‬ﺭﻭﻱ ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ ﻭ ﺷﻤﺎﺭﺵ ﺗﻌﺪﺍﺩ ﻳﻜﻬﺎ ﺩﺭ ﻧﺘﻴﺠﻪ ﻣﻲ ﺗﻮﺍﻥ ﺗﻌﺪﺍﺩ ﺑﻴﺘﻬﺎﻱ‬ ‫•‬
‫ﻣﺘﻔﺎﻭﺕ ﻳﺎ ‪ HD‬ﺭﺍ ﻣﺤﺎﺳﺒﻪ ﻧﻤﻮﺩ ‪.‬‬
‫‪X+Y= X.Y+ X Y‬‬
‫ﺍﮔﺮ ‪ X‬ﻭ ‪ Y‬ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ ﺑﺎﺷﻨﺪ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ‬ ‫•‬

‫‪X‬‬ ‫‪X‬‬ ‫‪Y‬‬ ‫‪Y‬‬

‫‪01000000‬‬ ‫‪10111111‬‬ ‫‪00001100‬‬ ‫‪11110011‬‬

‫ﺑﺮ ﺍﺳﺎﺱ ﻣﻮﺍﺭﺩ ﻓﻮﻕ‬

‫‪X .Y= 00001100‬‬

‫‪X.Y= 01000000‬‬

‫‪X.Y + X.Y =01001100‬‬ ‫ﻓﺎﺻﻠﻪ ‪ =3=HD‬ﺗﻌﺪﺍﺩ ﻳﻜﻬﺎ‬

‫ﭼﺮﺍ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﻫﻤﻴﺸﻪ ﻳﻚ ﻧﻴﺴﺖ ؟‬

‫ﺷﺎﻳﺪ ﺗﺼﻮﺭ ﺷﻮﺩ ﻛﻪ ﺩﺭ ﺍﺭﺳﺎﻝ ﻳﻚ ﺳﺮﻱ ﺍﻃﻼﻋﺎﺕ ﺑﺎﻳﻨﺮﻱ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﻫﻤﻴﺸﻪ ﻳﻚ ﺍﺳﺖ )‪ ( HD=1‬ﻭﻟﻲ‬
‫ﻭﺍﻗﻌﻴﺖ ﺍﻳﻦ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺍﺭﺳﺎﻝ ﺩﻳﺘﺎ ﻫﺮ ﻓﺮﻡ ﻳﺎ ﻗﺎﺏ ﺩﻳﺘﺎ ﻣﺘﺸﻜﻞ ﺍﺯ ﺑﻴﺖ ﻫﺎﻱ ﺩﻳﺘﺎ ﺑﻪ ﺍﺿﺎﻓﻪ ﺑﻴﺖ ﻫﺎﻱ ﻛﻨﺘﺮﻟﻲ‬
‫ﺍﺳﺖ ﻛﻪ ﺑﻪ ﺍﺑﺘﺪﺍ ﻭ ﺍﻧﺘﻬﺎﻱ ﺩﺍﺩﻩ ﺍﺿﺎﻓﻪ ﻣﻲ ﺷﻮﻧﺪ ‪ .‬ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﻴﻦ ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ ﻣﻤﻜﻦ ﺍﺳﺖ ﺗﻌﺪﺍﺩﻱ ﺑﻴﺖ‬
‫ﻛﻨﺘﺮﻟﻲ ﻣﺸﺎﺑﻪ ﺑﻮﺩﻩ ﻭﻟﻲ ﺳﺎﻳﺮ ﺑﻴﺘﻬﺎ ﻣﺘﻔﺎﻭﺕ ﺑﺎﺷﻨﺪ ﺑﻄﻮﺭ ﻛﻠﻲ ‪:‬‬
‫ﺍﮔﺮ ‪ m‬ﺑﻴﺖ ﺩﻳﺘﺎ ﺩﺍﺷﺘﻪ ﺑﺎﺷﻴﻢ ﻭ ‪ r‬ﺑﻴﺖ ﺑﺮﺍﻱ ﻛﻨﺘﺮﻝ ﺑﻪ ﺁﻥ ﺍﺿﺎﻓﻪ ﻛﻨﻴﻢ ﻗﺎﺏ ‪ n‬ﺑﻴﺘﻲ ﺧﻮﺍﻫﻴﻢ ﺩﺍﺷﺖ ﻛﻪ‪:‬‬
‫‪n=m+r‬‬
‫ﺩﺭ ﺍﻳﻦ ﻗﺎﺏ ‪:‬‬
‫ﻻ ﺗﻤﺎﻡ ‪ 2m‬ﺣﺎﻟﺖ ﻣﻤﻜﻦ ﻛﻪ ﺑﺮﺍﻱ ﺩﻳﺘﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻣﻌﺘﺒﺮ ﺍﺳﺖ )ﻳﺎ ﻣﻌﺘﺒﺮ ﻓﺮﺽ ﻣﻲ ﺷﻮﺩ ( ﻭﻟﻲ ﺗﻤﺎﻡ ‪2n‬‬
‫ﻣﻌﻤﻮ ﹰ‬
‫ﺣﺎﻟﺖ ﻣﻤﻜﻦ ﻛﻪ ﺑﺮﺍﻱ ﻗﺎﺏ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻣﻌﺘﺒﺮ ﻧﻴﺴﺖ ﺯﻳﺮﺍ ﻣﻤﻜﻦ ﺍﺳﺖ ﺑﻴﺘﻬﺎﻱ ﻛﻨﺘﺮﻟﻲ ﺛﺎﺑﺖ ﺩﺭ ﺍﺛﺮ ﺑﺮﻭﺯ‬
‫ﺍﺷﻜﺎﻝ ﺍﺯ ‪ 0‬ﺑﻪ ‪ 1‬ﻳﺎ ﺑﺎﻟﻌﻜﺲ ﺗﻐﻴﻴﺮ ﻛﻨﻨﺪ ‪.‬‬
‫ﺑﻨﺎﺑﺮﺍﻳﻦ ﺑﺎﻳﺪ ﻓﻬﺮﺳﺘﻲ ﺍﺯ ‪ 2N‬ﺣﺎﻟﺖ ﻣﻤﻜﻦ ﺭﺍ ﺗﻬﻴﻪ ﻭ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﺭﺍ ﺩﺭ ﺁﻧﻬﺎ ﺑﺮﺭﺳﻲ ﻧﻤﻮﺩ ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬ ‫‪٢٢٤‬‬

‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﭼﻪ ﺍﺳﺘﻔﺎﺩﻩ ﺍﻱ ﺩﺍﺭﺩ ؟‬

‫ﺍﺯ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﻣﻲ ﺗﻮﺍﻥ ﺑﺮﺍﻱ ﻣﻘﺎﺻﺪ ﺯﻳﺮ ﺍﺳﺘﻔﺎﺩﻩ ﻧﻤﻮﺩ ‪:‬‬
‫‪-١‬ﺗﺸﺨﻴﺺ ﺧﻄﺎ‬
‫‪ -٢‬ﺗﺼﺤﻴﺢ ﺧﻄﺎ‬

‫ﭼﮕﻮﻧﮕﻲ ﺗﺸﺨﻴﺺ ﺧﻄﺎ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫ﺑﻄﻮﺭ ﻛﻠﻲ ﺑﺮﺍﻱ ﺷﻨﺎﺳﺎﻳﻲ ‪ d‬ﺧﻄﺎ ﺑﻪ ﻛﺪﻱ ﺑﺎ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ‪ d+1‬ﻧﻴﺎﺯ ﺩﺍﺭﻳﻢ ﺗﺎ ﮔﻴﺮﻧﺪﻩ ﻣﺘﻮﺟﻪ ﻳﻚ ﻛﺪ ﻧﺎ‬
‫ﻣﻌﺘﺒﺮ ﺷﻮﺩ ‪.‬‬
‫ﻣﺜﺎﻝ ‪ :١‬ﺍﮔﺮ ‪ HD=1‬ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ‪d+1=1‬‬
‫ﻳﻌﻨﻲ ‪ d=0‬ﺍﺳﺖ ﺑﻌﺒﺎﺭﺕ ﺩﻳﮕﺮ ﺧﻄﺎﻳﻲ ﺗﺸﺨﻴﺺ ﺩﺍﺩﻩ ﻧﻤﻲ ﺷﻮﺩ ﻓﺮﺽ ﻛﻨﻴﺪ ﺩﺭ ﺳﻴﺴﺘﻤﻲ ﺑﺎ ‪ HD=1‬ﻛﺪ‬
‫‪ 00000000‬ﻭ ﺑﺪﻧﺒﺎﻝ ﺁﻥ ‪ 00000010‬ﺍﺭﺳﺎﻝ ﻣﻲ ﺷﻮﺩ ﮔﻴﺮﻧﺪﻩ ﻧﻤﻲ ﺗﻮﺍﻧﺪ ﺗﺸﺨﻴﺺ ﺩﻫﺪ ﻛﻪ ﻛﺪ ﺩﻭﻡ ﺩﻳﺘﺎﻱ‬
‫ﻭﺍﻗﻌﻲ ﺍﺳﺖ ﻳﺎ ﻛﺪﻱ ﺍﺳﺖ ﻛﻪ ﺩﺭ ﺁﻥ ﺧﻄﺎ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﺯﻳﺮﺍ ﺩﺭ ﺳﻴﺴﺘﻢ ‪ HD=1‬ﻛﺪ ‪ 00000010‬ﻧﻴﺰ ﺑﻌﻨﻮﺍﻥ‬
‫ﻳﻚ ﻛﺪ ﻣﻌﺘﺒﺮ ﺷﻨﺎﺧﺘﻪ ﻣﻲ ﺷﻮﺩ ‪.‬‬

‫ﻣﺜﺎﻝ ‪ : ٢‬ﺍﮔﺮ ‪ HD=2‬ﺑﺎﺷﺪ ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ‪ d+1=2‬ﻳﻌﻨﻲ ﻳﻚ ﺧﻄﺎ ﻗﺎﺑﻞ ﺗﺸﺨﻴﺺ ﺍﺳﺖ ﻓﺮﺽ ﻛﻨﻴﺪ ﺩﺭ‬
‫ﺳﻴﺴﺘﻤﻲ ﻛﺪ ‪ 00000000‬ﻭ ﺑﺪﻧﺒﺎﻝ ﺁﻥ ‪ 00000110‬ﺍﺭﺳﺎﻝ ﮔﺮﺩﺩ ﻳﻌﻨﻲ ﻓﻘﻂ ﺩﻭ ﺑﻴﺖ ﺩﺭ ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ‬
‫ﻣﺘﻔﺎﻭﺕ ﺍﺳﺖ ﺩﺭ ﺍﻳﻦ ﺣﺎﻟﺖ ﺍﮔﺮ ﺩﺭ ﺍﺛﺮ ﺧﻄﺎ ﻛﺪ ﺩﻭﻡ ﺑﻪ ‪ 00000100‬ﻳﺎ ﺑﻪ ‪ 00000010‬ﺗﺒﺪﻳﻞ ﺷﻮﺩ ﺗﻮﺳﻂ‬
‫ﮔﻴﺮﻧﺪﻩ ﻗﺎﺑﻞ ﺗﺸﺨﻴﺺ ﺍﺳﺖ ﻭﻟﻲ ﺍﮔﺮ ﺩﺭ ﺍﺛﺮ ﺩﻭ ﺧﻄﺎﻱ ﻫﻤﺰﻣﺎﻥ ﻛﺪ ﺩﻭﻡ ﺑﻪ ‪ 00000101‬ﺗﺒﺪﻳﻞ ﺷﻮﺩ ﮔﻴﺮﻧﺪﻩ‬
‫ﺗﺼﻮﺭ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﺷﺮﺍﻳﻂ ﻋﺎﺩﻱ ﺍﺳﺖ ﻭ ﻧﻤﻲ ﺗﻮﺍﻧﺪ ﺧﻄﺎ ﺭﺍ ﺗﺸﺨﻴﺺ ﺑﺪﻫﺪ ﭼﻮﻥ ‪ HD=2‬ﻫﻨﻮﺯ ﻭﺟﻮﺩ ﺩﺍﺭﺩ ‪.‬‬
‫ﺗﺬﻛﺮ ‪:‬‬
‫ﻻ ﺑﺮﺍﻱ ﺗﺸﺨﻴﺺ ﺧﻄﺎﻱ ﺗﻚ ﺑﻴﺘﻲ ﺍﺯ ﺑﻴﺖ ﺗﻮﺍﺯﻥ )‪ ( Parity‬ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﺷﻮﺩ ﺑﻌﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺩﺭ ‪ even parity‬ﻳﺎ‬
‫ﻣﻌﻤﻮ ﹰ‬
‫ﺗﻮﺍﺯﻥ ﺯﻭﺝ ﺍﮔﺮ ﺗﻌﺪﺍﺩ ﻳﻚ ﻫﺎﻱ ﻣﻮﺟﻮﺩ ﺩﺭ ﻛﺪ ﺑﺎ ﺍﺣﺘﺴﺎﺏ ﺑﻴﺖ ﺗﻮﺍﺯﻥ ﺯﻭﺝ ﺑﺎﺷﺪ ﺑﻴﺖ ﺗﻮﺍﺯﻥ ‪ ١‬ﺍﺳﺖ ﻣﺜﺎﻝ‬
‫‪10110101→ 1011010111‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٢٥‬‬ ‫ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫ﺩﺭ ﻏﻴﺮ ﺍﻳﻦ ﺻﻮﺭﺕ ﺑﻴﺖ ﺗﻮﺍﺯﻥ ﺻﻔﺮ ﺍﺳﺖ ‪.‬‬
‫ﺩﺭ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﺑﻴﺖ ﺗﻮﺍﺯﻥ ‪ ،‬ﻓﺎﺻﻠﻪ ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ ‪ HD=2‬ﺧﻮﺍﻫﺪ ﺑﻮﺩ ﺯﻳﺮﺍ ﺍﮔﺮ ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﻳﻜﻲ ﺍﺯ ﻳﻚ ﻫﺎ‬
‫ﺻﻔﺮ ﺷﻮﺩ ﺑﻴﺖ ﺗﻮﺍﺯﻥ ﻧﻴﺰ ﺻﻔﺮ ﺧﻮﺍﻫﺪ ﺷﺪ ﻭ ﺩﻭ ﺑﻴﺖ ﺩﺭ ﻛﺪﻫﺎﻱ ﻣﺘﻮﺍﻟﻲ ﻣﺘﻔﺎﻭﺕ ﺧﻮﺍﻫﺪ ﺑﻮﺩ ‪.‬‬
‫ﺑﻬﺮﺣﺎﻝ ﺍﺯ ﺑﻴﺖ ﺗﻮﺍﺯﻥ ﺑﺮﺍﻱ ﺷﻨﺎﺳﺎﻳﻲ ﺧﻄﺎﻱ ﺗﻚ ﺑﻴﺘﻲ ﺍﺳﺘﻔﺎﺩﻩ ﻣﻲ ﮔﺮﺩﺩ‪.‬‬

‫ﭼﮕﻮﻧﮕﻲ ﺗﺼﺤﻴﺢ ﺧﻄﺎ ﺑﺎ ﺍﺳﺘﻔﺎﺩﻩ ﺍﺯ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ‬

‫ﺑﻄﻮﺭ ﻛﻠﻲ ﺑﺮﺍﻱ ﺗﺼﺤﻴﺢ ‪ d‬ﺧﻄﺎ ﺑﻪ ﻛﺪﻱ ﺑﺎ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ‪ 2d+1‬ﻧﻴﺎﺯ ﺩﺍﺭﻳﻢ ﺯﻳﺮﺍ ﺩﺭ ﺍﻳﻨﺼﻮﺭﺕ ﻓﺎﺻﻠﻪ ﺑﻴﻦ‬
‫ﺩﻭ ﻛﺪ ﻣﺘﻮﺍﻟﻲ ﺁﻧﻘﺪﺭ ﺑﺰﺭﮒ ﺍﺳﺖ ﻛﻪ ﺣﺘﻲ ﺑﺎ ﺗﻐﻴﻴﺮ ‪ d‬ﺧﻄﺎ ﺑﺎﺯ ﻣﻴﺘﻮﺍﻥ ﻛﺪ ﺻﺤﻴﺢ ﺭﺍ ﻣﺸﺨﺺ ﻧﻤﻮﺩ‪.‬‬
‫ﻣﺜﺎﻝ ‪ :‬ﻛﺪﻫﺎﻱ ﺯﻳﺮ ﺭﺍ ﺩﺭ ﻧﻈﺮ ﺑﮕﻴﺮﻳﺪ ﻛﻪ ﺑﺪﻧﺒﺎﻝ ﻫﻢ ﺍﺭﺳﺎﻝ ﻣﻴﺸﻮﻧﺪ ‪:‬‬
‫‪0000000000‬‬
‫‪0000011111‬‬
‫‪1111100000‬‬
‫‪1111111111‬‬

‫ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﻣﻼﺣﻈﻪ ﻣﻲ ﮔﺮﺩﺩ ﻓﺎﺻﻠﻪ ﻫﻤﻴﻨﮓ ﺑﻴﻦ ﺁﻧﻬﺎ ‪ 5‬ﺍﺳﺖ ‪.‬ﭘﺲ ﺑﺮ ﺍﺳﺎﺱ ﺭﺍﺑﻄﻪ‪ 2d+1=5‬ﻣﻴﺘﻮﺍﻥ‬
‫ﺣﺪﺍﻛﺜﺮ ‪ ٢‬ﺧﻄﺎ ﺭﺍ ﺍﺻﻼﺡ ﻧﻤﻮﺩ‪ .‬ﻓﺮﺿﹲﺎ ﺍﮔﺮ ﺑﺎ ﺑﺮﻭﺯ ﺧﻄﺎ ﻛﺪ ‪ 0000000111‬ﺑﺮﺳﺪ ﮔﻴﺮﻧﺪﻩ ﻣﻲ ﻓﻬﻤﺪ ﻛﻪ ﻛﺪ‬
‫ﺍﺻﻠﻲ ﺑﺎﻳﺴﺘﻲ ‪ 0000011111‬ﺑﺎﺷﺪ ﻭ ﺁﻧﺮﺍ ﺍﺻﻼﺡ ﻣﻲ ﻛﻨﺪ ‪.‬‬
‫ﺩﺭ ﻣﺜﺎﻝ ﻓﻮﻕ ﺍﮔﺮ ‪ ٣‬ﺧﻄﺎ ﺭﺥ ﺩﻫﺪ ﮔﻴﺮﻧﺪﻩ ﻧﻤﻴﺘﻮﺍﻧﺪ ﻛﺪ ﺭﺍ ﺑﻄﻮﺭ ﺻﺤﻴﺢ ﺍﺻﻼﺡ ﻛﻨﺪ‪ .‬ﻣﺜﻼ ﺍﮔﺮ ﻛﺪ‬
‫‪ 0000000000‬ﺩﺭ ﺍﺛﺮ ﺑﺮﻭﺯ ‪ ٣‬ﺧﻄﺎ ﺑﻪ ﻛﺪ ‪ 0000000111‬ﺗﺒﺪﻳﻞ ﺷﻮﺩ ﮔﻴﺮﻧﺪﻩ ﻣﺘﻮﺟﻪ ﻭﻗﻮﻉ ﺳﻪ ﺧﻄﺎ ﻧﻤﻴﺸﻮﺩ‬
‫ﺑﻠﻜﻪ ﺷﺒﻴﻪ ﺣﺎﻟﺖ ﻓﻮﻕ ﺑﺎ ﺗﺼﻮﺭ ﺍﻳﻨﻜﻪ ‪ ٢‬ﺧﻄﺎ ﺍﺗﻔﺎﻕ ﺍﻓﺘﺎﺩﻩ ‪،‬ﺁﻧﺮﺍ ﺑﻪ ‪ 0000011111‬ﺗﺼﺤﻴﺢ ﻣﻴﻜﻨﺪ ﻛﻪ ﺩﺭﺳﺖ‬
‫ﻧﻴﺴﺖ‪.‬‬
‫ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ ﺍﻣﻜﺎﻥ ﺍﺷﺘﺒﺎﻩ ﻓﻮﻕ ﻣﻌﻤﻮﻻ ﺗﺮﺟﻴﺢ ﺩﺍﺩﻩ ﻣﻴﺸﻮﺩ ﺗﺎ ﺩﺭ ﺻﻮﺭﺕ ﺗﺸﺨﻴﺺ ﺧﻄﺎ ﺑﺠﺎﻱ ﺗﺼﺤﻴﺢ ﺗﻮﺳﻂ‬
‫ﮔﻴﺮﻧﺪﻩ ‪ ،‬ﺻﺮﻓﹲﺎ ﺑﻪ ﻓﺮﺳﺘﻨﺪﻩ ﺍﻃﻼﻉ ﺩﺍﺩﻩ ﺷﻮﺩ ﺗﺎ ﻣﺠﺪﺩﹲﺍ ﺍﻗﺪﺍﻡ ﺑﻪ ﺍﺭﺳﺎﻝ ﻛﺪ ﻧﻤﺎﻳﺪ‪.‬‬
Techno-Electro.com
‫‪Techno-Electro.com‬‬

‫ﺿﻤﻴﻤﻪ ‪٢‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺑﺮﺧﻲ ﺍﺯ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

‫‪Techno-Electro.com‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬ ‫‪٢٢٨‬‬

‫‪Techno-Electro.com‬‬

‫‪٢٢٩‬‬ ‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

‫‪Techno-Electro.com‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬ ‫‪٢٣٠‬‬

‫‪Techno-Electro.com‬‬

‫‪٢٣١‬‬ ‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

‫‪Techno-Electro.com‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬ ‫‪٢٣٢‬‬

‫‪Techno-Electro.com‬‬

‫‪٢٣٣‬‬ ‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

‫‪Techno-Electro.com‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬ ‫‪٢٣٤‬‬

‫‪Techno-Electro.com‬‬

‫‪٢٣٥‬‬ ‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

‫‪Techno-Electro.com‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬ ‫‪٢٣٦‬‬

‫‪Techno-Electro.com‬‬

‫‪٢٣٧‬‬ ‫ﻣﻘﺎﻳﺴﻪ ﻣﺸﺨﺼﺎﺕ ﺷﺒﻜﻪ ﻫﺎﻱ ﻓﻴﻠﺪﺑﺎﺱ‬

Techno-Electro.com
Techno-Electro.com

٣ ‫ﺿﻤﻴﻤﻪ‬

PROFIBUS ‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺷﺒﻜﻪ‬

‫‪Techno-Electro.com‬‬

‫‪Profibus‬‬ ‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺷﺒﻜﻪ‬ ‫‪٢٤٠‬‬

‫ﻳﻚ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﺗﻨﻬﺎ ﺯﻣﺎﻧﻲ ﺩﺭﺳﺖ ﻛﺎﺭ ﻣﻲ ﻛﻨﺪ ﻛﻪ ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﺑﻪ ﺻﻮﺭﺕ ﻣﻨﺎﺳﺐ ﺗﻌﻴﻴﻦ ﺷﺪﻩ ﺑﺎﺷﻨﺪ‪.‬ﻫﻤﭽﻨﻴﻦ‬
‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﻛﻪ ﺑﺮﺍﻱ ﻳﻚ ‪ Node‬ﺷﺒﻜﻪ ﺗﻌﺮﻳﻒ ﻣﻲ ﺷﻮﻧﺪ ﺑﺎﻳﺪ ﺑﺮﺍﻱ ﻫﻤﻪ ‪ Node‬ﻫﺎﻱ ﺷﺒﻜﻪ ﻳﻜﺴﺎﻥ ﺑﺎﺷﺪ‪.‬‬
‫ﺩﺭ ﺣﺎﻟﺖ ﻛﻠﻲ ﭘﺎﺭﺍﻣﺘﺮ ﻫﺎﻱ ﺑﺎﺱ ﺑﻪ ﻧﺮﺥ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ ﺑﺴﺘﮕﻲ ﺩﺍﺭﻧﺪ‪.‬ﺗﺬﻛﺮ ﺍﻳﻨﻜﻪ ﻧﺤﻮﻩ ﺗﻌﻴﻴﻦ ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮﻫﺎ ﺑﻪ ﺻﻮﺭﺕ‬
‫ﺗﺠﺮﺑﻲ ﺍﺳﺖ ﻭﺍﻛﻴﺪﹰﺍ ﺗﻮﺻﻴﻪ ﻣﻲ ﺷﻮﺩ ﻛﻪ ﺗﻐﻴﻴﺮ ﻣﻘﺎﺩﻳﺮ ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮﻫﺎ ﺗﻮﺳﻂ ﺍﻓﺮﺍﺩ ﺑﺎ ﺗﺠﺮﺑﻪ ﺻﻮﺭﺕ ﮔﻴﺮﺩ‪.‬ﺑﺮﺍﻱ ﺩﻳﺪﻥ‬
‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﻫﻤﺎﻧﻄﻮﺭ ﻛﻪ ﺩﺭ ﻓﺼﻞ ﭼﻬﺎﺭﻡ ﺗﻮﺿﻴﺢ ﺩﺍﺩﻩ ﺷﺪﻩ ﺍﺳﺖ ﺑﺎﻳﺪ ﺩﺭ ﭘﺘﺠﺮﻩ ‪ Network Setting‬ﻣﺮﺑﻮﻁ ﺑﻪ ﺷﺒﻜﻪ‬
‫‪ PROFIBUS‬ﻛﻠﻴﺪ ‪ Bus Parameters‬ﺭﺍﻓﺸﺎﺭ ﺩﻫﻴﺪ ﭘﻨﺠﺮﻩ ﺍﻱ ﻣﺎﻧﻨﺪ ﺷﻜﻞ ﺯﻳﺮ ﻇﺎﻫﺮ ﺧﻮﺍﻫﺪ ﺷﺪ‪:‬‬

‫‪(Time Target Rotation) Ttr‬‬

‫ﻣﺪﺕ ﺯﻣﺎﻧﻲ ﺍﺳﺖ ﻛﻪ ‪ ، Token‬ﺣﻠﻘﻪ ﺭﺍ ﺩﻭﺭ ﻣﻲ ﺯﻧﺪ ﻭﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻫﻤﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ Master‬ﻗﺮﺍﺭ ﮔﻴﺮﺩ‪.‬ﺩﺭ ﻭﺍﻗﻊ ﺩﺭ ﻃﻮﻝ ﺍﻳﻦ‬
‫ﺯﻣﺎﻥ‪ ،‬ﻫﻤﻪ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ ، Master‬ﻳﻚ ﺑﺎﺭ ‪ Token‬ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﻣﻲ ﮔﻴﺮﻧﺪ ﻭ ﺩﺭ ﻧﺘﻴﺠﻪ ﻣﻲ ﺗﻮﺍﻧﻨﺪ ﺑﺎﺱ ﺭﺍ ﺩﺭ ﺍﺧﺘﻴﺎﺭ ﮔﺮﻓﺘﻪ‬
‫ﻭﺗﺒﺎﺩﻝ ﺩﻳﺘﺎ ﺍﻧﺠﺎﻡ ﺩﻫﻨﺪ‪ .‬ﻣﺤﺪﻭﺩﻩ ‪ Ttr‬ﺑﺼﻮﺭﺕ ‪ 256 t_bit <= Ttr <= 16.777.960 t_bit‬ﺍﺳﺖ‪:‬‬
‫ﺍﮔﺮ ﻛﺎﺭﺑﺮ ﺑﺨﻮﺍﻫﺪ ﺩﺳﺘﻲ ﺍﻳﻦ ﭘﺎﺭﺍﻣﺘﺮ ﺭﺍ ﺗﻨﻈﻴﻢ ﻛﻨﺪ ﺑﺎﻳﺪ ﺣﺪﺍﻗﻞ ﺁﻧﺮﺍ ‪ ٥٠٠٠‬ﺑﺮﺍﺑﺮ ﺁﺩﺭﺱ ‪ HSA‬ﻳﻌﻨﻲ ﺑﺎﻻﺗﺮﻳﻦ ﺁﺩﺭﺱ ﺑﺎﺱ‬
‫ﺑﮕﻴﺮﺩ‪.‬ﺁﺩﺭﺱ ‪ HAS‬ﺩﺭ ﭘﻨﺠﺮﻩ ﻗﺒﻞ ﺍﺯ ﭘﻨﺠﺮﻩ ﻓﻮﻕ ﻇﺎﻫﺮ ﻣﻴﮕﺮﺩﺩ‪.‬‬
‫‪Techno-Electro.com‬‬

‫‪٢٤١‬‬ ‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺷﺒﻜﻪ ‪Profibus‬‬

‫‪GAP Factor‬‬
‫ﺑﺎ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ‪ ،‬ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ ‪ Master‬ﺟﺪﻳﺪ‪ .‬ﻣﻤﻜﻦ ﺍﺳﺖ ﻳﻚ ﺣﻠﻘﻪ ﭘﺎﺳﺨﮕﻮﻱ ﺍﺭﺗﺒﺎﻁ ﻣﻮﺭﺩ ﻧﻈﺮ ﻧﺒﺎﺷﺪ ﻭﻧﻴﺎﺯ ﺑﺎﺷﺪ ﻛﻪ‬
‫ﭼﻨﺪﻳﻦ ﺣﻠﻘﻪ ‪ Token‬ﺗﺸﻜﻴﻞ ﺷﻮﺩ‪ GAP Factor .‬ﺩﺭ ﻭﺍﻗﻊ ﺗﻌﺪﺍﺩ ﺣﻠﻘﻪ ﻫﺎﻱ ‪ Token‬ﺭﺍ ﭘﺲ ﺍﺯ ﺍﺿﺎﻓﻪ ﻛﺮﺩﻥ ﺍﻳﺴﺘﮕﺎﻫﻬﺎﻱ‬
‫ﺟﺪﻳﺪ‪،‬ﻧﻤﺎﻳﺶ ﻣﻲ ﺩﻫﺪ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﻋﺪﺩﻱ ﺑﻴﻦ ‪ ١‬ﺗﺎ ‪ ١٠٠‬ﺑﺎﺷﺪ‪.‬‬

‫‪Retry Limit‬‬
‫‪Acknowledge‬‬ ‫ﭘﺲ ﺍﺯ ﺍﻳﻨﻜﻪ ﻳﻚ ﭘﻴﻐﺎﻡ ﺑﻪ ﻃﻮﺭ ﺻﺤﻴﺢ ﺍﺭﺳﺎﻝ ﺷﻮﺩ‪،‬ﮔﻴﺮﻧﺪﻩ ﻳﻚ ﭘﻴﻐﺎﻡ ﻣﻴﺪﻫﺪ ﻭﺍﺻﻄﻼﺣﹰﺎ ﺍﻳﺴﺘﮕﺎﻩ ﮔﻴﺮﻧﺪﻩ‬
‫ﻣﻲ ﺩﻫﺪ‪.‬ﺍﮔﺮ ﭼﻨﺎﻧﭽﻪ ﺑﻪ ﻫﺮ ﺩﻟﻴﻞ ﺍﺭﺳﺎﻝ ﭘﻴﺎﻡ ﺩﭼﺎﺭ ﻣﺸﻜﻞ ﺷﻮﺩ ﻭ‪ Acknowledge‬ﻧﺸﻮﺩ ﻭﻳﺎ ﺯﻣﺎﻥ ‪ Time Out‬ﺳﭙﺮﻱ ﺷﻮﺩ‪،‬ﭘﻴﻐﺎﻡ‬
‫ﻣﺠﺪﺩﹰﺍ ﺍﺭﺳﺎﻝ ﻣﻲ ﺷﻮﺩ‪.‬ﭘﺎﺭﺍﻣﺘﺮ ‪ Retry Limit‬ﺩﺭ ﻭﺍﻗﻊ ﺗﻌﻴﻴﻦ ﻛﻨﻨﺪﻩ ‪ ،‬ﺣﺪﺍﻛﺜﺮ ﺗﻌﺪﺍﺩ ﺗﻜﺮﺍﺭ ﺍﺭﺳﺎﻝ ﭘﻴﺎﻡ ﺍﺳﺖ ﻭ ﻣﻴﺘﻮﺍﻧﺪ ﻋﺪﺩﻱ‬
‫ﺑﻴﻦ ‪ ١‬ﺗﺎ ‪ ١٥‬ﺑﺎﺷﺪ‪.‬‬

‫‪(Minimum Time Station Delay Response) Min-TSDR‬‬

‫ﺣﺪﺍﻗﻞ ﺯﻣﺎﻧﻲ ﺍﺳﺖ ﻛﻪ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﭘﺲ ﺍﺯ ﺩﺭﻳﺎﻓﺖ ﭘﻴﻐﺎﻡ ﺑﺎﻳﺪ ﻣﻨﺘﻈﺮ ﺑﻤﺎﻧﺪ ﻭﭘﺲ ﺍﺯﺁﻥ ﺑﻪ ﺁﻥ ﭘﺎﺳﺦ ﺩﻫﺪ‪.‬‬
‫)‪1 t_bit <= Min. Tsdr <= MIN(255 t_bit, ...... Max. Tsdr - 1, 34 + 2*Tset + Tqui‬‬

‫‪Max. TSDR‬‬
‫ﺣﺪﺍﻛﺜﺮ ﺯﻣﺎﻧﻲ ﺍﺳﺖ ﻛﻪ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﻣﻲ ﺗﻮﺍﻧﺪ ﺑﻪ ﻳﻚ ﭘﻴﻐﺎﻡ ‪،‬ﭘﺎﺳﺦ ﺩﻫﺪ‪.‬‬
‫‪٣٥ + ٢*Tset + Tqui <= Max. Tsdr <= 1.023 t_bit‬‬

‫‪(Slot Time) Tslot‬‬

‫ﺣﺪﺍﻛﺜﺮ ﺯﻣﺎﻧﻲ ﺍﺳﺖ ﻛﻪ ﻳﻚ ﻓﺮﺳﺘﻨﺪﻩ ﻣﻲ ﺗﻮﺍﻧﺪ ﻣﻨﺘﻈﺮ ﭘﺎﺳﺦ ﮔﻴﺮﻧﺪﻩ ﺑﺎﺷﺪ‪.‬‬

‫‪(Setup Time)Test‬‬
‫ﻣﺪﺕ ﺯﻣﺎﻧﻲ ﻛﻪ ﺑﻴﻦ ﺩﺭﻳﺎﻓﺖ ﻳﻚ ﭘﻴﻐﺎﻡ ﻭﭘﺎﺳﺦ ﺑﻪ ﺍﻥ ﻃﻮﻝ ﻣﻲ ﻛﺸﺪ‪.‬‬
‫‪1 t_bit <= Tset <= 494 t_bit‬‬

‫‪(Quiet Time) Tqui‬‬

‫ﻣﺪﺕ ﺯﻣﺎﻧﻲ ﻛﻪ ﻃﻮﻝ ﻣﻲ ﻛﺸﺪ ﺗﺎ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﺍﺯ ﺣﺎﻟﺖ ﻓﺮﺳﺘﻨﺪﻩ ﺑﻪ ﮔﻴﺮﻧﺪﻩ ﺗﻐﻴﻴﺮ ﻭﺿﻌﻴﺖ ﺩﻫﺪ‪.‬‬
‫)‪0 t_bit <= Tqui <= MIN(31 t_bit, Min. Tsdr - 1‬‬
‫‪(Idle Time 1) Tid1‬‬
‫ﺣﺪﺍﻗﻞ ﺯﻣﺎﻧﻲ ﻛﻪ ﻃﻮﻝ ﻣﻲ ﻛﺸﺪ ﺗﺎ ﻳﻚ ﺍﻳﺴﺘﮕﺎﻩ ﻓﺮﺳﺘﻨﺪﻩ‪ ،‬ﭘﺲ ﺍﺯ ﺩﺭﻳﺎﻓﺖ ﭘﺎﺳﺦ ‪،‬ﻣﺠﺪﺩﹰﺍ ﭘﻴﻐﺎﻡ ﺟﺪﻳﺪ ﺍﺭﺳﺎﻝ ﻛﻨﺪ‪.‬‬
‫‪Tid1 = 35 + 2*Tset + Tqui‬‬
‫‪Techno-Electro.com‬‬

‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺷﺒﻜﻪ ‪Profibus‬‬ ‫‪٢٤٢‬‬

‫‪(Idle Time 2) Tid2‬‬

‫ﺍﮔﺮ ﭘﺲ ﺍﺯ ﺍﺭﺳﺎﻝ ﻳﻚ ﭘﻴﺎﻡ‪ Acknowledge،‬ﺷﺪ ﻭﭘﺎﺳﺨﻲ ﺩﺭﻳﺎﻓﺖ ﻧﺸﺪ ﺍﻳﺴﺘﮕﺎﻩ ﻓﺮﺳﺘﻨﺪﻩ ﻳﻚ ﻣﺪﺕ ﺯﻣﺎﻥ ﺑﺎﻳﺪ ﺻﺒﺮ ﻛﻨﺪ‬
‫ﺳﭙﺲ ﭘﻴﻐﺎﻡ ﺑﻌﺪﻱ ﺭﺍ ﺍﺭﺳﺎﻝ ﻛﻨﺪ‪،‬ﺑﻪ ﺍﻳﻦ ﺯﻣﺎﻥ ‪ Tid2‬ﮔﻔﺘﻪ ﻣﻲ ﺷﻮﺩ‪.‬‬
‫‪Tid2 = Max. Tsdr‬‬

‫‪(Ready Time)Trdy‬‬
‫ﺣﺪﺍﻗﻞ ﺯﻣﺎﻧﻲ ﻛﻪ ﺑﺎﻳﺪ ﺑﮕﺬﺭﺩ ﺗﺎ ﺑﻌﺪ ﺍﺯ ﺍﺭﺳﺎﻝ ﻳﻚ ﭘﻴﺎﻡ ‪،‬ﻓﺮﺳﺘﻨﺪﻩ ﺑﺘﻮﺍﻧﺪ ﭘﺎﺳﺦ ﺭﺍ ﺩﺭﻳﺎﻓﺖ ﻛﻨﺪ ‪Trdy = Min. Tsdr‬‬

‫ﺩﺭ ﺗﻌﺎﺭﻳﻒ ﻓﻮﻕ ﻣﻨﻈﻮﺭ ﺍﺯ ﺩﺭﻳﺎﻓﺖ ﭘﺎﺳﺦ ‪ Acknowledge،‬ﺷﺪﻥ ﭘﻴﻐﺎﻡ ﺍﺭﺳﺎﻟﻲ ﺍﺳﺖ‪.‬‬
‫‪(Time-Blt) tBIT‬‬ ‫ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﻓﻮﻕ ﺩﻗﻴﻘﹰﺎ ﺑﺎﻳﺪ ﺍﺯ ﺳﻮﻱ ﺗﻤﺎﻣﻲ ‪ Node‬ﻫﺎ‪ ،‬ﺭﻋﺎﻳﺖ ﺷﻮﻧﺪ ‪.‬ﭘﺎﺭﺍﻣﺘﺮﻫﺎﻱ ﺑﺎﺱ ﻫﻤﮕﻲ ﺑﺮﺣﺴﺐ‬
‫ﻣﻌﻴﻦ ﻣﻲ ﺷﻮﻧﺪ‪ .‬ﻳﻚ ‪ tBIT‬ﺯﻣﺎﻥ ﭼﺮﺧﺶ ﻳﻚ ﺑﻴﺖ ﺩﺭ ﺷﺒﻜﻪ ﺍﺳﺖ ﻭﺑﻪ ﺻﻮﺭﺕ ﺯﻳﺮ ﻣﺤﺎﺳﺒﻪ ﻣﻲ ﺷﻮﺩ‪:‬‬
‫)‪ (Bit/s‬ﻧﺮﺥ ﺍﺭﺳﺎﻝ ﺍﻃﻼﻋﺎﺕ‪TBIT=1/‬‬

‫ﻳﺎ‬
‫‪TBIT (µsec) = 1/Mbps‬‬
‫ﺑﻪ ﻋﻨﻮﺍﻥ ﻣﺜﺎﻝ ﺍﮔﺮ ﻧﺮﺥ ﺍﺭﺳﺎﻝ ‪ 12Mbps‬ﺑﺎﺷﺪ‪،‬ﺑﺮﺍﺑﺮ‪ 83ns‬ﻭﺍﮔﺮ ﻧﺮﺥ ﺍﺭﺳﺎﻝ ‪ 1/5Mbps‬ﺑﺎﺷﺪ ‪ tBIT ،‬ﺑﺮﺍﺑﺮ‪ 667ns‬ﻣﻲ ﺑﺎﺷﺪ‪.‬‬

‫ﺗﺬﻛﺮ‪:‬‬
‫ﺩﺭ ﻗﺴﻤﺖ ﺑﺎﻻﻱ ﭘﻨﺠﺮﻩ ‪ Bus Parameters‬ﻳﻚ ﮔﺰﻳﻨﻪ ﺑﻪ ﻧﺎﻡ‬
‫‪Turn on cyclic distribution of the bus parameters‬‬
‫ﺑﻪ ﺻﻮﺭﺕ ‪ Cyclic‬ﺗﻮﺳﻂ ﺗﻤﺎﻡ‬ ‫ﻣﺠﻤﻮﻋﻪ ﺗﻨﻈﻴﻤﺎﺕ ﺍﻧﺠﺎﻡ ﺷﺪﻩ ﺑﺮﺍﻱ ‪ Subnet‬ﻣﻮﺭﺩ ﻧﻈﺮ‬ ‫ﻭﺟﻮﺩ ﺩﺍﺭﺩ ﻛﻪ ﺍﮔﺮ ﻓﻌﺎﻝ ﺷﻮﺩ‬
‫ﺍﺭﺗﺒﺎﻃﺎﺕ ‪ DP‬ﻓﻌﺎﻝ ﺩﺭ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻣﻨﺘﻘﻞ ﻣﻲ ﺷﻮﺩ‪.‬ﺯﻣﺎﻧﻲ ﺍﻳﻦ ﮔﺰﻳﻨﻪ ﺭﺍ ﻓﻌﺎﻝ ﻛﻨﻴﺪ ﻛﻪ ﻣﺮﺗﺒﹰﺎ ﻣﻲ ﺧﻮﺍﻫﻴﺪ ﻳﻚ ﻭﺍﺣﺪ‬
‫‪ PG‬ﺑﻪ ﺷﺒﻜﻪ ‪ PROFIBUS‬ﻛﻪ ﺩﺭ ﺣﺎﻝ ﻛﺎﺭ ﺍﺳﺖ ﻭﺻﻞ ﻛﻨﻴﺪ ‪.‬‬
‫‪Techno-Electro.com‬‬

‫ﺿﻤﻴﻤﻪ ‪٤‬‬

‫ﻣﻘﺎﻳﺴﻪ ﻓﺮﻣﺖ ﺩﻳﺘﺎ ﺩﺭ ‪ S7‬ﻭ ‪FMS‬‬

Techno-Electro.com

FMS ‫ ﻭ‬S7 ‫ﻣﻘﺎﻳﺴﻪ ﻓﺮﻣﺖ ﺩﻳﺘﺎ ﺩﺭ‬ ٢٤٤

Convert Data Type Bit Number of Range of Values

Length
> Bytes
S7 Type FMS PDU S7 in FMS PDU S7 FMS
BOOL Boolean 1 1 0,1 0x00, 0xff
2)
BYTE Unsigned8 8 1 every 8-bit string
WORD Unsigned16 2) 16 2 every 16-bit string
DWORD Unsigned32 2) 32 4 every 32-bit string
CHAR Octet string[1] 8 1 see ISO 646 and ISO 2375:
Defining registration
number 2 + SPACE
ARRAY Octet [n+1]*8 n+1 see ISO 646 and ISO 2375:
[x..x+n] OF string[n+1] Defining registration
CHAR 0<=n<=236 number 2 + SPACE
INT Integer16 16 2 –215..215–1
DINT Integer32 32 4 –231..231–1
REAL Floating-point 32 4 see IEEE Stand. 754
32
TIME Time 32 4 see 0..2 –1 ms
difference IEC 1131 IS and
DATE Octet string[2] 16 2 see see
IEC 1131 IS EN 50132
28
TIME_OF_ Time-of-day 32 4 or 6 see 0..2 –1ms
DAY or TOD IEC 1131 IS
S5TIME Octet string[2] 16 2 See IEC 1131 IS
28
DATE_AND Date 64 7 see 0..2 –1 ms
_TIME or DT IEC 1131 IS or0..216–1
days
STRING[n] Visible 8n n see
(where string[n] IEC 1131 IS
0<n<=237)
Timer Octet string[2] 16 2 0 to 65535
Counter Octet string[2] 16 2 0 to 65535
‫‪Techno-Electro.com‬‬

‫ﺿﻤﻴﻤﻪ ‪٥‬‬

‫ﻛﺪ ﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ ‪FMS‬‬

Techno-Electro.com

FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬ ٢٤٦

Error-Free Job Execution

Meaning STATUS ERROR DONE/NDR

Job completed without errors 0x0000 0 1

Job active 0x000B 0 0

Error Classes
Meaning Error Class
Indicates errors or problems involving the following: S FB parameter Block
assignment S Block execution in the CPU and CP
Indicates errors or problems on the interface between the user program and
Application
FB.
Definition
Indicates errors that usually involve inconsistencies between the user program
and FMS configuration

Indicates resource problems on the PROFIBUS CP. Resources

Indicates errors or problems in conjunction with the requested FMS service. Service

Indicates denied access to objects due to the following: S Absence of access Access
rights S Hardware problems S Other inconsistencies

Indicates problems accessing the object dictionary of the VFD.

OD (object
dictionary)

Unspecified error on the VFD VFD status

Other errors Other

Locally Detected Errors

Meaning STATUS ERROR DONE/NDR

Communications problem: 0x0001 1 0

For example K bus connection not established.

Function cannot be executed: either negative 0x0002 1 0

acknowledgment by the CP or error in the sequence,
for example K bus protocol error.

The connection is not configured (invalid ID specified). 0x0003 1 0

If the connection is configured, the error message
indicates that the permitted parallel job processing
limit has been exceeded. Example SAC=0 is
configured and a REPORT job is sent.
Techno-Electro.com

٢٤٧ FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬

The receive data area is too short or the data types do 0x0004 1 0
not match.

A reset request has been received from the CP (BRCV). 0x0005 1 0

The corresponding job execution on the CP is in the 0x0006 1 0

DISABLED state or a reset request has been received
from the CP; the transfer is therefore incomplete.

Corresponding job execution on the CP is in the 0x0007 1 0

wrong state.
With REPORT: the error is specified in greater detail in
the diagnostic buffer.

Job execution on the CP signals an error accessing 0x0008 1 0

the user memory.

Communications problem: 0x0001 1 0

For example K bus connection not established.

Function cannot be executed: either negative 0x0002 1 0

acknowledgment by the CP or error in the sequence,
for example K bus protocol error.

The connection is not configured (invalid ID specified). 0x0003 1 0

If the connection is configured, the error message
indicates that the permitted parallel job processing
limit has been exceeded. Example SAC=0 is
configured and a REPORT job is sent.

The receive data area is too short or the data types do 0x0004 1 0
not match.

A reset request has been received from the CP 0x0005 1 0

(BRCV).

The corresponding job execution on the CP is in the 0x0006 1 0

DISABLED state or a reset request has been received
from the CP; the transfer is therefore incomplete.

Corresponding job execution on the CP is in the 0x0007 1 0

wrong state.
With REPORT: the error is specified in greater detail in
the diagnostic buffer.

Job execution on the CP signals an error accessing 0x0008 1 0

the user memory.
Techno-Electro.com

FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬ ٢٤٨

Application Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified application reference error. 0x0200 1 0

The configured connection cannot be 0x0201 1 0

established at present; for example LAN
connection not established.
Definition Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified definition 0x0300 1 0
error.
Object with requested
index/name is not 0x0301 1 0
defined.
Object attributes are
0x0302 1 0
inconsistent.
Name exists already. 0x0303 1 0

Resources Error Class

Meaning STATUS ERROR DONE/NDR
Unspecified resource 0x0400 1 0
error.
No memory available. 0x0401 1 0

Resources Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified resource 0x0400 1 0
error.
No memory available. 0x0401 1 0
Techno-Electro.com

٢٤٩ FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬

Service Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified service 0x0500 1 0
error.
Conflict due to object
0x0501 1 0
status.
Configured PDU size
0x0502 1 0
exceeded.
Conflict due to object
0x0503 1 0
restrictions.
Inconsistent
0x0504 1 0
parameters.
Illegal parameters. 0x0505 1 0

Access Error Class

Meaning STATUS ERROR DONE/NDR
Unspecified access 0x0600 1 0
error.
Invalid object. 0x0601 1 0

Hardware error. 0x0602 1 0

Object access was
0x0603 1 0
denied.
Invalid address. 0x0604 1 0
Inconsistent object
0x0605 1 0
attributes.
Object access not
0x0606 1 0
supported.
Object does not exist in
OD or GetOD still 0x0607 1 0
active
Type conflict or 0x0608 1 0
variable content
outside permitted
range of values
Access using names
0x0609 1 0
not supported.
Techno-Electro.com

FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬ ٢٥٠

Object Dictionary (OD) Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified OD error. 0x0700 1 0

Permitted name length

0x0701 1 0
exceeded.
Overflow of the object
0x0702 1 0
dictionary.
Object dictionary is write
0x0703 1 0
protected.
Overflow of the extension 0x0704 1 0
length.
Overflow of the object
0x0705 1 0
description length.
Processing problem. 0x0706 1 0

VFD–Status/Reject Error Class, continued

Meaning STATUS ERROR DONE/NDR

Unspecified VFD status 0x0100 1 0
error.
RCC/SAC/RAC error 0x0108 1 0

Service not supported. 0x0106 1 0

PDU length error 0x0105 1 0

Bad FMS-PDU 0x0102 1 0

16 Application Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified error. 0x0800 1 0

Unspecified application reference error. 0x8200 1 0

0x8201 1 0
Application (for example user program) not
obtainable.
Techno-Electro.com

٢٥١ FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬

Definition Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified definition 0x8300 1 0
error.
Object with requested
0x8301 1 0
index/name is not defined.
Object attributes are
0x8302 1 0
inconsistent.
Name exists already. 0x8303 1 0

Resources Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified resource 0x8400 1 0
error.
No memory available. 0x8401 1 0

Service Error Class

Meaning STATUS ERROR DONE/NDR

Unspecified service error. 0x8500 1 0

Conflict due to object

0x8501 1 0
status.
Configured PDU size
0x8502 1 0
exceeded.
Conflict due to object
0x8503 1 0
restrictions.
Inconsistent parameters. 0x8504 1 0

Illegal parameters. 0x8505 1 0

Access Error Class

Meaning STATUS ERROR DONE/NDR
Unspecified access error. 0x8600 1 0

Invalid object. 0x8601 1 0

Hardware error. 0x8602 1 0

Object access was
0x8603 1 0
denied.
Techno-Electro.com

FMS ‫ﻛﺪﻫﺎﻱ ﺧﻄﺎ ﺩﺭ ﺍﺭﺗﺒﺎﻁ‬ ٢٥٢

Access Error Class, continued

Meaning STATUS ERROR DONE/NDR
Invalid address. 0x8604 1 0

Inconsistent object
0x8605 1 0
attributes.
Object access is not
0x8606 1 0
supported.
Object does not exist. 0x8607 1 0

Type conflict or variable 0x8608 1 0

content outside permitted
range of values
Access using names is
0x8609 1 0
not supported.

OD (Object Dictionary) Error Class

Meaning STATUS ERROR DONE/NDR
Unspecified OD error. 0x8700 1 0

Permitted name length

0x8701 1 0
exceeded.
Overflow of the object
0x8702 1 0
dictionary.
Object dictionary is write
0x8703 1 0
protected.
Overflow of the extension
0x8704 1 0
length.
Overflow of the object
0x8705 1 0
description length.
Processing problem. 0x8706 1 0

VFD Status Error Class

Meaning STATUS ERROR DONE/NDR
Unspecified VFD status 0x8100 1 0
error.

Other Error Class

Meaning STATUS ERROR DONE/NDR
Unspecified error 0x8000 1 0
detected by partner.
Techno-Electro.com

‫ﻛﻠﻤﺎﺕ ﺍﺧﺘﺼﺎﺭﻱ‬
Techno-Electro.com

‫ﻛﻠﻤﺎﺕ ﺍﺧﺘﺼﺎﺭﻱ‬ ٢٥٤

ASI Actuator Sensor Interface

BPS Bits Per Second
BRCT Broadcast
CP Communication Processor
CRC Cyclic Redundancy Check
CSMA Carrier Sense Multiple Access
CSMA/CA Carrier Sense Multiple Access with Collision Avoidance
CSMA/CD Carrier Sense Multiple Access with Collision Detection
DAE Destination with Address Extension
DDLM Direct Data Link Mapper
DP Decentralized Peripheral (Distributed Peripheral)
DPM1 DP Master Class1
DPM2 DP Master Class2
DSAP Destination SAP
EDD Electronic Device Description
EIA Electronic Industries Association
ERP Enterprise Resource Planing
ET Electronic Terminal
FCS Frame Check Sequence
FDL Fieldbus Data Link
FDT Field Device Tool
FDX Full Duplex
FISCO Fieldbus Intrinsically Safe Concept
FMA Fieldbus Management
FMS Field Message Specification
Gbps Gigabits Per Second
GSD General Station Data
HAS High Station Address
HDLC High Level Data Link Control
HDX Half Duplex
Techno-Electro.com

٢٥٥ ‫ﻛﻠﻤﺎﺕ ﺍﺧﺘﺼﺎﺭﻱ‬

IE Industrial Ethernet
IEC International electro-technical Commission
IEEE Institute Of Electrical And Electronics Engineers
ILM Infrared Linking Module
IP Internet Protocol
ISDL Integrated Services Digital Network
ISO International Organization for Standardization
Kbps Kilobits Per Second
LAN Local Area Network
LSAP Link Service Access Point
MAC Media Access Control
MAN Metropolitan Area Network
MBP Manchester coded Bus Powered
Mbps Megabits Per Second
MMAC Master Master Acyclic Connection
MPI Multipoint Interface
MSAC Master Slave Acyclic Connection
MSAC-SI Master Slave Acyclic Connection with Slave Initiative
MSCY Master Slave Cyclic Connection without Slave Initiative
OBT Optical Bus Terminal
OLM Optical Linking Module
OLP Optical Link Plug
OSI Open System Interconnection
OTDR Optical Time Domain Reflectometer
PA Process Automation
PDU Protocol Data Unit
PI Profibus International
PNO Profibus Neutzer Organization
Profibus Process FieldBus
PTP Point To Point
Techno-Electro.com

‫ﻛﻠﻤﺎﺕ ﺍﺧﺘﺼﺎﺭﻱ‬ ٢٥٦

SAE Source with Address Extension

SAP Service Access Point
SDA Send Data with Acknowledge
SDLC Synchronous Data Link Control
SDN Send Data with No Acknowledge
SRD Send and Request Data
SSAP Source SAP
STP Shielded Twisted Pair
TCP/IP Transmission Control Protocol/Internet Protocol
TSAP Transport Service Access Point
UART Universal Asynchronous Receiver/Transmitter
UTP Unshielded Twisted Pair
VFD Virtual Field Device
VPN Virtual Private Network
WAN Wide Area Network
WLAN Wireless Local Area Network
Techno-Electro.com

‫ﻣﻨﺎﺑﻊ ﻭ ﻣﺮﺍﺟﻊ‬
Techno-Electro.com

‫ﻣﻨﺎﺑﻊ ﻭ ﻣﺮﺍﺟﻊ‬ ٢٥٨

1. Decentralization with Profibus DP/DPV1 By: Josef Weigman& Gerhard Kilian

2. Profibus Specification Profibus Neutzer Organization

3. Profibus Technology and Application Profibus International

4. Profibus for Process Automation Profibus International

5. Communicatin Networks Samson

6. Serial Data Transmission Samson

7. Profibus PA Samson

8. Industrial Networks for Communication and Control S. Djiev

9. Fieldbus Overview Brad Harrison

10. Network Fundamentals Chuong Huynh

11. Industrial Communication Gustaf Olsson

12. Standard Fieldbuses H. Kirrmann

13. Field Bus: principles H. Kirrmann

14. Field Bus Operation H. Kirrmann

15. OSI model H. Kirrmann

16. Comparison Of Substation Network Topologies ABB

17. Profibus Network2000 Siemens

18. NCM for Profibus Primer Siemens

19. NCM for Profibus Vol 1 & Vol 2 Siemens

20. Configuring Hardware with Step7 Siemens

21. Communication with Simatic Siemens

22. Profibus Diagnostic & Troubleshooting Siemens

23. Profibus Workshop Siemens

24. Network Solution for Profibus Siemens

25. ‫ﺷﺒﮑﻪ هﺎى ﮐﺎﻣﭙﻴﻮﺗﺮى‬ Andrew S. Tanenbaum

‫ ﻋﻴﻦ اﻟﻪ ﺟﻌﻔﺮ ﻧﮋاد‬: ‫ﺗﺮﺟﻤﻪ‬
Techno-Electro.com