similar to: howto handle USB serial port keeps changing

Hi, I'm having trouble getting my Palm to sync with jpilot on my Centos system via USB. When I sync, I get this error in jpilot: pi_accept Illegal seek Exiting with status SYNC_ERROR_PI_ACCEPT Finished I have jpilot syncing fine with this Palm over the network, BTW. For USB, I set things up for udev as described on various websites. Here are the relevant ports & symlink (created

I've looked up the Kpilot manual, and I think I have an okay idea of what's going on with it. I'm trying to get it's detection feature to find my Palm Pilot. CentOS does seem to be able to recognize it, because if I run lsusb when running a hot sync, I get the following: [root at localhost dev]# lsusb Bus 001 Device 010: ID 0830:0060 Palm, Inc. Palm Tungsten T / Zire 71

Hi I'm looking for a tool that records and plots graphs of UPS load over time? Any suggestions? JonB

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

Hi I have a HP R3000 XR UPS which NUT never says is at 100% battery. It seems stuck in 98 or 99 . something percentage. How accurate should i expect the reports to be? All my other UPSes has been and is at 100%, even those i have retired. My monitor system runs debian. The host that is physically connected to this ups runs: nut 2.2.2-6.4 The web script runs nut-cgi 2.0.4-4 JonB

How do you go about configuring comm ports in Wine? I have a usb to serial adapter that is using ttyUSB1 under linux. The program I want to use under wine shows only the standard Windows comm ports; i.e, com1, com2, etc. How can I redirect those to ttyUSB1? dick

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

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

Yes I used. The problem can be the version of Asterisk? I use Asterisk 13 instead of 11. 2016-02-12 14:31 GMT-02:00, Shabbir abbasi <shabbirabbasi92 at gmail.com>: > have changed this > [dongle0] > audio=/dev/ttyUSB1 > data=/dev/ttyUSB2 > > To > > [dongle0] > imei=123456789012345 > > and imei exact same as on your device ? > > On Fri, Feb 12, 2016

Hi! I'm trying to use dongle in my Asterisk But appear for me all time this error [Feb 12 13:49:10] ERROR[13347]: chan_dongle.c:442 do_monitor_phone: [dongle0] timedout while waiting 'OK' in response to 'AT' -- [dongle0] Error initializing Dongle -- [dongle0] Dongle has disconnected -- [dongle0] Trying to connect on /dev/ttyUSB1... -- [dongle0] Dongle has

Yes, I used IMEI. But in CLI appearing nothing and it not register. 2016-02-12 14:27 GMT-02:00, Shabbir abbasi <shabbirabbasi92 at gmail.com>: > have you tried imei discovery > imei=123456789012345 > > > write imei number instaed of 12345... > > On Fri, Feb 12, 2016 at 8:51 PM, Vitor Mazuco <vitor.mazuco at gmail.com> > wrote: > >> Hi! >>

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 am trying to get JPilot working. I have configed gnome-pilot-applet, but it is not talking to the USB connected Treo650. My Treo has my name as the user, so from the applet, I see also a userid (my UID on this system it seems). I try to put that on the Treo and nothing happens. I have enabled the Backup Conduit. I am using /dev/pilot, which shows up when my Treo is connected via its USB

hi NUT 2.4.3 on new server can not see serial number, but old nut on different hardware can? I have 2 USB-hid ups from APC, 1500 and 3000 RM, i use the serial number to identify them. However my new UPS monitor server can not see the serial number? It works on Linux dkserver 2.6.22.18-vs2.2.0.6 #1 SMP Sat Feb 16 20:54:32 CET 2008 i686 GNU/Linux debian package 2.2.2-6.5 it does not work on

Manufacturer: Aviem Power RT 1000-3000VA Description: Rack/Tower Intelligent Online LCD UPS. connected with serial cable. #upsc battery.voltage: 24.96 battery.voltage.low: 21.5 battery.voltage.nominal: 24.0 beeper.status: enabled device.mfr: device.model: device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB1 driver.version: 2.6.3

I tried this [dongle0] ;audio=/dev/ttyUSB1 ; tty port for audio connection; no default value ;data=/dev/ttyUSB2 ; tty port for AT commands; no default value ; or you can omit both audio and data together and use imei=123456789012345 and/or imsi=123456789012345 ; imei and imsi must contain exactly 15 digits ! ; imei/imsi discovery is available on Linux only

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.

On 08/08/2013, at 18.58, Alf H?gemark <alf at i100.no> wrote: > On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: >> On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: >> >>> Hi there, >>> >>> OS: (L)ubuntu 12.04 precise LTS >>> Nut: 2.6.3-1ubuntu1.1 >>> Installation Method: Package (apt-get install nut)

I've a line like this that creates /dev/pilot link in my local udev rules: BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*[13579]", SYMLINK="pilot" And it seems to work fine for doing normal sync operation to Gnome Palm applet (well, not sure about that KERNEL parameter, however ttyUSB0 and ttyUSB1 look exactly the same, no other way to