Go to Post It isnt about winning and losing (although getting the trophies and medals are nice) - Winged Wonder [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

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #5   Spotlight this post!  
Unread 06-03-2011, 14:29
jmanela's Avatar
jmanela jmanela is offline
+1 is BIGGER than -1
AKA: Joshua Manela
FRC #2586 (Fondy Fire)
Team Role: College Student
 
Join Date: Aug 2008
Rookie Year: 2009
Location: Michigan
Posts: 314
jmanela is a splendid one to beholdjmanela is a splendid one to beholdjmanela is a splendid one to beholdjmanela is a splendid one to beholdjmanela is a splendid one to beholdjmanela is a splendid one to beholdjmanela is a splendid one to behold
Re: (Programming) Lessons learned from week 1?

For some reason, we were having trouble with the holomonic drive vi. During all of practice our drive was working fine. There were no troubles at all. Then all of the sudden, at the competition our robot begins to lose code every once in a while. We got an error message stating that we were starving the code, however when we got rid of all code that was unnecessary we were still getting the same problem. We decided to run a blank labview project just to test and see if it had worked out of the box, and it did. Then, I replaced the standard tank that the project comes with, with a mecanum Cartesian drive vi. We got the same message and received our robot would occasionally lose code as it ran like it used to. We ended up writing our own version of a tank using strictly motors and that worked. however, we still don't know why the mecanum drive would not work.

Our programming mentor suspects it had something to do with the safety config vi, however, I read up on it and if i read correctly it would just stop the motors if they didn't recieve and input within a certain time period. However, our problem was quite the opposite where all the values on our robot would stick when we lost robot code for the quick times that we did.

Any ideas?
__________________
||2009|| Entrepeneurship Award, QF - Traverse City | Rookie All Star, QF - Detroit | Highest Rookie Seed, Rookie All Star, QF - Michigan State Championship | Finalist - MARC ||2010|| Engineering Inspiration, Website Award, SF- Kettering | Judges Award, Website Award, SF - Detroit | Website Award, Winner, Michigan State Champ //Thank you 469 and 1918!! | Finalist - MARC ||2011|| Engineering Inspiration, Website - Kettering | Entrepreneurship, Website, Finalist - Waterford | Website - MSC
Reply With Quote
 


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 21:02.

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