3097 連續(xù)式混凝土攪拌機設(shè)計

3097 連續(xù)式混凝土攪拌機設(shè)計,連續(xù),混凝土攪拌機,設(shè)計 摘 要混凝土攪拌機是施工機械裝備中的重要設(shè)備,其產(chǎn)品質(zhì)量和生產(chǎn)效率直接影響著建筑施工質(zhì)量和建筑施工進(jìn)度。強制式攪拌機是應(yīng)用最普遍、使用率最高的混凝土攪拌機。雙臥軸攪拌機是新型攪拌機型，因其攪拌質(zhì)量好，生產(chǎn)率高，被廣泛用于各種攪拌場合。本畢業(yè)設(shè)計從攪拌的目的和機理出發(fā)。工作時,物料在葉片推動下沿螺旋面移動,由于兩軸的旋轉(zhuǎn)方向相反,兩軸間的物料產(chǎn)生擠壓、翻滾和揉搓,以達(dá)到攪拌混合效果。長期的生產(chǎn)實踐證明,通過對臥軸式攪拌機的葉片結(jié)構(gòu)和曲面形狀進(jìn)行合理的布置和設(shè)計，混凝土的質(zhì)量和生產(chǎn)效率會有很大的提高。結(jié)合三種葉片的優(yōu)點，通過對他們進(jìn)行有序、合理的布置，讓混凝土在有限的時間進(jìn)行盡可能的攪拌。對它們曲面形狀進(jìn)行理論分析和一些試驗，克服傳統(tǒng)攪拌機器的缺點，并注意到新型設(shè)計可能引起的新的問題。通過攪拌過程的分析，詳細(xì)闡述了各參數(shù)的設(shè)計，并結(jié)合理論分析，給出了結(jié)論和建議。關(guān)鍵詞：混凝土攪拌機；雙臥軸； 改進(jìn)型葉片 ABSTRACTConcrete mixer is the key device of construction machinery and equipment. It has product quality and production efficiency, which direct impacts on the construction quality and progress of construction. Compulsory mixer is the most common and the highest utilization rate of concrete mixers。Double horizontal shaft mixer is a new-style mixer, which is widely used in many conditions because of the high mixing quality and productivityThis paper begins with the mechanism and purpose of mixing. The materials leaves along the spiral of mobile on the work. Because of the two axis of rotation opposite direction, the materials between the two axis produces extrusion rolling and scrubbing, in order to meet the stirring mixed effect. It has been proved in the long-term production, through the horizontal Coaxial mixer surface of the leaf structure and shape of a reasonable layout and design, concrete’s quality and production efficiency will be greatly improvedCombining with the advantages of three leafs, Concrete is going to mix as much as possible in the limited time through their orderly, rational layout. I do some theoretical analysis and a number of tests for the leaf-surface’s shape. Though the new design test, it overcomes shortcomings of traditional mixer, and notes that the new design may cause new problems. Though the theoretical analysis of the mixing process and concretely explicating the parametric design .Finally, it gives conclusions and suggestionsKey words: concrete mixer; double horizontal shaft; improved blade 目 錄前言………………………………………………………………………………11 總述……………………………………………………………………………31.1 攪拌的作用 ……………………………………………………………31.1.1 混凝土的組成 ……………………………………………………31.1.2 攪拌的任務(wù) ………………………………………………………31.1.3 合理的攪拌機理 …………………………………………………31.2 混凝土攪拌機的類型 …………………………………………………41.3 國內(nèi)外混凝土攪拌機的發(fā)展?fàn)顩r ……………………………………61.4 本文的內(nèi)容和方法 ……………………………………………………72 總體設(shè)計方案確定及動力元件選擇…………………………………………82.1 總體設(shè)計方案 …………………………………………………………82.2 電動機的選型 …………………………………………………………82.3 減速器的選型 …………………………………………………………92.4 聯(lián)軸器的選擇與計算…………………………………………………103 葉片的設(shè)計與計算 …………………………………………………………113.1 原有葉片的布置………………………………………………………113.2 設(shè)計葉片的布置………………………………………………………133.2.1 葉片的布置………………………………………………………143.2.2 裹軸現(xiàn)象…………………………………………………………163.3 葉片的主要參數(shù)………………………………………………………173.3.1 輸送葉片主要參數(shù)的設(shè)計………………………………………173.3.2 主軸轉(zhuǎn)速的確定…………………………………………………183.4 螺旋葉片的加工………………………………………………………243.4.1 葉片螺旋面的成形………………………………………………243.4.2 坯料形狀的選擇…………………………………………………24 3.4.3 整圓坯料尺寸的確定……………………………………………243.4.4 壓模主要尺寸的確定……………………………………………263.5 螺旋葉片的制造工藝…………………………………………………273.5 螺旋葉片的校核………………………………………………………274 軸的設(shè)計與計算 ……………………………………………………………354.1 左軸的校核……………………………………………………………354.1.1 初步估算軸的直徑………………………………………………354.1.2 軸的結(jié)構(gòu)設(shè)計……………………………………………………364.1.3 左軸加工工藝過程卡……………………………………………364.1.4 軸承的校核………………………………………………………374.1.5 軸的校核…………………………………………………………394.2 鍵的校核………………………………………………………………404.3 銷軸的校核……………………………………………………………414.4 右軸的校核……………………………………………………………424.4.1 初步估算軸的直徑………………………………………………424.4.2 軸的結(jié)構(gòu)設(shè)計……………………………………………………434.4.3 軸的強度校核……………………………………………………444.4.4 軸承的校核………………………………………………………454.5 攪拌軸筒的校核………………………………………………………46結(jié)論 ……………………………………………………………………………48致謝 ……………………………………………………………………………49參考文獻(xiàn) ………………………………………………………………………50附錄：……………………………………………………………………………52外文資料與中文翻譯 ……………………………………………………52河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計1本科畢業(yè)設(shè)計外文翻譯學(xué)院： 萬方科技學(xué)院指導(dǎo)老師： 張昌娟專業(yè)班級： 08 機制 3 班姓名： 王偉光學(xué)號： 0828070136河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計2附錄：外文資料與中文翻譯外文資料Extending Blender: Development of a Haptic Authoring ToolAbstract -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 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計3view 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. BlenderHAMLAT 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 isnoted 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.河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計4C. 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. 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計5The 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 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計6property. 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. 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計7Components 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 IMLIEMENTATIONA Data StructureA.1 Mesh Data TypeBlender 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 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計8components 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 TypeIt 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,河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計9A.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 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計10equation: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 whileexploring 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 veryrough. 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 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計11selected 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 RenderingBlender currently support graphical rendering of scenes using an internal render or an external 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計12renderer (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 Blenderframework in that it exists outside the original source code. However, it is still heavily dependent on Blender data structures and types.D. ScriptingThe Blender Python (BPy) wrapper exposes many of the internal data structures, giving the internal Python scripting engine may access them. Similar to the datastructures 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.河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計13The 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. 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢業(yè)設(shè)計14These 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 areeasily 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, 河南理工大學(xué)萬方科技學(xué)院 2012 屆本科生畢