Virtual COM Port Drivers This page contains the VCP drivers currently available for FTDI devices. For D2XX Direct drivers, please click. Installation guides are available from the page of the section of this site for selected operating systems. VCP Drivers Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC.

Application software can access the USB device in the same way as it would access a standard COM port. This software is provided by Future Technology Devices International Limited ``as is' and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall future technology devices international limited be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. FTDI drivers may be used only in conjunction with products based on FTDI parts. FTDI drivers may be distributed in any form as long as license information is not modified.

If a custom vendor ID and/or product ID or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHCK re-certification as a result of making these changes. For more detail on FTDI Chip Driver licence terms, please Currently Supported VCP Drivers: Processor Architecture Operating System Release Date x86 (32-bit) x64 (64-bit) PPC ARM MIPSII MIPSIV SH4 Comments Windows. 201 7- 08-30 -WHQL Certified. Includes VCP and D2XX. Available as a Please read the. Linux -All FTDI devices now supported in Ubuntu 11.10, kernel 3.0.0-19 Refer to if you need a custom VCP VID/PID in Linux VCP drivers are integrated into the. Mac OS X 10.3 to 10.8 2012-08-10 -Refer to if you need a custom VCP VID/PID in MAC OS Mac OS X 10.9 and above 201 7-0 5-1 2 -This driver is signed by Apple Windows CE 4.2-5.2.

2012-01-0 6 -Windows CE 6.0/7.0 2016-11-03 -For use of the CAT files supplied for ARM and x86 builds refer to Windows CE 2013 2015-03-06 VCP Driver Support for WinCE2013.Includes the following version of of the Windows operating system: Windows 7, Windows Server 2008 R2 and Windows 8, 8.1, Windows server 2012 R2, Windows Server 2016 and Windows 10. Also, as Windows 8 RT is a closed system not allowing for 3rd party driver installation our Windows 8 driver will not support this variant of the OS. You must use the build for this platform.includes the following versions of Windows CE 4.2-5.2 based operating systems: Windows Mobile 2003, Windows Mobile 2003 SE, Windows Mobile 5, Windows Mobile 6, Windows Mobile 6.1,Windows Mobile 6.5 No Longer Supported: Processor Architecture Operating System Release Date x86 (32-bit) x64 (64-bit) PPC ARM MIPSII MIPSIV SH4 Comments Previous Windows Release 2017-03-10 WHQL Certified. Includes VCP and D2XX. Available as a Please read the. Windows XP, Vista, Server 2003, Server 2008 2012-04-13 -WHQL Certified Also available as a This is FTDI's final release before Microsoft stopped certifying drivers for these versions of Windows. Windows 2000 2009-10-22 -WHQL Certified Available as Windows 98/ME 2004-11-25 -Does not support FT2232 or FT4232 devices Windows 98/ME 2004-03-12 -Only supports FT2232D devices Mac OS 9 Mac OS 8 2004-05-18 -Mac OS X 10.9 and above 20 15-0 4-15.

. Windows USB Driver Installation require the when first used with Windows.

This usually happens when you first connect your BitScope. However you may need to install the driver if:. Your PC is not connected to the Internet,. You are using Windows XP or Vista ( not recommended!),. You are using Windows 7 Starter or Home Edition,. The automated windows installer fails for some other reason. You may then need to configure the software to.

To optimize performance in Windows we recommend. For more information about all this, read below or click through these links:. which is the usual case for most people. if automatic installation did not work for you!. by Windows when you installed the driver?. if it's not already automatically selected. if Windows prevents you accessing devices.

to improve your BitScope performance. if your BitScope still cannot not connect to your PC. Of course, email us anytime at if you need assistance! Automatic Driver Installation In most cases, there is nothing to do, just plug in the BitScope. The following pop-up should appear at the bottom right of the desktop. Its appearance may differ a little depending on the edition and version of Windows 7 or 8 you are using (The remainder of this tutorial uses Windows 7) To observe progress click the pop-up dialog to reveal: When the installation completes you will see: Take note of the COM Port identifier ( COM3 in this example) as you may need it later. Manual Driver Installation If the failed you may see this: In this case you will need to UNPLUG YOUR BITSCOPE and: and when complete, run it: You will be asked to extract it: and then install it: which may take some time to complete: When the installation is complete you may see this dialog: Take note of the COM Port identifier ( COM3 in this example) as you may need it later.

Which COM Port was assigned? Sometimes it's necessary to learn the device properties for a USB BitScope. The most common reason is to see the COM Port number Windows has assigned when the driver was installed (if you forgot to take note of it at the time). Select Devices and Printers: Find the BitScope (it should be listed) and select properties: and then select the Hardware Tab: Here you can see the COM Port number (COM3 in this example). Choosing the COM Port If only one USB BitScope is connected choosing the COM Port is unecessary All automatically connect with that one BitScope.

However, if more than one BitScope is connected or there are other FTDI COM Port devices connected to your PC (e.g. A serial mouse), you may need to configure the software to. This can be done with most BitScope Apps. With DSO click SETUP: and choose the correct COM Port (COM3 in this example) and Click OK: Doing this with one BitScope Application sets the port used for all applications so you won't need to do this again. In the case of DSO, click POWER to start the application: Note that COM3 is reported at the bottom of the application.

But Factorio, the factory building strategy game, is a different story. In Factorio, you land on an alien planet and have to build and maintain factories to survive and fight off alien enemies. You’ll have to mine resources, research technologies, build infrastructure, and automate production.

If the selected COM Port does not appear here, you are not connected to your BitScope. Window Device Manager Windows may when trying to view the COM port or adjust the device properties. In this case you may need to use Device Manager to access the device properties. First select the Computer Properties: and then choose the Device Manager: From the Device Manager, find the USB Serial Port: (which is COM3 in this example) and right-click to open the device properties: Reducing Device Latency BitScope prefers the shortest USB latency to achieve the highest performance. Unfortunately Windows 7 & 8 install the driver with a long latency by default. Reduce the latency value to significantly improve performance when talking to a USB BitScope with Windows 7 or 8. After, select the and then choose the properties for the COM port assigned to your BitScope (COM3 in this example): Select the Port Settings tab and click Advanced: At this point you may be told: If so, you will need to access the Port Settings tab via the instead (this is due to a bug in many editions of Windows 7 and 8).

Whether you've used Device Manager or this route you should then see: Change the default latency ( 16 ms) to 1 ms: Click OK to accept the new value. You may then need to restart Windows for the new value to take effect. Troubleshooting USB Connections If you have but still you cannot connect:.

Be sure to download and use the of BitScope Software. Temporarily disconnect any other USB Serial devices from your PC.

Check which Windows assigned when you installed the driver. Be sure to via the BitScope Software setup dialog. Check your BitScope is powered on (the red LED on the back should be lit). Confirm your power supply is good (for externally powered BitScope models).

Ft245r Drivers For Mac Download

Try connecting directly your PC's USB port if you're using a USB Hub. Connect via a different USB port possibly using a different USB cable. Try a different PC and/or to rule out PC based problems. If you can connect but there are still problems:. If reports OFFLINE. If reports SYDNEY.

Ft245r Drivers For Macbook Pro

If your BitScope seems to be slow to respond. If it's slow to connect. If you still have problems, especially if you are upgrading from older software versions, the configuration files used by the application software may have been corrupted. The file most likely to cause problems (if corrupt) is the probe file. The Local Probe File On Windows 7 & 8 the local probe file is located at: C: Users AppData Local BitScope BitScope.prb or on older versions of Windows: C: Documents and Settings Local Settings Application Data BitScope BitScope.prb where is your logged in user name on your PC. Delete this file to force the software to recreate it with correct information.

Ft245r Drivers For Mac Free

The Global Probe File There is another globally configurable probe file. This is unlikely to be corrupt but if you suspect it is, and you have adminstrator privileges on your PC to modify it, you can delete (or comment out) its contents (don't delete the file itself). It is highly unlikely you will need to do this but we mention it here as a last resort. None of this works for you? Email us at for assistance!