GMU:Printed Circuit Board Art/mxkllmnn: Difference between revisions

GMU:Printed Circuit Board Art/mxkllmnn (view source)

Revision as of 10:07, 8 March 2022

25 bytes removed , 8 March 2022

no edit summary

Mxkllmnn

157

edits

@@ Line 18: / Line 18: @@
 The unicorn also led to my first project idea: Adaptors. That is because modern (read: Apple) computers (mine included) exist in a dream world where all its peripherals work with USB type C, whereas I find myself in the reality of 2022, where they do not. Everywhere I go I have to take many different adaptors to make my computer (that obviously supports USB type C only) work. So the idea was to have a unicorn (read: Swiss Army knife) to help out. [[File:swinehorn_original.png|800px]]
 Unfortunately, when I tore down one of the adaptors available at the local electronics market, I found <I>myself</i> in a dream world. This time I realized that I do not have the electrical engineering degree I needed to understand the not-as-easy-as-I-thought circuitry of connecting different interface systems (HDMI/SD/Audio Jack/USB-A to USB-C). Even though it seems rather simple to transmit signals through copper traces, many components are necessary in between, if their ends do not speak the same language. From the picture one can see that there is at least one IC per interface, as well as quartz to translate between signals of different frequencies, not to speak of numerous capacitors, resistors, and regulators. So I started all over again.
+<center>
 <gallery>
 File:Adaptor02.jpg
 File:Adaptor03.jpg
 </gallery>
+</center>
 '''The SwitchSwitch Concept:'''
@@ Line 30: / Line 30: @@
 Very briefly, I wrack my head around systems whose user interfaces had to be modified as the result of process automation. In most cases, if the cybernetic loop of control and display is being altered, a transformation of the underlying system’s user interface is implicit. In home automation, for example, this has led to the disappearance of well-established interfaces (read: Switches) and now all too often leaves us frustrated [https://www.busch-jaeger.de/fileadmin/_processed_/c/7/csm_Systeme_free%40home_Image_1920x800_108960d603.jpeg]. So I am exploring alternatives to popular but dystopian smart home futures, or: How to teach old switches new tricks.
-One idea for this course was to introduce capacitive touch areas – a formation of discrete sensor pads, sliders, or a matrix (see sketches below) – to the surface and the frame of a conventional switch, where the PCB itself serves as the cover. By that, one would extend the switch’s binary characteristic and broaden the repertoire of input gestures.
+One idea for this course was to introduce capacitive touch areas – a formation of discrete sensor pads, sliders, or a matrix (see sketches below) – to the surface and the frame of a conventional switch, where the PCB itself serves as the cover with all components on one side and touchpads on its rear. By that, one would extend the switch’s binary characteristic and broaden the repertoire of input gestures. However, I soon realised that such a modification would undermine exactly what I am trying to preserve – the switching mechanism’s inherent psychophysical feedback that makes this kind of interface so appealing. Such feedback is in vain with touch displays that replace great user interfaces, which are actually much more in line with our human sensory nature. With regard to automation, going for graphical user interfaces (GUIs) is an obvious choice, as these are much easier to integrate due to their ability to react to system changes simply by programming, whereas physical switches do not respond automatically. So the idea to have a remotely switchable switch was born, hence the working title SwitchSwitch. Furthermore, by temporarily decoupling the switch from the circuit of the object to be turned on or off and putting a microcontroller in between, the (automated) system becomes capable of utilizing the acoustic, visual and haptic signals evoked via the usage of its interface to articulate intent (at least this is the hypothesis to be confirmed). The SwitchSwitch prototype functions as a platform to design output gestures made of sequences of clicks in combination with flickering lights as means of communication. To do so a conventional switch has been equipped with some more advanced technology. Now this project is about turning this technology into an appropriate form.
-<gallery>
-File:capacitiveTouch01.png
-File:capacitiveTouch02.png
-</gallery>
-However, I soon realised that such a modification would undermine exactly what I am trying to preserve – the switching mechanism’s inherent psychophysical feedback that makes this kind of interface so appealing. Such feedback is in vain with touch displays that replace great user interfaces, which are actually much more in line with our human sensory nature. With regard to automation, going for graphical user interfaces (GUIs) is an obvious choice, as these are much easier to integrate due to their ability to react to system changes simply by programming, whereas physical switches do not respond automatically. So the idea to have a remotely switchable switch was born, hence the working title SwitchSwitch. Furthermore, by temporarily decoupling the switch from the circuit of the object to be turned on or off and putting a microcontroller in between, the (automated) system becomes capable of utilizing the acoustic, visual and haptic signals evoked via the usage of its interface to articulate intent (at least this is the hypothesis to be confirmed). The SwitchSwitch prototype functions as a platform to design output gestures made of sequences of clicks in combination with flickering lights as means of communication. To do so a conventional switch has been equipped with some more advanced technology. Now this project is about turning this technology into an appropriate form.
 {{#ev:youtube|bJHKXVJdB_M}}
@@ Line 49: / Line 42: @@
 '''Design:'''
-The design was very much influenced by the early thoughts on the topic of "capacitive touch". I would have installed all the technical components in a [https://www.instructables.com/Dead-Bug-Prototyping-and-Freeform-Electronics/ dead bug] fashion, disappearing into the flush socket of the wall, if it hadn't been for the idea of realising the entire backend as a PCB in the front, with touchpads on its rear. However, when the idea of touch input gestures was dropped (because this contrasted with highlighting mechanical devices), all that was left were components that logically belong to the backend. Yet, having everything fit tightly into the cover of the switch makes debugging very easy. By removing it, all the connections are accessible. So the transfer from breadboard to a PCB was the only logical consequence.
+The design was very much influenced by the early thoughts on the topic of <i>capacitive touch</i>. I would have installed all the technical components in a [https://www.instructables.com/Dead-Bug-Prototyping-and-Freeform-Electronics/ dead bug] fashion, disappearing into the flush socket of the wall, if it hadn't been for the idea of realising the entire backend as a PCB in the front. However, when the idea of touch input gestures was dropped (because this contrasted with highlighting mechanical devices), all that was left were components that logically belong to the backend. Yet, having everything fit tightly into the cover of the switch makes debugging very easy. By removing it, all the connections are accessible. So the transfer from breadboard to a PCB was the only logical consequence.
 [[File:BackAsFront.png|800px]]
 Before going into detail about the actual layout or so-called floor planning, I would like to add a few sentences about the look. The new subject shifted the focus slightly to more technical/constructional aspects, which is why I felt the need to add a graphical element.