From aa890479aeb63fda4261d7598b8a3dcdb4779624 Mon Sep 17 00:00:00 2001 From: borisneubert Date: Mon, 6 Sep 2010 17:12:33 +0000 Subject: [PATCH] Docs updated on fhtsoftbuffer for CUL. git-svn-id: https://svn.fhem.de/fhem/trunk@712 2b470e98-0d58-463d-a4d8-8e2adae1ed80 --- fhem/docs/commandref.html | 43 ++++++++++++++++++++++++++++----------- fhem/docs/faq.html | 24 ++++++++++++++++++++-- 2 files changed, 53 insertions(+), 14 deletions(-) diff --git a/fhem/docs/commandref.html b/fhem/docs/commandref.html index 3068a6135..09b213b2c 100644 --- a/fhem/docs/commandref.html +++ b/fhem/docs/commandref.html @@ -1097,7 +1097,7 @@ A line ending with \ will be concatenated with the next one, so long lines As the FHZ command buffer for FHT devices is limited (see fhtbuf), and commands are only sent to the FHT device every 120 seconds, the hardware buffer may overflow and FHT commands get lost. - Setting this attribute implements an "unlimited" software buffer
+ Setting this attribute implements an "unlimited" software buffer.
Default is disabled (i.e. not set or set to 0).

@@ -1787,6 +1787,18 @@ A line ending with \ will be concatenated with the next one, so long lines the CUL. See the CUL firmware README document for details on CUL commands.
+
  • fhtbuf
    + CUL has a message buffer for the FHT. If the buffer is full, then newly + issued commands will be dropped, if the attribute fhtsoftbuffer is not set. Instead, a "EOB" message is issued. + fhtbuf returns the free memory in this buffer (in hex), + an empty buffer in the CUL is 40 (64 bytes). + A message occupies 3 + 2x(number of FHT commands) bytes, + this is the second reason why sending multiple FHT commands with one + set is a good idea. The first reason is, that + these FHT commands are sent at once to the FHT. +
    • +
  • ccconf
    Read some CUL radio-chip (cc1101) registers (frequency, bandwidth, etc), and display them in human readable form. @@ -1812,6 +1824,13 @@ A line ending with \ will be concatenated with the next one, so long lines attr CUN2 sendpool CUN1,CUN2,CUN3
    attr CUN3 sendpool CUN1,CUN2,CUN3

    • +
  • fhtsoftbuffer
    + As the CUL command buffer for FHT devices is limited (see fhtbuf), + and commands are only sent to the FHT device every 120 seconds, + the hardware buffer may overflow and FHT commands get lost or errors + may occur. + Setting this attribute implements an "unlimited" software buffer.
    + Default is disabled (i.e. not set or set to 0).

  • addvaltrigger
    Create triggers for additional device values. Right now these are RSSI and RAWMSG for the CUL family and RAWMSG for the FHZ. @@ -2966,7 +2985,7 @@ Attributes:
    dimup off on - toggle + toggle Examples: @@ -5500,9 +5519,9 @@ isday filenames.
    You can specify a path to which the files will be rendered. If you also specify a prefix, this will be used to build the resulting filename. -

    • +
  • multiprocess
    - This defines if the Renderer works in a multiprocessing mode.
    + This defines if the Renderer works in a multiprocessing mode.
    You can set multiprocessing either to on / off and the renderer will draw the time-scheduled tasks either in multiprocessing mode, or not. NOTE: Direct GET calls, except for a general GET (for all weblinks) will be renderer diff --git a/fhem/docs/faq.html b/fhem/docs/faq.html index 088cfe35d..de5d738d9 100644 --- a/fhem/docs/faq.html +++ b/fhem/docs/faq.html @@ -106,7 +106,7 @@
    @@ -140,10 +140,17 @@ + + + +

    --> @@ -534,5 +541,18 @@ See USB compendium for help. + +

    21. What is "unknown message: EOB" from a CUL device?

    +
      + 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 + likely LOVF (limit overflow) messages, too. define attr CUL fhtsoftbuffer 1 + to activate a quasi unlimited software buffer in fhem itself to avoid this + behavior.

      + + By the way, set CUL raw T01abcd (abcd= FHT house code) resets + the CUL FHT subsystem, no need to unplug/replug the CUL device in case of + the aforementioned issue. +