MiniCom

Using Minicom

NOTE: Read the next section to learn how to use telnet and ser2net instead of minicom to test ports. It might be easier.

To run minicom to test a usb/serial port you should first kill the Luup engine, the serial proxy, and Network Monitor which reboots Vera when it detects the Luup engine isn't running. Do this by running these 2 commands:

kill $(ps ax | grep 'Start_serproxy.sh.$\|Start_serproxy.sh$\|Start_LuaUPnP.sh$\|Start_LuaUPnP.sh.$\|Start_NetworkMonitor.sh$\|Start_NetworkMonitor.sh.$')

killall LuaUPnP NetworkMonitor serproxy ser2net

Next, download the minicom package, and extract the minicom program, with the commands:

mkdir /tmp/minicom

cd /tmp/minicom

wget -O /tmp/minicom.ipk http://downloads.x-wrt.org/xwrt/kamikaze/snapshots/brcm-2.4/packages/minicom_2.3-1_mipsel.ipk

tar zxvf /tmp/minicom.ipk

tar zxvf data.tar.gz

Afterwards you can setup and start using minicom by running the following command and specifying the port options.:

/tmp/minicom/usr/sbin/minicom -s -o

When you're done, rebooting Vera will restart the normal Luup engine, and serial port handling.  The minicom program will not remain on the device after reboot as the previous commands put minicom into a temporary ram drive.

Note: To see a list of usb-serial ports run: /proc/tty/driver/usb-serial

Using telnet instead of minicom with ser2net

The open source app ser2net is used for the RS232 to network communication. See: [1]. The serproxy binary is just a wrapper that calls ser2net. cat /var/log/cmh/serproxy.log to see the command line for ser2net that is being called. You can kill serproxy ser2net Start_serproxy.sh if you want to run ser2net by hand and change the command line parameters to test your ports. Then you can use telnet instead of minicom to test your serial port.