├── .github
└── workflows
│ └── arduino-lint.yaml
├── .gitignore
├── LICENSE
├── README.md
├── REFERENCE.md
├── docs
├── README.md
├── am-241.png
├── bg.png
├── buttons.jpg
├── controls.png
├── enclosure_empty1.jpg
├── enclosure_empty2.jpg
├── enclosure_panel1.jpg
├── enclosure_panel2.jpg
├── flow.drawio
├── flow.drawio.svg
├── gamma_mca.png
├── glaze.png
├── img1.jpg
├── inside_box.jpg
├── lu-176-advanced.png
├── lu-176.png
├── mushrooms-advanced.png
├── mushrooms.png
├── na-22.png
├── oled.jpg
├── oshw.svg
├── pcb_back.png
├── pcb_front.png
└── pinout.png
├── enclosure
├── README.md
├── enhanced
│ ├── Case_Lower.stl
│ ├── Case_Upper.stl
│ ├── LCD_Bezel .stl
│ ├── Panel_Cover.stl
│ └── README.md
└── simple
│ ├── 3D
│ ├── OBJ_PCB.mtl
│ └── OBJ_PCB.obj
│ ├── Case_Body_ReducedHeight_USB-B.STL
│ ├── Case_Body_ReducedHeight_micro-USB.STL
│ ├── Case_Body_USB-B.STL
│ ├── Case_Body_micro-USB.STL
│ ├── Case_Cover.STL
│ ├── Case_Cover_Handle.STL
│ ├── Case_Cover_OpenGamma.STL
│ ├── Case_Cover_Window.STL
│ └── README.md
├── hardware
├── BOM.csv
├── Gerber_PCB
│ ├── Drill_NPTH_Through.DRL
│ ├── Drill_PTH_Through.DRL
│ ├── Drill_PTH_Through_Via.DRL
│ ├── Gerber_BoardOutlineLayer.GKO
│ ├── Gerber_BottomLayer.GBL
│ ├── Gerber_BottomPasteMaskLayer.GBP
│ ├── Gerber_BottomSilkscreenLayer.GBO
│ ├── Gerber_BottomSolderMaskLayer.GBS
│ ├── Gerber_DocumentLayer.GDL
│ ├── Gerber_InnerLayer1.G1
│ ├── Gerber_InnerLayer2.G2
│ ├── Gerber_TopLayer.GTL
│ ├── Gerber_TopPasteMaskLayer.GTP
│ ├── Gerber_TopSilkscreenLayer.GTO
│ └── Gerber_TopSolderMaskLayer.GTS
├── PCB_Project_EasyEDA.json
├── PickAndPlace_PCB.csv
├── README.md
├── SCH_Project_EasyEDA.json
└── schematic.pdf
├── kitspace.yaml
└── software
├── README.md
├── ogd_pico-4.3.2-overclocked.uf2
├── ogd_pico-4.3.2.uf2
└── ogd_pico
├── FS.cpp
├── FS.h
├── Helper.cpp
├── Helper.h
└── ogd_pico.ino
/.github/workflows/arduino-lint.yaml:
--------------------------------------------------------------------------------
1 | # Execute Arduino Lint automatically upon push or pull request
2 | on: [push, pull_request]
3 | jobs:
4 | lint:
5 | runs-on: ubuntu-latest
6 | steps:
7 | - uses: actions/checkout@v3
8 | - uses: arduino/arduino-lint-action@v1.0.2
9 | with:
10 | path: ./software/ogd_pico/
11 | project-type: sketch # Only Check Arduino Sketches
12 | library-manager: update
13 | compliance: specification #strict
14 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | .vscode/
2 | software/ogd_pico/build/
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 |
635 | Copyright (C)
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Copyright (C)
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 | # Open Gamma Detector
4 |
5 | ---
6 |
7 | **This is the latest hardware revision 4.2 using the Pico 2! For older revisions, please have a look at the [other branches](https://github.com/OpenGammaProject/Open-Gamma-Detector/branches). A comparison between the 4.0 and 3.x hardware can be found [here](https://hackaday.io/project/185211-all-in-one-gamma-ray-spectrometer/log/225597-revision-40-status-report).**
8 |
9 | **This project is also on [Hackaday.io](https://hackaday.io/project/185211-all-in-one-gamma-ray-spectrometer), where I post important project updates and other announcements!**
10 |
11 | Open hardware for a hackable gamma spectrometer all-in-one device using a popular NaI(Tl) scintillation crystal and a silicon photomultiplier (SiPM). Extremely affordable design for a powerful DIY gamma spectroscopy setup with a total parts cost of around 200 USD if you get all the individual parts and assemble them on your own.
12 |
13 | The detector uses a standard serial-over-USB and hardware UART connections so that it can be integrated into as many other projects as possible, for example data logging with a Raspberry Pi, weather stations, Arduino projects, etc. It includes both scintillation counter and multichannel analyzer (MCA) functions depending on how you want to use it.
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | If you want a more barebones version of the Open Gamma Detector to only count pulses or similar, you can have a look at the [Mini SiPM Driver](https://github.com/OpenGammaProject/Mini-SiD) board.
22 |
23 | ## Features
24 |
25 | Here are some of the most important specs:
26 |
27 | - Compact design: Total size 120 x 50 mm. Approx. 70.5 x 50 mm area for electronics and additional 49.5 x 50 mm to mount a scintillator.
28 | - All-in-one: No external parts (e.g. sound card) required to record gamma spectra.
29 | - Standalone spectra recordings on built-in flash.
30 | - Easily programmable using drag-and-drop firmware files or the standard Arduino IDE.
31 | - Low-voltage device: No HV needed like with photomultiplier tubes.
32 | - Can use SiPMs in the voltage range of 27.5 V to 33.8 V.
33 | - 4096 ADC channels with built-in 3 V voltage reference.
34 | - Energy resolution of up to 7% @ 662 keV possible; highly dependent on your SiPM/scintillator assembly.
35 | - Energy Mode: ~10 µs total dead time while measuring energy (default settings).
36 | - Geiger Mode: ~1 µs total dead time without energy measurements (default settings).
37 | - Low power consumption: ~15 mA @ 5 V with default firmware at normal background.
38 | - Built-in ticker (buzzer) for audible pulse count rate output.
39 | - Additional broken-out power pins and I2C, SPI and UART headers for custom parts (e.g. display, µSD card, etc.).
40 | - Simple OLED support out of the box (SSD1306 and SH110x).
41 | - Built-in True Random Number Generator.
42 |
43 | ## How To Get One
44 |
45 | - For quick access and purchase of all the parts (PCB and BOM), you can use [Kitspace](https://kitspace.org/opengammaproject/open-gamma-detector) (non-affiliated).
46 | - Otherwise, use a PCB manufacturer and an electronics distributor of your choice and proceed on your own. All the files you'll need can be found in this repo.
47 | - If you don't want to deal with all of that, feel free to contact me. Just send me an e-mail if you want and we'll figure something out.
48 |
49 | **You will also need to buy a SiPM (e.g. the MICROFC-60035-SMT-TR) and scintillator (NaI(Tl) recommended) separately at a distributor of your choice.** You might also want to grab one of the countless SiPM breakout boards I made.
50 |
51 | ## Working Principle
52 |
53 | Here is a nice flow chart to describe how the device roughly works:
54 |
55 | 
56 |
57 | ## Hardware
58 |
59 | Hardware design has been done with [EasyEDA](https://easyeda.com/) and all the needed files for you to import the project as well as the schematic can be found in the `hardware` folder. There is also a Gerber file available for you to go directly to the PCB manufacturing step.
60 |
61 | Detailed information about the hardware of the detector as well as the potentiometer settings and assembly can be found in the [hardware directory](/hardware/).
62 |
63 | ## Software
64 |
65 | The software aims to be as simple as possible to understand and maintain. To achieve this I decided to use an off-the-shelf microcontroller - the [Raspberry Pi Pico 2](https://www.raspberrypi.com/products/raspberry-pi-pico-2/). This board can be programmed with the Arduino IDE over micro-USB and is powerful (dual core, fast ADC, plenty of memory, ...) enough for the purpose and also exceptionally cheap.
66 |
67 | To program the Pico 2 and/or play around with the firmware, head to the [software directory](/software/). There you will also find documentation on the serial interface (!), display support, and much more.
68 |
69 | ## Troubleshooting and FAQ
70 |
71 | Please have a look at [REFERENCE.md](REFERENCE.md) for some general guidance.
72 |
73 | If this doesn't help you, feel free to reach out and create an issue or open a discussions thread.
74 |
75 | ## Example Spectra
76 |
77 | Here is a small collection of example spectra I could make quickly without putting much effort into the detector settings (threshold, SiPM voltage, software tweaks). I'm using the [Tiny MicroFC Breakout](https://github.com/OpenGammaProject/Tiny-MicroFC-Carrier-Board) and just a single SiPM (which isn't the optimal setup actually). In addition, neither the electronics nor the scintillator and sample were shielded from EMI or background radiation whatsoever. So as you can see the detector is actually pretty robust in that regard.
78 |
79 | Background spectrum (2h) with no samples:
80 |
81 | 
82 |
83 | Spectrum (2h) of two tiny (~5 g) LYSO scintillator showing two distinct gamma peaks (201.83, 306.78 keV) with an additional ~55 keV X-ray peak. The 307 keV peak has an energy resolution of ~14% in this case:
84 |
85 | 
86 |
87 | Spectrum (5min) of Am-241 commonly used in household ionization smoke detectors (e.g. in the US, no longer in the EU). Gamma peaks at 26.34 and 59.54 keV:
88 |
89 | 
90 |
91 | Spectrum (2h) of a small tea cup with pure Uraninite (also known as pitchblende) contents in its glaze. You can see all kinds of isotopes of the Uranium series including the Bi-214 peak at ~610 keV. Because they just used the pure Uraninite without any filtering whatsoever, there is also some U-235 in it and all the daughter radionuclides as well:
92 |
93 | 
94 |
95 | Spectrum (30min) of a Na-22 test source, about ~2 µCi made with a Rev.2 board (worse energy resolution than the latest version). You can see the 511 keV annihilation peak and the small 1275 keV gamma peak (much smaller due to limited NaI efficiency and small scintillator size for this energy) as well as the compton edge and continuum:
96 |
97 | 
98 |
99 | Spectrum (2h) of about 100 grams of mushrooms still containing the isotope Cs-137 from the Chernobyl disaster. You can clearly see the gamma peak at 662 keV and the ~32 keV X-ray peak. Resolution of the 662 keV peak was ~8.6%, using only a single SiPM and an old NaI scintillator:
100 |
101 | 
102 |
103 | ---
104 |
105 | **Here are some of the same spectra using a larger 1x1 inch scintillator rated at 6.9% @ 662 keV and a 2x2 SiPM array:**
106 |
107 | Spectrum (1h) of the same mushroom sample from above. This time the resolution at the 662 keV Cs-137 was 7.7%, not bad!
108 |
109 | 
110 |
111 | Spectrum (1h) of a small batch of Lutetium(III) oxide. It contains Lu-176 just like the LYSO scintillator sample from above. Therefore it also has the same peaks, just a lot more clear now. The 307 keV peak now has an energy resolution of 11.5%.
112 |
113 | 
114 |
115 | ## Known Limitations
116 |
117 | 1. ~~The Raspberry Pi Pico's ADC has some pretty [severe DNL issues](https://pico-adc.markomo.me/INL-DNL/#dnl) that result in four channels being much more sensitive (wider input range) than the rest. For now the simplest solution was to discard all four of them, by printing a `0` when any of them comes up in the measurement (to not affect the cps readings). You can turn this behavior off by using the `set correction` command. This is by no means perfect or ideal, but it works for now until this gets fixed in a later hardware revision of the RP2040 (wish us luck!).~~ Fixed by the Pico 2!
118 | 2. The power supply is **not** temperature corrected itself, meaning changes in the ambient temperature with a constant voltage affect the gain of the SiPM. This will naturally result in a different DC bias, energy range and S/N ratio. This effect is negligible around room temperature, though. The temperature dependence of the gain is -0.8%/°C (21°C) for the MicroFC SiPMs. **The latest [MicroFC SiPM carrier board](https://github.com/OpenGammaProject/MicroFC-SiPM-Carrier-Board) has automatic temperature compensation on-board however! So use that if you want to get the best performance out of it.**
119 |
120 | ## Some Ideas
121 |
122 | ### Coincidence Measurements
123 |
124 | Using multiple detector boards with some firmware modifications it should be theoretically possible to implement a coincidence measurement feature. By respectively connecting the `VSYS`, `GND` and one of the broken-out pins to each other on both boards you have everything you need to get started. The pins would be used for an interrupt from the child detector to the parent to trigger a pulse if both timings coincide.
125 |
126 | At the moment, though, I couldn't get a coincidence mode feature running due to some weird timing issues. There might be a firmware update in the future to implement this feature. If you have any ideas, let me know!
127 |
128 | ### Cooling the SiPM
129 |
130 | During operation all the electronics including the SiPM naturally heat up ever so slightly. Due to the detector board (where most of the power is dissipated) not being directly connected to the SiPM self-heating is negligible, though. Therefore air or water cooling alone won't improve performance considerably, because it won't heat up much above ambient temps, if at all that is. However, you could cool the SiPM PCB with a Peltier module to sub-ambient temperatures. According to the [datasheet AND9770 (Figure 27)](https://www.onsemi.com/pub/Collateral/AND9770-D.PDF) every 10°C reduction in temperature decreases the dark count rate by 50%! But be sure to correct the SiPM voltage (overvoltage) in this case as it also changes with temperature.
131 |
132 | Note that the required breakdown voltage of the SiPM increases linearly with 21.5 mV/°C, see the [C-Series SiPM Sensors Datasheet](https://www.onsemi.com/pdf/datasheet/microc-series-d.pdf). This means that you would also need to temperature correct the PSU voltage if you wanted to use it with considerably different temperatures.
133 |
134 | ### Shielding Background Radiation
135 |
136 | Shielding the ambient background can be done ideally using a wide enough layer of lead (bricks) all around the detector with a thin layer of lower-Z material on the inside such as copper to avoid backscattering. The SiPM and the sample can then be put into the structure to get the best measurements possible (low background).
137 |
138 | See Wikipedia: [Lead Castle](https://en.wikipedia.org/w/index.php?title=Lead_castle&oldid=991799816)
139 |
140 | ## Related Projects
141 |
142 | This is a list of other awesome projects that are relevant or directly related to this one:
143 |
144 | - [OpenDosimeter](https://opendosimeter.org/): A low-cost dosimeter with open-source hardware and software inspired heavily by the Open Gamma Detector.
145 | - [CosmicWatch](http://www.cosmicwatch.lns.mit.edu/): A neat all-in-one device to detect muons. Completely open-source and designed for university students and schools. This project was the original inspiration to start with the Open Gamma Project.
146 | - [OpenGammaKit](https://github.com/vikulin/OpenGammaKit/): Re-design of the Open Gamma Detector hardware using KiCAD, with additionally updated software for mobile use.
147 |
148 | Check them out and let me know what you think. Special thanks to all of the contributors and the entire community for making this possible!
149 |
150 | ---
151 |
152 | Thanks for reading.
153 |
--------------------------------------------------------------------------------
/REFERENCE.md:
--------------------------------------------------------------------------------
1 | # Troubleshooting and FAQ
2 |
3 | ## Troubleshooting
4 |
5 | ### My device freezes or crashes periodically
6 |
7 | Make sure that the threshold setting is not set too low! If that's the case you should see the ACTivity LED blinking heavily or even staying on solid. The buzzer might also give you a great indication of the correct count rate setting. In this case, noise is probably overwhelming the detector and forcing it to reset.
8 |
9 | If this is not the case for you, reflash the firmware, reset all the settings and reboot the device. If the problem persists, please feel free to open an issue on GitHub.
10 |
11 | ### My device is not recognized by my computer
12 |
13 | Make sure you are using a micro-USB cable that can be used for data transmission! There are micro-USB cables for powering/charging devices only and they can be easily mistaken for a data cable.
14 |
15 | If this isn't the case for you and it doesn't get recognized at all (even while holding the `BOOTSEL` button), there might be a manufacturing defect or you might have made a mistakes when soldering the parts. Feel free to get in touch if that's the case.
16 |
17 | ### Settings on the device are not saved
18 |
19 | If you flashed it via the Arduino IDE be sure to select `Flash Size: "4MB (Sketch: 1MB, FS: 3MB)"`. Without these 64 KB of flash assigned to the file system, the Pico is unable to create and save a settings file.
20 |
21 | ### ~~I am seeing a sharp peak immediately around ADC channel 511~~
22 |
23 | ~~That is right, this is due to the DNL issues with the RP2040 ADC as described in the [Known Limitations](README.md#known-limitations) section of the readme.~~
24 |
25 | ~~This effect would have been much worse without some simple corrections in the firmware. Since there is currently no hardware fix, this is what we have to live with unfortunately. If you know about it, you can just ignore it since all the *real* peaks of the scintillator are much wider than that.~~ Fixed by the Pico 2.
26 |
27 | ### ~~There is always a peak at ADC channel 0~~
28 |
29 | ~~That is intentional behavior of the device. For the same reason as above, four ADC channels are ignored for the energy measurement.~~
30 |
31 | ~~Since this would potentially highly influence the count rate, giving lower values than there actually are, these counts are added back to the spectrum to ADC channel 0.~~
32 |
33 | ~~This way, all the counts are registered, but since there is actually never a signal near channel 0, you can clearly distinguish between the "right" spectrum and the rest.~~
34 |
35 | ~~If you want to disable this behavior, you can do so by using the `set correction` command over the serial interface. This will still omit the ADC channel readings, but won't create another peak at 0. In geiger mode, there will always only be a channel `0` since this is how the current cps is calculated.~~ Fixed by the Pico 2.
36 |
37 | ### There is always a peak near ADC channel 4095
38 |
39 | The ADC reference voltage is set to 3 Volts. Anything larger than that gets clipped, because the ADC cannot read higher voltages, meaning all pulses larger than 3V accumulate at the maximum ADC channel -- in this case 4095. That is completely normal behavior.
40 |
41 | ---
42 |
43 | ## FAQ
44 |
45 | ### How to update the firmware?
46 |
47 | Press and hold the "BOOTSEL" button on the Raspberry Pi Pico while plugging it into your USB port. It will then show up in your file explorer and you can once again drag-and-drop the firmware file. This also works if your device is completely frozen or crashed.
48 |
49 | ### Can I use a plastic scintillator?
50 |
51 | No, these cannot be used for gamma spectroscopy except in some edge cases. Generally, they have much worse efficiency than your typical inorganic scintillator, like NaI(Tl) or CsI(Tl), and extremely poor energy resolution.
52 |
53 | If you want to *just* count pulses (i.e. **not** measure pulse energy), plastic scintillators can be a better fit, because of their really low cost. If you want to count pulses only, though, it's probably better to use the simpler and much cheaper [Mini SiD](https://github.com/OpenGammaProject/Mini-SiD) board instead of the Open Gamma Detector. With plastic scintillators you can also detect high-energy particles such as beta radiation or muons, which NaI(Tl) generally cannot.
54 |
55 | ### How do I change the gain?
56 |
57 | Since hardware revision 3 the gain is fixed on all boards and cannot be changed without any hardware modifications. This makes it **much** easier to provide a device that has a very high chance of working out of the box without much fiddling around with pot settings or additional components.
58 |
59 | A downside of this is that different scintillator sizes, while working most of the time now, provide slightly different energy ranges and therefore bin per energy resolutions. Normally, this shouldn't be a problem, though.
60 |
61 | If you want to change the gain for whatever reason, you can do so by soldering the optional trim pot on the board (R20) with a [compatible pot (e.g. 5k)](https://www.lcsc.com/product-detail/Variable-Resistors-Potentiometers_BOURNS-3314J-1-502E_C58391.html). Be sure to also remove the existing 0605 resistors R7 and R11 in that case. You can then change the gain from roughly 1 to 6 on the fly.
62 |
63 | ### How do I calibrate the device?
64 |
65 | You have to get a material with at least two known gamma peaks and calibrate the detector using these two peaks. In the Gamma MCA calibration tab you select the two peak ADC channels and assign their gamma-ray energy.
66 |
67 | Ideally you want to use three peaks distributed evenly over your whole energy range to use the best calibration.
68 |
69 | ### Why don't you use a TIA or CSP or change X or Y?
70 |
71 | This device is made to be as simple and cheap as possible, while still yielding as great results as possible. In effect it is a compromise to get the best price-performance ratio.
72 |
73 | Of course, you could use transimpedance or charge-sensitive preamplifiers, however this would significantly increase complexity as you'd need additional parts for the correct power supplies and so on. Using more expensive amplifiers would surely also be an option.
74 |
75 | If you wanted to go the maximum-performance route, you'd also need to use a different microcontroller with a much better ADC, and maybe even consider using 4-layer boards with additional ground and power planes. Essentially, you'd have to re-design the whole board at this point.
76 |
77 | Instead of something like 8-10% energy resolution @ 662 keV (highly dependent on your SiPM/scintillator assembly), you'd then maybe get as much as 6% if you're lucky, which is the limit for most NaI or CsI scintillators anyways. That would come at a much higher cost, though. In my opinion, you get to a point of diminishing returns quickly, especially when designing an entry-level device such as this.
78 |
79 | ### Notes on different microcontrollers
80 |
81 | The Pico 2 is readily available virtually everywhere and it's really cheap. This makes it ideal for use in this kind of "simple" and cheap project. There are a couple of reasons I like to use it. You can read more about it in the [discussions thread about switching to the ESP32](https://github.com/OpenGammaProject/Open-Gamma-Detector/discussions/43).
82 |
--------------------------------------------------------------------------------
/docs/README.md:
--------------------------------------------------------------------------------
1 | ## Docs
2 |
3 | This folder includes all the files needed for the README and stuff.
4 |
--------------------------------------------------------------------------------
/docs/am-241.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/am-241.png
--------------------------------------------------------------------------------
/docs/bg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/bg.png
--------------------------------------------------------------------------------
/docs/buttons.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/buttons.jpg
--------------------------------------------------------------------------------
/docs/controls.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/controls.png
--------------------------------------------------------------------------------
/docs/enclosure_empty1.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/enclosure_empty1.jpg
--------------------------------------------------------------------------------
/docs/enclosure_empty2.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/enclosure_empty2.jpg
--------------------------------------------------------------------------------
/docs/enclosure_panel1.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/enclosure_panel1.jpg
--------------------------------------------------------------------------------
/docs/enclosure_panel2.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/enclosure_panel2.jpg
--------------------------------------------------------------------------------
/docs/flow.drawio:
--------------------------------------------------------------------------------
1 | 7VptV6M4FP41PUc/2EN5K36cqqPurh53687oxxRuIWsgPSHUdn79JmkoINRFB6Wds1UruUlIyH2ee29uGFhn8eqSoUV0QwMgA9MIVgPrfGCaI9s0B/LXCNYbydjRgpDhQDcqBFP8A7TQ0NIMB5BWGnJKCceLqtCnSQI+r8gQY/S52mxOSXXUBQqhJpj6iNSl33HAo43UM8eF/ApwGOUjj9zTTU2M8sb6SdIIBfS5JLIuBtYZo5RvruLVGRC5ePm6bPp93VG7nRiDhLfpcDH9zRt9OX00JsbT/e8PlpkszRPb3txmiUimn3gKDCOlRMSR+Eczvsi4fga+zhcGArFOukgZj2hIE0QuCumE0SwJQI5uiFLR5g9KF0I4EsJ/gPO1VjrKOBWiiMdE18IK8wfZfejo0mOp5nyl76wK67yQcLZ+KBceizvIYtFNlfJ+9dXUC5zSjPnwyhLmqEQsBP5KO40YuW6lAbSuLoHGIOYjGmjqnBhDrRsGBHG8rAISaVyH247be91RLJ6haELn8xR4GRviojRkIVKIeQN6HKOGnoHpErEKkwAvxWUoLxmo4Q0058DyejFeqUlDrxhQmjGIpT529OkTkeMyJI12kBztGySt0dswaQyFQT/dd1SOaqC8wT6jwkNwRgmRGDROxN+Xc3F/F8VC9ZNkli7Ukhuc4TAElorLgS3wbVzf3tegVgXSc4Q5TBdI6eRZ+MEqaOaYkDNKKFN9rcABL7CFPBXTeYJSjWfOLNd9TfNLYBxWbVRl2Zqb2u86efm58GKj3DVFJQ/mGrtVWdHUm9Vi1fSyFI5c+l/xrIwuBB+xZKNy8eKLqEmJuyYckhTzdS+M3/qTgq9byn8Iec2W5M2J+J/kfS9TNZJso4oky3mBkM1Mda/u6WzWIxRMsGCzEN5FlNM4k+EgwYrYR1N8d3PcKWHnc3B9v4mwwfh0Zryq7fcT1uyfsHVD2uCnF1IFiYrAMwWbJipDAixc571n7KXf79+zv5+vVlu+dk3Xn1Ju3RhPfUFggXzEqSTSwJnAMBQXt+j66J4cD5zzbt0gAm/eyCrX92A2/xhWjfpnVVPMfEh4t9sGl3uF9/o+t8GWXaI4lltehgKMpAVraZ9+yrs48qeRB+oje4jItSTffLrhx8jdO37U/X2DpkxPB/GWUKzx7VfwI27HfiTXqFbU/u7X3Hcp3JC7t6/yy5hRmnIVgSQK+TuTDF3S1vOhOSiceY7tdBQUuqMeg8Lk6v77xbVtrW6NP68cF9npX0mDspxvffAsz8Tk16WUSovcYHUvt93ndb6XG7fktNuXr2zUsfe/jj9Ax95exUPjNkb37+lksD1aUeGQcSQ2BUM1S5+yACdyhxDAEvtw/JnB0q6QaHcQ1YE1tq2qNXZ7t8b1qNYaWr1w9f388Vryp22u+mDinrqZ3ShPTDnM9Db84CIWx9y3vLPl1NYZJz4DlIJM8hc5aJWpQsqecWHv0IxIKYGlPNI+JEblmeHuzn8+xyfl8y5p6pYmJ1hF9RtXQxfA0Da3iOIFwXOV+D34fK/VP1GaNmKHhPsczp25kk9KTbXKeJTOJdGMLpXBiqD1cTqPGKSRfPulZPL2JWmyPVbvIND/wIO5tmbVfvOxum171r6HKzm7SjC9A/S09Zfq1MDHzM+wnNCRrkSJhNyVQN6vcCpn926l7frJTYBDzJVDbHpXYa9Ntt21ydZ6Otn/8N9u4FNGUmnYz3HqMxzjJD+Lk7XGGY3FEueiw+PSy7OGj9waiGLxZuVGY8X7qdbFvw==
--------------------------------------------------------------------------------
/docs/gamma_mca.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/gamma_mca.png
--------------------------------------------------------------------------------
/docs/glaze.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/glaze.png
--------------------------------------------------------------------------------
/docs/img1.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/img1.jpg
--------------------------------------------------------------------------------
/docs/inside_box.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/inside_box.jpg
--------------------------------------------------------------------------------
/docs/lu-176-advanced.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/lu-176-advanced.png
--------------------------------------------------------------------------------
/docs/lu-176.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/lu-176.png
--------------------------------------------------------------------------------
/docs/mushrooms-advanced.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/mushrooms-advanced.png
--------------------------------------------------------------------------------
/docs/mushrooms.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/mushrooms.png
--------------------------------------------------------------------------------
/docs/na-22.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/na-22.png
--------------------------------------------------------------------------------
/docs/oled.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/oled.jpg
--------------------------------------------------------------------------------
/docs/oshw.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/docs/pcb_back.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/pcb_back.png
--------------------------------------------------------------------------------
/docs/pcb_front.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/pcb_front.png
--------------------------------------------------------------------------------
/docs/pinout.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/docs/pinout.png
--------------------------------------------------------------------------------
/enclosure/README.md:
--------------------------------------------------------------------------------
1 | # Enclosures
2 |
3 | In the following folders you can find different enclosures for the Open Gamma Detector.
4 |
--------------------------------------------------------------------------------
/enclosure/enhanced/Case_Lower.stl:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/enclosure/enhanced/Case_Lower.stl
--------------------------------------------------------------------------------
/enclosure/enhanced/Case_Upper.stl:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/enclosure/enhanced/Case_Upper.stl
--------------------------------------------------------------------------------
/enclosure/enhanced/LCD_Bezel .stl:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/enclosure/enhanced/LCD_Bezel .stl
--------------------------------------------------------------------------------
/enclosure/enhanced/Panel_Cover.stl:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/OpenGammaProject/Open-Gamma-Detector/7f8ad6533d0133a020241e0ffb1acf2bf8966e12/enclosure/enhanced/Panel_Cover.stl
--------------------------------------------------------------------------------
/enclosure/enhanced/README.md:
--------------------------------------------------------------------------------
1 | # Parts List
2 |
3 | Here are all the parts you need to build this 3D printed enclosures. It's compatible with the Open Gamma Detector Rev. 2, 3 and 4 and also a lot more handy and smaller than the simple case.
4 |
5 | The case is designed to fit a scintillator with a maximum size of 5 x 5 x 5 cm. The USB connection can be accessed through a hole in the front.
6 |
7 | You can have a look at all the different designs by uploading them to [ViewSTL](https://www.viewstl.com/).
8 |
9 | All of the design work has been done by [@sebyon](https://github.com/sebyon), many thanks!
10 |
11 | ---
12 |
13 |