Ȩ > Ç¥ÁØÈ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ
Ç¥ÁعøÈ£ | [ÆóÁö] TTAK.OT-10.0209 | ±¸Ç¥ÁعøÈ£ | |
---|---|---|---|
Á¦°³Á¤ÀÏ | 2008-12-19 | ÃÑÆäÀÌÁö | 62 |
ÇѱÛÇ¥Áظí | ·Îº¿ Ŭ¶óÀ̾ðÆ® °ü¸® | ||
¿µ¹®Ç¥Áظí | The Management of Robot Clients | ||
Çѱ۳»¿ë¿ä¾à | º» Ç¥ÁØÀº URC ·Îº¿À» ¿ø°Ý°ü¸®Çϱâ À§ÇÑ °øÅë °ü¸® Ç׸ñÀ» Á¤ÀÇÇϸç, »óÀÌÇÑ Ç÷§ÆûÀ» °¡Áø URC ·Îº¿ ÀåÄ¡¿¡ ÀÀ¿ë ÇÁ·Î±×·¥ÀÇ ÀÇÁ¸¼ºÀ» ÃÖ¼ÒÈÇÏ°í Ç÷§Æû°£ÀÇ À̽ļºÀ» Çâ»ó½ÃÅ°±â À§ÇÑ ÀåÄ¡ Á¢±Ù¿¡ ´ëÇÑ °øÅëµÈ ÀÎÅÍÆäÀ̽º (API) Áß ¿ø°Ý Áø´Ü¿¡ °üÇÑ ºÎºÐÀ» Á¦½ÃÇÑ´Ù. | ||
¿µ¹®³»¿ë¿ä¾à | We don¡¯t guarantee URC Servers compatibility only standard communication protocol between robot clients because of the various robot client connection procedures and different robot profile information. So, this documents regard as standardization of the robot client connection and profiling. We would expect difficult work to develop and adapt standard managing specification if each company will defines different managing item. So, we would define common managing item to remote control robots and minimizes dependability of the application program as URC robot devices. We suggest remote diagonosis common interface (API) regard to device access to compatibility implementation as multiple platforms. | ||
±¹Á¦Ç¥ÁØ | |||
°ü·ÃÆÄÀÏ | TTAK.OT-10.0209.zip |