喜歡就充值下載吧。。資源目錄里展示的文件全都有，，請放心下載，，有疑問咨詢QQ:414951605或者1304139763 ======================== 喜歡就充值下載吧。。資源目錄里展示的文件全都有，，請放心下載，，有疑問咨詢QQ:414951605或者1304139763 ======================== 1 畢業(yè)設(shè)計（論文）任務(wù)書 系 部 機(jī)械工程系 指導(dǎo)教師 謝衛(wèi)容 職 稱 學(xué)生姓名 張安懷 專業(yè)班級 05機(jī)制（1）班 學(xué) 號 0515011127 設(shè)計題目 關(guān)節(jié)型機(jī)械手設(shè)計 設(shè) 計 內(nèi) 容 目 標(biāo) 和 要 求 （設(shè)計內(nèi)容目標(biāo)和要求、設(shè)計進(jìn)度等） 內(nèi)容： 1、關(guān)節(jié)型機(jī)械手的總體結(jié)構(gòu)設(shè)計 2、機(jī)械手各關(guān)節(jié)傳動系統(tǒng)設(shè)計 3、機(jī)械手控制系統(tǒng)設(shè)計 4、繪制裝配圖，零件圖，以及傳動和控制系統(tǒng)原理圖 要求： 1、收集資料（相關(guān)書籍5本以上，文章10篇以上）； 2、繪制零件圖，裝配圖，原理圖； 3、撰寫論文要符合要求； 4、翻譯3000字左右的英文文章一篇 進(jìn)度： 1、1-6周，主要進(jìn)行畢業(yè)設(shè)計準(zhǔn)備工作，熟悉題目，收集資料，進(jìn)行畢業(yè)實(shí)習(xí)，明確研究目的和任務(wù)，構(gòu)思總體方案； 2、7-10周，繪制相關(guān)的圖； 3、11-13周，收尾完善，編寫畢業(yè)設(shè)計論文，準(zhǔn)備畢業(yè)設(shè)計答辯。 指導(dǎo)教師簽名：謝衛(wèi)容 年 月 日 系 部審 核 此表由指導(dǎo)教師填寫 由所在系部審核 2-1 畢業(yè)設(shè)計（論文）學(xué)生開題報告 課題名稱 關(guān)節(jié)型機(jī)械手設(shè)計 課題來源 生產(chǎn)實(shí)踐 課題類型 AX 指導(dǎo)教師 謝衛(wèi)容 學(xué)生姓名 張安懷 學(xué) 號 0515011127 專業(yè)班級 05機(jī)制（1）班 本課題的研究現(xiàn)狀、研究目的及意義 本課題的研究現(xiàn)狀、研究目的及意義 研究現(xiàn)狀： 機(jī)械手是近幾十年發(fā)展起來的一種高科技自動化生產(chǎn)設(shè)備。它的特點(diǎn)是可通過編程來完成各種預(yù)期的作業(yè)任務(wù)，在構(gòu)造和性能上兼有人和機(jī)器各自的優(yōu)點(diǎn)，尤其體現(xiàn)了人的智能和適應(yīng)性。機(jī)械手作業(yè)的準(zhǔn)確性和各種環(huán)境中完成作業(yè)的能力，在國民經(jīng)濟(jì)各領(lǐng)域有著廣闊的發(fā)展前景。 我國國家標(biāo)準(zhǔn)(GB/T 12643-90)對機(jī)械手的定義:“具有和人手臂相似的動作功能，可在空間抓放物體，或進(jìn)行其它操作的機(jī)械裝置?！睓C(jī)械手可分為專用機(jī)械手和通用機(jī)械手兩大類。專用機(jī)械手:它作為整機(jī)的附屬部分，動作簡單，工作對象單一，具有固定(有時可調(diào))程序，使用大批量的自動生產(chǎn)。如自動生產(chǎn)線上的上料機(jī)械手，自動換刀機(jī)械手，裝配焊接機(jī)械手等裝置。通用機(jī)械手:它是一種具有獨(dú)立的控制系統(tǒng)、程序可變、動作靈活多樣的機(jī)械手。它適用于可變換生產(chǎn)品種的中小批量自動化生產(chǎn)。它的工作范圍大，定位精度高，通用性強(qiáng)，廣泛應(yīng)用于柔性自動線。 機(jī)械手最早應(yīng)用在汽車制造工業(yè)，常用于焊接、噴漆、上下料和搬運(yùn)。機(jī)械手延伸和擴(kuò)大了人的手足和大腦功能，它可替代人從事危險、有害、有毒、低溫和高熱等惡劣環(huán)境中的工作;代替人完成繁重、單調(diào)重復(fù)勞動，提高勞動生產(chǎn)率，保證產(chǎn)品質(zhì)量。目前主要應(yīng)用于制造業(yè)中，特別是電器制造、汽車制造、塑料加工、通用機(jī)械制造及金屬加工等工業(yè)。機(jī)械手與數(shù)控加工中心，自動搬運(yùn)小車與自動檢測系統(tǒng)可組成柔性制造系統(tǒng)(FMS )和計算機(jī)集成制造系統(tǒng)(CIMS )，實(shí)現(xiàn)生產(chǎn)自動化。隨著生產(chǎn)的發(fā)展，功能和性能的不斷改善和提高，機(jī)械手的應(yīng)用領(lǐng)域日益擴(kuò)大。 研究目的及意義： 工業(yè)機(jī)械手具有許多人類無法比擬的優(yōu)點(diǎn)，滿足了社會化大生產(chǎn)的需要，其主要優(yōu)點(diǎn)如下： 1.能代替人從事危險、有害的操作。只要根據(jù)工作環(huán)境進(jìn)行合理設(shè)計，選擇適當(dāng)?shù)牟牧虾徒Y(jié)構(gòu)，機(jī)械手就可以在異常高溫或低溫、異常壓力和有害氣體、粉塵、放射線作用下，以及沖壓、滅火等危險環(huán)境中勝任工作。工傷事故多的工種，如沖壓、壓鑄、熱處理、鍛造、噴漆以及有強(qiáng)烈紫外線照射的電弧焊等作業(yè)中，應(yīng)推廣工業(yè)機(jī)械手或機(jī)器人。 2.能長時間工作，不怕疲勞，可以把人從繁重單調(diào)的勞動中解放出來，并能擴(kuò)大和延伸人的功能。人在連續(xù)工作幾小時后，總會感到疲勞或厭倦，而機(jī)械手只要注意維護(hù)、檢修，即能勝任長時間的單調(diào)重復(fù)勞動。 3.動作準(zhǔn)確，因此可以穩(wěn)定和提高產(chǎn)品的質(zhì)量，同時又可避免人為的操作錯誤。 4.機(jī)械手特別是通用工業(yè)機(jī)械手的通用性、靈活性好，能較好地適應(yīng)產(chǎn)品品種的不斷變化，以滿足柔性生產(chǎn)的需要。 5.機(jī)械手能明顯地提高勞動生產(chǎn)率和降低成本。 由于機(jī)械手在工業(yè)自動化和信息化中發(fā)揮了以上巨大的作用，世界各國都很重視工業(yè)機(jī)械手的應(yīng)用和發(fā)展，機(jī)械手的應(yīng)用在我過還屬于起步階段，就顯示出了許多的無法替代的優(yōu)點(diǎn)，展現(xiàn)了廣闊的應(yīng)用前景。近十幾年來，機(jī)械手的開發(fā)不僅越來越優(yōu)化，而且涵蓋了許多領(lǐng)域，應(yīng)用的范疇十分廣闊。 關(guān)節(jié)型機(jī)械手占用空間小，工作范圍大，慣性小，所需動力小，能抓取底面物體，并且還可以繞障礙物選擇途徑，所以關(guān)節(jié)型機(jī)械手的研究具有很重要的意義。 課題類型： （1）A—工程實(shí)踐型；B—理論研究型；C—科研裝置研制型；D—計算機(jī)軟件型； E—綜合應(yīng)用型 （2）X—真實(shí)課題；Y—模擬課題； （1）、（2）均要填，如AY、BX等。 2-2 本課題的研究內(nèi)容 1) 擬定整體方案，特別是傳感器、控制方式與機(jī)械本體的有機(jī)結(jié)合的設(shè)計方案。 2) 根據(jù)給定的自由度和技術(shù)參數(shù)選擇合適的手部、腕部和機(jī)身的結(jié)構(gòu)。 3) 各部件的設(shè)計計算。 4) 工業(yè)機(jī)械手工作裝配圖的設(shè)計與繪制。 5) 液壓系統(tǒng)圖的設(shè)計與繪制。 6) 電器控制圖（）的繪制。 7) 編寫設(shè)計計算說明書。 本課題研究的實(shí)施方案、進(jìn)度安排 實(shí)施方案： 收集資料，擬定整體結(jié)構(gòu)設(shè)計，根據(jù)給定的自由度和技術(shù)參數(shù)選擇合適的手部、腕部和機(jī)身的結(jié)構(gòu)。 進(jìn)度安排： 1）.1-6周，主要進(jìn)行畢業(yè)設(shè)計準(zhǔn)備工作，熟悉題目，收集資料，進(jìn)行畢業(yè)實(shí)習(xí)，明 確研究目的和任務(wù)，構(gòu)思總體方案 2）.7-10周，繪制相關(guān)的圖 3）.11-13周，收尾完善，編寫畢業(yè)設(shè)計論文，準(zhǔn)備畢業(yè)設(shè)計答辯 2-3 已查閱的主要參考文獻(xiàn) 1.專著 [1] 李允文.工業(yè)機(jī)械手設(shè)計[M].北京：機(jī)械工業(yè)出版社，1996 [2] 加藤一郎.機(jī)械手圖冊[M]. 上海：上?？茖W(xué)技術(shù)出版社，1979 [3] 第一機(jī)械工業(yè)部機(jī)械研究院機(jī)電研究所編.工業(yè)機(jī)械手圖冊.北京：第一機(jī)械工業(yè)部機(jī)械研究院機(jī)電研究所，1976 2.論文集 [1] 付亞子.機(jī)械手控制系統(tǒng)[C].湖北：湖北工業(yè)大學(xué)，2006 [2] 通用機(jī)械手設(shè)計[C].湖北：湖北工業(yè)大學(xué)，2006 指導(dǎo)教師意見 指導(dǎo)教師簽名： 年 月 日 3 畢業(yè)設(shè)計（論文）學(xué)生申請答辯表 課 題 名 稱 關(guān)節(jié)型機(jī)械手設(shè)計 指導(dǎo)教師（職稱） 謝衛(wèi)容 申 請 理 由 已按照指導(dǎo)教師的要求完成設(shè)計，特申請答辯 學(xué)生所在系部 機(jī)械工程系 專業(yè)班級 05機(jī)制（1）班 學(xué)號 0515011127 學(xué)生簽名： 日期： 畢業(yè)設(shè)計（論文）指導(dǎo)教師評審表 序號 評分項目（理工科、管理類） 評分項目(文科) 滿分 評分 1 工作量 外文翻譯 15 2 文獻(xiàn)閱讀與外文翻譯 文獻(xiàn)閱讀與文獻(xiàn)綜述 10 3 技術(shù)水平與實(shí)際能力 創(chuàng)新能力與學(xué)術(shù)水平 25 4 研究成果基礎(chǔ)理論與專業(yè)知識 論證能力 25 5 文字表達(dá) 文字表達(dá) 10 6 學(xué)習(xí)態(tài)度與規(guī)范要求 學(xué)習(xí)態(tài)度與規(guī)范要求 15 總 分 100 評 語 （是否同意參加答辯） 指導(dǎo)教師簽名： 另附《畢業(yè)設(shè)計（論文）指導(dǎo)記錄冊》 年 月 日 4 畢業(yè)設(shè)計（論文）評閱人評審表 學(xué)生姓名 張安懷 專業(yè)班級 機(jī)制（1）班 學(xué)號 0515011127 設(shè)計（論文）題目 關(guān)節(jié)型機(jī)械手設(shè)計 評閱人 評閱人職稱 序號 評分項目（理工科、管理類） 評分項目(文科) 滿分 評分 1 工作量 外文翻譯 15 2 文獻(xiàn)閱讀與外文翻譯 文獻(xiàn)閱讀與文獻(xiàn)綜述 10 3 技術(shù)水平與實(shí)際能力 創(chuàng)新能力與學(xué)術(shù)水平 25 4 研究成果基礎(chǔ)理論與專業(yè)知識 論證能力 25 5 文字表達(dá) 文字表達(dá) 10 6 學(xué)習(xí)態(tài)度與規(guī)范要求 學(xué)習(xí)態(tài)度與規(guī)范要求 15 總 分 100 評 語 評閱人簽名： 年 月 日 5 畢業(yè)設(shè)計（論文）答辯表 學(xué)生姓名 張安懷 專業(yè)班級 05機(jī)制（1）班 學(xué)號 0515011127 設(shè)計（論文）題目 關(guān)節(jié)型機(jī)械手設(shè)計 序號 評審項目 指 標(biāo) 滿分 評分 1 報告內(nèi)容 思路清新；語言表達(dá)準(zhǔn)確，概念清楚，論點(diǎn)正確；實(shí)驗方法科學(xué)，分析歸納合理；結(jié)論有應(yīng)用價值。 40 2 報告過程 準(zhǔn)備工作充分,時間符合要求。 10 3 創(chuàng) 新 對前人工作有改進(jìn)或突破，或有獨(dú)特見解。 10 4 答 辯 回答問題有理論依據(jù)，基本概念清楚。主要問題回答準(zhǔn)確，深入。 40 總 分 100 答 辯 組 評 語 答辯組組長（簽字）： 年 月 日 答 辯 委 員 會 意 見 答辯委員會負(fù)責(zé)人（簽字）： 年 月 日 6-1 畢業(yè)設(shè)計（論文）答辯記錄表 學(xué)生姓名 張安懷 專業(yè)班級 05機(jī)制（1）班 學(xué)號 0515011127 設(shè)計（論文）題目 關(guān)節(jié)型機(jī)械手設(shè)計 答辯時間 答辯地點(diǎn) 答辯委員會名單 問題1 提問人： 問題： 回答（要點(diǎn)）： 問題2 提問人： 問題： 回答（要點(diǎn)）： 問題3 提問人： 問題： 回答（要點(diǎn)）： 記錄人簽名 （不足加附頁） 6-2 問題4 提問人： 問題： 回答（要點(diǎn)）： 問題5 提問人： 問題： 回答（要點(diǎn)）： 問題6 提問人： 問題： 回答（要點(diǎn)）： 問題7 提問人： 問題： 回答（要點(diǎn)）： 問題8 提問人： 問題： 回答（要點(diǎn)）： 記錄人簽名 7 畢業(yè)設(shè)計（論文）成績評定總表 學(xué)生姓名：張安懷 專業(yè)班級：05機(jī)制（1）班 畢業(yè)設(shè)計（論文）題目：關(guān)節(jié)型機(jī)械手設(shè)計 成績類別 成績評定 Ⅰ指導(dǎo)教師評定成績 Ⅱ評閱人評定成績 Ⅲ答辯組評定成績 總評成績 Ⅰ×40%+Ⅱ×20%+Ⅲ×40% 評定等級 注：成績評定由指導(dǎo)教師、評閱教師和答辯組分別給分(以百分記)，最后按“優(yōu)(90--100)”、“良(80--89)”、“中(70--79)”、“及格(60--69)”、“不及格(60以下)”評定等級。其中， 指導(dǎo)教師評定成績占40%，評閱人評定成績占20%，答辯組評定成績占40%。 Extending Blender: Development of a Haptic Authoring Tool Abstract -In this paper, we present our work to extend a well known 3D graphic modeler - Blender - to support haptic modeling and rendering. The extension tool is named HAMLAT (Haptic Application Markup Language Authoring Tool). We describe the modifications and additions to the Blender source code which have been used to create HAMLAT Furthermore, we present and discuss the design decisions used when developing HAMLAT, and also an implementation "road map" which describes the changes to the Blender source code. Finally, we conclude with discussion of our future development and research avenues. Keywords - Haptics, HAML, Graphic Modelers, Blender, Virtual Environments. I. INTRODUCTION A. Motivation The increasing adoption of haptic modality in human-computer interaction paradigms has led to a huge demand for new tools that help novice users to author and edit haptic applications. Currently, the haptic application development process is a time consuming experience that requires programming expertise. The complexity of haptic applications development rises from the fact that the haptic application components (such as the haptic API, the device, the haptic rendering algorithms, etc.) need to interact with the graphic components in order to achieve synchronicity. Additionally, there is a lack of application portability as the application is tightly coupled to a specific device that necessitates the use of its corresponding API. Therefore, device and API heterogeneity lead to the fragmentation and disorientation of both researchers and developers. In view of all these considerations, there is a clear need for an authoring tool that can build haptic applications while hiding programming details from the application modeler (such as API, device, or virtual model). This paper describes the technical development of the Haptic Application Markup Language Authoring Tool (HAMLAT). It is intended to explain the design decisions used for developing HAMLAT and also provides an implementation "road map", describing the source code of the project. B. Blender HAMLAT is based on the Blender [1] software suite, which is an open-source 3D modeling package with a rich feature set. It has a sophisticated user interface which is noted for its efficiency and flexibility, as well as its supports for multiple file formats, physics engine, modem computer graphic rendering and many other features. Because of Blender's open architecture and supportive community base, it was selected as the platform of choice for development of HAMLAT. The open-source nature of Blender means HAMLAT can easily leverage its existing functionality and focus on integrating haptic features which make it a complete hapto-visual modeling tool, since developing a 3D modeling platform from scratch requires considerable development time and expertise in order to reach the level of functionality of Blender. Also, we can take advantage of future improvements to Blender by merging changes from its source code into the HAMLAT source tree. HAMLAT builds on existing Blender components, such as the user-interface and editing tools, by adding new components which focus on the representation, modification, and rendering of haptic properties of objectsin a 3D scene. By using Blender as the basis for HAMLAT, we hope to develop a 3D haptic modeling tool which has the maturity and features of Blender combined with the novelty of haptic rendering. At the time of writing, HAMLAT is based on Blender version 2.43 source code. C. Project Goals As previously stated, the overall goal for the HAMLAT project is to produce a polished software application which combines the features of a modem graphic modeling tool with haptic rendering techniques. HAMLAT has the "look and feel" of a 3D graphical modeling package, but with the addition of features such as haptic rendering and haptic property descriptors. This allows artists, modelers, and developers to generate realistic 3D hapto-visual virtual environments. A high-level block diagram of HAMLAT is shown in Figure 1. It illustrates the flow of data in the haptic modeling. HAMLAT assists the modeler, or application developer, in building hapto-visual applications which may be stored in a database for later retrieval by another haptic application. By hapto-visual application we refer to any software which displays a 3D scene both visually and haptically to a user in a virtual setting. An XML file format, called HAML [2], is used to describe the 3D scenes and store the hapto-visual environments built by a modeler for later playback to an end user. Traditionally, building hapto-visual environments has required a strong technical and programming background. The task of haptically rendering a 3D scene is tedious since haptic properties must be assigned to individual objects in the scene and currently there are few high-level tools for accomplishing this task. HAMLAT bridges this gap by integrating into the HAML framework and delivering a complete solution for development of hapto- visual applications requiring no programming knowledge. The remainder of the paper is organized as follows: in Section 2, we present the proposed architecture extensions and discuss design constraints. Section 3 describes the implementation details and how haptic properties are added and rendered within the Blender framework. In Section 4 we discuss related issues and future work avenues. II. SYSTEM OVERVIEW AND ARCHITECTURE The Blender design philosophy is based on three main tasks: data storage, editing, and visualization. According to the legacy documentation [3], it follows a data- visualize-edit development cycle for the 3D modeling pipe line. A 3D scene is represented using data structures within the Blender architecture. The modeler views the scene, makes changes using the editing interface which directly modifies the underlying data structures, and then the cycle repeats. To better understand this development cycle, consider the representation of a 3D object in Blender. A 3D object may be represented by an array of vertices which have been organized as a polygonal mesh. Users may choose to operate on any subset of this data set. Editing tasks may include operations to rotate, scale, and translate the vertices, or perhaps a re-meshing algorithm to "cleanup" redundant vertices and transform from a quad to a triangle topology. The data is visualized using a graphical 3D renderer which is capable of displaying the object as a wireframe or as a shaded, solid surface. The visualization is necessary in order to see the effects of editing on the data. In a nutshell, this example defines the design philosophy behind Blender's architecture. In Blender, data is organized as a series of lists and base data types are combined with links between items in each list, creating complex scenes from simple structures. This allows data elements in each list to be reused, thus reducing the overall storage requirements. For example, a mesh may be linked by multiple scene objects, but the position and orientation may change for each object and the topology of the mesh remains the same. A diagram illustrating the organization of data structures and reuse of scene elements is shown in Figure 2. A scene object links to three objects, each of which link to two polygonal meshes. The meshes also share a common material property. The entire scene is rendered on one of several screens, which visualizes the scene. We adopt the Blender design approach for our authoring tool. The data structures which are used to represent objects in a 3D scene have been augmented to include fields for haptic properties (e.g., stiffness, damping); user interface components (e.g., button panels) which allow the modeler to change object properties have also been updated to include support for modifying the haptic properties of an object. Additionally, an interactive hapto-visual renderer has been implemented to display the 3D scene graphically and haptically, providing the modeler or artist with immediate feedback about the changes they make to the scene. in the current version of the HAMLAT. the modifications to the Blender framework include: data structures for representing haptic properties, an editing interface for modifying haptic properties, an external renderer for displaying and previewing haptically enabled scenes, scripts which allow scenes to be imported/exported in the HAML file format. A class diagram outlining the changes to the Blender ramework is shown in Figure 3. Components which are ertinent to HAMLAT are shaded in gray. HAMLAT builds on existing Blender sub-systems by extending them or haptic modeling purposes. Data structures for representing object geometry and graphical rendering areaugmented to include field which encompass the tactile properties necessary for haptic rendering. To allow the user to modify haptic properties GUI Components are integrated as part of the Blender editing panels. The operations triggered by these components operate directly on the d ata structures used for representing hatic cues and may be considered part of the editing step of the Blender design cycle. Similarly to the built-in graphical renderer, HAMLAT uses a custom rendlerer for displaying 3Ds scenes grphcal and haptcall, an is ineedn of the Blender renderer. This component is developed independently since haptical and graphical rendering must be performed simultaneously and synchronously. A simulation loop is used to update haptic rendering forces at a rate which maintains stability and quality. A detailed discussion of the implementation of these classes and their connectivity is given in the next section. III IMLIEMENTATION A Data Structure A.1 Mesh Data Type Blender uses many different data structures to represent the various types of objects in a 3D scene a vertices; a lamp contains colour and intensity values; and camera a object contains intrinsic viewing parameters. The Mesh data structure iS used by the Blender inframework to describe a polygonal mesh object. It iS of particular interest for hapic rendering since many solid objects in a 3D scene may be represented using this type of data structure. The tactile and kinesthetic cues, which are displayed due to interaction with virtual objects, are typically rendered based on the geometry of the mesh. Hptic rendering is performed based primary on data stored in this data type. Other scene components such as lamps, cameras, or lines are not intuitively rendered using force feedback haptic devices and are therefore not of current interest for haptic rendering. An augmented version of the Mesh data structure is shown in Figure 4. It contains fields for vertex and face data, plus some special custom data fields which allow data to be stored to/retrieved from disk and memory. We have modified this data type to include a pointer to a MHaptics data structure, which stores haptic properties such as stiffness, damping, and friction for the mesh elements (Figure 5). A.2 Edit Mesh Data Type It should be noted that the Mesh data type has a comPlimentary data structure, called EditMesh, which is used when editing mesh data. It holds a copy of the vertex, edge ,and face data for a polygonal mesh. when the user switches to editing mode, the Blender copies the data from a Mesh into an EditMesh and when editing is complete the data is copied back. Care must be taken to ensure that the hapic property data structure remains intact during the copy sequence. The EditMesh data structure has not been modified to contain a copy of the hapic property data ,but this may properties in edit mode is required). The editing mode is mainly used to modify mesh topology and geometry, not the haptic and graphical rendering characteristics, A.3 Haptic Properties In this section we'll briefly discuss the haptic properties which may currently be modeled using HAMLAT. It is important for the modeler to understand these properties and their basis for use in haptic rendering. The stiffness of an object defines how resistant it is to deformation by some applied force. Hard objects, such as a rock or table, have very high stiffness; soft objects, such as rubber ball, have low stiffness. The hardness-softness of an object is typically rendered using the spring-force equation: Where the force feedback vector f which is displayed to the user is computed using ks the stiffness coefficient (variable name stiffness)for the object and x the penetration depth (displacement) of the haptic proxy into an object. The stiffness coefficient has a range of [0,1], where 0 represents no resistance to deformation and 1 represents the maximum stiffness which may be rendered by the haptic device. The damping of an object defines its resistance to the rate of deformation due to some applied force. It is typically rendered using the force equation: Where kd is the damping coefficient (variable name}MHaptics; damping) anddepdt is the velocity ofthe haptic proxy as it;penetrates an object. The damping coefficient also has a range of [0,1] and may be used to model viscous behaviour of a material. It also increases the stability of the hapticrendering loop fordstiffmaterials. The static friction (variable name stjriction) and dynamic friction (variable name dyjriction) coefficient are used to model the frictional forces experienced whilee xploring the surface of a 3D object. Static friction is experienced when the proxy is not moving over the object's surface, and an initial force must be used to overcome static friction. Dynamic friction is felt when the proxy moves across the surface, rubbing against it. Frictional coefficients also have a range of /0,1], with a value of 0 making the surface of a 3D object feel "slippery" and a value of 1 making the object feel very rough. Frictional forces are typically rendered in a direction tangential to the collision point of the hapticproxy at an object's surface. B. Editing Blender uses a set of non-overlapping windows called spaces to modify various aspects of the 3D scene and its objects. Each space is divided into a set of areas andpanels which are context aware. That is, they provide functionality based on the selected object type. For example, if a camera is selected the panel will display components which allow the modeler to change the focal length and viewing angle of the camera, but these components will not appear if an object of another type is selected. Figure 6 shows a screen shot of the button space which is used to edit properties for a haptic mesh. It includes user-interface panels which allow a modeler to change the graphical shading properties of the mesh, perform simple re-meshing operations, and to modify the haptic properties of the selected mesh. HAMLAT follows the context-sensitive behavior of Blender by only displaying the haptic editing panel when a polygonal mesh object is selected. In the future, this panel may be duplicated to support haptic modeling for other object types, such as NURB surfaces. The Blender framework offers many user-interface components (e.g., buttons, sliders, pop-up menus) which may be used to edit the underlying data structures. The haptic properties for mesh objects are editable using sliders or by entering a float value into a text box located adjacent to the slider. When the value of the slider/text box is changed, it triggers an event in the Blender window sub-system. A unique identifier that the event is for the haptic property panel and the HAMLAT code should be called to update haptic properties for the currently selected mesh. C Hapto-Visual Rendering Blender currently support graphical rendering of scenes using an internal render or an external renderer (e.g., [4]). In this spirit, the haptic renderer used by HAMLAT has been developed as an exteral renderer. It uses the OpenGL and OpenHaptics toolkit [5] to perform graphic and hapic rendering ,respectively. The 3D scene which is being modeled is rendered using two passes: the first pass render the scene graphically, and the second pass renders it haptically. The second pass is required because the OpenHaptics toolkit intercepts commands send to the OpenGL pipeline and uses them to display the scene using haptic rendering techniques. In this pass, the haptic properties of each mesh object are used much in the same way color and lighting are used by graphical rendering they define the type of material for each object. To save CPU cycles, the lighting and graphical material properties are excluded from the haptic rendering pass. Figure 7 shows source code which is used to apply the material properties during the haptic rendering pass. The haptic renderer is independent from the Blender framework in that it exists outside the original source code. However, it is still heavily dependent on Blender data structures and types. D. Scripting The Blender Python (BPy) wrapper exposes many of the internal data structures, giving the internal Python scripting engine may access them. Similar to the data structures used for representing mesh objects in the native Blender framework, wrappers allow user defined scripts to access and modify the elements in a 3D scene. The hapic properties of a mesh object may be accessed through the Mesh wrapper class. A haptics attribute has been added to each of these classes and accessed through the Python scripting system. Figure 8 shows Python code to read the haptic properties from a mesh object and export to a file. Similar code is used to import/export HAML scenes from/to files. An import script allows 3D scenes to be read from a HAML file and reproduced in the HAMLAT application; export script allows 3D scenes to be written to a HAML file, including haptic properties, and used in other HAML applications. The BPy wrappers also expose the Blender windowing system. Figure 9 shows a panel which appears when the user exports a 3D scene to the HAML file format. It allows the user to specify supplementary information about the application such as a description, target hardware, and system requirements. These are fields defined by the HAML specification [2] and are included with the authored scene as part of the HAML file format. User-interface components displayed on this panel are easily extended to agree with the future revisions of HAML. The current version of HAMLAT shows that a unified modeling tool for graphics and haptics is possible. Promisingly, the features for modeling haptic properties have been integrated seamlessly into the Blender framework, which indicates it was a good choice as a platform for development of this tool. Blender's modular architecture will make future additions to its framework very straightforward. Currently, HAMLAT supports basic functionality for modeling and rendering hapto-visual applications. Scenes may be created, edited, previewed, and exported as part of a database for use in by other hapto-visual applications, such as the HAML player [6]. However, there is room for growth and in there are many more ways we can continue leveraging existing Blender functionality. As per future work ,we plan to extend HAMLAT TO include support for other haptic platforms and devices.Currently, only the PHANTOM series of devices is supported since the interactive renderer is dependent on the OpenHaptics toolkit [5]. In order to support otherd evices, a cross-platform library such as Chai3D or Haptik may be used to perform rendering. These libraries support force rendering for a large range of haptic hardware. Fortunately, due to the modularity of our implementation, only the interactive haptic rendering component need be altered for these changes. In addition to support multiple hardware platforms, a user interface co