YART = Yet Another RCode Tool |
Please refer to separate pages for other models:
Overview
YART is a simple drag-and-drop tool for customizing the behavior of existing YART-enabled personalities.YART is not a replacement for more powerful RCODE programming tools like Master Studio or AbNet, but it is a great place to start.
YART_APG (Audio Personality Generator) is a separate tool for converting audio files (.WAV files) into AIBO actions.
Supported AIBOs
- ERS-110/111 supported with YART 11x.
- ERS-210 supported.
- ERS-220 supported.
- ERS-311/312/31L supported.
Required Hardware:
- An ERS-210 model AIBO OR
- An ERS-220 model AIBO OR
- An ERS-31x model AIBO (311 Latte, 312 Macaron or 31L Pug)
- A Pink Programmable Memory Stick (AKA "PMS" or RCode stick) - ERA-MS008 or ERA-MS016, $34->$39
- A memory stick reader to install the software (Use only Sony brand stick readers)
Installation:
- Put an available PMS stick into your computer's stick reader
- Select any folders you see at the root of the stick (usually OPEN-R and CUSTOM) and delete them. Do not format the stick.
- Download the proper RCodePlus runtime for the model of your AIBO.
- For the ERS-210: RCode Plus 2.52 'A' (210)
- For the ERS-220: RCode Plus 2.52 'A' (220)
- For the ERS-31x: RCode Plus 2.52 'A' (31x)
- (Save this .ZIP file on your computer. You may want to use it again later.)
- Unzip this RCodePlus file to the root of your PMS memory stick.
- RCodePlus 2.51 'A' contains the latest version of YART and YART_APG (.05). There is nothing else to install.
- On your PC, run the program "\CUSTOM\YART.EXE" on the memory stick
- See instructions below
NOTE: If you install other non-YART personalities (eg: Disco or DogsLife) on top of it, you will replace the RCODE program.
YART Tutorial
After installation, you can go through the YART Tutorial which will cover the basic operations, including how to add your own audio files (using YART_APG).YART Overview
The user interface is relatively simple:Step 1:
On the upper left is the conditions tree ("When this happens"). Select a condition from this tree. You can expand or contract the groups.Step 2:
On the upper right is the most important window, the code window ("AIBO does this"). This shows the RCODE statements that are executed when the selected condition happens. Read what is here, and decide if you like it or want to change it.Step 2B:
If you don't like what is in the code window, grab it with the mouse and drag it out of the window (that will delete it).Most PLAY statements are followed by a WAIT statement. They go together, so delete both if you don't want them.
Step 3:
In the middle is a dropdown list of Action categories ("Available Actions"). When you pick a new Action category, the list below it fills with the available actions.Action categories include:
- Standard - basic things like sitting and standing, walking and killing time.
- LEDs - turning certain LEDs on or off (model specific)
- User Actions - provides access to user actions (see below)
- System Actions - built-in actions, in many different categories (see below)
- Subroutines - for more complicated things like Name Registration and Take a Picture.
Step 4:
Browse through the Action list (below "Available Actions") and find one you want. Grab the item you want and drag it into the code window. It will expand to the appropriate RCODE statements. For most things this is usually:
PLAY ACTION system_action_name // comment
WAIT
_or_
PLAY ACTION+ user_action_name // comment
WAIT
NOTES:In this case "WAIT" will wait until all actions are completed (ie. the action performance is over).
If "WAIT" is followed by a number, that is the number of milli-seconds to wait.
Some actions have "_NOWAIT" in the name, because they repeat the same thing over and over. Use these with caution (you should stop them with "PLAY ACTION STOP", see "Standard"/"Stop playing").
Step 5: Repeat
Repeat the process to add more actions (step 4), or actions from a different catetegory (step 3&4) or for a different condition (repeat steps 1,2,3 & 4). When you are finally done, press the "Save RCODE program to memory stick" button and try out your creation in your AIBO.Step 6: Test, Repeat
After testing it out in your AIBO, put the memory stick back into your PC, and run "\CUSTOM\YART" on the memory stick again. Do what is needed to fix or otherwise improve your creation.User Actions
The "User Actions" list is empty when you first install YART. You can create your own user actions using Master Studio or YART_APG. You can also borrow user actions from existing personalities (like DogsLife or ObeyCat or Cartman). Please see the YART Tutorial for how to turn your own audio files into user actions. See the YART Advanced page for how to borrow user actions from existing personalities.System Actions
There are many model independent actions built into AIBO. Over 350 of them are named and provided by YART. The same action names will work in the ERS-210, ERS-220 and ERS-31x series AIBOs.These are built in system actions, and act smoothly. These are the essentially the same actions used in the main "AiboLife" personality (and will be used where appropriate in future DogsLife personalities)
If you don't care about the ERS-31X, you have an addition 225 ERS-2x0 specific actions available to you as well (see below under "O2_" actions).
System Action Categories
System Actions are categorized by how they are used by AIBO. This is not necessarily what the performance does (but more what AIBO means to say). You can pick the category in the YART "Available Actions" dropdown list. The "System: " actions are listed below.- ALONE_??? - Play Alone - things AIBO does by himself
- HUMAN_??? - Play with Human - things AIBO does with you
- ROBOT_??? - Play with Robot - things AIBO does with other AIBOs
- OBJECT_??? - Play with Object - things AIBO does with things (usually pink balls)
- EMOTION_??? - Show emotions / moods (joy, fear, disgust, ...)
- FEELING_??? - Show feelings (bored, embarrased, dislike, ...)
- PHYSIO_??? - Physiological reactions (cold, hot, itchy, peeing, ...)
- REQUEST_??? - Requests (play with me)
- REFLEX_??? - Reflexes (react to noise or surprise)
- INTENT_??? - Show Intentions (just say no)
- OFF_??? - Offsensive (attack, provoke, escape)
- GUARD_??? - Guard / Defensive (attack, cover, threaten)
- CONTACT_??? - Contact - AIBO raises paw to touch something (in different locations)
- TACTILE_??? - Tactile - Reactions to being touched (hate it, pressed, tickled)
- CHGPOS_??? - Special case position changes (advanced)
- SEARCH_???, FOLLOW_??? - Ball search and tracking (advanced)
- SYS_??? - System specific warnings etc
- O2_??? - Only on ERS-210 and ERS-220 (see below)
Model Independent Actions
If you create an RCODE program using these actions, you program will immediately work on any other model AIBO with no translation. For example:
EMOTION_ANGRY1_SLP = Aibo showing anger, when in the sleeping position
PHYSIO_EXCRETE0_STD = Aibo excreting (peeing) while standing
_SIT = AIBO is sitting
_SLP = AIBO is sleeping (laying down)
_STN = AIBO is on the station
_ANY = any posture
_SND = audio only (posture doesn't matter)