The motion doesn't look natural. There is no momentum on their movements. And considering the lack on information on their website, I'd say it's fake. But props for making it very believable. suckers.
Look at what the top-of-the-line research robots can do, and this is far beyond those capabilities. Balance is a very non-trivial issue. With the low-power, low-performance embedded processor they could fit in there, there's no way the robot could balance itself that fast to those types of motions - even if they were all reprogrammed. Give me a schematic of the cpu board and the software code, and I might give it a second chance.
So since they were only possible damages, can he sell the device and do up to $180 million in damages before they can charge him again because of double jeopardy? i mean, that sounds like a $180 million credit to do damages.
So, I do A LOT of USB hardware/software stuff in my disseration work, and I think the Cypress series is by far the best. If you get an elcheapo chip to convert the USB signals then you have to program the protocol manually which is a serious pain (that was the first thing I tried). I gave up and switched to a Cypress EZ-USB because it's the most popular, meaning it has the most support out there. You don't have to use the microcontroller because you can access the USB directly using a DMA to the USB memory location. The microcontroller runs at 24MHz, while the full speed mode (USB 1.1) runs at 12Mbits/s, but the project you describe doesn't need to be faster than 24MHz. For a slow speed application you can just route the data from the USB memory to an output port, and capture the input data on another port. It's a 52 pin package (surface mount) - two 8-bit ports and one 2 bit port on this package.
There's a book released by Intel called "USB Design by Example" which has the EXACT project you're working on. It details all the hardware setup and provides software examples. Its software is in Microsoft Visual Basic and C++. If you want to reproduce that project this is the best way to go. Let the microcontroller deal with the USB protocol to keep it simple.
The motion doesn't look natural. There is no momentum on their movements. And considering the lack on information on their website, I'd say it's fake. But props for making it very believable. suckers. Look at what the top-of-the-line research robots can do, and this is far beyond those capabilities. Balance is a very non-trivial issue. With the low-power, low-performance embedded processor they could fit in there, there's no way the robot could balance itself that fast to those types of motions - even if they were all reprogrammed. Give me a schematic of the cpu board and the software code, and I might give it a second chance.
So since they were only possible damages, can he sell the device and do up to $180 million in damages before they can charge him again because of double jeopardy? i mean, that sounds like a $180 million credit to do damages.
So, I do A LOT of USB hardware/software stuff in my disseration work, and I think the Cypress series is by far the best. If you get an elcheapo chip to convert the USB signals then you have to program the protocol manually which is a serious pain (that was the first thing I tried). I gave up and switched to a Cypress EZ-USB because it's the most popular, meaning it has the most support out there. You don't have to use the microcontroller because you can access the USB directly using a DMA to the USB memory location. The microcontroller runs at 24MHz, while the full speed mode (USB 1.1) runs at 12Mbits/s, but the project you describe doesn't need to be faster than 24MHz. For a slow speed application you can just route the data from the USB memory to an output port, and capture the input data on another port. It's a 52 pin package (surface mount) - two 8-bit ports and one 2 bit port on this package.
There's a book released by Intel called "USB Design by Example" which has the EXACT project you're working on. It details all the hardware setup and provides software examples. Its software is in Microsoft Visual Basic and C++. If you want to reproduce that project this is the best way to go. Let the microcontroller deal with the USB protocol to keep it simple.
gtstapler