Working with the Lektriever Series 80 — What You Actually Need to Know
I spent roughly three years supporting these devices across a few different accessibility units before moving on. The Series 80 is a refreshable braille display terminal made by the Dutch company Lektriever, and it does one thing really well: it turns any text-based output into tactually readable braille cells in real time. That sounds straightforward until you are actually trying to make it work in a busy office environment where someone needs it to function without constant intervention. The device connects through USB or optionally via the serial port on older configurations. You will need the appropriate driver installed on the host computer first, and then you point the software you are using toward the correct COM or USB virtual port. This part takes maybe ten minutes if everything behaves. It took me about forty-five minutes once because the USB cable I had on hand was not fully shielded and the signal was dropping intermittently. I swapped to a shorter, properly grounded cable and the issue went away immediately. Cheap cables cost you more than you think. The braille cells themselves are arranged in the standard European layout — that means dot patterns follow the traditional six-dot cell configuration with additional cells for the full twelve-dot system when needed. Most European languages and many non-European scripts work out of the box with the right language pack loaded. If you are working in something less common, you may need to verify character mapping support before relying on it for critical documents.
One thing people do not always catch: the refresh rate on the Series 80 is about sixty hertz, which means text scrolls smoothly when you are reading ahead, but there is a slight mechanical delay when you jump between sections. Fast navigation can make it feel like the display is lagging even though it is not actually lagging. You get used to it, but if someone is expecting instant response like a screen reader on a monitor, they might be frustrated at first. The workaround is to slow down the cursor movement slightly and let each page render fully before advancing.
Practical Setup Details
The hardware includes a row of programmable keys along the bottom edge. These map to common commands like navigation, paragraph jumps, and function toggles depending on your software. I usually set mine to match the most frequently used actions for the person I am supporting rather than leaving them on factory defaults. Factory defaults are fine for initial testing but not optimized for daily work. The device also has a built-in speaker output if you want to pair it with audio for dual-mode access. Some users find that helpful, others find it cluttering. I have found it useful mainly during the initial calibration phase when you are checking that the braille output is syncing correctly with the audio narration. After that, most users drop the audio and rely on braille alone because it is faster for sustained reading. Software compatibility is generally broad. The Series 80 works with most screen readers and braille embossers on Windows, and it has reasonable support on Linux as well. macOS support exists but can be finicky with third-party applications. If you are running a specialist program that does not expose standard accessibility APIs, the device may not respond the way you expect. I encountered this once with a legacy medical record system that wrote directly to a proprietary terminal interface. The Lektriever saw the output but the braille cells were displaying garbage characters because the encoding was misaligned. The fix was to run the output through a Unicode conversion filter before it reached the display driver.
Get the Full Details
Known Limitations and When It Fails
The Series 80 is not designed for heavy multimedia use. It handles text perfectly. Images, audio files, video — none of that translates to braille and the device will not attempt to. If you are expecting a general-purpose assistive terminal, this is the wrong choice. It is a braille reader first and that is all it is. The refreshable cells themselves have a limited lifespan. Lektriever rates them at several million cycles, which sounds good until you realize that heavy daily use in a public institution can wear them faster than expected. I replaced a cell module on a unit that had been running approximately four years of full-time school use. The tactile feedback started feeling sluggish and some cells stopped responding consistently. Replacement parts are available but they are not cheap. Budget for maintenance if this device is going to see constant use. Another practical issue: the device generates a small amount of mechanical noise from the cell actuators. In a quiet reading room or library setting, that noise can be distracting to other users even though it is not loud on the device itself. I learned this the hard way when a user brought one into a shared study space and received complaints within an hour. The solution was to move the device to a semi-private area or add a soft mat underneath to dampen the sound.
Power consumption is low but the device does require a stable connection. If you are using it on a laptop with a weak USB port, you may experience intermittent disconnects. An external powered USB hub solved that problem completely in my experience. Do not skip that step if you are unsure about your power delivery.
Common Pitfalls to Avoid
People often assume the device will automatically detect the connected software and configure itself. It does not always do that correctly, especially with less mainstream applications. I have seen cases where the braille translation was off by one character because the software was sending data in a format the driver did not fully support. Always test with a simple text document first before relying on the device for complex workflows. The firmware on the Series 80 is updateable, and I strongly recommend keeping it current. Older firmware versions had a bug where the display would freeze if you scrolled too quickly through a long document. The fix was released fairly quickly after I reported it, but anyone running an outdated version may still encounter it. Check the Lektriever website for the latest firmware before you dive into extended reading sessions. One more thing: do not ignore the cleaning schedule. Dust accumulation in the cell mechanism is a real problem over time. I have seen units where the braille cells stuck because fine dust from paper and carpet fibers worked its way into the actuator housing. A gentle compressed air blast every few months goes a long way. I do not mean to suggest this is a frequent maintenance task, but it is something that gets overlooked until it causes a noticeable failure.
The Lektriever Series 80 Manual itself is available on the company website and covers the technical specifications, wiring diagrams, and troubleshooting steps in detail. If you run into something that the manual does not address, Lektriever's technical support has been reasonably responsive in my experience, though response times can vary depending on your region and whether you are an authorized institutional customer or an individual user. Bottom line: this is a solid piece of hardware for dedicated braille reading. It is not a cure-all, it will need occasional maintenance, and it does not handle everything you might want it to. But for text-based work where braille access is the primary requirement, it performs reliably and the learning curve is manageable once you get past the initial setup quirks.
