Spykee Manuals and Firmware: Where Every Surviving File Lives

If a forum post sent you here, you were probably following a link that ended in manualpc-en.pdf or firmware-en.pdf. Those paths worked for years. They do not work now, and no redirect on this domain will bring the files back, because the files were never ours to serve. This site is an independent publication with no connection to Meccano or to Spin Master, which has owned the Meccano brand since August 2013. Every manual below is Meccano’s copyright, the SDK document is Wavestorm’s and carries their own do not distribute notice, and we host none of it. What follows is a directory of pointers into public archives, with the dead ends marked so you stop hunting for them. If you want the robot’s story rather than its paperwork, that lives in our history of the Spykee robot.

Why do the old spykeeworld.com links go nowhere?

From 2007 to roughly 2013 this address was Meccano’s own Spykee site, and it did the job a product site does. The manuals lived under /spykee/documents/, the software and the firmware lived under /spykee/download/, and the SDK paper sat in a folder called free.software. Robotics forums, blogs and mailing lists linked those paths directly, which is why they are still scattered across the web sixteen years later.

Nobody published a shutdown notice, and we are not going to invent a date for one. The evidence gives a bracket instead. Real PDF captures run through 2014. By April 2015 the same paths were answering with a NetNames domain parking page that reads “The domain www.spykeeworld.com is registered by NetNames.” The community had read the writing earlier than that: on the German robotics forum Roboternetz in December 2011, a buyer who had already given up on his unit wrote that “Ich vermute beim Spykee handelt es sich um einen Auslaeufer der nun so guenstig wie moeglich verscherbelt wird,” which is his guess that the robot was a discontinued line being dumped as cheaply as possible. He also had the practical complaints you would expect: “Bildqualitaet ist wirklich schlecht,” a battery that emptied in minutes after a three hour charge, and a dock the robot circled without ever finding.

Here is the trap in the Wayback calendar, and it catches people constantly. Those 2015 and later captures return a status of 200. Green dot, looks alive, click it and you get parking junk instead of a manual. Use the capture dates in the tables below rather than the newest snapshot available. Between 2018 and 2021 the domain also ran as an affiliate review blog, and that owner rehosted exactly one real Spykee file: firmware-en.pdf, byte for byte identical to the original at 64,187 bytes, at a WordPress uploads path from May 2019. That copy is gone too.

I need the PC or Mac console manual

This is the one most people want, and there are four of them. The PC manual and the Mac manual are separate documents at separate version numbers: English for PC is version 1.7, English for Mac is version 1.5. The PC edition runs 43 pages and covers the whole arc, from building the robot through WiFi setup, driving, the video surveillance mode, the firmware tab and the technical data sheet. Its cover carries the Meccano logo and a line that is now a small piece of history in itself: “Online assistance: [email protected].” That mailbox is at this domain. Nobody answers it.

If you do not want to pull a four megabyte PDF, use the ManualsLib mirror and read it a page at a time. Two pages carry most of the troubleshooting value: page 36 has the firmware update procedure, page 37 has the reset instructions and the technical data sheet. There is also a copy in the FCC filing. Meccano (Hong Kong) filed the robot under ID R9P870850 as “Spykee, the WiFi Spy Robot,” and the user manual went in as three exhibit parts. The usual FCC lookup sites block automated requests, so the mirror below is the one that answered.

I need the assembly instructions for the three builds

One kit, three robots. The PC manual puts it plainly: “select the spy robot model you like best from the three available choices: Robot, Scorpion, or Lunar Vehicle; now go ahead and build it!” Each build had its own booklet, and the covers are nothing like the software manuals. They are full bleed lime green with a photo of the finished robot, eleven languages listed down the side, kit number 0850 in the corner and an 8+ age badge. Page two is a classic Meccano parts inventory grid.

The old site served each booklet under two different filenames, which is why forum links to these are so inconsistent. We checked the payloads rather than the names. WhiteRobot02.pdf and instructionsrobot-en.pdf are the same file down to the byte, and the same holds for the other two pairs. Grab whichever link you find. You are getting the same document.

Where is the firmware, and what is firmware-en.pdf really?

Start with the correction, because half the links pointing at this domain get it wrong. firmware-en.pdf is not a firmware update guide and it is not firmware. It is a three page white paper from Wavestorm, the French startup that built the robot’s electronics, and it explains how to compile your own firmware image. It tells you to “get the source tarball on meccano site (sdk.tar.bz2) and untar it,” then run “make defconfig : select the default configuration for spykee,” and it says the build produces “two files: uImage (linux kernel) et rootfs.arm_nofpu.squashfs (filesystem).” The stray French “et” in an English document is my favorite detail in the whole file. Every page carries the footer “2008-05-23 Copyright 2008 Wavestorm Do not distribute without authorization,” which is exactly why we point at it instead of hosting it.

Read it as a document, not as a recipe. The sdk.tar.bz2 tarball it depends on is not in the archive. The only capture at that path is 2016 parking junk, so unless someone has a copy on an old hard drive, the build described in that paper cannot be reproduced from public files today.

Stock firmware never came as a download for most owners anyway. It arrived through the console. The manual says that when you are online and connected to the robot on the administrator account, “a message might inform you of the availability of firmware update,” and the install runs from the Configuration icon, Firmware tab. The manual then shouts, in capitals: “IMPORTANT: DO NOT DISCONNECT OR TURN OFF THE ROBOT DURING FIRMWARE UPLOAD.” Good advice for a device with 4Mb of NOR flash and no recovery path.

The version numbers are settled, and versions.txt is why. That plain text file is what the console polled, and the November 2009 capture reads firmware-version = 1.0.22, pc-software-version = 1.0.10, mac-software-version = 1.0.0. The manual’s own screenshot of the Firmware tab independently shows 1.0.22 sitting in a window labeled Console v1.0.9. If your robot reports 1.0.22, it is current, and it will stay current forever.

One more thing worth knowing before anyone tries to reflash anything: this is a Linux machine. Meccano’s own free software notice in the manual says the firmware “includes software, namely BusyBox v.1.7.2, mtd and ms-dos file system which are free software distributed under the GNU General Public Licence V.2.0,” and it names the authors, Cedric Lacage and Benjamin Bagland. Wikipedia records that the full firmware source and documentation were made available as of May 2010. A 200 MHz ARM9 with 32Mb of RAM running BusyBox is a small computer, and people have treated it like one ever since.

What did not survive

The software did not. That is the honest hole in this page, and no amount of searching has closed it. You can read the directory listing that proves consolepc.zip and consolemac.dmg existed, at the sizes and dates below. You can read the manual telling you to “Go to the website on www.spykeeworld.com under the ‘Install’ heading” and download the Windows version, which then installed itself to C:/Program Files/Spykee. What you cannot do is get the bytes. Bounded archive queries for all three installer paths return zero captures, and no archive.org item holds them either.

The one archived firmware binary is worse than missing, because it looks fine until you open it. firmware.zip was captured on January 10, 2012 at 2,034,440 bytes, and it is truncated. Two independent downloads both fail integrity with “End-of-central-directory signature not found.” Anyone telling you the firmware is on the Wayback Machine has not unzipped it.

What we will not do is send you to a download blog to fill the gap. Several pages that rank for “Spykee software” are auto generated stubs, and the ones we checked were either offering unverifiable binaries or offering software for Spykee Vox, a different toy in the same family. A robot you cannot control is annoying. A random executable from a 2013 download farm is worse.

What the Spykee console actually was

Get the name straight first, because it saves an hour of searching. The control software is the Spykee console, a desktop application for Windows and Mac. It is not a phone app, and it is not SpykeeCell. Spykee Cell is a separate, later toy with its own manual, and searching for it will hand you documents for hardware you do not own.

The requirements printed in the manual date the whole thing: “Windows 2000 SP5, Windows XP SP2 .NET framework 2.0 installed, Windows Vista,” plus a computer with an internal or external WiFi card, 512 MB of RAM and 100 MB of free disk. Remote mode wanted a minimum 512 Kbps up and 2 Mbps down, which tells you how much of 2008 is baked into this product.

Which brings us to the question a Spykee parent asked on r/arduino in December 2024, and it is the exact question this page exists to answer: “we can’t get it to connect wirelessly on our modern computers, have you had any luck with older systems such as windows XP? how do you run it?” The straight answer has two halves. There is no verified copy of the console installer to run, on XP or anything else. And even with one, remote mode is dead on arrival, because the manual is explicit that “Robot registration is required for remote mode use,” and registration was a service on this domain. There is no robot registration here. There is nothing to sign up for.

What still works on an untouched robot is local. Spykee falls back to its own ad hoc network by default, “after approximately 15 seconds,” so the robot will still announce itself even with no infrastructure at all. If you point it at an access point instead, two Meccano footnotes save real time: “The WEP key must be entered in hexadecimal format and not in ASCII characters,” and if you use WPA, “check that the encryption is ‘WPA Personal’ and not ‘WPA Enterprise’.” Both of those are on page 40 of the PC manual.

Two more pages earn their keep on a survivor. The reset button is under the chassis, and holding it more than 10 seconds restores factory defaults. The battery is a 9.6V NiMH pack that takes 3 1/2 hours to recharge, and the manual warns that “The robot will not charge if it is switched OFF,” which explains a lot of dead Spykees. If the pack itself is finished, that is a cell problem rather than a documentation problem, and our basics of repairing robot toys covers where to start.

Can you still drive a Spykee in 2026?

Yes, but not the way the box promised, and the community split on this years ago. One camp wants the stock experience back. The other decided the robot was more interesting as a chassis with a Linux board in it, and that camp is the loud one now. Both of the recent Reddit revival threads are Arduino conversions, and the reception was warm: hundreds of upvotes, plus the same joke over and over, because everyone sees Johnny 5 when they look at this thing.

The third path is the oldest one. Wavestorm shipped an SDK white paper on purpose, Meccano released the source, and within a year of the US launch Hackaday was writing up people driving a Spykee with webcam finger tracking. In 2011 the robotics team at DoBots reviewed the retail product without much affection, calling the suspension basic enough that “a small bump can already block Spykee’s way” and the docking “barely working,” then said the part that matters here: “it is possible to make your own modifications to it and make it a really stunning robot.” That was always the appeal. We keep the full project ledger in our history of WiFi robot hacking, and if you would rather buy something a manufacturer still supports, we look at the modern alternatives to Spykee separately.

These are community workarounds, not endorsements, and none of them is a supported product. Take them as what other owners did, then decide for yourself.

How we checked, and what to do when a link dies

Every pointer on this page was fetched on August 10, 2026 and checked for a real payload, not just a status code. A PDF had to start with the PDF magic bytes and open. versions.txt had to contain version numbers. That check is what separated the good captures from the parking pages, and it is why the archived firmware.zip is listed as broken rather than quietly linked.

None of that makes any of it permanent. Archives reorganize, retailers prune old assets, and mirrors go behind login walls. If a link on this page stops working, tell us and we will re-verify it and swap in the next surviving copy we can confirm. Until then, one habit will save you: when you open a Wayback capture of an old spykeeworld.com path, check the date in the URL. Anything from 2015 or later is a parking page.