element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
Forum BUSSES, MODULES and NETS
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 177 subscribers
  • Views 1023 views
  • Users 0 members are here
  • busses
  • nets
  • modules
Related

BUSSES, MODULES and NETS

lostwithouthope
lostwithouthope over 8 years ago

Hi everone,

 

maybe someone can help me. I'm pretty familiar with but it seems like I cant solve the following problem: (I'm working with EAGLE 7.7)

 

I've created a MODULE named DAC_CHANNEL and added a "bus" PORT called DB[0..13] to it.

I've added 16 DAC_CHANNEL MODULES to my schematic, created 4 BUSSES (DAC_DATA0:DB[0..13]; DAC_DATA1:DB[0..13]; DAC_DATA2:DB[0..13]; DAC_DATA3:DB[0..13]) and connected 4 MODULES to each BUS.

THIS works perfectly, now the PROBLEM:

I need to connect the BUSSES to the PINS of a FPGA. So I use NET to connect PINS to a BUS and get a list with the members of the BUS (DB0 to DB13) but selecting one of them will name the NET only DB0 but the correct name would for instance DAC_DATA0:DB0.

So cannot connect anything to this BUSSES except the MODULES, even manually naming a net DAC_DATA0:DB0 doesn't work as I'm not allowed to use ':' in names but when I look up the name of the net between the modules in the PCB editor it is named DAC_DATA0:DB0.

 

Attached you find a picture of my problem

 

I would be gratefull for any hints.

Cheers Reinhard

 

Nachricht geändert durch Reinhard Klambauer

Attachments:
image
  • Sign in to reply
  • Cancel

Top Replies

  • rachaelp
    rachaelp over 8 years ago +1 verified
    Hi Reinhard, I just tested this out on one of my boards and it seems to be ok. What you need to do is use a generic bus name within the module and then at the top level where you connect the modules to…
  • lostwithouthope
    lostwithouthope over 8 years ago in reply to rachaelp +1 suggested
    Hi rachaelp , thx for your solution, I already used this way, I've just hoped that there is a better solution. It seems like there is already some kind of prefix support build into eagle but not really…
Parents
  • rachaelp
    0 rachaelp over 8 years ago

    Hi Reinhard,

     

    I just tested this out on one of my boards and it seems to be ok. What you need to do is use a generic bus name within the module and then at the top level where you connect the modules to the FPGA then manually name the busses such that they get the correct individual names e.g. DAC_DATA0:DAC_DATA0_DB[0..13], DAC_DATA1:DAC_DATA1_DB[0..13] etc.

     

    I know it's a pain having to do that, I think there should be an option to enable to bus name to prefix the signal name but currently this doesn't happen. If you do what I have suggested above then you should have correctly unique signals for each of your DAC's to your FPGA.

     

    Best regards,

     

    Rachael

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • rachaelp
    0 rachaelp over 8 years ago

    Hi Reinhard,

     

    I just tested this out on one of my boards and it seems to be ok. What you need to do is use a generic bus name within the module and then at the top level where you connect the modules to the FPGA then manually name the busses such that they get the correct individual names e.g. DAC_DATA0:DAC_DATA0_DB[0..13], DAC_DATA1:DAC_DATA1_DB[0..13] etc.

     

    I know it's a pain having to do that, I think there should be an option to enable to bus name to prefix the signal name but currently this doesn't happen. If you do what I have suggested above then you should have correctly unique signals for each of your DAC's to your FPGA.

     

    Best regards,

     

    Rachael

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
  • lostwithouthope
    0 lostwithouthope over 8 years ago in reply to rachaelp

    Hi rachaelp,

     

    thx for your solution, I already used this way, I've just hoped that there is a better solution. It seems like there is already some kind of prefix support build into eagle but not really accessible.

    Have a look a my attached screen shot: as long as there are only modules connected to the bus the individual nets get the more meaningful name DAC_DATA_0:DB13 and so on... really weird image

    image

    Best regards Reinhard

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube