http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/ SolidWorks Tips, Tricks and Partner Reviews Thu, 15 Dec 2011 02:20:17 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-25 Alan K. Thu, 05 Feb 2009 03:07:40 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-25 Roger, It sounds like you've experimented with the libraries in CircuitWorks? I'm having a problem moving my work back & forth between home & office; when I open an idf file at home, transfer the library to work, and then try to open it at work the parts seem to rotate around or don't appear at all. Any advice? I also tried the Desktop EDA program which I liked very much, but it's not fully running on my 64 bit OS. I considered going back to a 32 bit OS, but haven't made a final decision yet. So far the Desktop EDA has been easier to use, and functions better than CW. Also, spending $3,500 on SW premium just to get Circuitworks is not very appealing. Roger,
It sounds like you’ve experimented with the libraries in CircuitWorks? I’m having a problem moving my work back & forth between home & office; when I open an idf file at home, transfer the library to work, and then try to open it at work the parts seem to rotate around or don’t appear at all. Any advice? I also tried the Desktop EDA program which I liked very much, but it’s not fully running on my 64 bit OS. I considered going back to a 32 bit OS, but haven’t made a final decision yet. So far the Desktop EDA has been easier to use, and functions better than CW. Also, spending $3,500 on SW premium just to get Circuitworks is not very appealing.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-1260 Alan K. Thu, 05 Feb 2009 03:07:00 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-1260 Roger, It sounds like you've experimented with the libraries in CircuitWorks? I'm having a problem moving my work back & forth between home & office; when I open an idf file at home, transfer the library to work, and then try to open it at work the parts seem to rotate around or don't appear at all. Any advice? I also tried the Desktop EDA program which I liked very much, but it's not fully running on my 64 bit OS. I considered going back to a 32 bit OS, but haven't made a final decision yet. So far the Desktop EDA has been easier to use, and functions better than CW. Also, spending $3,500 on SW premium just to get Circuitworks is not very appealing. Roger,
It sounds like you’ve experimented with the libraries in CircuitWorks? I’m having a problem moving my work back & forth between home & office; when I open an idf file at home, transfer the library to work, and then try to open it at work the parts seem to rotate around or don’t appear at all. Any advice? I also tried the Desktop EDA program which I liked very much, but it’s not fully running on my 64 bit OS. I considered going back to a 32 bit OS, but haven’t made a final decision yet. So far the Desktop EDA has been easier to use, and functions better than CW. Also, spending $3,500 on SW premium just to get Circuitworks is not very appealing.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-24 Roger Castro Tue, 02 Dec 2008 01:51:25 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-24 I've used both Circuitworks and Desktop EDA's ECAD to MCAD conversion to create Solidworks 3D PCBs for about 5 years. Yes, both Circuitworks and Desktop EDA will make a 3D; but, Circuitworks only uses the IDF format which, if it isn't version 4, does not support traces, pads, silk screens, or layers. Since most PCB CAD systems at this time only output IDF version 2 or 3, all you get is a dumb board with parts and holes....and depending on the PCB design system used, the self extracting 3D of a component from IDF is not always very concise. That's why I only use components I have in my Solidworks 3D libraries, which are cross matched with the schematic and its PCB component footprint. I guess you could say the PCB 3D is therefore schematic driven. I use Desktop EDA because its a direct link between Altium and the Solidworks platform. No muss no fuss. Setup is easy and you can have a Solidworks 3D in a short period of time. I can produce very realistic 3Ds of PCBs to prepare documentation from everything to just PCB assembly, to product integration, to test fixture design. When sending PCB information to vendors I've had more than one ask how such a document was created.....and checking alignment on a PCB in a spring pin test fixture with an overclamp lid assembly is easy to do. No more crushed components or broken spring pins. You know the dimensioning is correct before you order the fixture. (WOW! Do it right the first time)...Even the interface PCBs contained within the test fixture are in 3D. **Roger, thank you for your comment. My reviews tend to be superficial as many of the products are ones that I don't need in my day-to-day activities and I just don't have the time to get as in-depth as I'd like. Comments like yours are extremely beneficial to others. ** I’ve used both Circuitworks and Desktop EDA’s ECAD to MCAD conversion to create Solidworks 3D PCBs for about 5 years. Yes, both Circuitworks and Desktop EDA will make a 3D; but, Circuitworks only uses the IDF format which, if it isn’t version 4, does not support traces, pads, silk screens, or layers. Since most PCB CAD systems at this time only output IDF version 2 or 3, all you get is a dumb board with parts and holes….and depending on the PCB design system used, the self extracting 3D of a component from IDF is not always very concise. That’s why I only use components I have in my Solidworks 3D libraries, which are cross matched with the schematic and its PCB component footprint. I guess you could say the PCB 3D is therefore schematic driven.
I use Desktop EDA because its a direct link between Altium and the Solidworks platform. No muss no fuss. Setup is easy and you can have a Solidworks 3D in a short period of time. I can produce very realistic 3Ds of PCBs to prepare documentation from everything to just PCB assembly, to product integration, to test fixture design.
When sending PCB information to vendors I’ve had more than one ask how such a document was created…..and checking alignment on a PCB in a spring pin test fixture with an overclamp lid assembly is easy to do. No more crushed components or broken spring pins. You know the dimensioning is correct before you order the fixture. (WOW! Do it right the first time)…Even the interface PCBs contained within the test fixture are in 3D.
**Roger, thank you for your comment. My reviews tend to be superficial as many of the products are ones that I don’t need in my day-to-day activities and I just don’t have the time to get as in-depth as I’d like. Comments like yours are extremely beneficial to others. **

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-1259 Roger Castro Tue, 02 Dec 2008 01:51:00 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-1259 I've used both Circuitworks and Desktop EDA's ECAD to MCAD conversion to create Solidworks 3D PCBs for about 5 years. Yes, both Circuitworks and Desktop EDA will make a 3D; but, Circuitworks only uses the IDF format which, if it isn't version 4, does not support traces, pads, silk screens, or layers. Since most PCB CAD systems at this time only output IDF version 2 or 3, all you get is a dumb board with parts and holes....and depending on the PCB design system used, the self extracting 3D of a component from IDF is not always very concise. That's why I only use components I have in my Solidworks 3D libraries, which are cross matched with the schematic and its PCB component footprint. I guess you could say the PCB 3D is therefore schematic driven. I use Desktop EDA because its a direct link between Altium and the Solidworks platform. No muss no fuss. Setup is easy and you can have a Solidworks 3D in a short period of time. I can produce very realistic 3Ds of PCBs to prepare documentation from everything to just PCB assembly, to product integration, to test fixture design. When sending PCB information to vendors I've had more than one ask how such a document was created.....and checking alignment on a PCB in a spring pin test fixture with an overclamp lid assembly is easy to do. No more crushed components or broken spring pins. You know the dimensioning is correct before you order the fixture. (WOW! Do it right the first time)...Even the interface PCBs contained within the test fixture are in 3D. **Roger, thank you for your comment. My reviews tend to be superficial as many of the products are ones that I don't need in my day-to-day activities and I just don't have the time to get as in-depth as I'd like. Comments like yours are extremely beneficial to others. ** I’ve used both Circuitworks and Desktop EDA’s ECAD to MCAD conversion to create Solidworks 3D PCBs for about 5 years. Yes, both Circuitworks and Desktop EDA will make a 3D; but, Circuitworks only uses the IDF format which, if it isn’t version 4, does not support traces, pads, silk screens, or layers. Since most PCB CAD systems at this time only output IDF version 2 or 3, all you get is a dumb board with parts and holes….and depending on the PCB design system used, the self extracting 3D of a component from IDF is not always very concise. That’s why I only use components I have in my Solidworks 3D libraries, which are cross matched with the schematic and its PCB component footprint. I guess you could say the PCB 3D is therefore schematic driven.
I use Desktop EDA because its a direct link between Altium and the Solidworks platform. No muss no fuss. Setup is easy and you can have a Solidworks 3D in a short period of time. I can produce very realistic 3Ds of PCBs to prepare documentation from everything to just PCB assembly, to product integration, to test fixture design.
When sending PCB information to vendors I’ve had more than one ask how such a document was created…..and checking alignment on a PCB in a spring pin test fixture with an overclamp lid assembly is easy to do. No more crushed components or broken spring pins. You know the dimensioning is correct before you order the fixture. (WOW! Do it right the first time)…Even the interface PCBs contained within the test fixture are in 3D.
**Roger, thank you for your comment. My reviews tend to be superficial as many of the products are ones that I don’t need in my day-to-day activities and I just don’t have the time to get as in-depth as I’d like. Comments like yours are extremely beneficial to others. **

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-23 Steve Kith Mon, 18 Feb 2008 21:24:45 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-23 Circuitworks has been very impressive until I've found this problem. There's a glitch that I've found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there's a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority. Circuitworks has been very impressive until I’ve found this problem. There’s a glitch that I’ve found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there’s a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-1258 Steve Kith Mon, 18 Feb 2008 21:24:00 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-1258 Circuitworks has been very impressive until I've found this problem. There's a glitch that I've found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there's a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority. Circuitworks has been very impressive until I’ve found this problem. There’s a glitch that I’ve found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there’s a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-22 Steve Kith Mon, 18 Feb 2008 20:55:59 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-22 Circuitworks has been very impressive until I've found this problem. There's a glitch that I've found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there's a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority. Circuitworks has been very impressive until I’ve found this problem. There’s a glitch that I’ve found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there’s a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-1257 Steve Kith Mon, 18 Feb 2008 20:55:00 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-1257 Circuitworks has been very impressive until I've found this problem. There's a glitch that I've found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there's a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority. Circuitworks has been very impressive until I’ve found this problem. There’s a glitch that I’ve found when I would export out an IDF file back to the layout tool. If your Solidworks part model contains a translation/rotation feature, the IDF file will interpret that and add another translation/rotation to the ECAD model. This is pretty frustrating if you have more than one iteration. For example, the first import from ECAD to MCAD works great, the next export from MCAD to ECAD may have problems if there’s a translation/rotation in the model because it translate and rote it again. My current fix is to only import from ECAD. This is currently working but not as effective as the software claims to be. I will probably look into Desktop EDA and see how the software compares. Also, Paul at Circuit works is aware of the problem, not sure what they are doing about it. Maybe customer pressure will encourage them to make it a priority.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-21 Jeff Mirisola Thu, 23 Aug 2007 00:53:24 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-21 Scott, I wish I could give you a good answer, but I don't know. I never tried CircuitWorks. Scott,
I wish I could give you a good answer, but I don’t know. I never tried CircuitWorks.

]]> http://www.jeffmirisola.com/2006/11/desktop-eda-the-review/comment-page-1/#comment-1256 Jeff Mirisola Thu, 23 Aug 2007 00:53:00 +0000 http://jeffsblog.solidworksheard.com/?p=31#comment-1256 Scott, I wish I could give you a good answer, but I don't know. I never tried CircuitWorks. Scott,
I wish I could give you a good answer, but I don’t know. I never tried CircuitWorks.

]]>