neato xv-12 lcd panel illuminates but no text manufacturer

The owner of this website (www.doityourself.com) has banned the autonomous system number (ASN) your IP address is in (20473) from accessing this website.

Unfortunately I have had this same problem twice on my Neato XV (two years apart). Both times the problem was a broken LCD display card, replacing the card fixed the problem. I was able to buy a used Neato XV LCD display card on eBay for about $40. Amazon may have them too.

Follow the Neato XV-21 repair guide on ‘Motherboard Repair’ (thank you Nastassja Klipsch!!) Until you get the two halves of the robot apart. There are a ton of screws, so if I have to do this again I will take better care to write down where they all came from (I started to forget).

You don’t need to remove the Lidar unit, so stop at that point in the guide. The LCD display card is screwed into the top shell of the robot. Once you get the robot apart it is pretty easy to disconnect the cable connector and replace the display.

The page you are looking for no longer exists. Perhaps you can return back to the homepage and see if you can find what you are looking for. Or, you can try finding it by using the search form below.

This SGVHAK teardown project came courtesy of an electronics waste bin. A nondescript box with a USB cable, it has three moving parts on top of a heavy base. The center piece takes up majority of width, and two far smaller pieces sitting on either side. Each piece can be pressed down and we can feel a tactile click of a switch. It has a respectable heft and doesn’t look damaged or even worn. It feels rather beefy and unlikely to physically break.

A label on the bottom of the device lets us know it is version 14 of the Infinity IN-USB-2 foot pedal. Which explains its mass and durability: this box was designed to sit under a desk and be stepped on. A box sitting out of sight explained its raised side pedals allowing its user to find them by feel.

There were a few visible plastic clips holding individual pedals in place, but they were only the first line of defense – unclipping them allowed individual pedal to move a little further but did not release them. There were also a few hinge pins that could be removed, but again it allowed additional movement but did not release.

The two shiny metal weights were held by tenacious stretchy glue. We could pry them up far enough to see they weren’t obviously hiding screws, but we were wary to apply addition force as it threatened to break apart the plastic housing.

Without an obvious way forward for nondestructive disassembly, we decided to pause and reassemble the pedal to see if it can be useful intact before we risk destroying it. My computer was running Ubuntu at the time, which gave us a starting point with the dmesg tool to see what kind of greeting it has to say to my computer.

Now we can try treating it as a file with the cat command. Every time we press or release a pedal we get some kind of visual feedback but we don’t understand it.

We then tried treating it as a serial port using minicom but that didn’t get us much further. It vaguely resembles the garbage that might occur if a baud rate setting is incorrect, but changing baud rate in minicom didn’t do anything. Probably because it’s not a serial port!

Since the device was classified as a USB HID v1.00 Device, the next thought was to try communicating with it via some sort of HID API for developers. But USB HID is not a trivial thing and after a half hour of following and reading links to documentation I was no closer to talking to the pedal in a “proper” way. So I tabled that approach and returned to treating it as a file. It’s pretty trivial using Python’s file APIs to open it up for reading.

Not every action will trigger data events. There’s a small time window where separate events are collapsed together for a single notification. If I’m quick enough on the press and on release, I can push the right and left pedals simultaneously for a single 0x05 report, then release simultaneously for a 0x00 report, without any intermedia reports of 0x04 or 0x01.

With that knowledge under our belts, experimentation then moved to Windows 10, which immediately recognized it as a USB HID and even shows us the name. However, it doesn’t do much without further help.

Searching for answers on the web, we learned this device was designed for people transcribing audio recordings into text. The pedals allow them to control sound playback (pause, play, rewind, etc.) without taking their typing hands off the keyboard. I’m sure this is a productivity boon for its target audience, but that wasn’t us. Fortunately, the manufacturer has also released a piece of software call Pedalware which will allow this pedal to be used outside its designed scenario, like emulating keyboard keys or mouse buttons. I thought it sounded interesting enough to try.

That was enough to get Pedalware up and running on my Windows 10 computer. Now I can assign an arbitrary keyboard or mouse action to each of three pedals.

But that’s fine, the device was never intended to be a gaming peripheral. The real problem comes from its driver software becoming unreliable as a computer goes into low-power standby. When the computer resumes, the pedal doesn’t always come back into action. And once it gets stuck, the only way to get it back is a full reboot.

This was a sign of the times when this device was designed. I remember when many peripherals would not gracefully handle a computer going to sleep, which meant I typically leave my computer running in the Windows XP/Vista/7 days. Computers have gotten more power efficient over these years but it’s still better to put them to sleep. Also, modern USB peripherals are much better about resuming from sleep.

But this pedal does not, and that’s probably why it was retired. Fortunately, my work does not require a predictably functional foot pedal, so I’ll keep it around and try using it on the occasions when it works.

When Linkedin limited it"s users by literally cutting their legs off from ever contacting a decent amount of prospects; ALL other apps simply "downplayed" the limit... and ran! NOT Waalaxy! They quickly found a solution... and not just a simple get-a-round, but a comprehensive- full featured solution! Not only allowing you to "connect" and msg via Linkedin, but instead utilizing MULTIPLE channels to connect! So instead of a limit; you actually have MORE ways to connect using Waalaxy. Do not waste your time testing the rest - I DID. Waalaxy also has daily support if needed.

When Linkedin limited it"s users by literally cutting their legs off from ever contacting a decent amount of prospects; ALL other apps simply "downplayed" the limit... and ran! NOT Waalaxy! They quickly found a solution... and not just a simple get-a-round, but a comprehensive- full featured solution! Not only allowing you to "connect" and msg via Linkedin, but instead utilizing MULTIPLE channels to connect! So instead of a limit; you actually have MORE ways to connect using Waalaxy. Do not waste your time testing the rest - I DID. Waalaxy also has daily support if needed.