Tag Archive for FTDI

New USB PID for CANUSB

We have decided after some long testing to stop using our own PID with CANUSB which was FFA8 and instead use standard FTDI 6001. The main reason for this is that since Windows 8.X (and Windows 10) it will not support unsigned drivers. The change will happen on new devices being made from February 2015, but it could be that our distributors have the “old” configuration for some time. Let us Point out that there is nothing wrong with using the CANUSB with either PID and you as a user will not notice any mayor difference from a program point of view, it will only show in Device Manager if you look there. The FFA8 configuration will show up as “Lawicel CANUSB” and the 6001 will show up as standard “USB Serial Converter”. The big advatage of this is that we do not need to alter the standard FTDI USB drivers and get them unsigned, it means you can use the standard off shelf FTDI USB drivers and in many cases when you have an internet connection the Windows will detect, download and install drivers it self, if it dowsn’t you can download them here from FTDI. Also using MacOS or Linux it should be easier to install drivers.

CANUSB Old versus New

The CANUSB software that you have done or any commercial software that you use as well as our CANUSB DLL do not check for the PID, so there is no difference in behaviour. We believe this is the right choice. If you for some reason do not want this, you can reprogram the standard PID 6001 to the old FFA8 or if you have an old CANUSB and want to update it, simply download the “FT Prog” software from FTDI and change it.

In order to keep track of this (for support issues) we have made a change in the serial number sticker (the yellow label on the CANUSB) and put a plus sign in front of the serial number, see the red ring on the Picture above to the right, this indicates that the CANUSB has been programmed with the PID 6001.

FT Prog

If you want to change the PID, download the “FT Prog” here from FTDI, install and run it (do this on a computer where CANUSB worked with PID FFA8, not on a PC with Windows 8.X or Windows 10). While having the CANUSB attached to an USB port, press the “Scan and Parse” icon to read in the data from the EEPROM of the CANUSB. Then select “USB Device Descriptor” as the picture above shows. In the picture above it shows the old Lawicel CANUSB PID FFA8, to change it to the new, simply select the value “FTDI Default” from the property “Custom VID/PID” drop down box. After this is done puch the flash icon from the menu and program it, now it will use the standard PID 6001 instead (after you removed it and installed drivers again). Of course a new CANUSB can also be reprogrammed to the old “FFA8 Custom PID”. DO NOT ALTER ANY OTHER CONFIGURATION!

New FTDI USB driver available

New FTDI USB driver package, version 2.08.30 CDM is added here.

CANUSB and Windows 8/8.1

This post has been updated in march 2015 and is only valid for CANUSB using our own PID FFA8, if you have a newer CANUSB (we started to ship out them in February 2015) we changed PID to standard FTDI 6001 so off the shelf signed FTDI drivers could be used instead of our modified for our PID. Please read this post for more information on newer CANUSB with PID 6001 and how to verify which you have.

Below is original post from January 28th 2013. Read and use only if you have a CANUSB with PID FFA8.

We have now tested CANUSB together with Windows 8 (and later versions) and there are some things to think of when you use Windows 8. Our test PC is using Windows 8.1 Pro on 64bit but it will be same on all versions. We have updated this post with some new information as well, see bottom of this post.

Due to the requirement in Windows 8 (and later versions), that all drivers need to be signed, the FTDI driver for CANUSB will not be installed unless you change some settings in Windows 8. Please also note that in the writing of this the FTDI drivers are not approved for Windows 8 according to their web. But even if FTDI drivers later will be approved and signed for Windows 8, we need to unpack them and edit info for our CANUSB (add info for PID=0xFFA8), then pack them again and put here for download, this means they will be unsiged again. We will not send off drivers to be signed at Microsoft each time FTDI releases a new driver, it will be a costy procedure for us. This was not a problem in Windows 7, where unsigned drivers could be installed if you just said yes to the question you got, but in Windows 8 it is diffrent.

The instructions here is at your own risk, but it is easy to make Windows 8 to accept non signed drivers. You can force Windows 8 by doing the following below.

We have found this post to be the best on how to install unsigned drivers in Windows 8, so try this first before doing anything below!

How to install unsigned drivers in Windows 8.

If the above doesn’t work here are some other help:

Open a Command Promt (cmd) as Administrator and type the following 2 commands:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

With bcdedit you are configuring the boot menu of Windows, so be careful. If something goes wrong wou will need a Windows DVD to repair the bootmanager.

After a restart you can go to device manager and choose to update the FTDI driver by right clicking on CANUSB and choose to update driver, point to where you downloaded the driver and all is OK.

When FTDI USB driver is installed you can turn off this again by starting the Command Promt (cmd) as Administrator and type the following 2 commands:

bcdedit -deletevalue loadoptions
bcdedit -deletevalue TESTSIGNING

And you are back to the default values after you have restarted Windows 8. This two procedures only apply to the FTDI USB driver, our own CANUSB DLL driver do not need to be signed, it is only drivers related to hardware.

Unsure how to run cmd as an Administrator, check this post. It is not as easy as just log in as an Administrator, you need to start it as well with Administrator privileges.

There are also other ways todo this since we originally wrote this post, if you follow this links and/or this link for some valuable information on how to install unsigned drivers in Windows 8 (and later versions). You might even before you do the above on some new PC’s click the “Clear Security Bits” in the BIOS.

New FTDI USB driver available

New FTDI USB 2.08.24 CDM driver package added here.

New FTDI USB driver available

New FTDI USB 2.08.14 CDM driver package added here.

New FTDI USB driver available

New FTDI USB 2.08.02 CDM driver package added here.

New FTDI USB driver available

New FTDI USB 2.06.00 CDM driver package added here.

New hardware revision of CANUSB

We have revised the CANUSB hardware (from serialnumber W700) to use the FT245RL instead of the FT245BL, this makes the CANUSB approved for industrial usage -40C to +85C. The driver is the same and no other changes has to be made at the user level.

New FTDI USB driver available

After FTDI released new CDM drivers in May 2008, we have now tested them with great success and have made updated zip package to include support to our CANUSB in them (since we have our own PID, the FTDI drivers found at FTDI’s webpage can’t be used directly. You find the new drivers and istallation instructions in the Downloads section.

New FTDI USB driver available

Long time since any news, mostly beacuse the drivers work good. However we are now using the new USB drivers from FTDI (CDM – Combined Driver Model). With this new driver you can use the D2XX and the VCP from same installation file and they can co-excist on the same PC at the same time, though not be used at the same time. You find the new drivers and istallation instructions in the Downloads section.

We plan soon to release a new CANUSB driver DLL (it’s being BETA tested by some users) which have many new functions and extended samples. We plan to release this in November.