Hi There, We have this rather large-ish floor-standing Best Axxium Pro, Model Series 0650. I tried using both the "bestups" and "blazer_ser" drivers with it, but no go. So before I go any further: *Should* one of these work with it and, if not, do I have any options? (E.g.: Modify a current driver, resuscitate one that was started and abandoned, etc.? I can code.) My test platform was nut 2.4.3-1ubuntu3.2 under Ubuntu 10.04 LTS on a laptop. I have confirmed the serial port works. I used a 9-pin null modem adapter, as both the laptop and Axxium Pro were transmitting on pin 3. Thanks, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.
torsdagen den 6 juni 2013 14.58.53 skrev Jim Seymour:> Hi There,Hi Jim,> We have this rather large-ish floor-standing Best Axxium Pro, Model > Series 0650. >That would be the tower model.> I tried using both the "bestups" and "blazer_ser" drivers with it, but > no go. So before I go any further: *Should* one of these work with it > and, if not, do I have any options? (E.g.: Modify a current driver, > resuscitate one that was started and abandoned, etc.? I can code.) >It may talk bcmxcp protocol. If it say advanced binary protocol for the communication, it may be the bcmxcp. Some Sola and Best ups'es was using this protocol.> My test platform was nut 2.4.3-1ubuntu3.2 under Ubuntu 10.04 LTS on a > laptop. I have confirmed the serial port works. I used a 9-pin null > modem adapter, as both the laptop and Axxium Pro were transmitting on > pin 3.Yes it should use only rx and tx line. 9600,8,n,1. No handshake, as the protocol is binary and use a start sequence and checksum. Regards //Kjell
On Jun 6, 2013, at 2:58 PM, Jim Seymour wrote:> Hi There, > > We have this rather large-ish floor-standing Best Axxium Pro, Model > Series 0650. > > I tried using both the "bestups" and "blazer_ser" drivers with it, but > no go. So before I go any further: *Should* one of these work with it > and, if not, do I have any options? (E.g.: Modify a current driver, > resuscitate one that was started and abandoned, etc.? I can code.)UPS vendors have a habit of changing out the innards without changing the model name. So the answer about the correct driver will depend on which UPS model and generation this is most similar to. Some of the documentation on the web refers to the "Check-UPS II" software. If you have an original manual for this UPS, does it suggest a specific monitoring tool? If it is Check-UPS, I think that is closest to the bestups driver-- but it might not recognize your particular model's ID string. (The bestups driver is very light on debugging messages.) Kjell's suggestion of bcmxcp might also be correct, but the Axxium product brochure looks to be of a similar vintage to the Best Power Patriot Pro II that I had, which came with a Check-UPS II CD.> My test platform was nut 2.4.3-1ubuntu3.2 under Ubuntu 10.04 LTS on a > laptop. I have confirmed the serial port works. I used a 9-pin null > modem adapter, as both the laptop and Axxium Pro were transmitting on > pin 3.The bestups driver might be more complete than blazer_ser at version 2.4.3-- there are some later comments in the blazer_ser driver that seem to cover additional Best quirks. If you run the driver directly with at least two -D flags (something like /lib/nut/bestups -DD -a name-of-ups) what log messages do you get? -- Charles Lepple clepple at gmail
On Jun 10, 2013, at 11:05 AM, Jim Seymour <jseymour at LinxNet.com> wrote:> But the manual > also says "The Axxium Pro system communicates with your computer using > an advanced binary protocol."I can see that phrase being used to describe BCM/XCP.
On Jun 10, 2013, at 11:05 AM, Jim Seymour wrote:> I tried all three: bcmxcp (produced only "Receive error > (PW_COMMAND_START_BYTE): 0!!!"), blazer_ser ("blazer_status: short > reply") and bestups ("debug level is ..." and "Unable to detect...").You mentioned the null-modem cable, but are you using a motherboard RS-232 port, or a USB-to-serial converter? This thread has some information on Prolific vs. FTDI adapters: http://thread.gmane.org/gmane.comp.monitoring.nut.user/6494/focus=6495 Maybe Kjell has some insight on what else to try with the bcmxcp driver. -- Charles Lepple clepple at gmail
On Tue, 11 Jun 2013 09:32:23 -0400 Charles Lepple <clepple at gmail.com> wrote: [snip]> > You mentioned the null-modem cable, but are you using a motherboard > RS-232 port, or a USB-to-serial converter?Real, honest-to-goodness RS-232 port. [snip]> Maybe Kjell has some insight on what else to try with the bcmxcp > driver. >If I could just see what, if anything, the UPS is sending back, it would help. Maybe I'll try stack-tracing the drivers. Thanks, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.
Sent this before, but it apparently got lost in the ether... On Tue, 11 Jun 2013 09:32:23 -0400 Charles Lepple <clepple at gmail.com> wrote: [snip]> > You mentioned the null-modem cable, but are you using a motherboard > RS-232 port, or a USB-to-serial converter?Real, honest-to-goodness RS-232 port. [snip]> Maybe Kjell has some insight on what else to try with the bcmxcp > driver. >If I could just see what, if anything, the UPS is sending back, it would help. I stack-traced each of the drivers. It looks like they're all timing out awaiting a response? Thanks, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.