Skip to content

Added datasheet fields#20

Open
AlfVII wants to merge 2 commits intomainfrom
19-add-datasheet-field-for-magnetics-where-the-construction-is-missing
Open

Added datasheet fields#20
AlfVII wants to merge 2 commits intomainfrom
19-add-datasheet-field-for-magnetics-where-the-construction-is-missing

Conversation

@AlfVII
Copy link
Copy Markdown
Collaborator

@AlfVII AlfVII commented Apr 7, 2026

No description provided.

@AlfVII AlfVII linked an issue Apr 7, 2026 that may be closed by this pull request
@AlfVII AlfVII requested a review from Carlosman1996 April 7, 2026 15:27
"type": "string",
"enum": ["production", "prototype", "obsolete"]
},
"reference": {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reference maybe is the same as partNumber

"type": "string"
},
"matchCode": {
"description": "Internal match / order code used by the manufacturer.",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe, to make it more clear, I should rename it to internalPartNumber.

},
"cost": {
"description": "The manufacturer's price for this part",
"type": "string"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cost should be a number

"type": "integer"
},
"automotive": {
"description": "True if the part is qualified for automotive applications (AEC-Q200 or equivalent).",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably this field can be standards. Inside, it can be a list of standards and there you can find all of them (e.g. all that applies to automotive or directly "automotive")

"description": "Turns ratio (e.g. 100 means 1:100) for coupled inductors / transformers.",
"type": "number"
},
"couplingCoefficient": {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it necessary? The leakage inductance is already specified

}
},
"magneticDatasheetElectrical": {
"description": "Electrical characteristics as stated in the datasheet.",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are several fields that could not apply or could not be defined by the manufacturer. An example can be the insulation fields, commonModeFilter, impedancePoints, maximumImpedance, selfResonanceFrequency..., and others that do not apply to inductors for example like turns ratio or leakage. The really necessary fields has to be the basic ones: inductance, dc_resistance, saturation, rated current, rated voltage?

The objective is to map whatever magnetic element without braking the DTO

"$ref": "#/$defs/magneticDatasheetMechanical"
},
"application": {
"description": "Application parameters published by the manufacturer — describes the circuit this component was designed for, not the component's intrinsic electrical properties.",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say to remove the application part. This specs are in other parts of the MAS, here you want only to do a summary of the magnetic, that could be used in different applications

"height": {
"description": "Body height in metres.",
"$ref": "./utils.json#/$defs/dimensionWithTolerance"
},
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add footprint, and pins lenght and diameter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add datasheet field for magnetics where the construction is missing

2 participants