`dut-control ec_uart_pty` should give you the EC console.

The others may be the servo v4 console and servo micro console. I could remove that print or maybe even try to enhance it such that it will actually reflect what the console is. I had originally added it as a quick way to see what the console was.

Thanks, would be nice to use the dut-control name. I will use dut-control from now on

 $ dut-control | grep pty
2016-11-15 09:21:21,449 - Servod - ERROR - Getting jtag_buf_on_flex_en: 'Suart' object has no attribute 'wr_rd'
2016-11-15 09:21:24,851 - Servod - ERROR - Getting spi2_buf_on_flex_en: 'Suart' object has no attribute 'wr_rd'
2016-11-15 09:21:24,974 - Servod - ERROR - Getting spi1_buf_on_flex_en: 'Suart' object has no attribute 'wr_rd'
atmega_pty:/dev/pts/32
cpu_uart_pty:/dev/pts/36
dut_pty:/dev/pts/31
ec_uart_pty:/dev/pts/41
raw_ec_uart_pty:/dev/pts/38
raw_servo_console_pty:/dev/pts/35
raw_servo_v4_console_pty:/dev/pts/24
raw_usbpd_uart_pty:/dev/pts/34
servo_console_pty:/dev/pts/39
servo_v4_console_pty:/dev/pts/33
uart1_pty:/dev/pts/38
uart2_pty:/dev/pts/36
uart3_pty:/dev/pts/34
usbpd_uart_pty:/dev/pts/40


What is the different between servo_console_pty vs servo_v4_console when I am using servov4.  Looks like I can connect to both and have different help output.

servo_console_pty is servo micro's console.