Hello,
I’m testing Solidworks (Electrical) 2017 right now. But I experience a strange problem.
When I try to ‘associate’ a part, it is not possible to push the green checkmark after selecting the part.
When I select the part I want to associate, you see it in the ‘Associate component’ box, but after that nothing happens.
Can someone tell me what the problem is? Is it a known issue?
Thanks.
Standard we use version 2015. The part is standard stored in PDM, but because we testing version 2017, I made an export from the part.
Version 2017 is installed on a sperate server/machine. So the part is not read only.
I do all the steps what I normally do in 2015. So I'm wondering that it will not work in 2017.
The assembly is also an export from PDM. So far I know it will be not a difference between working in PDM, and working with export models/parts.
Testing version 2015 on the seperate machine was also not a problem.
The part has no errors or something. And I imported the part with the 'insert' function in the Electrical Manager.
Patrick
Hi Patrick,
I would recommend that you contact your VAR as this is most likely a machine-specific issue. The reason I suspect this is because I've been using SOLIDWORKS Electrical 2017 for a while now and haven't had any issues so far with associating components is concerned.
I hope this helps!
Best,
Loretta
Hello
We are using SWe 2016 (SP3) and there is a major problem with components association.
When using only parts with connection points (EW_cable and c-points), it will work just fine. BUT if you add that part with another one and save it as assembly, the component references with routing will fail if those assemblies are inserted twice (cannot associate with different component reference). Routing should work with assembly components, if there are needed points for cable/wire connection.
Most components are possible to make as a part, but I want use assemblies because of ERP data. Some SWe component are consist with several sub component, like light switch (rocker, frame, switch element and back box). I want that data included to BOM
Now I am using a shortcut/detour and mate connection point-part (just a dummy part with connection points) to every assembly to get routing working. But this solution it's not even close what it should done.
Best regards
Tero Koskinen
Apologies for the late reaction. Due lack of time, I was not able to testing version 2017.
So, it looks like that Solidworks releases a new version were routing is not working?
I hope to do some tests this week, to find out what go’s wrong in SW routing.
Hi
I find solution for use of sub-assemblies. You just have to mate parts on the routing assembly. And I add all component to component/auxiliary parts. Now all those 3D parts are seeing/associated as S2(-switch).
There are major issue with Dassault to get rid of this assembly bug.
Yesterday I tested some situations.
A simple connector to connector connection is no problem. It works fine.
But when I use a 'pack and go' assembly I got the problems what I described in my first post.
I used the two methods to insert a assembly: A new assembly, and the 're use' method.
When I made a simple assembly by my self (two cable entries for example), it is possible to route a cable between two connectors and the cable entries.
Maybe there is something wrong with the pack and go. But this function always worked fine when I need to open a SW assembly in a newer version. The pack and go is from a assembly into PDM.
Another update:
I tried another project. And this work well in the following situation: Tools --> Solidworks Electrical --> Process --> Solidworks assembly, and then select a location. After that I import the assembly.
When I choose 'select existing file' ( and choose the assembly of a product), routing will not work. Parts will not associate.
It looks like that the part is associated, but it is not. I do not get the problems like my first post.
It is nice that the 'normal' way for importing a assembly works well. And that it is possible to route wires and cables in a project.
I don't know why the first project do work. Maybe because the model has configurations? The second project do not have configurations.
Interesting! This isn't a standard behavior.
To diagnose, a couple of questions:
Is the part of question set as read only?
Is the part stored in PDM?
Is the part imported (and if so, was it checked for faulty faces etc)?
Is the part top-level within the assembly (i.e. is it nested within a subassembly or not)?
Thanks,
Loretta