Your cDAQ's IP of 169.254.39.22 means it is looking for (and not finding!) a DHCP Server to assign you another IP temporarily. You effectively "asked for it" by specifying Link-Local.
I have a tiny bit of experience with configuring an NI RIO device's Wireless. If I'm using my Home Network, which has WPA and requires that I know the SSID of my router (but otherwise doesn't have other "corporate" gateways requiring further authentication), I can configure the RIO in two ways -- one is to give it an IP Address in the Router's address space (in my case, 192.168.1.x), and specify "DHPC or Link Local", or to make the RIO a Network Hub, which I think makes it essentially a DHCP Server, in which case the RIO chose its own IP address (in the 10.x.x.x address space, and gave itself an address in the 172.16.x.x range, which I had to specify as the IP address when configuring my RIO's "Property" entry in the Project.
[Sorry -- I know this sounds like mumbo-jumbo -- I don't understand all the ramifications, myself. I will say I initially tried the "Router" route, which is easy to set up in my home, but when I try to do this in a Managed Network (at work), while I can put the PC on the Network (as I can "log on" to the Network), I can't (myself) give the RIO "permission" to join the Network. Reversing things so the RIO configures its own, very limited, "private" network and the PC disconnects from the Corporate Network and connects to the "RIO Network", is more likely to allow us to join PC and RIO without violating Security Protocols.]
Bob Schor
.png){kind=link}