in reply to Logging the serial console with minicom and running commands with control::cli

Since you're already using Control::CLI, can't you use the "Output_log" parameter of Control""CLI's object constructor (see here for more details) to capture all output from the device?

If you're not getting back what you believe that you should for any command(s) that you send via Control::CLI, I'd recommend using the Dump_log parameter to capture all input and output. Another route is to manually connect to the device to run the command(s) in question and see how the device responds.

  • Comment on Re: Logging the serial console with minicom and running commands with control::cli

Replies are listed 'Best First'.
Re^2: Logging the serial console with minicom and running commands with control::cli
by Anonymous Monk on Dec 08, 2014 at 15:59 UTC

    I cannot really use the output_log as we run a suite comprised of several scripts some of which don't use control::cli and some are not even perl so I need some external means of logging the output of the unit.

    As I said before this is not an issue with the device or control::cli or minicom . All commands run fine either manually or scripted I just cannot log the output of the unit. I suspect that minicom is taking over and configuring the tty causing control::cli to not be able to read what it is expecting

    I have tried using intercepttty to 'clone' the serial port and this sort of works but intercepttty does seem to be a little flaky and doesn't log everything .