Add small gate auto-close to existing PIC16F873 .asm + build HEX (no code changes).

@cnarvaez1957

Hello. I have extensive experience with Microchip PIC microcontrollers, including the PIC16F873. I am an expert in MPLAB, MPLAB X IDE, MPASM, and PIC-AS assembler. Sincerely, Carlos

@jaredj49

Hi, I have extensive hands-on experience with legacy Microchip assembly projects, including maintaining and modifying production firmware for devices such as the PIC16F873 using classic MPASM toolchains. I can insert your ~15-line gate auto-close logic precisely within READINP (after INP8 check and before NOIP/RETURN) with clearly marked start/end comments, without altering ORG/RES directives, banking structure, # immediates, or the existing __CONFIG 0xD01 setting. The build will be compiled using a compatible legacy MPASM version (not PIC-AS), ensuring the resulting .hex matches your original architecture and assembles cleanly under MPLAB X with zero syntax modernization. Deliverables will include the updated .asm file with only the required insertion, compiled .hex file, complete MPLAB X project folder, and a short build note confirming MPASM version, clean build status, and exact insertion location. I understand the 4 MHz XT configuration and will ensure no unintended timing or banking side effects are introduced. Best regards. Jared

@yaroslavmark

✅Okay, I got what you want exactly. I am a senior embedded systems engineer with over 10 years of experience, providing low-level PIC assembly development, legacy MPASM builds, and MPLAB project maintenance for production hardware. In my opinion, the safest way to handle this is to surgically insert the auto-close block exactly at the specified READINP location without touching ORG/RES structure, banking logic, or legacy syntax, then rebuild using a verified legacy MPASM toolchain to preserve timing and config behavior. I’ll keep your __CONFIG 0xD01 untouched and ensure the HEX is generated cleanly under the correct device settings for the 4 MHz XT crystal environment. This project is very similar to my previous works. Recently, I updated a 4,300-line PIC16F877A industrial controller file where I inserted a 12-line watchdog recovery routine between two legacy state checks without modifying banking macros or immediate syntax, then rebuilt it under MPASM 5.51 with zero warnings. I’ve also maintained older gate and pump control boards running at 4 MHz where precise flag and ZERO bit behavior had to remain cycle-accurate. Via private chatting or meeting, I will provide the creative idea and good tech solution for your project and I want to discuss about the budget and timeline in detail. Best regards. Yaroslav

@tetianam8

⭐⭐⭐⭐⭐ Yes — I can do this exactly as specified: legacy PIC16F873 MPASM build, no PIC-AS, no rewrite, no “modernization,” and no changes to ORG/RES, banking conventions, # immediates, or __CONFIG 0xD01. I’ll insert your ~15-line gate auto-close block in READINP, after the INP8 check and before NOIP/RETURN, wrapped with clear START/END comments, and keep the rest of the file untouched aside from optional light comment/spacing alignment if helpful. Deliverables you’ll get: Updated .asm (only the insertion added) Compiled .hex Full MPLAB X project folder Short note: MPASM version used, “build clean,” and exact insertion location Process: Insert block + verify banking context (BANK0/BANK1 as you wrote) Build in MPLAB X using MPASM (legacy) Deliver package + stand by for your PICkit 4 hardware test Up to 2 minor revision rounds (banking/timing/behavior tweaks) included

@TheDesignBloke

Hi there, I went through your project carefully, and the core challenge is clear: inserting a small gate auto-close block into your existing PIC16F873 assembly code without altering any legacy syntax. This isn’t a surface-level task , it needs someone who understands assembly language intricacies and can execute precisely without hand-holding. I’ve handled similar work with complex legacy systems where accuracy and speed matter. My approach is straightforward: I'll directly insert the specified code in the READINP section while maintaining your original structure and formatting. No guesswork, just efficient results that align with your standards. If this aligns, I can start immediately and deliver the updated .asm file and .hex within 3 days. One quick question before I proceed: Could you please confirm the MPASM version you prefer for building the .hex? Best regards, Muskan

@antonk52

✔✔✔Hold on!! Looking for a Developer Who Gets Results? Hire Me, Relax, and Watch Your Project Turn Into Success✔✔✔ I can update your PIC16F873 assembly exactly as described: insert the 15-line gate auto-close block in READINP after INP8 and before NOIP/RETURN, with clear start/end comments. I will: • Use the original MPASM syntax—no CBLOCK conversion, no legacy fixes • Keep all banking, #immediates, and ORG/RES intact • Deliver the updated .asm, compiled .hex, and full MPLAB X project folder • Provide a short note with MPASM version, “build clean”, and insertion location Fixed price: $200 AUD (within your $150–$250 range) Timeline: 2 days for first delivery, with up to 2 minor revisions if needed I have extensive experience with legacy PIC assembly and fast, accurate MPASM builds, ensuring smooth hardware testing on your PIC16F873 board.

@MADTechUK

Hi there, I am eager to assist with adding the auto-close gate functionality to your existing PIC16F873 assembly file. With a strong background in microcontroller programming and experience specifically with legacy PIC assembly, I understand the intricacies involved in working with such legacy systems while ensuring compatibility with MPASM. I will effectively insert the specified ~15-line code segment into the READINP section as requested while preserving the original file's legacy syntax, ensuring that no other configurations are altered. Expect a swift turnaround of 1-3 days for the updated .asm file, compiled .hex file, and an MPLAB X project folder. Could you provide any specific timing requirements for the auto-close function? Thanks, Muskan

@sofiaa446

❤️Hello! I have hands-on experience with PIC16F87x family devices using classic MPASM, and I understand the constraints of maintaining legacy assembly projects without “modernizing” or restructuring them. I will not convert to CBLOCK, will not alter # immediates, will not change banking structure, and will not touch ORG/RES layout or your existing __CONFIG 0xD01. ✔ Confirmation I can compile using an older MPASM toolchain (not PIC-AS, no migration). I will insert only the provided ~15-line block, clearly wrapped in: The insertion will be placed exactly after INP8 check inside READINP, before NOIP/RETURN, as specified. Banking context will be preserved exactly as written. No syntax “corrections” or structural rewrites. I am really impressed about this opportunity as this is perfect fit for my skills and would like to discuss how we can move forward. Regards,

@michaelr146

Hi, there, I'm a licensed professional engineer with 10+ years in embedded electronics and legacy PIC work. I understand you want a 15-line gate auto-close block inserted into READINP after INP8, without changing ORG/RES, # immediates, or banking, and to build with an old MPASM toolset. I’ve done similar insertions on PIC16F873 projects and kept timing and flow intact. Solution - Insert the block between INP8 check and NOIP/RETURN with clear start/end comments - Preserve all existing syntax and # immediates as-is - Produce an updated .asm file with exact placement and comments - Compile to .hex using the specified MPASM version, no CBLOCKs or syntax changes - Provide a full MPLAB X project folder and a short notes file detailing MPASM version and build steps I’ve done close-variant work on legacy PIC16 assemblies and delivered working hexs on hardware before. Do you want me to preserve any existing inline comments around the insertion point besides your requested start/end markers? I look forward to working with you. Best Regards, Michael

@astasoft14

Hello, I am highly experienced with legacy PIC16F873 development and the specific nuances of MPASM. I understand the importance of maintaining your existing syntax, banking, and # immediate formatting without modernization. I will precisely integrate the 15-line gate auto-close block into the READINP routine. I have already reviewed your logic and will ensure the BANK1 transitions and 16-bit DOSETIME checks function correctly within your ~5000-line source. My Process: Code Integration: Precise insertion into the assembly without altering your legacy structure. Verification: I will use Proteus VSM to simulate the updated .hex file, verifying that the gate triggers, manual overrides, and pulse timings work exactly as intended. Legacy Build: Compiled using the original MPASM environment to ensure 100% binary compatibility. No-Risk Guarantee: I will not accept any payment until you have the working, verified code in hand and are satisfied with the results. Looking forward to helping you maintain this system.