|
Re: Vision processing works in RUN, not in START-UP
OK, I just wanted to post this follow up in case any one else runs into this issue.
We found the root cause of the issue we were having, and it purely was an oversight on our part. We must have looked right at the cause a hundred times, no exaggeration.
Every time we opened up Main.vi to begin calibration, we enabled Vision, and moved on to our calibration of the vision processing code. We never even realized we needed to set "Enabled" as the default state. Thus, when we built and deployed the code as Start-up, vision was set to the default state of disabled. Therefor, vision processing was not taking place on the deployed code.
Once we set it to enabled and set that as the default, everything worked as expected!
__________________
CalGames 2009 Autonomous Champion Award winner
Sacramento 2010 Creativity in Design winner, Sacramento 2010 Quarter finalist
2011 Sacramento Finalist, 2011 Madtown Engineering Inspiration Award.
2012 Sacramento Semi-Finals, 2012 Sacramento Innovation in Control Award, 2012 SVR Judges Award.
2012 CalGames Autonomous Challenge Award winner ($$$).
2014 2X Rockwell Automation: Innovation in Control Award (CVR and SAC). Curie Division Gracious Professionalism Award.
2014 Capital City Classic Winner AND Runner Up. Madtown Throwdown: Runner up.
2015 Innovation in Control Award, Sacramento.
2016 Chezy Champs Finalist, 2016 MTTD Finalist
|
Jon is very right, going forward I have a hard time envisioning any future Championship Chairman's award winners without a significant social media presence. It's just too big of an avenue to be ignored. - Karthik [more] 
Hybrid Mode
