Difference between revisions of "CNC Bender v11-20091218"

From ATTWiki
Jump to: navigation, search
(25px OPTIMIZATION - for [BEGIN RUN AGAIN])
(25px REPAIR - For [BEGIN RUN AGAIN] Feature)
 
(61 intermediate revisions by one user not shown)
Line 8: Line 8:
 
<tr>
 
<tr>
 
<td>
 
<td>
Type of Upgrade: '''Critical: ACCURACY'''
+
Type of Upgrade: '''Critical ACCURACY'''
 
</td>
 
</td>
 
<td>
 
<td>
Line 23: Line 23:
 
</table>
 
</table>
  
__NOTOC__
+
__TOC__
  
  
===[[image:Check.jpg|25px]] REPAIR - Feed Accuracy Fix During Feed/Rotate Motion When Bend Arm Returning===
+
===[[image:Check.jpg|25px]] REPAIR - Feed Accuracy Issues During Feed/Rotate Motion When Bend Arm Returning===
 
<table>
 
<table>
 
<tr valign=top>
 
<tr valign=top>
 
<td width=300>
 
<td width=300>
* There were circumstances were the Feed positioning was interfered with by Processor making multiple calls to the BEND axis when the BEND axis was returning to ZERO.<br><br>
+
* There were circumstances were the Feed positioning axis accuracy could decrease unacceptably by Processor making multiple calls to the BEND axis when the BEND axis was returning to ZERO, and the Feed/Rotate axes began to move at the same time.<br><br>
 +
 
 
* We discovered this problem running on a new high-speed Pro-face operator station running LiteControl.<br><br>
 
* We discovered this problem running on a new high-speed Pro-face operator station running LiteControl.<br><br>
 
* We are convinced that this issue could occur in any bender with newer software being run in a fast Pro-face control.<br><br>
 
* We are convinced that this issue could occur in any bender with newer software being run in a fast Pro-face control.<br><br>
* The issue is directly linked to the "Don't Move if Within Position Tolerance Of" value in the AXIS configuration file, and situations where multiple axes are called simultaneously in the same COMDEF (like when the bend arm is returning and the Feed/Rotate axis starts up).<br><br>
+
 
* The "ignore" Axis property is now ignored and can be removed from the axis file.<br><br>
+
* '''After several tests, we have confirmed that this version of CNC Bender completely RESOLVES the issue.'''<br><br>
 +
</td>
 +
 
 +
<td width=300>
 +
[[image:bendarm_blur_vb150.jpg|200px]]
 +
 
 +
* The issue is directly linked to:
 +
 
 +
# The "Don't Move if Within Position Tolerance Of" value in the AXIS configuration file - where axis moves are skipped when they are already in position.<br><br>
 +
# ...Combined with situations where multiple axes are called simultaneously in the same COMDEF (like when the bend arm is returning and the Feed/Rotate axis starts up).<br><br>
 +
</td>
 +
</tr>
 +
 
 +
</table>
 +
 
 +
<br><br>
 +
 
 +
===[[image:Check.jpg|25px]] CHANGE - Removed TOLERANCE Option from AXIS File===
 +
<table>
 +
<tr valign=top>
 +
<td width=300>
 +
* The "Dont Move If Position Within Tolerance Value" value is no longer used<br><br>
 +
* This resolves issues discussed in the previous section.<br><br>
 +
* '''This line can be safely removed from all future main.axislist files'''<br><br>
 +
 
 +
This feature was originally introduced in version [[CNC Bender 10.0.6.0m - Tolerance Move Skip]] in November of 2006.  It was intended to reduce problems with the axes floating near zero, and Absolute moves having difficulty determining which way to move into position. (For example, the Feed axes could attempt to run backwards behind zero under very rare circumstances until version [[CNC Bender v11-20091201]], where all axes are now kept far from internal zero.)<br><br>
 +
 
 +
Because of the permanent resolution to the absolute direction problem in version [[CNC Bender v11-20091201]], and because of the problems caused by this option as discussed in previous sections, it was removed from CNC Bender.
 
</td>
 
</td>
  
 
<td>
 
<td>
[[image:bendarm_blur_vb150.jpg|300px]]
+
[[image:removed_dontmovewithin_fromaxis.jpg|300px]]
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 46: Line 74:
 
<br><br>
 
<br><br>
  
===[[image:Check.jpg|25px]] OPTIMIZATION - for [BEGIN RUN AGAIN]===
+
===[[image:Check.jpg|25px]] REPAIR - For [BEGIN RUN AGAIN] Feature===
  
 
<table>
 
<table>
<tr>
+
<tr valign=top>
 
<td width=300>
 
<td width=300>
* As of version [[CNC Bender v11-20091104]], CNC Processlist Builder inserts a new [BEGIN RUN AGAIN] label placed in the middle of each part's process list to trim off processing time by showing CNC Processor where to start when the same part is run the second time and greater.<br><br>
+
* We discovered that the return of the process to the [BEGIN RUN AGAIN] label did not occur until after the '''second time''' through the processlist.  This increased time slightly, and sometimes caused the bend arm to pause on the way to the home position when the '''"Last Row Absolute Feed Clear - Immediate Move"''' was ENABLED.<br><br>
 +
 
 +
* '''This problem has been resolved.'''  Parts now run faster on the second time through the process, and the bend arm motion will not be stopped and restarted while returning.<br><br>
  
* We discovered that the switch to the [BEGIN RUN AGAIN] label did not occur until after the second time through the processlist.  This increased time slightly, and sometimes caused the bend arm to pause on the way to the home position when the '''"Last Row Absolute Feed Clear - Immediate Move"''' was ENABLED.<br><br>
 
  
 
</td>
 
</td>
  
<td>
+
<td width=300>
[[image:LastRowAbsoluteFeedClearImmediateOption.jpg|500px]]<br>
+
[[image:LastRowAbsoluteFeedClearImmediateOption.jpg|300px]]<br><br>
 +
Explanation of Feature: As of version [[CNC Bender v11-20091104]], CNC Processlist Builder inserts a new [BEGIN RUN AGAIN] label placed in the middle of each part's process list to trim off processing time.  This allows CNC Processor to skip the initialization section of each new part after it has been run once.<br><br>
 +
 
 +
The benefit is removal of all latency when the process initializes all axes for loading the next part into the machine.
 +
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 66: Line 99:
 
<br><br>
 
<br><br>
  
===[[image:Check.jpg|25px]] NEW - Second Constant Run List Designed for HIGH SPEED OPERATIONS ===
+
===[[image:Check.jpg|25px]] REPAIR - Placed Collision Messages back in the Immediate Message Box===
 +
<table>
 +
<tr valign=top>
 +
<td width=300>
 +
As of the previous version ([[CNC Bender v11-20091201]]), the collision warnings were no longer sent to the Immediate Message box.
 +
<br><br>
 +
This is a problem because the software would switch between AUTO and MANUAL mode without any kind of report why.  This version resolves that issue.
 +
<br><br>
 +
'''All collision warnings are now again sent to the Immediate Message box.'''
 +
<br><br>
 +
This places the collision messages directly in front of the user on the screen. 
 +
</td>
  
<table cellpadding=5>
 
<tr>
 
 
<td width=300>
 
<td width=300>
* USe the new high-speed constant run list for processes that should run all the time and get high attention.<br><br>
+
[[image:collision_immediate_message.jpg|200px]]
* Control the interval of how often the list runs in the Processor tab in the Low Level menu.<br><br>
+
</td>
 +
</tr>
  
* The list file is separate from the ConstantRun processlist.  The name is '''"ConstantRunHS.processlist"'''<br><br>
+
</table>
  
* Put tube-support control in this list to make it more responsive to fast moving Feed axes.
+
<br><br>
  
 +
===[[image:Check.jpg|25px]] ENHANCE - TCP/IP Error Messages Now Include the Module Name===
 +
<table>
 +
<tr valign=top>
 +
<td width=300>
 +
As of this version, the TCP/IP messages sent to the Immediate Message box include the module name that caused the problem.
 +
<br><br>
 +
This is how the new message will appear:<br><br>
 +
'''[TCP/IP Errors] - STOPPING Communication with Modules (Problem with module: digital_output_221)'''
 +
<br><br>
 +
This places the module names directly in front of the user on the screen, rather than only in the TCP/IP log on disk.
 
</td>
 
</td>
  
<td width=350>
+
<td width=300>
[[image:HighSpeedConstantRun.jpg|500px]]
+
[[image:tcpip_modulename_immediate_message.jpg|200px]]
 
</td>
 
</td>
 
</tr>
 
</tr>
  
 
</table>
 
</table>
<br>
+
 
<br>
+
<br><br>
  
 
=Other Pages=
 
=Other Pages=
Line 93: Line 146:
 
*Back to [[CNC Bender Software Updates]]
 
*Back to [[CNC Bender Software Updates]]
 
*See [[CNC Bender General Information]]
 
*See [[CNC Bender General Information]]
*See [[Absolute Rotate]]
 
*See [[Absolute Rotate Offset Position]]
 
 
*See [[Final Feed Clearance]]
 
*See [[Final Feed Clearance]]
*See [[Mandrel Retract]]
 
*See [[Mandrel Retract Part Release]]
 

Latest revision as of 17:23, 21 December 2009

Cncbender logo pushbending.png

Type of Upgrade: Critical ACCURACY

The changes in this version are designed to make CNC Bender more accurate and run faster.

Operatorstation model.jpg

Contents


Check.jpg REPAIR - Feed Accuracy Issues During Feed/Rotate Motion When Bend Arm Returning

  • There were circumstances were the Feed positioning axis accuracy could decrease unacceptably by Processor making multiple calls to the BEND axis when the BEND axis was returning to ZERO, and the Feed/Rotate axes began to move at the same time.

  • We discovered this problem running on a new high-speed Pro-face operator station running LiteControl.

  • We are convinced that this issue could occur in any bender with newer software being run in a fast Pro-face control.

  • After several tests, we have confirmed that this version of CNC Bender completely RESOLVES the issue.

Bendarm blur vb150.jpg

  • The issue is directly linked to:
  1. The "Don't Move if Within Position Tolerance Of" value in the AXIS configuration file - where axis moves are skipped when they are already in position.

  2. ...Combined with situations where multiple axes are called simultaneously in the same COMDEF (like when the bend arm is returning and the Feed/Rotate axis starts up).



Check.jpg CHANGE - Removed TOLERANCE Option from AXIS File

  • The "Dont Move If Position Within Tolerance Value" value is no longer used

  • This resolves issues discussed in the previous section.

  • This line can be safely removed from all future main.axislist files

This feature was originally introduced in version CNC Bender 10.0.6.0m - Tolerance Move Skip in November of 2006. It was intended to reduce problems with the axes floating near zero, and Absolute moves having difficulty determining which way to move into position. (For example, the Feed axes could attempt to run backwards behind zero under very rare circumstances until version CNC Bender v11-20091201, where all axes are now kept far from internal zero.)

Because of the permanent resolution to the absolute direction problem in version CNC Bender v11-20091201, and because of the problems caused by this option as discussed in previous sections, it was removed from CNC Bender.

Removed dontmovewithin fromaxis.jpg



Check.jpg REPAIR - For [BEGIN RUN AGAIN] Feature

  • We discovered that the return of the process to the [BEGIN RUN AGAIN] label did not occur until after the second time through the processlist. This increased time slightly, and sometimes caused the bend arm to pause on the way to the home position when the "Last Row Absolute Feed Clear - Immediate Move" was ENABLED.

  • This problem has been resolved. Parts now run faster on the second time through the process, and the bend arm motion will not be stopped and restarted while returning.


LastRowAbsoluteFeedClearImmediateOption.jpg

Explanation of Feature: As of version CNC Bender v11-20091104, CNC Processlist Builder inserts a new [BEGIN RUN AGAIN] label placed in the middle of each part's process list to trim off processing time. This allows CNC Processor to skip the initialization section of each new part after it has been run once.

The benefit is removal of all latency when the process initializes all axes for loading the next part into the machine.



Check.jpg REPAIR - Placed Collision Messages back in the Immediate Message Box

As of the previous version (CNC Bender v11-20091201), the collision warnings were no longer sent to the Immediate Message box.

This is a problem because the software would switch between AUTO and MANUAL mode without any kind of report why. This version resolves that issue.

All collision warnings are now again sent to the Immediate Message box.

This places the collision messages directly in front of the user on the screen.

Collision immediate message.jpg



Check.jpg ENHANCE - TCP/IP Error Messages Now Include the Module Name

As of this version, the TCP/IP messages sent to the Immediate Message box include the module name that caused the problem.

This is how the new message will appear:

[TCP/IP Errors] - STOPPING Communication with Modules (Problem with module: digital_output_221)

This places the module names directly in front of the user on the screen, rather than only in the TCP/IP log on disk.

Tcpip modulename immediate message.jpg



Other Pages