Commercial use and roadmap for the new Fusion Electronics Python API

Commercial use and roadmap for the new Fusion Electronics Python API

970070B967T
Observer Observer
54 Views
1 Reply
Message 1 of 2

Commercial use and roadmap for the new Fusion Electronics Python API

970070B967T
Observer
Observer

Hi,

I've been experimenting with the new Fusion Electronics Python API that was introduced in May, as I'm looking into building a commercial add-in around PCB analysis.

I'm testing on Fusion 2704.1.53 at the moment.

So far I've been able to access things like the active Board, signals, wires, layers, vias, polygons, and the Electronics export manager at runtime. The issue I've run into is that the relevant adsk.electron classes all seem to still be marked as Preview in the API documentation.

From what I understand, Autodesk's guidance is that Preview API functionality shouldn't be used in distributed applications, so I wanted to check whether I'm interpreting that correctly.

A few things I'm particularly interested in:

1. Is it currently OK for a commercial Fusion add-in to depend on classes such as Board, Signal, Wire, Layer, Via, etc., or should these not be used in a distributed add-in until they leave Preview?

2. Is there any rough roadmap for when the main Electronics API objects are expected to become released/stable?

3. Is there currently another released API route for getting routed PCB geometry, or is the new Electronics API the intended way forward?

I've also been trying to find access to the actual physical/electrical PCB stack-up. In particular things like dielectric thickness, copper thickness, dielectric material and relative permittivity. I haven't been able to find these exposed through the API so far. Is that functionality available somewhere I've missed, or is stack-up access something that's planned for the Electronics API later?

Finally, I noticed that Board.exportManager can create an EAGLE-compatible .brd export, but those export classes also appear to be Preview. Is programmatic .brd export expected to become a supported route for third-party commercial add-ins?

I'm mainly trying to work out whether it's sensible to start building against the Electronics API now, knowing that it may become stable later, or whether it's better to wait for more of the API to move out of Preview first.

Any clarification on the intended direction of the Electronics API would be really helpful.

Thanks!

0 Likes
55 Views
1 Reply
Reply (1)
Message 2 of 2

bhavani_sankuratri
Autodesk
Autodesk

Hi @970070B967T ,

 

Hope you are doing good! Just checking in to see if your questions have been answered. If you still need any assistance, please let us know.

Bhavani Sankuratri | Community Manager
0 Likes