Dear Team,
May i know below specifications diptrace supported.
a) Capture - It should have Tcl programming interface which provides programming access to the user interface, command structure, connectivity objects, and design database.
b) Component Information system - CIS should work with databases that comply with Microsoft’s ODBC standard to directly access data in an MRP, ERP, or PLM system, or in an inter¬mediate database dedicated to engineering component data.
c) PCB layout - It should have SPECCTRA® for automatic and auto-interactive interconnect routing for handling routing challenges from contemporary designs to high-density multilayer PCBs requiring complex design rules.
Diptarce Feature
Re: Diptarce Feature
a. There is no Tcl programming interface in DipTrace Schematic. But we develop export to XML format that will allow to create custom scripts easier than with DipTrace ASCII format.
b. DipTrace doesn't allow to work with libraries as database, we will consider this feature.
c. You can export your board to Autorouter DSN format, then open DSN file either in Specctra or Electra or other compatible autorouter. After autorouting in third-party router, save SES file and import it in DipTrace.
b. DipTrace doesn't allow to work with libraries as database, we will consider this feature.
c. You can export your board to Autorouter DSN format, then open DSN file either in Specctra or Electra or other compatible autorouter. After autorouting in third-party router, save SES file and import it in DipTrace.
Re: Diptarce Feature
a. tcl: http://tech.saigonist.com/b/code/why-tc ... guage.html - to add scripting means opening the API then maintaining and supporting it, at the least one more body.Alex wrote: ↑04 Aug 2021, 07:22 a. There is no Tcl programming interface in DipTrace Schematic. But we develop export to XML format that will allow to create custom scripts easier than with DipTrace ASCII format.
b. DipTrace doesn't allow to work with libraries as database, we will consider this feature.
c. You can export your board to Autorouter DSN format, then open DSN file either in Specctra or Electra or other compatible autorouter. After autorouting in third-party router, save SES file and import it in DipTrace.
b. When you step into the world of E.F. Codd you best have deep pockets, I worked with ESRI on moving to SDE, their front end to the different RDBMS systems, I was one of many Oracle people. At a city, state, nation level a database is a must for ESRI, for circuit boards big enterprise players with many designers gain with a database but for the Diptrace 'market' a database would just add a level of complexity and cost your users don't need or want.
c. RTM
-
- Posts: 5
- Joined: 24 Apr 2018, 05:38
Re: Diptarce Feature
Dear Team,
Thanks for the answers.
Thanks for the answers.
-
- Posts: 2
- Joined: 21 Oct 2024, 09:14
Re: Diptarce Feature
Could you kindly provide information regarding the following specifications for DipTrace?
a) Capture: Is there a Tcl programming interface available? This would allow programming access to the user interface, command structure, connectivity objects, and design database. Having this would be particularly useful for automation and custom script integration, similar to how ERP systems like Odoo offer flexibility through their modular and customizable framework.
b) Component Information System (CIS): Does DipTrace’s CIS module support databases that comply with Microsoft’s ODBC standard? The goal is to directly access data from systems like MRP, ERP (for example, Odoo), or PLM systems. Seamless integration with an ERP system is essential for keeping engineering component data synchronized with procurement and inventory.
c) PCB Layout: Does it include SPECCTRA® for automatic and auto-interactive interconnect routing? This capability is crucial for addressing routing challenges in contemporary designs, particularly for high-density, multilayer PCBs that require complex design rules, which would enhance our production efficiency much like how an ERP system optimizes resource management.
Looking forward to your feedback on these features!
a) Capture: Is there a Tcl programming interface available? This would allow programming access to the user interface, command structure, connectivity objects, and design database. Having this would be particularly useful for automation and custom script integration, similar to how ERP systems like Odoo offer flexibility through their modular and customizable framework.
b) Component Information System (CIS): Does DipTrace’s CIS module support databases that comply with Microsoft’s ODBC standard? The goal is to directly access data from systems like MRP, ERP (for example, Odoo), or PLM systems. Seamless integration with an ERP system is essential for keeping engineering component data synchronized with procurement and inventory.
c) PCB Layout: Does it include SPECCTRA® for automatic and auto-interactive interconnect routing? This capability is crucial for addressing routing challenges in contemporary designs, particularly for high-density, multilayer PCBs that require complex design rules, which would enhance our production efficiency much like how an ERP system optimizes resource management.
Looking forward to your feedback on these features!
-
- Posts: 2
- Joined: 26 Sep 2024, 11:32
Re: Diptarce Feature
DipTrace supports exporting boards to the DSN format, allowing routing in Specctra or compatible routers like Electra. You can import the SES file back into DipTrace post-routing, which enables advanced routing workflows without native integration. Here, they have a section on third-party autorouter integration, which details exporting the PCB layout to DSN format for use in tools like Specctra and Electra and re-importing SES files after routing.