Welcome to HackerBox 0084 where we will explore PCB rework tools and techniques. Configure development tools for the ESP8266 D1 Mini 2.4GHz Wi-Fi Module. Assemble a minimal embedded test platform using the ESP8266 D1 Mini module, OLED display, input buttons, and an output RGB LED. Leverage the minimal embedded test platform to implement a graphical game, packet capture tool, and other network security experiments. Apply a logic probe to debugging digital circuits and test jumper wire connections while making wire mods. Perform a bodge wire modification to repair an RGB LED circuit. Extend the number of MCU output pins by making PCB cuts and jumps to add a digital SIPO shift register configured to drive multiple LEDs. Deadbug mod a PISO shift register to extend the number of MCU input pins and support a sixteen button keypad. Assemble an SMD soldering practice kit to improve surface mount soldering skills.
Slightly more advanced rework technique generally involves trace cutting and jumping. Use of wire added to a board can be called "jumpers", "wire mods", "white wires", "bodge wires", and so forth. Wire mod work can get pretty involved when wiring in an entire chip (dead bug or otherwise), or swapping pin order on an entire bus slot connector. This beauty popped up recently on Hackaday.
Bga Mods Rework Software Download
Some of the most advanced rework techniques can deal with rebuilding lifted pads/traces, working with BGA (ball grid array) devices, or making mods to finished deliverable products that must remain visually tidy as well as mechanically robust.
The Seismic Analysis Code (SAC) is the result of toil of many developers over almost a 40-year history. Initially a Fortran-based code, it has undergone major transitions in underlying bit size from 16 to 32, in the 1980s, and 32 to 64 in 2009; as well as a change in language from Fortran to C in the late 1990s. Maintenance of SAC, the program and its associated libraries, have tracked changes in hardware and operating systems including the advent of Linux in the early 1990, the emergence and demise of Sun/Solaris, variants of OSX processors (PowerPC and x86), and Windows (Cygwin). Traces of these systems are still visible in source code and associated comments. A major concern while improving and maintaining a routinely used, legacy code is a fear of introducing bugs or inadvertently removing favorite features of long-time users. Prior to 2004, SAC was maintained and distributed by LLNL (Lawrence Livermore National Lab). In that year, the license was transferred from LLNL to IRIS (Incorporated Research Institutions for Seismology), but the license is not open source. However, there have been thousands of downloads a year of the package, either source code or binaries for specific system. Starting in 2004, the co-authors have maintained the SAC package for IRIS. In our updates, we fixed bugs, incorporated newly introduced seismic analysis procedures (such as EVALRESP), added new, accessible features (plotting and parsing), and improved the documentation (now in HTML and PDF formats). Moreover, we have added modern software engineering practices to the development of SAC including use of recent source control systems, high-level tests, and scripted, virtualized environments for rapid testing and building. Finally, a "sac-help" listserv (administered by IRIS) was setup for SAC-related issues and is the primary avenue for users seeking advice and reporting bugs. Attempts are always made to respond to issues and bugs in a timely fashion. For the past thirty-plus years
2ff7e9595c
Comments