search for: 2400bauds

...be great if you could test this patch (through some > reboots) and report back. > > Then, I don't think it's an issue with the device. > There is a long run TODO (mentioned in the header of libshut.c) that > is the baudrate negotiation. > The driver still communicates at 2400bauds, which is not that much for > such verbose units. We could go at least for 9600 on these units, > which is 4 times faster already. > This may cause some slowness and behavior issues as you're > experiencing, under some circumstances. > For example, the test using a 5SC750 on L...

Hello Arno, > Question: have you also tested oldmge-shut? > Otherwise, that might be interesting to do so and send back the > results of these tests... Yes, I've tried this as well with worse results unfortunately. This driver seems to be even more unstable. When it gets able to set communication with the UPS (which is not always the case), it usually lost it again after a while.

...sly (setline...). So, it would be great if you could test this patch (through some reboots) and report back. Then, I don't think it's an issue with the device. There is a long run TODO (mentioned in the header of libshut.c) that is the baudrate negotiation. The driver still communicates at 2400bauds, which is not that much for such verbose units. We could go at least for 9600 on these units, which is 4 times faster already. This may cause some slowness and behavior issues as you're experiencing, under some circumstances. For example, the test using a 5SC750 on Linux (Debian Jessie) shows t...

...e great if you could test this patch (through some > reboots) and report back. > > Then, I don't think it's an issue with the device. > There is a long run TODO (mentioned in the header of libshut.c) that is > the baudrate negotiation. > The driver still communicates at 2400bauds, which is not that much for > such verbose units. We could go at least for 9600 on these units, which is > 4 times faster already. > This may cause some slowness and behavior issues as you're experiencing, > under some circumstances. > For example, the test using a 5SC750 on Li...

...ough some >> reboots) and report back. >> >> Then, I don't think it's an issue with the device. >> There is a long run TODO (mentioned in the header of libshut.c) >> that is the baudrate negotiation. >> The driver still communicates at 2400bauds, which is not that >> much for such verbose units. We could go at least for 9600 on >> these units, which is 4 times faster already. >> This may cause some slowness and behavior issues as you're >> experiencing, under some circumstances. >> For...