Hello again and thanks much for the quick and detailed response. I think for now I'll stick with the stable release and I'll keep trying with bluetooth. I did add the bluetooth address to the bluetooth device line. I think I can stop changing things up since I got the device to connect with the dongle. If I can get it to consistantly connect that way I agree, the internal one should work too. The typing was the first thing I noticed, and it worked quite well. Navigating was confusing, and I couldn't get the help file to load which I think would have helped me know what keys to hit for what functions. Anyway, I'll get back to you with further info when I fight with it some more. Thanks again for your patience with a total newbie. Have a great day... Cheereo!
On 1/5/20, Dave Mielke <[email protected]> wrote: > [quoted lines by tony seth on 2020/01/05 at 00:53 -0800] > >>does the BrailleMe work with streight usb as well as bluetooth? > > It didn't, but it should now. Are you able to build the latest development > code? > >>I've done a factory reset on my Brailleme > > That shouldn't have been necessary. Also, doing too many things at the same > time makes it much more difficult to figure out what any problem(s) might > be. > >>and re-installed Brltty > > Again, that shouldn't have been necessary. > >>so as to have a nice clean environment to start out from. > > I understand the goal. > > >From here, I've made sure that Brltty doesn't start when the computer >>starts, and have uncommented the Inceptor driver in the drivers list, and >>bluetooth in the devices list. > > Did you add the BrailleMe's Bluetooth device address to the braille-device > line? > >>I'm sticking to the command line method as I get more feedback from that. >> I've >>gotten the Brailleme to pair consistantly, > > That's a good idea. Note that you can use the -n option to make brltty stay > in > the foreground. When running it this way, use CTRL-C to stop it. > > You can also use the -L (uppercase) option to specify a log file, and you > can > use the -l (lowercase) option to tell brltty what to log. In this case, you > might use: > > -L/path/to/logfile > -ldebug,inpkts,bluetooth > > Then, if you'd like us to look through a log file you can attach it to a > post > to this list. > >>and have trusted the device, > > That isn't necessary. Trusting a device means that it, i.e. the device > iotself, > is allowed to start the Bluetooth connection. In this case, of course, it's > the > host (i.e. brltty) which is always starting the connection. > >>this time using an usb bluetooth dongle > > If you have internal Bluetooth then you shouldn't need to be doing it that > way. > Again, since too many things have changed at the same time, we don't know > at > this point. > > My guess is that you were actually successfully pairing before since, if > I'm > realling correctly, the BrailleMe was saying "connection failed". I don't > think > it'd have gotten that far if it weren't paired. > >>and actually got it to connect once out of many times. > > That's good news. > >>It worked very well, > > Do you mean for braille output, for typing, or for navigation. Braille > output > and typing should work well, but my personal opinion is that the key > bindings > for navigation may well not be working very well (yet). > >>but then I went to close the connection and the device locked up so I had >> to >>hard restart it. > > I suspect that that's a timeout issue. In other words, it might just be > that > you need to give the BrailleMe a short amount of time to realize that the > Bluetooth connection is gone. > >>I couldn't get it to connect after that, although I can get it to pair >>consistantly. > > You shouldn't need to be continually repairing it. If it's paired > successfully > once then it should stay paired until you unpair it. You can list the > currently > paired devices with bluetoothctl's paired-devices command. > > -- > I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ > Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/ > EMail: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke > Phone: +1 613 726 0014 | Canada K2A 1H7 | > _______________________________________________ > 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://brltty.app/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://brltty.app/mailman/listinfo/brltty
