>but we are not so much interested in modifying behaviors, but to study how they change after robot interaction with children.
>>Can you describe your setup and program goals in more detail?
our main hypothesis is that using 'standard' rb_Pleo behaviors, we could associate changes in rb_Pleo's internal variables with user's interaction. In fact, this is the main proposal with pet robots, to evolve social variables according to interaction. Obviously, it would be wonderful to know how standard behaviors' logic is, or, at least, to work with a simplified version (no need for food, for instance). Programming from scratch a completely new behavior is out of our scope since we are more interested on interaction than programming. However it would be very interesting to inhibit some features in order ti simplify variables' relationships.
Another interesting point would be to monitor variables through some wireless element, as it was able with ugobe Pleo. A funny video was made available in youtube with bluetooth some weeks ago, but either, it is a fake or a 'soon improvement' by innvolab, not ready for the current version.
>>When running do your Pleos need to communicate with a separate computer, or can they run stand-alone?
[You can still write programs on the non-RB UGOBE Pleo, and trivially port it to the PleoRB.]
They can run stand-alone, but, obviously, it would be an interesting feature to have wireless communication.
>> Have you tried doing something similar on the non-RB UGOBE Pleos?
No, we made the Xbee hack on one of them and we were expecting that it would be possible to do in the new rb_Pleo. In fact, information from camera would be of interest, but there is not enough memory to save data, neither wireless communication is possible.
>>However it sounds like you are NOT interested in writing your own personality, but using the built in personality.
>>I don't know if that will work without significant customization of the personality (which is difficult) or rewriting the personality (which is also very difficult).
yes, a simplified default personality would be the most interesting one, but we can arrange with the built-in personality. Our initial programming problems are more in the variable-reading side.
---
>>Additional comments:
>>* Pleo_rb 'internal values' (we're interested on them before and after interaction) can be checked and/or modified by using statsrb_v11, proberb_v1 and >>changerb_v1 (thanks a lot PleoPet)
>>That only works if you use the default personality (or one with minor tweeks)
how to program minor tweeks without interrupt the main program? Which kind of small modifications could be done? Do you have some example that we can use to extrapolate? I read you were able to un - scary a Pleo when no-light was present. Is it very difficult to make this kind of modifications or inhibitions in the default behavior?
>>* Pleo_rb USB connection is currently a nightmare. It seems that the USB BatteryAdapter (degers) should work. Could you send me any feedback? Works it? >>However, we cannot obtain pdf instructions. Could you help us?
>>Unfortunately that special build USB adapter didn't happen.
http://bobthepleo.com/forums/index.php?topic=2329.0>>You can make your own with a few jumper cables (extend the 3 battery leads), but it is not a good way to run the robot normally since it needs an external >>power supply.
Thanks for your assessment.
>>* Windows7x64 seems that will not work. Will W7x32 works? I mean, is it possible to obtain drivers?
>>The W7x32 drivers do work partially, but last I tried they didn't actually work as a serial port.
:-(
>* finally, a lot of doubts about about dino-mite. Will dino-mite_v102 work with the previous configuration?
DinoMite doesn't work on a PleoRB for a number of reasons. Even if it did, the difficult access to the USB port prevents you from using it for real PleoRBs.
:-(
Thanks a lot, again, PleoPet for your reply. We are starting to work with statsrb_v11 and changerb_v1.