Skip to content

Documenting r3.6 & r3.7? #28

@mrienstra

Description

@mrienstra

Looks like tags stop at r3.5a.

Would be helpful to clarify what is officially considered revision 3.7 & 3.6 (and perhaps also alpha revisions). Not sure if going back further and filling in the gap between 3.5a and 3.6a is worthwhile or not, not sure how many of those were made.

revision 3.7

All PRs and commits which mention 3.7 (new to old):

#26: Corrected the potentiometer fixing hole.
Increased hole 2.00 to 2.31 mm.
(doesn't mention 3.7, but technically the latest version, maybe this is r3.7.1?)

#23: Some changes to panels before production
I've made some small changes to the panels before production to increase reliability.
I took the opportunity to split the panels into two files to remove the VCut separation that can be ugly sometimes and definitely opened the 8ML-4 connector since we will be only producing the version with that connector.
(a comment mentions "rely[ing] on panel differences to distinguish 3.6 from 3.7", suggesting this PR is part of 3.7 and not 3.6)

ada1ed4
Cyclops 3.7a

  • Replace 1 turn pot with 10 turn pot
  • Update panels to fit it
  • Add JST wire to board connector to connect it

4a701e2
Changes to revision 3.7 after in the field testing

  • Some small moves on the panel and pcb for manufacturing purposes

revision 3.6

All PRs and commits which mention 3.6 (new to old):

d234c57
Merge branch '3.6-production'

544ad60
Manual update for 3.6

  • Device assembly is no relatively up to date for 3.6 production.
  • Fixed more erros found in pre-production check by Filipe.
  • Added images of production process.

27fb19a
Ready for 3.6 production

  • These designs are up to date for 3.6 production
  • I need to create an assembly manual before moving forward

18c7e44
Final fixes for 3.6

  • Fixed issue with parasitic oscillation in BJT booster stage
  • Fixed issue with bandwidth limit selection by simply removing cold
    switch and using the straight panel switch -- extra trace length does
    not matter because it engages the BW limit (self correcting)
  • Should be ready for production and master merge

43a96a7
Minor fixes after assembly of 3.6

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions