First, "software issues" can either be failing to deploy the code properly (including mistakes like not reimaging the cRIO to the right version etc), failing to send the right value to the motor/component (which is not the problem according to you), or calling the wrong devref in Teleop. When everything's defined properly and you send the right value to the motor but nothing actually works, it's probably an electrical problem, though it doesn't mean programmers shouldn't know how to solve them...
I'm gonna echo a bunch of stupid mistakes/solutions we've been experiencing/using before;
*Did you connect your PWMs
the right way? Follow
this PDF, on page 2, you'll see which side is the signal and which is the Ground. You can see the right order for the sidecar's end on the sidecar itself.
If, say, the red wire is "signal" on the jaguar's side, it should be "signal" on the sidecar's side too. Don't follow any other guidelines about that matter.
*Does the victor/jaguar get ANY input? AKA, when you enable your code, does it change its indicator led from slow flash to constant light? Does the led seem to respond to your input despite the fact that the motor wouldn't? Do you get a slow, flashing RED light at any point?
*Have you tried following an FRC example for controlling and testing a motor? When things don't work, always go to an example first as they are properly defined right from the get go, and they usually have a little chart showing you how to connect your component right.
*Have you connected fuses?
*Have you made sure your digital sidecar module is connected to the
2nd slot in the cRIO?
*Are any sensors/spikes working?