Fluidstream Troubleshooting

When the Fluidstream Simulation does not behave as expected, the issue typically falls into one of two categories:

💡 Before troubleshooting, always check the Neighbours Map (Show Neighbours Map on the Module Ribbon) — it shows exactly how AseptSoft connected all entities and which mapper rule was used for each connection. This is your primary diagnostic tool.

🔍 Troubleshooting Workflow

Follow this general approach for any Fluid Stream problem:

📘 Example 1: Unrecognised Component

Problem: You encounter an AutoCAD component that has not been set up during the First Time Setup. For example, when a new P&ID is loaded that contains an object type that was not present in the original PIDs used for the initial configuration.

Symptom: Fluid stops at or flows through the component incorrectly because AseptSoft does not know what class (Valve, Clamp, Tank, etc.) to assign it.

Solution: This requires the AseptSoft development team to update the First Time Setup. Contact support and provide:

• The P&ID file containing the new component

• A description or screenshot of the unrecognised object

• The expected behaviour (should it block fluid? allow? generate?)

📘 Example 2: Fluid Jumping Between Lines

Problem: Fluid appears to jump from a vertical line to a horizontal line unexpectedly.

Symptom: Two vertical lines end on the same horizontal line. The Endpoint Proximity Mapping connects all three endpoints together, creating an unintended junction.

Solution: Either:

• Create a gap between the two vertical lines and the horizontal line so they are no longer within the Tolerance Distance

• Make the horizontal line continuous instead of having two separate vertical lines ending on it

• Adjust the Tolerance Distance if the false connection occurs at a very small distance

ℹ️ Why this happens: When two line endpoints are within the Tolerance Distance of the same entity, they all become connected. Ensure that lines that should be separate have sufficient spacing.

📘 Example 3: Fluid in Non-Pipe Lines

Problem: Fluid is visible in lines that are not pipe lines — for example, wall lines or instrumentation signal lines.

Symptom: Coloured overlay appears on lines that represent walls, signal paths, electrical connections, or construction geometry.

Solution:

1. Identify the layer — Use AutoCAD's Q-Select (Quick Select) to determine which layer these lines are on

2. Check impact first — Before disabling the layer, use Q-Select to review what other entities share the same layer. You do not want to accidentally exclude pipe lines

3. Disable the layer — Open the Layer Settings from the Module Ribbon → Simulations panel and set the problematic layer to Forbidden

4. Clear Cache and re-run the simulation

⚠️ Caution: Always check the full impact of disabling a layer using Q-Select before making changes. Some PIDs place both pipes and non-pipe elements on the same layer.

📘 Example 4: Lines Not Connecting (Fluid Won't Jump a Gap)

Problem: Two pipe lines are close to each other but the fluid does not jump between them.

Symptom: The Neighbours Map shows no blue connection line between the two pipes.

Solution: Check which mapping strategy should handle this gap:

If no mapper can handle the gap, use the AseptSoft Connector to manually create connection points.

📘 Example 5: Coloured Objects in Black-and-White Viewport

Problem: Even though the AseptSoft viewport is set to black and white, some coloured objects remain visible in the drawing, making it hard to see the Fluid Stream overlay.

Symptom: Non-simulation colours interfere with the visual readability of the fluid flow overlay.

Solution: This is an AutoCAD display setting issue:

1. Check your Visual Style settings in AutoCAD

2. Ensure the viewport's colour override is properly configured

3. The Fluid Stream overlay uses its own layers (AseptSoft FluidFlow and AseptSoft Empty FluidFlow) — these are always coloured regardless of viewport settings

4. Use the LWEIGHT command and enable Display Lineweight for improved overlay visibility

📘 Example 6: New Object Type Not Handled

Problem: A P&ID contains a component type that AseptSoft has never encountered before, and the Fluid Stream either ignores it or connects to it incorrectly.

Symptom: The object was not part of the original First Time Setup classification.

Solution: Contact the AseptSoft development team to add the new object type to the classification. Provide:

• The P&ID drawing file

• The block name of the unrecognised component

• The expected fluid behaviour (Allow, Deny, Generate, etc.)

Until the classification is updated, you can use the AseptSoft Connector command to manually define connection points for the unrecognised object.

🛠️ Quick Reference: Diagnostic Tools

🔗 Related Pages

• Fluidstream Simulations — Main overview of how the simulation works

• Fluidstream Mapping Strategies — Detailed description of all mapping algorithms and their tolerance settings

• First Time Setup — Initial configuration performed by the development team

• Module Ribbon — Simulations panel controls

• Engineering Items — Valves, instruments, and fittings

• State — Determines how each item responds to fluid