FHEM/fhem-mirror
2
0
Fork 0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-01-31 12:49:34 +00:00
Code Issues Releases Wiki Activity

- Peter Sun Dec 23 19:59:00 MEST 2007

Browse Source 
- linux.html: Introduction refinement.


git-svn-id: https://svn.fhem.de/fhem/trunk@131 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
pest 2007-12-23 19:06:07 +00:00
parent 21730103ff
commit fc08f30c7a
3 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
fhem/CHANGED
View File

@ -367,6 +367,7 @@
- feature: HMS100CO (by Peter) - feature: HMS100CO (by Peter)
- feature: EMGZ (by Peter) - feature: EMGZ (by Peter)
- feature: Generate warning if too many commands were sent in the last hour - feature: Generate warning if too many commands were sent in the last hour
- doc: linux.html: Introduction (Peter S.)
- TODO - TODO
emem -2.5kW / getDevData for emwz -1 emem -2.5kW / getDevData for emwz -1

4
fhem/HISTORY
View File

@ -160,3 +160,7 @@
- Martin Fri Dec 21 13:39:17 CET 2007 - Martin Fri Dec 21 13:39:17 CET 2007
- voip2fhem added (contrib/) - voip2fhem added (contrib/)
- Peter Sun Dec 23 19:59:00 MEST 2007
- linux.html: Introduction refinement.

10
fhem/docs/linux.html
View File

@ -10,6 +10,12 @@
<h2>fhem.pl - Hints for GNU/Linux</h2> <h2>fhem.pl - Hints for GNU/Linux</h2>
<table border=1><tr><td>
Note: Depending on the GNU/Linux distribution (Debian, openSuSE, etc.) and version of the Linux kernel you may or <i>may not</i> have to do the following steps.<br>
It is worth giving it a try without any modifications <b>first</b>.<br>
We are trying to convince the kernel developers to enable all ELV devices by default. If that is done, the following steps are unnecessary. We will update this page then accordingly.
</td></tr></table>
<hr>
<p><b><a name="onedevice">One device</a></b><br> <p><b><a name="onedevice">One device</a></b><br>
If you connect one USB device (FHZ1000PC, FHZ1300PC, EM1010PC, WS300, ...) If you connect one USB device (FHZ1000PC, FHZ1300PC, EM1010PC, WS300, ...)
to your GNU/Linux server you can use the regular <i>ftdi_sio</i> kernel module. to your GNU/Linux server you can use the regular <i>ftdi_sio</i> kernel module.
@ -33,7 +39,7 @@ The you load the module using:<br>
<code><br> <code><br>
# modprobe ftdi_sio<br> # modprobe ftdi_sio<br>
</code><br> </code><br>
<hr>
<p><b><a name="multipledevices">Multiple devices</a></b><br> <p><b><a name="multipledevices">Multiple devices</a></b><br>
If you're using multiple USB devices (FHZ1000PC, FHZ1300PC, EM1010PC, WS300, ...) If you're using multiple USB devices (FHZ1000PC, FHZ1300PC, EM1010PC, WS300, ...)
you cannot use the methode above. You need to modify the ftdi_sio kernel module you cannot use the methode above. You need to modify the ftdi_sio kernel module
@ -113,7 +119,7 @@ You should now see multiple ttyUSB devices:
crw-rw---- 1 root uucp 188, 0 2007-02-11 23:00 /dev/ttyUSB0<br> crw-rw---- 1 root uucp 188, 0 2007-02-11 23:00 /dev/ttyUSB0<br>
crw-rw---- 1 root uucp 188, 1 2007-02-11 23:00 /dev/ttyUSB1<br> crw-rw---- 1 root uucp 188, 1 2007-02-11 23:00 /dev/ttyUSB1<br>
</code><br> </code><br>
<hr>
<p><b><a name="devicelinks">Device links</a></b><br> <p><b><a name="devicelinks">Device links</a></b><br>
If you're using multiple USB devices (FHZ, EM, WS...) it might occur that the If you're using multiple USB devices (FHZ, EM, WS...) it might occur that the
enumeration of the /dev/ttyUSB<i>n</i> numbers get mixed up if one of the enumeration of the /dev/ttyUSB<i>n</i> numbers get mixed up if one of the