Voir la source de TB0331 Idle Time Overrun Message

{{Tuto Details
|Main_Picture=TB0331_Idle_Time_Overrun_Message_PHOTO-2020-05-26-07-32-02.jpg
|Description=<translate>Error message appears on screen to operator. “Idle Time Overrun – Contact Stuga”. It is not clear what this message means or what could be the root causes.</translate>
|Categories=Maintenance, Software
|Tags=idle, time, overrun
}}
<translate>= Technical Bulletin =
{| class="wikitable" border="0" cellspacing="0" cellpadding="0"
| width="106" valign="top" |'''TB Number:'''
| width="554" valign="top" |331
|-
| width="106" valign="top" |'''Originator:'''
| width="554" valign="top" |Gareth  Green
|-
| width="106" valign="top" |'''Machine:'''
| width="554" valign="top" |Flowlines  / ZX /Microlines – Baldor Controllers
|-
| width="106" valign="top" |'''Date:''' 
| width="554" valign="top" |28/11/16
|-
| width="106" valign="top" |'''Circulate to:'''
| width="554" valign="top" |Service; 
|-
| width="106" valign="top" |'''Title:'''
| width="554" valign="top" |Idle Time  Overrun Error Message
|}

== Problem ==
Error message appears on screen to operator. “Idle Time Overrun – Contact Stuga”. It is not clear what this message means or what could be the root causes.

== Root Causes ==
{{#annotatedImageLight:Fichier:TB0331 Idle Time Overrun Following error.png|0=70px|hash=|jsondata=|mediaClass=Image|type=frameless|align=right|src=https://stuga.dokit.app/images/9/92/TB0331_Idle_Time_Overrun_Following_error.png|href=./Fichier:TB0331 Idle Time Overrun Following error.png|resource=./Fichier:TB0331 Idle Time Overrun Following error.png|caption=|size=70px}}The error is created by the Baldor controller on any one of the servo controlled axes (X, Y or Z) when the axis does not quite get to its intended position. More specifically, when the axis is nearly there, but within the “FolErr” distance (one of the axis setup parameters). 


Treat it the same way you would a Stall or Following Error, except you have the knowledge that the axis is very nearly at its position.
{| class="wikitable" border="1" cellspacing="0" cellpadding="0"
| width="659" valign="top" |'''Potential Root Causes'''
|-
| width="659" valign="top" |Z axis travel limited on V notch move to 100mm –  swarf packed under bearing block
|-
| width="659" valign="top" |Spindle not spinning as it hits profile – x axis cannot  move
|-
| width="659" valign="top" |Blunt tool in spindle
|-
| width="659" valign="top" |Plunge speed too fast on a spindle
|}

== Where has it come from? ==
The test and subsequent alarm for this error comes following investigations into spindle failures in 2015. A failure mode was discovered where the spindle could plunge with a “Speedy” operation, but due to various reasons, the spindle was not spinning when it hit the profile. 

* The spindle error was not picked up and the x axis tried to move to complete the slot. 
* The spindle was pressed into the profile, so the x axis was jammed, but it only had to move the 20mm of the slot length. 
* The 20mm was less than the X axis minimum following error (60mm)
* The machine sat doing nothing with full power into the spindle motor
* After a few minutes, the spindle burnt out

A fault detection system was introduced to timeout if the controller was waiting for idle, yet the axis was within its following error distance. Instead of waiting forever, an “Idle Time Overrun” error is thrown, which ensures any spindle power is switched off.

= What to do about it? =

* Check for the root causes (above) , or anything that could stop an axis getting to its position
* Reduce the FolErr parameter for the axis that is creating the fault. NOTE this is not a cure for the problem, because the machine will now produce a servo error. The actual root cause of why the axis is not getting to position will still need to be identified</translate>
{{PageLang
|Language=en
|SourceLanguage=none
|IsTranslation=0
}}
{{AddComments}}
{{Tuto Status
|Complete=Draft
}}