Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VIs that should be re-entrant and aren't #8

Open
SeasDiver opened this issue Nov 13, 2019 · 0 comments
Open

VIs that should be re-entrant and aren't #8

SeasDiver opened this issue Nov 13, 2019 · 0 comments

Comments

@SeasDiver
Copy link

When creating a Master instance, several VIs are not reentrant and should be. While the VIs are not-reentrant, a parallel application that is trying to instantiate connections with multiple Modbus slaves will block if one is not responding. These VIs are:

  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\master\Create Master Instance (TCP).vi
  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\subvis\Modbus API\Initialize.vi
  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\master\Initialize.vi
  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\subvis\Protocol\Interfaces\Network Master\Initialize Master.vi
  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\subvis\Protocol\Serial\Serial Master\Initialize Master.vi
  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\subvis\Protocol\TCP\TCP Master\Initialize Master.vi
  • C:\Program Files (x86)\National Instruments\LabVIEW 2019\vi.lib\Modbus\slave\Initialize.vi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant