On Tue, 8 Sep 2015 22:25:54 -0400
Charles Lepple 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
@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 that it might get out of sync
On Aug 26, 2015, at 4:43 PM, Mario Lobo ml...@digiart.art.br wrote:
1) run stty -f /dev/cuaU0 raw jusbefore running solis
What about this: run solis first, let it fail, then run stty?
The default settings look wrong, but in theory the driver should fix them up.
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
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
On Aug 23, 2015, at 6:26 PM, Mario Lobo ml...@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
On Sun, 23 Aug 2015 11:09:03 -0400
Charles Lepple clep...@gmail.com wrote:
On Aug 21, 2015, at 10:10 AM, Mario Lobo ml...@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
7 matches
Mail list logo