Quote:
Originally Posted by Pat Roche
snip
|
As I'm sure you know, programming bugs are never really "random," and as intermittent as this one may seem, there is probably a common thread (perhaps literally
) among the code of teams experiencing this issue. Not that your code is the problem, but your code contains the trigger that reproduces the problem.
Are you doing anything...unusual in autonomous? Something most teams might not be doing? Examples I can think of include: spawning new tasks/threads, using an SPI, I2C, or serial driver, calling native vxWorks API functions, using interrupts on the digital inputs, calling FPGA functions directly, reading/writing files on the FTP server, doing anything network-related. All of these things should work, but perhaps one of them is broken and no one has realized it yet because the feature is so rarely used. I would especially look for anything timing-related, since the problem appear intermittent.
The question that perplexes me is: if the issue is intermittent, why does it always occur two matches in a row?
I'm not FTA or anything...just a guy who has spent a lot of his free time in the past few years studying the cRIO and control system. I would love to see this issue fixed, and am curious to hear if you discover anything.