Go to Post I...want...to...go...to...Champs. REALLY REALLY BADLY. - CalTran [more]
Home
Go Back   Chief Delphi > Technical > Programming > NI LabVIEW
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 31-01-2014, 17:51
Laxkief9098 Laxkief9098 is offline
Registered User
FRC #4557
 
Join Date: Jan 2014
Location: Connecticut
Posts: 17
Laxkief9098 is an unknown quantity at this point
Code suddenly not working

We are a second year team and pretty familiar with labview. We made a new robot project and added our our drive code. It worked. Then we added 3 other Sub Vi's in the tele-op Vi. These VI's execute an encoder, a gyro (drive straight), and a shooting sequence. We deployed the updated code and the drive system stopped working. Between the two deployments we changed the motor controllers (we have changed them in the programming as well). The Robot code Boolean on the driver station keeps cutting out and then the CRio discontinues communication, however the robot is still on and connected. We have run a default program and it works. Any ideas???/ please help!!!
Reply With Quote
  #2   Spotlight this post!  
Unread 31-01-2014, 18:02
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,795
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Code suddenly not working

The phrase "shooting sequence" combined with "...added 3 other Sub Vi's in the tele-op Vi." might indicate that your sequence doesn't immediately return to Teleop, but holds on and doesn't let anything else continue.
Teleop may be grinding to a halt.

Look at or tell us if what you implemented includes delays and/or loops.

If you'd like us to really identify the problem we'll need to see your vi's.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Reply With Quote
  #3   Spotlight this post!  
Unread 31-01-2014, 23:17
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Code suddenly not working

Things that sound like "shooting sequence" typically belong in the Periodic Tasks vi. If it either includes either explicit delays or waits for robot actions to occur based on sensor input, it's not likely to work as part of Teleop.

Teleop gets called each time a new data packet is sent from the Driver Station with joystick/gamepad/Cypress input values. It needs to do its job and end quickly. If it hasn't finished running before the next Driver Station communication occurs, it'll disrupt the vital communication tasks, and the robot will probably report a "loop running slow" error.
Reply With Quote
  #4   Spotlight this post!  
Unread 01-02-2014, 08:19
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Code suddenly not working

The project contains a folder called Support Code and in it is a VI, Elapsed Times.

If you place this in teleop and interactively run your project, you can then open the panel of the Elapsed Times and it will display how long between calls from that location. If it is more than 20ms, you probably have too much in teleop.

This VI can be used for vision loop and periodic task loops as well.

Greg McKaskle
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 09:53.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi