by AlphA » Mon Mar 31, 2008 3:47 pm
by AlphA
Mon Mar 31, 2008 3:47 pm
Have you looked at the behavior control program or the motion data?
While in the "normal state loop", the spider is programmed to perform motion 50 (demo scenario). This is not to simply walk forward until it detects an object. If you look at the motion data, you'll see that motion 50 loops a walk cycle a few times, then turns right. I don't have my CM-5 with me, so I can't confirm exactly what motion 50 is doing. But, I'm pretty sure that's how it works.
So, if your bot stops walking forward, BACKS UP then turns, it is performing its "obstacle response". On the other hand, if your bot simply goes from walking forward to turning right (without backing up), it is carrying out the demo scenario, which is normal.
If it fails to detect obstacles, check your lighting. Bright lights can sometimes confuse the sensors. If I was you, I would throw together a simple program telling the CM-5 to print AX-S1 sensor data. Then, move your hand near each sensor and make sure the data output corresponds.
In behavioral control programmer, replace motion 50 (demo scenario) with motion 2 or motion 3 (forward walks) and you should should have the behavior you want.
Have you looked at the behavior control program or the motion data?
While in the "normal state loop", the spider is programmed to perform motion 50 (demo scenario). This is not to simply walk forward until it detects an object. If you look at the motion data, you'll see that motion 50 loops a walk cycle a few times, then turns right. I don't have my CM-5 with me, so I can't confirm exactly what motion 50 is doing. But, I'm pretty sure that's how it works.
So, if your bot stops walking forward, BACKS UP then turns, it is performing its "obstacle response". On the other hand, if your bot simply goes from walking forward to turning right (without backing up), it is carrying out the demo scenario, which is normal.
If it fails to detect obstacles, check your lighting. Bright lights can sometimes confuse the sensors. If I was you, I would throw together a simple program telling the CM-5 to print AX-S1 sensor data. Then, move your hand near each sensor and make sure the data output corresponds.
In behavioral control programmer, replace motion 50 (demo scenario) with motion 2 or motion 3 (forward walks) and you should should have the behavior you want.