similar to: [HCL] Artronic art 1000 bl supported by blazer_ser

On Feb 10, 2015, at 5:24 PM, Miroslav Todorov <miro0218 at yahoo.com> wrote: > Hi Artronic art 1000 bl is supported partially by blazer_ser: > When you say "partially supported", what is not supported? Are any of the values incorrect? -- Charles Lepple clepple at gmail

Dear Daniele, i understand perfectly, i'd like to explain you why we choosed to clone the blazer_usb driver: some of our devices uses Voltronic Q1 protocol and we tried the Krauler Subdriver (it was the one with the right "commands", Q1, F, etc.), but the issues were 2: - first: the Krauler Subdriver expects a different number of bytes in answer because in debug i see "Short

Dear Mr Claesson, prepare for quite a long letter from me. I hope you will have time to read it. I bestowed a whole morning on trying to identify the correct upstype. Here are the results: root@marto:/home/marto# /usr/local/ups/bin/powercom -DD -u root -a Inform -x type=KP625AP Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) debug level is '2'

Hello list, we've got a PowerWalker VI 1000E/RT LCD UPS and like to use it with NUT using the blazer_ser driver. For the blazer_ser driver to display percentage, one has to add battery.voltage.high and battery.voltage.low voltages to the ups config. Here's what I received from the powerwalker customer service: Battery-Low Voltage: 21.6VDC Battery Shutdown: 19.2VDC Now my questions: 1.

Hi, I'm trying to get an Effekta UPS (works directly with blazer_ser) working behind a seriell to ethernet converter (Brainboxes ES-246). I've set the converter to 2400 baud, 8N1, no flow control. On the linux side I started socat and blazer_ser. All I got are timeouts after 12 seconds. I can see network traffic with tcpdump but I've no idea what to do to get this working. Does

Hi, today I have tested the Zinto 800 with blazer_ser and blazer_usb on Citrix Server 7.0. Both works fine. upsc-Output (blazer_ser): battery.charge: 94 battery.voltage: 25.70 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal: 24.0 device.mfr: device.model: ZINTO 800 device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port:

On 2014-06-03 00:58, Charles Lepple wrote: >> I'm pretty sure I wouldn't rely on a charge percentage derived this way ;-) It's nice to see how much time one has left, event if it's not perfectly accurate. >> As mentioned in the other thread about the tripplite_usb driver, apart from having two sets of calibration constants, one for OL and one for OB, there is no

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

Hi, I tried using 2.6.1 version for windows with a Megatec-compatible UPS and was surprised to find out it doesn't work at all. The reason for that is blazer_ser using ser_get_buf specifying a buffer large enough to accept any reasonably possible response, setting buflen accordingly. That calls select_read() and it's supposed to wait until something is available and then to read up all

On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more

On Jun 2, 2014, at 6:48 PM, Charles Lepple wrote: > On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > >> >> Hi, >> >> thanks for the reply. >> >> On 2014-05-29 05:21, Charles Lepple wrote: >>>> Now my questions: >>>> 1. should the blazer_ser's high voltage be the voltage during charging >>>> or right

On Fri, Apr 15, 2016 at 11:22 AM, Pierre Moreau <pierre.morrow at free.fr> wrote: > On 11:06 AM - Apr 15 2016, Ilia Mirkin wrote: >> On Fri, Apr 15, 2016 at 10:57 AM, Pierre Moreau <pierre.morrow at free.fr> wrote: >> > Currently, every backlight interface created by Nouveau uses the same name, >> > nv_backlight. This leads to a sysfs warning as it tries to

The Apple GMUX is the one managing the backlight, so there is no need for Nouveau to register its own backlight interface. v2: Do not split information message on two lines as it prevents from grepping it, as pointed out by Hans de Goede Signed-off-by: Pierre Moreau <pierre.morrow at free.fr> --- drm/nouveau/nouveau_backlight.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git

fixes d9c0aadc5aa241df26ce8301d34a8418919fb5ae Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nouveau_backlight.c | 7 +++++++ drm/nouveau/nv50_display.c | 4 ++-- drm/nouveau/nv50_display.h | 4 ++++ 3 files changed, 13 insertions(+), 2 deletions(-) diff --git a/drm/nouveau/nouveau_backlight.c b/drm/nouveau/nouveau_backlight.c index 380f3402..057708da

My bad; I did test suspend/resume, but not unbinding. Shouldn’t that happen on shutdown as well, as the driver gets unloaded? I don’t remember seeing that issue there though. On 2018-02-17 — 13:40, Lukas Wunner wrote: > Unbinding nouveau on a dual GPU MacBook Pro oopses because we iterate > over the bl_connectors list in nouveau_backlight_exit() but skipped > initializing it in

On Mon, Feb 19, 2018 at 10:38:04AM +0100, Pierre Moreau wrote: > My bad; I did test suspend/resume, but not unbinding. Shouldn???t that > happen on shutdown as well, as the driver gets unloaded? I don???t remember > seeing that issue there though. Sorry Pierre, I missed this question and am seeing it only now on saving the message away: On shutdown the driver isn't unloaded, rather

My appologies, this estimation is about right, I spent last week at COMPSTAT in prague and didn't follow the list closely. Inspite of this fact I believe my posting is not entirely out of date. regards Diman Todorov ------------------------------ You are 8 days behind the times -- take a look at the current R-devel. On Sun, 29 Aug 2004, Diman Todorov wrote: > Dear Dirk, > I

On Mon, Feb 19, 2018 at 10:38:04AM +0100, Pierre Moreau wrote: > On 2018-02-17 13:40, Lukas Wunner wrote: > > Unbinding nouveau on a dual GPU MacBook Pro oopses because we iterate > > over the bl_connectors list in nouveau_backlight_exit() but skipped > > initializing it in nouveau_backlight_init(). > > --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c > > +++

On Fri, Apr 15, 2016 at 10:57 AM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Currently, every backlight interface created by Nouveau uses the same name, > nv_backlight. This leads to a sysfs warning as it tries to create an already > existing folder. This patch adds a incremented number to the name, but keeps > the initial name as nv_backlight, to avoid possibly breaking

Hello. Using the ":include", which generates a "LEFT OUTER JOIN" SQL command, it is possible to eagerly preload second order data objects (children) for a given association. I wanted to know, if it is possible to eagerly preload and cache third order (or more) data objects, which are little-children or little-little-children. As I''ve seen. it is possible to add