Question/Problem

 How to solve TD not positioned correctly in XXYY. 

Environment

 - Lenze PLC

- Transfer Device

- iCollector 

 

Answer/Solution

 1. You will see the Below error, Following with the location where the ICL is faulted. In this case its 801.

     

2.  Y dimension out by 0.3mm (should be less than 6mm).

    

 3. Now check the camera weather its reading properly or not:

     

 4.  First try triggering the camera. After triggering, X,Y position values came back same as the pre-trigger one.

No servo problem since it was in motion just not at the right spot.

 

 

 5. Try resetting the fault and put ICL in production, if faulted again with TD going to the same previous position.

       This means Top camera need to be calibrated.

        Also Check and Verify the End camera, check the Y dimension value.

6. Now Move the  TD to 1,1 to check the calibration on the camera. TD should be aligned with 1,1.

   Ask site to check the position.

7. If its not aliened property then go to manual mode  

   Turn on the Servo and move the TD to desired position by jogging. 

   After reaching desired position turn off the servo. 

   

8. Now we can now re-calibrate the camera.

Open FB_ExtendedEquipment,

find Top_XY_ObjectScanner.Calib and make it false - double click, debug -> Write Value

 

 

9. Reset fault and put ICL back in Production. TD will stay there until camera is calibrated.

      Go to commissioning -> Status Bits -> Click TOP to calibrate the top camera.

      Wait for the Green flashing light at the bottom of the TOP button to turn solid Green.

      

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Related items

 

[This section is for attachments and/or links to other items. Attached documents shall be up-to-date, correct and using Honeywell standard templates.]

 

Internal Notes

 

[Section is meant for information only available for internal use. This includes references to internal records, such as Jira tickets, bug numbers, etc.]

***If there is information in this section prior to migration to SalesForce, then it may NOT be published. This information will be fully visible along with all information above.***

 

Reason for confidentiality

 

#NotValidated

[Section is meant for a brief reason for any data recorded in Internal Notes above, or any reason that the general article cannot be released to the public. Can be updated to #Validated once reused and agreed by KCS Contributor]

***If there is information in this section prior to migration to SalesForce, then it may NOT be published. This information will be fully visible along with all information above.***

 

DISCLAIMER:

Information in this document is subject to change without notice and does not represent a commitment on the part of Intelligrated. This information is typical of the questions and general advice given; however, your particular case and circumstances may produce different results or require different recommendations. Therefore, use of this information is not a suitable replacement for contacting Intelligrated Technical Service engineering for specific recommendations and solutions to your application.

 

No part of this article may be reproduced or transmitted in any form or by any means including recording, or information storage and retrieval systems, for any purpose without the express written permission of Intelligrated. All information contained within the article is private and confidential and the sole property of Intelligrated.

 

In no event, shall Intelligrated be liable for any damages whatsoever including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss, even if Intelligrated has been advised of the possibility of such damages. Because some states do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.

 

Template updated 2022-09-20 kwk Pending approval