02-13-2015 09:09 AM
Re-flashing the cDAQ's firmware did not fix the issue. Looks like it has to go back to NI