nimodbus.llb vs modbus IO Server in project?

[Andy.C]

I am plan on creating 20+ Modbus TCP Masters on a CRIO and wanted to know if there is any real benefit to using the nimodbus.llb versus creating a modbus master through the project? I want to poll 20+ devices and consolidate the data on a modbus tcp slave on the CRIO. I plan on polling the devices every 500 or 1000 ms. Will there be noticeable performance boost if I use the nimodbus.llb? I personally would like to create the Modbus masters through the project cause its cleaner and easier but I was not sure if performance would be an issue with that many masters running on a CRIO.

[Joe D.]

Hi Andy,

I would use the Modbus I/O server built into DSC. I believe that you will see a noticable performance difference, but the only way to know for sure is to benchmark it. I don't see any issues with having that many modbus master but have not tried it to know for sure. Please post back and let us know how it goes.

Also the following links my prove usefull for you:

Do LabVIEW and LabVIEW Real-Time Support the Modbus Protocol? (this talks about the differences between the I/O server and nimodbus.llb)

Modbus Library for LabVIEW to an FPGA-based implementation for use with the cRIO serial modules.  (really cool)

Please let us know if we can be of any help