• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. Regarding SI230 OR 610 FEATURES

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 164
  • Views 13192
  • 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

Regarding SI230 OR 610 FEATURES

archive
archive over 19 years ago

Hello all,
i was looking the data sheets Comparision of SI210 230 AND 610 CAN ANY ONE TELL ME WHAT THE BELLOW FEARUEWS MEANS

1) BATCH SIMULATION

2) DIFFERENCIAL SIGNAL CONSTRAINST CAPTURE

3) COUPLED LINE SIMULATION

4) CROSSTALK SIMULATION ( WHICH NOT THERE IN 210 AND PRESENT IN 230)

PLS REPLY FOR THIS IT IS IMPORTANT FOR ME.

ALLEN


Originally posted in cdnusers.org by allen
  • Cancel
Parents
  • archive
    archive over 19 years ago

    Allen:

    The biggest difference between 230 and 610 is that 210 lacks the autorouter and you won't get real time "red" or "green" flags if you are manually routing and you violate or meet constraints. 230 is fine for most pre- and post- layout analysis work. 210 is a subset of 230 which does not let you define constraints for board files. It is good for exploratory work but not really useful in the full design flow.

    You should probably start with 230 if you want to see how the tool can fit into your Allegro design flow.


    Originally posted in cdnusers.org by Kalevi2
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 19 years ago

    Allen:

    The biggest difference between 230 and 610 is that 210 lacks the autorouter and you won't get real time "red" or "green" flags if you are manually routing and you violate or meet constraints. 230 is fine for most pre- and post- layout analysis work. 210 is a subset of 230 which does not let you define constraints for board files. It is good for exploratory work but not really useful in the full design flow.

    You should probably start with 230 if you want to see how the tool can fit into your Allegro design flow.


    Originally posted in cdnusers.org by Kalevi2
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information