Week 16 Updates

src/views/Week16.vue

@@ -47,7 +47,11 @@
                 <li>The part was cut using a laser machine.</li>
                 <li>We attached the finished part to the Pen Plotter, completing the setup.</li>
             </ul>
-
+            <p>So basically, we had a Pen Plotter machine that we could operate with G-Code, and a Hot-Wire Cutter, 
+              which had no 'intelligent' parts—only a wire that heats when connected to the electrical network. We cut the 'leg' detail, 
+              which we attached to the Pen Plotter with the intention of moving the foam around the Hot Wire to cut it. 
+              In the first picture below, you can see my laptop connected to the Pen Plotter, where I checked our generated G-Codes, and 
+              Tetiana was observing the movement of the 'leg' piece</p>
             <div class="image-row2">
               <figure class="image-container">
                 <img class="thumbnail" style="max-width: 750px" src='../assets/images/week16/connecting-part-2.jpg' alt='Connecting parts'>
@@ -58,6 +62,7 @@
                 <figcaption>Checking how the part works by controlling the pen plotter in Universal G-Code sender</figcaption>
               </figure>
             </div>
+
           </li>
           <li> <strong>Modelling of figure for Foam cutting</strong>
             <ul>
@@ -130,13 +135,32 @@
                 <figcaption>At the bottom of the code there is an error message</figcaption>
               </figure>
             </div>
-            <p>I opened the file in Univeral G-Code Sender and it looked great! It has the additional path added to the starting point. And no overlaps. </p>
+            <p>I opened the file in Universal G-Code Sender and it looked great! It has the additional path added to the starting point. And no overlaps. </p>
             <div class="image-row">
               <figure class="image-container">
                 <img class="thumbnail" style="width: 750px" src='../assets/images/week16/generated-gcode-sender.png' alt='G-Code preview'>
                 <figcaption>New Path preview in Universal G-Code Sender</figcaption>
               </figure>
             </div>
+            <p> <h4>Universal G-Code Sender Interface Overview</h4>
+                <ul>
+                  <li>The Code-Source preview window displays the loaded G-Code file for the session. No additional parameters are needed as all instructions are embedded in the G-Code.</li>
+                  <li>The Real-Time values panel, located on the left side, shows live machine coordinates, feed rate, and spindle speed.</li>
+                  <li>The Toolbox window includes two frequently used options:
+                    <ul>
+                      <li><strong>Reset Zero:</strong> Resets the machine's zero point to the current coordinates.</li>
+                      <li><strong>Return To Zero:</strong> Moves the machine back to its original zero coordinates.</li>
+                    </ul>
+                  </li>
+                  <li>The Visualizer window shows the tool’s real-time movement and highlights completed portions of the toolpath.</li>
+                </ul> 
+            </p>
+            <div class="image-row">
+              <figure class="image-container">
+                <img class="thumbnail" style="width: 750px" src='../assets/images/week16/UGSparams.png' alt='G-Code preview'>
+                <figcaption>Universal G-Code Sender Window</figcaption>
+              </figure>
+            </div>
             <p>
               But when trying to cut this figure we noticed that our setup is inverted, so we needed to mirror the image around Y-Axis. On the image below we are trying to
               understand what change should be applied to out G-Code to make the proccess doable by our machine.

src/views/Week8.vue

@@ -54,6 +54,11 @@
                 </li>
                 <li>It is also possible to check the final design in the 3D view.</li>
             </ul>
+            <p>I got some Design Rule Checks errors, as you can see on the screen 2. The error "Input Power pin is not driven by any Output Power pins" - error
+              occurs when a power input pin (e.g., VCC or GND) on a component is not connected to any power output source, such as a voltage regulator, power supply, or battery.
+In my case it was because I had 2 Power Sources on the board, which was a mistake, and the 2nd was not connected to the power pin an caused the error. Also sometimes to fix this error
+you need to use PWR_FLAG symbol in KiCAD to indicate that a net is being powered externally. This symbol helps the Design Rule Check (DRC) understand that the net is intentionally powered and suppresses this warning.
+   The second error "Pin not connected" usually means that pin was not connected. If it's by design, wi should you speceal Not Connectd (NC) symbol to mark such pins.</p>
             <div class="image-row">
               <figure class="image-container">
                 <img class="thumbnail" src='../assets/images/week8/ruleErrorSignOnSchematic.png' alt='No footprint error'>