d2xx

How to use the FTDI D2XX library on OSX?

流过昼夜 提交于 2019-12-12 07:07:30
问题 I'm trying to talk to a an usb device connected to an EasySync USB2-H-5004-M USB to RS485 converter at baud rate 3750000 but on OSX. I've some c++ code working on Windows and have just managed to get it to compile on OSX (using the D2XX dylib instead of the dll) but I have an issue with communication somewhere and I'm not sure where to start and how to resolve this. I'm using openFrameworks/c++ and the method to list devices looks like this: int FTDI::enumerateDevices(){ DWORD numDevs; FT

Why can't I access my FTDI device using D2XX on a Raspberry Pi?

岁酱吖の 提交于 2019-12-08 03:59:52
问题 I'm trying to make use of FTDI's D2XX drivers to access a USB-Serial device on a Raspberry Pi 3. Here's what I've done so far: I downloaded the 1.3.6 ARMv6 hard-float version of the driver (which states that it is suitable for a Raspberry Pi), and then followed the Readme instructions to install it into the /usr/local/lib folder I ran the sudo rmmod ftdi_sio and sudo rmmod usbserial commands as advised to unload the default kernel driver In my program, the first thing I do is invoke the FT

How can I get Linux device with FTDI D2XX driver API

扶醉桌前 提交于 2019-11-30 14:25:19
问题 I am using FTDI D2XX driver API to communicate with a FTDI device. It gives me some information about the device like locid, serialnumber, description but it is not enough. How can I get the device number ( /dev/ttyUSBXX ) or bus or port with this API. thanks 回答1: As the D2XX Programmer's Guide tells in the Introduction: For Linux, Mac OS X (10.4 and later) and Windows CE (4.2 and later) the D2XX driver and VCP driver are mutually exclusive options as only one driver type may be installed at

How can I get Linux device with FTDI D2XX driver API

人盡茶涼 提交于 2019-11-30 10:37:19
I am using FTDI D2XX driver API to communicate with a FTDI device. It gives me some information about the device like locid, serialnumber, description but it is not enough. How can I get the device number ( /dev/ttyUSBXX ) or bus or port with this API. thanks As the D2XX Programmer's Guide tells in the Introduction: For Linux, Mac OS X (10.4 and later) and Windows CE (4.2 and later) the D2XX driver and VCP driver are mutually exclusive options as only one driver type may be installed at a given time for a given device ID. The problem is that your Linux may automatically loads the VCP driver (