Skip to main content

Unsupported cables

Error ID: 3104
Platform: Process Simulate
Severity: Warning (informational only)

Resolver detected TxCable devices in the station. TxCable is currently not supported by export, so these cables are excluded.

Dialog text shown in Resolver​

TxCable devices:
{cableName1}
{cableName2}
...

These cables are not of supported type and will be excluded from export.

Unsupported cables warning with export dynamic link attachments enabled

Warning visibility

If message visibility looks inconsistent, check whether Do not show this again was selected earlier. Reloading the study (or opening a new one) is a practical way to re-validate expected warning behavior.

Effect in Resolver engine​

When TxCable is excluded, cable geometry is not loaded into the Resolver engine for this export.

TxCable not loaded in Resolver engine

The highlighted area shows the expected cable region missing in the engine representation.

Key behavior​

  • This warning is about TxCable specifically.
  • It can still appear even when Export dynamic link attachments is enabled.
  • Enabling the option does not make TxCable exportable today.

For troubleshooting related to this option, see Dynamic devices filtered.

How this differs from Dynamic devices filtered (3101)​

  • 3101 Dynamic devices filtered: generic dynamic attachment devices filtered (commonly when option is disabled).
  • 3104 Unsupported cables: TxCable objects are unsupported and excluded regardless.

Both warnings may be seen in the same project depending on model content and option state.

How to troubleshoot​

  1. Confirm that listed objects are TxCable devices.
  2. Evaluate whether excluding those cables affects your collision confidence for this study.
  3. If cable behavior is critical, use a supported approximation in the station model for export workflow.
  4. Re-run export and confirm only expected warnings remain.

When it is usually safe to continue​

You can usually continue when:

  • cables are not collision-critical for the analyzed motion,
  • you are running early-stage validation,
  • you accept that cable physics/geometry is not included in Resolver export.

For production decisions with tight cable clearance, use additional validation in Process Simulate.