Search the Community

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 License Type BSD (Most common)  

Hi! I'd like to communicate with an OPC UA Server and I'm looking for a solution without using the LabVIEW Toolkit, like using a dll or similar... Has anyone developed something like this yet?

Hi, I am looking for a paid or free course online for LabVIEW instrument control that covers topic like communication protocols, RS232. GPIB etc. Can anyone suggest a good one. Thank You. Govind

I'm using a Labview Shared Library (DLL) to comunicate between a C# program (made by another company) and a labview Executeable (which means different processes) on the same PC. Currently i'm using network published shared variables, to communicate between the Labview DLL and the LABVIEW program (both made by me) which works well, except for the performance. Each time the DLL is called it needs to connect to the shared variable, which takes between 50 and 300 ms. When it is connected, the data transfer is instant. I have tried to use the PSP "Open Variable Connection In Background", which is a bit faster, because it doesn't wait to verify the connection. But it still adds some overhead. I have also tried to use notifiers from this example: https://lavag.org/topic/10408-communication-between-projects/ . Opening connection and sending the notifier takes 50 - 100 ms. I guess both the notifier and the shared variables are "slow" because they use the network communication, even if it is the same pc both programs are running on (localhost). Does any of you know of a faster method of communicating between a program that is running continuesly (connection open constantly) and one only exectuted when new data is ready (connection "re"-opened on every instance)? Thanks in advance. Best Regards Mads

Hi, I would like to ask which method should I use for transferring latest data between determinism process. I don't want to use single process shared variable with RT FIFO enable since it will polling data. I don't want to use the RT FIFO function because I cannot send the latest value. Queue is not determinism. I am not sure if Notify is determinism or not. Anyone with experience about this? Regards, Thang Nguyen

Hi, I am new to this group, so if the post is not in some proper format, I apologize. I am trying to communicate Agilent 8563EC series Signal Measurement equipment. Using the example vi of controlling that instrument, I am trying to modify it to grab the center frequency from the instrument instead of popping the value from labview it self, i.e. I am trying to convert the center frequency from a control to a indicator. But, when I am trying to set the center frequency from the instrument, it is not showing up in labview programmed interface, instead it is changing the value in the instrument itself to 13 GHz, though I am giving it 55 MHz from the instrument. The value is showing properly when I am running the subvi of center frequency alone, but when I am trying to run the complete VI, it is inserting a garbage value in labview as well as changing my instrument parameter of center frequency. Please Help! Thanks.