[BRLTTY] Focus 1 70 display and USB to serial adapter: possible connecting this scenario?

[Hammer Attila]

Hi Dave,


Very thank you the entire help with you doing for me. I not known 
detailed the BRLTTY logging options practices (yet). :-):-)

Tomorrow I will generate you a full english language log file with you 
suggested with serial communication related (when I use the usb to 
serial adapter).

I tested the serial port with minicom utility, the cable is working 
fortunatelly, perhaps need tweaking BRLTTY related settings this 
scenario related.

I used the sudo minicom -b 9600 -D /dev/ttyACM0 command to test the cable.


I would like finding in Focus1 model why not working the automatic USB 
detection, because interesting this issue too.

When I generating for you an USB connection related log file a second 
thread (for example focus 1 70: usb autodetection problem addressed 
thread), what -l option use with debug purpose?

The -ldebug,usb,inpkts,outpkts option is good?

If I remember correct BRLTTY 6.7 still supporting based the reference manual section 8 with Focus 1 modell with USB connection mode too.
Link:
https://brltty.app/doc/Manual-BRLTTY/English/BRLTTY-8.html
I will reading importanter parts the documentation main page, because since when last time I readed the documentation, lot of things changed.

Attila

2024. 12. 22. 20:51 keltezéssel, Dave Mielke írta:
> [quoted lines by Hammer Attila on 2024/12/22 at 14:24 +0100]
>
>> In syslog I see now following error message, translate to english for you in
>> Ubuntu 20.04, BRLTTY 6.5:
>>
>> Dec 22 14:01:56 hammera-pc brltty[1410]: unable to connect to polkit:
>> g-io-error-quark (159) Error initializing authority: Could not connect: No
>> such file or directory (1)
>>
>> What file missing for BRLTTY and polkit related? When I used the my Alva
>> display with USB connection, I not see similar error messages.
> I'm not sure. It'd be helpful for me to see the whole log. A way to get brltty to log in English is to override the system's locale with the $LANG environment variable. Invoking brlttyu like this should work:
>
>     LANG=C brltty -b fs -d serial:ttyACM0
>
> One thing you might check is that the device name still is ttyACM0. The number on the end is dynamically assigned so it's always possible that it isn't 0.
>
> When logging, please use -l (lowercase) to specify at least these ctegories:
>
>     -ldebug,serial,inpkts,outpkts
>
>> Another interesting error messages:
>>
>> Dec 22 14:01:59 hammera-pc brltty[3886]: can't isolate namespaces
> ...
>
> Those are from a different brltty process that's running on yur system in order to support the graphical environment. You can tell because the braille driver is ba (BrlAPI) and the screen driver is a2 (AT-SPI-2). The best way to get the logs just for the brltty process that you're debugging is to use its -L option to direct those logs to a specific file.
>
>> Perhaps me need trying buying a 9 pin serial connector cable to the
>> motherboard connector if not have better ydea.
> I don't think that'd be necessary.
>
>> Unfortunatelly the display USB port with usb cable is unusable the BRLTTY 6.5
>> and higher version, because shows following error message the log file:
>>
>> [brltty] USB URB status error 75: The value is too large for the specified
>> data type
>> 2024-03-31 at 14:28:26.852  [brltty] USB: endpoint descriptor not found: 00
> Again, I think I'd like to see the whole log in order to try to figure this one out.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20241222/1bc2ef2a/attachment-0001.htm>