OUR NETWORK:TiVo Community TechLore Sling Community My DigitalEntertainer MyOpenRouter MediaSmart home See all... About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 5347650.0
February 1, 2008 11:39 AM

Categories: Robot Hacks and Mods Robopanda

Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

I,robot114

Member
Joined: 12/19/2007

Has any one found any robopanda hacks?

i've thought of changing the LEDs in its eyes.

How about installing an IR sensor in one of the eyes??

I've just thought about these, i'm too afraid of breaking my little panda.

"Life is not measured by the breaths we take, but by the moments that take our breath away."

Discussion:    Add a Comment | Comments 1-25 of 210 | Latest Comment | 1 2 3 4 5 6 7 8 9 Next »

February 1, 2008 5:27 PM

There is already an IR sensor in the eye, if you look close at his... left (I think) eye when he is off, you should be able to see it.

RoboGuide - Your guide to hacking all things WowWee

February 6, 2008 4:05 PM

Then why does Wowwee not mention this on the package??(:^o

"Life is not measured by the breaths we take, but by the moments that take our breath away."

February 6, 2008 4:26 PM

Why would they?

RoboGuide - Your guide to hacking all things WowWee

February 7, 2008 2:43 PM

I don't know but they mentioned it on the roboreptiles package.(:^0

"Life is not measured by the breaths we take, but by the moments that take our breath away."

February 7, 2008 5:46 PM

I think they said IR Vision, which is different.

RoboGuide - Your guide to hacking all things WowWee

February 8, 2008 11:03 AM

Whats the diffrence??(:^0

"Life is not measured by the breaths we take, but by the moments that take our breath away."

February 8, 2008 1:42 PM

An IR receiver isn't IR vision. Vision requires an emitter and a receiver (at least one of each) to "bounce" the signal off an object and get that signal back. The quicker the IR signal sent by the emitter is received back, the closer the object in question is in proximity. A little bit of math can tell the robot a semi accurate distance measurement, if the software has been set up to do that.

Perhaps Panda's receiver is in preperation for the impending programmable remote?

Watch out, don't step in the anthropomorphization.

February 8, 2008 1:58 PM

That's my guess too. has anyone tried shooting panda with any of the remotes?

Visit my Roving RoboReporter blog!

February 8, 2008 5:38 PM

Oh, it also has a IR emitter in the other eye.

RoboGuide - Your guide to hacking all things WowWee

February 8, 2008 8:47 PM

Perhaps they're in place for a future firmware upgrade to give your Panda the ability to Tivo Animal Planet.

I can't bring myself to spend the money on the Panda to find out the answers to these wonderments. Maybe if my kid showed any interest in it at all I would... 

Watch out, don't step in the anthropomorphization.

May 12, 2008 4:13 PM

If someone interested in RoboPanda reverse engineering/hacking - check out http://sevik.org/robopanda

There is work in progress, but some results already achieved :))

Free RoboPanda!!! :)

May 13, 2008 7:17 AM

Wow, that's very impressive Sevik! Do you have any videos of him saying something new? And would you consider posting a picture of your dev board and emulator cartridge in this thread? It will take a long time for me to read and truly understand all that you've figured out, but definitely a very nice job!

Visit my Roving RoboReporter blog!

May 13, 2008 7:57 AM

Sevik is not quite that far along yet. Exactly how the audio is formated is still in question.

RoboGuide - Your guide to hacking all things WowWee

May 13, 2008 8:48 AM updated: May 13, 2008 8:49 AM

This is not such an easy task :)

But we are moving :)

Hope to get attention of some more than 3 capable persons to this task... :)

About audio - I hope that some of codecs (only 2 seen in stock cartridges ) can be uncompressed PCM :))

Free RoboPanda!!! :)

May 13, 2008 9:31 AM

sevik said: ...Hope to get attention of some more than 3 capable persons to this task... :) ...
Are you working on this with other people, and are you asking for more people to help? It sounds like Nocturnal is already working with you perhaps?

Visit my Roving RoboReporter blog!

May 13, 2008 9:37 AM updated: May 13, 2008 9:38 AM

For now only me and Nocturnal really involved in this task.

And I'll be glad to see some more :))

More technical discussion takes place at Unofficial Robosapien Hacks and Mods Forum

Free RoboPanda!!! :)

May 14, 2008 2:19 PM

Thanks for sharing your project, Sevik. We'd love to hear more updates on how the project is going, and don't be afraid to discuss it here too :) There are lots of people here who would really enjoy seeing it.

Keep us posted and have fun. Pete

Peter Redmer
Administrator
Visit my blog, "Caffeinated Pixels"
Follow Me on Twitter

May 14, 2008 3:52 PM

Are you looking for any skills in particular that you and Nocturnal don't already have covered? I have a Robopanda to hand, and would love to hear him sing Stairway to Heaven instead of 'lets have an adventure'!

Visit my Roving RoboReporter blog!

May 14, 2008 4:14 PM

:)) You can try to guess audioencoding methods :))

For now we need to decode many bytecodes and guess and check effects of many 29XX commands.

For decoding bytecodes small tracer like first nocturnal's version is really enought (there are need to trace first 30-40 accesses) and small spi flash based cardemu needed (minimal valid cartridge image can be put in 100-200 bytes).

I have big tracer and cartridge emulator, so any tasks with big amount of needed tracing/large cartridge contents can be accomplished.

There are always need in better tools :)) I have decoder and emu, but no real assembler.

Free RoboPanda!!! :)

May 14, 2008 7:09 PM updated: May 14, 2008 7:15 PM

So from this bit of your web documentation:
Audio data chunk format:

* int32 - length
* int8 - codec (07 or 09)
* int8 - something (always 128)
* 32 or 48 byte chunks of data
* int16 - something (always FFFF)
* int16 - checksum?

Looking in Nocturnal's cartridge image for patterns of x07 0F nn(32 or 48x) FF FF,
should hit a whole series of audio chunks, correct?

Visit my Roving RoboReporter blog!

May 14, 2008 10:45 PM

Or you can go here and here, I wrote a program to dump the records out a while back.

Its been a while, but I'm pretty certain I dropped the record structure (except the details recorded in the name, which is probably recordnum-type-checksum), and just kept the data.

RoboGuide - Your guide to hacking all things WowWee

May 14, 2008 10:50 PM

Ah, thanks Nocturnal. Do you know if those are the equivalent of the cartridge_dump *.aud files from Sevik's emu_log archive? Also I gather the data is little-endian, correct?

Visit my Roving RoboReporter blog!

May 14, 2008 11:42 PM

They are not quite the same, the *.aud files include the record structure as well as the data, mine are just the data. We also seem to be disagreeing on the total number of items.

RoboGuide - Your guide to hacking all things WowWee

May 15, 2008 12:17 AM updated: May 15, 2008 12:25 AM

there are list of pointers to start of audio data chunks at start of cartridge (starting at 0005 offset, 3 byte for pointer up to @PEND string, So there are no need for guessing for number of items and its location. And yes, *.aud files - it's exactly this audio chunks.

play bytecode reads start of chunk from this table (see emu logs)

there are at least 2 codecs supported, and when by mistake I putted another value player worked too, but used yet another (not 32 or 48) frame size.

I plan to find all accepted codecs values but this task is lower in list - after decoding of most used bytecodes, assembler in cartridge builder and stack support in emu :))

Free RoboPanda!!! :)

May 15, 2008 12:48 AM updated: May 15, 2008 12:53 AM

*.aud files has all record structure, except for 4 bytes with length.

at least codec value is integral part of data, and can't be dropped :))

Looking at traces I found that player always (for 7 codec at least, I have not waited to end of song) reads 356 bytes more than really present in audio data...

may be It's player fifo prefetch. It matches initial read size of 254+140 bytes - 32 byte frame - 6 bytes of header(length + codec + 0x128). I think tailer really not supposed to be read by player.

Need to check this values for 9 codec.

Free RoboPanda!!! :)

Discussion:    Add a Comment | Back to Top | Comments 1-25 of 210 | Latest Comment | 1 2 3 4 5 6 7 8 9 Next »

You must login to discuss this item.

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

close this window
close this window