Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 15076
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to complete the loop of ECAD-MCAD collaboration using IDX format in 17.2

smenin

Is anybody using the IDX format?  We have used IDF for years, but are starting to transition to IDX.  We did testing using 16.6, and after a few bumps were smoothed out, we thought we had the process down.  The projects we started to use it with happened to be 17.2 designs, but that shouldn't have been a problem.  What we found was that 17.2 is unable to import MCAD acceptances of changes made by ECAD, so the propose-accept loop of the IDX process cannot be completed.

  • We started with a baseline in Creo, saved to IDX and imported the holes, outline, areas into Allegro.
  • Components were added in Allegro and exported as an incremental IDX.  These changes were "additions".
  • The IDX is opened in Creo, the changes accepted, and the accepted status saved in the IDX.
  • Importing the IDX back into Allegro is supposed to mark the transactions as accepted in the BRD, but Allegro states "No change to process. The following are up to date: 1. MCAD's proposed transactions. 2. ECAD's approved or rejected transactions."
  • So, if another change is made to any of those components that were already accepted into Creo (but not recorded as accepted in Allegro), the new change is exported as an "addition" again, and Creo can't import because the component already exists! 

Has anyone else experienced this? Have a work around? We opened a case with Cadence, and they've submitted it as a bug report, but don't know how quickly a resolution would be found.

  • S0undman99

    I'm seeing the same thing right now.  If you can assume that everything is accepted by your MCAD team, then you can just re-baseline right after sending out the incremental data, and that will allow you to only send updates for the next incremental.  That's what I'm doing as of right now.  It doesn't work if the MCAD team needs or wants to reject something though (but you could always accept and then send the changes back to ECAD as a request from the MCAD team.  NOT how it's supposed to work, but it could be a workaround until Cadence/PTC figure out what's happening.

  • smenin
    in reply to S0undman99

    Glad to hear it's not just us!  I see the slight workaround to be able to only send new changes.  That might work.  On the Creo side, because the object already exists, the import fails. In order to accept the new changes, if it's an object that already exists, it will have to be deleted from Creo before being able to import the new "addition".  Will report back with any updates.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.