Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread Arnaud Quette
2010/12/1 John Bayly freebsd.po...@tipstrade.net On 01/12/2010 14:17, Arjen de Korte wrote: Citeren Charles Lepple clep...@gmail.com: The get_belkin_reply() function looks fragile to me. Three seconds should be enough to fill the buffer, but if you put a few upsdebugx() calls around

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread Arjen de Korte
Citeren Arnaud Quette aquette@gmail.com: Thanks for the suggestions, I've added the flush statement as well as some debugging information. As this is a intermittent issue I decided to try overloading the UPS by sending it repeated beeper commands while watching the debug output. What

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread Arjen de Korte
Citeren John Bayly freebsd.po...@tipstrade.net: Last but not least, in most drivers, we allow a couple of missed replies before we call dstate_datastale() so that glitches don't lead to automatic reconnects. Can you suggest what driver would be a good template to use? Take a look at the

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread John Bayly
On 02/12/2010 10:54, Arjen de Korte wrote: Citeren John Bayly freebsd.po...@tipstrade.net: Last but not least, in most drivers, we allow a couple of missed replies before we call dstate_datastale() so that glitches don't lead to automatic reconnects. Can you suggest what driver would be a

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread Gene Heskett
On Thursday, December 02, 2010 10:05:54 am Arjen de Korte did opine: Citeren Arnaud Quette aquette@gmail.com: Thanks for the suggestions, I've added the flush statement as well as some debugging information. As this is a intermittent issue I decided to try overloading the UPS by

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread John Bayly
On 02/12/2010 15:28, Gene Heskett wrote: On Thursday, December 02, 2010 10:05:54 am Arjen de Korte did opine: Citeren Arnaud Quetteaquette@gmail.com: Thanks for the suggestions, I've added the flush statement as well as some debugging information. As this is a intermittent issue I decided

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-02 Thread Gene Heskett
On Thursday, December 02, 2010 04:36:43 pm John Bayly did opine: On 02/12/2010 15:28, Gene Heskett wrote: On Thursday, December 02, 2010 10:05:54 am Arjen de Korte did opine: Citeren Arnaud Quetteaquette@gmail.com: Thanks for the suggestions, I've added the flush statement as well as

[Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-01 Thread John Bayly
I've a Belkin Regulator Pro (F6C1400-EUR) connected via serial to a FreeBSD machine using NUT v.2.4.3 Sometimes I get a series of logged messages saying that the data is switching between stale and valid, this in itself isn't an issue, however occasionally when the communication is

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-01 Thread Charles Lepple
On Dec 1, 2010, at 7:42 AM, John Bayly wrote: I've a Belkin Regulator Pro (F6C1400-EUR) connected via serial to a FreeBSD machine using NUT v.2.4.3 Sometimes I get a series of logged messages saying that the data is switching between stale and valid, this in itself isn't an issue,

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-01 Thread Arjen de Korte
Citeren Charles Lepple clep...@gmail.com: The get_belkin_reply() function looks fragile to me. Three seconds should be enough to fill the buffer, but if you put a few upsdebugx() calls around ser_get_buf_len(), it should be evident whether the read is timing out, or if there is a problem

Re: [Nut-upsuser] Belkin Regulator Pro dropping connection and halting

2010-12-01 Thread John Bayly
On 01/12/2010 14:17, Arjen de Korte wrote: Citeren Charles Lepple clep...@gmail.com: The get_belkin_reply() function looks fragile to me. Three seconds should be enough to fill the buffer, but if you put a few upsdebugx() calls around ser_get_buf_len(), it should be evident whether the read