Jump to content

Modbus I/O Server


monti

Recommended Posts

I have been successful in communication with a Delta PLC using Modbus library support & even built some projects using this method of communication with more than one PLC.

What I want to be able to do is to use the 'Modbus I/O Server' to set up the elements in my project & not have to use the Modbus function or code fragment that I have used before. Please also clarify the following.

1. The thing should work with just the Modbus I/O server & a VI

2. It should also work with DSC

I am having major problems regarding both these areas. While there is a lot of stuff out there & some 'very high level' opinions on what to do, it leaves me none the wiser about how simply go along & get a simple data exchange from a PLC using ethernet modbus & set up an alarm function to it with the DSC module.

I have used LV to develop a project with many I/O's & a lot of simulation. Understand most of the structures & tricks about getting data around

Link to post

Hi Monti,

The biggest barrier for most people to the modbus IO server is that you have to have the DSC module. But if you do have it the it makes modbus much simpler and you get the features such as alarming.

The best thing I'd suggest is give it a go. If you don't have it already download a trial of DSC and follow some of the examples.

Cheers,

James

Link to post

Hi James,

Thanks a lot for replying. I do have the DSC module. I 'm a bit confused as regards how it all fits together.

What I have done previously was to use the 'Modbus library' functions & write out an app for conencting to the PLC's. This works fine though I have the task ( cumbersome ) of defining the Modbus commands, length of registers to be read etc & then use a shift register approach to switch between the MOdbus commands.

What I was hoping for in the Modbus I/O server was to be able to define all this during the creation of the I/O server & be absolved of it all later on. This is typically what you do when using other SCADA systems. I'm sure this will work with LV as well but can't seem to peice it together.

Many thanks.

Link to post
  • 4 years later...
13 hours ago, Meriem Ait said:

Hello,

I'm trying to connect labview with a datalogger using modbus but i don't have the modbus in the version of labview that i have.

LabVIEW does not ship with Modbus communication. That feature is part of the Data Supervisory and Control module (DSC). There is the Plasmionique Modbus Master  in the download section that may do what you're needing (I've not used it) and the NI Modbus code on the NI website.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Porter
      View File Plasmionique Modbus Master
      This package contains the Plasmionique Modbus Master library for LabVIEW.
      It supports RTU, ASCII and TCP modes with the following function codes:
      0x01 - Read Coils
      0x02 - Read Discrete Inputs
      0x03 - Read Holding Registers
      0x04 - Read Input Registers
      0x05 - Write Single Coil
      0x06 - Write Single Register
      0x07 - Read Exception Status
      0x0F - Write Multiple Coils
      0x10 - Write Multiple Registers
      0x16 - Mask Write Register
      0x17 - Read/Write Multiple Registers
      0x2B/0x0E - Read Device Identification
      Other features include:
      - Sharing a COM port across multiple Modbus sessions using VISA locks (10 second timeout).
      - Sharing a Modbus session across multiple communication loops.
      - TCP transaction ID handling to ensure that requests and responses are matched up correctly in case responses are received out of order.
      - Modbus Comm Tester, available through the "Tools->Plasmionique" menu, for testing communication with a slave device without writing any code. 
      - Detailed help document available through the "Help->Plasmionique" menu.
      Examples are included in "<LabVIEW>\examples\Plasmionique\MB Master\":
      MB_Master Comm Tester.vi: Demonstrates usage of API to open/close connection and communicate with a Modbus slave device. MB_Master Multiple Sessions.vi: Demonstrates usage of API to open concurrent Modbus sessions. MB_Master Simple Serial.vi: Demonstrates polling of a single input register over serial line. Download a copy of the user guide here: MB_Master - User Guide.pdf
      Note that Version 1.3.4 of this library has been certified compatible with LabVIEW and has been released on the LabVIEW Tools Network: http://sine.ni.com/nips/cds/view/p/lang/en/nid/214230
      The most recent version of this library will always be released on LAVA first before going through NI's certification process.
      ***This project is now available on GitHub: https://github.com/rfporter/Modbus-Master
      Submitter Porter Submitted 04/01/2016 Category LabVIEW Tools Network Certified LabVIEW Version 2012 License Type BSD (Most common)  
    • By Porter
      This package contains the Plasmionique Modbus Master library for LabVIEW.
      It supports RTU, ASCII and TCP modes with the following function codes:
      0x01 - Read Coils
      0x02 - Read Discrete Inputs
      0x03 - Read Holding Registers
      0x04 - Read Input Registers
      0x05 - Write Single Coil
      0x06 - Write Single Register
      0x07 - Read Exception Status
      0x0F - Write Multiple Coils
      0x10 - Write Multiple Registers
      0x16 - Mask Write Register
      0x17 - Read/Write Multiple Registers
      0x2B/0x0E - Read Device Identification
      Other features include:
      - Sharing a COM port across multiple Modbus sessions using VISA locks (10 second timeout).
      - Sharing a Modbus session across multiple communication loops.
      - TCP transaction ID handling to ensure that requests and responses are matched up correctly in case responses are received out of order.
      - Modbus Comm Tester, available through the "Tools->Plasmionique" menu, for testing communication with a slave device without writing any code. 
      - Detailed help document available through the "Help->Plasmionique" menu.
      Examples are included in "<LabVIEW>\examples\Plasmionique\MB Master\":
      MB_Master Comm Tester.vi: Demonstrates usage of API to open/close connection and communicate with a Modbus slave device. MB_Master Multiple Sessions.vi: Demonstrates usage of API to open concurrent Modbus sessions. MB_Master Simple Serial.vi: Demonstrates polling of a single input register over serial line. Download a copy of the user guide here: MB_Master - User Guide.pdf
      Note that Version 1.3.4 of this library has been certified compatible with LabVIEW and has been released on the LabVIEW Tools Network: http://sine.ni.com/nips/cds/view/p/lang/en/nid/214230
      The most recent version of this library will always be released on LAVA first before going through NI's certification process.
      ***This project is now available on GitHub: https://github.com/rfporter/Modbus-Master
    • By Porter
      NI Labs Modbus API is now on GitHub!
      Password protection of VIs has been removed.
      https://github.com/NISystemsEngineering/LabVIEW-Modbus-API
    • By ensegre
      This is a DSC module question: has anybody here experience with building standalone executables which include shared variables bound to DSC modbus i/o servers? I have an issue with deployment, possibly related to licensing. I posted on the dark side, but haven't got feedback yet.
      https://forums.ni.com/t5/LabVIEW/shared-variable-bound-to-Modbus-i-o-not-working-in-deployed/td-p/3809801
      TIA, Enrico
    • By daoudi
      Hi,
      How i can to send the data through modbus TCP/IP (behavior of a PLC) and receive the data in other client computer with ( station , I/O ADRESSE)
      can you send me an example for this operation please.
       
      Thank you for your help.
       
       
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.