
elfege
Hello,
I'm trying to control my WowWee Rovio through httpget cgi commands with EZB scripts manager and so far it works but I can't get it to work with the user account I have set. Since it's connected to the Internet it's unimaginable to use it without user security.
For example I can get it to go home and dock with the following command :
httpget(http://192.168.0.142/rev.cgi?Cmd=nav&action=13)
But it works only if I deactivate the user security feature.
I tried to input user and password as follows :
httpget(http://192.168.0.142/rev.cgi?user=USERNAME&password=PASSWORD&Cmd=nav&action=13)
but it doesn't work. I must be missing something, I guess.
I'm using this documentation (below) to find out the solution but I can't find an answer to my question, perhaps and probably because I don't understand all the grammar in cgi commands. So if someone knows out I could work this arround, that would be great. I've been looking since yesterday now.
http://www.wowwee.com/static/support/rovio/manuals/Rovio_API_Specifications_v1.2.pdf
Many thanks,
Elfege
PS : since I already pay for a fix IP address I'm very relunctant to use a DynDNS account.
But I do need to find the time to get my InMoov in costume to try and win that $500 in EZ-Money
Thanks for the links, I had not seen the last two.
https://github.com/jcrona/rovio-fw
I like that 10 years ago they had already solved the self charging issue in what seems to be a simpler way to reproduce than the Roomba/ Neato solution. If nothing else, this will be a good experiment platform for future robots (and it looks so cool, who could resist....)
I do have one issue, and wondering if it is my hardware or endemic. When I use one of the commands to turn x degrees, the back wheel never stops and it keeps going in circles until I give any other navigation command. Happened with original firmware, so it is not something that broke in the new firmware. I don't think it is wiring because all other navigation commands work fine, so the wheel is definitely controlled.
Other observations. I find it strange that it will not charge when powered off. I first thought I had a bad battery until I read in the manual that it needs to be on to charge. Even with the new firmware that can control the blue LEDs, it can't control them when it is docked and charging, so not something I can have turned on and ready in a room that I don't want lit up in blue all the time.
Alan
I'll open it up one day soon and check for loose connections or burned components. Still a cool looking robot, and my cats love it almost as much as Roli. They both come running to watch every time I turn it on.
Alan
I have successfully breadboarded a room 9 module using a NE556 timer. Still working on an enclosure with a lens so it will work much like the Rovio base.
But still have not figured out how the navigation actually works to the point where I can start coding it in ARC.
@Alan Have you used the GetMCUReport() to check if the encoder count is changing for the read wheel?
/rev.cgi?Cmd=nav&action=20
it seems they have very cheap wifi card build in.most of users change,
the wifi card with a more exspencive one to solve the problem.
if i understood ,the rover use wifi for docking?
I have not yet. I am still just playing around with the built in web interface. Haven't had a huge amount of time to use it yet, but that is a good idea to try.
Alan
Alan
There are 4 LEDs 2 are IR the other 2 are visible light. The 2 visible light are just for aiming not used for navigation. the 2 IR, each have a set frequency they pulse at with a 50% duty cycle. Here is a freq chart
RMID LED# Target Freq Hz
0 1 3040
0 2 2010
1 1 4050
1 2 3090
2 1 4170
2 2 3210
3 1 4290
3 2 3330
4 1 4410
4 2 3450
5 1 4530
5 2 3570
6 1 4650
6 2 3690
7 1 4770
7 2 3810
8 1 4890
8 2 3930
9 1 5010
9 2 4050
If you use the API command:
http://ipaddress:port/rev.cgi?Cmd=nav&action=1
This will generate a report that looks like this:
Cmd = nav\nresponses = 0|x=3471|y=1632|theta=-3.065|room=0|ss=18210\n|beacon=0|beacon_x=0|next_room=9|next_room_ss=37\n|state=0|ui_status=0|resistance=0|sm=15|pp=0|flags=0001\n|brightness=6|resolution=3|video_compression=2|frame_rate=30\n|privilege=0|user_check=0|speaker_volume=5|mic_volume=5\n|wifi_ss=212|show_time=0|ddns_state=0|email_state=0\n|battery=117|charging=72|head_position=203|ac_freq=2\n
If x and y both have numbers and room=0, I think that should be good.
I have written an EZ-Script that gets this info and parses it into variables if you are interested.
here a little text for the docking of the rovio.its from robotcommunity.com.
rovio comm
Code: