Contact Support
https://github.com/contact
<!-- Like Button --> <br/><br/><iframe allowTransparency='true' expr:src='"http://www.facebook.com/plugins/like.php?href=" + data:post.canonicalUrl + "&layout=button_count&show_faces=false&width=100&action=like&font=arial&colorscheme=light"' frameborder='0' scrolling='no' style='border:none; overflow:hidden; width:100px; height:21px;'/> <!-- Like Button -->

sudo apt-get udpate sudo apt-get install socat
# socat tcp-listen:8000,reuseaddr,fork file:/dev/ttyUSB0,nonblock,waitlock=/var/run/tty0.lock,b115200,raw,echo=0
socat pty,link=/dev/ttyUSB0,waitslave tcp:pi.oeey.com:8000
# while true ; do socat pty,link=/dev/ttyUSB0,waitslave tcp:pi.oeey.com:8000 ; sleep .001 ; done
# tio -b 115200 /dev/ttyUSB0 [tio 16:53:30] tio v1.20 [tio 16:53:30] Press ctrl-t q to quit [tio 16:53:30] Connected > I sent something to the serial port
# on RedHat based: yum install minicom # on Debian based: sudo apt-get install minicom
# Menu CTRL-A Z # To Quit CTRL-A Q # To send (via xmodem/ymodem/zmodem) CTRL-A S # To receive (via xmodem/ymodem/zmodem) CTRL-A R # To configure CTRL-A O
# Bring up minicom configuration minicom -s # Connect to ttyUSB0 with 115200 baud rate minicom -b 115200 -D /dev/ttyUSB0The default configuration is 115200 8N1 with Hardware Flow Control. I usually disable Hardware Flow Control in my setting and save to the default 'df1'.
tio /dev/ttyUSB0 tio -b 115200 /dev/ttyUSB0 # 115200 is the default baud rate
mkdir ~/.src cd ~/.src wget https://github.com/tio/tio/releases/download/v1.20/tio-1.20.tar.xz tar -avxf tio-1.20.tar.xz cd tio-1.20/ ./configure make && make install
sudo apt-get install autoconf mkdir ~/.src cd ~/.src git clone https://github.com/tio/tio.git cd tio sh autogen.sh ./configure make && make install
# tio -b 115200 /dev/ttyUSB0 [tio 16:53:30] tio v1.20 [tio 16:53:30] Press ctrl-t q to quit [tio 16:53:30] Connected > some serial text
ctrl-t q
"Spring" forward into action, and "Fall" back to sleep.


Show how to read the schematic diagram of the project you chose and, to the best of your ability, explain to your counselor how the circuit you built operates.
Electronics merit badge requirements | |
| |
![]() |
| Apple Xserve Server |
Xserve3,1
Model: Intel Xserve3,1 (2009)
Processor: 2.26 GHz Quad-Core Intel Xeon
Memory: 12 GB 1066 MHz RAM
Network: 2x Intel 82574L Gigabit Network
Storage: (3 high speed SAS drives,
but not important as controller is not supported)
Graphics: NVIDIA GeForce GT 120 with 256 MB of GDDR3 SDRAM
Expansion:
* 2x PCIe 2.0 ×16
* 3x USB 2.0
* 2x Firewire 800
* 1x RS-232 serial
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
>>> import this