search for: ftdi

Hi. I have some problems with USB->Serial FTDI FT232BM chip drivers on FreeBSD 7.0... FreeBSD recognize the USB device, but when I making connection to /dev/cuaU0 or /dev/ttyU0 I cant send & receive any data from device. cu -l/dev/cuaU0 -s9600 - No response at all, can't even quit the program cu -l/dev/ttyU0 -s9600 - Sometimes working,...

I have a AIS Receiver which requires a ftdi chip driver(which I have) but I am stumped as to how I may get wine to load and see it. I need to run ShipPlotter software which seems to sit very nicely in the Wine environment but cannot make contact with the receiver as there is no driver. Any help would be appreciated.

I've got USB->Serial converter: Code: Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC and I need communicate with this converter to devices(Kirk) via specific Kirk windows software. I have mapped converter: Code: ln -s /dev/ttyUSB0 com1 but I can't connect to it. If I connect the Kirk device directly through mapped /dev/ttyS0, the device get connected. Any

I am working on a program which links with the FTDI USB driver (ftd2xx.dylib). Prior to a couple of hours ago I had only worked with Debug builds of my code (no compiler optimizations). In testing a production build, I found that using anything other than -O0 results in the FTDI driver returning bad data; just a lot of zeroes. I tested and re-tested...

...l signals, and they probably will NOT work with a > > USB port because they require very specific behavior from those signals at > > power up and reboot times. > > I've used various serial devices, including UPSes, via various > USB-to-serial adapters (Prolific PL2303 and FTDI FT2232C), and all the > signaling works fine. Only issue you sometimes have is that there are > many cheap adapters on Amazon that claim to be Prolific or FTDI but are > in fact counterfeit clones - those may or may not work reliably for ANY > purpose. > Another possibility for th...

On Wed, Jul 8, 2020 at 8:46 AM H <agents at meddatainc.com> wrote: > > I believe I mentioned that the UPS has the serial port, the computer thus > has USB. > > yes, but is it 'basic serial UPS' or is it 'enhanced serial UPS' ? the former do NOT use the rx/tx data of the serial port at all, they ONLY use the serial port control signals, and they probably

Hi Charles! Thanks a lot for your response. Now I figure why the isbmex driver was not working. On the other hand I've tried to run the command suggested. But no success. I got this information when running the dmesg command after running the modprobe $ sudo modprobe ftdi_sio vendor=0x0483 product=0x0035 [35816.111760] usbcore: registered new interface driver usbserial [35816.111792] usbcore: registered new interface driver usbserial_generic [35816.111814] usbserial: USB Serial support registered for generic [35816.136413] usbcore: registered new interface driver f...

...39;2' > > Unable to open auto: No such file or directory The problem is that the "isbmex" driver was written for a serial-only UPS, and I don't think we have any information on the USB protocol. However, the manufacturer's driver package indicates that this might be a FTDI serial converter. Please try the following: $ sudo modprobe ftdi_sio vendor=0x0483 product=0x0035 and see if you get a new /dev/ttyUSB* device node. -- Charles Lepple clepple at gmail

...do an update soon -- non-trivial since my Internet connection is via dialup). I recently bought a couple of Adafruit Arduino compatibles, a Flora and a Metro 328. Hooking up the Flora and the Metro to a Raspberry Pi running Raspbian (kernel 4.9.35-v7+), tells me that the Metro 328's USB uses a FTDI USB serial interface (ftdi_sio.ko) and the Flora uses the cdc_acm (cdc-acm.ko) USB serial interface. Both of these drivers are available with CentOS 6's kernel, but since Adafruit uses their own Vendor & Product IDs and my (old) kernel's ftdi_sio and cdc-acm drivers don't have Adafr...

...1-0000:00:05.7-4|| ||janv. 23 21:26:22 vm-bullseye kernel: usbcore: registered new interface driver usbserial_generic|| ||janv. 23 21:26:22 vm-bullseye kernel: usbserial: USB Serial support registered for generic|| ||janv. 23 21:26:22 vm-bullseye kernel: usbcore: registered new interface driver ftdi_sio|| ||janv. 23 21:26:22 vm-bullseye kernel: usbserial: USB Serial support registered for FTDI USB Serial Device|| ||janv. 23 21:26:22 vm-bullseye kernel: ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected|| ||janv. 23 21:26:22 vm-bullseye kernel: usb 3-2: Detected FT232BM|| ||janv. 23...

I got a UPS Sola Basic but it is not working, I'm providing the details. I hope that someone can help me to get it working. Please let me know if there is some other information that I should provide :) OS name and version Ubuntu 12.04 $ uname -a Linux olimpo 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Exact NUT version, 2.7.1

Hello! At first, i want to run the latest HandBrake (version 0.93) on a Mac with Mac OS 10.4 (Tiger). The problem is, that Handbrake is developed for Mac OS 10.5 (XCode SDK is not compatible to Mac OS 10.4 one). So i decided to try it with wine/darwine. Because wine is better supported on Linux and you can get easier newer version (apt-get), i decided to run HandBrakeCLI.exe on Debian Etch

...t; the serial port control signals, and they probably will NOT work with a > USB port because they require very specific behavior from those signals at > power up and reboot times. I've used various serial devices, including UPSes, via various USB-to-serial adapters (Prolific PL2303 and FTDI FT2232C), and all the signaling works fine. Only issue you sometimes have is that there are many cheap adapters on Amazon that claim to be Prolific or FTDI but are in fact counterfeit clones - those may or may not work reliably for ANY purpose. -- Chris Adams <linux at cmadams.net>

...NOT work with > a > > > USB port because they require very specific behavior from those > signals at > > > power up and reboot times. > > > > I've used various serial devices, including UPSes, via various > > USB-to-serial adapters (Prolific PL2303 and FTDI FT2232C), and all the > > signaling works fine. Only issue you sometimes have is that there are > > many cheap adapters on Amazon that claim to be Prolific or FTDI but are > > in fact counterfeit clones - those may or may not work reliably for ANY > > purpose. > > &gt...

This is a general problem with the low-cost Prolific processor chip and drivers. You should invest in a better USB to Serial adapter (http://www.usconverters.com/index.php?main_page=product_info&cPath=67&products_id=244) with a FTDI chipset. It costs a bit more but its well worth the money. The drivers for the FTDI chipset are well documented and compatible with most devices.

I have just bought an FTDI USB UART New USB device found, idVendor=0403, idProduct=6015 New USB device strings: Mfr=1, Product=2, SerialNumber=3 Product: FT231X USB UART Manufacturer: FTDI However this appears to be slightly too new for the ftdi_sio driver in C6.4; it's not detected. If I force it modpro...

On Mon, Aug 12, 2019 at 10:16:35AM +1000, Jobst Schmalenbach wrote: > On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith (fredex at fcshome.stoneham.ma.us) wrote: > > Hi all! > > > > I'm stuck on something really bizarre that is happening to a product > > I "own" at work. It's a C program, built on CentOS, runs on CentOs or > > RHEL, has been

...erface with a 24V DC UPS from Siemens (full name: Siemens SITOP UPS500S, manufacturer nr 6EP1933-2EC41). As this device is not listed in the compatibility list, I will have to write my own driver. I already found out, that the UPS has a serial-over-USB interface (USB full-speed, 12 MBps), using an FTDI chip. Over this serial port, it will periodically spit out some 5-character plaintext strings (every 75 msec): BUFRD - battery ok, UPS functionality available ALARM - battery critical or bad. When on line: no UPS functionality possible; when on battery: battery level critical, will shut down very s...

Hi Occasionally I get emails from my NUT system saying that one of my UPSes lost power for about a minute. Losing power: Date: 15. nov 2010 17.40.25 CET regaining power: Date: 15. nov 2010 17.41.34 CET 69 seconds later. But why? None of the 3 other UPSes reports any power loss. What is the problem? So I made some scripts that logs the input, output and frequency at the time of power loss,

...ocol output usbcore: registered new driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device ftdi_sio 4-2:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB0 usbcore: registered new driver ftdi_sio drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Dr...