Site Logo
Site Logo
 
It is currently Fri Oct 31, 2014 11:25 am

All times are UTC [ DST ]




Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: updates
PostPosted: Tue Nov 21, 2006 7:30 pm 
Offline
DELCAM Guru
DELCAM Guru
User avatar

Joined: Mon Oct 09, 2006 2:01 pm
Posts: 290
Location: midwest
id like to know where to find a ductpost update? "1490" i think


Top
 Profile  
 
 Post subject:
PostPosted: Wed Nov 22, 2006 1:34 pm 
Offline
Site Admin
User avatar

Joined: Tue Jul 20, 2004 11:10 am
Posts: 145
Location: Birmingham, UK
It is on the PowerMILL 7 DVD and we are arranging to upload it to http://updates.delcam.com

Bart


Top
 Profile  
 
 Post subject:
PostPosted: Wed Nov 22, 2006 1:53 pm 
Offline
DELCAM Guru
DELCAM Guru
User avatar

Joined: Mon Oct 09, 2006 2:01 pm
Posts: 290
Location: midwest
THANKS,HOW COME IT WASNT INCLUDED IN THE DOWNLOAD?


Top
 Profile  
 
 Post subject:
PostPosted: Tue Nov 28, 2006 10:15 am 
Offline
Site Admin
User avatar

Joined: Tue Jul 20, 2004 11:10 am
Posts: 145
Location: Birmingham, UK
now available from http://updates.delcam.com

or be selecting

Help Check for updates from the PowerMILL GUI and selcting the option to Visit the Updates Site.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Nov 29, 2006 4:10 pm 
Offline
DELCAM Guru
DELCAM Guru
User avatar

Joined: Tue Jul 27, 2004 10:21 pm
Posts: 384
Location: Windsor, CANADA
whats new in the 1490 ductpost?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Nov 29, 2006 8:50 pm 
Offline
DELCAM Guru
DELCAM Guru
User avatar

Joined: Wed Sep 01, 2004 4:24 pm
Posts: 1514
Location: Porto, Portugal
iamcdn wrote:
whats new in the 1490 ductpost?


Release notes for DUCTpost 1490
Requires PAF 2005.06 codes.
There was previously a problem with the linearisation causing DUCTpost to hang when coordinates were updated using the option file, such as
define block move linear
x coordinate ; y coordinate ; z coordinate ( zcoord + ToolLength[1] ) ;
azimuth axis ; elevation axis
end if

This is now solved. [ductpost#1098]
New coolant codes have been added to complement the new coolant settings available in PowerMILL. We now have "coolant on air", "coolant on double" and "coolant on through". [ductpost#1103]

Previously, we had a problem when using multiaxis drilling. If we had a vertical hole after a series of non-vertical holes, we could get incorrect values for WorkPlaneA, WorkPlaneB and WorkPlaneC. [ductpost#1112]
Release notes for DUCTpost 1480
Requires PAF 2005.06 codes.
Some problems have been fixed with arcs, particularly where the tool axis was not in a principal plane. Sometimes these arcs were incorrectly reported as being non-planar. [ductpost#1079, ductpost#1087]
When setting the Tool Change Position to "Before Connection" in the PowerMILL NCProgram form, previously DUCTpost might not output the necessary 3+2 angles. This issue is now solved. [ductpost#1083]
Direct access has been provided to the drill cycle "code number" that is written in the CLDATA. This "code number" uniquely identifies the cycle type. The block variable "CycleCodeNumber" provides this. [ductpost#1086]
A problem has been fixed with the block variables "ModelX" and so on. The issue is that these were not working correctly when DUCTpost was performing a 5-axis retract-and-reconfigure. [ductpost#1090]
Some new switches have been added. "swm" and "swn" have been added as logic flags. Integer flags "intg", "inth", and so on (up to "intn") have also been added. [ductpost#1094]
Release notes for DUCTpost 1470
Requires PAF 2005.06 codes.
DUCTpost 1460 introuduced a change in behaviour for SafeZ in canned cycles. Although correct, this change could produce results that may be unexpected. Therefore, this behaviour is no longer the default. Users requiring the newer behaviour for SafeZ in canned cycles can set:
use true safez in cycles = true

[ductpost#936]
Release notes for DUCTpost 1461
Requires PAF 2005.06 codes.
Release notes for DUCTpost 1460
Helical milling cycles that are expanded by DUCTpost now also go through the "cycle start" block immediately before the helical moves begin. [ductpost#975]
A new block "special record" has been added. This block is triggered whenever a PowerMILL "special record" is encountered. PowerMILL special records are general-purpose records and are mostly used to carry information that is useful, rather than essential. They are characterised in CLDATA by a major word of 29000 and a minor word of 0, and an integer code. A block variable "SpecialRecordCode" has been added, which returns the integer code used to identify the particular special record in question. One example where this functionality might be useful is for the case of "expanded drilling cycles". A special record is written out to indicate that this expansion has been taken place. With the previous scheme, DUCTpost needed changing each time such a record is added. With this scheme, it is possible to write:
define block special record
if ( SpecialRecordCode == 21 )
N ; "(Moves from an expanded drill cycle follow)"
end if
end define

If desired, the "real" and "string" parts of the special record can be extracted using the constructs "SpecialRecord[SpecialRecordCode]" for the real part, and "SpecialRecordString[SpecialRecordCode]" for the string part. [ductpost#976]
A problem existed with cutter compensation being turned off, when cutter compensation was used with expanded helical multiaxis drilling. This has been fixed. [ductpost#973]
The option file dump command, "ductpost -w", would incorrectly report that both "heid" and "h400" have "tape split on toolchange = true". This has now been fixed. [ductpost#393]
In order to prevent confusion, it is now only allowable to use "WorkplaneA", "workPlaneB" and "WorkplaneC" for option files where "workplane angles = apparent". Similarly, it is now only possible to use "WorkplaneAz" or "WorkplaneEl" if "workplane angles = machine tool". [ductpost#988]
Previously, it was possible for arcs to be output that were not exactly in principal planes. This is no longer possible. [ductpost#989]
Some slight tweaks were made to DUCTpost's handling of CLDATA to ensure consistency with future versions of PowerMILL. [ductpost#1012, ductpost#1021, ductpost#1027 ]
Previously, there was a problem with linearisation when the tool axis reached an orientation that was anti-parallel to the singular axis. This has been corrected. [ductpost#1010]
If, when a block is "expanded" by including any user blocks the total number of instructions is greater than the maximum allowed, DUCTpost could have crashed. The crash has been fixed, and the number of instructions allowed in a block has been increased to make this less likely to occur. [ductpost#1016]
Some block variables have been added to give access to the toolpath workplane data. "ToolpathWorkplaneA" and so on have been added to grant access to the Euler angles for a toolpath workplane. "ToolpathWorkplaneX", and so on grant access to the position of the toolpath workplane. Note that in most cases, users should carry on using "WorkplaneA" and so on, since that always gives the current workplane, and properly takes care of the workplane shifts used in 5-axis drilling. [ductpost#958]
TABLE-TABLE machines that have the settings "workplane angles = apparent" and "workplane angles = machine tool" now use machine tool workplanes when using drilling cycles (just as HEAD-HEAD and HEAD-TABLE machines do). [ductpost#957]
It is now possible to use "retract and reconfigure style" and "expand helical drilling cycles" without incorrect interaction between them. [ductpost#1036]
A flag "linearise first move" has been added. This flag defaults to true, but if it is set to false, the move to the first position in the CLDATA file is not linearised. [ductpost#900]
A problem with the linearisation of the very first move has been corrected. Previously, if a the from block was not empty, and didn't contain angles, then the coordinate values were out of step with the angles as output. This caused the linearisation to go wrong, since the initial position was wrong. [ductpost#900]
In a couple of cases, RAPID moves in CLDATA were not being converted to fast feedrate moves correctly, which has been corrected. [ductpost#1035]
A block variable "pitch" has been added, which gives the hole pitch as required by some machines for tapping. [ductpost#814]
A change has been made to the "safez" block variable when used in cycles. Previously, "safez" behaved differently in cycles to elsewhere. When used in cycles, "safez" returned the z value of the last coordinate before the cycle. This inconsistency has been removed. The previous behaviour is obtainable by using "CycleSafeZ", if this is desired. [ductpost#936]
A flag "use toolpath safe heights = true" has been added. If that is set to "true", then the current SafeZ and StartZ values are taken from those set for the current toolpath. Previously, the first SafeZ and StartZ values were used for all toolpaths. [ductpost#1041]
Two new codes have been added: "azimuth clamp on" and "azimuth clamp off". [ductpost#632]
A setting has been added that can prevent the "clearing" of modal words that takes place at the start of a drill cycle (by default). To stop the clearing of modal words, use the setting "clear modal words for cycles = false" [ductpost#1042]
The number of characters allowed in the address letter of a word has increased to 128. [ductpost#1044]
A problem with arcs in CLDATA in 5-axis has been fixed. Previously, if an arc was output in 5-axis mode, for a toolpath with an extremely fine tolerance, the arc may not have been output correctly by DUCTpost. [ductpost#1047]
"ToolComp" is now working correctly. Previously, this may have only worked fully if a tool change was present between toolpaths. [ductpost#1045]


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB