Vinie i.m still working on a rovioligths (blue leds)..its implemented all leds on/off and a every single blue led on...but it.s not finished yet because i just can work a few hours every saturday, when will finish i will post a how too.

Regards.

vinnie said: OK, I was able to make a really simple modification to the build, introducing my our HTML pages on Rovio. This is very encouraging. It was very easy to do, since I'd already gotten the build process working. I just dropped them in \Host\LibCamera\Res\Flash_Koitech and did a build and update. The extra files were right there on Rovio where the main index.htm was located. Has anyone else noticed the .PCM files in the resources? I wonder if there's a debugging commmand we can send via cgi that will play them through rovio's speaker.

As Chris75 said earlier there is no reason why we cannot redesign our own index pages:

This is a screeshot of my own personal build/skin available here. I was wondering whether I could put barely visible navigation controls over the video screen which then disappear after clicking a control button? Any advice anyone... particularly regarding editing the style sheet. Even more desirable would be the ability to switch to a full video screen with disappearing navigation?

Sociorobotics Blog: http://sociorobotics.wordpress.com ~ Wikipedia: http://en.wikipedia.org/wiki/Sociorobotics

Hi chaps,

I would really love to get a copy of the Rovio schematics but the link on page 1 seems to be dead. Does anyone know of an alternative source?

Cheers,

Jay

vinnie said: The full schematic for the Rovio appears to be shown here. There's even a first page that shows how the cables and connections run.

Does anyone happen to have this schematic saved, every time I try and download from that link I get an unable to connect error :(

Cheers.

Phill.

Hi milw,

Many thanks for the datasheet for the processor! Did I read the original thread correctly that a version of the schematic was available for the entire rovio including the wiring looms and ancillary items in the unit?

Cheers,

Jay :-)

vinnie said: @RoboaRovio: nice work on the new build!

Thanks for your comments Vinnie.

After a bit of thought I was wondering firstly if you could find time to edit your original Thread intro to take into account all the information we are gathering here.

I get the feeling that your/this Thread could become vital in the future development of Rovio itself. Together the Rovio community seems to have amassed just about everything there is to allow hardware and software development/hacking of this cool little robot. There is however a bit of a gap regarding the base station and beacon despite this excellent report by Peter Redmer and hack by Thingverse or DIY beacon by ScribbleJ. There is also a brilliant thread (Inside Rovio) by tome. It would therefore be particularly advantageous for us all to co-ordinate our online community to take Rovio forward now that the manufacturers have backed out.

Any ideas or propositions here would be much appreciated. For instance could we bring together a development team which is funded by everyone in some way rather than highly knowledgeable individuals making a quick buck with bespoke software (roviocommander etc)?

The crux of this post is community co-ordination so any ideas or proposals are very much appreciated.

RoboaRovio

Sociorobotics Blog: http://sociorobotics.wordpress.com ~ Wikipedia: http://en.wikipedia.org/wiki/Sociorobotics

milw said: I think a wiki format might be more friendly in the long run; we can also contribute articles to RoboCommunity but I'm not sure how much editing is possible after it is published; plus (IIRC) articles are more geared to single authors rather than collaborative editing. I might also still have the ability to 'stickify' forum posts, otherwise I'm sure Pete Redmer would be able to. What other ideas do you all have? I've only been following this one thread, how many of you check the main forum for new threads? -Scott

-Scott, that's a great start. Are you familiar with opening a wiki? We could keep all the relevent development tools/info etc in one place (Sourceforge perhaps?). We could also separarate the project into areas of interest, hardware/software/beacons etc but still continue to collaborate seamlessly. Even perhaps get some of the original developers interested again? It would also supplement these Robocommunity forums no end.

Can we have some more expressions of interest please.

Thanks again Scott

Sociorobotics Blog: http://sociorobotics.wordpress.com ~ Wikipedia: http://en.wikipedia.org/wiki/Sociorobotics

chris75 said: good idea, I think a Wiki is definitely needed, it's hard to keep track of things (code changes/ file resources / ideas etc...) via a forum, but setting up & operating a wiki is time consuming. An option would be to use one like sourceforge or github. On github there are already Rovio projects including mine, it's mostly a site to share source using git but there is a wiki section. Not sure how good it is, i just used it for a few minutes. If you want to have a look: main site: http://github.com Search: rovio Someone posted the published sources: https://github.com/IHeartRobotics/Rovio I publish some code to hack Rovio before sources were made available: https://github.com/chris75/rovio-hack I you find a place for a wiki, i'll probably contribute. At this time, i'm too busy to help much. Hope this helps anyway. Chris

Thanks for the info Chris, I have been fiddling around on Sourceforge today to see what it offers - the link is http://sourceforge.net/projects/rovio/?source=directory I'm also constrained by time so if anyone has any experience with Sourceforge your help would be very much appreciated. Github looks OK but Sourceforge seems to provide a much more comprehensive interface with its own wiki, blog, dicussion boards, tickets, coding area, web site etc.

If you PM me Chris I will add you as an administrator and you can also have a good look around and let us know your thoughts, that goes for you too Milw and anyone else who would like to get involved (vinnie). I have already put up (for download) everything that I have, so it would be nice to have everything in one place. I was also hoping that colt45 the guy who built the Rovio Fire Engine would also get involved.

I was also thinking that we could 'start at the beginning' to entice new owners and non-techs by providing comprehensive 'walk throughs', resolutions and 'how 2's' so that it's accessible to everyone rather than just a developers resource.

Lastly, any and all contributors will be warmly welcomed here so please make yourself known, let others know, but mostly, please get involved.

Thanks Again Chris

Sociorobotics Blog: http://sociorobotics.wordpress.com ~ Wikipedia: http://en.wikipedia.org/wiki/Sociorobotics

They released the full schematic? Awesome!

My blog: http://qiaosong.tk My co-founded robotics company: http://cyberwirx.com

RoboaRovio said:... If you PM me Chris I will add you as an administrator and you can also have a good look around and let us know your thoughts, that goes for you too Milw and anyone else who would like to get involved (vinnie)...

thanks RoboaRovio, if you can add me, I have a sourceforge account already- i'll PM you my username and my email. Great start! I'll dig into my backups and notes.

@Vinnie: Think there is a confusion, i'm not the one behind RovioCommander. I decline credits :)

As for LEDS, there is the MCU method described in : turning-off-Rovio-s-lights-without-hardware-modification thread.

I was unable to shut off LEDs when Rovio is docked, seem the MCU take over to indicate charging state. Not sure it is feasible to bypass this.