Background

1 Introduction

As the demand for hardware design automation tools grows, the need for machine-readable datasheets becomes more critical. Establishing a standardized Electronic Datasheet (EDS) specification alleviates the burden on component vendors to produce multiple datasheets for various tools, promoting the reuse of tools across different designs.

1.1 Objectives

Component manufacturers produce datasheets to document various details about their components, such as performance, electrical characteristics, size, orientation, and packaging. EDS provide this information in a machine-readable format. The goal of this specification is to establish a standardized, machine-readable format for representing component datasheets.

1.2 Scope

This document is designed for EDS producers, such as component vendors, and for individuals who will use EDS to automate designs, such as tool creators. The specification will cover common classes of components used in designs. Examples are included in the appendices to provide context for future additions to this specification.

1.3 Keywords

• Required: The field is required in the EDS.
• Optional: The field may or may not be included in the EDS.
• Shall: Indicates a mandatory requirement.
• May: Indicates an optional requirement.

1.4 References

• The JSON data interchange syntax, ECMA-404, 2nd edition, December 2017
• JSON Schema: A media Type for Describing JSON Documents, draft-bhutton-json-schema-00, December 2020.
• Terms, Definitions, and Letter Symbols for Microelectronic Devices, JESD99C – December 2012

2. Working with Electronic Datasheets

2.1 Electronic Datasheet Distribution by Component Vendors

EDS released by a hardware component vendor can include one or multiple files. Multiple files are typically used when a single datasheet covers multiple parts from the same family, when a part is complex or, when a part has additional information, not in JSON format, such as footprints. In this case, the specification has a provision that enables vendors to capture common or core properties across all the parts in one file while using additional files to capture the changes between parts.

There are multiple existing models for hardware component vendors to distribute their parts datasheets. The recommendation is for these vendors to leverage these existing models for EDS. Existing models include private and public distributions directly from the vendors or through an electronic components’ distributor.

In a public release, the hardware component vendor makes their latest EDS available to the public, generally, through a public website. An example of this might be a GitHub repository where each vendor has a repository. The EDS can be directly downloaded through the website without any requirements, and customers can optionally add their contact information to be notified about updates in the EDS.

Electronic components distributors have agreements with hardware component vendors to distribute their products to customers. In the existing model, distributors either include a local copy of the component datasheet to their website or add links to the datasheets on the vendor’s website. In the case of EDS, the recommendation is to use the later model, with an EDS link always pointing to the latest release. The goal is to avoid a situation where copies of local EDS become out of sync with the latest release.

In a private distribution model, the EDS is shared by a hardware component vendor to one or more select customers, for Intellectual Property (IP) protection. This may require an NDA between the parties involved. The EDS can be shared through means like a private repository or a private database, or through encrypted emails. With this model, the vendors have a good visibility of the customers using their EDS and can directly notify them of updates through email. It’s also recommended to provide a release document identifying EDS changes from one release to the next.

2.2 Importing Electronic Datasheets in a Part Library Management System

Most companies doing hardware design rely on a Part Library Management (PLM) System to store information about electronic components. These systems are often linked to CAD tools to guide component selection during hardware design. Additionally, these systems have an important role in Bill of Materials (BOM) generation and purchasing. Therefore, a natural entry point for EDS information is a PLM system.

Given the importance of component accuracy in a PLM system, it is likely that companies will initially want some manual review of new EDS before they are integrated into a shared PLM system. One suggested method of achieving this is to have an internal datasheet database that is connected to any datasheet repositories (public or private) that are used by that company. Updates can be manually pulled in and compared as new datasheets are available. Once the updates have been checked, new datasheet changes can be submitted to the internal database. This database would be indexed by internal part numbers that correspond to the EDS.

Converting this internal company datasheet database to information in the PLM system can be done automatically because datasheets in the internal database have already been manually verified. To do this conversion, a one-time mapping file between properties in the EDS schema and the specific properties in a company’s PLM is created. Companies can then write a simple generator script using this mapping file to convert EDS entries to PLM properties. Additionally, as EDS will likely contain new information not available in the PLM system, this information can be added or exist in a separate database alongside the PLM system. As tooling advances, these new properties can be leveraged to provide richer schematic validation.

The advantage of this system is it leverages existing PLM systems, which are often deeply integrated with engineering workflows. However, it makes these PLM systems more efficient to generate and update.

2.3 Tools to Generate Electronic Datasheets

The Digital Datasheet Creator (DDC) is an open-source tool that is available to make datasheet creation less time consuming. The tool can be found here: datasheet creator. It consists of a series of template spreadsheets for each part type that can be filled in and run through the creator script to generate a specification-compliant JSON datasheet file.

3. Use Cases

EDS can be used for many applications. The list of use cases included here is not meant to be exhaustive and it is expected that new applications will be developed as more people start using these EDS. Sample applications include automated hardware design checks to identify bugs earlier in the design cycle, automated hardware designs to speed up board development, components comparison to identify replacement components on a design.

4.Specifications

4.1 Electronic Datasheet Format

EDS shall be written in the JSON (JavaScript Object Notation) format. The specification is written in JSON schema to facilitate validation of a JSON datasheet.

4.2 Required Information.

EDS shall include the following information:

• The manufacturer’s name
• The Manufacturer Part Number (MPN)
• Information to identify the source datasheet
• The datasheet version given by date or GUID
• The component part type. See appendix for examples.
• List of Component Pins as defined by the specification.

4.3 Date Format

EDS shall follow the international standard notation, YYYY-MM-DD.

4.4 Top Level Component Specification

Source: component.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |componentID|methods for identifying the version of the electronic datasheet|./common/componentID.json#/componentID|Yes| |coreProperties|core component properties as defined by the specific component spec file|./common/coreProperties.json#/coreProperties|No| |pins|array of pin objects with associated properties|./common/pinSpec.json#/pinSpec|No | |package|component package information|./common/package.json#/package|No| |register|register information|./common/register.json#/register|No| |thermal|component temperature and thermal resistance information|./common/thermal.json#/thermal|No| |componentPropertyExternalFiles|external files that describe key component properties. External files can be used in lieu of defining core properties, pins, and package information in the same file|./common/externalFileMap.json#/externalFileMap|No| |additionalSpecExternalFiles|external files that contain information outside of the json spec. Examples include layout, simulation, etc.|./common/externalFile.json#/externalFile|No| |reliability|reliability information about the component|./common/reliability.json#/reliability|No| |powerSequence|information about component power sequencing|./common/powerSequence.json#/powerSequenceTable|No|

4.5 Common

4.5.1 Specification To Capture Information To Identify Components

Source: componentID.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |manufacturer|company that manufactures the part|String|Yes| |componentName|base part name that describes the form and fit of a component|String| | |orderableMPN|orderable manufacturer part numbers, including packing and software information|array of String|Yes| |sourceDatasheetID|methods for identifying the human-readable source information for a electronic datasheet|#/$defs/sourceDatasheetID|Yes| |digitalDatasheetID|methods for identifying the version of the electronic datasheet|#/$defs/digitalDatasheetID|Yes| |status|production status of a component|String| | |complianceList|list of standards the part complies with|array of String| |

4.5.2 DigitalDatasheetID

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |publishedDate|date the electronic datasheet was published|String| | |eDatasheetSpecRevision|revision of the electronic datasheet specifications used to create the electronic datasheet|String|Yes| |guid|vendor defined guid (see https://www.guidgenerator.com/) to uniquely identify electronic datasheet version|String| |

4.5.3 SourceDatasheetID

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |publishedDate|date the source datasheet was published|String| | |version|version of the source datasheet|String| | |datasheetURI|uri to the source datasheet pdf or html view|String| | |productURI|uri to the source datasheet's product page'|String| |

4.5.4 Specification To Capture Protection Thresholds Data Of a Component

Source: componentProtectionThresholds.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |thermalShutdownThresholdRising|thermal Shutdown (tsd) Threshold with temperature rising|../common/values.json#/valueOptions| | |thermalShutdownThresholdFalling|thermal Shutdown (tsd) Threshold with temperature falling|../common/values.json#/valueOptions| | |thermalShutdownHysteresis|thermal Shutdown (tsd) Hysteresis|../common/values.json#/valueOptions| | |powerSupplyProtection|undervoltage lockout, overvoltage protection thresholds of a supply|array of #/$defs/powerSupplyProtection| |

4.5.5 PowerSupplyProtection

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |supplyPinName|name of the power supply pin or any other pin monitored|String| | |overVoltageProtectionThresholdRising|Overvoltage Protection (OVP) Threshold with power supply rising|../common/values.json#/valueOptions| | |overVoltageProtectionThresholdFalling|Overvoltage Protection (OVP) Threshold with power supply falling|../common/values.json#/valueOptions| | |overVoltageProtectionHysteresis|Overvoltage Protection (OVP) Hysteresis|../common/values.json#/valueOptions| | |underVoltageLockoutThresholdRising|Undervoltage Lockout (UVLO) Threshold with power supply rising|../common/values.json#/valueOptions| | |underVoltageLockoutThresholdFalling|Undervoltage Lockout (UVLO) Threshold with power supply falling|../common/values.json#/valueOptions| | |underVoltageLockoutHysteresis|Undervoltage Lockout (UVLO) Hysteresis|../common/values.json#/valueOptions| |

4.5.6 Specification To Capture The Current Consumption Data Of a Component

Source: currentConsumption.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |supplyName|name of the power supply |String| | |quiescentCurrent|quiescent current (Iq) of a device|../common/values.json#/valueOptions| | |shutdownCurrent|shutdown current (Isd) of a device|../common/values.json#/valueOptions| | |activeCurrent|current consumption when a device is in active mode|../common/values.json#/valueOptions| | |sleepCurrent|current consumption when a device is in sleep mode|../common/values.json#/valueOptions| | |idleCurrent|current consumption when a device is in idle mode|../common/values.json#/valueOptions| |

4.5.7 Specification For Referencing An External File

Source: externalFile.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |fileDescription|text description of the contents of an external file|String| | |standardFileType|type of file being linked|String| | |otherFileType|type of file being linked, if not in the standard list|String| | |fileExtension|extension of file linked|String| | |companionSoftware|optional, name of software program used to access file|String| | |standardReferenced|optional, name of the standard the file is written in|String| | |fileURI|URI linking to the CAD file|String| |

4.5.8 Specification For Referencing An External File For Different Components

Source: externalFileMap.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |coreProperties|core component properties as defined by the specific component spec file. These properties are described by the common part of the part number|../common/externalFile.json#/externalFile| | |additionalCoreProperties|core component properties as defined by the specific component spec file. These properties are described by the changing part of the part number|../common/externalFile.json#/externalFile| | |pins|pin properties specified by the pin spec file|../common/externalFile.json#/externalFile| | |package|package information specified by the package spec file|../common/externalFile.json#/externalFile| | |powerSequence|information about component power sequencing|../common/externalFile.json#/externalFile| | |register|register information|../common/externalFile.json#/externalFile| | |thermal|component temperature and thermal resistance information|../common/externalFile.json#/externalFile| | |reliability|reliability information about the component|../common/externalFile.json#/externalFile| |

4.5.9 Specification Of a Graph

Source: graph.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |title|title of a graph|String| | |xUnits|x-axis units|String| | |xLabel|x-axis title|String| | |yUnits|y-axis units|String| | |yLabel|y-axis title|String| | |numberOfCurves|total number of curves in graph|Number| | |curve|data represented by one or more curves in a graph|array of #/$defs/curve| |

4.5.10 Curve

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |label|description of the data captured by a curve|String| | |xData|x-axis values of the curve|array of Number| | |yData|y-axis values of the curve|array of Number| |

4.5.11 Specification Of An Instance In a Part

Source: instanceSpec.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partName|name of the part defined in the electronic datasheets specifications|String|Yes| |instanceName|name of an instance of the part|String| | |instanceProperties|instance properties, as defined in the part specification|../common/coreProperties.json#/coreProperties| |

4.5.12 Specification Of a Package

Source: package.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |length|length of a side of a package|../common/values.json#/valueOptions| | |width|width of a side of a package|../common/values.json#/valueOptions| | |height|height of a package|../common/values.json#/valueOptions| | |standardPackageSize|name of standard package size (imperial)|String| | |standardPackageType|name of standard package types|String| |

4.5.13 Specification Of Pinpaths Through An IC

Source: pinPaths.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |numberOfPinPaths|number of pinPaths defined. This number should not be higher than the number of components included in the part|Number| | |partPinPaths|list of pins associated with each component in a multi-component part|array of #/$defs/partPinPaths|Yes|

4.5.14 PartPinPaths

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |componentName|name of a component within a part |String| | |componentPinNames|names of pins associated with each of the component in the part. Pin names must match the name used in part pin definition|array of String| |

4.5.15 Specification Of Pins

Source: pinSpec.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |terminalIdentifier|pin or ball number(s) as defined by datasheet|array of String|Yes| |name|name given to the signal appearing at the terminal of a component|String|Yes| |standardizedName|standard name of pin|String| | |description|description of the signal appearing at the terminal of an electric/electronic component|String| | |numberOfSupportedFunctions|the total number of functions supported by this pin|Number| | |pinProperties|list of properties for each pin|#/$defs/pinProperties| | |functionProperties|list of properties for each pin function configuration|array of #/$defs/functionProperties| | |pinPaths|information on pin paths - pins associated with each component in a multi-component part (such as A1,Y1 and A2,Y2)|../common/pinPaths.json#/pinPaths| |

4.5.16 ExternalComponents

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |componentType|type of external component required to be connected to a pin|String|Yes| |configuration|electrical configuration of component connected to pin with respect to the pin|String|Yes| |value|value of component|../common/values.json#/valueOptions| |

4.5.17 FunctionProperties

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |perFunctionName|name of the function of a pin|String| | |perFunctionProperties|list of pin properties that change based on the pin function configuration|#/$defs/pinProperties| |

4.5.18 PinProperties

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |vih|the high-level input voltage for which operation of the logic element within specification limits is to be expected|../common/values.json#/valueOptions| | |vil|the low-level input voltage for which operation of the logic element within specification limits is to be expected|../common/values.json#/valueOptions| | |vol|the voltage level at an output terminal with input conditions applied that, according to the product specification, will establish a low level at the output|../common/values.json#/valueOptions| | |voh|the voltage level at an output terminal with input conditions applied that, according to the product specification, will establish a high level at the output|../common/values.json#/valueOptions| | |absVmax|maximum voltage rating beyond which damage to the device may occur|../common/values.json#/valueOptions| | |absVmin|absolute minimum voltage that can be applied to a pin|../common/values.json#/valueOptions| | |voltageOperatingRange|voltage operating range that can safely be applied to a pin|../common/values.json#/valueOptions| | |currentRange|current range that can safely be drawn/injected from/to a pin|../common/values.json#/valueOptions| | |inputLeakage|current draw out of a high impedance input pin|../common/values.json#/valueOptions| | |outputLeakage|current flow from a pin during the off state|../common/values.json#/valueOptions| | |dcResistance|resistance of a pin of a connector|../common/values.json#/valueOptions| | |interfaceType|type of interface enabled by pin|String| | |pinUsage|standardized usage of pin|String| | |direction|direction of a pin|String| | |electricalConfiguration|electrical configuration of a pin|String| | |polarity|whether the active state of a pin is high or low|String| | |voltageOptions|list of voltage levels supported by a pin|../common/values.json#/valueOptions| | |floatUnused|description of whether pin can safely be floated if it is not used|Boolean| | |internalPullUp|indicates the value of an internal pull-up on a pin|../common/values.json#/valueOptions| | |internalPullDown|indicates the value of an internal pull-down on a pin|../common/values.json#/valueOptions| | |esd|indicates whether ESD protection exists on a pin|Boolean| | |externalComponents|list of external component structures recommended to be attached to a pin|array of #/$defs/externalComponents| |

4.5.19 Specification Of Power Fets Properties

Source: powerFetProperties.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |singlePowerFetPair|single pair of power fets (typical in buck or boost configuration)|#/$defs/powerFetPair| | |inputPowerFetPair|input power fet pair (in a buck-boost configuration)|#/$defs/powerFetPair| | |outputPowerFetPair|output power fet pair (in a buck-boost configuration)|#/$defs/powerFetPair| |

4.5.20 PowerFetPair

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |ilimHSFET|maximum sustained output current under which the high side FET will operate properly|../common/values.json#/valueOptions| | |ilimLSFET|maximum sustained output current under which the low side FET will operate properly|../common/values.json#/valueOptions| | |rdsonHSFET|high side FET on-resistance|../common/values.json#/valueOptions| | |rdsonLSFET|low side FET on-resistance|../common/values.json#/valueOptions| |

4.5.21 Specification Of Power Sequencing Information

Source: powerSequence.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |powerTransitionName|datasheet specific name given to a particular power transition for tracking|String| | |powerTransitionDescription|description of power transition|String| | |signal1|signal that comes up first in the sequence. Also used if there is only one relevant signal for a power transition (such as rise time) |String| | |signal1TerminalIdentifiers|list of component pins associated with signal 1|array of String| | |signal2|signal that comes up second in the sequence |String| | |signal2TerminalIdentifiers|list of component pins associated with signal 2|array of String| | |timeCondition|time between the signal 1 and signal 2 events|../common/values.json#/valueOptions| | |powerDirection|whether this is a power up or power down event|String| | |nextPowerState|power state the device enters after the signal transition|String| | |currentPowerState|power state the device is currently in before the signal transition|String| | |riseTime|time for a signal to go from low to high (only applies to one signal)|../common/values.json#/valueOptions| | |slewRate|maximum rate at which a voltage rail changes per time (only applies to one signal)|../common/values.json#/valueOptions| | |fallTime|time for a signal to go from high to low (only applies to one signal)|../common/values.json#/valueOptions| | |transitionStartCondition|the percentage of max voltage where rise or fall time starts being measured for timing (only applies to one signal)|../common/values.json#/valueOptions| | |transitionEndCondition|the percentage of max voltage where rise or fall time stops being measured for timing (only applies to one signal)|../common/values.json#/valueOptions| |

4.5.22 Specifications Of a Ratio

Source: ratio.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |numerator|numerator of ratio|Number| | |denominator|denominator of ratio|Number| |

4.5.23 Specification Of a Register

Source: register.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |registerName|name of a register|String|Yes| |registerLongName|full Name of a register|String| | |registerAddressOffset|address of a register|String|Yes| |registerSize|size of a register|../common/values.json#/valueOptions|Yes| |registerType|type of a register|String| | |registerEndianness|memory storage order for the bytes|String| | |registerResetValue|reset value of a register|String| | |registerValue|value of a register|String| | |registerIpName|name of the IP or interface controlled by changes in the register|String| | |registerAccessType|access type of a Register|String| | |registerBitField|describes the bit fields in the register|#/$defs/registerBitField| |

4.5.24 RegisterBitField

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |bitFieldName|Name of the bit field|String| | |bitFieldLongName|Long Name of the bit field|String| | |bitFieldDescription|Describes the bit field|String| | |bitFieldNumber|Number of a bitfield|Number| | |bitFieldRange|Range of the bit field|String| | |bitFieldResetValue|Reset value of a bit field|String| | |bitFieldAccessType|Access type of a bit field|String| |

4.5.25 Specification Of The Reliability Of a Component

Source: reliability.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |failuresInTime|the number of expected failures per one billion hours of operation for a device|../common/values.json#/valueOptions| | |meanTimeToFail|the average time a product or system functions before its first failure under normal conditions|../common/values.json#/valueOptions| |

4.5.26 Specification Of Thermal Properties On Components

Source: thermal.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |junctionTemperature|recommended operating junction temperature range of a part|../common/values.json#/valueOptions| | |junctionTemperatureAbsMax|absolute maximum junction temperature of a part|../common/values.json#/valueOptions| | |ambientTemperature|recommended operating ambient air temperature range of a part|../common/values.json#/valueOptions| | |ambientTemperatureAbsMax|absolute maximum ambient air temperature of a part|../common/values.json#/valueOptions| | |caseTemperature|case temperature range of a part|../common/values.json#/valueOptions| | |caseTemperatureAbsMax|absolute maximum case temperature of a part|../common/values.json#/valueOptions| | |leadTemperatureAbsMax|absolute maximum lead temperature of a part|../common/values.json#/valueOptions| | |storageTemperatureAbsMax|absolute maximum storage temperature of a part|../common/values.json#/valueOptions| | |packageThermalResistance|package thermal resistance of a part|../common/values.json#/valueOptions| | |thermalResistanceJunctionToAmbient|thermal resistance between the semiconductor junction of a part and the ambient air|../common/values.json#/valueOptions| | |thermalResistanceJunctionToCase|thermal resistance between the semiconductor junction and the package surface of a part|../common/values.json#/valueOptions| | |thermalResistanceJunctionToBoard|thermal resistance between the semiconduction junction of a part and the board|../common/values.json#/valueOptions| | |thermalResistanceJunctionToLead|thermal resistance between the semiconduction junction of a part and the solder pad|../common/values.json#/valueOptions| | |thermalResistanceCaseToAmbient|thermal resistance between the package surface of a part and the ambient air|../common/values.json#/valueOptions| | |thermalDesignPower|power at which thermal compliance should be evaluated at steady-state|../common/values.json#/valueOptions| | |peakPower|maximum transient power the part will dissipate|../common/values.json#/valueOptions| |

4.5.27 Specification Of Value

Source: values.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |values|list of values that reflect possible values for a property|array of #/$defs/value| |

4.5.28 Value

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |siUnit|name of SI unit of measure|String| | |unitName|name of unit if not defined in the siUnit list|String| | |typValue|typical unit quantity corresponding to unit text - example 40mV would have a value of 40|Number| | |minValue|minimum unit quantity corresponding to unit text - example: 30mV would have a value of 30|Number| | |maxValue|maximum unit quantity corresponding to unit text - example: 50mV would have a value of 50|Number| | |unitFactor|multiplier on the value to achieve the SI unit listed - for example if millivolt was selected, 40mV would have a unitFactor value of 1; if volt was selected, the unitFactor value would be 0.001|Number| | |relativeValueReference|if unit quantity is based on another reference, value of the reference|String| | |relativeValueModifier|if a unit quantity is based on another reference, the value that edits that reference|Number| | |relativeValueOperator|if a unit quantity is based on another reference, the operation that is performed with the modifier|String| | |conditions|conditions under which the property is measured|array of String| |

4.6 Clock

4.6.1 Specification Of Clock

Source: clock.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |fixedFrequency|clock frequency value if the clock has a fixed frequency|../common/values.json#/valueOptions| | |numberClockOutputs|number of clock outputs in a clock IC|Number| | |differentialSingleEnded|property describing whether a clock output is single ended or differential|String| | |jitter|cycle to cycle clock jitter|../common/values.json#/valueOptions| | |frequencyTolerance|amount of frequency variation from nominal frequency|../common/values.json#/valueOptions| | |powerSupplyRejectionRatio|power supply rejection ratio (PSRR) or ratio between power supply variation and output variation|Number| | |outputFormat|signal format of clock output|String| | |currentConsumption|current used by device in various power modes|../common/currentConsumption.json#/currentConsumption| |

4.6.2 Specification Of Oscillator

Source: oscillator.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |baseResonator|technology producing resonance|String| | |frequency|output frequency of oscillator|../common/values.json#/valueOptions|Yes| |frequencyStability|frequency change over temperature, load, supply voltage change and aging|Number| | |currentConsumption|current consumption of a device|../common/currentConsumption.json#/currentConsumption| | |outputLoad|maximum capacitive load that can be supported by oscillator|../common/values.json#/valueOptions| | |riseTime|time for output to go from 10% to 90% of output max|../common/values.json#/valueOptions| | |fallTime|time for output to go from 90% to 10% of output max|../common/values.json#/valueOptions| | |startUpTime|time between enable and output reaching 10% of output max|../common/values.json#/valueOptions| | |dutyCycle|time above 50% of output max over entire period|../common/values.json#/valueOptions| | |phaseJitter|variation of waveform period|../common/values.json#/valueOptions| |

4.7 Data_converter

4.7.1 Specification Of ADC

Source: adc.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |digitalResolution|number of bits of resolution in the digital output|Number| | |conversionTime|time required to convert from an analog signal to digital output|../common/values.json#/valueOptions| | |sampleRate|maximum rate at which the ADC can convert samples|../common/values.json#/valueOptions| | |offsetError|difference (in LSB) of the output at the zero point between an actual and ideal ADC|Number| | |gainError|difference (in LSB) of how the actual transfer function matches the ideal transfer function, also called full scale error|Number| | |integralNonlinearity|deviation (in LSB) of an actual transfer function from an ideal transfer function|Number| | |differentialNonlinearity|difference (in LSB) in step width between the actual and ideal transfer functions|Number| | |rmsNoise|root mean square (RMS) noise of ADC|Number| | |SNR|signal to noise (SNR) ratio of the converter|Number| | |interface|digital communication interfaces supported|array of String| | |inputType|whether the ADC has a single ended or differential input|String| | |inputChannels|number of input channels|Number| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.7.2 Specification Of DAC

Source: dac.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |digitalResolution|number of bits of resolution|Number| | |offsetError|analog response to an input code of all zeros|../common/values.json#/valueOptions| | |gainError|difference (in percentage of FSR) of how well the slope of the actual transfer function matches the ideal transfer function|../common/values.json#/valueOptions| | |integralNonlinearity|deviation of an actual transfer function from an ideal transfer function, in LSB|Number| | |differentialNonlinearity|difference between the ideal and the actual output responses for successive DAC codes, in LSB|Number| | |settlingTime|time from application of input code to valid output response|../common/values.json#/valueOptions| | |sampleRate|maximum rate at which the DAC can convert samples|../common/values.json#/valueOptions| | |interface|digital communication interfaces supported|array of String| | |outputType|whether the DAC has a single ended or differential output|String| | |outputChannelCount|number of output channels|Number| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.8 Hardware

4.8.1 Specification Of Connector

Source: connector.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |function|intended function of a connector|String| | |contactCount|number of contacts in a connector|Number|Yes| |type|property describing the method of mating to the connector|String| | |cycleRating|number of plug/unplug cycles a connector is rated to support|Number| | |pitch|distance from the center of one contact on the connector to the center of the next contact|../common/values.json#/valueOptions| | |keying|property describing whether a connector has an asymmetry to prevent it from being plugged in the wrong direction|Boolean| |

4.8.2 Specification Of Switch

Source: switch.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |type|property describing the way in which the switch is activated|String| | |contactType|property describing the order in which switch contact is made and broken|String| | |circuitConfig|property describing the number of poles and throws in a switch|String| | |cycleRating|number of on/off cycles a mechanical switch can reliably sustain|Number| | |voltageRating|maximum DC voltage potential that can be applied across an open switch|../common/values.json#/valueOptions| | |currentRating|maximum DC current that can flow through a closed switch without causing excessive heating|../common/values.json#/valueOptions| | |onResistance|nominal resistance of a closed switch|../common/values.json#/valueOptions|Yes| |dielectricRating|maximum AC voltage potential that can be applied across an open switch for one minute|../common/values.json#/valueOptions| |

4.9 Ic_io

4.9.1 Specification Of Bridge Chip

Source: bridge_chip.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |muxRatio|ratio of inputs to outputs|../common/ratio.json#/ratio| | |inputInterfaces|list of interfaces at the input of the bridge|array of String| | |outputInterfaces|list of interfaces at the output of the bridge|array of String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.9.2 Specification Of High Speed Mux

Source: highspeed_mux.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |muxRatio|ratio of inputs to outputs|../common/ratio.json#/ratio| | |inputInterfaces|list of interfaces high speed mux is designed for|array of String| | |maxDataRate|maximum data rate supported by high speed mux|../common/values.json#/valueOptions| | |insertionLoss|insertion loss through high speed mux|Number| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.9.3 Specification Of Level Shifter

Source: level_shifter.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |inputVoltage|nominal input voltage of level shifter|../common/values.json#/valueOptions| | |outputVoltage|nominal output voltage of level shifter|../common/values.json#/valueOptions| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.9.4 Specification Of Redriver

Source: redriver.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |numberChannels|number of lanes (single ended or differential) supported by redriver|Number| | |interface|list of interface(s) supported by redriver|array of String| | |maxDataRate|maximum data rate supported by redriver|../common/values.json#/valueOptions| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.9.5 Specification Of Retimer

Source: retimer.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |numberOfLanes|number of lanes (single ended or differential) supported by a device|Number| | |interface|list of interface(s) supported by a device|array of String| | |dpMaxLinkRate|maximum interface speed supported by DP interface of a device|String| | |maxDataRate|maximum data rate supported by a device|../common/values.json#/valueOptions| | |integratedAuxLsSwitch|whether the AUX/LSx switch for SBU is integrated|Boolean| | |commonClock|whether a device supports common reference clock|Boolean| | |sris|whether a device supports Separate Reference clock with Independent Spread spectrum clocking(SRIS)|Boolean| | |srns|whether a device supports Separate Reference clock with No Spread spectrum clocking (SRNS)|Boolean| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.9.6 Specification Of USB Battery Charging 1.2 (bc12) Detector

Source: usb_bc12.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |hostMode|whether host mode is supported by bc12 chip|Boolean|Yes| |deviceMode|whether device mode is supported by bc12 chip|Boolean|Yes| |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.9.7 Specification Of USB-C PD Controller

Source: usbc_pdcontroller.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |pdVersion|version of power delivery spec implemented by controller|String|Yes| |usbTypecRevision|usb type-c spec revision implemented by controller|String| | |powerRoleSupported|roles supported by pd controller|String| | |fastRoleSwapSupport|whether the pd controller supports fast role swap (FRS)|Boolean| | |vconnPowerSupport|whether the pd controller has support for vconn power|Boolean| | |vconnPowerLimit|power limit supported by internal vconn switch (if supported)|../common/values.json#/valueOptions| | |vconnMaxCurrent|maximum continuous current supported by internal vconn switch (if supported)|../common/values.json#/valueOptions| | |vconnOverCurrentLimit|over current limit supported by internal vconn switch (if supported)|../common/values.json#/valueOptions| | |integratedVbusDischargeSwitch|whether the pd controller has one or more integrated vbus discharge switches |Boolean| | |integratedLoadSwitch|whether the pd controller has an integrated load switch for vbus power |Boolean| | |maxSinkCurrent|maximum continuous current supported by pd controller integrated sink load switch|../common/values.json#/valueOptions| | |maxSourceCurrent|maximum continuous current supported by pd controller integrated source load switch|../common/values.json#/valueOptions| | |sinkfetOverCurrentLimit|over current limit supported by pd controller integrated sink load switch|../common/values.json#/valueOptions| | |sourcefetOverCurrentLimit|over current limit supported by pd controller integrated source load switch|../common/values.json#/valueOptions| | |onResistanceSinkFet|on-resistance of the integrated sink load switch|../common/values.json#/valueOptions| | |onResistanceSourceFet|on-resistance of the integrated source load switch|../common/values.json#/valueOptions| | |interface|describes the communication interface from the chip to the host|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| | |componentProtectionThresholds|thermal and power supply protection thresholds of a device|../common/componentProtectionThresholds.json#/componentProtectionThresholds| |

4.9.8 Specification Of USB-C Port Controller

Source: usbc_portcontroller.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |pdVersion|version of power delivery spec implemented by controller|String|Yes| |usbTypecRevision|usb type-c spec revision implemented by controller|String| | |usbTcpiRevision|usb type-c port controller interface spec revision implemented by controller|String| | |powerRoleSupported|roles supported by pd controller|String| | |fastRoleSwapSupport|whether the port controller supports fast role swap (FRS)|Boolean| | |vconnPowerSupport|whether the port controller has support for vconn power|Boolean| | |vconnFetOnResistance|on-resistance of the integrated Vconn FET|../common/values.json#/valueOptions| | |vconnPowerLimit|power limit supported by internal vconn switch (if supported)|../common/values.json#/valueOptions| | |vconnMaxCurrent|maximum continuous current supported by internal vconn switch (if supported)|../common/values.json#/valueOptions| | |vconnOverCurrentLimit|over current limit supported by internal vconn switch (if supported)|../common/values.json#/valueOptions| | |integratedVbusDischargeSwitch|whether the port controller has one or more integrated vbus discharge switches |Boolean| | |integratedMux|whether the port controller has one or more integrated high speed muxes|Boolean| | |interface|describes the communication interface from the controller to the policy manager|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| | |componentProtectionThresholds|thermal and power supply protection thresholds of a device|../common/componentProtectionThresholds.json#/componentProtectionThresholds| |

4.10 Ic_microcontroller

4.10.1 Specification Of Microcontroller/ec

Source: microcontroller.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |onChipFlash|capacity of built-in flash in a microprocessor|../common/values.json#/valueOptions| | |onChipRAM|capacity of built-in RAM in a microprocessor|../common/values.json#/valueOptions| | |onChipROM|capacity of built-in ROM in a microprocessor|../common/values.json#/valueOptions| | |coreProcessor|description of core processor|String| | |coreArchitectureBits|number of bits of data a CPU can transfer per clock cycle|String| | |clockSpeed|speed of main CPU clock|../common/values.json#/valueOptions| | |firmwareVersion|firmware version of the part|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.11 Ic_misc

4.11.1 Specification Of Audio Codec

Source: audio_codec.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |dataLength|number of bits in a data word|Number| | |hpOutputSNR|headphone amplifier output SNR|Number| | |hpOutputTHD+N|headphone output total harmonic distortion plus noise|../common/values.json#/valueOptions| | |micInputSNR|microphone input SNR|Number| | |micInputTHD+N|microphone input total harmonic distortion plus noise|../common/values.json#/valueOptions| | |jackDetect|describes whether headphone jack detection is supported|Boolean| | |interface|describes the communication interface from the chip to the host|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.11.2 Specification Of Speaker Amplifier

Source: speaker_amplifier.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |dataLength|number of bits in a data word|Number| | |outputPower|typical output power from speaker amplifier|../common/values.json#/valueOptions| | |efficiency|typical speaker amplifier efficiency|../common/values.json#/valueOptions| | |thd+n|typical total harmonic distortion plus noise of amplifier|../common/values.json#/valueOptions| | |sampleRate|sample rate of data out of amplifier|../common/values.json#/valueOptions| | |interface|describes the communication interface from the chip to the host|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.11.3 Specification Of TPM

Source: tpm.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |interface|describes the communication interface from the chip to the host|array of String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.11.4 Specification Of WLAN Module

Source: wlan_module.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |wlanSpec|version of wlan specification supported by module|String| | |bluetoothVersion|version of bluetooth supported by module|String| | |txrxChains|number of tx and rx chains in a wifi module|String| | |m2FormFactor|wlan module form factor described by jedec standard m.2 form factors|String| | |keying|pcie card key|String| | |lteCoexFilter|describes whether module supports lte coexistence filtering|Boolean| | |interface|describes the communication interface from the chip to the host|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.11.5 Specification Of WWAN Module

Source: wwan_module.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |networkSupport|networks supported by wwan module|String| | |gpsSupport|whether wwan module has gps support|Boolean| | |m2FormFactor|wlan module form factor described by jedec standard m.2 form factors|String| | |keying|pcie card key|String| | |interface|describes the communication interface from the chip to the host|String| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.12 Logic

4.12.1 Specification Of Logic Gate

Source: logic_gate.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |type|logical operation performed by logic gate|String|Yes| |numberGates|number of logical gates encapsulated in logic IC|Number| | |schmittTrigger|property describing whether logic gate has schmitt trigger inputs|Boolean| | |propagationDelay|time between input changing to output changing|../common/values.json#/valueOptions| | |rampTime|time for output to go from 10% nominal output voltage to 90% nominal output voltage|../common/values.json#/valueOptions| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.13 Memory

4.13.1 Specification Of DRAM

Source: dram.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |type|type of dram|String| | |capacity|capacity of dram chip|../common/values.json#/valueOptions|Yes| |ranksperModule|numbers of ranks on dram module|Number| | |diesPerChip|number of dies on dram chip|Number| | |channelsPerDie|number of channels per die on dram chip|Number| | |banksPerChannel|number of banks per channel of dram|Number| | |bitsPerChannel|channel density of dram|../common/values.json#/valueOptions| | |bitsPerDie|total die density of dram|../common/values.json#/valueOptions| | |pageSize|page size of dram|../common/values.json#/valueOptions| | |rows|number of rows per channel of dram|Number| | |columns|number of columns per row of dram|Number| | |dataRate|dram maximum data rate|Number| | |speed|dram maximum speed|../common/values.json#/valueOptions| | |latencyCas|cl/tCAS, delay between read command issued and first output data available for read|Number| | |delayRasCas|tRCD,delay between activation of row and activation of column where data is stored in the dram|../common/values.json#/valueOptions| | |delayRasPrecharge|tRP, delay between closing access to a row through the precharge command and activating a new row to access data |../common/values.json#/valueOptions| | |delayActivePrecharge|tRAS, delay between row active command issued and precharge command issued |../common/values.json#/valueOptions| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.13.2 Specification Of EEPROM

Source: eeprom.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |accessTime|time to access the eeprom|../common/values.json#/valueOptions| | |bitsPerWords|number of columns in the eeprom|Number| | |bootBlockSize|size of the eeprom boot block|../common/values.json#/valueOptions| | |capacity|capacity/density of eeprom|../common/values.json#/valueOptions|Yes| |clockFrequency|eeprom clock frequency|../common/values.json#/valueOptions| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| | |dataRetention|maximum number of read and write cycle the part can support|Number| | |endurance|time in years a bit in the eeprom can retain its data state |Number| | |interface|interface of eeprom to host|String| | |numberOfWords|number of rows in the eeprom|Number| |

4.13.3 Specification Of Flash Memory

Source: flash_memory.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |capacity|capacity/density of flash memory|../common/values.json#/valueOptions|Yes| |pageSize|page size of flash memory|../common/values.json#/valueOptions| | |blockSize|block size of flash memory|../common/values.json#/valueOptions| | |bootBlockSize|size of the flash memory boot block|../common/values.json#/valueOptions| | |interface|interface of flash memory to host|String| | |clockFrequency|flash memory clock frequency|../common/values.json#/valueOptions| | |blockEraseTime|time it takes to erase a block (largest erasable unit) of the flash memory|../common/values.json#/valueOptions| | |sectorEraseTime|time it takes to erase a sector (smallest erasable unit) of the flash memory|../common/values.json#/valueOptions| | |chipEraseTime|time it takes to erase the flash memory|../common/values.json#/valueOptions| | |pageProgramTime|time it takes to program a page of the flash memory|../common/values.json#/valueOptions| | |endurance|time in years a bit in the eeprom can retain its data state |Number| | |dataRetention|maximum number of read and write cycle the part can support|Number| | |hwReset|whether the part supports a hardware reset pin|Boolean| | |writeProtect|whether the part has a write protect pin|Boolean| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.13.4 Specification Of ROM

Source: rom.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |capacity|capacity of rom|../common/values.json#/valueOptions| | |interface|interface of rom to host|String| | |qeStatus|indicates whether the Quad Enable(QE) bit is set|Boolean| | |currentConsumption|current used by device in various power modes|array of ../common/currentConsumption.json#/currentConsumption| |

4.14 Passives

4.14.1 Specification Of Capacitor

Source: capacitor.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |value|capacitor value|../common/values.json#/valueOptions|Yes| |tolerance|nominal tolerance of a capacitor|../common/values.json#/valueOptions| | |ratedVoltage|maximum voltage which may be applied continuously to a capacitance|../common/values.json#/valueOptions| | |dielectric|dielectric material used in the capacitor|String| | |polarized|describes whether the capacitor is polarized|Boolean| | |equivalentSeriesResistance|equivalent series resistance (ESR) of the capacitor|../common/values.json#/valueOptions| | |temperatureCoefficient|change in capacitance when the temperature is changed|Number| | |minTemperature|minimum temperature under which a capacitor can be expected to reliably operate|../common/values.json#/valueOptions| | |maxTemperature|maximum temperature under which a capacitor can be expected to reliably operate|../common/values.json#/valueOptions| | |capacitorDerating|graph object to capture capacitance changes with voltage changes|../common/graph.json#/graph| |

4.14.2 Specification Of Common Mode Choke

Source: common_mode_choke.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |diffModeCutoff|frequency at which the differential mode attenuation equals -3dB|../common/values.json#/valueOptions| | |commonModeAttenuation|graph object to capture common mode attenuation of a common mode choke at various frequencies|../common/graph.json#/graph| | |dcResistance|dc resistance (DCR) of a common mode choke|../common/values.json#/valueOptions| | |rmsCurrent|applied DC current (IRMS) that produces a common mode choke temperature rise of 40 deg C|../common/values.json#/valueOptions| | |intendedApplication|intended application of a particular common mode choke|String| |

4.14.3 Specification Of Ferrite Bead

Source: ferrite_bead.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |dcResistance|dc resistance (DCR) of ferrite bead|../common/values.json#/valueOptions| | |rmsCurrent|applied DC current (IRMS) that produces a ferrite bead temperature rise of 40 deg C|../common/values.json#/valueOptions| | |impedance100MHz|impedance of ferrite bead under standard testing conditions at 100MHz|../common/values.json#/valueOptions| | |impedanceTolerance|variation of ferrite bead impedance expressed as +/- percentage|../common/values.json#/valueOptions| |

4.14.4 Specification Of Inductor

Source: inductor.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |value|inductor value|../common/values.json#/valueOptions|Yes| |tolerance|nominal tolerance of an inductor|../common/values.json#/valueOptions| | |ratedCurrent|maximum continuous current the inductor can handle|../common/values.json#/valueOptions| | |saturationCurrent|current where the inductor enters the magnetic state, and the inductance drops a specified amount|../common/values.json#/valueOptions| | |rmsCurrent|DC current that produces an inductor temperature rise of 40 degrees Celsius|../common/values.json#/valueOptions| | |selfResonantFrequency|frequency at which the inductor starts behaving like a capacitor|../common/values.json#/valueOptions| | |dcResistance|DC resistance of the inductor|../common/values.json#/valueOptions| | |temperatureCoefficient|change in inductance when the temperature is changed|Number| | |minTemperature|minimum temperature under which a inductor can be expected to reliably operate|../common/values.json#/valueOptions| | |maxTemperature|maximum temperature under which a inductor can be expected to reliably operate|../common/values.json#/valueOptions| | |saturationCurve|graph object to capture inductance as a function of current|../common/graph.json#/graph| | |resonantFrequencyCurve|graph object to capture inductance as a function of frequency|../common/graph.json#/graph| |

4.14.5 Specification Of Resistor

Source: resistor.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |value|resistance value|../common/values.json#/valueOptions|Yes| |tolerance|nominal tolerance of a resistor|../common/values.json#/valueOptions| | |powerRating|measure of power a resistor can dissipate indefinitely without degrading performance|../common/values.json#/valueOptions| | |temperatureCoefficient|change in resistance when the temperature is changed|Number| | |maxOverloadVoltage|maximum voltage that can be applied to the resistor for a short period of time|../common/values.json#/valueOptions| | |maxLimitingElementVoltage|maximum voltage value that can be applied continuously to the resistor|../common/values.json#/valueOptions| | |minTemperature|minimum temperature under which a resistor can be expected to reliably operate|../common/values.json#/valueOptions| | |maxTemperature|maximum temperature under which a resistor can be expected to reliably operate|../common/values.json#/valueOptions| | |resistorDerating|graph object to capture resistance changes with temperature|../common/graph.json#/graph| |

4.15 Power

4.15.1 Specification Of Battery Charger

Source: battery_charger.json

|Property|Description|JSON Data Type|Required?| |:----|:----|:----|:----| |partType|part type|String|Yes| |chargerType|battery charger type|String| | |converterType|switching charger type|String| | |chargerTopology|type of battery charger topology (Narrow VDC vs Hybrid Power Boost)|String| | |batteryConfig|battery configuration supported by the device|array of String| | |batteryCellChemistry|battery cell chemistry supported by the device|array of String| | |inputPowerSource|input power source supported by the device|array of String| | |inputCurrentAccuracy|accuracy of input current when set|../common/values.json#/valueOptions| | |batteryChargeCurrent|charging (fast charge) current of a device|../common/values.json#/valueOptions|Yes| |batteryChargeCurrentAccuracy|charging current regulation accuracy of a device|../common/values.json#/valueOptions| | |batteryPreChargeCurrent|charging current of a device in pre-charge phase|../common/values.json#/valueOptions| | |batteryPreChargeCurrentAccuracy|pre-charging current regulation accuracy of a device|../common/values.json#/valueOptions| | |batteryTrickleChargeCurrent|charging