Iso Creation Timeout

Iso Creation Timeout

Anonymous
Not applicable
1,831 Views
5 Replies
Message 1 of 6

Iso Creation Timeout

Anonymous
Not applicable

When creating an Iso from a .PCF the project and split settings are set to force the line-number onto one sheet to create a system Iso (the pipework will arrive in prefabricated modules stacked 3 high to make up a riser).The fabricator wants to see the piping system interacting between the three modules so that he can decide where to make the physical splits for assembly (although we, the designers, are deciding where the module splits are located....)

 

During creation from PCF to Iso the Iso generally times out especially when 1 line number is used throughout the entire modular system - (the pipework gets intricate).  Please does anybody know of the correct .XML settings that will allow a more complex Iso to be created on one sheet in order to overcome this issue?

 

I'm currently looking at the LayoutOptimization settings in the .XML but would like to avoid to much unnecessary experimentation if there is an answer already out there...

 

I will be able to add some screenshots in the morning if that's helpful.

 

Many thanks

0 Likes
1,832 Views
5 Replies
Replies (5)
Message 2 of 6

dgorsman
Consultant
Consultant

Screenshots of the piping arrangement would be helpful, indeed.  If you are trying what I *think* you're trying... that might not be possible for an isometric.

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.


0 Likes
Message 3 of 6

Anonymous
Not applicable
Thanks for your reply, I'll post some shots when I get in to work in a
couple hours.

Regards, Stuart
0 Likes
Message 4 of 6

Anonymous
Not applicable

Here are some shots of the riser and it's contents.  I'm currently working on the CHWF line.  We're not using P&ID links so have control of the line numbering through the assignment of lines. 

 

 

0 Likes
Message 5 of 6

Anonymous
Not applicable

Here are some shots of the riser and it's contents.  I'm currently working on the CHWF line.  We're not using P&ID links so have control of the line numbering through the assignment of lines. 

 

RA06_CHWF_01.pngRA06_CHWF_Module_01.pngRA06_CHWF_Module_02.pngRA06_CHWF_Module_03.pngRA06_CHWF_03.pngRA06_CHWF_02.pngRA06_All.pngRA06_MULTI_02.pngRA06_MULTI_01.png

0 Likes
Message 6 of 6

jason.drew
Community Manager
Community Manager

The default timeout value for PnPIso.exe.config is 30 minutes. Please try this:

 

Modify PnPIso.exe.config located in the following folder using an XML editor such as XML Notepad 2007

 

C:\Program Files\Autodesk\AutoCAD 2017\PLNT3D

 

Change 'sendTimeout' value to the desired limit in minutes. This example below is setting the timeout for 1 hour and 30 minutes:

 

<?xml version="1.0"?>
<configuration>
  <configSections>
    <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
      <section name="Autodesk.ProcessPower.Iso.Runtime.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/>
    </sectionGroup>
  </configSections>
  <applicationSettings>
    <Autodesk.ProcessPower.Iso.Runtime.Properties.Settings>
      <setting name="ConfigFile" serializeAs="String">
        <value>IsoConfig.xml</value>
      </setting>
      <setting name="MaxIsoEngineInstances" serializeAs="String">
        <value>-1</value>
      </setting>
    </Autodesk.ProcessPower.Iso.Runtime.Properties.Settings>
  </applicationSettings>
  <system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="SimpleServiceBehavior">
          <serviceMetadata httpGetEnabled="false" policyVersion="Policy15"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <services>
      <service behaviorConfiguration="SimpleServiceBehavior" name="Autodesk.ProcessPower.Iso.Runtime.IsoService">
        <endpoint address="isoservice" binding="netNamedPipeBinding" bindingConfiguration="IsoServiceBinding" contract="Autodesk.ProcessPower.Iso.Runtime.IIsoService"/>
        <endpoint address="isoservice/mex" binding="mexNamedPipeBinding" contract="IMetadataExchange"/>
      </service>
      <service behaviorConfiguration="SimpleServiceBehavior" name="Autodesk.ProcessPower.Iso.Runtime.IsoEngine">
        <endpoint address="isoengine" binding="netNamedPipeBinding" bindingConfiguration="IsoEngineBinding" contract="Autodesk.ProcessPower.Iso.Runtime.IIsoEngine"/>
        <endpoint address="isoengine/mex" binding="mexNamedPipeBinding" contract="IMetadataExchange"/>
      </service>
    </services>
    <client>
      <endpoint
          name="IsoEngineService"
          binding="netNamedPipeBinding"
          bindingConfiguration="IsoEngineBinding"
          contract="Autodesk.ProcessPower.Iso.Proxy.IIsoEngine"/>
    </client>
    <bindings>
      <netNamedPipeBinding>
        <binding name="IsoServiceBinding"
                 receiveTimeout="24:00:00"/>
        <binding name="IsoEngineBinding"
                 sendTimeout="00:90:00"
                 receiveTimeout="00:40:00"/>
      </netNamedPipeBinding>
    </bindings>    
  </system.serviceModel>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
  </startup>
  <runtime>
    <gcConcurrent enabled="false"/>
  </runtime>
</configuration>

 



Jason Drew
Designated Support Specialist