Hopefully This repo will grow over time. Currently, it contains some tests for a circular linked list I implemented today.
Watch this space…
]]>Today the staff published one of my posts. They called it “Something Doubly Amazing”, which is not the title I gave but works well enough. I hope it helps people get a tiny bit of an idea of what it is like to study on a campus with students in your course and people who also have the same beliefs as you.
Enjoy.
]]>It is taught by Dr. Bryan Duarte of Arizona State University. Workshops are conducted on Zoom each week and there is a mailing list where both announcements and discussion threads are posted, which can be joined here.
So far, only one session has been conducted, where the participants have mainly introduced themselves and done some very introductory work with the Python Shell (console), being introduced to very basic types with variable names and assignments.
The sessions appear to be pretty easy-going and not too fast-paced. I would recommend it for anyone who would like to either learn the language, or at least more solidly consolidate one’s Python knowledge.
]]>Currently I either have added (or am in the process of adding) the following features to Splashkit:
You can view my contributor rank and up-to-date individually committed contributions on the parent Splashkit core SDK repository.
]]>Mostly these are quite helpful for independently navigating the physical layout of boards, connecting wires, etc. They are left here as a hopefully helpful compilation; though a google search should turn up these results anyway.
I did want to add one final note on board orientation. Mostly you can figure it out from the description given on the Blind-Arduino Blog; but there could be one added helpful note made, namely that to orientate the board correctly, the power supply port should be on the top-left and the USB port should be on the top-right.
It’s been an interesting journey trying to figure some of this stuff out. My hope is mainly that by referencing these links here, combined with some meta tags on this site and Google’s layered search algorithm, it may be more likely that these resources will pop up in search results, hence the somewhat abruptness of this post.
]]>It allows for data to be collected from a basic hardware Carbon Monoxide sensor, namely the DFRobot MQ7. It collects gas readings between 20 and 20,000 particles per million (PPM). when collecting the data, it logs the results to a Comma-separated values (CSV) file on an inserted SDHC memory card.
It has been tested and runs well on an Arduino UNO r3 with an Arduino-compatible data logging shield. The sensor requires at least four pins (including the data logging) for this code to work (one analog, one digital, one 5v and one ground).
Obviously, it requires external calibration for the data to be accurate, which can only be done if you have another sensor to compare with, or use a calibration kit. Licensed under GNU LGPL as necessitated by DFRobot.
It is relatively simple to use and implement. If you purchase an arduino board, all you have to do is just:
If you are allergic to graphical interfaces, or are sight-impaired and / or do not have the Java Access Bridge (JAB) – which is quite out-of-date anyway and will probably become increasingly unusable over the years – then you can always use the Arduino-CLI, the Arduino command-line interface (CLI). This simplifies the process even more, if you are used to text-based computer interaction. Also, NVDA is the only screen-reader that reliably works with the IDE, whereas JAWS crashes nearly every single time for some reason.
I was originally thinking of using this code for an assignment; however, this is no longer viable for certain ethical reasons. So the code is now publicly available.
]]>‘Review’ is probably a somewhat pathetic word to describe this post. But owing to some confusion that seems to exist in a number of places, coming from people who have purchased and are trying to use the display, I have endeavoured to compile at least a summary of some of the issues people are having with the Focus Blue, along with some hopefully helpful solutions. Mostly I have been a very happy Focus Blue display user for the last decade or so. This F40B 5th-Gen is a really good display and I do not intend to look anywhere else. But for some reason there seem to be some issues this time, perhaps partially with the display itself but mostly with things like the documentation, which is creating if only mostly minor problems for beginners in particular. It may be important to state that I am using the latest Focus 5 firmware as of this writing (5.81-61).
One lesson I prematurely learnt the hard way, not having immediate access to either a built-in or external disk-drive, was that at least two 5th-gen user guides exist on the FS website. This one, on the FS support sub-domain, is up-to-date but this one, on the main website domain, which is the one that annoyingly always comes up in a Google search, is not! Users beware. Unfortunately, this discrepancy has probably caused me to ask some potentially stupid questionbbs to some people but that’s the way of it. One can check the FS Braille display documentation page. But There is no specific, immediately obvious reason, to my knowledge, as to why one should necessarily have assumed that there was a problem. Unless there is a really good reason for keeping the two user guides up on their website, it would probably be good if FS would either update the latter, or remove it altogether.
Also, it may be worth noting that there is a separate guide for the built-in Scratchpad, used for taking notes on the fly and transfering / exporting them to other applications such as a text editor or word processor.
With the discovery of the new user docs, many of the formerly perceived documentation issues are not valid. But one that is still glaringly obvious is that I am pretty sure that the user’s guide contains absolutely no information on how to perform a factory reset. It probably should be contained in the diagnostics section. It’s not exactly like it’s a state secret or anything, so presumably it may be a simple oversight that FS may hopefully fix at some point. If you contact FS technical support, or a re-seller’s diagnostics team, they can give you the answer. I believe the command sequence is: while holding down the power button, press RightSelector+RightShift+LeftModeButton (the mode button being above the navigation] rockers. Unless the last button to use is actually the left panning button, that should be the sequence.
One of the things that some first-time users don’t seem to realise is that the Focus Blue 5th-Gen display, in its native / mostly autonomous mode, neither engages in any back-translation, nor even any forward-translation. So you can’t write easily readable print text into a text file without exporting from the Scratchpad to another device such as a PC; and even then you have to rely on the back-translational capability of the mediating screen-reader. I believe the Scratchpad saves text in Unicode, rather than ASCII plain text. But you have to pretty much write everything on the display as-is in computer Braille Code, which could be quite daunting if you are not sufficiently technologically literate and / or not an engineer, or a mathematician, or a scientist of some description. So even though you have the option of saving your files in the Scratchpad as plain text (.txt), the reality is that you are writing a raw Braille-formatted (BRF) file anyway. But ironically, the option to literalistically save a file onto the removable storage micro sd card as a .brf file is not available.
Consequently, on a similar note, even though I understand its functional capability, I do not understand the exact funcional necessity of the so-called .fnz file format, whatever that is supposed to stand for. Essentially, it is meant to be used for exporting back-translated notes onto another device via Bluetooth or USB. But considering that you can save as plain text &endash; and that doing so does not allow the production of coherently print-readable files but only raw Braille-formatted files – I’m not quite sure why the file format actually exists. Unless FS does not want the user to be able to figure it out, the documentation does not explain much about how how the FNZ files are encoded but the files are also not really protected, so you can still open them up in a standard text editor. I’m just not sure what the digits represent, whether they are convertible hexadecimal values, or something else. Would be really curious and interested to know if anyone has some answers. Unless you cannot export .txt files and backtranslate on-the-fly by this method? To be honest I have not yet specifically tested out this possibility.
Also, one final note: the Focus Blue has a duplicate Computer Braille issue with FS’ JAWS for Windows screen-reader, in that it does not know how to natively handle Braille dots-456. In JAWS, this problem has been around for quite a while. This is easy to fix with JAWS but not in the display itself. If you type dots 456 into the display, rather than encoding an underscore (_) into the text, it encodes the theoretically non-existent ASCII character 127 (the delete character), which is technically not even a genuine character and is not immediately recognised by JAWS. The only way around this is to try to consistently remember to simply type dots-4567 instead of dots-456, which always types an underscore properly and still ends up looking like dots-456 when reading text output on a PC, even when in a screen-reader is suppressing dots 7 and 8 to represent a classic Braille cell.
One thing that confused me for a while (and I know that others have had similar queries) was how to toggle and then adjust the seconds display in the display’s built-in clock. I think it is as simple as saying that you cannot adjust the seconds but only the hours and minutes. You can only toggle the display or suppression of the seconds and have to just wait until the actual time gets to the relevant minute, setting the time accordingly, if one really wants to be that accurate which I suppose many people possibly could not care less.
Commentary from multiple people professionally working within assistive tech fields tell me that the only person to have these problems (especially the USB one) is reportedly only yours truly, even though the display has been around for a littl while now… Not sure what that means, if anything at all. Maybe the revelation is that my parents have lied to me all along and I was actually born on the 13th and not the 12th or something; but at least that was a half-lucky Tuesday and not a Friday. Anyway, I will outline the following two issues with the following two solutions:
On two separate occasions, Windows 10 has kicked up a fuss and displayed an alert notification, telling me that the display was not recognised properly and that the driver(s) could not be found or be installed properly. They actually did install but they must have become corrupted somehow.
I tried doing a windows update and repair but these did not work. Because Windows assumed at least the mere existence of the Focus 5 drivers, I had to do the following:
A very helpful and knowledgeable individual informed me that sometimes the display stops working if you happen to have installed the Microsoft Narrator Braille display drivers, which I must have done at some point, perhaps because they are generally labeled in optional Windows features rather than being explicitly identified with narrator. But even after uninstalling them, sometimes there are still issues. To do this, I theoretically uninstalled the Focus 40 BT Bluetooth device driver as it was listed in device manager, although I don’t know that there is anything installed on top of the standard Microsoft Bluetooth platform. I also did a jaws repair and re-started the computer. I still had to remove the Focus 40 BT device (not the driver but the device which was apparently still paired with my computer somehow), then everything worked fine after re-pairing and connecting. I can’t remember the exact process though but it ultimately worked.
This is actually a really good display generally speaking; and I hope that my current post does not deter any potential FS / re-seller’s customer(s) from buying one. But if you want to be a proficient Braille consumer and communicator (reading and writing) then you may need to do some further investigation to be able to use this display properly. Hopefully this post makes this process less necessary, thanks to the help of some personal critical thinking skills, as well as good practical advice from many mailing lists, friends and acquaintances. Hopefully also FS will take some of this on board where required, based on some reports that have been made to tech support.
]]>The only two direct contributions I have made thus far have been minor updates to provide backwards-compatibility between the two most widely-used versions of the programming language PyLBC is written with and for, namely the stable but now legacy Python version 2.7 and the much newer Python 3, which is still under on-going development. For some reason, the programs created with PyLBC still won’t compile to machine language with Py3, so this is a work-in-progress. But it more-or-less works now if one runs from source.
I have sent pull requests to the main developer and one other person but for now, the code can only be accessed within my own fork.
]]>There is one big life change though that also happens to change some things about this site: I have enrolled and in two months, will be studying a Bachelor of Computer Science at Deakin University. Basically this means that there are some people who might say I am becoming an official nerd. I have basically chosen a degree which is kind of arguably between an information technology degree and a software engineering degree. This necessarily means a couple of pragmatic things have to be announced:
The Facebook page and its username are still the same and point to the new site.
Well that’s a wrap, pretty much. I’ve got lots of stuff to do to get ready for the next several months. So this might be all there is for a while, again.
]]>