InstaCal, API Detection, or Both?

Most programmers using the Universal Library will install and configure their hardware using InstaCal. All software using the Universal Library will then use the configuration file "cb.cfg" generated by InstaCal to determine what devices are installed and how they are configured. If that is adequate for your situation, you will not need any of the API functions listed in the Device Discovery sections below.
Most example programs use this method for hardware detection and configuration, with the exception of Python examples which default to runtime detection but are easily modified to use InstaCal.

Other programmers may find it desirable to detect and configure hardware at runtime. Although this requires more work for the programmer, it may be more convenient for the end user of the application. This approach will typically be used by OEMs and distributed applications where the hardware to be used is undefined. A couple of example programs are available that demonstrate this approach.

The Universal Library API provides functions and methods for detecting many types of MCC devices at runtime. These features can be used in lieu of, or in addition to, using InstaCal for detection and configuration.

See Also