Rodney, IM going 2B accused of only talking about 1 thing on this forum, but 2 bad. The NVDK is something I know about, and IM the only person I know who has successfully deployed it 4 an MAB app. There must B more, but I looked, unsuccessfully.
3 biggies.
First, steady INPUT torque should be limited to their recommended 48 ft*lb. I say this 'cos my app pushes this limit and has worked flawlessly 4 >2 years, and others who cratered theirs. almost certainly over torqued. They didn't volunteer this, but it seemed obvious 2 me from description of their builds. This torque limit will be hard (but not impossible) to stay under, with your other drive train components.
Second, you need a strong, STEADY, 12 (minimum) volt/5-6 amp power source to shift up with. Otherwise your electronics will cycle off every time U hit a bump, and you will be stuck in low until you reboot (power off, then back on). I made a charge system from scratch - proud of it but lots of work.
Third, your controller has Mickey Mouse circuit board anchoring. The jiggling will tear it loose at the plug in points FU don't gorilla glue them in place. Search kcvale posts from 2-3 years ago, as he took some good pix and gave some good advice on this.
Second post on this today, coincidentally. As I said earlier, I only think a NVDK equipped MAB can work 4 (1) lower powered 20" powered wheel apps like mine, or (2) as jackshafts, spinning faster with less torque.
FUR still interested, check my vids from last year. Overlong, but fairly explanatory and complete.
G'luck!
