PRE2018 3 Group13: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
No edit summary
 
(43 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== 1 Abstract ==
== Problem statement ==
<p>A robot which is able to read a book/form of text and is able to translate it into braille so that deaf-blind people can read it.</p>
Globally, around 356.000 people are deafblind, which means they cannot hear nor see. The way to communicate with these people is with braille writing. Regarding leisure, obviously, there are a lot of restrictions. Take for example reading books. Only around 1% of all books has been translated to braille, which means that people who are deafblind have very limited reading material. People that are just blind often will revert to listening to audio books, because there are so little braille books.


<sup>==== Test ====</sup>
=== Objective ===
Hello
The objective for this project is to make it possible for people to read all books in braille writing, by making a real-time translator which converts digital files to tangible braille. This way, people whose only choice to read books is by using braille, can read any book they want to, without being limited to the small number of books that have been printed in braille writing.
 
=== Target group ===
The group for which this project is relevant is deafblind people, as said. However, the people that will use the device that will be the solution to this problem will have to be able to read braille writing. However, this is not the only group at which the final product is aimed.
 
Visually impaired people do not always enjoy listening to audio books. Perhaps the circumstances do not allow for listening to an audiobook, or reading braille is perceived to be more comfortable. These people are also an important target group which will be taken into account when designing a solution to the stated problem.
 
== Abstract ==
On this wiki page, the project of group 13 will be fully described and explained. As stated in the Problem Statement, this project has to be about robotics, while keeping in mind the USE aspects. In chapter 3, it is explained what goals are set and how these goals will be reached. A role division and a planning is made, so the process is structured and the work is divided properly.
 
Chapter 4 will be about the user requirements. Of course, the users are a big part of the project and the user-friendliness will be one of the main points of focus. Thus, this chapter elaborates widely about different solutions to the posed problem, as well as researched the user experiences and preferences. This way, the user requirements can be set up to the user’s liking, so the end product will be as user-friendly as possible and therefore compliant with the USE aspects.


== 2 Problem statement ==
In chapter 5, the end products of the project will be described. Since two final products were made, as well as a conceptual addition to the found solution, this chapter is divided in separate sections, each elaboration on the different end products and the tasks that came along with them, such as programming and modelling.
<p>In this world, there is an estimate of around 356.000 deafblind people internationally. Only around 1% of all books are translated in braille which means that people who are deaf-blind have small amount of available reading material. Even the blind people will most often need to resort to audio books if they want to read a certain novel.</p>


=== Objective ===
A project cannot be complete without recommendations on further improvements. In chapter 6, it is explained what can still be improved upon and which steps can be added to further improve the outcome of the project.
<p>Make it possible for people whose only choice to read books is using braille to read books which are not translated in braille and give a choice to blind people who prefer to read in silence to do so.</p>
 
(Finally, the group reflects on their own process and explains which parts of the project should have been done differently, what could have enhanced the group process and what other steps could have been taken to get to a better result.)


=== Target group ===
<p>The users of our device will be people with visual and/or hearing impairments who know how to read braille. For the people with both visual and hearing impairments, they will use this product in order to read novels. For the people with just visual impairments, they will use the product incase they prefer to read in silence. Most visual impaired people have to resort to use audio books because of limited availability braille books.</p>


== 3 Approach ==
== Approach ==
<p>If we build a prototype of the mechanical part:
<p>For the mechanical prototype:<br/>
Firstly, we will research braille on which we can base our user requirements on. We then look for existing patents and their mechanics on a Braille output system and look for possible trade-offs. Once we have detailed insight on the possible solutions, we devise our own solution based on our design decisions that correspond to the user requirements.
Firstly, we will research braille on which we can base our user requirements on. We then look for existing patents and their mechanics on a Braille output system and look for possible trade-offs. Once we have detailed insight on the possible solutions, we devise our own solution based on our design decisions that correspond to the user requirements.
We make a concept to visualize our idea and eventually we will make a (physical) prototype that can be tested with our target users.</p>
We make a concept to visualize our idea and eventually we will make a (physical) prototype that can be tested with our target users.</p>


<p>If we only focus on user-friendliness<br />
<p>For the user-friendliness:<br />
Firstly, we will research braille on which we can base our user requirements on. We then look for the most user-friendly materials and user-interface so we can improve the user-friendliness of the machine.</p>
Firstly, we will research braille on which we can base our user requirements on. We then look for the most user-friendly materials and user-interface so we can improve the user-friendliness of the machine.</p>


=== Milestones ===
=== Milestones ===
<p>Have digital text be the input of a reusable interface where the text is converted to braille. The braille can be projected per word or group of words, depending on their length.
<p>Have digital text be the input of a reusable interface where the text is converted to braille. The braille can be projected per word or group of words, depending on their</p> length.
Choose the research topic
<ul>
Summarize a State-of-the-Art by performing a literature study
<li>Choose the research topic </li>
Find a contact person that fits our target user group to gather additional information regarding our case
<li>Summarize a State-of-the-Art by performing a literature study</li>
Create user requirements for the robot
<li>Find a contact person that fits our target user group to gather additional information <il>regarding our case</li>
Validate the requirements with the contact person  
<li>Create user requirements for the robot</li>
Design a concept build corresponding to the requirements
<li>Validate the requirements with the contact person </li>
Validate the concept with the contact person
<li>Design a concept build corresponding to the requirements</li>
Build a prototype of our concept and test it with the contact person
<li>Validate the concept with the contact person</li>
Produce a final presentation in which we discuss the process, design and prototype</p>
<li>Build a prototype of our concept and test it with the contact person</li>
<li>Produce a final presentation in which we discuss the process, design and prototype</li>
</ul>


=== Deliverables ===
=== Deliverables ===
<p>Compact, user-friendly and cost-efficient physical braille interface. The Braille interface should accept digital text and convert it to several Braille characters at a time.
<p>Compact, user-friendly and cost-efficient physical braille interface. The Braille interface should accept digital text and convert it to several Braille characters at a time.
User-friendliness consists of:
User-friendliness consists of: </p>
Type of material to interact with
<ul>
Speed of the machine
<li>Type of material to interact with </li>
Possible physical interaction with buttons/triggers (functionality)</p>
<li>Speed of the machine </li>
 
<li>Possible physical interaction with buttons/triggers (functionality) </li>
</ul>
<p>Possibly a working prototype of one or several letters, that can be reset and configures itself to a given input.</p>
<p>Possibly a working prototype of one or several letters, that can be reset and configures itself to a given input.</p>


Line 46: Line 57:
<ul>
<ul>
<li>Material choice <ul><li>Dennis</li></ul> </li>
<li>Material choice <ul><li>Dennis</li></ul> </li>
<li>User interface (layout, buttons etc.) <ul><li>Thomas</li></ul> </li>
<li>User interface and requirements <ul><li>Thomas</li></ul> </li>
<li>Converting feedback of test person to useful information <ul><li>Luc</li></ul> </li>
<li>Hardware modelling <ul><li>Luc</li></ul> </li>
<li>Hardware internals stuff <ul><li>Luc</li></ul> </li>
<li>Prototype builder <ul><li>Simon</li></ul> </li>
<li>Builder <ul><li>Simon</li></ul> </li>
<li>Programmer <ul><li>Dirk</li></ul> </li>
<li>Programmer if we build a 6-segment letter prototype <ul><li>Dirk</li></ul> </li>
</ul>
</ul>


Line 56: Line 66:
The planning of the project can be found [[0LAUK0 PRE2018 3 Group 13 Planning|here]].
The planning of the project can be found [[0LAUK0 PRE2018 3 Group 13 Planning|here]].


== 4 User requirements ==
== User requirements ==
We will need a way to convert (digital) text to braille and we can do it as follows: <br>
We will need a way to convert (digital) text to braille and we can do it as follows: <br>


Line 66: Line 76:
We have a seperate page for the literature study which contains summaries of knowledge relevant to braille and its users. From systems, mechanisms to its perception and standards.
We have a seperate page for the literature study which contains summaries of knowledge relevant to braille and its users. From systems, mechanisms to its perception and standards.
The page can be found [[0LAUK0 PRE2018 3 Group 13 SotA Literature Study|here]].  
The page can be found [[0LAUK0 PRE2018 3 Group 13 SotA Literature Study|here]].  
==== Mechanisms ====
Here, existing solutions (mechanisms) can be described. Other subdivisions can be made separately in this chapter.


=== Material study ===
=== Material study ===
Line 77: Line 84:
Therefore we have decided to look for existing surveys that relate to our users and questions. The results of all user surveys are on [[0LAUK0 PRE2018 3 Group 13 User Research|this]] page.
Therefore we have decided to look for existing surveys that relate to our users and questions. The results of all user surveys are on [[0LAUK0 PRE2018 3 Group 13 User Research|this]] page.


== 5 Final results ==
 
== Final results ==
In this chapter, the final results will be described, as well as the process of getting to these results.
In this chapter, the final results will be described, as well as the process of getting to these results.


=== Sentence (dummy) ===
=== Sentence (dummy) ===
We designed to demonstrate the look and scale of the braille surface, this involes 3d models and a somewhat simplified 3d printed product. More detail [[0LAUK0 PRE2018 3 Group 13 Dummy_sentence|here]].


==== Casing (dummy)====
The second part of the dummy will be the casing. This casing refers to the outside of the dummy which is used to provide an estimate of the size of our robot and a base on which the other parts will be attached to. Since we focus more on the reading aspect, for the base a simple box would be sufficient. The dimensions of this box will most likely depend on the needed estimated space for the hardware and the size of the braille display.  An important thing to take into consideration when creating the casing, will be to consider interaction between the braille display dummy and the casing itself. For example, in case you want to change the letters of braille on the display, the casing should allow for a display to be removed and reattached.


=== Letter (solenoids) ===
=== Letter (solenoids) ===
 
For the function prototype we have created one functional letter. This letter accept pdf intput and displays the text one by one letter controlled by a button. The letter is represented by solenoids and the software shows its workings on the connected computer. More details on the functioning and the creation process are  [[0LAUK0 PRE2018 3 Group 13 Letter_software|here]].
 
==== Software ====
 


=== Concept interface ===
=== Concept interface ===
We have created a conceptual interface for how the product would look in reality, this mostly concerns where the buttons for refreshing and toggeling automatic refreshing have to be placed. More detail [[0LAUK0 PRE2018 3 Group 13 Concept_interface|here]].


== Further improvement and future work ==
We are happy about our one letter prototype but if our product was to be produced, the refreshable braille display would obviously contain more letters. This would be easily achievable with a larger budget, as it is basically creating multiple single letter displays and connecting them. As for functionality, it would mostly stay the same.


== 6 Further improvement and future work ==
We would also change the size of our prototype. For our one-letter prototype we prioritized accessibility over compactness, since we had limited time and a limited budget. We chose to get the solenoids that we could easily acquire in a short period of time. There isn’t much choice for different sizes on the market. If our product were to go in production we would ideally be able to make (or have access to) custom sized (smaller) solenoids so we could fit everything in a much smaller case. Same goes for the batteries, we would use smaller lithium battery packs, as opposed to multiple AA batteries that take up lots of space. We would then incorporate our design idea for the casing into the product, with the letters and buttons positioned conveniently for the reader. We would add a “previous” button, to return to the previous line, and optionally a motion sensor for continuing to the next line.
 
 
== 7 Reflection (OPTIONAL) ==
If we have time left, we can add a Reflection chapter to evaluate the project. 
<h4>Braille to Arduino</h4>
<p>
We're using an Arduino Uno with 6 outputs which represents a braille character.
For testing purposes, we'll be using LEDs for these 6 outputs.
Serial Monitor is used for input. Enter the numbers of the LEDs you want to enable (eg. 1256).
After you press “send” on the interface or “enter” on your keyboard, the lights corresponding to the number input will light up.
We've also added a button and by pressing it, you can reset all lights (the Braille output).
</p>
 
<h4>Defining the output of Arduino to Braille</h4>
 
<p>
[[File:electromagnet.png]]
[[File:transistor.png]]
 
An electro magnet (suited for Arduino) can be turned on and off via a digital pin. The current through the Arduino itself is too weak for it to operate, so we need an external power supply (battery). Then, to regulate the voltage we’ll need a transistor.
 
Alternatively, we can also use relays. The Arduino would power the On/Off action of the relay and an external power supply can power the magnet.
 
We’ll need 6 electro magnets, 6 transistors (or relays if we go for that option), and one battery.
 
To reverse polarity of an electro magnet we can use the transistor, simply switch the output of the two transistor pins.
</p>
 
<h4>Serial communication between Windows and Arduino</h4>
<p>
We’ll be using Serial communication to connect our Windows software (PDF to binary output) to our Arduino software (binary output to solenoid).
And in order to do that, we’ll be using the following library.
https://sourceforge.net/projects/javaarduinolibrary/
As we do not have all the parts yet for the solenoid, we’ll be using LEDs for now. It’s the same principle.
</p>
<p>
We can for instance send an output of 111000, it will be communicated to the Arduino via the Serial port, and the Arduino will enable the first 3 of the 6 LEDs.
[[File:arduino3leds.jpg]]
</p>
 
<h4>Solenoid & Serial communication testing</h4>
<p>We have acquired a single solenoid for testing purposes. Our main goal was to find out if the solenoid we got was of good quality and if the strength of the solenoid was sufficient (can we push it down “accidentally” while reading?), before we invest in 6 of them. We did at first get a faulty solenoid, but the second one we got is perfect. After a lot of testing we could conclude that the solenoid is powerful enough and works reliably.</p>
 
<p>We have made a program to test both our solenoid and serial communication, while also gaining some more experience with GUIs (which will be used in our final product). </p>
 
<p>
To connect to the Arduino from Windows, we have made a port selection GUI. Select the COM port, and click on connect.<br/>
[[File:selectport.png]]
</p>
 
<p>
We have added two simple functions: “Pin up” and “Pin down”. These buttons control the state of the solenoid.<br/>
[[File:controlpanel.png]]
</p>
 
<p>
The single solenoid testing setup. <br/>
[[File:singlesetup.png]]
</p>
 
<p>
We’ll be buying 5 more solenoids next. (for complete braille input we require 6 pins)
</p>
 
<h4>Finalizing the functional prototype (hardware)</h4>
<p>We now have 6 solenoids in total, to display a single braille character. Every single solenoid is connected to a transistor to regulate the current and voltage, a diode to prevent current from flowing back, and a 220 Ohm resistor. We have a button to continue to the next character (from the loaded text file).</p>
 
<p>To power this all, we’re using a 9V battery connected to a 5V converter (because our solenoids can only handle 5V), connected directly to the solenoids. The reason we’re connecting the battery directly to the solenoids is because we ran into an issue earlier when connecting them to the 5V from the Arduino. The Arduino would crash, trying to supply too much current to power the 6 solenoids.</p>
 
<p>[[File:fprototype.png]]</p>
 
<h4>Functional prototype finished</h4>
 
<p>We have now finished the functional prototype. We encountered another power issue, namely that the solenoids would be getting a bit inconsistent after the 9V battery has drained a little. They weren’t getting enough current. We solved this issue by replacing the 9V battery with a 6X AA battery pack. After the circuit was perfectly working, we finished the software for the PC. We extended the software such that you first have to select the COM port (to connect to the Arduino), then you select the PDF file that you would like to read, and finally a window will pop up informing you about the state of the Arduino and the letters (and Braille output) sent.</p>
<p>[[File:com.png]]</p>
<p>[[File:pdf.png]]</p>
<p>[[File:window.png]]</p>
 
<h4>3D modelling the mechanism</h4>
For the 3D modelling of the mechanism, several iterations will be made of different ideas. The model will keep changing because used methods or components will change. First a single dot of a braille letter was modelled, using some assumed dimensions for the parts. The technical drawing of this model can be seen below as a section of the complete pin.
 
[[File:Braille_dot.png]]
 
Then, six of these dots were used to model one complete braille letter, as is one of the goals for the end of the project. However, the model changed because we chose to use a different mechanism. The whole model was made from scratch, to include a solenoid mechanism with a cam and follower. This model can be seen below.
 
[[File:Braille_letter_V2.jpg]]
 
Also, a model was made of a pad of arbitrary length with several letters next to each other. This could be used for the dummy, but is also a help to visualize how much space we will have. The eventual length of the pad will be decided upon when the user-requirement list is set up.
 
[[File:Braille_display.png]]
 
 
<h4> braille dot distance research </h4>
 
The braille standards are different all around the world. The exact reasoning for these standards are nowhere to be found, however there was an article about how much you can feel with your body,  which found out that the human finger is able to detect objects of a size of 2.3mm. Most values of the braille standards had a distance of between dots for around this value. While I did not find any further research to support my claim, I believe that the dot distance is based on this found value.
Because I can not find what the exact reasonings for the differences between the values are, I suggest that we go for the electronic braille standards since we our robot falls within this category.
 
https://www.pharmabraille.com/pharmaceutical-braille/marburg-medium-font-standard/
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3928539/
https://cdn.discordapp.com/attachments/140133975606689793/557703767332618260/Meier_FootFeedback_iWOAR2015.pdf
 
==converting a pdf file to braille code==
 
Using http://braillebug.afb.org/braille_deciphering.asp for general braille rules.
 
We can describe a 6-pin braille symbol by the position of the ‘active’ pins. In order from top to bottom and then left to right. We can represent this as a boolean vector or equivalent binary number. The symbol ‘a’ for example becomes 100000.
 
 
Conversion rules:
*Each letter in the alphabet and some symbols are converted to the corresponding braille code. (using a table)
*A capital letter is made by adding 000001 in front of the normal code.
*A capitalised word is made by adding the 0000001 symbol twice before it. (what if the only non-capitalised symbols in a word are not letters?)
*A number is made by placing 001111 in front of the symbols for the letters that correspond to the digits. For example a=1,b=2 so  12 = 001111 100000 110000
*000011 must be placed between a number and a letter if the letter directly follows the number
*Some groups of letters get contracted to a single symbol or multiple (but less) symbols. (using a table)
 
 
 
 
Currently we have written a program in java that accepts a pdf file and outputs a txt file with the text translated symbol by symbol to braille. The braille is encoded as described above.
 
TODO:
Apply word context dependent rules including the number and letter prefixes.
Add a way for the user to supply character translations so that things like language specific translation can be added when needed.
Pass the translation to the arduino.
 
 
===V2===
 
 
DONE:
Segregation into words.
Word specific number and letter symbols.
Contractions for full words, prefixes and suffixes. A full list of these is not implemented and has to be provided, what kind of contractions people want to read also differs from person to person (grade 2 and grade 3  braille).
 
PROBLEMS:
*Complicated grammar rules like mentioned in https://en.wikipedia.org/wiki/English_Braille :
“When there are several ways to write a word, the shortest one is chosen, and when they are of equal length, the one without (two-cell) abbreviations is chosen. So, thence is written th-ence (3 cells) rather than the-n-c-e (4 cells). However, with the sequences -anced, -ancer, -enced, -encer, the form with -ance/-ence is used even if not shorter.”
“In general, these are acceptable as parts of longer words as long as they retain their pronunciation”
 
Some of these could be practically impossible to implement, for example when pronunciation is mentioned.
 
*Currently capitalized parts words are not contracted unless this part is also capitalised in the list of contractions used by the program. (this could actually be the desired behaviour)
 
*Contractions containing punctuations symbols cannot be recognized right now because they are not considered part of the word. (luckily I don't think these exist)
 
 
We are choosing to ignore the more complicated situations since we do not even know if most people can read these kind of contractions.
 
 
===description of the algorithm===
*The algorithm looks for the next word in the text. A word is a sequence of symbols which is between 2 symbols that are not alphanumeric (e.g. punctuation and whitespace)
*All symbols that are between this word and the previous word are translated to the corresponding braille symbol (punctuation and whitespace)
*A table is used to look for possible contractions for the whole word, a prefix or a suffix. The contracted part of the word is then removed an*d the contraction is saved.
*The rest of the word is translated symbol for symbol while also adding the symbols indicating capitalization and numbers.
 
 
== Final results ==
<p> In the next section, we will split the final results were split into two product: a dummy sentence and a working refreshable letter. The main reason is to reduce costs, since a fully working sentence would be very costly and not on a true scale. </p>
 
<h4>The dummy sentence</h4>
The wiki section on the dummy sentence can be found [[0LAUK0 PRE2018 3 Group 13 Dummy_sentence|here]].
 
<h4> The casing </h4>
<p>The second part of the dummy will be the casing. This casing refers to the outside of the dummy which is used to provide an estimate of the size of our robot and a base on which the other parts will be attached to. Since we focus more on the reading aspect, for the base a simple box would be sufficient. The dimensions of this box will most likely depend on the needed estimated space for the hardware and the size of the braille display.  An important thing to take into consideration when creating the casing, will be to consider interaction between the braille display dummy and the casing itself. For example in case you want to change the letters of braille on the display, the casing should allow for a display to be removed and reattached. </p>
 
==Sources for materials ==
<p>[1]https://www.the-warren.org/ALevelRevision/engineering/Materialclasses.html</p>
<p>[2]https://www.engineeringtoolbox.com/young-modulus-d_773.html</p>
<p>[3]http://burncentrecare.co.uk/about_burned_skin.html https://www.orfit.com/faq/what-are-low-temperature-thermoplastic-materials-lttps/</p>
<p>[4]https://agmetalminer.com/metal-prices/carbon-steel/</p>
<p>http://www.campaignforwool.org/about-wool/ </p>
<p>http://bieap.gov.in/Pdf/CGTPaperII.pdf </p>
<p>https://global.kyocera.com/fcworld/charact/strong/rigidity.html </p>
<p>https://www.engineeringtoolbox.com/ceramics-properties-d_1227.html </p>
<p>http://www.dynacer.com/properties/ </p>
<p>http://www.newworldencyclopedia.org/entry/Elastomer </p>
<p>https://www.britannica.com/science/elastomer</p>
<p>https://en.wikipedia.org/wiki/Thermosetting_polymer</p>
<p>https://en.wikipedia.org/wiki/Thermoplastic</p>
<p>https://www.onealsteel.com/carbon-and-alloy-steel.html</p>
<p>https://www.metalsupermarkets.com/what-is-chromoly/</p>
<p>https://www.economicshelp.org/blog/301/concepts/understanding-elasticity/</p>

Latest revision as of 23:59, 10 April 2019

Problem statement

Globally, around 356.000 people are deafblind, which means they cannot hear nor see. The way to communicate with these people is with braille writing. Regarding leisure, obviously, there are a lot of restrictions. Take for example reading books. Only around 1% of all books has been translated to braille, which means that people who are deafblind have very limited reading material. People that are just blind often will revert to listening to audio books, because there are so little braille books.

Objective

The objective for this project is to make it possible for people to read all books in braille writing, by making a real-time translator which converts digital files to tangible braille. This way, people whose only choice to read books is by using braille, can read any book they want to, without being limited to the small number of books that have been printed in braille writing.

Target group

The group for which this project is relevant is deafblind people, as said. However, the people that will use the device that will be the solution to this problem will have to be able to read braille writing. However, this is not the only group at which the final product is aimed.

Visually impaired people do not always enjoy listening to audio books. Perhaps the circumstances do not allow for listening to an audiobook, or reading braille is perceived to be more comfortable. These people are also an important target group which will be taken into account when designing a solution to the stated problem.

Abstract

On this wiki page, the project of group 13 will be fully described and explained. As stated in the Problem Statement, this project has to be about robotics, while keeping in mind the USE aspects. In chapter 3, it is explained what goals are set and how these goals will be reached. A role division and a planning is made, so the process is structured and the work is divided properly.

Chapter 4 will be about the user requirements. Of course, the users are a big part of the project and the user-friendliness will be one of the main points of focus. Thus, this chapter elaborates widely about different solutions to the posed problem, as well as researched the user experiences and preferences. This way, the user requirements can be set up to the user’s liking, so the end product will be as user-friendly as possible and therefore compliant with the USE aspects.

In chapter 5, the end products of the project will be described. Since two final products were made, as well as a conceptual addition to the found solution, this chapter is divided in separate sections, each elaboration on the different end products and the tasks that came along with them, such as programming and modelling.

A project cannot be complete without recommendations on further improvements. In chapter 6, it is explained what can still be improved upon and which steps can be added to further improve the outcome of the project.

(Finally, the group reflects on their own process and explains which parts of the project should have been done differently, what could have enhanced the group process and what other steps could have been taken to get to a better result.)


Approach

For the mechanical prototype:
Firstly, we will research braille on which we can base our user requirements on. We then look for existing patents and their mechanics on a Braille output system and look for possible trade-offs. Once we have detailed insight on the possible solutions, we devise our own solution based on our design decisions that correspond to the user requirements. We make a concept to visualize our idea and eventually we will make a (physical) prototype that can be tested with our target users.

For the user-friendliness:
Firstly, we will research braille on which we can base our user requirements on. We then look for the most user-friendly materials and user-interface so we can improve the user-friendliness of the machine.

Milestones

Have digital text be the input of a reusable interface where the text is converted to braille. The braille can be projected per word or group of words, depending on their

length.

  • Choose the research topic
  • Summarize a State-of-the-Art by performing a literature study
  • Find a contact person that fits our target user group to gather additional information <il>regarding our case
  • Create user requirements for the robot
  • Validate the requirements with the contact person
  • Design a concept build corresponding to the requirements
  • Validate the concept with the contact person
  • Build a prototype of our concept and test it with the contact person
  • Produce a final presentation in which we discuss the process, design and prototype

Deliverables

Compact, user-friendly and cost-efficient physical braille interface. The Braille interface should accept digital text and convert it to several Braille characters at a time. User-friendliness consists of:

  • Type of material to interact with
  • Speed of the machine
  • Possible physical interaction with buttons/triggers (functionality)

Possibly a working prototype of one or several letters, that can be reset and configures itself to a given input.

Role division

  • Material choice
    • Dennis
  • User interface and requirements
    • Thomas
  • Hardware modelling
    • Luc
  • Prototype builder
    • Simon
  • Programmer
    • Dirk

Planning

The planning of the project can be found here.

User requirements

We will need a way to convert (digital) text to braille and we can do it as follows:

Create a robot which is able to translate e-books into braille so that the users can read it (with translate we do not mean to write a new book with the translation but instead some other form of reusable interface).

In order to determine fitting user requirements, we have broken down our research into different sections in which we look at general literature studies, user focused research and materials for the braille interaction. From these sections we draw our overall user requirements, which can be found at: https://drive.google.com/open?id=1D0T3C2wYtNyWK7ZE4wtTIpXq9gRA280T4eBAQZk00WI

State-of-the-Art literature study

We have a seperate page for the literature study which contains summaries of knowledge relevant to braille and its users. From systems, mechanisms to its perception and standards. The page can be found here.

Material study

For materials we’ll first look into materials which can act as a cover over the pins of the robot. For this to be possible, the material would need to be sufficiently elastic. With this approach we aim to provide a good user experience which might be hindered by the spaces and inconsistencies that a non-elastic braille display would provide. This inconsistencies might be created because of faults in the connection between the braille display and the pins or unintended deformation of the braille display. Based on the feedback we’ll receive from our interviews, we might look into the non-elastic materials. Further in depth information can be found here.

User research

Besides the literature study, we would like more direct involvement from our target group as well. To involve them in the design and development process and in order to do so, we have attempted to contact several institutes and communities for blind people both through phone calls and online posts. Unfortunately, the amount of responses we got is low and we only managed to get a few of our survey filled in. Therefore we have decided to look for existing surveys that relate to our users and questions. The results of all user surveys are on this page.


Final results

In this chapter, the final results will be described, as well as the process of getting to these results.

Sentence (dummy)

We designed to demonstrate the look and scale of the braille surface, this involes 3d models and a somewhat simplified 3d printed product. More detail here.

Casing (dummy)

The second part of the dummy will be the casing. This casing refers to the outside of the dummy which is used to provide an estimate of the size of our robot and a base on which the other parts will be attached to. Since we focus more on the reading aspect, for the base a simple box would be sufficient. The dimensions of this box will most likely depend on the needed estimated space for the hardware and the size of the braille display. An important thing to take into consideration when creating the casing, will be to consider interaction between the braille display dummy and the casing itself. For example, in case you want to change the letters of braille on the display, the casing should allow for a display to be removed and reattached.

Letter (solenoids)

For the function prototype we have created one functional letter. This letter accept pdf intput and displays the text one by one letter controlled by a button. The letter is represented by solenoids and the software shows its workings on the connected computer. More details on the functioning and the creation process are here.

Concept interface

We have created a conceptual interface for how the product would look in reality, this mostly concerns where the buttons for refreshing and toggeling automatic refreshing have to be placed. More detail here.

Further improvement and future work

We are happy about our one letter prototype but if our product was to be produced, the refreshable braille display would obviously contain more letters. This would be easily achievable with a larger budget, as it is basically creating multiple single letter displays and connecting them. As for functionality, it would mostly stay the same.

We would also change the size of our prototype. For our one-letter prototype we prioritized accessibility over compactness, since we had limited time and a limited budget. We chose to get the solenoids that we could easily acquire in a short period of time. There isn’t much choice for different sizes on the market. If our product were to go in production we would ideally be able to make (or have access to) custom sized (smaller) solenoids so we could fit everything in a much smaller case. Same goes for the batteries, we would use smaller lithium battery packs, as opposed to multiple AA batteries that take up lots of space. We would then incorporate our design idea for the casing into the product, with the letters and buttons positioned conveniently for the reader. We would add a “previous” button, to return to the previous line, and optionally a motion sensor for continuing to the next line.

Retrieved from "https://dsdwiki.wtb.tue.nl/index.php?title=PRE2018_3_Group13&oldid=73039"