Dave, here's the log. I terminated brltty after the log began to repeat. BRLTTY 3.10 [http://mielke.cc/brltty/] brltty: Working Directory: /etc/brltty brltty: Writable Directory: /lib/brltty/rw brltty: Configuration File: /etc/brltty.conf brltty: Data Directory: /etc/brltty brltty: Library Directory: /lib/brltty brltty: Tables Directory: /etc/brltty brltty: Text Table: text.nabcc.tbl brltty: Attributes Table: attributes.tbl brltty: Contractions Directory: /etc/brltty brltty: Contraction Table: none brltty: checking for screen driver: lx brltty: initializing screen driver: lx brltty: device directory: /dev brltty: checking screen device: /dev/vcsa brltty: screen device: vcsa brltty: checking console device: /dev/tty0 brltty: console device: tty0 brltty: device opened: /dev/vcsa: fd=3 brltty: screen opened: vcsa: fd=3 brltty: device opened: /dev/tty0: fd=4 brltty: console opened: tty0: fd=4 brltty: Screen Font Map Size: 546 brltty: VGA Character Count: 512(large) brltty: attributes masks: font=0800 unshifted=F700 shifted=0000 brltty: Screen Driver: lx [Linux] brltty: Linux Screen Driver: brltty: Screen Parameter: charset= brltty: Screen Parameter: hfb= brltty: Screen Parameter: debugsfm= brltty: BrlAPI Server: release 0.5.2 brltty: API Parameter: auth= brltty: API Parameter: host= brltty: API Parameter: stacksize= brltty: linking local socket lock: File exists brltty: socket 0 established (fd 5) brltty: socket 1 established (fd 6) brltty: exit status: 0 brltty: Console opened: fd=7 brltty: checking braille device: ttyUSB0 brltty: checking for braille driver: ts brltty: initializing braille driver: ts -> ttyUSB0 brltty: serial device opened: /dev/ttyUSB0: fd=8 brltty: Sending query at 9600bps brltty: Valid reply received. brltty: Display replied: 40 cells, version v5.0 brltty: Detected PowerBraille 40 brltty: Switched to 19200bps. Checking if display followed. brltty: timeout after 100 milliseconds brltty: Display did not respond at 19200bps, falling back to 9600bps. brltty: Valid reply received. brltty: Found display again at 9600bps. brltty: Must be a TSI emulator. brltty: Braille Display Dimensions: 1 row, 40 columns brltty: shifts: fwin=40 hwin=20 vwin=5 brltty: api link brltty: Braille Driver: ts [TSI] brltty: TSI Braille Driver: version 2.74 (April 2004) brltty: Braille Device: ttyUSB0 brltty: Help File: brltty-ts.hlp brltty: Help Page: /etc/brltty/brltty-ts.hlp[0] brltty: Preferences File: /etc/brltty-ts.prefs brltty: cannot open file: /etc/brltty-ts.prefs: No such file or directory brltty: beeper enabled brltty: tone: msec=60 note=64 brltty: tone: msec=100 note=69 brltty: api unlink brltty: Display idle: sending query brltty: Got reply to idle ping brltty: Display idle: sending query brltty: Got reply to idle ping brltty: api link brltty: Screen Font Map Size: 546 brltty: VGA Character Count: 512(large) brltty: attributes masks: font=0800 unshifted=F700 shifted=0000 brltty: Display idle: sending query brltty: Got reply to idle ping brltty: beeper disabled brltty: Display idle: sending query brltty: Got reply to idle ping
Rob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Mielke Sent: Tuesday, September 09, 2008 11:22 AM To: Informal discussion between users and developers of BRLTTY. Subject: Re: [BRLTTY] SEIKA THDZ 40 [quoted lines by Rob Meredith on 2008/09/09 at 10:08 -0400] >I'm not sure if THDZ means Treo in Japanese, but if it does, I never would >have figured that out. That's my error. :-) I was expecting English, so, when I read it quickly, my brain must've made "corrections" for potentially missing and/or extra dots. >The display has only a USB connector. Okay, the ttyUSBn devices would be the right ones to use. >I checked dmesg and /dev, and it is infact showing up as ttyUSB0. That makes sense. >I don't know if it only emulates a PowerBraille 40, or if it has its own >protocol. It seems like it would have its own protocol, but the manual isn't >telling. > >I guess I am now wondering how closely the display emulates the PowerBraille >40, and if something must be sent to the device to switch it into PowerBraille >40 mode. I haven't tried it on Windows yet, but according to the manual, you >just tell your screen reader you have a PowerBraille 40, and it works. Then it should work equally well with brltty. Can you run with: -ldebug (to log extra stuff) -e (to write logs via standard error) 2>/path/to/file (to redirect standard error to a file) Then please post the log so we can have a look at it. -- Dave Mielke | 2213 Fox Crescent | The Bible is the Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | May 21, 2011, is Judgement Day. EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | October 21, 2011, is the End. http://FamilyRadio.com/ | http://Mielke.cc/bible/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
