Vector: Difference between revisions
m headung |
A lot of prototype information |
||
| Line 1: | Line 1: | ||
Vector is a little AI-powered robot that is packed with technology—and character. It's designed as a robot companion and helper for people at home. Vector was developed by Anki, a San Francisco startup founded by Boris Sofman, Mark Palatucci, and Hanns Tappeiner, who met as students in the PhD program at Carnegie Mellon's Robotics Institute. The company's first products were the robot racing games Anki Drive and Anki Overdrive in 2013 and 2015, respectively. They were followed by Cozmo, a small programmable robot, and then Vector, a social AI-powered robot released in 2018. Anki raised a total of US $182.5 million from Andreessen Horowitz, JP Morgan, and other investors. In April 2019, after failing to secure a critical round of funding, Anki shut down. Later that year, Anki assets, including Overdrive, Cozmo, and Vector, were acquired by Digital Dream Labs, in Pittsburgh, Pa. The company now offers Vector 2.0, which received both hardware and software upgrades. [Vector released on October 12th, 2018] | |||
== Changes between Vector 1.0 and 2.0 == | == Changes between Vector 1.0 and 2.0 == | ||
| Line 17: | Line 17: | ||
== Prototypes == | == Prototypes == | ||
'''''THIS | '''''MOST OF THIS SECTION COMES FROM''' https://randym32.github.io/Anki.Vector.Documentation/index.html, '''THANKS RANDY''''' | ||
=== P1 === | === P1 === | ||
| Line 30: | Line 30: | ||
=== P3 === | === P3 === | ||
P3 is the last prototype batch before DVT. Not much is known about these either. | P3 is the last prototype batch before DVT. Not much is known about these either. Other than that the headboard design was nearly finalized by this point | ||
=== DVT1 === | === DVT1 === | ||
| Line 39: | Line 39: | ||
* Their partition tables are old, similar to what looks like stock Qualcomm. | * Their partition tables are old, similar to what looks like stock Qualcomm. | ||
* Many Victor DVT1s run builds which are more similar to Android than Embedded Linux. | * Many Victor DVT1s run builds which are more similar to Android than Embedded Linux. | ||
* Many Victor DVT1s are in FAC (factory) mode. If you find one in FAC mode, he is very likely running old proof of concept software | * Many Victor DVT1s are in FAC (factory) mode waiting to be placed into the playpens. If you find one in FAC mode, he is very likely running old proof of concept software. | ||
* If you find one with Cozmo eyes, it is probably the same proof of concept firmware. Some have been upgraded to a slightly newer kernel though. Some can run behaviors when shaken. | * If you find one with Cozmo eyes, it is probably the same proof of concept firmware. Some have been upgraded to a slightly newer kernel though. Some can run behaviors when shaken. | ||
* Their serial numbers are strings such as "1f19f8b7". | * Their serial numbers are strings such as "1f19f8b7" which is a shortened version of their QSN. | ||
* Most have SSH open, but there is a root password. ADB over TCP is fully open but it may require a couple reboots. | * Most have SSH open, but there is a root password. ADB over TCP is fully open but it may require a couple reboots. | ||
* Their BLE software is old, and it is hard to connect them to your own Wi-Fi. | * Their BLE software is old, and it is hard to connect them to your own Wi-Fi. | ||
The "head board" hardware is pretty much exactly the same, but the "body board" hardware is very different compared to modern Vector hardware. | The "head board" hardware is pretty much exactly the same, but the "body board" hardware is very different and missing stuff compared to modern Vector hardware. Despite this it is possible to upgrade them to modern bodyboard firmware and use them with your modern head although it's not advisable due to voltage drops causing frequent shutdowns. | ||
=== DVT2 === | === DVT2 === | ||
| Line 56: | Line 56: | ||
* Many of these run the same exact build (labelled "0.10.0d"). It is speculated that a few of these were animation bots. | * Many of these run the same exact build (labelled "0.10.0d"). It is speculated that a few of these were animation bots. | ||
* All we have seen so far run the same exact kernel. | * All we have seen so far run the same exact kernel. | ||
* It is possible to put modern firmware in | * It is possible to put modern firmware on these bots and with a DVT3 or newer bodyboard they work well! | ||
* While the bodyboards in these bots can run modern DFU they cannot charge in modern body firmware. What you can do is use the current bodyboard firmware and upgrade the headboard to run WireOS or any CFW based on it. | |||
Similarities to Victor DVT1: | Similarities to Victor DVT1: | ||
* Their serial numbers are strings such as "1f19f8b7". | * Their serial numbers are strings such as "1f19f8b7" which is their QSN. | ||
* The "head board" hardware is pretty much exactly the same, but the "body board" hardware is very different compared to modern Vector hardware | * The "head board" hardware is pretty much exactly the same, but the "body board" hardware is very different and missing stuff compared to modern Vector hardware. | ||
* There are some positives if you are a passionate developer. They have ADB open which means you can solder on USB and mess around all you want. Everything is completely open and unlocked so you could have a fun time. There is no (useful) recovery or system_b partition so be careful. | * There are some positives if you are a passionate developer. They have ADB open which means you can solder on USB and mess around all you want. Everything is completely open and unlocked so you could have a fun time. There is no (useful) recovery or system_b partition so be careful. | ||
* Most have SSH open, but there is a root password. ADB over TCP is fully open but it may require a couple reboots. | * Most have SSH open, but there is a root password. ADB over TCP is fully open but it may require a couple reboots. | ||
| Line 74: | Line 75: | ||
* It is possible to connect many of them to Wi-Fi without faking a network. | * It is possible to connect many of them to Wi-Fi without faking a network. | ||
* All we have seen so far have SSH open with the normal modern key. | * All we have seen so far have SSH open with the normal modern key. | ||
* Their body boards are a little different. | * Their body boards are a little different and can run modern firmware perfectly. | ||
* Many have been upgraded(?) to the modern partition table and have unlock OTAs so their headboards could act exactly like normal dev boards. | * Many have been upgraded(?) to the modern partition table and have unlock OTAs so their headboards could act exactly like normal dev boards. The body board will need a new DFU flashed but after that they'll work perfectly. | ||
* They started off with a random string serial number, but many have been upgraded to the more normal 00###### layout. | * They started off with a random string serial number, but many have been upgraded to the more normal 00###### layout. | ||
* Their head boards have heatsinks. This ended up not being necessary for production. | * Their head boards have heatsinks. This ended up not being necessary for production. | ||
| Line 82: | Line 83: | ||
* Their serial numbers started off as strings such as "1f19f8b7". | * Their serial numbers started off as strings such as "1f19f8b7". | ||
* The "head board" hardware is pretty much exactly the same | * The "head board" hardware is pretty much exactly the same as production other than the heatsink. | ||
=== DVT4 === | === DVT4 === | ||