100 Continue
The requestor should continue with the request. The server returns this code to indicate that it has received the first part of a request and is waiting for the rest.
101 Switching Protocols
This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so
102 Processing
As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.
200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
201 Created
The request has been fulfilled and resulted in a new resource being created.
202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
203 Non-Authoritative Information (since HTTP/1.1)
The server successfully processed the request, but is returning information that may be from another source.
204 No Content
The server successfully processed the request, but is not returning any content.
205 Reset Content
The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
206 Partial Content
The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
207 Multi-Status (WebDAV) (RFC 2518 )
The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
300 Multiple Choices
Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
301 Moved Permanently
This and all future requests should be directed to the given URI.
302 Found
This is the most popular redirect code, but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945 ) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
303 See Other (since HTTP/1.1)
The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
304 Not Modified
Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified
Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
305 Use Proxy
The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.
306 Switch Proxy
No longer used.
307 Temporary Redirect (since HTTP/1.1)
In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.
400 Bad Request
The request contains bad syntax or cannot be fulfilled. The server didn't understand the syntax of the request.
401 Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The request requires authentication. The server might return this response for a page behind a login.
402 Payment Required
The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.
403 Forbidden
The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found
The server can't find the requested page. For instance, the server often returns this code if the request is for a page that doesn't exist on the server. The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible. No indication is given of whether the condition is temporary or permanent.
405 Method Not Allowed
A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
406 Not Acceptable
The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field containing a challenge applicable to the proxy for the requested resource.
408 Request Timeout
The server timed out waiting for the request.
409 Conflict
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
410 Gone
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a 404 Not Found can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request.
413 Request Entity Too Large
The request is larger than the server is willing or able to process.
414 Request URI Too Long
The URI provided was too long for the server to process.
415 Unsupported Media Type
The request did not specify any media types that the server or resource supports. For example the client specified that an image resource should be served as image/svg+xml, but the server cannot find a matching version of the image.
416 Requested Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion (for example, if the client asked for a part of the file that lies beyond the end of the file).
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.
418 I'm a teapot
The HTCPCP server is a teapot. The responding entity MAY be short and stout. This code was defined as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
422 Unprocessable Entity (WebDAV) (RFC 4918 )
The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV) (RFC 4918 )
The resource that is being accessed is locked
424 Failed Dependency (WebDAV) (RFC 4918 )
The request failed due to failure of a previous request (e.g. a PROPPATCH).
425 Unordered Collection (RFC 3648 )
Defined in drafts of WebDav Advanced Collections, but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817 )
The client should switch to TLS/1.0.
449 Retry With
A 微软 extension. The request should be retried after doing the appropriate action.
450 Blocked by Windows Parental Controls
A 微软 extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
500 Internal Server Error
A generic error message, given when no more specific message is suitable.
501 Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the downstream server.
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely request from the downstream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates (RFC 2295 )
Transparent content negotiation for the request, results in a circular reference.
507 Insufficient Storage (WebDAV) (RFC 4918 )
509 Bandwidth Limit Exceeded (Apache bw/limited extension)
This status code, while used by many servers, is not specified in any RFCs.
510 Not Extended (RFC 2774 )
Further extensions to the request are required for the server to fulfill it.
XML 地图 | Sitemap 地图
不同种类螺杆的技术要求_js金沙登入网址118
舟山js金沙登入网址118机械js金沙登入网址118

锐意进取、创新致远

  • 专业设计、制造螺杆、机筒、料筒的生产企业
  • 全国咨询电话  0580-8592012

    二维码

    不同种类螺杆的技术要求

    日期:2017-11-28 浏览量:100+

    摘要:一般的注塑机用一要标准的中径螺杆,再配两根高低压的常规螺杆,可适用于范围较广的通...


    螺杆要求--种类与形式:

    1、常规注塑螺杆 :一般的注塑机用一要标准的中径螺杆,再配两根高低压的常规螺杆,可适用于范围较广的通用塑料和工程塑料的加工。这种螺杆也是三段式:加料段,压缩段,均化段。都是考虑注塑机预塑和注塑加工的物料的工作特点来定。 

    2、加长注塑螺杆:是有较高塑化能力各较好混合作用的通用型注塑螺杆,与常规螺杆比较其特点是:长径比大(20~25),计量段长(30%),计量段槽较浅(0.04~0.05D),压缩比较大(0.11~012D),因此有利于塑化各混合作用. 

    3、型的硬聚氯乙烯注塑螺杆:这种螺杆的特点是:长径比小,计量段和输送段较短,压缩段较长;计量段的螺槽较深,压缩比较小,适合于对硬聚氯乙烯等热稳定性差的塑料进行注塑成型。为了减少强剪切作用和存料,防止过热分解,这种螺杆适合配以有熔体流动空的“Z”型螺杆头。 

    4、无计量段注塑螺杆:无计量段注塑螺杆又称“ZM”螺杆,其特点是没有计量段,只有加料段和过渡段,所以这是一种两段式的螺杆。由于无计量段可以减少熔体过热,增加塑化能力和混炼效果,所以适用于注塑ABS和防止剪切过热的其它非结晶性材料,如用来加工阻燃型抗冲击型聚苯乙烯、聚碳酸酯、充填聚苯乙烯、聚氯乙烯、和充填尼龙等。无计量段螺杆长径比一般为20,加料段与过渡段的长度各占50%,各段推荐螺槽深 

    5、分离型注塑螺杆:(BM螺杆)分离注塑螺杆以称“BM”螺杆,在注塑上已得至广泛运用,主种螺杆的特点是在熔融段(过渡段、压缩段)增加一条副螺纹,把主螺纹槽分的成两部分,当螺杆旋转时主螺纹刮下的熔膜从螺棱与料筒壁的间隙中流入副螺纹的螺槽,使固体床与熔池分开,从而保持固体床与料筒内壁的良好好接触,便于输送和传热。 

    6、波状螺杆(HPM螺杆):波状螺杆有“单波”和“双波”之分。单波型螺杆的特点是两个相邻螺槽的底径是相等的,但却是偏心的,而且偏心距相等,并对称开螺杆轴线。由于螺槽深度沿轴向呈波浪形周期性地变化,所以预塑时物料受到强挤压各强剪切作用,吸取大量机械能并进行能量转换;而到波谷时物料得到松弛,进行能量的均衡各温度的均化。对已经熔融的聚合物来说将很快地通过强剪切区,而对剩余的固体物料来说将被迫受强剪切作用进行周期性的变化,从而加速了固体床的解体和熔融。双波螺杆不仅可以提高塑化能力,而且能增加混炼效果。适用于有填料、颜料以及发泡剂的物料注塑成型,能得到均匀的组分;也适用注塑硬聚氯乙烯等热敏性物料,可以减少降解作用。 

    7、混炼型注塑螺杆:混炼型注塑螺杆的特点是在计量段位置上设置混炼元件。基于对普通螺杆的分析表明;在过渡段,聚合物初步熔融,在螺纹后缘也形成了熔膜。所以整个固体床实际上被熔膜包围,降低了熔融效率。所以在过渡区,仍以强调稳定地熔融和输送作用为宜。在物料经过过渡段全部熔融之后,再加上一段混炼区,并在混炼区上设置混炼元件,使物料得以进一步混合和均化。混炼元件型式有以三种。销钉型混炼元件(IKV混炼元件);屏障型混炼元件(直槽混炼元件以又称Maddook元件);其它屏障型混炼元件,(分流形混炼元件又称DIS形混炼元件) 

    8、组合螺杆:组合螺杆是多用在螺杆计量段的心轴上,根据物料的不同性质安装不同功能的混炼元件组。混炼元件做成键的形式,并用键和心思连接,套的端面要精密配合,以防熔体进入。

    XML 地图 | Sitemap 地图