https://community.element14.com/The community for engineers, technicians, makers and creators.en-USTelligent Community 12https://community.element14.com/learn/events/c/e/1757Thu, 04 Jun 2026 15:00:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:529a9eaa-7e14-484f-81eb-8bffc6ab37edJoRatcliffeJoin this webinar to examine how DC coupled, high speed Digitizers operate and discover the technical challenges that emerge as bandwidths extend beyond 1 GHz. We will take a focused look at the limitations inherent in conventional high-speed Digitizer front ends, including linearity, noise performance, dynamic range, and system level coupling issues. There will be a live demonstration of a new Analog Devices evaluation kit engineered to directly address these challenges, supported by detailed performance parameters and measurement data that demonstrate what next generation Digitizer designs look like. In less than an hour, this session will cover: A primer on the principles of DC-Coupled, high-speed Analog-to-Digital Converters The applications (and challenges!) associated with high-speed Digitizers and how they are solved with ADI’s New ADMX6001 Digitizer The different approaches to resolving/mitigating these challenges Live demo of a high-speed Digitizer and how challenges can be addressed, using an ADMX6001 eval kit Live Q&A The Presenters: Will Drachler - Principal Marketing Engineer - Analog Devices Will is a Principal Marketing Engineer in the Instrumentation System Solutions group. He has more than 40 years of experience at Analog Devices spanning linear solutions, optical systems, and the digitization of high‑speed signals. Will holds a BSEE from the Rochester Institute of Technology. LinkedIn: Will Drachler Malcolm Sherman-Godfrey - Senior Engineer, Systems Design/Architecture - Analog Devices Malcolm is a systems design engineer in ADI's Instrumentation System Solutions group, experienced in architecting RF and precision elements of high-speed digitizers and vector network analyzers. He has a BSEE from the Rochester Institute of Technology and has been with ADI since completing an MSEE at the Georgia Institute of Technology. LinkedIn: Malcolm Sherman-Godfrey Jordan Ratcliffe - Marketing Program Senior Specialist - element14 Community Jordan Ratcliffe will be your host from the element14 Community for Introductions and Q&A. LinkedIn: Jordan Ratcliffe More about Analog Devices: Every day, electronic devices are becoming smarter with greater integration. Body sensors can monitor our health. Cars can drive themselves. Networked homes can power up when needed. At Analog Devices, we’re solving engineering problems and empowering design innovation, enabling our customers to create products that shape our world. We invent highly integrated solutions that make technology seamless. Our innovative and high-performance analog and mixed-signal products and technologies make systems smaller and smarter, with enhanced security and increased energy efficiency. We channel our collective expertise to stretch the limits of technology, understand your needs, and help you get to market faster. You can find out more about Analog Devices here . Attend and Learn to Earn a Certificate Watch the webinar until the end to earn a certificate. Read here for more information about how to get your certificate: /members-area/support/w/site-faq/27798/how-do-i-earn-a-certificate-for-viewing-a-webinar-or-webcast Are you prepared? This webinar uses the online service on24 to deliver the presentation. Click through and check that you meet the minimum system requirements before attending.linearityanalog-to-digital converterADI-e14DC coupled high speed digitizerADMX6001analog devicesdigitizersystem level coupling1ghznoise performancedynamic rangehttps://community.element14.com/learn/events/c/e/1752Tue, 28 Apr 2026 14:00:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:cc6fea7e-ea3c-4c38-8c7e-21a6f8dcd4ccJoRatcliffeThis webinar has been rescheduled to Tuesday 28th April (2pm Coordinated Universal Time) Discover how to unlock the full potential of Data Acquisition (DAQ) using a no-code approach, demonstrated in this webinar with a live demo of a motor and fan test combined with LabVIEW and NI software tools. Whether you’re validating new designs or looking to improve your workflow, this session is designed to give attendees the knowledge to build robust, repeatable tests using simple configuration tools. This webinar will show you how to quickly set up reliability tests, automate start stop cycles, measure motor efficiency, and evaluate fan airflow, without writing any code. Join us for an expert-led session covering: An overview of no-code testing with DAQ DAQ testing essentials A live demo: Building a fan and motor test without coding Stay until the end for a live Q&A session where you can have all your questions on data acquisition, no-code, LabVIEW and more, answered by the session's expert host: Jelmer van den Dries, Principal Field Application Engineer at Emerson. The Presenters: Jelmer van den Dries - Principal Field Application Engineer - Emerson Jelmer brings 8 years of experience from working at Emerson, working exclusively in their Test and Measurement business unit. He has extensive experience working with leading automotive OEMs and Tier 1s in the UK and Europe, designing, and building out data acquisition systems and test solutions. He is a specialist in real-time test solutions such as SIL and HIL systems. LinkedIn: Jelmer van den Dries Jordan Ratcliffe - Marketing Program Senior Specialist - element14 Community Jordan Ratcliffe will be your host from the element14 Community for Introductions and Q&A. LinkedIn: Jordan Ratcliffe More about Emerson: Emerson delivers future-ready test and measurement solutions through the power of the NI platform—a combination of high-performance open software, modular hardware, and AI-driven capabilities that enhance productivity. Flexible and scalable, the NI platform transforms how engineers automate measurement, control, and testing of complex products that move our world forward. For more information, visit Emerson.com . Attend and Learn to Earn a Certificate Watch the webinar until the end to earn a certificate. Read here for more information about how to get your certificate: /members-area/support/w/site-faq/27798/how-do-i-earn-a-certificate-for-viewing-a-webinar-or-webcast Are you prepared? This webinar uses the online service on24 to deliver the presentation. Click through and check that you meet the minimum system requirements before attending.testingnino-codedata acquisitionemersondaqno codelabviewhttps://community.element14.com/learn/events/c/e/1752Sun, 26 Apr 2026 13:00:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:1d301911-e50b-4b31-8e05-9dc34ead3eb1m.arguelloDiscover how to unlock the full potential of Data Acquisition (DAQ) using a no-code approach, demonstrated in this webinar using a motor and fan test combined with LabVIEW and NI software tools. Whether you’re validating new designs or looking to improve your workflow, this session is designed to give attendees the knowledge to build robust, repeatable tests using simple configuration tools. This webinar will show you how to quickly set up reliability tests, automate start stop cycles, measure motor efficiency, and evaluate fan airflow, without writing any code. Join us for an expert-led session covering: An overview of no-code testing with DAQ DAQ testing essentials A live demo: Building a fan and motor test without coding Stay until the end for a live Q&A session where you can have all your questions on data acquisition, no-code, LabVIEW and more, answered by the session's expert host: Jelmer van den Dries, Principal Field Application Engineer at Emerson.nino-codedata acquisitionemersondaqno codelabviewhttps://community.element14.com/learn/events/b/blog/posts/we-are-at-hackaday-europe---16th---17th-may-2026-in-lecco-italyTue, 14 Apr 2026 10:07:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:a2a67302-4c2c-43e4-ad5d-b5f63035913ce14philWe are excited to say we will be sponsoring and attending: Hackaday Europe 16th - 17th May 2026 Lecco, Italy Who is attending from element14 Community and element14 presents : Phil Hutchinson e14phil (Head of e14 Presents) Clem Mayer mayermakes (e14 Presents Host) Lorraine Underwood lorrainbow (e14 Presents Host) Milos Rasic milosrasic98 (e14 Presents Host) Pat Deegan psychogenic (e14 Presents Host) element14 Community will be there! element14 Community and the element14 presents team will be in attendance! Come say hello, you will also get an exclusive achievement for attending this event. Show us your projects, learn about our activities and get some swag! Event: Join us for Hackaday Europe 2026! A weekend of hardware talks, badge-hacking, and celebrations! We're back! We are thrilled to announce the return of Hackaday Europe, a hardware conference on Saturday, May 16th in Lecco, Italy, just outside of Milan. Plus extra festivities on the 15th and 17th! Join us to experience talks and workshops exploring the most unique, cutting-edge, and world-changing topics around hardware creation. You'll hear talks, see demos, and take workshops on topics ranging from learning new tools or techniques to fabrication adventures, from code-wrangling that firmware project to your giant LED design project, and everything in between. The demos, badge hacking, food and drink, DJ sets, and a warm and welcoming village of great people make this an event you don't want to miss. This will sell out, get your ticket now! Lightning Talks: We will have two sessions for 7-minute lightning talks. To participate fill out the form here: https://forms.gle/TLuBC36wofbXXYCP8 Workshops: When workshop tickets sell out, attendees can join the waitlist by emailing their name, conference ticket number, and workshop choice to prize@hackaday.com. You must be a conference ticket holder to participate in a workshop. Conference Events: This is the seventh Hackaday Europe. We hosted the first Hackaday Belgrade in 2016 to an enthusiastic, sold-out hall and the second in 2018. In 2023, 2024, and 2025 we brought the event back to Berlin again to a sold-out audience and we are very excited to bring this event to an all new location! Here's what we have in the works: Talks and Workshops will cover hardware, engineering, creativity in technical design, product design, prototyping, etc. from 10AM to 9PM. Badge Hacking goes all day and will be extended into the wee hours of the morning. Every attendee of Hackaday Europe will receive one of these amazing custom electronic badges. The badge demo presentations will take place at 11 pm. There's More: We're keeping the costs low to offset your travel costs. The cost of admission includes the cost of the badge, excellent food and drinks during the conference, and a Hackaday party late into the night on Saturday. Keep an eye out for more details on Friday night's pre-party! We can't wait to see you all there! LOCATION: Politecnico di Milano Lecco Campus, Via Gaetano Previati, 1/c, 23900 Lecco (LC), Italy Tickets: https://www.eventbrite.com/e/hackaday-europe-2026-tickets-1985449808825#location Hackaday https://hackaday.com/tag/hackaday-europe/makerhackadayhackaday eueventsconferencearduinoitalyhttps://community.element14.com/challenges-projects/design-challenges/smart-security-and-surveillance/f/forum/56830/identity-protocol---part-2---django-server/234976Tue, 14 Apr 2026 04:00:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:2c54537b-9c6d-4a5a-b238-0c56155fd48earvindsasaramic I just saw the selected challenger. I'm sorry that your ideas were not selected, but id like to hear out your ideas if it's okay for you to share it.https://community.element14.com/technologies/test-and-measurement/b/blog/posts/spice-circuit-simulation-a-simple-explanationTue, 14 Apr 2026 02:23:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:7328923d-6cc9-4c05-ad7a-2907e1d272d3shabazTable of Contents Introduction I Want to Try It, Now! SPICE Quick Overview Elementary Models Pin Ordering for Component Symbols An Entire Circuit Choosing and Running Simulations DC Voltages and Currents (Operating Point) Simulations Time-Domain (TRAN) Simulations Frequency Response Simulations (AC) Summary Further Information Introduction Circuit simulation is powerful, and can be very accurate, depending on the how closely the circuit has been modelled to the actual circuit. It can save a lot of time to simulate, before constructing for real. There are different kinds of circuit simulation engines, and different types of simulations to want to run, and some are more appropriate for particular niches in electronics engineering. The engine discussed in this blog post is called SPICE , and it is broadly used in electronics. SPICE dates back to the 1970’s, although the version used today was developed in the late 1980’s. Despite its ancientness, it is used professionally for simulating circuits containing passive components, discrete semiconductors as well as various integrated circuits, and the breadth of typical circuits can include (but is not limited to) amplifiers, filters, power supplies, oscillators and so on. SPICE is even used to an extent, to simulate custom integrated circuit designs (or at least subcircuits). This blog post explores some of the popular capabilities of SPICE, and how it can be employed with CAD schematic entry software. I use example screenshots from KiCad, but this blog post is not KiCad specific; the concepts described work with other software too, such as LTspice. I Want to Try It, Now! If you want to explore for yourself, it’s very easy, a five-step process. Here are the steps, using an example project by michaelkellett which is an audio preamplifier. Please note this won’t teach how to use KiCad (that requires some self-training, for instance using this 50-minute video: Creating Circuit Boards with KiCad ), nor will it cover all aspects of SPICE, but will show how to run a simulation and explain how SPICE works, so that the benefits of SPICE can be explored further by those interested. 1. Download and install KiCad 10 2. Download the discrete_preamps project zip file and extract it to anywhere on your PC 3. Run KiCad, open the extracted preamp_k2 project, and open up the schematic 4. Click on Inspect->Simulator 5. You’ll see several simulation tabs. Click to select any of them, then click on the triangle RUN icon! SPICE Quick Overview There’s a simulation engine for electronics called SPICE, which traditionally ran on mainframes. It relies on internal models for various basic components such as resistors, capacitors and transistors, and accepts parameters as inputs to tweak the models for each component. Then, an entire circuit can be described as a collection of models and their wiring to each pin in the model. Finally, the desired type of simulation can be chosen, and SPICE will run it, and spit out a dataset, which can be charted. Desktop CAD software can incorporate the SPICE engine, but in the background, the transfer of information between the CAD software and the SPICE engine is based on text-based files. That’s because SPICE follows the traditional batch-processing paradigm that was popular with mainframes. A user would prepare a set of instructions, send them to the computer, and then come back later to see the generated results. Today, the user would sketch a circuit graphically, but in the background KiCad (or any other software that uses SPICE) will prepare text files describing the components and circuit, and call the SPICE engine passing the text file names on the command line, and in return, SPICE will generate a file of results. The CAD software will then chart the results graphically from the results file. As far as the user is concerned, they need never know that text data was exchanged to make the simulation occur. Elementary Models As mentioned, SPICE’s internal models (such as an NPN transistor model) rely on parameters to tweak the model to represent specific components, such as a BC549 NPN transistor. For instance, for an NPN or PNP transistor, one of the parameters would be the voltage across the base-to-emitter when current is flowing into the base. The transistor datasheet would be consulted to determine that voltage (it may be say 0.7V) and then the model would be configured by the following parameter setting: VJE = 0.7 This would take ages since there can be a lot of parameters for a component model, so instead, one would download the manufacturer-supplied model file, which can have various suffixes, but .lib is common. A BC549 transistor would have a SPICE model file called BC549.lib and it would contain a list of the parameters, all ready for simulating that transistor. In the example snippet below, the top part contains comment lines, followed by the model name BC549/550 and the NPN model type instruction to SPICE that indicates which model type to apply (for instance, for say N-channel mosfets, the model type field would need to be set to NMOS ). After that, all the parameter settings for that model type follow. * BC549/550 NPN EPITAXIAL SILICON TRANSISTOR ELECTRICAL PARAMETERS *-------------------------------------------------------------------- * Switching and Amplifier * Vcbo & Vceo: BC549(Vcbo:30V / Vceo:30V) * BC550(Vcbo:50V / Vceo:45V) *-------------------------------------------------------------------- * MODEL PARAMETERS FROM MEASURED DATA: BC549 *-------------------------------------------------------------------- .MODEL BC549/550 NPN + LEVEL = 1 + IS = 2.24183E-14 + NF = 0.996496 + ISE = 1.90217E-14 + NE = 2 + BF = 228.4 The above is known as an elementary model. Pin Ordering for Component Symbols The model described above needs to somehow be mapped onto a graphical symbol, and some way of assigning pins is required. For instance, the NPN circuit symbol may have pins called B, C, E, or one may choose to call the pins BASE, COLLECTOR, EMITTER. SPICE works with any desired pin naming, it just use the order to determine which is which; internal to SPICE, each elementary model has a specific hard-coded pin order, and for NPN transistors the order happens to be collector, base, emitter. You wouldn’t know that order without delving into SPICE documentation, but ordinarily one doesn’t need to know this to use SPICE. The model so far only tells SPICE how to model the transistor, but it doesn’t tell SPICE what pins go where. That needs to be further input into SPICE, and that input can be self-generated by KiCad or whatever desktop software the user is using with SPICE. So, when a NPN symbol is created and drawn up in a symbol editor tool, there will be a drop-down menu that will either allow the user to assign each pin name to a order (i.e. if you name the collector pin “C”, then you would need to assign “C” to “1” since SPICE expects the collector pin to be listed first), or the symbol editor tool will have been pre-programmed with the expected order for each model type, and will allow the user to assign the “C” pin to “Collector” in the drop-down menu. The screenshot below shows a user assigning a pin called “E” to the BC549 model. An Entire Circuit Whenever a circuit contains a BC549 transistor, KiCad will automatically provide SPICE with an explanation of that, with a line such as: Q1 Net-_Q1-C_ Net-_Q1-B_ Net-_Q1-E_ BC549/550 The above line indicates that the user’s circuit contains a BC549 transistor that the user has labeled as Q1 . The fields beginning with Net- just happen to be names that KiCad decided to give to each wire drawn in the circuit, and the wire name connected to the BC549 collector has to be listed first, because the SPICE internal NPN model requires that to come first as mentioned earlier. Sometimes a user will create their own signal (i.e. net) names in the schematic, for instance the wire connected to the BC549 base may be named INPUT , and in that case, KiCad will choose to use the user-provided net name: Q1 Net-_Q1-C_ /INPUT Net-_Q1-E_ BC549/550 In summary, KiCad will provide SPICE with a list of all the components and their connections, and the model names, as shown in the example line above. It’s sometimes called a netlist . The netlist snippet below would correspond to a circuit containing a capacitor, two transistors, and a resistor. C1 Net-_Q1-E_ Net-_C1-Pad2_ 22u Q1 /BOB Net-_Q1-B_ Net-_Q1-E_ BC549/550 Q2 Net-_Q2-C_ /INPUT Net-_Q2-E_ BC549/550 R5 Net-_Q1-E_ Net-_Q3-E_ 16k Choosing and Running Simulations Now that SPICE is aware of component models, and the circuit topology, it can be made to run a desired simulation (technically known as an analysis ). SPICE offers different analyses, of which the following three are typically encountered (others are too, but I will only cover these three for now, and may add more to this section later). DC Voltages and Currents (Operating Point) Simulations When designing a circuit, often the user needs to bias components to operate in a certain region, and then perhaps a varying signal is applied. This is easiest to picture with an amplifier circuit. The transistors would been to be placed into a region where they are passing some current, so that later when a varying audio signal arrives, that signal will linearly affect the amplified output. A DC Operating Point simulation tries to calculate such initial voltages and currents in the circuit when no varying signals are present. It’s as if a user applied a multimeter to locations in a circuit. When KiCad (or any other software application that uses the SPICE engine) runs such a simulation, the output will be a list of these voltages and currents for each wire in the circuit. Here is a snippet of example output: I(q1:c): 101.647uA I(q1:b): 432.641nA I(q1:e): -102.079uA V(net-_q1-b_): 1.31966V V(/in): 0V P(c2): 0.00114469fW V(net-_c3-pad1_): 5.63932V P(c3): -3.82135e-05fW Most users won’t ever need to follow that, and will instead look to see how the desktop software displays it graphically; in the screenshot below, it can be seen that the voltage at Q1 base is 1.32V, and the current flowing through the collector is 102 uA. Both of those values are also in the text output above. Time-Domain (TRAN) Simulations What SPICE calls a TRAN (short for Transient) analysis is really an oscilloscope-like simulation of all the voltages and currents in a circuit, as if an oscilloscope voltage or current probe were applied everywhere. Imagine testing a real circuit, where first a user may use a multimeter, which is close to what a DC Operating Point analysis (as discussed earlier) achieves, and then the user connects up the oscilloscope, which is what a TRAN analysis is closest to. Much like how an oscilloscope is set to a certain timebase (time per division) setting and then the oscilloscope Run/Stop button is pressed to capture the signal values over a period of time, the TRAN analysis is configured near-identically. Usually you need to choose the start and stop time and the step time for each sample of results. As with any other analysis, SPICE will output a load of values, but KiCad will also display them graphically. A user can choose which signals are of interest, and those will be displayed just like if an oscilloscope was being used. In the example in the screenshot below, the user has selected to view one signal, but others could be chosen too, just like oscilloscope channels. An important thing to note, is that unlike an oscilloscope, SPICE does not run continually. It’s a one-time simulation. If changes are made to the circuit, then the simulation needs to be rerun. In contrast, with an oscilloscope, you can make changes to a circuit and watch the effects in real-time. A few rare software tools can provide simulations that look real-time, but in the background, they are likely repeatedly running the SPICE engine for small periods of time, and updating the chart each time, thus making it appear dynamically updated. It can work really well, but unfortunately KiCad doesn't support that (and neither does LTspice , TINA/Spice , PSPICE , and so on). Frequency Response Simulations (AC) SPICE has an analysis called AC , which applies a swept frequency stimulus signal, and records the output at each frequency. CAD software can read the output file, and convert to gain and phase values and plotted as would a frequency response analyzer test tool. This sort of simulation is highly useful for examining filter bandwidths, and seeing if an audio amplifier has a flat response or not, for example. SPICE needs to be told what frequency range to use; for an audio amplifier, one might select from 10 Hz to 100 kHz perhaps. The screenshot below shows that the user was interested to see the simulation run up to 10 MHz (which is typed as either 10Meg , or 10e6 , and _not_ 10M; this is an artifact from SPICE’s heritage). Unlike the earlier analyses (DC Operating Point and Transient), to be useful, the AC analysis always requires the SPICE engine to be instructed where the stimulus signal is to be applied. With KiCad, a sine-wave stimulus is indicated directly on the schematic, by placing a component called VSIN from KiCad’s supplied Simulation_SPICE library and wiring it to the circuit just like any other component. The stimulus source needs some configuration to work with SPICE. In KiCad, this is entered by double-clicking on the symbol and editing a symbol property: Technically all that is required is for that line to always state AC 1 (this scales the values to read correctly) however it’s useful to precede it with something like SIN(0 1m 1k) because that is then useful for TRAN simulations which may benefit from sine wave stimulus too (it depends on the circuit in question). The values 0, 1m and 1k represent the DC offset, Vpeak amplitude, and frequency, i.e. a sine wave with 1 mV peak (2 mV p-p) and 1 kHz frequency. Since the ordering may be hard to remember, it’s possible to place comments after a semicolon: The screenshot below shows what the simulation results can look like. SPICE will have generated a file containing detail for each connection in the circuit, across the specified range of frequencies. The user can select the signals of interest, and the software will chart the frequency response. Summary SPICE allows the user to perform analyses (i.e. simulations) to achieve measurements of the type that could be performed in real life with a multimeter, oscilloscope and frequency response analyzer. Other types of simulation are possible too. SPICE is text-file based, and manufacturers supply model files containing parameters or netlists for more complex devices and subcircuits, which can be assembled into a circuit netlist by CAD software such as KiCad, based on a schematic a user may create. When instructed to run a simulation based on those text files, SPICE will generate output in text form, which the CAD software can present graphically. Thanks for reading! Further Information (+) KiCad 8: Working with Circuit Simulations! - element14 Community SPICE3 User Manual (PDF) Preamp circuit discussion (see the comments sections below the blog)kicadsimulationcircuit simulationcadspicehttps://community.element14.com/challenges-projects/design-challenges/smart-security-and-surveillance/f/forum/56830/identity-protocol---part-2---django-server/234975Tue, 14 Apr 2026 02:13:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:3a59be96-5c25-4b82-9584-256f2ef50b1carvindsaYou've asked some serious questions and i love it. Django calls itself a "battery included " framework and comes with almost everything needed to prototype a web app and thus it includes its own admin interface which is next best thing to editing data on the database directly. But it cannot be styled well, so I developed a custom one from scratch. Now, To answer your questions, 1. The enumeration shown is only for easy understanding, it can be a uuid or any unique random string. 2. In ideal case, these system should be firewalled to access only internal networks and would require tls pinning or mTLS to avoid mitm attack. mTLS is something the ATECC508A can do well, although its limited to some 16 single write slots for the encryption key. for an proper mtls rotation system as required for an ideal security system with attec508a il have to the mtls keys encrypted by one a dedicated key in the ATECC508A and have the ciphertext saved in a general flash chip. I'm not sure if I can achieve that within the timeline of this challenge though Would've been lovely to implement though.https://community.element14.com/challenges-projects/design-challenges/smart-security-and-surveillance/f/forum/56830/identity-protocol---part-2---django-server/234974Tue, 14 Apr 2026 01:42:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:68455c9b-fb96-4922-aea3-354b2d83417csaramicpretty cool setup - is the whole admin interface above something that comes with Django? or is it built from scratch? I presume some kind of library? I do like the idea of your encryption running via a chip ATECC508A , I env ordered some to have a bit of a play. I know that this is a PoC (proof of concept) but it always interests me to take a look at vulnerabilities in a security system. What I can see so far: enumerable ID's for GET /api/keys/ / presumably ID-001, ID-002 as this is an unauthenticated endpoint does that mean I can find out who works there? is there a chance of a man-in-the-middle attack with a server? is there any auth proving that the server is the right one to respond with? I presume you could: TLS certificat pinning? HMAC - respond with an X-signature that is HMAC-SHA256 over the body using the door's API key as the HMAC secret mTLS - Mutual TLS - set the CA certificates ahead of time anyway, interested to see how it all works out in the end - good luckhttps://community.element14.com/products/raspberry-pi/f/forum/56837/trying-the-pi-pico-rx-sdr-project/234973Mon, 13 Apr 2026 23:56:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:87d50b8b-131b-4ab9-b716-dcb209533518scottiebabeSpent some time putting the UI bits on a front panel. Most of the configuration options are only available via the physical UI, not the usb serial interface. The author did a nice job on the UI, it looks sharp.https://community.element14.com/challenges-projects/design-challenges/smart-security-and-surveillance/f/forum/56831/accessing-the-pan1326b-bluetooth-module-on-the-max32630fthr/234972Mon, 13 Apr 2026 21:24:00 GMT93d5dcb4-84c2-446f-b2cb-99731719e767:294c9fb8-fdce-4f67-b04b-77b9031aa5dcBigGThat made all the difference and with a little tidy up and a few bug fixes, thanks to my AI secret agent, I got there in the end. I now get the magic sequence: #include "pwrseq_regs.h" #include "rtc_regs.h" #include "ioman_regs.h" #include "gpio_regs.h" // Define the correct Serial port based on your MXC_HardwareSerial.h discovery #define SerialBLE Serial0 // Pin Definitions for MAX32630FTHR #define BLE_SHUTDOWN_PIN P1_6 // nSHUTD (Active Low) #define M4_RTS_OUT_TO_BLE P0_2 // M4 RTS Output #define BLE_RTS_IN_TO_M4 P0_3 // BLE Module RTS Input (M4 CTS) #define M4_TX_PIN P0_0 // UART0 TX (Mapping B) #define M4_RX_PIN P0_1 // UART0 RX (Mapping B) // HCI_Reset Command: [PacketType][OpCode Low][OpCode High][Length] const uint8_t HCI_RESET_CMD[] = {0x01, 0x03, 0x0C, 0x00}; void setup() { // Initialize Debug Serial (USB) Serial.begin(115200); while(!Serial); delay(500); Serial.println("\n--- PAN1326B Final Methodical Sketch ---"); // Set 1.8V Logic for all Bluetooth UART pins useVDDIO(M4_TX_PIN); useVDDIO(M4_RX_PIN); useVDDIO(M4_RTS_OUT_TO_BLE); useVDDIO(BLE_RTS_IN_TO_M4); Serial.println("1. VDDIO set to 1.8V."); // Configure 32.768 kHz Clock (P1.7) MXC_RTCCFG->clk_ctrl |= MXC_F_RTC_CLK_CTRL_NANO_EN; MXC_RTCCFG->osc_ctrl |= MXC_F_RTC_OSC_CTRL_OSC_WARMUP_ENABLE; MXC_RTCTMR->prescale = MXC_V_RTC_PRESCALE_DIV_2_0; MXC_PWRSEQ->reg4 |= MXC_F_PWRSEQ_REG4_PWR_PSEQ_32K_EN; Serial.println("2. 32kHz Heartbeat active on P1.7."); // Prepare Pins: Set M4 RTS LOW BEFORE the module wakes up // This ensures the BLE module sees "Permission to Speak" immediately. pinMode(M4_RTS_OUT_TO_BLE, OUTPUT); digitalWrite(M4_RTS_OUT_TO_BLE, LOW); pinMode(BLE_RTS_IN_TO_M4, INPUT); // Monitor the module's RTS pinMode(M4_RX_PIN, INPUT); // Prepare RX for data Serial.println("3. Flow control pins staged (M4 RTS = LOW)."); // Initialize SerialBLE (Serial0) // Note: We use 115200 but re-assert IOMAN immediately after. SerialBLE.begin(115200); // Force IOMAN to Mapping B (Crossover) // Serial0.begin() often reverts to Mapping A. We force it back to B. // 0x11 = Request Mapping B for RX/TX pins. MXC_IOMAN->uart0_req = 0x11; while (MXC_IOMAN->uart0_ack != 0x11); Serial.println("4. UART0 Mapping B (Crossover) Locked."); // Pulse Reset (nSHUTD) pinMode(BLE_SHUTDOWN_PIN, OUTPUT); digitalWrite(BLE_SHUTDOWN_PIN, LOW); delay(100); digitalWrite(BLE_SHUTDOWN_PIN, HIGH); Serial.println("5. BLE Reset released. Waiting for module..."); } void loop() { static int lastRtsState = -1; int currentRtsState = digitalRead(BLE_RTS_IN_TO_M4); // Monitor for the Module's RTS drop (Signaling it is ready) if (currentRtsState != lastRtsState) { Serial.print("\n[Module RTS Change: "); Serial.print(currentRtsState == LOW ? "LOW (Ready)" : "HIGH (Busy)"); Serial.println("]"); lastRtsState = currentRtsState; // AUTO-TRIGGER: If the module just became ready, send the reset command if (currentRtsState == LOW) { Serial.println(">>> Sending HCI_Reset Command..."); SerialBLE.write(HCI_RESET_CMD, 4); } } // Handle Manual 'r' Trigger from PC if (Serial.available()) { char c = Serial.read(); if (c == 'r') { Serial.println("\n>>> Manual Trigger: Sending HCI_Reset..."); // Clear buffer first while(SerialBLE.available()) SerialBLE.read(); SerialBLE.write(HCI_RESET_CMD, 4); } } // Read and Print Module Response if (SerialBLE.available()) { // Wait briefly for the full packet to arrive delay(10); Serial.print("<<< BLE Response (HEX): "); while (SerialBLE.available()) { byte b = SerialBLE.read(); if (b < 0x10) Serial.print("0"); Serial.print(b, HEX); Serial.print(" "); } Serial.println(); } }