Conference csc32::consolemanager

    Assuming you are using the GUI editor:
    
    Use the editor to Create or Modify the node. 
    
    Set the "Transport type" to Pseudo-terminal. 
    
    Enter the following inthe "Command " box
    
    MCR LPS$CONSOLE node-name-of-LPS20 
    
    Note that you must have the LPS supporting host software installed on
    the PCM engine.
    
    Regards,
       dan

    Also, just one further little tidbit. When you connect to the console,
    I've noticed that you must issue a control_w to refresh the screen. 
    After that, it works like a charm. Also, be advised that the
    lps$console software is constantly updating the screen every ten
    seconds or so, event if there is nothing new to report. You'll see lots
    of funny characters used for positions the cursor. You might want to
    consider disabling logging when you add the system. If I remember
    correctly, there is a pushbutton at the bottom of the system screen
    which disables this.
    
    dave

    Thanks a lot, it works fine now.		Martin

    I have set up an LPS20 as described in .1 - and it works nicely....
    
    Just 1 proble. If I exit from the LPS> prompt, I get a pause and then
    go back to the LPS prompt. ie it looks like the LPS$CONSOLE command is
    finished with and then restarted. This becomes an endless loop that I
    can only git rid of by useing the File Exit on the DECterm.
    
    (This is using a connect from C3)
    
    Cheers,
    
    Andy

    You never want to exit from the command you are running in the pseudo
    terminal. If you do, then you are effectively killing the connection. 
    Instead, you want to just disconnect from the console. You can 
    use the file exit command or just type the ctrl_e to exit. The latter
    is prefered by PCM because you are telling PCM directly to close the 
    connection. By exiting the terminal window, the terminal window
    emulator is telling PCM that the connection has been aborted.
    
    Cheers,
    
       Dave

    Dave,
    
    Thanks - I now realise that my question was based on severe mental
    degredation due to lack of brain power. Of course everything is
    behaving as it should - apologies for outting in such a dumb
    question...
    
    ;^)
    
    Andy

    Andy,
    
       No prob. 
    
    dave

    Actually there is a temporary command created to run whatever command
    that you have entered into the config database. That command file
    checks the exit status of the command and if it was successful it
    simply reruns the command hence the "loop" that you saw. As Dave
    already said you should just disconnect from the console.
    
    Regs,
      Dan

I have connected a pseudo terminal for an LPS17 but am unable to get events
for the connection. I am testing the on-line and off-line message and I have 
ensured that my text/start/context is correct. I also tried changing from literal
to regular expression without success. When I use the monitor interface, this 
produces all escape characters as expected due to the LPS console program 
supporting screen output only. When I use the extract/review interface, the 
data appears slightly garbled and events do not follow on one line. When using 
the connect interface, the output is perfect naturally as I am then in screen 
mode. Has anyone been able to get events from an LPS printer.


Thanks,

Dave.

    Dave,
       I'll try and set this up and do some testing. The LPS's have always
    a headache as they *don't* send CR-LF terminators rather they use
    cursor positioning ESC sequences. This caused some interesting problems
    with VCS too.
    
    Regs,
      Dan