similar to: Awfully OT Question.

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

On Sun, 23 Aug 2015 11:09:03 -0400 Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > > > >> Not sure what to look for yet. It might be easier to add in the > >> debug calls to the source code-- can you try building NUT from > >> source? If you installed via the ports tree (as

On Sep 11, 2015, at 8:11 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > > On Thu, 10 Sep 2015 22:31:08 -0400 > Charles Lepple <clepple at gmail.com> wrote: > >> On Sep 9, 2015, at 2:06 PM, Mario Lobo <mlobo at digiart.art.br> wrote: >>> >>> By the constance of header and footer bytes, I think something >>> different is going on

On Tue, 8 Sep 2015 22:25:54 -0400 Charles Lepple <clepple at gmail.com> wrote: > @rpvelloso on Github suggested some changes (driver version v0.64) > that should help with the initial sync: > > https://github.com/networkupstools/nut/commit/debc8e0280ea4de9a0db5ca34aa66705b285f61f > > It's the solis_debug branch on Github. > > Does that help? I'm concerned

On Aug 20, 2015, at 6:33 PM, Mario Lobo <mlobo at digiart.art.br> wrote: > > ** cuaU0 > > [>]/usr/local/libexec/nut/solis -D -a lobos -u root > Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3) > 0.000000 debug level is '1' > 21.065536 Solis not detected! aborting ... It looks like /dev/cuaU0 is the port that was suggested for a

On Fri, Sep 11, 2015 at 10:54 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > I know the battery is fully charged and that the load is more than 7.2%. > > The battery voltage seems correct. Mario, I realize some of the variables are not yet correct, but is this better than before? I would like to merge the solis_debug branch in to the master branch. Bruno, Any ideas? Mario

On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > >> Not sure what to look for yet. It might be easier to add in the debug >> calls to the source code-- can you try building NUT from source? If >> you installed via the ports tree (as opposed to binary packages), you >> should have most of the dependencies installed. You might also need

Test -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things."

Hi Charles; I tried both of your suggestions: 1) run stty -f /dev/cuaU0 raw jusbefore running solis 2) Unplug/plug, and run solis right after. The problem still persists. [~]>stty -a -f /dev/cuaU0 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc

On Aug 23, 2015, at 6:26 PM, Mario Lobo <mlobo at digiart.art.br> wrote: > > I hope it helps! It is a bit easier to read than the ktrace output. Here are the bytes received, without the other messages: Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) CommReceive: RecPack: (25 bytes) => 00 17 91 49 5e 5e bc fe bb 46 88 ac 1b 0a a0 ed 01 07 07 bb 46 82 ae 1b 09

Hi, I know the problem now. Previously i use as.timeSeries function, but the error message of setar function still came out. Anyway, many thanks to Pascal for the solution. Best Regards, Ario On Mon, Jul 23, 2012 at 4:28 PM, Pascal Oettli <kridox@ymail.com> wrote: > Hello, > > It works for me (with a warning message), by adding this line before the > setar procedure: > >

Kinda confused by this... I have a Cisco 7960 configured with a couple SIP extensions configured on the phone. Just trying to dial one extension from the other on the same phone, but when I do, I get: -- Remote UNIX connection -- Executing Dial("SIP/2001-ffd4", "SIP/2002") in new stack -- Called 2002 -- Got SIP response 486 "Busy here" back

Turns out another user reported the same issue with a slightly different model: https://github.com/networkupstools/nut/issues/231 <https://github.com/networkupstools/nut/issues/231> The "stty -f /dev/cuaU0 raw" trick should help, but I am confused as to why FreeBSD has different "raw" settings than what is set up at the same time as the baud rate:

Hi, I run a fully updated CentOS 4.4 machine. This morning I got the errors below in my daily Logwatch report (Sendmail part). What has happend? Just some new bogus spammer that cant get the protocol right or is the server under attack? I have googled around but cannot fins any answer or I just suck at googleing... Any ideas ? Jens --------------------- sendmail Begin

Hello, This patch adds client and server support for transmitting the st_nlink field across SSH2_FXP_NAME and SSH2_FXP_ATTRS responses. Please let me know if there anything I can do to improve this patch. I am not subscribed to list so please CC me. Index: sftp-common.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/sftp-common.c,v retrieving

*Hi all, I got problems installing RSTAR, MSVAR, and MSVECM packages. * > install.packages("RSTAR")Installing package(s) into ‘C:/Program Files/R/R-2.15.1/library’ (as ‘lib’ is unspecified)Warning in install.packages : package ‘RSTAR’ is not available (for R version 2.15.1) > install.packages("MSVAR") Installing package(s) into ‘C:/Program Files/R/R-2.15.1/library’

Hi all, I have problem to estimate a SETAR model. I always get an error message. Here is the code: ## there are 4175 observation in the series (a). > a[1:10,1] [1] 1.496498 1.496602 1.496636 1.496515 1.496515 1.496463 1.496429 1.496549 1.496480 [10] 1.496498 > library("tsDyn") > selectSETAR(a, m=2)Using maximum autoregressive order for low regime: mL = 2 Using maximum

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty files. * Roll over to new file when

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 3) * Don't link empty files. * Roll over to new file when filesystem maximum link count is reached. * If link fails for another reason, leave

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 5) * Fixed silly logic error. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty