dependencies for parts

Hi

I'd like to suggest that the XML for individual parts have a list of dependencies for the other parts required to allow the selected part to be fully functional.

The dependencies could then be displayed as suggestions within the UI or the parts could be automatically added to the design if the user prefers.

If each part has its own dependencies then a circuit could almost be self designing & optomizing by placing just a few required parts?!

Lee

Hi Lee,

that's an interesting suggestion. I don't think that it's possible to say that parts depend on other parts, like an LED does not always require a resistor to go with it. But we are definitely planning to add the concept of 'modules' at some point. Modules will be parts composed of other parts and have a specific purpose, e.g. something simple like a button with pull-up resistor, or more complex things like an RFID reader.

Also the Arduino could then be modularized, and you could combine an Arduino core module with a Bluetooth communication module and a battery power module.

Is that the direction you are having in mind?

- andré>

Mainly i was thinking about having suggestions to meet the basic requirements of a part,intended to help those with no prior knowledge of a part without having to refer to data sheets.For example, if a part requires a external timer a suggestion of a crystal or oscillator.

In this example maybe the requirement would be a class and suggestions would be for parts that are of the required class, suggestions could then include parts and modules.

I am just thinking aloud here & mabey dependencies was not the right term.

Lee

Yes, I think it is a good idea to be suggestive of these kinds of part dependencies. If we do not make them strict, but as you say, rather 'suggest a class of parts', it could be very helpful for beginners.

For the beginning, we intend to have this information in the part reference on the website, and later we could add this as a feature within the software.

Thanks for the idea!