Go to Post While we're on the topic of games... there have to be some people who'd be interested in a good round of FIRST ROBOTICS!!!!!!!!!!!!!!!!!!! :p :yikes: :D :rolleyes: - Leav [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
  #1   Spotlight this post!  
Unread 26-02-2011, 01:18
WizenedEE's Avatar
WizenedEE WizenedEE is offline
Registered User
AKA: Adam
FRC #3238 (Cyborg Ferrets)
Team Role: Leadership
 
Join Date: Jan 2011
Rookie Year: 2010
Location: Anacortes, WA
Posts: 395
WizenedEE is a name known to allWizenedEE is a name known to allWizenedEE is a name known to allWizenedEE is a name known to allWizenedEE is a name known to allWizenedEE is a name known to all
Autonomous Independent Can Only Get Called a few Times

When I test autonomous mode, using the "independent" vi, something weird is happening. I wired all the motor speeds and times and such to controls (rather than constants) to make them easy to change on the fly. However, after about five times of enabling, watching it run, adjusting the values, and enabling again, enabling doesn't do anything until I reload the code (click the finish button, then hit the run button again).

I suspect that it might be an error in how the autonomous code is called and aborted. This is because, when I open up the start vi function (in the init case of autnomous), it has a comment saying,

"The BIG problem with the VI refs.We are using a static VI ref to make sure the AutoInd VIis on the controller and doesn't require users to deploy to debug.

We open a new independent ref each time we run because we need to let the AutoInd VI own the ref, or it will be invalid when the agent is closing things down. Because it is owned by the AutoInd VI, it also means the clone ref goes bad when the AutoInd VI finishes. Next time we want to run we need to clone again."

If the controller is taking multiple clones of the vi, would that cause it to stop working after a while? I'm not really sure of what exactly clones are, either.

Also, the comment seems to say that it's not necessary to redeploy to modify the autonomous code. Whenever I try to change something in the block diagram, even when it's disabled and the vi isn't "running", the driver station immediately says that robot code was lost. This isn't such a big problem, but should that work? Is it working for other teams?

I also remember the head programmer from last year saying that autonomous independent was messing up then, which is why we used iterative.

Right now, I'm planning on just using an autonomous iterative vi (like last year) and putting that inside the autonomous enabled case.

If there's any other teams that have had similar problems, solutions, or questions about what's happening, please respond. Thanks!
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 09:22.

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