René's URL Explorer Experiment


Title: Off by 0.1mm in allowed thickness calculations for input module · Issue #14 · FrameworkComputer/InputModules · GitHub

Open Graph Title: Off by 0.1mm in allowed thickness calculations for input module · Issue #14 · FrameworkComputer/InputModules

X Title: Off by 0.1mm in allowed thickness calculations for input module · Issue #14 · FrameworkComputer/InputModules

Description: Between the spacer dimensions in Mechanical/Small/Module/c1_design_space_ref.pdf and the PCB limit area dimensions in Mechanical/Small/PCB/c1_pcb_concept_design_ref.pdf there appears to be an "off by 0.1mm" error, caused by double-counti...

Open Graph Description: Between the spacer dimensions in Mechanical/Small/Module/c1_design_space_ref.pdf and the PCB limit area dimensions in Mechanical/Small/PCB/c1_pcb_concept_design_ref.pdf there appears to be an "off ...

X Description: Between the spacer dimensions in Mechanical/Small/Module/c1_design_space_ref.pdf and the PCB limit area dimensions in Mechanical/Small/PCB/c1_pcb_concept_design_ref.pdf there appears to be an "...

Opengraph URL: https://github.com/FrameworkComputer/InputModules/issues/14

X: @github

direct link

Domain: patch-diff.githubusercontent.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Off by 0.1mm in allowed thickness calculations for input module","articleBody":"Between the spacer dimensions in `Mechanical/Small/Module/c1_design_space_ref.pdf` and the PCB limit area dimensions in `Mechanical/Small/PCB/c1_pcb_concept_design_ref.pdf` there appears to be an \"off by 0.1mm\" error, caused by double-counting the 0.1mm difference between the nominal 0.9mm thickness of the top edge alignment feature and the 0.8mm thickness of the PCB (and this applies also for the \"1.0 mm thick PCB\" variant, which appears to be based on the 0.8mm thick PCB and assumes the top edge of the PCB is milled down 0.2mm, and so inherits the mistake from the 0.8mm PCB design).\r\n\r\nThere appears to be /second/ 0.1mm of \"clearance\" in the PCB design.\r\n\r\nApologies for lack of a diagram, here's the pure math.  Starting from the non-PCB design, which appears to match the actual production spacer hardware I have in measuring 2.35mm thick at the top edge, with an alignment feature 0.9mm thick, and installed it sits flush with the keyboard lattice.  Starting from the midplate and working up, that 2.35mm of thickness is divided up as:\r\n\r\n* 0.50mm below the top edge alignment feature\r\n* 0.90mm for the top edge alignment feature\r\n* 0.95mm above the top edge alignment feature\r\n\r\n(The `c1_design_space_ref.pdf` implicitly indicates 0.95 for the top edge feature and explicitly marks 0.90 above it,  but (a) that doesn't match the production spacer I measured, and (b) it doesn't affect this next stackup which is keyed off the /bottom/ of the alignment feature.)\r\n\r\nThe stack up for the PCB design *should* be, I believe:\r\n* 0.1mm of \"clearance\" below bottom-side components **\u003c- this is not indicated**\r\n* 0.4mm for bottom-side components\r\n* 0.8mm for the PCB, sitting flush to the bottom of the 0.9mm allowance for the alignment feature\r\n* 1.05mm above the top of the PCB **\u003c- this is the error, it is marked as 0.95mm**\r\n\r\nWhichever correction is applied to the 0.8mm PCB drawing would need to be applied to the 1.0mm PCB drawing as well; most likely the top side clearances for both would be bumped up by 0.1mm: 0.85mm \"flush to lattice\" for the 1.0mm PCB and 1.05mm \"flush to lattice\" for the 0.8mm PCB, and the \"flush to C deck\" numbers bumped as well.\r\n\r\nIt seems that the root cause here was not taking account the 0.1mm thickness difference between the 0.8mm PCB and the nominal 0.9mm alignment feature in recomputing the top side allowances.\r\n\r\nThe \"0.1mm of clearance below bottom side components\" is also not clearly marked on the PCB-concept drawings, but is easily inferred from the \"0.5t spacer\" which *is* marked.  If the spacer is 0.5mm tall and there is only 0.4mm height allowance for bottom-side components, the difference must be due to an undocumented clearance provided; especially since the non-PCB CAD drawing clearly indicates 0.5mm thickness below the alignment feature for that entire portion.\r\n\r\nI'm certain this is splitting hairs, but I'm posting this in case it helps other folks staring at the top sets of CAD design files and trying to make the numbers add up.  The allowed thickness above the PCB has been a recurrent concern for input module design (especially in the keyboard area!) so I'm sure the additional 0.1mm will be welcomed by some. :)  Certainly I'd appreciate confirmation that my understanding is correct.","author":{"url":"https://github.com/cscott","@type":"Person","name":"cscott"},"datePublished":"2024-07-11T03:00:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/14/InputModules/issues/14"}

route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:69f5886a-4792-8a46-f851-181e645d55ba
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idD520:319DA7:612242:7EDC0D:69765BA5
html-safe-nonce2b329dec29c40bdc2792fce0bb35ad95c19f35072e0da9cda253b1cd11835e27
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJENTIwOjMxOURBNzo2MTIyNDI6N0VEQzBEOjY5NzY1QkE1IiwidmlzaXRvcl9pZCI6IjM5MjcyMTQ5NjY0NzcwNTI4MzciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac2040e02ff9a4ae60adebbbff254acceb271cb8f676f005584c11d571498f3850
hovercard-subject-tagissue:2402127534
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/FrameworkComputer/InputModules/14/issue_layout
twitter:imagehttps://opengraph.githubassets.com/bb3de0d63512dd5d02c14cfaafb551dacb2d03f636ceea04740542985fbaccfd/FrameworkComputer/InputModules/issues/14
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/bb3de0d63512dd5d02c14cfaafb551dacb2d03f636ceea04740542985fbaccfd/FrameworkComputer/InputModules/issues/14
og:image:altBetween the spacer dimensions in Mechanical/Small/Module/c1_design_space_ref.pdf and the PCB limit area dimensions in Mechanical/Small/PCB/c1_pcb_concept_design_ref.pdf there appears to be an "off ...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamecscott
hostnamegithub.com
expected-hostnamegithub.com
None032152924a283b83384255d9489e7b93b54ba01da8d380b05ecd3953b3212411
turbo-cache-controlno-preview
go-importgithub.com/FrameworkComputer/InputModules git https://github.com/FrameworkComputer/InputModules.git
octolytics-dimension-user_id58124942
octolytics-dimension-user_loginFrameworkComputer
octolytics-dimension-repository_id565703470
octolytics-dimension-repository_nwoFrameworkComputer/InputModules
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id565703470
octolytics-dimension-repository_network_root_nwoFrameworkComputer/InputModules
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release5b577f6be6482e336e3c30e8daefa30144947b17
ui-targetfull
theme-color#1e2327
color-schemelight dark

Links:

Skip to contenthttps://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues/14#start-of-content
https://patch-diff.githubusercontent.com/
Sign in https://patch-diff.githubusercontent.com/login?return_to=https%3A%2F%2Fgithub.com%2FFrameworkComputer%2FInputModules%2Fissues%2F14
GitHub CopilotWrite better code with AIhttps://github.com/features/copilot
GitHub SparkBuild and deploy intelligent appshttps://github.com/features/spark
GitHub ModelsManage and compare promptshttps://github.com/features/models
MCP RegistryNewIntegrate external toolshttps://github.com/mcp
ActionsAutomate any workflowhttps://github.com/features/actions
CodespacesInstant dev environmentshttps://github.com/features/codespaces
IssuesPlan and track workhttps://github.com/features/issues
Code ReviewManage code changeshttps://github.com/features/code-review
GitHub Advanced SecurityFind and fix vulnerabilitieshttps://github.com/security/advanced-security
Code securitySecure your code as you buildhttps://github.com/security/advanced-security/code-security
Secret protectionStop leaks before they starthttps://github.com/security/advanced-security/secret-protection
Why GitHubhttps://github.com/why-github
Documentationhttps://docs.github.com
Bloghttps://github.blog
Changeloghttps://github.blog/changelog
Marketplacehttps://github.com/marketplace
View all featureshttps://github.com/features
Enterpriseshttps://github.com/enterprise
Small and medium teamshttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
App Modernizationhttps://github.com/solutions/use-case/app-modernization
DevSecOpshttps://github.com/solutions/use-case/devsecops
DevOpshttps://github.com/solutions/use-case/devops
CI/CDhttps://github.com/solutions/use-case/ci-cd
View all use caseshttps://github.com/solutions/use-case
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
View all industrieshttps://github.com/solutions/industry
View all solutionshttps://github.com/solutions
AIhttps://github.com/resources/articles?topic=ai
Software Developmenthttps://github.com/resources/articles?topic=software-development
DevOpshttps://github.com/resources/articles?topic=devops
Securityhttps://github.com/resources/articles?topic=security
View all topicshttps://github.com/resources/articles
Customer storieshttps://github.com/customer-stories
Events & webinarshttps://github.com/resources/events
Ebooks & reportshttps://github.com/resources/whitepapers
Business insightshttps://github.com/solutions/executive-insights
GitHub Skillshttps://skills.github.com
Documentationhttps://docs.github.com
Customer supporthttps://support.github.com
Community forumhttps://github.com/orgs/community/discussions
Trust centerhttps://github.com/trust-center
Partnershttps://github.com/partners
GitHub SponsorsFund open source developershttps://github.com/sponsors
Security Labhttps://securitylab.github.com
Maintainer Communityhttps://maintainers.github.com
Acceleratorhttps://github.com/accelerator
Archive Programhttps://archiveprogram.github.com
Topicshttps://github.com/topics
Trendinghttps://github.com/trending
Collectionshttps://github.com/collections
Enterprise platformAI-powered developer platformhttps://github.com/enterprise
GitHub Advanced SecurityEnterprise-grade security featureshttps://github.com/security/advanced-security
Copilot for BusinessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/premium-support
Pricinghttps://github.com/pricing
Search syntax tipshttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
documentationhttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
Sign in https://patch-diff.githubusercontent.com/login?return_to=https%3A%2F%2Fgithub.com%2FFrameworkComputer%2FInputModules%2Fissues%2F14
Sign up https://patch-diff.githubusercontent.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=FrameworkComputer%2FInputModules
Reloadhttps://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues/14
Reloadhttps://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues/14
Reloadhttps://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues/14
FrameworkComputer https://patch-diff.githubusercontent.com/FrameworkComputer
InputModuleshttps://patch-diff.githubusercontent.com/FrameworkComputer/InputModules
Notifications https://patch-diff.githubusercontent.com/login?return_to=%2FFrameworkComputer%2FInputModules
Fork 16 https://patch-diff.githubusercontent.com/login?return_to=%2FFrameworkComputer%2FInputModules
Star 215 https://patch-diff.githubusercontent.com/login?return_to=%2FFrameworkComputer%2FInputModules
Code https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules
Issues 5 https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues
Pull requests 0 https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/pulls
Actions https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/actions
Projects 0 https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/projects
Security 0 https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/security
Insights https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/pulse
Code https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules
Issues https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues
Pull requests https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/pulls
Actions https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/actions
Projects https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/projects
Security https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/security
Insights https://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/pulse
New issuehttps://patch-diff.githubusercontent.com/login?return_to=https://github.com/FrameworkComputer/InputModules/issues/14
New issuehttps://patch-diff.githubusercontent.com/login?return_to=https://github.com/FrameworkComputer/InputModules/issues/14
Off by 0.1mm in allowed thickness calculations for input modulehttps://patch-diff.githubusercontent.com/FrameworkComputer/InputModules/issues/14#top
https://github.com/cscott
https://github.com/cscott
cscotthttps://github.com/cscott
on Jul 11, 2024https://github.com/FrameworkComputer/InputModules/issues/14#issue-2402127534
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.