Go to Post If I had come up with a chokehold strategy, I wouldn't talk about it on Chief Delphi. - Tom Bottiglieri [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 16-02-2011, 17:37
dahlboy15 dahlboy15 is offline
Vice President
AKA: Dyson Dahl
FRC #3290 (Robo-Bears)
Team Role: Programmer
 
Join Date: Jan 2011
Rookie Year: 2010
Location: Baudette, MN
Posts: 14
dahlboy15 is an unknown quantity at this point
Main vi help-urgent

Ok recently I deleted my old teleop cold and pasted in some new stuff. I deleted EVERYTHING from the old teleop vi and then copied and pasted the new code. The Match Info, Call Context, and LED toggle rate (ms) were copied and pasted into teleop as well. Now in Main vi there are broken wires because it says I have connected two wires of different types. How do I fix this? I have the old code and have tried copying and pasting back into teleop but nothing changes in Main. When I hover my house over the Teleop vi in Main I see no terminals for the wires to be wired into. So I need to know how to fix this because I can no longer build any code because of the broken wires and I don't think I should just delete the wires and try to load again because then I will lose the working code in the robot and frustrate people around me.
Reply With Quote
  #2   Spotlight this post!  
Unread 16-02-2011, 17:55
Ian McShane Ian McShane is offline
Registered User
FRC #3585 (Rogue Robots)
Team Role: Programmer
 
Join Date: Jan 2011
Rookie Year: 2009
Location: NH
Posts: 141
Ian McShane will become famous soon enoughIan McShane will become famous soon enough
Re: Main vi help-urgent

I think you have no choice but to delete and replace the wires one by one, a word of advice, copy don't delete in the future, and also if you are close with everything else in the program, i recomend taking some time and copying it by hand next time(I actually had to do that myself last night when some global data went missing).
__________________
in FIRST, it's process over product, and team over robot.
http://www.roguerobotsof4h.com/
Team 3585 Rogue Robots of 4-H

Last edited by Ian McShane : 16-02-2011 at 17:59. Reason: re-read and understood the question
Reply With Quote
  #3   Spotlight this post!  
Unread 16-02-2011, 18:12
dahlboy15 dahlboy15 is offline
Vice President
AKA: Dyson Dahl
FRC #3290 (Robo-Bears)
Team Role: Programmer
 
Join Date: Jan 2011
Rookie Year: 2010
Location: Baudette, MN
Posts: 14
dahlboy15 is an unknown quantity at this point
Re: Main vi help-urgent

Quote:
Originally Posted by Ian McShane View Post
I think you have no choice but to delete and replace the wires one by one, a word of advice, copy don't delete in the future, and also if you are close with everything else in the program, i recomend taking some time and copying it by hand next time(I actually had to do that myself last night when some global data went missing).
How would I replace the Match info, Call Context, and Led toggle rate parts of the vi?
Reply With Quote
  #4   Spotlight this post!  
Unread 16-02-2011, 18:18
Ian McShane Ian McShane is offline
Registered User
FRC #3585 (Rogue Robots)
Team Role: Programmer
 
Join Date: Jan 2011
Rookie Year: 2009
Location: NH
Posts: 141
Ian McShane will become famous soon enoughIan McShane will become famous soon enough
Re: Main vi help-urgent

See what happens if you replace them with the ones original to the c rio project template that they give us. If you already tried that, i am not sure what to tell you.
__________________
in FIRST, it's process over product, and team over robot.
http://www.roguerobotsof4h.com/
Team 3585 Rogue Robots of 4-H
Reply With Quote
  #5   Spotlight this post!  
Unread 16-02-2011, 18:19
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,833
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: Main vi help-urgent

When you deleted everything, you also deleted all the Inputs they represented that Teleop.vi starts out with.

You can put them back pretty easily, but you have to know what goes where.

You add inputs (and outputs) to a vi from its' front panel.
  • Open the Teleop front panel
  • In the upper-right corner you'll see the Teleop icon, right-click and choose "Show Connector"
  • You'll get a white box filled with tinier boxes, each one representing a possible input or output node
  • Click on one of the tiny boxes, then click on the element or cluster on the front panel that needs to be associated with it.
  • For instance, the bottom-most, left-most box should be associated with the error input cluster.
After you've added the required inputs back in, then go to Robot Main.vi and you will see the Teleop icon grayed out.
  • Right-click and choose "Relink SubVI"
  • Then you will be able to rewire the missing connections if they don't automatically reattach themselves
You can also create a new robot project, copy the Teleop.vi into your current project folder, replacing the corrupted one that's already there.
Then when you delete just avoid deleting the Error cluster, the Match Info, and the Call Context.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 16-02-2011 at 18:37.
Reply With Quote
  #6   Spotlight this post!  
Unread 16-02-2011, 18:22
Ian McShane Ian McShane is offline
Registered User
FRC #3585 (Rogue Robots)
Team Role: Programmer
 
Join Date: Jan 2011
Rookie Year: 2009
Location: NH
Posts: 141
Ian McShane will become famous soon enoughIan McShane will become famous soon enough
Re: Main vi help-urgent

ohhhhhh, i don't think i understood what you meant before, because what Mr McLeod is saying is right. you just did not reconnect the wires.
__________________
in FIRST, it's process over product, and team over robot.
http://www.roguerobotsof4h.com/
Team 3585 Rogue Robots of 4-H
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 20:31.

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