similar to: Communicating with a USB device

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]

Hello everyone and best wishes for 2023 :) I have an old *Garmin Drive Smart 50 GPS* and I want to be able to attach it when it is in preboot mode to a VM hosted by a *Debian 11 host*. From what I understand, the preboot mode allows us to flash a firmware before the GPS actually starts (used among other things when the GPS is soft bricked). When I connect the GPS to the host it gives:

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?

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

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

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 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.

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

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

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

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

I am new to Linux, Ubuntu, WIne etc but despite all that I am operating in Ubuntu 8.10, with MapSource 6.13.6 installed via Wine 1.0.1. I know there is an issue in getting MapSource to recognize the GPS while connected via USB but I am unable to understand the steps provided to solve this issue. I've been advised to enter "sudo modprobe garmin_gps" in terminal and to check the

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)

On Feb 26, 2014, at 2:10 AM, Victor Romero wrote: > 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 :) Thank you for providing all of this information! > OS name and version > Ubuntu 12.04 > $ uname -a > Linux

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:

I have been trying to get an EVDO modem to work with Centos 5. I can make it dial out with wvdial only when I'm the root user. Otherwise I get this error: Cannot open /dev/ttyUSB0: Device or resource busy I added the user to the uucp group. crw-rw---- 1 root uucp 188, 0 Dec 3 02:30 /dev/ttyUSB0 crw-rw---- 1 root uucp 188, 1 Dec 3 02:30 /dev/ttyUSB1 crw-rw---- 1 root uucp 188, 2 Dec

>> I setup apcsmart driver on port /dev/ttyUSB0 in ups.conf and check that runing user=root. >> > user=root is only for testing- this may cause other permissions problems later. It looks like the simplest way to handle this on Debian is to add the system 'nut' user to the 'dialout' group: $ sudo adduser nut dialout > I have been meaning to collect some

Hi Having followed this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/and seeing support for Apollo UPSes mentioned on the compatibility list (genericups, type=4) I tried to set up Nut as follows. OS: Ubuntu Server 12.04 Nut: 2.6.3 (I believe - from Ubuntu repos) ups.conf: > [apollo] > driver = genericups > upstype = 4 > port = /dev/ttyUSB0

Thanks for the response. No /dev/ttyUSB0. /dev/tty and /dev/tty1 ... /dev/tty63 /dev/ttyS0 ... /dev/ttyS3 but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 What ought the major number be? On 2016-10-20 07:33, Charles Lepple wrote: > [please use reply-all to include the list - the headers are not > mangled] > >> On Oct 18, 2016, at

[please use the nut-upsuser@ address rather than nut-upsuser-owner@ and be sure to use Reply-All - thanks!] On Dec 23, 2014, at 1:52 PM, Janez Kremzer <janez256 at gmail.com> wrote: > Hi! > > I woud like to use Raspberry Pi with NUT installed whic coud shut down NAS in the office. > NAS doesn't have comport and this is the reasion why not to use NAS directly. > >