Labview and Mitsubishi OPC: communication

Hi,
My problem is I have to communicate between a Mitsubishi FX1N and Labview using OPC. I have Labview 8.0 is that enough to communicate or do I need the DSC module ? I want to do I so simple as posible, nothing fancy. Maybe use of global variables ?
Dr. Mackay

Hi
DSC is not necessary to read OPC tags, but it does have a lot of neat features. You can use Datasockets to read OPC tags. A very simple example that demonstrates this is called NI Demo OPC Client and can be found in NI Example Finder. To find the URL of the OPC tags you want to read, you can use DataSocket Select URL.vi.
Regards

Similar Messages

Labview and opc

Hi, currently im using labview to communicate with an OPC server over a network. So i wrote my program a few months ago now. And im still having issues with communication to the remote opc server. The last few weeks i thought id cracked it, but it seems to be losing comms again, not sure if its to do with dcom settings or network settings. It seems to be intermittent, not sure what it could be??
Stuart

Hi Stuart,
I have researched your issue and have found a number of documents which I think could be of use. I have linked these document below.
Good example to use, to communicate with a remote opc server?
Connecting LabVIEW to an OPC Server through a DataSocket Connection
DataSocket Tutorial
I hope one of these helps.
Best Regards,
Christian Hartshorne
Applications Engineer
National Instruments

Labview HDA and DA OPC clients

I have developed a true OPC HDA and DA clients in Labview, using the OPC Foundation's wrapper, to solve some of the problems I was having with the DataSocket for DA access, and to address the non-existent access to HDA servers (historical data access).
Is there any interest or need for these in this community ??
Leo
[email protected]

Hi,
How do you access OPC HDA server using LabVIEW?
Thanks.

Response time between LabVIEW w/DSC module and RSLinx OPC server hosting FlexLogix PLC tags too long

We are experiencing communication response time delays between LabVIEW with DSC module and RsLinx OPC Server hosting all FlexLogix PLC tags (around 500-600 tags).
The nominal response time for the system watchdog is < 500ms, but we occasionally have spikes of up to 1.5 seconds once every few days even when the system is idling.
Changing more than six PLC connected shared variables at the same time from LabVIEW also causes the watchdog response times to spike above 500ms.
Our watchdog is programmed so that LabVIEW toggles the watchdog bit to 1 as soon the shared variable event detects that the PLC has toggled it to 0. The PLC, however, waits 300 ms until it toggles it.
Our system:
Windows XP SP3
LabVIEW 9 F3
RSLinx Opc Server v2.54
Allen Bradley FlexLogix PLC

What is your update rate set for in the RSLink OPC server?
You aren't toggling the same flag from both ends are you?
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Communications between LabVIEW and spectrum analyzer

hi, im a beginner in LabVIEW and spectrum analyzer, and im now trying to let LabVIEW captures signal coming from spectrum analyzer. i have all the required components needed but i have totally no idea how to get started, is there any exercises or labs available here?

It will depend on your method of communication with the device. If it is RS232 you can go to the example finder (Help > Find Examples) and search for RS232 or however you plan on communicating with the device. Or you can browse the catagories for examples on various topics.
Depending on the device the manufacturer may have LabVIEW drivers on their web site. But anybody will need more information on the analyzer and the signals before you can be helped.

Connecting between labVIEW and PLC S7-1200 using EPICS

Hello everyone,
I'm trying to connect between LabVIEW and PLC S7-1200 using EPICS. I did it using OPC and it succeeded and the communication was done, so right now i'm trying to do it using EPICS. so Can anyone help me with that?
Thanks in advance.
Ahmed

Hello,Ahmed:
Now I'm trying to conect S7-1200 to Labview by OPC server 2012, I'm newer for both PLC S7-1200 and OPC server. by the help file of NI's OPC I tested many times, but lost totally.
You mentioned that you have succeeded making the connection between them, could you please help me :
1) How to set in Simense TIA software? I can set the PLC's IP address now, that's all;
2) OPC server setting.
if there is a video, that will be great.
thanks a lot.
Delphi77.

LabVIEW with Siemens hardware communication

My application has Siemens AC Drive with Siemens PC CP5613 card being provided. Communication with the drive is thru' Profibus with LabVIEW. Does LabVIEW have a direct interface to communicate with Siemens CPS5613 card.

Hi!
No, unfortunately direct communication between LabVIEW and this card is impossible. (Theoretically you can looking for examples, which delivered with this card and calling DLLs for accessing, r/w Dual-Port RAM and so on, directly from LabVIEW, or over DLL-wrapper, but this not very easy). So, better way - using OPC server, which normally delivered with this card. Over OPC you can get access to Profibus. You can use OPC.SimaticNET server, or OPC.SimaticNET.DP (inline) server. Better way - using over LabVIEW DSC, but you can also to get acces over DataSocket without DSC (if you have not more than 30 items for reading and writing)
With best regards...

How do I correctly time while loops using SCPI and VISA/Ethernet communication to send DC current Values to a Power supply?

I'm rather new to using labview and I having an
issue with a test Data Aquisition lab I'm trying to setup using a
Keithley 6221 AC/DC current source and a basic PCI M-series NI-DAQmx.
First of all, I'm looking to update the current value on a power
supply at a rate of atleast 10Hz and I'm using SCPI commands and VISA
communication through ethernet to do so. Attached below is the VI I
have written.
The issue I'm having is this:
My VI will
loop through the values fine in software, or so it seems. I am unable
to get the Power supply to update sequentially if I don't set my loop
delay to anything greater than 130ms. If I try to run the loop faster
it starts skipping values instead of counting 1,2,3,4,5,1,2,...etc. it
goes 1,2,4,5,2,4,1,2 on the display of the power supply and my DAQ unit
also skips these values so I know that the number just isn't getting
read to the Power supply in time. I was wondering if this was due to
my sloppy programming or if it is a hardware issue, my computer or the
method of communication to the power supply? Is this due to the fact
that I'm using ethernet and VISA communication? Is there a faster way
to communicate or is GPIB faster? Any input at all would be extremely
helpful.
On a side note: Right now I'm using an pre-determined
array of values that I can update on the fly but in the future this
with be put into a closed-loop control system. The value for the
power supply output will be determined by the loop and sent that way.
Attachments:
basic DC loop 6221 Keithley.vi ‏145 KB

Also, one of the string constants is NOT set to '\' Codes Display. Here is an alternative method of calculating the index. I removed the DAQ and VISA stuff since I could not run it.
Lynn
Attachments:
basic DC loop 6221 Keithley.2.vi ‏16 KB

How to convert labview data into opc tag

Hi all,
Can any one please tell me how i can convert the labview data global into a OPC tag? I have some data globals reading and writing data to the globals. Now i wanted to use a PLC device to send its outputs to the field.
The PLC device will supports the OPC tags so i wanted t create OPC recognised tags in my labview. Is it possible. I saw that labview also having OPC functinalities. Please any one guide me in doing this.
I will be very thankful to them
Ramme..

As I said, I believe you can do this for globals as well by opening its front panel (double click the global) and using a DS connection for the control that represents that specific global.
As for other alternatives:
NI sells the DSC module which comes with an OPC server and with better tags.
You can use a common protocol like Modbus to interact with the PLC.
You can use the custom protocol used by the PLC.
The last two would require that you would change your program structure, so you would only want to use them under certain conditions.
I believe the practical limit for OPC tags with DS is a few hundred tags, but I never used it myself so I didn't run into it. You can try searching the forums to find out more.
Try to take over the world!

Communicating between LabVIEW and Basic Stamp 2.0

Hello,
We are trying to control the movement of a Parallax Boe-Bot (robot with
Board of Education) via LabView programming. The BOE operates on
Basic Stamp programming to control the pulse width sent to two servo
motors.
Is there a way to establish communication between LabVIEW and Basic
Stamp 2.0? We need to send commands from LabVIEW to the
Basic Stamp to control the pulse width and therefore the rotation of
the two servo motors. We also need to send a signal from an
accelerometer based on the robot to the LabVIEW ADC.
The ultimate goal is to do this with wireless communication, but for
right now we are simply trying to figure out any way to send the data
between LabVIEW and the Basic Stamp.
Any ideas?
Thank you,
Adam

Hi Adam,
You can communicate with a BASIC Stamp microcontroller over GPIB using VISA. To see some LabVIEW example code, just search for GPIB in the NI Example Finder (Help>>Find Examples). This will show you the basics of GPIB communication in LabVIEW. I also found this link by searching the NI discussion forums for "basic stamp"
http://www.parallax.com/html_pages/downloads/software/software_basic_stamp.asp
Here you can download an example using LabVIEW 7.0 or higher to communicate with a BASIC Stamp 2.
I hope this is helpful! Let us know if you have further questions.
Megan B.
National Instruments

Large applications - Labview and other programming languages

Hello Labview Users,
as the forum saw this very interesting thread about large applications programmed in Labview
(see: http://sine.ni.com/niforum/niforum?requireLogin=False&forumDU=http://forums.ni.com/ni/board/message?... ) I would like to ask the community about their experiences with Labview applications in combination with other programming languages.
In advance: I have several years of experience in programming Labview applications starting from quick-and-dirty solutions which had to run within few hours and complex test solutions. I saw Labview growing and becoming better with the released versions and lot of things I missed in former times got implemented in the meantime. Actually I have to develop a complexe ATE solution with numerous equipment to control and numerous data to be captured and archived. Despite the Verison 8 I still feel still some drawbacks of the LV concept which let me hestitate to setup the solution completly in Labview:
1) It is alway hard to re-use code of complex applications since it is not possible to do some kind of global search an replace of functions
variables etc. It nearly impossible to re-use approved code structures (e.g a state machine) if the "inner part" is changing more the a little bit.
2) If the application requires a certain flexibility (e.g. exchangeable test equipment of varying vendors) this is hard to implement since you have to define a lot of parameters through your hierarchy if you dont want use global variables which slow down your application and hide
the code functionality.
3) Despite modern PCs the look and feel of LV applications appears somewhat slow compared to other applications. For complex user interfaces the polling methode generates a lot of complex code. (I dont have expierence with the event-structure).
Now my questions:
Do you have experience of implemention of complex solutions dividingthe code modules using Labview and other languages? Which other
languages did you use? Why did you use these languages (speed, flexibility of text based code, available library functions)? Did you found out this to improve your development time and code maintainibility?
(I concider a solution where I do the single tests with Labview-VIs but delegate all the test sequencing and data collection stuff written in PERL which allows really very compact code)
I'm curious what your experiences are.
rainercats

Given that you're asking these questions in a forum for LabVIEW users the opinions given are going to be somewhat slanted towards the general like of LabVIEW. I've been working with LabVIEW for a long time, ever since 2.something on a Mac. I've written numerous large-scale applications as well as "mundane" instrument drivers. As you've noted you're experienced with LabVIEW, so you know some of its strengths and weaknesses.
To address your specific questions:
(1) Yes, that has always been a limitation in LabVIEW, but I don't believe it is an overriding one to choose C over LabVIEW. Putnam provided one workaround for the search and replace of VIs. Once you've programmed in LabVIEW long enough you get used to doing it this way. Is it clumsy? Yes. As for the re-use of code structures, that's not entirely true. You can create a "template" VI (a regular VI, not a .vit) that contains the code you want to re-use and place in your palette with the "Merge VI" option set. That way you can select it from your functions palette, plop it down on your diagram, and you get the "template" VI's diagram placed right into your new VI.
(2) This is not something that is specific to LabVIEW, as this exists with any programming language. It's not the language that limits you here, it's how you've designed your code. In a language like C++ you would go with classes. You can do the same thing in LabVIEW. IVI is another option (though not preferred by me).
(3) As Putnam mentioned, you should be using the event structure.
Other thoughts:
The biggest strength I see with LabVIEW is that each VI is a miniature program, which allows development and debugging of functions a snap. With a language like C you have to write another program to call that function in order to debug it. The biggest weakness? I would say user interface. Yes, even with the event structure. Don't get me wrong, the event structure has vastly improved the way user interfaces and event handling in general are done with LabVIEW, but it simply doesn't hold muster to a program written in C or VB. ActiveX anyone? LabVIEW still doesn't do ActiveX properly in terms of actually getting the controls to work. Programming ActiveX controls is just plain aggravating what with all the property nodes taking up so much diagram space.
It certainly makes sense to use the best tools available to you to get the job done. In my recent projects I had to write software to run automated tests on some products my company made. The test modules were written in LabVIEW. The tests executive was a proprietary engine driven by a SQL Server database. I had to write a "wrapper" DLL that interfaced between the LabVIEW code and the executive since the executive hadn't been designed to call LabVIEW DLLs directly. This allowed us to use LabVIEW as the preferred language for developing the test modules and let the guys who were fiddling with the test executive do their bit. Of course, TestStand's premise is basically that.

Reference Library for Converting Between LabVIEW and XML Data (GXML)

Please provide feedback, comments and questions on the Reference Library for Converting Between LabVIEW and XML Data (GXML) in this thread.
The latest version of the NI GXML Library is availble in VIPM on the NI LabVIEW Tools Network repository.

Francesco, Thank you for the feedback. With this component it was my intention to make a more "terse" version of the LabVIEW Flatten to XML VI that was also supported on RT and that gave the user more flexbility regarding the structure of the parsing type definition. I think you are right that the XML parser is not compliant to section 2.11 of the XML spec. The parser does specifically looking for a #D#A and this appears to be an oversight on my part. Please confirm for me, the specifcation is saying that the XML parser should be able to recognize three possibilities as an "end of line" character: #D#A, #D, or #A. Am I reading this right?There are more efficient (and in some cases much more efficient) ways of sharing data between LabVIEW and LabVIEW: some examples are flattened binary strings and the datalog binary format. XML is slower than these optons but the upside is that it is human readable. Furthermore XML is inherently hierarchical which is convenient for complex data structures like clusters of arrays of clusters, etc. If you don't care about human readability then you are correct XML doesn't make as much sense.I will return to the GXML source code and try to fix this in the near future but I would hope that instead of creating yet another custom VI from scratch that you could reuse what I have provided for you. I included enough documentation in the source code so that users could make some modificiations themselves. The target application for this reference library was LabVIEW to LabVIEW communication. As such I documented the schema on the dev zone document from a LabVIEW perspective. It includes all the supported datatypes and all the supported data structures (cluters, arrays, multidimensional arrays, clusters of multidimensional arrays, etc.) I do see some value in making a more conventional XML spec but the time investment required didn't really line up with my intended use case. Were there any other downsides to GXML that I have missed? Best Regards, Jeff TippsSystems Engineer - Sound and VibrationMessage Edited by Jeff T. on 04-21-2010 10:09 AM

Labview and multicore technology

Greetings
the scenario that i'm having now is as following:
- I'm a 1st year PhD student,and am trying to figure out(find) a new,innovative and impressive project in wireless communications systems area. while am doing my literature review and exploring my favorit knowledge base www.ni.com website ,by chance, i read some titles about the new Multicore tech.then, after surfing most ni's webcasts i got many ideas on how to exploit this tech. together with LabVIEW to boost up my yet-undefined PhD wireless com.main project.in other words,i want to speed-up any existing wireless technology (e.g beamforming algorithms of smart antennas).However, while i met my supervisor i did for him a quick demo and he was wondering about which wireless topic we can make use of multicore tech together with labview,i suggested him {improving wireless systems using multicore tech. and labview coding}.But, a class A student told us that that multithreading problems of multicore tech. have already been solved by software giants, and nothing special about using labview to design parallel processing as many other text-based langauges can do the same,as their compilers already designed for multicore systems.I get depressed actually after he told me this.becuase am intending to use labview (my most favorit software with multicore tech to simulate the performance of a wireless system,and publish a paper about this topic.
in short gentle men, i wish u guide me and tell me anything related to multicore tech with labview.any new problem you want to simulate it using labview so that i can work on it using labview.and please try to refer me to the latest updates about multicore and latest webcast as i saw almost all webcasts now available on ni website. and suggestion, any feed back, any new PhD research idea.all welcomed and appreciated.
thanks a lot
please help to find something related to wireless, anything new for research.....please
Labview Lover

Labview Lover wrote:
labview (my most favorit software with multicore tech to simulate the performance of a wireless system,and publish a paper about this topic.
Why not do a project using Labview to create different models of wireless technologies, and create simulations toevaluate their potential performance. The benefit of multi-core programming would be to optimize the speed to which you canrun simulations of the models. For instance, you can include spectral analysis using LabVIEW.
An idea would be to do the above for RAKE receivers or Software Defined Radios. There are many things you can research and investigate using LabVIEW. You can create the hardware and compare physical to the model. There are lots of project ideas in this area.
R

Plot different data set depending of some conditions using labview and veristand

Hi Community,
i have a couple of points saved as XY data points on my desktop. The files are save as csv. the idea is to read the file utilizing the Read From Spreadsheet File vi when some conditions are met and then plot the XY data wiht XY Graph Addon of the veristand workspace.
for instance:
if case 1 is true read the corresponding file and then plot the first set of data
if case 2 is true read the corresponding file and then plot the second set of data
if case n is true read the corresponding file and then plot the n set of data.
Could you give some advices how to implement it (Labview and Veristand)?
I'm using LV and NIVS 2012
Thx
Mich
Attachments:
vide.vi ‏35 KB

Hi Michel,
I believe the easiest method will be to use the VeriStand .NET API to call into VeriStand and utilize LabVIEW for creating the decision making cases that you have. I have attached some examples of using the VeriStand API in LabVIEW.
Using the NI VeriStand .NET API in LabVIEW to Control a VeriStand System
https://decibel.ni.com/content/docs/DOC-32268
Where Can I Find LabVIEW Examples Using the NI VeriStand API?
http://digital.ni.com/public.nsf/allkb/E1066949FA67B6CE862578A7005988D5?OpenDocument
Please let me know if this helps.
Matt S.
Industrial Communications Product Support Engineer
National Instruments

Using LabView and Modbus to Communicate with AKD Servo Drive

I’m working on a project to control a Kollmorgen AKD servo application using Modbus directly from LabVIEW. I’m new to both LabVIEW and servo drives so forgive me if this seems simple. I have established communications to the drive through Modbus and have been successful at some rudimentary control of the servo. I know the drive only supports "Write Multiple Registers” and “Read Holding Registers” functions and there are scaling factors that need to be applied. What I need is some help with taking the Modbus information supplied by Kollmorgen for each command and formatting it for communication to the servo and vice versa. I need to understand how to take the supplied 8, 16, 32, and 64 bit information for commands, scale it, and format it into the two or four registers required for the drive to read the parameters. In turn, I also need to understand how to take the same information and read it and scale it from the drive. I’ve attached a spreadsheet with the particular commands I’m interested in and a sample VI that seems to work for speed control but to be honest, I'm not sure how/why.
Attachments:
KM Modbus Cross Reference.xlsx ‏57 KB
VEL.CMDU.vi ‏10 KB

OK, I've got the ability to read values from the AKD drive pretty well sorted out. I'm now having trouble with the ability to write. I want to use Labview to program Motion Tasks in the AKD drive. To do this I need to perform three commands: MT.NUM (specify the motion number), MT.P (specify the angular position), and MT.SET to set the parameters for the task. MT.P requires sending a 64 bit signed float or a 32 bit signed float (requiring four or two registers respectively). I used ModPoll to see what values the drive held in the MT.P registers after entering the desired angular position using the AKD Workbench software. For example: using Workbench I entered 234.567 for the angular position and read 208 and -32506 from registers 2060 & 2061 (the 32 bit registers for MT.P). After scouring the forum I put together the attached VI to try to write to the same registers but I can not seem to get the translation of the input (angular position) to the register values correct (entering 234.567 does not produce 208 and -32506 in registers 2060 & 2061). Anyone have any ideas?
Attachments:
Motion Task Definition Rev H.vi ‏21 KB

Labview and Mitsubishi OPC: communication

Similar Messages

Maybe you are looking for