[alopex_rex]

I've had this happen many many times, and it's always the result of a code issue. There are lots of things that won't cause compiler errors, but will cause the code to crash (and when the code crashes, the driver station will say there's no code.) Right after merging together a bunch of code is a prime time for errors to pop up. There's lots of things that could cause it; in the past it's often been variables that are used without being initialized, and this year we've done it with SmartDashboard (eg trying to read a variable that doesn't exist).

The best thing to do is often to comment out broad swathes of code, until it stops crashing, then to slowly add stuff in until you figure out what the problem lines are. If the separate parts worked by themselves, the natural first place to look would be the joints where they come together.

Hope this helps!