Routed Systems in ETO

[venkatt]

Hi,

I understand that Routed Systems functionality is not available to ETO applications primarily because it does not have a programmable interface (API). So, wondering if there are any other workarounds to using functionality provided by Routed Systems (specifically Cable and Harness) in ETO applications. Perhaps a custom application etc., looking for any ideas to see how this could be done.

Thanks,

Venkatesh.

[FarrenYoung]

First, it looks like you are an Autodesk employee. I'm curious why you are coming here for help instead of going directly to your colleagues.
Second, I've done this via reverse engineering, but as you know this isn't guaranteed to work from version to version or even service pack to service pack as the way routed systems works internally could be changed without notice.

[venkatt]

Thanks for your response. Well, I also wanted to see if customers have had the need for cabling/wiring in their apps and if so how they resolved it. It seems like you reverse engineered Routed Systems to implement your own app/plugin that gives you that same functionality. If yours is a different app from Routed Systems, why are you concerned about updates to Routed Systems (new release or service pack) breaking your app, is that because the functionality provided by your app will not match with the updated Routed Systems?

-Venkatesh.

[venkatt]

Could you please share some details regarding the workaround solution that you built. Also, I'm curious to know whether you were able to read the cable/wire properties (e.g. length, bend radius) by other means, e.g. using the Inventor API.