-
Notifications
You must be signed in to change notification settings - Fork 114
KLC Document audio connector pin mapping decission. #364
Comments
@evanshultz as you worked out the current naming, could you provide a first draft as a comment? |
Sure. It seems to fit into KLC clauses S3.7 and F2.4, and should work with all other text since I've included a note about the pin 1 equivalent for footprints below. If that isn't accepted, I note pin 1 discussed in clauses F4.1, F5.1, F5.2, and F7.2. I've written this explicitly for audio jacks and nothing else. This could be condensed and generalized if we apply this to other places. For example, I believe there is acceptance for SD/SIM/etc. cards at . If this is the case, I can re-word to a general statement that in some places we use names instead of numbers for pins and then perhaps a small table showing the types of symbols/footprints were this is done. I think an image is very helpful and we can find a nice one at [1], but if we need to make our own let me know. Alternatively, I have pointed out several symbols which illustrate this. For S3.7:
For F2.4:
|
The image uses pin numbers which wouldl be confusing. I suggest making a similar one but instead of 1,2,3 use T,R,S Edit: i am not so sure that f2.4 and s3.7 are the correct rules to edit. On the footprint side we might want to add a rule similar to "by default footprints use the pin numbers indicated in the datasheet" and then list exceptions. (audio connectors, sd cards, ...) I would add it somewhere under F4 (would be best added as 4.3 but that would require moving all other rules.) Or we add these rules to the general section |
No description provided.
The text was updated successfully, but these errors were encountered: