Hi fellow engineers, I have had issues with adding in vision processing from RectangularTarget.vi into my code for this years robot.
I followed their instructions that are given in the RectangularTarget.vi and created a duplicate folder, and then pasted it into my Labview Code, however when I do so, it breaks the wiring in Robot Main.vi from DrvrStn Get Mode to Robot Mode above the case structure. When I try to rewire it, it says that I have the wrong type of wire. It does the same thing in the Begin.vi with the wire between the mode selector and the Robot Mode.
In short, replacing my code with the visual programming folder breaks wiring in the Begin.vi and Robot Main between the mode selector and DvrvStn Get Mode, respectively.
Following the Tutorial 8 instructions for incorporating the 2013 example vision code into a new project overwrites Robot Global Data.vi. The example Robot Global Data doesn’t have the Robot Mode in it. I ended up opening another 2013 project and copying the missing enum for Robot Mode back into the Robot Global Data.vi.
To Lemons, only the wiring between DrvrStn Get Mode and Robot Mode are broken, I’m at home now, but I believe all the other wiring is fine, except the wiring in begin.vi where the wire connecting to Robot Mode is also broken.
Alan Anderson, I pasted the 2013 Rectangular Target into my code for this year. I followed the description in the Rectangular Target 2013 to duplicate part of the code and import (paste) it into my project for this year. I put the contents of the Visual Processing folder it created, into where the rest of my project was. (also contained the rest of the Vi’s that are in my code.)
Mark McLeod, it gave me the option to replace or rename the new files when pasting them into this years code, I did not delete anything, only replaced them with the files from vision processing.
mswalker, can you link to “Tutorial 8” please? Also what is an enum? Somehow I never thought to copy the Robot Mode from another 2013 project, I’ll try that when I get to school tomorrow, thanks for the great idea. We have a tiny team this year (~4 or 5 people, 6 including a parent and a teacher) so I have been occupying myself with writing and understanding the autonomous code until this works.