[Nut-upsdev] anybody familiar with these init(?) sequences?

[Kjell Claesson]

Den Monday 03 March 2008 14.07.17 skrev AE sysadmin:
> Hi,
>
Hi Vova,
> I am unable to monitor my RS232S connected device with
> any of the monitors I have tried - either splitting COM1 or
> sharing it results in device side timeouts.
>
> I did not test the device from NUT as it is not supported officially
> anyway and as I want to do my best to make sure that I am
> doing things cleanly.
>
> The init sequences that the Windows based monitoring app is
> sending are the following:
>
> 51 31 0d
> 51 31 0d
> 51 31 0d
> 51 31 0d
>
Q1<cr>

> 43 46 0d
> 43 46 0d
> 43 46 0d
> 43 46 0d
CF<cr>

And this look exactly as a megatec protocol.
>
> Quick grep on NUT src did not show anything comprehensible
> for me. Maybe anyone of you had seen these numbers before?
>
You had to grep for the ascii representative of the hex nubers you got from 
the monitor.

> (yes, I know, the device product name is missing in my mail).
>
>
> Would be grateful for any pointers.

Try the megatec driver.

Regards
Kjell