When your iProg+ programmer displays the "Not Connected" status despite being a new device, it usually stems from a driver conflict, a power supply issue, or a serial number mismatch in the software. Troubleshooting Steps
Check Driver Installation: The most common cause is the lack of proper FTDI drivers. Open Device Manager on your PC.
Look for "Ports (COM & LPT)" or "Universal Serial Bus controllers."
If you see a yellow exclamation mark or "Unknown Device," right-click and manually update the driver using the "Drivers" folder provided with your iProg software.
Verify Serial Number (SN): The software and the hardware must share the same serial number to communicate.
Check the sn.txt file in your software directory. It must match the hardware ID (common IDs for clones include 1, 35, or 45).
If they don't match, the software will refuse to initialize the connection. USB Port & Cable:
Ensure you are using a USB 2.0 port. Some iProg clones struggle with USB 3.0 (blue ports).
Try a different USB cable; the ones bundled with the units are often of lower quality and may fail to provide stable data transmission.
Power Supply: iProg requires stable 12V for many operations (like EEPROM or MCU programming). Ensure your external power supply is connected if the script you are running requires more than just USB power.
Disable Antivirus: Security software often flags iProg executable files or scripts as "cracks" or malware, deleting essential .dll files needed for the connection. Re-extract the software with your antivirus temporarily disabled. Common Status Indicators Red LED: Power is reaching the board.
Green LED: Data communication is active. If only the red light stays on and the software says "Not Connected," the PC is not "talking" to the internal FTDI chip.
The "Programmer not connected" error on a new unit usually stems from driver installation issues or operating system incompatibility. Common Fixes Driver Reinstallation
: The most frequent cause is an incorrectly installed driver. You should uninstall the current driver and manually reinstall it. OS Compatibility
: iProg+ software is notoriously unstable on Windows 10/11. It is highly recommended to use Windows 7 (32-bit) for reliable operation. Software Version : If you are using V89, try switching to
, as it is often more stable and guaranteed to work on Windows 7. : Avoid using USB 3.0 (blue) ports; try a USB 2.0 port
or a different cable to ensure the laptop recognizes the device. Critical Warnings Power Supply
connect the iProg+ unit to an external 12V power supply. It must only be powered via the 5V USB port. External 12V power can permanently damage the hardware. Hardware Damage
: If the software displays "power loaded," this indicates a hardware failure (like a blown transistor), which usually requires a hardware replacement. iprog programmer not connected new
Are you seeing any specific LED colors on the unit, or is the software giving a "power loaded" error as well? IPROG Pro V87/V89 Universal Programmer Instruction Manual
If your iProg+ programmer shows a "Not Connected" status during a new setup, it
usually indicates a driver conflict, a power supply issue, or a hardware-software mismatch often found with clone devices Quick Hardware Diagnostics
Check the LED indicator light on your programmer to identify the problem state: LED is OFF:
The programmer has no power supply or is physically damaged. LED is BLINKING: The programmer is working, but the driver is not installed correctly LED is ON (Solid):
The programmer is working and the driver is correctly recognized. REVELTRONICS - Forum Common Fixes for New Setups Reinstall USB Drivers
: This is the most common cause. You may need to manually uninstall the current driver from the Device Manager (where it might appear as an "Other Device" or have a yellow exclamation mark) and reinstall the specific driver provided with your software. Use USB 2.0 Ports : Some iProg+ clones have compatibility issues with
(blue ports). Try connecting to a standard USB 2.0 port or using a USB hub. Check the USB Cable
: Faulty or low-quality USB cables can cause intermittent connection errors. Test with a known working high-quality cable to see if the status changes. Serial Number Mismatch
: If you are using specific scripts, the software may require the programmer to have a matching serial number. Some versions allow you to change the serial number via the software to enable compatibility with different script packs. Disable Driver Signature Enforcement
: On Windows 10 and 11, the OS may block the iProg driver because it isn't digitally signed (Error Code 52). You may need to restart Windows in "Disable Driver Signature Enforcement" mode to complete the installation. REVELTRONICS - Forum Software Configuration Ensure the software's iProgPro.ini
or similar configuration files are not pointing to the wrong COM port. You can check which COM port the device is assigned to in the Windows Device Manager under "Ports (COM & LPT)". for Windows 11? Programmer is not connected - REVELTRONICS - Forum
Re: "Programmer is not connected" ... Problem solved, the driver was not properly installed. REVELTRONICS - Forum Programmer is not connected (V1.9.0) - REVELTRONICS
The "Not Connected" error in iProg+ software typically indicates a communication failure between the hardware and your computer. Follow these troubleshooting steps to resolve the issue: 1. Core Hardware & Power Checks
USB Power Only: Ensure the iProg+ unit is connected only to a 5V USB port on your computer.
⚠️ Warning: Never connect an external 12V power supply to the main unit, as this can permanently damage the internal components.
Connection Stability: Verify that the USB cable is firmly seated in both the iProg+ unit and the computer. Try using a different USB port, preferably on the back of a desktop PC for better power stability. 2. Driver & Software Configuration Iprog Pro Full V89 Universal Programmer Instruction Manual
Troubleshooting the "iProg Programmer Not Connected" Error The "Programmer Not Connected" error in iProg+ software typically stems from driver misconfiguration, hardware power issues, or operating system incompatibility. Use the following guide to identify and resolve these connectivity issues. 1. Identify Connection Status When your iProg+ programmer displays the "Not Connected"
The iProg+ software and device use indicators to signal the connection state: No Power/Damaged:
The programmer is not receiving power or is hardware-damaged. Driver Missing:
The programmer is powered and working, but the driver is not correctly installed. Connected:
The programmer is working, and the driver is installed correctly. 2. Basic Hardware Checks
Before attempting software fixes, ensure the physical setup is correct: USB Port Power: Only connect the iProg+ to a standard 5V USB port on your computer. Avoid 12V External Power:
connect an external 12V power supply to the main iProg+ unit. This can permanently burn out the internal circuits.
Verify the USB cable is secure. If the software still fails to detect it, try a different USB port or a different cable to rule out a faulty connection. 3. Driver and Port Configuration
Most connectivity issues occur because the computer fails to assign the device to the correct COM port. Manual Driver Installation: If the device appears as an "Unknown Device" in Device Manager
, right-click it and select "Update Driver." Point the installation wizard to the folder within your iProg software directory. COM Port Setting: Device Manager Ports (COM & LPT)
. The device should be listed as "iProg universal programmer." For optimal compatibility with many scripts, ensure it is set to Driver Reinstallation:
If errors persist, uninstall the existing driver from Device Manager, unplug the device, restart your PC, and perform a fresh installation. 4. Software and OS Compatibility
The iProg+ software is primarily designed for older environments. Recommended OS: Windows 7 (32-bit) for the best stability. Incompatibility with Windows 10/11:
While some versions (like V89) may work on Windows 10, they are often unstable and may fail to recognize the hardware. Software Version:
If using V89 (a testing version) results in errors, it is recommended to revert to the more stable V87 software 5. Advanced Hardware Repair (Clones)
If the software detects the unit but specific adapters (like RFID or UART) fail, the issue may be internal to the programmer's mainboard: USB driver Installation Guide (Win 8 / 8.1 / 10) - DediProg
The "Programmer not connected" error in iProg software typically indicates a communication failure between the hardware and the computer. This guide explores the common causes and provides a structured approach to troubleshooting this issue. Understanding the Status Indicators
Before diving into software fixes, check the LED status on your iProg+ main unit:
: The programmer is not receiving power or is physically damaged. LED Blinking (Slowly) Open Device Manager ( devmgmt
: The hardware is working, but the device driver is either missing or incorrectly installed. LED On (Solid Red)
: The programmer is powered and the drivers are installed correctly. Phase 1: Physical and Hardware Verification
Often, a simple hardware oversight causes the "not connected" message. USB Port & Cable
: Try a different USB port on your laptop. Faulty USB cables are a frequent cause of connection drops; replacing the cable has resolved many "not connected" or "unknown device" errors. Power Warnings
: Ensure the unit is only connected via the 5V USB cable. Connecting to an external 12V power supply can permanently burn out the internal power module. Direct Connection
: Avoid using USB hubs, as they may not provide enough power or stable communication for the programmer. Phase 2: Driver Installation & Configuration
If the red LED is blinking, your computer does not recognize the device properly. Manual Driver Installation
: If you are using a newer version of the software (e.g., v1.3.x or later), ensure drivers from previous versions are manually uninstalled from the Windows Device Manager before installing new ones. COM Port Settings
: In Device Manager, check under "Ports (COM & LPT)." The iProg universal programmer should typically be assigned to for certain software versions to function correctly. Unsigned Drivers
: On modern Windows systems, driver installation may hang if the driver is not digitally signed. You may need to disable driver signature enforcement temporarily. Phase 3: System Compatibility iProg software has specific operating system preferences: Recommended OS : It is highly recommended to use Windows 7 32-bit for the most stable performance. Windows 10/11 Issues
: Many users report that Windows 10 and 11 systems can cause "not connected" errors or software freezes during operations like flash erasing. If you must use Windows 10, ensure it is a clean installation and consider running the software in compatibility mode. Software Versions
: If V89 (often a testing version) shows connection errors, try reverting to , which is known for higher stability on most systems. Summary Troubleshooting Checklist Potential Result Blinking means drivers; Solid means software/COM port. Replace USB Cable Fixes intermittent connection or "unknown device". Device Manager Uninstall "Unknown Device" and reinstall driver manually. Ensure it is set to COM4 if required by your version. Compatibility Switch to Windows 7 32-bit if Windows 10 fails. the drivers in Windows 10? IPROG Pro V87/V89 Universal Programmer Instruction Manual
devmgmt.msc).iPROG Virtual COM Port (correct)USB Serial Device or Unknown Device (incorrect)Action if incorrect: Proceed to driver reinstallation (Section 4).
90% of "Not Connected (New)" errors on Windows 10/11 are due to driver signatures. iProg clones need a specific, unsigned FTCProg.dll or iProg.sys driver.
How to disable permanently (Windows 10/11):
bcdedit /set testsigning on and press Enter.Alternative (One-time boot):
If driver installation succeeds but software still says "Not Connected", the iPROG may have corrupted or outdated firmware.
USB Serial Port → Uninstall device.Unknown device under Other devices.The "iProg programmer not connected" error is rarely a fatal device failure. In 90% of cases involving new units, the culprit is a missing CH340 driver, an incorrect COM port number assignment, or a low-quality USB cable. Addressing the USB-to-Serial bridge configuration typically resolves the issue immediately.
It sounds like you’re encountering an “iPROG programmer not connected” error, possibly with the word “new” appearing in the message. This is common when using iPROG (a PIC microcontroller programmer, often a clone of the K150 or similar JDM/ProgPic type programmers) with software like iPROG Programmer Software, WinPIC, PICPGM, or IC-Prog.
Below is a helpful troubleshooting report to resolve this.