For anyone who used to be in FLL

[Res0lu7ion]

This is probably a longshot but I'm having difficulties programming my old RCX block.

I'm trying to make it so i can use a wired "controller" made of push sensors react to the motors. Can someone check my programming because it doesn't seem to want to work.



I already posted this in the FLL section but there's been alot of inactivity there recently so I was hoping I could just get help here.

[Bob Steele]

How do you know the difference between a lot of inactivity and a little inactivity?
sorry
just wondering

[Laaba 80]

What is it doing when you test it?

[Phoenix Spud]

So, let me see if I'm reading your code correctly...

You want to have 3 touch sensors controlling the robot. Port one is for the A motor, three for the B motor and two is an "abort" button. When a touch sensor is pushed in the motor it controls moves backward but when it isn't pushed it moves forward. Did I get all this correctly?

Also, what version of RoboLab are you using?

It appears to me that your abort button isn't working. To correct this, in your first task put a "delete tasks" icon. (I believe it looks like a split icon but has a broom on it.)

It also looks like it will have a lot of lag. To get rid of this, delete all the one second waits.

Hope that helps!

[ptitchener]

I think that your issue is that you are using subroutines (the blue forks) instead of task splits to fork the program. Subroutines only run when they are triggered in the main program. To fix this all you should have to do is switch the blue forks to brown ones that have a white bottom.
One good way to do this type of program is to have a touch sensor loop that has the the motor block on the inside and the reverse motor command right after it in a loop that loops while the touch sensor is released and then the jump. This makes it so that while the touch sensor is pushed, the motor goes, but when the touch sensor is not pushed, then the motor will reverse, because the loop will end. When the touch sensor is pushed again, the program will jump back to the loop that runs while the sensor is pushed again. I think that this would make it so that you wouldn't need the touch sensor forks. It also would get rid of the one second lag. I've never tested a program like this, but I think that it should work.

[Mike Schreiber]

I believe you need to move yout red and blue down arrows (the jump landings) to the very beginning of the program immediatly after your Green light, otherwise you're ignoring the 2nd sensor the entire time. I would also put an ABC stop after the 2nd sensor and then another jump loop like you did with the others so you can stop and then start up again, this also allows you to take out the wait 1s because you can stop whenever you want by pressing sensor 2. Not sure if I'm right haven't touched robolab since 5th grade, good luck.

EDIT: ptitchener is right the blue forks are subroutines, I'm not sure the brown ones are the right ones either, but they may be.

I think we need an explanation of what you want your controls to do in order to tell you if your code is correct. For example

Push down 1:
Release 1:
Push down 2:
etc...

[Res0lu7ion]

Originally Posted by Laaba 80

What is it doing when you test it?

The middle button is the only thing that actually works.

Also to anyone who was asking sensor one and two wants to move the motor on each side forward or backward when i push it.. I made the sensors like a controller with


[Sensor one here] [Sensor two here] [and Sensor three here]