Re: [hpoj-devel] new "ptal-mlcd" I/O driver checked into CVS

[<pa...@rc...>]

Joe Piolunek wrote:
> The package I got from CVS on Mar. 14 builds without errors, but I can't seem 
> to get it to print
...
> Here are some of the messages that appeared on the command line at one point. 
> I'm not sure what I was doing when they appeared (possibly trying to print), 
> but maybe they'll mean something to you. Sorry if it doesn't help.
> 
> ]$
> ptal-mlcd: ERROR at transport/ExMlcCommandChannel.cpp:186, dev=<par:0>, 
> pid=939, errno=11
> Reply timer popped on port=0, count=1!
> 
> ptal-mlcd: ERROR at ExMgr.cpp:783, dev=<par:0>, pid=939, errno=11
> exClose(reason=4202)
> 
> ptal-mlcd: ERROR at ParPort.cpp:163, dev=<par:0>, pid=939, errno=11
> statusWaitSetClear(event=23) timed out!
> ]$
Hi, Joe.  The reply timer pop probably happened 15 seconds after the first
connection attempt was made to start up MLC, and indicates that there's some
problem receiving a reply to an MLC command, probably due to a communication
error.  Please try the following test:

- Run "script" in order to capture the following output.
- Invoke ptal-mlcd as you normally do, but append the "-nofork" switch to
  the command line.  This will bring up a debug console.
- Issue the command "log" to turn on debug logging.
- Issue the command "activate" to start the MLC conversation with the
  peripheral.
- As soon as the initial log messages stop, issue the command "dump" to
  display all the internal state.
- After about 15 seconds, you'll probably get some more log messages
  including the reply timer pop message.
- Ctrl-C out of ptal-mlcd, Ctrl-D out of "script", and mail me the output.
  This will enable me to see how far it got before the error happened.

> The install/print-howto instructions do seem like they could be simplified.
OK, I'll look into that at some point.

Thanks,
David