Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

Custom Feature: Cable/Wire Routing

12345679»

Comments

  • eric_pestyeric_pesty Member, pcbaevp Posts: 2,811 PRO

    @NeilCooke,
    Still working on resolving this, I just realized that the extrudes for both stripped ends are created on the same end of the wire. Also a strip length set to 0 causes an error (extrusion fail in the console).

    Stripped ends.gif
  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 6,078 image

    @eric_pesty thanks - I did encounter that recently and fixed it in my test examples - let me look again.

    Senior Director, Technical Services, EMEA
  • Matt_NCMatt_NC Member Posts: 14 PRO
    image.png

    I'm also having the same issue, but it looks like you are on it. If it's helpful info, the extrudes both appear on the "To" end of the wire

  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 6,078 image
    edited July 21

    @eric_pesty @Matt_NC I have just pushed an update to fix the stripped end appearing on the same end of the wire - the logic that was there for years had no right to have ever worked, but now it should be fine.

    @eric_pesty The "connector requires library update" is a catch-all. In this instance, your WAGO connectors are essentially splices (or daisy-chained connectors with more than one wire attached) which is not currently supported. I did mention it in the video but did not point out that this also includes splices. I am currently working on this, but it is a challenge.

    I also fixed the zero length strip value which ended up being a typo in a variable name.

    Senior Director, Technical Services, EMEA
  • eric_pestyeric_pesty Member, pcbaevp Posts: 2,811 PRO

    Thanks for the quick update, the stripped ends are back where they should be!
    I wasn't quite clear what you meant in the video about the "daisy-chain" part but I think I get it now!

  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 6,078 image

    @eric_pesty I also made some adjustments to the Harness layout feature so now you can at least flatten USBIN. The issue there was related to the Wire ref USBBHD having a tiny stub length and a stub offset of zero, therefore leaving a small gap. It works now, but it is better to at least adjust the stub offset to a negative value to ensure the wire touches the back of the connector.

    Senior Director, Technical Services, EMEA
  • eric_pestyeric_pesty Member, pcbaevp Posts: 2,811 PRO

    Thanks Neil, I'll keep the stub offset in mind.
    I was jus messing around with the USB, I don't actually need to flatten this as it's just an OTS part I just use the wiring feature for these as it makes for a nicer workflow.

  • eric_pestyeric_pesty Member, pcbaevp Posts: 2,811 PRO

    Ok, I've had a chance to experiment a bit more and submitted a couple tickets about specific things I'm seeing but I also have a couple "higher level" questions.

    • What I am working on right now is intended to be assembled "in-house" and what I have done in the past is to create an assembly with the wires in a "straight" representation and then used assembly items to indicate qty. of each wire required. This also results in a sort of "library" of wires being created through the items. In the example there is a table showing the lengths of each "run" but that doesn't provide a rolled up qty of each wire or show a part number for the wire to use. Is there a plan for addressing this?
    • Ideally we would have the ability to have pre-defined library of wire and also support for multi-conductor "wires" (i.e. OTS jacketed cables).
    • You mention adding labels and boots, etc… but with this not being an assembly, what is the intended way of showing these in the drawing (especially if they need a part number/description attached)? Would they have to be defined specifically and/or tagged with the right properties to show up in the "cut-list"?
    • How is this intended to function with release management? Right now the 3D harness that would be inserted in the assembly is pretty much completely detached from the straightened version and the drawing so I am wondering how to best manage part numbers and revisions.

    Thanks for the continued effort on this, this is starting to look quite polished!

  • Matt_NCMatt_NC Member Posts: 14 PRO

    I can confirm it has fixed the issue for me 👍🏻

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.