View Single Post
  #9   Spotlight this post!  
Unread Yesterday, 15:43
slibert slibert is online now
Software Mentor
AKA: Scott Libert
FRC #2465 (Kauaibots)
Team Role: Mentor
 
Join Date: Oct 2011
Rookie Year: 2005
Location: Kauai, Hawaii
Posts: 374
slibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud of
Re: NavX causing robot code to reboot

Quote:
Originally Posted by tr6scott View Post
https://www.chiefdelphi.com/forums/s...d.php?t=154205

We are a labview team, we have also had strange issues with NAVX this year...
Hmmm, missed that thread. So I'm curious also when your robot application is initializing the MXP IO (if any), and if that might be contributing to some sort of collision. The best hypothesis I can come up with is a race condition when allocating the MXP IO resources that in turn causes the allocation of SPI and other comm resources to fail (except the first time after loading the app after reimaging). Does this seem plausible to you?
Reply With Quote