[BRLTTY] Long-standing HT warning

[Mario Lang]

Dave Mielke <dave at mielke.cc> writes:

>>I am seeing the following warning printed by BRLTTY whenever I
>>turn my HT display off and on again:
>>
>>brltty: Unexpected byte: 37 (state 2)
>
> Can you determine if that byte is logged when you turn it off or when you turn
> it on? Perhaps, with a sufficient pause between, a timestamp might reveal this
> answer.
>

With the following diff from latest svn

Index: BrailleDrivers/HandyTech/braille.c
===================================================================
--- BrailleDrivers/HandyTech/braille.c	(revision 2113)
+++ BrailleDrivers/HandyTech/braille.c	(working copy)
@@ -421,7 +421,7 @@
     currentState = state;
   }
   gettimeofday(&stateTime, NULL);
-  // LogPrint(LOG_DEBUG, "State: %d+%d", currentState, retryCount);
+  LogPrint(LOG_DEBUG, "State: %d+%d", currentState, retryCount);
 }
 
 static int
@@ -1312,7 +1312,7 @@
       if (count == 0) break;
     }
     timedOut = 0;
-    /* LogPrint(LOG_DEBUG, "Read: %02X", byte); */
+    LogPrint(LOG_DEBUG, "Read: %02X (state %d)", byte, currentState);
 
     if (byte == 0X06) {
       if (currentState != BDS_OFF) {

I get the following log.  It starts just about before I turned the display
off for about 50 seconds.  79 is keyboard input (I use the external keyboard
as my primary system console kbd)

Feb 18 17:20:09 x2 brltty[11449]: State: 4+0
Feb 18 17:20:09 x2 brltty[11449]: Read: 79 (state 4)
Feb 18 17:20:09 x2 brltty[11449]: command: 0023F0
Feb 18 17:20:09 x2 brltty[11449]: Read: 79 (state 4)
Feb 18 17:20:09 x2 brltty[11449]: command: 00235A
Feb 18 17:20:09 x2 brltty[11449]: Read: 7E (state 4)
Feb 18 17:20:09 x2 brltty[11449]: State: 3+0
Feb 18 17:20:55 x2 brltty[11449]: Read: FE (state 3)
Feb 18 17:20:55 x2 brltty[11449]: State: 2+0
Feb 18 17:20:55 x2 brltty[11449]: Read: 74 (state 2)
Feb 18 17:20:55 x2 brltty[11449]: State: 3+0
Feb 18 17:20:55 x2 brltty[11449]: Read: FE (state 3)
Feb 18 17:20:55 x2 brltty[11449]: State: 2+0
Feb 18 17:20:55 x2 brltty[11449]: Read: 37 (state 2)
Feb 18 17:20:55 x2 brltty[11449]: Unexpected byte: 37 (state 2)
Feb 18 17:20:55 x2 brltty[11449]: Read: FE (state 2)
Feb 18 17:20:55 x2 brltty[11449]: State: 2+1
Feb 18 17:20:55 x2 brltty[11449]: Read: 37 (state 2)
Feb 18 17:20:55 x2 brltty[11449]: Unexpected byte: 37 (state 2)
Feb 18 17:20:56 x2 brltty[11449]: State: 1+0
Feb 18 17:20:56 x2 brltty[11449]: Read: FE (state 1)
Feb 18 17:20:56 x2 brltty[11449]: State: 2+0
Feb 18 17:20:56 x2 brltty[11449]: Read: 74 (state 2)
Feb 18 17:20:56 x2 brltty[11449]: State: 3+0
Feb 18 17:20:56 x2 brltty[11449]: State: 4+0
Feb 18 17:20:56 x2 brltty[11449]: Read: 7E (state 4)
Feb 18 17:20:56 x2 brltty[11449]: State: 3+0
Feb 18 17:20:57 x2 brltty[11449]: Read: 0F (state 3)
Feb 18 17:20:57 x2 brltty[11449]: command: 000000
Feb 18 17:20:57 x2 brltty[11449]: Read: 8F (state 3)
Feb 18 17:20:57 x2 brltty[11449]: command: 000001
Feb 18 17:20:57 x2 brltty[11449]: State: 4+0
Feb 18 17:20:57 x2 brltty[11449]: Read: 7E (state 4)
Feb 18 17:20:57 x2 brltty[11449]: State: 3+0
Feb 18 17:20:58 x2 brltty[11449]: Read: 79 (state 3)
Feb 18 17:20:58 x2 brltty[11449]: command: 0023E0

And so on.

So it seems both happen after the display was turned on.

-- 
CYa,
  Mario