首页/文章/ 详情

ANSA<Assembly第七弹_Connection Manager②

27天前浏览991

嗨,大家晚上好。

今天继续给大家分享Connection Manager

模块二:检查连接调整焊接方向与搜索距离,编辑边距,关于该功能的介绍在帮助文档616页。

1、在连接生成完成后,检查是必不可少的一步,ANSA刚好提供了这样一个方便的功能,点击inspect,会弹出检查选项对话框,零件的显示模式是以ENT,还是PID,part,零件是否透明以及高亮。检查一个后,点击NEXT自动切换到下一个连接数据,也可以直接点击连接数据列表某一个。

2、为了规范,大家也可以把所有连接数据ID重命名,选择需要重命名的数据,双击第一个ID输入起始数值,enter确定,所有选择ID将会以增量为1重命ID。

3、调整焊接边距,如果存在上下两块板位置不正确,生成的连接数据就就如图所示,焊接数据右端超出网格区域。如何调整?

选择需要调整的焊接数据,右键Edit Margins,距离只能缩短不能变长,右键点击端头即可拖动。

如果命令行报出无法投影切割,帮助文档给出的解决办法,就是调整焊接边距。

调整效果如图,端头网格得以保证

4、调整焊接方向与搜索距离,在生成特殊的焊缝时,焊接方向同样特别重要,默认的焊接方向可能导致无法成功生成,这就需要手动调整焊接方向。焊接方向箭头应该是朝向焊枪的方向。

选择需要调整的焊接数据,右键Set Weld Position。

工作区左下角弹出操作说明

Right-Drag arrow end to rotate itx

Left-Drag arrow end to resize it

Shift+left-Click to reset position

Shift+Right-Drag arrow end to move along curve

左键可以调整搜索距离,右键可以调整焊接方向。shift+左键数据重置。

晚安

每日一语

完成伟大的事业不在于体力,而在于坚韧不拔的毅力。

来源:TodayCAEer
ANSA焊接
著作权归作者所有,欢迎分享,未经许可,不得转载
首次发布时间:2024-08-14
最近编辑:27天前
TodayCAEer
本科 签名征集中
获赞 16粉丝 8文章 163课程 0
点赞
收藏
作者推荐

HyperWork 2024 -二次开发-Tcl语言-Namespaces(10/12)

NamespacesprovideameansoforganizingproceduresandvariablesinTcl.Anamespacebasicallycreatesauniquelocalscope.Withineachuniquescope,variablesandprocedurescreatedinthatscopeareisolatedfromboththeglobalscopeandfromotherscopes.Thisallowsthedeveloperameanstosegregateproceduresandvariablesinanorganizedmanner.Namespacescanbenested,andproceduresandvariablescanbeimportedto,exportedfrom,andreferencedinothernamespacesortheglobalscope.Thefollowingdiagramshowsavisualrepresentationoftheglobalscopeandseveraldifferentnamespaces,includingvariablesandproceduresdefinedineach.AglobalprocedureactsjustlikeanyfunctionwithinTcl.Aglobalprocedurecanbecalledfromanamespacewithoutanyneedtoimportorotherwiselocalizetheprocedure.Aprocedurewithinanamespaceislocaltothenamespaceunlessitisexplicitlycalledortheprocedureisexportedfromthenamespace.Theglobalscopeisalsodesignedsuchthatanyvariablesdefinedoutsideofaprocedureoranamespaceareautomaticallyintheglobalscope.Toaccessaglobalvariableinalocalscope,suchasaprocedureornamespace,youwillneedtousetheglobalcommand.Asascriptgrowsandasthenumberofscriptsrunningsimultaneouslyincreases,theabilityofthedevelopertoavoidconflictbetweenthenamesofproceduresandvariablesdefinedintheglobalscopedecreases.ThefollowingTclcodedemonstrateshowtheglobalcommandpermitsaccesstoglobalvariablesinalocalscope.setf&quot;Thisisaglobalvariable&quot;;#Thisprocedurecannotaccesstheglobalvariablef.proctestproc1{}{catch{puts$f}val;puts$val;}#Thisprocedurecanaccesstheglobalvariablefusingtheglobalcommand.proctestproc2{}{globalf;catch{puts$f}val;puts$val;}testproc1;can&#39;tread&quot;f&quot;:nosuchvariabletestproc2;ThisisaglobalvariableLikewise,anyvariabledeclaredasglobalfromwithintheprocedurewherethevariableisdefinedisalsoincludedintheglobalscope,oncetheprocedurehasbeenrun.Anyattempttoaccessthevariablebeforerunningtheprocedurewillcauseanerror.Theupvarcommandcanbeusedtochangetheavailabilityofavariablebyprovidingapointertothesourcevariable’scontents.Namespacesaddanotherlevelofsyntaxtoprocedureandvariablenames.Adoublecolon::istheseparatorbetweennamespacenamesandprocedure/variablenames.Anexampleofanamespacecalledmy_namespacewouldbe::my_namespace.Theglobalnamespaceindicatorisjustthedoublecolon.Thismeansthatinsteadofusingtheglobalcommand,itisalsopossibletoreferenceglobalvariablesinsideproceduresusingtheglobalnamespaceindicator.set::element_list&quot;12345&quot;;proc::element_info{}{puts$::element_list;set::node_list&quot;10203040&quot;;puts$::node_list;}element_info;1234510203040puts$::element_list;12345puts$::node_list;10203040However,usingglobalvariablesisriskybecausetheymayconflictwithvariablesorproceduresdefinedintheglobalscopeofotherTclscripts.Instead,user-definednamespacesarerecommended.Thefollowingtablecontainssomecommonlyusednamespacecommandsandasummaryoftheirusage.Formorein-depthexplanationsandacompletelisting,referredtohttp://www.tcl.tk/man/ortoaTcl/Tkhandbook.namespaceevalnameUsedtodefineanamespaceortoruncommandsinsideanamespace.namespacecurrentReturnsthequalifiednameofthecurrentnamespace.namespacedeleteDeletesandexistingnamespace.namespaceexistsCheckfortheexistenceofanamespace.variableUsedtodefine,andoptionallyassignavalueto,avariablewithinanamespace.ThevariablecommandcanbeusedtosharevariablesbetweenproceduresandthemainbodyoftheTclscript.namespaceeval::my_namespace{variableelement_list&quot;12345&quot;;}proc::my_namespace::element_info{}{variableelement_list;puts$element_list;variablenode_list&quot;10203040&quot;;puts$::node_list;}::my_namespace::element_info;1234510203040puts$::my_namespace::element_list;12345puts$::my_namespace::node_list;10203040Thefollowingcodegivesexamplesofhowvariablesandprocedurescanbemanipulatedfromnamespaces,procedures,andtheglobalscope.#Scriptbegins.#Defineavariableintheglobalscope.setf&quot;Thisisaglobalvariable&quot;;#Thisglobalprocedurewillgenerateanerrorbecausethe#globalvariablefisnotinthescope.proctestproc1{}{catch{puts$f}g;puts$g;}#Thisprocedurewillnotgenerateanerrorbecausethe#globalvariablefislocalizedwiththeglobalcommand.proctestproc2{}{globalf;catch{puts$f}g;puts$g;}#Acalltodeletethenamespaceclearsvariableswithin#thatnamespace.catch{namespacedelete::testspace};#Thenamespaceevalcommandcreatesanewnamespace.namespaceeval::testspace{variablefg&quot;Thisisanamespacevariable&quot;;#Exportasingleprocedureforuselater.namespaceexporttproc3}#Procedurescanbeorganizedintonamespaces.proc::testspace::tproc1{}{#Globalproceduresdonotrequireanamespaceindicator.testproc1;testproc2;#Procedureswithinthesamescopedonotrequirea#namespaceindicator.tproc2;tproc3;#Proceduresfromothernamespacesmustbeexplicitlydeclared#unlessanamespaceimportisused.catch{oproc1}ds;puts$ds;::otherspace::oproc1;}#Thisnamespaceprocedurewillgenerateanerrorbecausethe#namespacevariableisnotinthescope.proc::testspace::tproc2{}{#Thecatchcommandisusedtopreventthescriptfrom#exitingwithanerror.catch{puts$fg}g;puts$g;}#Thisnamespaceprocedurewillnotgenerateanerrorbecausethe#namespacevariableislocalized.proc::testspace::tproc3{}{#Thevariablecommand,ifreferringtoanexisting#namespacevariableandnotmakinganassignment,#allowslocalaccesstothevariable.variablefg;catch{puts$fg}g;puts$g;}#Acalltodeletethenamespaceclearsvariableswithin#thatnamespace.catch{namespacedelete::otherspace};#Creatingasecondnamespace.namespaceeval::otherspace{variablefh&quot;Thisisadifferentnamespacevariable&quot;;}proc::otherspace::oproc1{}{#Thenamespaceimportcommandcanbeusedto#localizeprocedures.namespaceimport::testspace::tproc3;variablefh;catch{puts$fh}h;puts$h;tproc3;#namespaceoriginreturnsoriginalnamespaceoftheproc.puts[namespaceorigintproc3];}#Runtheprimaryprocedure::testspace::tproc1Runningthesecommandsgeneratesthefollowingoutput.Someproceduresarecalledmorethanonce,sopaycloseattentiontowheretheprocedurecallismade.can&#39;tread&quot;f&quot;:nosuchvariableThisisaglobalvariablecan&#39;tread&quot;fg&quot;:nosuchvariableThisisanamespacevariableinvalidcommandname&quot;oproc1&quot;ThisisadifferentnamespacevariableThisisanamespacevariable::testspace::tproc3来源:TodayCAEer

未登录
还没有评论
课程
培训
服务
行家
VIP会员 学习 福利任务 兑换礼品
下载APP
联系我们
帮助与反馈