Using the cDAQ-9136 without embedded controller

[barney99]

We are working on a project where a client would like to use their cDAQ-9136 chassis with one or more NI-9205 modules.  We have accomplished this successfully using the cDAQ-9184 (replaced apparently with the newer cDAQ-9185) interfacing with an external PC computer (Laptop running LabWindows).  We would like to use the cDAQ-9136 with an external PC computer and basically bypass the imbedded computer.  However, when we connect an external PC computer to the cDAQ-9136, it does not show up as a network device in NI-MAX.  I have two questions:  

A) Can we use the cDAQ-9136 with a LabWindows application on an external laptop bypassing the imbedded computer?

B) Can we get the cDAQ-9136 to connect as a network device from NI-MAX running on our laptop?

[ZYOng]

No, it is not possible. You can connect and interact with the cDAQ-9136 using the application development environment from the host PC. However, for production deployment, you should build and deploy your CVI application to the cDAQ-9136, regardless if it is running Windows or Linux. You might need to build additional RT-HMI communication logic. See Table 4 in Understanding Communication Options Between the Windows HMI, RT Processor, and FPGA

While it might seem that having the embedded controller makes everything more complicated, the existence of the embedded controller provides some benefits, e.g. shorter latency and lower risk of interruption due to network disconnection.

Another alternative would be using ni/grpc-device. You can use the same client API to communicate with the server running on the laptop for cDAQ-9184 or cDAQ-9136 (WES or Linux RT).