similar to: Wine + winebottler + azloader.exe + rs232 to usb, adapter

Hello guys. I am new in mac world and in wine apps. I have this singular situation: I have a macbook with wine and winebottler installed. I want to use this exe app: azloader.exe. Ok, wine is able to load it normally. But... the problem is, my macbook has not the RS-232 port. So I bought a RS-232 to USB adapter. I've installed the correct "drive" to use that. I've tried that in

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

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

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

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

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

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

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.

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)

Hello, CentOS 6.2. I have spent all morning googling and trying different things to get the permissions on my ttyUSB0 port set correctly using udev. I am at my wits end. Why is this so convoluted!? I would really appreciate it if someone could tell me how to do this. The default permissions come up 660 root,dialout. I have tried adding myself to group dialout but still get permission denied

Hello all and thanks. I read here <https://mn3m.info/posts/configure-ups-monitor-using-nut-on-debian/> while searching around for my issue's resolution. In this I see that this nut driver is creating and using an entry in /dev (in this case ttyS0). So I "ll tty*" and see nothing with nut. Since this is a USB UPS, I suppose I should be looking for something in /dev/ttyUSB*.

Can someone please help me with writing a udev rule? I need /dev/ttyUSB0 to automatically have 777 rights when plugged in. I'd like it to only apply to that one specific device. I'm not sure where to start, what files to look at and also what to write to make it work. TIA Brad This e-mail transmission contains information that is confidential and may be privileged. It is intended only

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

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

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, I have an OEM of KStar UDC9101S which is Megatec protocol rs232 capable unit. So I use blazer_ser protocol=megatec /dev/ttyUSB0 with no issue to get NUT running. Please direct me what command should I issue to collect the data in order to include the UPS to device database? P.S. tryed /lib/nut/blazer_ser -DD... but no difference from a regular output has being added by the driver.

Hi All I am connecting a ups via a usb to serial converter. Works fine, however when the converter is unplugged and plugged back in, udev creates another device e.g instead of ttyUSB0 it creates ttyUSB1. Here is the udev rule that I added to the top of the 025_nut-usbups.rules file in order to create a static symlink should udev decide to create the device as either ttyUSB0 or ttyUSB1.

I am far from expert on these matters. But have a couple questions: 1. Are you sure that /dev/ttyUSB0 exists and is the result of the Prolific USB->serial converter? For example, if you yank the Prolific and reboot, is /ttyUSB0 there still? It is possible that there is another /dev/ttyUSBx out there.I doubt this but wonder. 2. I have recently been fuddled due to permission problems of

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

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]