Skip to content

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

Description

@SeasDiver

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions