1. Accessing Flux: Flux is a browser-based electronics CAD program. To begin, simply navigate to the Flux website and log in or sign up if you're a new user.
2. Starting a New Project: Once logged in, you can start a new project by selecting the option to create a new design. This will open a blank workspace where you can start drawing your schematic.
3. Placing Components: You can add components to your schematic by browsing or searching in the component library available within Flux. Drag components from the library onto the canvas and drop them where you would like them to be placed.
4. Making Connections: To connect components, you can draw wires between their terminals. Be mindful of creating a logical and neat layout to make troubleshooting easier.
5. Assigning Values: After placing your components, you can assign them appropriate values (e.g., resistance for a resistor, capacitance for a capacitor) directly on the schematic.
6. Switching to PCB Layout: Once your schematic is complete, you can switch to the PCB layout view. Flux will automatically import the components and connections from your schematic. You then arrange the components on the PCB and route the connections using traces.
7. Checking and Exporting: Use the design rule check (DRC) feature to ensure there are no errors in your design. Once you're satisfied with your design, you can export the Gerber files for manufacturing or share your design with others for collaboration.

• Tutorials: In-depth tutorials about how to use Flux are available to walk you through the more detailed aspects of the platform.
• Reference: Find detailed information about the elements of Flux in the documentation.
• YouTube: Video example projects and tutorials all in Flux can be great visual aids for learning.
• Slack: Join the community of engineers, contractors, and hobbyists using Flux to ask questions and share experiences.

C
#include <16F877A.h> // Change this according to your PIC model
#fuses NOWDT, HS, NOPUT, NOPROTECT 
#use delay(clock=20M) // Set this according to your oscillator frequency

void main(){
    // Set pin RC0 as output
    set_tris_c(0xFE); // Configures all of PORTC as output except RC0
    
    while(TRUE){
        // Turn on the LED
        output_high(PIN_C0);
        delay_ms(1000); // Pause for 1 second
        
        // Turn off the LED
        output_low(PIN_C0);
        delay_ms(1000); // Pause for 1 second
    }
}

• Include Directive: You need to include the correct header file for your particular PIC microcontroller model. For instance, if you're not using a PIC16F877A, you need to change the #include <16F877A.h> line to match your microcontroller.
• Fuses: The #fuses directive sets configuration bits. NOWDT disables the watchdog timer, HS sets the oscillator to High Speed, NOPUT disables power-up timer, and NOPROTECT disables code protection. These might need to be adjusted based on your specific requirements.
• Clock Frequency: Adjust the #use delay(clock=20M) line to reflect the clock frequency of the oscillator you're using. In this example, a 20 MHz crystal oscillator is presumed.
• Pin Configuration: This example uses RC0 (PIN_C0) as the output pin. If you wish to use a different pin, adjust the set_tris_c function and output_high/output_low functions accordingly.
• Infinite Loop: The while(TRUE) loop continuously toggles the LED state, creating the blink effect.

• Diode (D1): This is characterized by specific properties like saturation current $93.2e-12$ A, emission coefficient $3.73$, series resistance $0.42 \Omega$, and a forward voltage of $1.70$ V. These properties suggest it could be used for signal conditioning or protection.
• Tactile Switch (SW1, MPN: B3FS-1050P by OMRON): A standard switch likely used for user input, possibly as a power or mode switch on the hoverboard.
• Resistors (R1 and R2):
  • R1 has a resistance of $10k\Omega$ and is in an SMD_0603 package, which suggests it could be part of a pull-up/down circuit or for current limiting.
  • R2 has a resistance of $220\Omega$ in the same package type, possibly used for LED current limiting or signal conditioning.
• Microcontroller (U1, MPN: PIC16F877A-I/P by Microchip Technology): A critical component likely acting as the control unit for the hoverboard, interpreting sensor data, and managing motor control among other functions. It has numerous I/O pins for versatile connectivity.
• Crystal Oscillator (X1): Specified to operate at $10M$ Hz, providing a clock signal for the microcontroller, ensuring precise timing for operations.
• PowerNet1: An unidentified power source or power distribution point in the design, marked to be excluded from both the Bill of Materials (BOM) and the PCB, indicating it might be a conceptual placeholder or external component.

• Net: 2d204bfa8fcbbe653b6d227d5c83e946: Connects the microcontroller's MCLR/VPP pin to one terminal of R1 and one terminal of SW1, potentially forming a reset circuit.
• Net: c5105ec1daeccb8edaa8211fc71fd0ec: Links the crystal oscillator to the OSC2/CLKO pin on the microcontroller, likely part of the clock circuit.
• Net: 0a7f8a646b8169d95f534c491d0b51a5: Connects PowerNet1 to one terminal of R1, indicating R1's role in a power or signal path.
• Net: c4f8b8e5a1242cb69b3ad367c106e95c: Connects one terminal of R2 to the RB0/INT pin on the microcontroller, possibly used for input or interrupt signaling.
• Net: e55d7e37181bf74eca79e17e7b7e0b4f: Connects the cathode of D1 to one terminal of SW1, likely part of a protection or control circuit.
• Net: a9e5719ab408395765254d451fd791d3: Links the crystal oscillator to the OSC1/CLKI pin on the microcontroller, forming the remainder of the clock circuit.
• Net: 72feef6e675796615ca1faac2e1fc8e4: Connects one terminal of R2 to the anode of D1, suggesting a possible protective or current-limiting function for D1.

1. PIC16F877A-I/P MCLR/VPP:
   • The MCLR/VPP pin is used for Master Clear (Reset) input, which is active low, and also for the programming voltage input. This pin typically requires an external pull-up resistor to ensure that it remains in a logic high state during normal operation to prevent any unintentional resets. It's also recommended for protection against noise or accidental low conditions that may trigger a reset.
   • The datasheet excerpt recommends using a combination of a resistor and a capacitor with the MCLR pin for ensuring a stable startup condition and protection against spurious resets.
   • The project does not list a specific connection to MCLR/VPP other than connecting to R1 through Net 2d204bfa8fcbbe653b6d227d5c83e946, and it does not mention a capacitor directly connected to this pin for forming an RC network, which is a typical configuration for a reset pin to provide noise filtering and debounce functionality.

1. Verify the connection of R1 to U1: (MCLR/VPP). Ensure that R1 ($10k$ ohms) is connected between U1: (MCLR/VPP) and VDD to act as a pull-up resistor. This setup is critical for ensuring that the MCLR/VPP pin is by default in a high state for normal operation. The connection is indicated in Net 2d204bfa8fcbbe653b6d227d5c83e946, but you should confirm the physical routing in the schematic to ensure correct biasing.
2. Consider adding an external capacitor (of recommended value from the datasheet, often in the range of a few nanofarads to microfarads) between U1: (MCLR/VPP) and GND to form an RC network. This capacitor will help in noise suppression and provide a stable reset condition. While the datasheet provides guidelines on the use of an RC network for the MCLR pin, the exact values of resistor and capacitor may depend on your specific application requirements, including the desired debounce time and the noise environment. A typical starting point might be using a $10k\Omega$ resistor (which is already part of your design as R1) and a $0.1\mu F$ capacitor.