1. Erdos Port Devices Driver Ed
2. Erfos Port Devices Driver

G o to Device Manager by going to start / search box and type device manager and enter and then double-click on the program icon that appears. Check each device for a red x, yellow! These identify devices with problems (probably drivers, but also conflicts or something else). Click on each for further details and troubleshooting tips. Automation Integrator uses Pepperl+Fuchs Comtrol for Device Connectivity. A leading integrator of factory automation and robotics solutions selected the Pepperl+Fuchs Comtrol DeviceMaster UP 2-port 2E for a production line cell for forging spindles. In this application laser markers communicating via Ethernet TCP/IP were used to apply a serial. On Windows 10, a device driver is an essential piece of code, which allows the system to interact with a specific hardware (such as graphics card, storage driver, network adapter, Bluetooth, etc.

Dec 21, 2020 • Filed to: USB Recovery • Proven solutions

Have you ever had difficulty connecting your devices to your computer using a Prolific USB to Serial adapter? If yes you are lucky to find this page, it will give you all the information need to fix an unresponsive Serial driver adapter. You may have noticed a yellow exclamation mark hovering over or beside the USB to Serial Driver when searching your Device Manager and if you have we can all agree that it signifies a prevailing problem.

Overview of the Error

If you are not able to connect your device to your PC using a USB to Serial adapter it may be that

• The USB driver is outdated
• The USB Driver is missing
• Or even a corrupted driver

While you can't be so sure what the exact problem is there are solutions you can adopt to fix the issue once and for all. Read on to find quick fixes to resolve the problem.

1# Fix Prolific USB to Serial Driver not Working

Solution: Roll your Prolific USB to Serial Driver back to an older version

Updating your drivers often work wonders for your system because it makes sure that it runs on the latest features that guarantee maximum functionality. Unfortunately updating your drivers can cause this kind of error especially if your latest update does not work too well with your hardware. Once you upgrade your PC to the latest Windows version your Prolific USB to Serial Driver also updates to the latest driver software and if the driver is not compatible with your Hardware issues may arise. To correct the error, you will have to download the driver again by following these steps.

• Right-click on your PC Start button and open Device Manager

• Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver

• For driver software click My computer

• From My computer select 'Let me pick from a list of drivers available'

• Choose an older version from the list then click Next

• The driver you selected will be installed automatically
• Once it has been downloaded reconnect the driver to see if it works.

2# Fix Prolific USB to Serial Driver 'Coder 10'

Driver issues reveal themselves in so many ways or through messages such as

• This device will not start (Code 10)
• There is no driver installed in this device
• The driver was not successfully installed

A code 10 error may arise because the chip you are using is not an original one. If you are using a fake, the manufacturer has a way of disabling it due to copy write infringement and the copy write takes effect once you download a recent update. To protect your PC from getting this code, you will have to make sure that your Windows 10 never updates a driver without approval. Updates come in the form of 64 bit and 32-bit drivers. Below we will show you how to work your way around the problem.

Window 64 bit Fix

To fix Windows 64 bit OS including Prolific USB to Serial Adapter, follow through these steps.

• Download 'PL2303_64bit_Installer.exe and Save
• Remove every USB to Serial adapter from your PC and double click the 'PL2303_64bit_installer.exe
• Follow the prompt by plugging in one USB to Serial adapter the click on Continue
• Reboot your PC to get Windows up and running

If you have followed these process through and you still see the same error go to your device manager

• Open the control panel and navigate to Device Manager
• From your control panel navigate to the System category and click the Hardware tab
• Scroll to the LPT/COM port and double click Prolific USB to Serial Comm Port
• Click Drivers in the Properties section
• The Driver you choose should read '3.3.2.102 with an appropriate date attached
• If the date is wrong then it means the wrong driver was installed
• Unplug the Serial adapter and run the steps again to install the correct driver

Window 32-bit

For Windows 32-bit OS systems follow these steps

• You will have to download the 'PL-2303_Driver_Installer.exe and save from Microsoft download link
• Run the program and eradicate the driver if you can
• Run the installer once more to install a correct driver

To Troubleshoot for error if your device still does not work

• Go to Control panel, enter System to access your Device Manager
• Scroll down to the LPT/ COM port then double click Prolific USB to Serial Comm Port
• Click Driver in the Windows Properties section
• The driver must be numbered as '2.0.2.8' and dates accordingly

If the driver was not installed, remove the Serial adapter then run 'PL2303_Driver_Installer.exe' again. Follow directions in Device Manager to download the correct driver

The three solutions listed in this article have proven to be quite helpful in fixing a Prolific USB to Serial driver not working on Windows 10. They may appear confusing at first but if you follow each step in detail you can resolve the issue.

Video Tutorial on How to Fix USB Device Not Recognized

USB Solution

Recover USB Drive

Format USB Drive

Fix/Repair USB Drive

Know USB Drive

Erdos Port Devices Driver Ed

Erfos Port Devices Driver

Comments

• The AVR chip normally has fuses set to prevent overwriting the bootloader. So I wonder if you really managed to overwrite the bootloader or just having problems to rewrite firmware. I also got the timeout warning sometimes with healthy bootloader. So I would power of the rumba and repower it and upload new firmware.
  If we assume you managed to destroy bootloader somehow, I know it can be written with a ISP or other arduino used as ISP (https://www.arduino.cc/en/tutorial/arduinoISP) - is that what you try to do? Then make sure to use the right ISP connector on rumba board. There are 2 - one for serial usb driver and one for the firmware. You need the one next to motor driver like shown here: https://reprap.org/wiki/File:RRD-RUMBA_ISP_2560.JPG with that you can repair any bootloader.
• I tried many times to power off/on and install firmware from arduino environment. At Rumba Board, just the Tx LED is flashing one per 10 seconds, also LCD Display shows nothing. Therefore I think, the bootloader is damaged, firmware doesn't start.

  In arduino doku I mostly find to use windows and flip software, but I was not successful like described above.

  So the only chance I see ist either an arduino as ISP
  

  As far as I understand (https://reprap.org/wiki/RUMBA) now I have to burn

  - ATmega16u2 Firmware using the JTAG connector and an extra programmer

  - and then hopefully being able to transfer the repetier firmware to the board using USB
  

  On the other hand thinking of all the time diging for informations.. I'm close to buy a new board.
  

  
  
• First you can burn both with ISP connector. And the ATmega16u2 chip has no bootloader so you can not have deleted it with the upload. So if you never used the ISP port for your tests it should still be in tact. If you see the com port in windows it is in tact. So all you need is flash the mega2560. You can also buy a cheap for this like this one: https://smile.amazon.de/dp/B07DLZPV7Q/ref=psdc_1626220031_t1_B00LUJYI26 less then 13 euro and much cheaper then a rumba board. And you are prepared if anything goes wrong in future.
• Thank you for being active also on easter sunday!
  

  I'll follow your recommendations and will report afterwards.

  Regarding the firmware update feature of repetier server something went wrong.
  Since I want to understand what has happened:

  compiled V1.0.3 with some modifications and exported it.

  Two files were generated, one without, one with bootloader.

  Then, in the servers Website I called firmware update and selected to hex file with bootloader.

  In the dialog there were some messages (which I dont remember), then many many stk500 timeout messages, every 10 econds.

  What could have gone wrong in my opinion?

  The arduino environment does not know about the connected rumba board. It only knows arduino mega 2560.

  Therefore the created bootloader may not compatible to the rumba board.
  

  If everything is back working, I#ll try firmware update using the non-bootloader file. This should be less dangerous.

  Wish you'll find more easter eggs today than easter bugs!
• I can not really say what happened. What the uploader does is calling calling avrdude with same parameter arduino ide calls for the non bootloader upload. It might be that the files contain target address (bootloader is at end of memory I think while Program goes to start). But if you write to bootloader memory that would change the software running at same address which will crash maybe the bootloader. Not 100% sure since I did not write it. But then you have a problem like you described. But also the fuses were then set wrong I guess since bootloader should be protected to prevent overwriting. With an ISP it is possible to change these fuses. That is how you upload the bootloader - also ISP does not need bootloader to upload.
• Now my printer is back, a damaged bootloader of atmega2560 was the problem.
  Thanks for your help, Repetier!
  But all I tried without success and the way it worked for me might be interesting for others:
  What I didn't get to work:
  1) following https://reprap.org/wiki/RUMBA#ATmega_2560_STK500v2.2FArduino2560_Bootloader
  entering the DFU mode seemed to work, Tx/Rx flashed shortly.
  Didn't find any way to install the Atmel flip driver atmel_usb_dfu.inf in Win10 because of missing certificate
  2) setup a WinXP system in virtual box
  driver was not accepted (other reason, not because of certificate)
  3) setup a Win7 system in virtual box
  driver was accepted (devie manager showed Atmel USB Devices / ATMega16U2
  as other reason, not because of certificate)
  Flip acceptet to select USB for communication. Clicking on open: could not open device
  4) Hardware programmer Erfos AVR-ISP in Arduino IDE
  6 pin cable was not included, made one
  USB device was recognized in Win10
  Arduino IDE: Selected AVR-ISP,
  Main Errors stk500_getsync() attempt 1 of 10: not in sync: resp=0x03
  avrdude: stk500_recv(): programmer is not responding
  5) Hardware programmer Arduino as ISP
  Arduino IDE
  Cabeling like several manuals
  Selected Arduino as ISP as Programmer
  Main error message: avrdude.exe: Device signature = 0x000000 (retrying)
  6) Hardware programmer Diamax AVR USB Stick
  like above
  7) installed Atmel studio
  all selection boxs in device programming were emtpty.
  didn't want to read through manuals
  What worked finally for me (I'm a greenhorn in bootloaders, so there could be just small steps to make other options work - or not work):
  hardware programmer 'DIAMEX USB ISP-Programmer Stick für AVR'
  searched for another programming software, found bitburner
  Settings: no changes
  Tab AVRDude
  - AVR Device: ATMEGA2560 (m2560)
  - Programmer: Atmel AVR ISP V2 (avrispV2)
  - COM7 (found in device manager)
  - AVRDude Arguments: <empty>
  Tab AVR Memories
  - Flash: <Bootloader-hex-File from reprap link (see above)
  - EEPROM: grayed out
  - Memory Programmer: Flash only
  - Button write --> it wrote and said success!!
  AVR Fuses
  - Set fuse bytes like shown in Reprap Link
  - Low Fuse, Value 0xFF
  - High Fuse, Value 0x10
  - Extended Fuse, Value 0xFD
  - Write
  Power Off/On Board
  Then I was able to write Repetier Firmware usind the arduino IDE.
  One more information:
  The Bootloader hex file from reprap-Link is not identical to the bootloader,
  which is ceated by arduino IDE when ATmega 2560 is set, and you export the compiled binary file.
  The reprap linked bootloader is part of the arduino V1.8.3, named Mega2560-prod-firmware-2011-06-29.hex,
  but this file seems to be not used (not found in boards.txt).
  Hope this helps somebody else!