How to use eeprom in labview

[Greg McKaskle]

Inside the loop, the code compares the millisecond tick time to 1500. The millisecond tick is relative to when the robot booted, or when the app started, and keeps going up until it wraps. More than likely, the code should take the time when the button latched, subtract from the current time, and compare to 1500.

Also, personally, I'd take the time, X, and Y, and write them to a single file rather than having the data spread amongst two with duplicated times. This also extends if you add a manipulator or another degree of freedom to the robot or even sensor values that record the response of the robot.

Greg McKaskle

[windtakers]

The Thing I'm having trouble with is the tick counter. Because i only want the joysticks to be recorded for 15sec, but because the tick counter starts at the robot boot up and not when the case is true the tick counter is already over 15sec even before i get to actually wanting to record the joysticks.

[Mark McLeod]

It goes something like this, although this example is for a different purpose you should be handling the time in a similar fashion:

[windtakers]

this is awesome, and by the way i use your team website for labview help all the time. can't believe i didn't see this one. I think I have the timed task all done now. when I extract the data in autonomous that was saved into the spreadsheet i know that i need to tell the motors how long to run on a certain speed, but i don't know how to do that. Also this is a picture of my updated periodic tasks.

[Mark McLeod]

To play it back you can run a While loop inside the Autonomous vi

• Set initial conditions, e.g., pseudo-joystick values = zero
• Feed initial pseudo-joystick values into motor set speed
• While forever loop (with an appropriate delay)
  • Read one playback line
  • In an inside loop (with an appropriate delay)
    • Keep checking until elapsed time >= recorded Robot Time (make sure the times are measured the same)
    • When the condition is true, pass the new pseudo-joystick values out, exit the inside loop
  • Feed pseudo-joystick values into motor set speed
  • Make allowances to set speed to zero after the last playback line is read as a safety measure (that'll also help handle partial/incomplete playback files)

[windtakers]

Here is a picture of my autonomous. Can you tell me if it's programed right.