Hi Dave,
The stty -F /dev/ttyS0 -a command shows following output when Focus 1
display is use in real serial connection the /dev/ttyS0 port (the
display this situation full functional and right presents Orca output in
Mate Terminal):
speed 57600 baud; rows 0; columns 0; line = 0;
intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>;
eol = <undef>; eol2 = <undef>; swtch = <undef>; start = <undef>; stop = <undef>;
susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>;
discard = <undef>; min = 0; time = 0;
-parenb -parodd -cmspar cs8 -hupcl -cstopb cread clocal -crtscts
ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0
ff0
-isig -icanon iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt
-echoctl -echoke -flusho -extproc
Hopefully this information help, this is the right result when happens a
real serial to serial connection.
Interesting this right result, I looked the stty -F /dev/ttyACM0 device
when attached the focus display, you will be see the difference what
happens when I trying attaching the USB serial cable between the
computer USB port and the Focus1 display real serial port.
Default wrong baud rate calibrate I think the serial dongle (9600 baud)
the /dev/ttyACM0 device, and the other data fields is possible wrong.
Looks following lines:
speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt
= ^R;
werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon
-ixoff
-iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke -flusho -extproc
So, I try founding a command how can possible changing on the fly the
USB dongle baud rate, and an Ubuntu forum founded following command
suggestion:
screen ttyACM0 57600
Not the best way, but this command works, beginning working the Focus
display with USB serial cable the /dev/ttyACM0 device, until restart not
happening.
After screen ttyACM0 57600 command the stty -F /dev/ttyACM0 -a command
shows following right result:
speed 57600 baud; rows 0; columns 0; line = 0;
intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof =
<undef>;
eol = <undef>; eol2 = <undef>; swtch = <undef>; start = <undef>; stop =
<undef>;
susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>;
discard = <undef>; min = 0; time = 0;
-parenb -parodd -cmspar cs8 -hupcl -cstopb cread clocal -crtscts
ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon
-ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
bs0 vt0 ff0
-isig -icanon iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop
-echoprt
-echoctl -echoke -flusho -extproc
I tested this solution with my newer machine and notebook, works perfect.
Only the baud rate need store persistent, the brltty.conf file not
provide possibility the FS driver to set serial baud rate if a display
is attached with usb serial adapter?
With your help, I can use this old Focus 1 display on a traditional
serial port and with the USB serial converter on my newer machines,
where there is no physical serial port, this help was a lifesaver for me
in terms of Hungarian Braille developments, because Braille board
developments can best be tested with a real Braille display.
But why the automatic detection of the display does not work with the
original traditional USB cable is a good question.
Thank you for your help.
Attila
2024. 12. 23. 19:09 keltezéssel, Dave Mielke írta:
[quoted lines by Hammer Attila on 2024/12/23 at 12:53 +0100]
With safe testing environment the building related, I am use now the Debian
12 awailable 6.7 version sources when changing the you wrote baud related
line into the driver file (temporary I will doing my local machine a quilt
patch for BRLTTY package the baud change related and recompile and reinstall
the packages).
You can test without installing as you can run brltty right out of the build
tree via the run-brltty script in its top-level directory. It takes exactly the
same options as brltty itself.
This line change affects only with Focus 1 series models, other Freedom
Scientific displays is unaffected this change related if need final applying
this change the official code base?
Yes, that'll be a problem but we can deal with it later if it turns out to be
necessary.
So, a thing is absolute sure: general serial connection mode with general
serial port and general 9 pin serial cable is working, so the display is
usable,
On that system, with direct serial support, please do the following command
while brltty is running with the device:
stty -F /dev/ttyS0 -a
The first line of that output will tell you what baud the device - ttyS0 - is
currently set to.
If it happens that you don't have time to respond during the holidays, no
problem, I wish everyone who celebrates Christmas a happy holiday.
Don't worry about that. Specific days that commemorate events don't matter to
me. If some event matters to me then I'm in a permanent state when it comes to
caring about it and don't need some special day to make it matter.
When it comes to Christmas, by the way, the whole world seems to have its date,
i.e. the date on which Jesus was born, completely wrong. A huge hint to this is
that the Herod who had all the babies around Bethlehem killed who were less
than two years old died in 4BC. This doesn't make the "Bible wrong, though,
because it itself points to the year 7BC for when He was born. The chain of relevant
events is as follows:
Zechariah (John the baptizer's father) served in the temple during the course
of Abijah, which was the 8th of 24 courses throughout the Hebrew year. In 8BC,
the second half of the fourth Hebrew month was roughly the last two weeks of
June. Elizabeth (John's mother), therefore, would've conceived in early July,
i.e. shortly after Zechariah returned home from his temple duties.
When Mary was told that Jesus would be conceived, we're also told that this was
during the sixth month of Elizabeth's pregnancy. This brings us, therefore,
pretty much to the end of 8BC.
We then add a full-length pregnancy for Mary and we land near the start of
October. When we look at the Hebrew calendar for 7BC we find that the Day of
Atonement was October 2 (I think - memory could be wrong on this point). While
the Bible dosn't explictly say that Jesus was born on the Day of Atonement,
it's indeed a day that very accurately prefigures the event. It's the day on
which the high priest would put off all of his glorious garments and put on
simple clothing, which is exactly a figure of what Jesus actually did do by
leaving Heaven and joining us here on this earth as, to all appearances, a
fellow human being.
If my English is not completely good, don't be angry with me. :-):-)
Now why would I be angry with someone just because his English isn't perfect?
That just isn't the way I think. We all belong to the very same single race -
the Human Race - as fellow citizens of this world.
_______________________________________________
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
