I2C Jobs

1) Project goal Design a single PCB device for testing cable harnesses up to 25 wires, where both ends of the same harness are connected to the board: Side A: 25 lines (A1..A25) Side B: 25 lines (B1..B25) Total: 50 signal lines on the PCB. The detailed test logic (continuity/shorts/mapping) will be implemented in firmware later. For this phase, the key deliverable is robust hardware (schematic + PCB) prepared for such testing. 2) Scope of work (hardware only) Electrical schematic PCB layout Production files: Gerbers + drill BOM (with specs and acceptable alternatives) Assembly files (pick&place/positions) preferred Short mapping table: MCP23017 pins → A/B line numbers (Firmware is NOT required in this phase. Optional “I2C scan / basic blink” is a bonus.) 3...

Description: We are developing a prototype of a motor control system based on an existing PCB that uses an ATmega16 microcontroller. The current system controls the speed and torque of the main motor and the speed of a secondary motor. Inputs are presently taken from a custom-made keyboard with tactile push buttons, and motor control is achieved by pulling specific GPIO pins high or low in defined sequences. The objective of this task is to replace the physical keyboard input system with a capacitive touch LCD display, where the on-screen UI buttons will perform the same functions as the existing tactile buttons. The touchscreen interface will control motor on/off, speed, and torque, while ensuring that the existing motor control logic based on GPIO sequences remains functionally the same....

I already have the full schematic and the finished PCB files for a board that combines an ESP module with a PIC18F microcontroller. What I’m missing is a clear, practical explanation of how everything talks to each other, especially over UART, and how that interaction is implemented on the physical board. Here is what I need from you: • A step-by-step walkthrough of the signal paths that handle UART traffic between the ESP and the PIC18F, including any level-shifting, buffering, or hand-shake lines that support the link. • A guided tour of the PCB layout that shows where those signals travel—layer changes, vias, ground references, decoupling, and any routing choices that affect integrity or noise. • Simple notes on any supporting circuitry (power rails, ...

I already have the full schematic and the finished PCB files for a board that combines an ESP module with a PIC18F microcontroller. What I’m missing is a clear, practical explanation of how everything talks to each other, especially over UART, and how that interaction is implemented on the physical board. Here is what I need from you: • A step-by-step walkthrough of the signal paths that handle UART traffic between the ESP and the PIC18F, including any level-shifting, buffering, or hand-shake lines that support the link. • A guided tour of the PCB layout that shows where those signals travel—layer changes, vias, ground references, decoupling, and any routing choices that affect integrity or noise. • Simple notes on any supporting circuitry (power rails, ...

# Embedded Linux System – Technical Specification ## Custom Hardware Platform based on Raspberry Pi CM4 --- ## 1. Project Overview This project is based on an **existing, functional custom hardware platform** using a **Raspberry Pi Compute Module 4 (CM4)**. A standard Raspberry Pi OS is already running on the device. The goal of this project is **not to create a prototype**, but to bring an **existing custom CM4-based hardware platform into a professionally engineered, maintainable, and reproducible software state**, suitable for industrial deployment and scaling. --- ## 2. Project Goals The primary project objective is to **bring a custom hardware platform with a Raspberry Pi CM4 module into a robust, industrial-grade software state**, including: - a clean and well-docu...