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

Fixing faq 21

Browse Source 
git-svn-id: https://svn.fhem.de/fhem/trunk@3005 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
rudolfkoenig 2013-03-31 10:02:01 +00:00
parent 6516a41541
commit 02e25a766a
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
fhem/docs/faq.html
View File

@ -544,13 +544,13 @@ See <a href="USB.html">USB compendium</a> for help.
<ul> <ul>
If too many messages for FHT devices are queued in CUL, the fht buffer If too many messages for FHT devices are queued in CUL, the fht buffer
subsystem of CUL overflows. You get EOB (end of buffer) messages and subsystem of CUL overflows. You get EOB (end of buffer) messages and
likely LOVF (limit overflow) messages, too. define <code>attr CUL fhtsoftbuffer 1</code> likely LOVF (limit overflow) messages, too. Either you tried to send too much
to activate a quasi unlimited software buffer in fhem itself to avoid this commands to the FHT80b, or (more probably) the communication to the FHT80b is
behavior.<br><br> disturbed or the FHT80b is not paired with the CUL.
<br><br>
By the way, <code>set CUL raw T01abcd</code> (abcd= FHT house code) resets Since the FHT buffer is not cleaned automatically, you have to do it manually
the CUL FHT subsystem, no need to unplug/replug the CUL device in case of with the <code>set CUL raw T01abcd</code> (abcd= FHT house code) command, or
the aforementioned issue. by unpluggin/replugging the CUL.
</ul> </ul>
<a name="faq22"></a> <a name="faq22"></a>