Flat Sequence Problems

[Darthjawafett]

Alright so in autonomous I want a flat sequence of events. Where the robot moves forward stops turns right so that its left side faces the goal and then I want its shooter mechanism to work. I programmed it to do this if it sees the goal is hot and what happened was that it ran all of that code at the same time. I do have wait timers programmed in the sequence but it still runs all of it at once.

[mgerber]

Could you post a picture of your code?

[Darthjawafett]

[Alan Anderson]

Originally Posted by Darthjawafett

...it still runs all of it at once.

Can you clarify what that means? Your drive motors are being asked to do three different things in sequence. What do they actually do when the code runs? When does your solenoid actually change state?

[Mark McLeod]

You need to stop the motors in the last frame.

[Darthjawafett]

Alright so what happens is that when autonomous is run the pistons change state and the motor runs forward while turning at the same exact time. What I want the robot to do is to move forward, then stop, then turn, then stop and when it turns i want the piston to change its state.

Any Suggestions?

[Mark McLeod]

Does your Telop driving code work properly?
Could we see that to compare?

Are your speed controllers wired the same on both sides of the robot, or is the wiring reversed on one side?

Did you invert the motors in Begin?

[Alan Anderson]

I don't understand what "motor runs forward while turning" is describing. Is it only one of your drive motors that is misbehaving? Try telling us what your drive wheels are doing.


Does anything in Periodic Tasks also control your drive motors and/or the solenoid?


How is everything defined in Begin? It might help to show us that code too. [A static screen capture is less useful than the actual code -- there is a wire coming into your sequence that runs somewhere we can't follow it, for example. You can select the relevant part of the vi and save it as a vi snippet (from the Edit menu), making a .png file that you can upload as a picture but which we can also run in LabVIEW in order to inspect it more closely.]


What exactly are you doing in order to run autonomous mode? Please be as detailed and specific as you can.

[Darthjawafett]

Teleop is working properly


And the Begin Vi where one motor is inverted to have the robot drive forward when both have the same value.

[Greg McKaskle]

Your wait values are large enough that you can practically turn on execution highlighting and run your code from the run button with the diagram open.

Greg McKaskle

[Darthjawafett]

Here is my google drive with all of the files related to the project. For those who requested it
https://drive.google.com/#folders/0B...DJMLW04Y0w0Wmc

[mgerber]

The first frame has a delay of 200ms, or .2 seconds. Is it possible that the frame is executing too quickly for you to see? That could explain why it seems to start turning instantly.

[Darthjawafett]

Possibly, but when it was at 1000 ms as its wait timer and it still had the same result. I think the most its wait timer was set to was 2000 ms

[Alan Anderson]

Originally Posted by Darthjawafett

Here is my google drive...

It looks like you haven't given anyone else permission to view that folder.



Looking at the screen shots, I don't see anything in your teleop that controls your drive motors. That was the part that Mark wanted to compare against your autonomous code.

Again, might you have anything in Periodic Tasks that could be interfering with the drive and solenoid outputs?

This isn't very relevant, but I'm also a little curious about your drivebase mechanical setup. It seems unusual to me that it's the left motor you have inverted.

[Darthjawafett]

I've edited my permissions on Google Drive so now you can check the project itself. The way our build team sets up the motors one usually faces the other way from the other motor so I have to invert one so that if both joysticks are moved forward the robot also moves forward