similar to: FTDI USB->Serial a Wine

hello everyone, I've been testing the NUT solution as opposed to the undocumented LanSafe application to control my Eaton UPS. I am on a Slackware 13.37 system with a 2.6.37.6 kernel. NUT version is 2.4.3 . I installed the tarball by compiling it directly on my system (as a slackbuild package). The UPS is an Eaton Powerware 9155, but I don't know how to obtain the manufacturing date. The

Dear friends, I installed NUT and followed all suggested procedures to verify if my ups is supported. No driver recognized my ups, and the genericups tests get wrong. Here I send some informations about it: The ups model is APC BZ1200-BR I use Ubuntu, and the lsusb results Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC for ups. The

Wine does great job for GUI on screen (PC Oscilloscope) But, can't USB connect to external hardware device that has FTDI 245AM chip in it. See device in /dev/ttyUSB0. See device in lsusb, also in lsmod. Did normal linking, ln -s /dev/ttyUSB0 /.wine/dosdevices/com3. No luck. See the link with: ls -al of dosdevices. Using COM3 because in Windows registry in Wine, it says COMPORT=3 Any help?

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.

OK, I am running CentOS 6 on my Laptop and Desktop, presently kernel version 2.6.32-696.20.1.el6.x86_64 (yes, a version or so out of date -- I'll probably 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

doctordruidphd wrote: > I am trying to use software to program a scanner radio (BCD396t and UASD software). The software installs and seems to run properly, reading and writing database files. But I cannot connect to the scanner, through a USB-to-serial cable. > OS: ubuntu-8.10, kubuntu-8.10, debian/lenny (tried them all) > > lsusb identifies the cable as follows: > Bus 002 Device

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this:

Hello, I have an application that sends data out to a serial port, then should receive the reply. After some hassles I got the application to enumerate the serials (in a dialog box where you select the port), and after creating the link in dosdevices (in lower case I should note, wine will not recognize COM1) it actually starts sending out data (verified using a terminal on the other end). But

I have not yet found a USB-to-serial adapter detected as /dev/ttyACM1. Try /dev/ttyUSB0 ? - Mike On Sat, Feb 13, 2016 at 10:14 AM, Robert Heller <heller at deepsoft.com> wrote: > I sent this out about a week or so ago, but I have heard nothing. I am > *thinking* it is a SELINUX problem, but I cannot figure out what. The > SELINUX > settings for both machines are *exactly* the

I am trying to use software to program a scanner radio (BCD396t and UASD software). The software installs and seems to run properly, reading and writing database files. But I cannot connect to the scanner, through a USB-to-serial cable. OS: ubuntu-8.10, kubuntu-8.10, debian/lenny (tried them all) lsusb identifies the cable as follows: Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc.

Yes I do have Linux. I have assigned the ups.conf file as seen below.. [testups] Driver = usbhid-ups Port = /dev/ttyUSB0 When I try to start the ups driver I get the following error... $ sudo upsdrvctl start Network Ups Tools - UPS driver controller 2.7.1 Network Ups Tools - Generic HID driver 0.38 (2.7.1) USB communication driver 0.32 No matching HID UPS found Driver failed to start (exit

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

I have Garmin Mapsource v8 working 100% with Wine and Linux kernel 2.6.16. Transfer from/to the GPS connected to a USB Serial converter on /dev/ttyUSB0 works 100% also. But then, I try with kernel 2.6.18 and 2.6.19 and Mapsource doesn't find the GPS. It's not a Linux issue as I can access the GPS with minicom. Device file permisions are OK. Anyone has and idea of what can be happening

Hi, I recently installed a Upsonic PrOffice 650 UPS, which is a cheap model[1] available in Australia. It has a serial and USB port, and comes with a note saying WinPower software can be downloaded from [2]. Investigation of the software shows it to be Java with native libraries for serial and USB. Disassembling various classes reveals it talks at 2400 baud, and has a protocol similar to

Hi I have a serial UPS connected using a serial2USB device. Usually it is port=/dev/ttyUSB0, but occasionally i need port=/dev/ttyUSB1. How do you guys handle something like this? JonB

Anyone have an idea as to how to automatically detect the USB number and create a sym link in the dosdevices directory. The problem is that I have several USB devices not used at the same time, and when the USB to serial adapter is connected, a /dev/ttyUSB? is assigned. To use this assignment under WINE, I need to automatically detect /dev/ttyUSB? and then create a sym link in

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]

I have to reinit a firewall that can only be done from its console port, and I do not have an XP system with Hyperterminal on it. So I went through the archive and learned that minicom could do the job for me. I installed it and went to configure it (minicom -s). I can set the speeds, but the challenge is selecting the serial device. I have a Serial-to-USB dongle, and when I connect it,

Ubuntu creates /dev/ttyUSB0 for me when I plug in the usb-to-serial-adapter. I have a symbolic-link to /dev/ttyUSB0 from 'dosdevices/com1'. What is new in 10.04 Ubuntu is that I have to sudo chmod o+r and sudo chmod o+w on /dev/ttyUSB0 every time before I start the app which uses that serial line. ttyUSB0 goes away when I unplug the serial adapter from the USB port or shut down the

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 modprobe ftdi_sio vendor=0x0403 product=0x6015 then it gets detected as a