Flux Blog

AI at the Click on a Button

The Copilot Context Menu makes harnessing the power of Copilot easier than ever before. By giving users a list of predetermined prompts and actions to choose from, the Context Menu lets you access Copilot with the click of a button. Simply right-click on a component or project, and choose the prompt you want to use.

Some options include:

• Check Decoupling Capacitors: Decoupling capacitors can be confusing. If you’ve ever wondered whether a part needs them, whether you have enough of them, or if your values are correct, Copilot has you covered with a ready-made prompt.
• Explain: Not sure what’s happening in a circuit? Just select the “Explain” prompt and Copilot will give you a detailed explanation of your schematic.
• Recommend Replacement: Worried about your part’s availability? Select this prompt and Copilot will search through thousands of components to find the perfect replacement for your circuit.

Improve Productivity, Remove Bottlenecks

Copilot relies on Large Language Model (LLM) technology, whose quality and accuracy may vary. For this reason, it’s important to think of Copilot as a tool to augment your work, not a replacement for a real engineer. But, now that Copilot is even easier to use, the opportunities are endless.

As a professional, you can catch errors earlier on, save time, and reduce risks in your design. As a student, you can learn faster and get a deeper understanding of your designs. As anyone who loves hardware, you can have more confidence in your design knowing that a powerful AI has your back every step along the way.

Get Started Now!

Copilot keeps getting better, but it would be meaningless without the Flux community. The real power of Copilot lies in what each Flux user will create with it. We can’t wait to see what amazing designs you all come up with. So what are you waiting for? Try out Copilot today!

Story

I live nestled in the heart of an agrarian country. Here, the soil holds tasteful tales of the past and the future of our economy. If you like numbers, here’s a bunch for you, Agriculture contributes approximately 33% of our GDP and employs more than 40% of our total population. You see, my journey into this project wasn’t fueled by a quest for innovation, but if I end up innovating something, I accept that. It was fueled by a need to improve, even just a tiny bit, the current state of affairs. USAID published an article saying that in recent years agricultural productivity has stagnated. Current methods of farming are pretty archaic and if we are to depend on these same methods to boost our productivity, we risk being obsolete as well.

One of the biggest challenges that farmers currently face is the gap that exists between them and the technology that could improve their output. This project aims to eliminate that gap. I have built an IoT sensor node that can be deployed to the farm and collect important parameters for a farmer which can be analyzed and used to maximize productivity. With this aim in mind, I have to solve several challenges including:

• It has to be powered by a battery and be solar rechargeable.
• The sensor nodes must be cost-effective because a number of them will have to be deployed.
• It has to be able to send information to the cloud using LPWAN.
• It can communicate with industry-grade sensors.

To solve these four main problems, I started by drafting a block diagram that provides an overview of the electronics.

Generally, the aim is to have a node that includes a high-performance, low-power, low-cost microcontroller at the heart of the board which can support industry-grade sensors using RS485 protocols, a low-power wide area networking module, a power management circuit that can supply power to both the MCU and any peripherals connected.

In this project, I will be describing how I accomplished that in the Green Dot Board. You can head to the Project and clone or fork it to have edit access.

Step 1: Power Management: Brave board

One of the most important features of the Green Dot Board is power management. As described in the core requirements of the system, is the ability to work autonomously for years without any power concerns. I therefore decided to start by designing a power management circuit and making sure that works fine first to de-risk the whole system.

Most of the sensors that can be hooked onto this system require either 3.3V, 5V, or 12V. I therefore designed the power management circuit to be able to deliver all these powers. You can check out the Brave Power management circuit here. This board can be powered by either LiPo batteries, 4V - 6V solar power panels, or a Micro USB. From these inputs, there is a set of dedicated components to generate and regulate each of the mentioned outputs.

a) 12V and 5V Rail

Starting with the 12V and 5V rail, I used the high-efficiency MT3608L 1.2MHz step-up converter. I used a voltage divider circuit to adjust the output of the component and used an SPDT switch to enable switching between the 12V and 5V output.

• Setting the output voltage can be calculated using the following equation.

Vout = Vref x (1 + R1/R2) where Vref = 0.6V as per the datasheet

• Recommended values for the inductor are 4.7uH - 22uH and the high switching frequency of the regulator enables me to select small components here.
• For the input and output capacitors, 22uF ceramic capacitors have either X5R or X7R type of dielectrics.

b) 3.3V Rail

For the 3.3V rail, I first use an RT8059 converter which is a high-efficiency Pulse Width Modulated (PWM) step-down DC/DC converter, capable of delivering 1A output current over a wide input voltage range from 2.8V to 5.5V. This was very ideal for my case since the LiPo batteries I will be using have a nominal voltage of 3.7V, a maximum of 4.2V when fully charged, and a minimum of about 3.0V when fully discharged.

• You can set the output voltage using a voltage divider circuit using the same equation we’ve seen.
• For the inductor selection, you can use the following equation to get an approximate value for the inductor.

where the ripple current can be approximated as 30% - 40% of the maximum output current

I then used an ultra-low loss power distribution switch with a programmable current limit to protect the power source from overcurrent and short circuit conditions. Current limiting is set by connecting a resistor Rset from ISET Pin to GND. To get the value of the Rset you want, you can use the following equation.

Rset = 6800/Current(A)

c) Charging circuit

For charging the batteries, I used the CN3063 which is a constant-current /constant-voltage linear charger for single-cell Li-ion and Li-Polymer rechargeable batteries. This device is ideally suited for solar-powered applications but it can also work with the USB specifications. It has a regulation voltage preset at 4.2V with 1% accuracy but can also be changed using a resistor. the device accepts input voltages of 4.4V to 6V meaning we would have to use a small solar panel delivering about 5W.

Some interesting features I haven’t mentioned yet of this device include the following.

• Programmable Charge Current: With an external resistor, the continuous charge current can be programmed up to 600mA, providing flexibility in charging requirements.
• Adaptive Charging: The on-chip 8-bit ADC adjusts the charging current based on the output capability of the input power supply, making it suitable for diverse scenarios.
• Status Indication: The open-drain output pin indicates the charger's status, providing visibility into the ongoing charge cycle.

The charge current is set by connecting a resistor Riset from the ISET pin to GND. The ISET pin’s voltage is regulated to 2V during constant charge current mode.

Ich = (Vset / Rset) x 900

I then used two diodes to direct current from both USB and Solar to the charging circuit.

Improvements for a V2 level, so reading the value with an MCU will prove invaluable.

• I also realized that there are scenarios where I would have both a solar panel and a USB connected to the brave board. Although nothing gothic happens to the board, I will have an automatic switch using a MOSFET to disconnect the Solar panel when both the solar panel and the USB are connected to the board.

Step 2: Wireless Connectivity

For wireless connectivity, LoRaWAN was an obvious selection. I won’t go deep into the theory behind LoRaWAN, all I can say now is that LoRaWAN stands as a low-power, wide-area networking protocol, leveraging the LoRa radio modulation technique as its foundation. Its primary function lies in establishing wireless connectivity for devices to the internet. For example, enabling your motion sensor to have a heart-to-heart with your alarm system and notify you when unprecedented motion is recorded.

LoRaWAN boasts several features that position it as an ideal fit for our IoT applications:

• Long Range: As the name suggests, LoRaWAN provides long-range communication, making it a great choice if we are deploying a sensor node at the end of a large farm.
• Low Power Consumption: LoRaWAN operates with a low-power design, allowing our IoT devices to conserve energy and operate on battery power for extended periods.
• Low Data Rates: While not suitable for high-bandwidth applications, LoRaWAN's low data rates are perfect for transmitting small packets of data at regular intervals. This makes it suitable for applications like sensor networks and monitoring systems where periodic updates are sufficient.

I decided to choose the SEEED Studio’s LoRa-E5 module because it has built-in AT command firmware, making it easy to create prototypes or applications with just a few simple commands. However, soldering the module onto the board was probably the most challenging bit of the whole Green Dot development process. The module is small, and I don’t believe I had the right tools to handle that kind of hand soldering. It was only after I got soldering flux, and a better soldering iron tip that I was able to finish the job.

Designing around this module is quite simple. I connect UART and NRST to the host MCU to send AT commands. In addition, I connect Pin24 to a tactile push button because the grounding of the module will force the module to enter Boot upgrade mode. This module works on 3.3V so I also make sure to provide that.

a) Registering our LoRa Module

To register a device to a LoRaWAN platform, you can choose either of two options, Activation By Personalization (ABP) or Over The Air Activation (OTAA). One of the main differences between the two is that ABP offers simplicity and speed, while OTAA provides enhanced security through dynamic key exchange so for our case we will use OTAA to register our device.

When registering a device using OTAA (Over-The-Air Activation) in a LoRaWAN network, you typically need the following information:

• Device EUI (Extended Unique Identifier): A unique identifier for the device. This is often a hardware-specific identifier burned into the device. This can be generated and written to the device but I’m going to just read it directly.

# Generating the Device EUI
import secrets

dev_eui = secrets.token_hex(8).upper()
print("DevEui:", dev_eui)

# Reading it
dev_eui = read_id(b'DevEui')
print("DevEui:", dev_eui)

• Application EUI (AppEUI): A unique identifier for the application. This is required for OTAA and is assigned to the application by the network provider. It serves as a way to associate the device with a specific application. You may obtain it from your LoRaWAN network provider, or you can generate it yourself. It is a 64-bit (8-byte) value.

app_eui = secrets.token_hex(8).upper() # Formerly called JoinEUI
print("AppEUI:", app_eui)

• Application Key (AppKey): A secret key shared between the device and the network server. This key is used during the OTAA process to establish a secure connection. The AppKey is typically kept confidential and should be known only to the device and the network server. It is a 128-bit(16-byte) value. Similarly, you can use a random value as your AppKey.

app_key = secrets.token_hex(16).upper()
print("AppKey:", app_key)

I’ll be using Loriot for this demonstration because that was readily available to me, but the same concepts apply to other similar platforms like The Things Network (TTN). Step 1 would be to enroll a device by providing the generated keys and a name for the device.

The next step would be to make sure those same keys are written to the LoRa module. This can be done as shown below.

from credentials import *
def configure_lora_module():
    set_work_mode("LWOTAA")

    # Set OTAA parameters
    set_id("AppEui", app_eui.encode())
    set_key("APPKEY", app_key.encode())
    set_id("DevEui", DevEui.encode())

    # Join the network using OTAA
    status = join_network()
    return status

Step 3: Selecting a Microcontroller

Choosing the right microcontroller is pivotal for the success of an IoT sensor node. Considering the requirements of low cost, low power, efficiency, and an easy development environment. I decided to go with the Seeed Studio’s XIAO RP2040. This breakout features the RP2040 microcontroller from Raspberry Pi bringing with it high performance, low cost, and ease of use to the microcontroller space.

Some of the features outlined on Seeed Studio’s website include:

• High Performance: Powered by Raspberry Pi 2040 chip, dual-core operating up to 133 MHz, equipped 264KB of SRAM, and 2MB of onboard flash memory.
• Ultra-small Design: 21 x 17.5mm, Seeed Studio XIAO series classic form factor, suitable for wearable devices
• Multiple Development Interfaces: 2x buttons, 11x digital / 4x analog pins, 1x I2C interface, 1x UART port, 1x SPI port, and 1x SWD Bonding pad interface
• Multiple Developing Platforms: Support Arduino / MicroPython / CircuitPython development, friendly for beginners, satisfied for electronics enthusiasts.

This SEEED module has an onboard RGB LED which we will use to visually illustrate the state of the system.

Sensor Interface

When it comes to interacting with sensors, the green dot board can hook up UART, I2C, and RS485 sensors. The connection block also has a set of two pins which can be used as programmable IO pins using the RP2040.

For the RS485, I’m using the SP3485 a +3.3V low-power half-duplex RS485 transceiver with a 10Mbps data rate. The RS485 standard allows for multi-drop (multiple devices on the same bus) and long cabling lengths. In addition, it offers great noise immunity. Some of the sensors that can be connected include the following;

• Soil NPK Sensor
• Industrial Soil pH sensor
• Industrial Soil Moisture & Temperature & EC Sensor

The supporting components around the RS3485 include a bypass capacitor, a pull-up resistor on the RO line, and a termination 120-ohm resistor at the end of the twisted pair A B cables. I used a 120 ohm because the twisted pair cable used in RS485 is defined to have a characteristic impedance of 120 ohms and so by adding a 120-ohm resistor at the end of an RS485 transmission line, the signal will be dampened by the resistor instead of reflected into the bus.

The last bit is to route to my microcontroller.

NOTE: During testing, I realized something that you might have already noticed from this schematic, I had forgotten to connect the ENABLE pins from the SP3485 to my microcontroller. This will be done in my second revision.

Firmware

I wrote a simple MicroPython code to that sends some data to the cloud as proof of concept. The code can be found on my GitHub Profile. I started by writing simple functions to interact with the LoRa module and then used those functions to join the network and send data to the cloud.

# This function sends an AT command to the LoRa module
def send_at_command(command, response_timeout=5000):
    uart.write(command + b'\r\n')
    time.sleep_ms(response_timeout)
    return uart.read().decode('utf-8')

# This function sends hex data and blinks the onboard RGB LED when successfully sent
def send_msghex(hex_data):
    command = b'AT+MSGHEX=' + hex_data
    response = send_at_command(command)
    if "ERROR" not in response:
        blink_rgb_led(PURPLE)
    if "FPENDING" in response:
        print("Downlink Received!")
    print(response)

In the main file, I start by importing the required libraries and defining the firmware parameters.

import time
import machine
from machine import Pin, I2C, deepsleep

import SHT31
from lora_lib import configure_lora_module, send_msghex

# Define firmware parameters
UPLINK_INTERVAL = 60000         # In milliseconds
FIRST_TIME = True

# Configure SHT31 Sensor
i2c = I2C(id=1, scl=Pin(7), sda=Pin(6), freq =400000)
sensor = SHT31.SHT31(i2c, addr=0x44)

I then enter an infinite loop that first checks whether It’s the first time we are running the code, if it is then we join the network, if not we continue with the rest of the code that first reads sensor values and then sends then converts the values into hexadecimal for transmission. After transmission, the system sleeps for the defined uplink interval period.

# Loop after joined network
while True:
    if FIRST_TIME:
        # Configure LoRa Module
        status = configure_lora_module()
        FIRST_TIME = False

    # Read sensor data
    temp_humi = sensor.get_temp_humi()
    humidity = temp_humi[1]
    temperature = temp_humi[0]

    # Convert into hex for transmission
    sensor_data_hex = f'{int(humidity * 100):04x}{int(temperature * 100):04x}'

    # Transmit data
    send_msghex(sensor_data_hex)

    # Sleep for UPLINK INTERVAL (adjust as needed)
    print(f"Temperature: {temperature}")
    print(f"Humidity: {humidity}")
    time.sleep_ms(UPLINK_INTERVAL)

The final setup looks as shown below. I’m looking into getting a 3D-printed enclosure to just keep everything nice and tidy.

Conclusion and final remarks

And there you have it folks, The Green Dot Board. This journey has been a total delight for me from the very beginning and I hope you can say the same thing. You can see below an illustration of how data is being received in the cloud. The next step from here would be to build either a custom dashboard to display all this information or to use a platform like Datacake which would integrate seamlessly with Loriot or TTN to do the data visualization.

I will be implementing some of the issues that arose along the way and updating the design in flux. You should be getting prompts of new updates as I do then and either choose to receive or deny them. Accepting updates is as simple as clicking the accept button.

Why Flux for PCB Design?

Flux stands out in the PCB design industry, adhering to three core principles: promoting reusability, fostering collaboration, and keeping the designer focused. The emphasis on reusability allows individuals and organizations to amplify their impact. Users can leverage the work of others in the community by using templates, modules, or example projects, saving time and resources. This approach to PCB design not only streamlines the development process but also fosters a collaborative environment where designers can share and build upon each other's work, leading to more innovative and efficient designs. By keeping these principles at the forefront, Flux ensures that designers remain focused on what's most important, allowing them to deliver high-quality, effective PCB solutions for complex industrial sensing applications.

Reference Designs Highlights

Our PCB design projects, showcased below, are not just innovative solutions but also serve as reusable modules in Flux. Each module is carefully crafted to ensure it can be easily adapted and used by anyone in the community. These modules exemplify the principle of reusability, allowing other designers to leverage our work for their own applications, fostering a collaborative and efficient approach to PCB design.

1. Advanced Light Sensing: TSL25911FN

We developed a high-precision light intensity measurement system using the TSL25911FN. Flux Copilot played a crucial role in optimizing the layout for minimal interference and maximum sensitivity, ensuring accurate light measurement critical in quality control systems within manufacturing processes.

2. Robust Data Communication: PCA9615

The PCA9615 was the cornerstone of our design for reliable long-distance I²C communication in noisy industrial environments. By leveraging Flux, we successfully mitigated EMI effects, making this design essential for large-scale industrial automation networks.

3. Thermal Imaging Breakthrough: MLX90640ESF-BAA-000-TU

Utilizing the MLX90640ESF-BAA-000-TU, we crafted a sophisticated thermal imaging sensor. Flux was instrumental in the design, allowing for intricate circuitry that handles the high data throughput and thermal management required for accurate imaging. This sensor has become a game-changer in industrial safety and process monitoring, providing critical thermal data in real-time.

4. Precision Pressure Control: PGA300ARHHR

The PGA300ARHHR was the key component in our design of a high-precision pressure sensor system. This sensor is now widely used in fluid dynamics control in various industrial applications, demonstrating its versatility and reliability.

5. Distance Measurement Innovation: VL53L0CXV0DH

Our design using the VL53L0CXV0DH revolutionized short-range distance measurement in industrial settings. The layout and routing capabilities in Flux allowed us to maximize the sensor's range and accuracy, making it ideal for applications like inventory management and automated guided vehicles.

6. Multi-Range Sensing Solution: VL6180X

Incorporating the VL6180X, we developed a versatile multi-range sensor, adept at handling both proximity and ambient light measurement. Thanks to Flux's precision in PCB layout, we achieved a compact design that is now crucial in space-constrained industrial environments, particularly in robotics and assembly lines.

7. Advanced Long-Range Sensing: VL53L1X

The VL53L1X enabled us to push the boundaries of long-range sensing. This sensor offers exceptional range and accuracy, which is now integral in large-scale automation and monitoring systems.

8. Cutting-Edge Imaging Sensor: VL53L4CD

Our VL53L4CD-based design marked a significant advancement in high-resolution imaging sensors. Leveraging Flux's capabilities, we engineered a PCB that supports complex data processing, essential for applications like precision mapping and 3D modeling in industrial scenarios.

9. Time-of-Flight Sensing Mastery: TMF8801-1BM

The TMF8801-1BM was central to our innovative time-of-flight sensor design. With Flux, we've enabled us to layout the board more efficiently, resulting in a sensor that excels in real-time positioning and collision avoidance in automated systems.

10. Enhanced Object Detection: TMF8820-1AM

Using the TMF8820-1AM, we designed a sensor specifically for efficient object detection. The measurement tool in Flux allowed us to create a design that provides high-accuracy detection, making it ideal for safety and surveillance applications in industrial environments.

11. Color Sensing Precision: TCS3200D-TR

Our TCS3200D-TR-based design focused on high-fidelity color detection. We achieved a design that offers remarkable color sensing discrimination, essential in quality control processes in industries like textiles and printing.

12. Advanced Light Sensing: ISL29125IROZ-T7

The ISL29125IROZ-T7 allowed us to develop a high-performance light sensor. This sensor is used extensively in ambient light measurement and color balancing in industrial displays.

13. Laser Measurement Expertise: AFBR-S50LV85D

In our design with the AFBR-S50LV85D, we specialized in long-range laser measurement. This sensor isideal for applications requiring precise distance measurements, such as in warehouse logistics.

14. Advanced CMOS Sensor Design: AR0144CS

The AR0144CS was the foundation for our high-resolution CMOS sensor. Using Flux, we developed a PCB that supports complex image processing algorithms, crucial for detailed visual inspections in automated manufacturing processes.

15. Proximity Sensing Redefined: VCNL3040

Our design using the VCNL3040 redefined proximity sensing in industrial environments. With Flux, we crafted a compact and efficient layout, resulting in a sensor widely used in machinery safety and user interface applications.

16. UV Sensing Innovation: LTR-390UV-01

The LTR-390UV-01 led to our breakthrough in UV light sensing. Thanks to Flux's layout design tool, we created a sensor that accurately measures UV light intensity, crucial for monitoring and controlling industrial processes involving UV curing and sterilization.

17. Reflective Sensing Solution: QRE1113

Using the QRE1113, we developed a reflective sensor adept at detecting object presence and positioning. This sensor offers high sensitivity and reliability, essential in applications like conveyor belt control and product sorting in manufacturing lines.

18. Compact Distance Measurement: GP2Y0D805Z0F

Our design with the GP2Y0D805Z0F focused on compact distance measurement solutions. Thanks to Flux, we were able to create a tiny yet highly effective sensor used in applications where space is at a premium, such as in handheld devices and robotics.

Overcoming Challenges

The design journey for each of these modules presented unique challenges, underscoring the versatility and adaptability required in the field of PCB design, particularly when using Flux.

• ‍Thermal Management in MLX90640ESF-BAA-000-TU: Designing with the MLX90640ESF-BAA-000-TU, a thermal imaging sensor, required meticulous attention to thermal management. We had to ensure that the heat generated by the sensor did not affect its performance, which was critical for applications in safety and process monitoring.‍
• Signal Integrity with PCA9615: For the PCA9615, ensuring signal integrity over long I²C communication lines in noisy industrial environments was a significant challenge. We focused on designing a robust layout that could resist electromagnetic interference, essential for reliable data communication in automation networks.‍
• Size Constraints with VL53L0X: Incorporating the VL53L0X into a compact sensor module for distance measurement involved overcoming size constraints. The challenge was to maintain the sensor’s range and accuracy in a significantly reduced footprint, making it suitable for space-constrained applications like inventory management.‍
• Power Optimization for VCNL3040: Designing with the VCNL3040, a proximity sensor, posed challenges in power optimization. We had to ensure that the sensor operated efficiently to extend the battery life of the devices it was integrated into, which was crucial for its use in safety and user interface applications.‍
• Light Interference with ISL29125IROZ-T7: The ISL29125IROZ-T7, a light sensor, required us to devise ways to manage light interference effectively. This was crucial for its application in ambient light measurement and color balancing in industrial displays, where accuracy is paramount.

These challenges and others like them were addressed through innovative design approaches, leveraging Flux’s capabilities in layout design and component integration. By overcoming these hurdles, we were able to create modules that are not only effective in their specific applications but also versatile enough to be adapted for a wide range of uses in the industrial sector.

The Future of Industrial Sensing

The future of industrial sensing is marked by rapid technological advancements and a shift towards smarter, more efficient systems. Integration of IoT and AI technologies is transforming sensors into intelligent devices capable of real-time data analysis and decision-making. Miniaturization remains a key trend, with sensors getting smaller yet more powerful, catering to space and energy-efficient needs in diverse industrial applications.

Emerging materials and manufacturing techniques promise to enhance sensor sensitivity and durability, crucial for extreme industrial environments. Customization and flexibility in sensor design are increasingly important, enabling quick adaptation to specific industrial needs. This is where tools like Flux, promoting reusability and collaboration, become vital.

Additionally, environmental sustainability and data security are becoming critical considerations in sensor development and deployment. As sensors become more interconnected, ensuring secure and reliable data transmission is paramount.

In conclusion, the industrial sensing landscape is evolving towards more adaptable, intelligent, and sustainable solutions, with immense potential for innovation and impact in various industrial sectors.

Engage with Us

We'd love to hear about your experiences with industrial sensor designs or any inquiries you might have. If you're looking for expert advice or services in PCB design, feel free to contact us or join our Slack channel and share with our community of 2,000 and growing. Together, we’ll change the future of PCB design!

Keep Innovating!

It’s tempting to think that LLMs are able to read our minds, but in practice, that’s far from the truth. While Copilot is surprisingly good at filling in the blanks when you ask it a question, to get the best results, you need to ask the best questions. Imagine you’re onboarding a coworker. The more detail and context you provide the new employee, the faster they’ll get up to speed and the more productive they’ll become.

We want to make this process as easy as possible for all Flux users. So, after hundreds of hours of testing and talking to dozens of real users, we’ve put together six prompting tips that will help you get the most out of Copilot. Read on to learn more!

Give Copilot Context 

When it comes to LLMs, what you put in is what you get out. So if you want clear and detailed answers, you need to make sure that you provide Copilot with descriptive prompts. When you let Copilot know your goals, constraints, or more details about what you want to build - it can give better answers.

Here’s an example of a “bad” and “good” version of the same prompt:

Bad:
@copilot what’s the best IMU for this project?

Good:‍

@copilot can you recommend a suitable IMU for this project? I want to keep overall board power consumption below 1A. This is an automotive design, so all components must also be ASIL-D certified. I’m also on a budget, so the total BOM must be less than $2.00.

The best way to give Copilot context is to use Copilot Presets. A powerful new feature that allows you to declare project requirements like operating temperature, voltage, or compliance standards. They are the go-to way to help Copilot understand the full context of your project. 

Be Specific

A good prompt is also specific. Don’t just ask Copilot for help finding a component; tell it what factors it should consider so that it knows your criteria. 

‍Bad:
@copilot review my decoupling capacitors

Good: 

@copilot list all ICs and the decoupling capacitors attached to each. Ensure to include all ICs present in the design, including digital ICs, power converters, LDOs, etc. For every IC, clearly state:
• What power net the decoupling capacitors are attached to. What is the stated voltage of that net?
• The voltage rating and value of the attached decoupling capacitors.

Another tip here is to mention components explicitly by their component designator so that Copilot knows exactly which components you’re referring to. For example,

‍Bad:
@copilot what is the operating voltage of my microcontroller?

Good:

@copilot what is the operating voltage of U1 in my project?‍

Ask for a Desired Format Output

Copilot is a text-based assistant, but that doesn’t limit what kind of responses it can give you. Users can prompt Copilot to respond in a variety of different ways, including tables, LaTeX, code blocks, and markdown formatting. 

Also, many users might not know that Copilot can even output files for you—if you know how to ask! For example, you can ask Copilot to produce a CSV of your project BOM for you with a prompt like the following:

‍@copilot can you generate a BOM for this project in a CSV format?

With unique output formatting, Copilot’s responses can more easily integrate into your workflow.

Be Technically Accurate

First off, a good prompt is one that is technically accurate. If your question doesn’t make sense, then the response is likely to be inaccurate as well. 

Here’s an example of a technically “bad” and “good” version of the same prompt:

‍Bad:
@copilot how do I choose the right material for a PCB?

‍Good:

@copilot what are the key considerations when choosing the right dielectric and stackup for a PCB?

Fortunately, you can also use Copilot’s assistance to gauge whether or not your question is technically accurate, and it’ll help you formulate better questions. To get to the good prompt above, you could ask Copilot 

@copilot what are PCBs made out of? What are the materials called and why do they vary?

Use Copilot Shortcuts

If you’re still not getting the results you want out of Copilot, we have you covered. We provide users with premade Copilot Shortcuts that are accessible through the Copilot Context Menu. Simply right-click on a component or project and choose the prompt you want to use, knowing that it was engineered for the best results possible.

Some options include:

• Checking Decoupling Capacitors: Decoupling capacitors can be confusing. If you’ve ever wondered whether a part needs them, whether you have enough of them, or if your values are correct, Copilot has you covered with a ready-made prompt.
• Explain: Not sure what’s happening in a circuit? Just select the “Explain” prompt, and Copilot will give you a detailed explanation of your schematic.
• Recommend Replacement: Worried about your part’s availability? Select this prompt, and Copilot will search through thousands of components to find the perfect replacement for your circuit.

Use The Right Copilot Expert

We recently launched a feature called Copilot Experts, which provides you with a set of specialized AI models, each tailored for distinct aspects of hardware design. You can choose which AI model you want to access based on the task at hand, allowing for a more specialized experience that’s tailored to your needs. Right now, our three Expert models are

‍• Generalist: This is the default Copilot model that you know and love. He’s a jack of all trades who retains the versatility to do anything you need. Try this prompt:

@copilot how does a CAN transceiver work?

• Librarian: This model excels in parts inquiries and navigates datasheets with ease. The next time you have a question about a part, Librarian has got you covered! For example,‍

@copilot How do I use U1 as a CAN transceiver?

• Help: This is your go-to for Flux product guidance. Have questions about how to use the tool? Don’t feel like sifting through the documentation? Just ask the Help Expert for the answers. You can ask questions like‍

@copilot How do I connect U1's ground pins to ground?

For the best results with Copilot, make sure you’re working with the right Expert for the job!

YOU Can Make Copilot Even Better!

Flux is driven by our community, and that means you have a unique opportunity to help make Copilot even better. We’d love for you to participate in pushing the limits of Copilot and share your findings with the community on what works well. If you discover a prompt that’s really impactful, let us know so that we can share it with everyone!

The best way to get involved is to join our Slack channel and share with our community of 2,000 and growing. Together, we’ll change the future of PCB design!

The Inspiration Behind PCB Plant Wallpapers

I’ve been thinking a lot about what Steve Jobs did. With the products he created at Apple, he found a way to merge engineering with the humanities. In doing so, he enabled more people to experience and connect with technology. Wow, I thought, This kind of thinking is powerful but overlooked for PCB and electronics design. There is an artistic side that's often overlooked. I wanted to capture the feeling of creation, of invention, in these wallpapers. The goal is to kindle the spark of inspiration and also celebrate the creativity and ingenuity that engineers bring to their work every day.

Design Details and Features

E‍ach wallpaper was designed with Midjourney. Many iterations of prompt tuning and post processing were required to produce a series that felt right. I wanted to strike a balance between the artificial and natural. And I wanted to inspire with a sense of fantasy while still keeping one foot in the possible. The result is four wallpapers which evoke futurism with the classic forms of the natural world. Brilliant color and glowing light evoke optimism while a shallow depth of field and the dark background evokes an intimacy. These products - or are they organisms - are shot in a reserved style of a professionally photographed object.

Why These Wallpapers Resonate with Engineers

‍For engineers, I hope these wallpapers will be more than just a background for their screens; they'll be a source of daily inspiration. The fusion of a PCB’s precision with the organic form of plants reflects the innovative spirit of engineering. It's a daily reminder of how engineering not only solves practical problems but also creates beauty and harmony.

How to Get These Wallpapers

Ready to bring this unique blend of technology and nature to your workspace? We're excited to share that these exclusive wallpapers come in stunning 4K resolution, ensuring that every detail of the intricate PCB designs is beautifully rendered. And the best part? They are available for both desktop and mobile phones, directly downloadable from this blog post!

‍In a world where technology often distances us from nature, these wallpapers serve as a beautiful reminder of how the two can coexist harmoniously. They’re more than just decoration; they're a statement of the beauty in engineering and an ode to the creativity that engineers bring to our world.

Wallpapers for iPhone:

• Flex Flower Wallpaper
  Download
• Integrated Circuitry Wallpaper
  Download
• Photo Synthesizer Wallpaper
  Download
• Tropical Phase Array Wallpaper
  Download

Share the PCB Plant Magic with Your Network

If these unique PCB plant wallpapers have sparked your interest, share this post with your fellow engineers and designers. Let's spread the word about this innovative blend of technology and nature! And if you have ideas for future designs, we’d love to hear them on our Slack Community.

That's where Flux for Organizations comes in, and we're thrilled to make it free for public and educational organizations. At Flux, we are deeply committed to the belief that open-source hardware will be the vanguard of global innovation. We're here to make it easier for teams worldwide to collaborate and build the future.

Centralized Resource Hub

Navigating through fragmented resources for reliable component libraries or design rules can be both time-consuming and frustrating. Flux offers a centralized resource hub that brings everything you need right to your fingertips. Component libraries, AI-driven design suggestions via Copilot—you name it, we’ve got it.

Collaboration That Just Works

Forget the days of email chains filled with zip files that make version control a living nightmare. Flux's built-in version control, Copilot Presets, and Project Templates are designed to make every design iteration transparent, accessible, and most importantly, collaborative. Learn more

Community Showcases

The challenge of recruiting incredible talent for open-source projects is real. That's why your organization’s Flux profile does more than just list who's on your team. Use it to highlight community contributions, showcase public projects, and even spotlight the heroes who make your community vibrant. See example

Manage Project Costs with Ease

Hardware components come with real costs, which can become prohibitive especially for community-driven projects. With Flux's real-time pricing and availability features, automated email updates on component pricing, and total project cost visibility, you’ll never be in the dark. Learn more

AI Superpowers

While large hardware firms have resources that smaller, community-driven projects can only dream of, Flux levels the playing field. Our AI assistant, Copilot, brings enterprise-level capabilities right to your desktop, allowing you to compete on a much broader scale. Learn more about Flux Copilot

Free for Public and EDU Organizations

Whether you're an open-source hardware group, a manufacturer like Aisler sharing stackup templates, or a university showcasing academic projects, we support your collaborative efforts. For those in need of more privacy and customization like Weyland Yutani Megacorp, our paid organizational accounts start at just $49 per editor. Learn more about private organizations

Get Started Today

1. Log in or sign up for Flux.
2. Navigate to your profile menu.
3. Select "organizations", then "create new organization"
4. Input your details, and you're good to go.

We’re not just offering a tool; we're building a home where the open-source hardware community can truly flourish. Join us in this exciting journey toward a more collaborative and innovative future.