General Mechanical

General Mechanical

Topics relate to Mechanical Enterprise, Motion, Additive Print and more

moving heat source error

    • Hasan İlker ÇELİKER
      Subscriber

      *** ERROR ***                           CP =    3419.344   TIME= 23:27:45
       Subscript range error.  Parameter PT_LEN1 is dimensioned as 203 x 1,   
       but location -1 x 1 is being requested                                 
                                                                              

       *** ERROR ***                           CP =    3419.344   TIME= 23:27:45
       No data exists for dimensioned parameter PT_LEN1 with subscripts -1 x  
       1.                                                                     

       *** ERROR ***                           CP =    3419.344   TIME= 23:27:45
       The above error occurred processing field= DIST1-PT_LEN1(LOC31,1)      
        Line= *SET,RT,                                                        
       ((DIST%INDEX(INC2,1)%-PT_LEN%INDEX(INC2,1)%(LOC3%INDEX(INC2,1)%,1))/(PT
       _LEN%INDEX(INC2,1)%(LOC2%INDEX(INC2,1)%,1)-PT_LEN%INDEX(INC2,1)%(LOC3%I
       INDEX(INC2,1)%,1).           

       

       

      how can I fix this error?

    • Aniket
      Forum Moderator

      Hi can you please provide some more information about your setup? which version are you using for workbench? Are you using free extension for moving heat source? which version are you using for that?

      -Aniket

      Forum Rules & Guidelines

    • Bill Bulat
      Ansys Employee

       

       

      Here's a couple of exerpts from our records. I'm not sure these will help... it's all I was able to find from a search on "PT_LEN1":

       

      PT_LEN1 is the array to store the incremental length of the path based on the nodes.

      ...Now if these are not the problems. It is very likely that the problem is resulting due to 2 issues:Make sure that the Last Patch in the details of the Heat Flux is turned on.The time you are inputting is causing an issue. Basically the end time (5sec) may be too off. The idea is to round it off to the next integer so if the path is 0.015m long and velocity is 0.005. It would take 3sec. So if the model takes 2.7 sec (let's say) then make it 3sec. Also make sure that the step end time is long enough in your analysis settings.

       

      --Bill

    • Hasan İlker ÇELİKER
      Subscriber

      I am using version 2022R2.

Viewing 3 reply threads
  • You must be logged in to reply to this topic.