Effect of Lubricant on Wear Debris Color Diagnosis

Authors

  • M. A. Khan National University of Sciences and Technology, PNEC Campus
  • R. B. Hussnain National University of Sciences and Technology, PNEC Campus
  • K. Basit National University of Sciences and Technology, PNEC Campus
  • M. Safdar National University of Sciences and Technology, PNEC Campus
  • M. Raza National University of Sciences and Technology, PNEC Campus

Abstract

Color feature of debris is quite often used for source diagnosis in machine component while performing wear debris analysis (WDA). This feature is commonly observed and analyzed with different offline debris imaging setups. In these setups, its attributes remain consistent in their values as just a colorless medium i.e. air is in between the imaging setup and the observed debris. But in the case of an online debris analysis, the measurements of these attributes can be affected as the imaging has to perform in the presence of a machine lubricant. The lubricant color can affect the measurement of debris original color attributes and further can cause a wrong source diagnosis. In this paper, the effects of lubricant color on debris color measurements are discussed. A debris imaging setup is used for experimentation. Micro size steel debris are analyzed with three different lubricants. The debris color measurements are initially performed in an offline mode when the debris are placed on a glass slide. Later the mentioned measurements are taken in the presence of lubricants when the debris are flowing with the lubricant medium via a flow cell. Finally a comparison is made which concludes that the darker the lubricant the lesser will be chances to deduce the material (color and attributes). Whereas brighter lubricants do not hinder the analysis and identification of material and hence are considered suitable for qualitative wear debris analysis.

Downloads

Download data is not yet available.

Downloads

How to Cite

Khan, M. A., Hussnain, R. B., Basit, K., Safdar, M., & Raza, M. (2015). Effect of Lubricant on Wear Debris Color Diagnosis. Journal of Mechanical Engineering and Technology (JMET), 5(2). Retrieved from https://jmet.utem.edu.my/jmet/article/view/347

Issue

Vol. 5 No. 2

Section

Others

License

JMET Copyright Principles
 
JMET seeks to retain copyright of the articles it publishes, without the authors giving up their right to use their own material.

Originality

The manuscript is neither been published before, nor is it under consideration for publication in any other journals. It contains no matter that is scandalous, obscene, libelous or otherwise contrary to law.

Terms of Acceptance 

When the article is accepted for publication, the authors shall hereby agree to transfer to the Journal of Mechanical Engineering and Technology, all rights, including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):

 All proprietary right other than copyright, such as patent rights.

  1. The right to make further copies of all or part of the published article for my/our use in classroom teaching.
  2. The right to reuse all or part of this material in a compilation of my/our own works or in a textbook of which I/we am/are the author(s).
  3. The right to make copies of the published work for internal distribution within the institution that employs me/us.

The authors agree that copies made under these circumstances will continue to carry the copyright notice that appeared in the original published work. The authors agree to inform any co-authors, if any, of the above terms. The authors certify that they have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and they agree to supply such written permission(s) to Journal of Mechanical Engineering and Technology upon request.

                                                                  ADOConnection.CacheExecute(3600, SELECT 				o.submission_id, 				MAX(s.context_id) AS journal_id, 				MAX(i.date_published) AS i_pub, 				MAX(p.date_published) A..., Array[2]) % line  132, file: DAO.inc.php
                                                               DAO.retrieveCached(SELECT 				o.submission_id, 				MAX(s.context_id) AS journal_id, 				MAX(i.date_published) AS i_pub, 				MAX(p.date_published) A..., Array[2], 3600) % line   91, file: ArticleSearchDAO.inc.php
                                                            ArticleSearchDAO.getPhraseResults(Object:Journal, Array[1], null, null, , 500, 1) % line  202, file: SubmissionSearch.inc.php
                                                         SubmissionSearch._getMergedPhraseResults(Object:Journal, Array[1], , null, null, 500, 1) % line  147, file: SubmissionSearch.inc.php
                                                      SubmissionSearch._getMergedKeywordResults(Object:Journal, Array[4], , null, null, 500, 1) % line  195, file: SubmissionSearch.inc.php
                                                   SubmissionSearch._getMergedPhraseResults(Object:Journal, Array[4], null, null, null, 500, 1) % line  147, file: SubmissionSearch.inc.php
                                                SubmissionSearch._getMergedKeywordResults(Object:Journal, Array[3], null, null, null, 500, 1) % line  133, file: SubmissionSearch.inc.php
                                             SubmissionSearch._getMergedArray(Object:Journal, Array[1], null, null) % line  264, file: SubmissionSearch.inc.php
                                          SubmissionSearch.retrieveResults(Object:Request, Object:Journal, Array[1], null, null, null, Object:DBResultRange, Array[1]) % line   92, file: RecommendBySimilarityPlugin.inc.php
                                       RecommendBySimilarityPlugin.callbackTemplateArticlePageFooter(Templates::Article::Footer::PageFooter, Array[3]) % line  107, file: HookRegistry.inc.php
                                    HookRegistry.call(Templates::Article::Footer::PageFooter, Array[3]) % line 1256, file: PKPTemplateManager.inc.php
                                 PKPTemplateManager.smartyCallHook(Array[1], Object:Smarty_Internal_Template) % line   43, file: a4fc84a2d9d2a85c011fcc528f09577e88e2fcff^1c372c95cd85572e0fbc9a53d0323a0b229cfc78_0.app.frontendpagesarticle.tpl.php
                              content_68d93a219ef926_76299402(Object:Smarty_Internal_Template) % line  123, file: smarty_template_resource_base.php
                           Smarty_Template_Resource_Base.getRenderedTemplateCode(Object:Smarty_Internal_Template) % line  114, file: smarty_template_compiled.php
                        Smarty_Template_Compiled.render(Object:Smarty_Internal_Template) % line  216, file: smarty_internal_template.php
                     Smarty_Internal_Template.render(false, 1) % line  232, file: smarty_internal_templatebase.php
                  Smarty_Internal_TemplateBase._execute(Object:Smarty_Internal_Template, null, a4fc84a2d9d2a85c011fcc528f09577e88e2fcff, null, 1) % line  134, file: smarty_internal_templatebase.php
               Smarty_Internal_TemplateBase.display(frontend/pages/article.tpl, null, a4fc84a2d9d2a85c011fcc528f09577e88e2fcff, null) % line  924, file: PKPTemplateManager.inc.php
            PKPTemplateManager.display(frontend/pages/article.tpl) % line  297, file: ArticleHandler.inc.php
         ArticleHandler.view(Array[1], Object:Request) % line  391, file: PKPRouter.inc.php
      PKPRouter._authorizeInitializeAndCallRequest(Array[2], Object:Request, Array[1], false) % line  231, file: PKPPageRouter.inc.php
   PKPPageRouter.route(Object:Request) % line  143, file: Dispatcher.inc.php
Dispatcher.dispatch(Object:Request) % line  281, file: PKPApplication.inc.php
PKPApplication.execute() % line   68, file: index.php