[Nut-upsdev] [blazer_usb] Support for TECNOWARE ERA LCD (FGCERALCD0K85)

Charles Lepple clepple at gmail.com
Thu Jan 10 03:54:52 UTC 2013

On Jan 9, 2013, at 2:36 PM, Rob Power wrote:

> Asking for string 13 --> output: ..#.2.3.0...0. .0.0.2. .1.2...0.0. .5.0...0... (Unknown command)

String 13 (0xd) is the USB/krauler version of "F", and the expected first character in the response is "#" (as confirmed above). The rest of the string is static parameters, parsed here: http://trac.networkupstools.org/projects/nut/browser/tags/v2.6.5/drivers/blazer.c#L296

> Status: beep = 1 (capture n. 0013-0010)
> Asking for string 7 --> output:  ..U.P.S. .N.o. .A.C.K. (should be Q command)
> Asking for string 12 --> output: P.#. . ..... (Unknown command)

Similarly, string 12 (0xc) is "I", the vendor request. The response is parsed here: http://trac.networkupstools.org/projects/nut/browser/tags/v2.6.5/drivers/blazer.c#L348

> ask string 13 (Meaning: "hey, I'm sending you a manteinance command")
> ask string <command number> (Meaning: "do this/do that")
> expecting "ups no ack" response
> ask string 12 (Meaning: "hey, have you done last thing I asked?")

I'm pretty sure there isn't any stored state for those commands. It's a really simple protocol, aside from the obfuscation introduced with the USB-to-serial converter.

I forgot that we have the protocol library documents online:


> PS: I hope I may eventually make some tries adding debug options to the code in next days (more probably next week). What values do you suggest to print out? "buf" variable for example?

'buf' is probably empty if there is an EPROTO error being returned. I would say just add a few lines to confirm that my suspicions are correct regarding what path is being taken through the code.

Does USBlyzer have an option to dump the whole initialization sequence (up until the point that things start to repeat)? That might shed some light on what else is being sent (or if there is yet another langid_fix value that is needed).

Charles Lepple
clepple at gmail

More information about the Nut-upsdev mailing list