Quote:
Originally Posted by krupinski
ok.... this is darty's captain.... the problem we have is a code issue... when we finished the benchtest the jags were working fine.. we upgraded the cRIO and driverstation, then tested with the preloaded arcade and it worked still.... we then deployed our own code that was made from the tutorial mentioned above, when we deployed however the jags received no pwm signal from our code... we wasted a few days trying to fix it to no avail... when this didnt work, our programers reimaged the cRIO to get back to what we knew worked,the default code... we then tested and the cRIO performed fine.... we then deployed our code again and the pwm signal was missing again.... what darty needs to know is how to get the signal to the jag from the cRIO, that is to say, what is the code needed to program the pwm for the jags.... long story short, all our programers left last year and this is our programing teams first year... they need help.. BAD!!!
|
Make sure that you reset the cRio after downloadiing the code. If you've re-flashed, you MUST do a complete power down to init the FPGA. I would recommend connecting a terminal program via the RS-232 port on the cRio so that you can see exactly the error that is causing the nocode condition. That's how we fixed ours. Its pretty hard to understand what is wrong with the code without knowing why. Error messages will be displayed via RS-232 with codes that correspond to vxworks errors and warnings. HTH