Difference between revisions of "Serial Hack"

From LinuxMCE
Jump to: navigation, search
(→‎Comments: Zaerc, please try to understand the objectives of a wiki page and the objectives of a discussion page.)
 
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
[[Category: Programmer's Guide]]
 +
[[Category: Serial]]
 +
[[Category: GSD]]
 +
 +
This should no longer be needed. If it is, please file a detailed bug report.
 +
 
== Serial List Hack ==
 
== Serial List Hack ==
 
In some situations, (which, I might add are becoming more and more common now) a core or core/hybrid may not have enough, or indeed, any serial ports for automation kit such as the [[X10]] modules to jack into.
 
In some situations, (which, I might add are becoming more and more common now) a core or core/hybrid may not have enough, or indeed, any serial ports for automation kit such as the [[X10]] modules to jack into.
Line 6: Line 12:
 
A simple replacement, which, while inferior to the current script in that it does not detect the ports in use, does correctly list all serial ports, both USB and normal serial. However, it requires the 'tree' command, so:
 
A simple replacement, which, while inferior to the current script in that it does not detect the ports in use, does correctly list all serial ports, both USB and normal serial. However, it requires the 'tree' command, so:
  
 +
sudo apt-get install tree
  
−
<pre>sudo apt-get install tree</pre>
+
Once that has completed, tree will have been installed, and we can use its '-fi' mode to produce full paths, then it is just a simple matter of removing the original ListSerialPorts.sh file and writing our own, just copy these commands in a terminal window (see [[Editing_Text]] for alternative options), it will make a backup of the old script too:
−
 
+
−
 
+
−
Once that has completed, tree will have been installed, and we can use its '-fi' mode to produce full paths, then it is just a simple matter of removing the origional ListSerialPorts.sh file and writing our own, I use [[vim]] for this, but any other terminal or graphical text editor will do the job:
+
 
   
 
   
−
 
+
mv -iv /usr/pluto/bin/ListSerialPorts.sh /usr/pluto/bin/ListSerialPorts.sh-`date '+%Y%m%d:%H%M'` &&
−
<pre>
+
  cat >/usr/pluto/bin/ListSerialPorts.sh << "EOF"
−
sudo rm /usr/pluto/bin/ListSerialPorts.sh
+
−
sudo vim /usr/pluto/bin/ListSerialPorts.sh
+
−
</pre>
+
−
 
+
−
 
+
−
Now that [[vim]] is open, enter the following:
+
−
 
+
−
 
+
−
<pre>
+
−
#!/bin/bash
+
−
 
+
−
tree -fi /dev | grep ttyS
+
−
tree -fi /dev | grep ttyUSB
+
−
</pre>
+
−
 
+
−
==Comments==
+
−
 
+
−
If someone out there has a better way of doing this, please post it here! -AVJohn
+
−
 
+
−
----
+
−
How about:
+
−
 
+
−
  cat >/usr/pluto/bin/ListSerialPorts.sh <<"EOF"
+
 
  #!/bin/bash
 
  #!/bin/bash
 
   
 
   
Line 42: Line 23:
 
  tree -fi /dev | grep ttyUSB
 
  tree -fi /dev | grep ttyUSB
 
  EOF
 
  EOF
 +
  
−
That should overwrite the file in one go, without having to use vi.
+
==Comments==
−
--[[User:Zaerc|Zaerc]] 04:53, 20 September 2007 (MST)
+
  
−
 
+
If someone out there has a better way of doing this, please post it here! -AVJohn
−
Let's all join in the mis-understanding of Wiki and this page.  How do you want to edit a file today?
+
−
 
+
−
I think this would be cool.
+
−
 
+
−
perl -e 'print "#!/bin/bash\n\ntree -fi /dev | grep ttyS\ntree -fi /dev | grep ttyUSB"' > /usr/pluto/bin/ListSerialPorts.sh
+
−
 
+
−
What do you all think about that coolness?  It's all on a single line so it can be edited unlike the Zaerc version.  Perl is widespread and easy to type.  Probably it could just be copied and pasted.  Wow that's sweet.
+
−
 
+
−
Anyway, I doubt that AVJohn was asking for contributions as to how to edit a dang file.  Probably, since the page is called "Serial Hack", he was asking if there was a better way to fix the serial situation, rather than editing a file.  But that's no matter, I think that everyone should become smarter for reading this blog on the main page.  Is't it great!
+
−
 
+
−
Cheers to all!
+
−
 
+
−
Zaerc - I've added content, so you should feel good about that.  I know that in your mind all additions are good additions and deserve a place on a Wiki page.  Removing blather like this would be horrific so I'm sure this will stay here for a long time.
+
−
 
+
−
[[User:Trout|Trout]] 07:10, 23 September 2007 (MST)
+
−
 
+
−
 
+
−
[[Category: GSD]]
+
−
[[Category: LinuxMCE_Devices]]
+
−
[[Category: Programmer's Guide]]
+

Latest revision as of 09:24, 14 January 2010


This should no longer be needed. If it is, please file a detailed bug report.

Serial List Hack

In some situations, (which, I might add are becoming more and more common now) a core or core/hybrid may not have enough, or indeed, any serial ports for automation kit such as the X10 modules to jack into.

In these cases a USB-to-Serial converter may be used, but LinuxMCE does not list these correctly in its admin pages. This is due to the script "/usr/pluto/bin/ListSerialPorts.sh" which creates the list of serial ports, not giving the correct path (usually /dev/ttyUSB#, where # is a number).

A simple replacement, which, while inferior to the current script in that it does not detect the ports in use, does correctly list all serial ports, both USB and normal serial. However, it requires the 'tree' command, so: 

sudo apt-get install tree

Once that has completed, tree will have been installed, and we can use its '-fi' mode to produce full paths, then it is just a simple matter of removing the original ListSerialPorts.sh file and writing our own, just copy these commands in a terminal window (see Editing_Text for alternative options), it will make a backup of the old script too: 

mv -iv /usr/pluto/bin/ListSerialPorts.sh /usr/pluto/bin/ListSerialPorts.sh-`date '+%Y%m%d:%H%M'` &&
cat >/usr/pluto/bin/ListSerialPorts.sh << "EOF"
#!/bin/bash

tree -fi /dev | grep ttyS
tree -fi /dev | grep ttyUSB
EOF

Comments

If someone out there has a better way of doing this, please post it here! -AVJohn

Retrieved from "http://wiki.linuxmce.org/index.php?title=Serial_Hack&oldid=22099"