WAGO Linux Controller and LabVIEW

Hello,
in WAGO catalogue I've seen two interesting products: The "WAGO-I/O-IPC" (758-870) and "Linux Ethernet Controller" (750-860). Both are working with Linux.
I have'nt experience in Linux, IPC and LabVIEW RT, i'm only good in LabVIEW. But I want to know
- if these two devices are programmable via LabVIEW RT,
- where I can get information, what kind of target systems available for LabVIEW RT
Thank you
C. Dietz
Test Engineering
digades GmbH
www.digades.com

Hello,
LabVIEW RealTime applications can currently run on PXI-Systems, desktop PCs, compact Fieldpoint, compact RIO and compact Vision systems. Please refer to this link for a complete overview.
These hardware targets run Pharlap or VxWorks as operating system. LabVIEW supports Linux on Intel/AMD desktops but I'm pretty sure that those applications won't run on the WAGO-I/O-IPC or the Linux Ethernet Controller.
Please let me know if you need further details.
Best regards,
Jochen Klier
National Instruments Germany

Similar Messages

Linear actuator, motor controller and labview. Establishing connection.

Overiew:
I have a 12VDC linear actuator (potentiometer built in) connected to power and Jrk 21v3 USB Motor Controller with Feedback (http://www.pololu.com/catalog/product/1392). The USB motor controller connects to the computer through USB, actuator's feedback wires connect to the motor controller.
Problem:
Establishing connection between the motor controller and labview.
What I have done so far:
I installed drivers to the motor controller and windows detects it. NI MAX detects my motor controller (pic attached), but for some reason, when i try to access it through daq assistant in labview it doesnt see it. I also tried accessing it through VISA with no results..
Help will be appreciated.
Thanks
Peter
Solved!
Go to Solution.
Attachments:
problem.jpg ‏124 KB

You have a few things you need to look into:
When you installed the software, did it install a USB > Virtual Com Port dll such as FTDIchip or similar? If so, when you hook up your device, it'll reveal itself as a normal (new) Com Port in Device Manager. You then need to try to talk to that com port.
If you are trying to use the native USB on the board (as MAX has detected for you), then you'll need to use the .NET framework code provided by the manufacturer (probably written in C#), and make your own Constructors in LabVIEW. If you've never done this, it isn't trivial.
I would call the manufacturer and just tell them what you are trying to do. They've probably dealt with LabVIEW before, and may have an example to get you started.
edit: For fun, I followed the link you provided (which doesn't really work). I searched their site for "LabVIEW", and indeed got several hits. This one thing I downloaded (can't resist looking at code) was a gigantic turd ball. However, it did appear to use a normal Com port.
Richard

How to configure the GPIB controller in LABVIEW or MAX to send UNLISTEN and UNTALK when each message ends?

In a PC to PC GPIB configuration, one PC is used as a non-controller and it reads either LACS or TACS status bits continuously. It apears that the controller PC does not send UNTALK and UNLISTEN at the end of each message. The non-controller reads and writes therefor times-out.
What is the correct message synchronisation for a non-controller?
I use Labview 6, PCIIA, WIN98SE.
Thanks.

Are you using LabVIEW as the controller, non-controller, or both?
NI-488.2 does have a configuration option to enable unaddressing. I am not sure of where it is in LabVIEW, but if you search for unaddressing, you should find some information on it. With unaddressing, NI-488. will unaddress the device after communicating with it.
If you are not using LabVIEW as the non-controller, National Instruments does have a software package called NI-Device that may help. This is an API designed for non-controllers. It does not currently have a LabVIEW interface. It works under C++ with a PCI-GPIB board.
A third option is to rewrite your device application. Your device should really not care about TACS or LACS as you read them from the status register Your device
should only look for LACS, DCAS, and perhaps DTAS (if you desire triggering). When it is LACS, it should read data. After a read has completed, it should interpret the data and get ready for a response. It is only at that moment that the device should look for TACS (and DCAS). It is hard to put a flowchart here, but if you design the flow of a standard instrument, you will see some patterns about when to look for certain status bits.

Is it possible to micro step using the Pci7314 (open loop) controller and umi7764 and Labview.

Is it possible to micro step using the Pci7314 (open loop) controller, umi7764 and Labview. if so how would this be set up. i have searched the valuemotion vi libraries and found no microstepping functions. Please could you offer any advice. cheers JON ROGERS

Hi Jon,
Micro-stepping is a property of the motor amplifier (motor drive) rather than the controller. It sounds like you are using a 3rd party drive, since you have a UMI. You want to check with your motor amplifier documentation to see if it's supported. Usually, there will be dip-switches on the drive that sets the microstep factor.
Hope this helps. Please let me know if you have any questions.
Thanks,
Ken Sun
Applications Engineering
National Instruments

Running 2 stepper motors with LabVIEW using RMV ST400-NT controller and driver

Hello, I am new to programming as well as motors in general so please bare with me in my attempt to explain myself. I have a project involving laser therapy and I am attempting to control two stepper motors from Falhauber, Type AM2224-R3-AV-4.8. I will be using a RMV ST400-NT controller and driver. Original plan was to use 3 stepper motors for control in 3 axis but realized 2 axis is complicated enough. My power source is an Agilent E3630A. I am new to this whole thing and from what I have read form examples and other posts is that NI drivers seem to work best for these applications. I've written simple programs from examples, reading and watching videos. I want to know whether it's possible for these to work together using LabVIEW and also a nudge to help me get started would be much appreciated. Can someone please help guide me in the right direction, I feel a bit lost when it comes to all this. Thank you for your time and consideration. Also, I will be using Windows 8 laptop with Labview 8.5. I have attached pics of components I will be using.
Justo T.
Attachments:
photo 1.JPG ‏1150 KB
photo 2.JPG ‏987 KB
photo 3.JPG ‏1085 KB

Hi jtarula,
I want to preface this response by saying that I am mre familiar with NI controller and driver rather than the one that you have. I am assuming that you are using the dll provided by the manufacturer here:
http://www.rmv.com/download.htm
With these, you should be able to interface with LabVIEW using the call library function node. What the controller is capable I am uncertain of. I am certain that you should be able to since another user has commented on the use in LabVIEW before in another forum post.
I also want to let you know that LabVIEW 8.5 is not supported on Windows 8, which means that you may run into some compatibility issues. Here is the compatibility chart.
Paolo F.
National Instruments
Applications Engineer

Mks mass flow controllers only giving 2 sig. figs. over deviceNet and labview

We can only read 2 digits (before the decimal point) on an MKS deviceNet mass flow controller using Labview 2013. Does anyone know a solution to increase the resolution on this device? We should be able to read 3 digits past the decimal point.

Hi David,
Could you also specify the type of mass flow controller device?
According to our engineer, we had the APIs to set the attributes of DeviceNet device, but the specific type of the device is required. Attached is the document of some device type. You could turn to page 75 to see there the S-Analog Sensor Object Attributes::FlowDataType could be Get/Set.
Attachments:
1485A-1480A-185A-180Aman.pdf ‏964 KB

Use NI LabView and LabView RT with third party PXI chassis

I want to use NI LabView and LabView RT, some PXI chassis of N.I and
some PXI chassis of Third Party( not N.I ) for diversity, How I will Install
Pharlap ETS ( LabView RT ) on those third party PXI's.
More simply
Third party PXI chassis and controllers support LabView RT or not?
Note: Mark Andre Hary [email protected] of Sensing Systems LLC answer to this question as:
"You can't. I think NI bought Pharlap, and they do not offer board support packages (BSPs) for non-NI PXI controllers. There is no way to get LabVIEW-RT running on a controller not purchased from NI. You will have to use a standard RTOS like Linux,VxWorks, or QNX.
Regards

As described in the web links below, the only way to run LabVIEW Real-Time for ETS on a third-party system would be to follow the procedure for desktop PC computers. You may find that your third party PXI controller may meet the requirements listed in the below link and you will be able to run Real-Time on the controller. If you decide to do this, you will need to purchase the LabVIEW Real-Time Desktop Deployment license (also linked below). After purchasing the deployment license, you will be sent boot disks that will install the real-time OS onto your system. There is no need to purchase Pharlap ETS from Ardence directly.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/cb3434da94466dd286256e9e006bb775?OpenDocument
http://sine.ni.com/nips/cds/view/p/lang/en/nid/13751
Instead of using LabVIEW Real-Time for ETS, you could use LabVIEW Real-Time for RTX instead. This system allows you to run Windows and the Ardence Real-Time eXtensions (RTX) real-time kernel concurrently on one machine. Currently device support for LabVIEW RT for RTX systems is limited to RIO devices. This is all described in the below link.
http://zone.ni.com/devzone/conceptd.nsf/webmain/9cc60298315a687e86256e78007b3a96
I hope this answers your question.
Regards,
Kristi H - National Instruments

How to implement a dual booting PXI system using windows 7 and labview RT

Good Day
My name is Mariano Ocana from the University of Manitoba, and I want to implement a dual system using windows 7 and labview RT in a PXIe-1082 chassis with a PXIe-8102 embedded controlled (the chassis came with windows 7 installed). What are the steps to use both systems (windows and RT) in the same chassis?, in the NI help comes an example implementing a dual system using windows xp and RT, it is the same procedure?.
Thank you in advance for all your help.
Regards
M. Ocana

Greetings, Mariano.
The real issue you have to contend with is whether or not you have a LabVIEW RT license. If the 8102 controller was purchased Windows-Only, you likely do not have a license to run LabVIEW RT on the controller - you can purchase one, I think it's about $500, and at that point you can request a LabVIEW RT Configuration CD (that's not what it's called, but the sales guy will know what I'm talking about). The Config CD is a CD that will partition your controller correctly with both FAT32 and NTFS filesystems (in the appropriate way) to allow you to run Windows 7 and LabVIEW Real-Time on the controller correctly. Once done, you can then switch within the BIOS between LabVIEW Real-Time and Windows in order to dual-boot.
Either way, you likely need to contact NI sales to either purchase an RT license (if one was not received at the time of purchase) or to request a Configuration CD (it might also be called a dual-boot install CD or similar).
-Danny

How to perform datalogging in a file using RT controller and a host PC?

I'm Using PXI-8145RT Controller and a Host PC(Dell Laptop),I used the TCP/IP DAQ Vi's but Im getting problems in logging data into a file at the Host using the Vi's .For 3 Channels the program works fine but as I increase the Number of Channels the program stops running on the RT Controller! Do we have to configure some TCP/IP settings for this or i have to use some other methods for datalogging into a file on the host using an RT Controller on the ethernet.

If you increase the number of channels and the RT program stops running, it could be that your scan rate is too fast for the increased number of channels on the 8145. First try to lower your scan rate by a large amount (a factor of 10, for example) to see if this is the problem. If you still see the same behavior when going above 3 channels of input, I would suggest looking at the following links for more information on communication with RT.
General Communication Info:
NI Developer Zone: Communicating with a Real-Time Engine
Specific Documents:
NI Developer Zone: Real-Time FIFO for Deterministic Data Transfer Between VIs
NI Developer Zone: TCP/IP between the Host PC and Real-Time Series Hardware
Furthermore, if you are using LabVIEW RT 7.0, I would highly suggest the use of the RT Communication Wizard. It will create the communication portion of your RT application for you.

How to implement a StateSpace-Controller in Labview

I have to implement a StateSpace-Controller in Labview. What is the
best way of doing it?
I have tried two versions -- a continous SS-Controller and a discrete
Version. The Problem is, they show different results, and I can't find
the mistake.
If you have a solution at hand, I would appreciate if you could send
me the file!
Thank you very much!

I started a post to your other thread:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HFORCEKWTID=65816:5&HOID=506500000008000000B4900000&HExpertOnly=&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0

How to use a ps3 controller with labview

Hello, I am trying to implement a ps3 controller in labview but am having trouble. I was wondering if anyone knew how to do this or had any ideas for me. Thanks for the help

Hi Keaton
I'm not too sure how the inputs of the controllers work on a lower level, but Sixaxis offers a driver to integrate the ps3 controller onto a pc. It is available at this website:
http://dl.qj.net/playstation-3/tools-and-utilities/sixaxis-driver-for-pc.html
This may be an easier starting point that having to go from scratch. You can look into using the call library functions in labview and access some of the functions that may be available in that driver. This seems like a better choice then pulling out wires and using a daq device to read value since you wont actually have to take apart the controller. That being said, for support on that driver, you might have more luck on the sixaxis forums here:
http://forums.qj.net/
Hope this helps
Luke W

Motion control: PXI 7350 controller and UMI 7774 to interface with third-party driver UDK5114NW2

Dear community,
This is about Motion control in Labview: I try to control a step motor by using a PXI 7350 controller and UMI 7774 to interface with third-party driver UDK5114NW2. The problem is 5 Disable LEDS on UMI 7774 board always lit even when I check "enable" on "Motion I/O setting" in configuration of PXI 7350 motion controller. Furthermore, when I start to control step motor, it is not working and I found disable LED on UMI board still lit. I don't know how to solve this problem. Can someone help me to figure out? Thank you in advance!
Hau Nguyen.

Dear Community,
I said wrong, 4 disable LEDS on UMI 7774 Board instead of 5 as my previous post. Why nobody help me to solve this problem. I can not turn off disable LEDs on UMI 7774 Board so I can not start the strp motor. Please help me!
Hau Nguyen.

NI-Fieldpoint support in Windows 7 and LabView 8.6

We have a "classic" FieldPoint system with an ethernet controller. We want to be able to read/write from/to the FieldPoint network using a computer with LabView 8.6 and Window 7. Is NI-FieldPoint supported in LabView 8.6 and Windows 7?
Regards,
nate
Solved!
Go to Solution.

Hi natewkidd,
I feel like there is some confusion between the operating systems running on a development machine (like Windows 7) and the real-time operating systems that run on our real-time controllers (like the FP-2000). I will do my best to clear up this confusion by first answering your questions.
1) What is the difference between LabView Real-Time 2009 and LabView 2009?
LabVIEW Real-Time 2009 is actually a software package officially known as the LabVIEW 2009 Real-Time Module that is installed after the LabVIEW 2009 development software to allow the user to develop and deploy real-time applications to real-time targets such as your FP-2000. You can think of the LabVIEW 2009 Real-Time Module almost as a plug-in for LabVIEW 2009 to allow for real-time application development and deployment.
2) If I have a FP-2000 on the ethernet network and want to use a computer running Windows 7 and LabView 2009 to record and display data, will I still be able to communicate with the FieldPoint network using the FieldPoint Read/Write VIs from my Windows 7 machine?
If you were just going to use the FP-2000 as a network module (NOT deploying a real-time application to run on the FP-2000 itself), you should be able to communicate with it using just the FieldPoint Read/Write VIs from your Windows 7 machine with LabVIEW 2009 and the NI-FieldPoint 6.0.5 driver. In this situation, you actually do not need the Real-Time Module since you are not deploying the application to the real-time target.
Regarding the FP-2000 not being supported beyond LabVIEW 8.5.1, this is because the memory on the controller is not large enough to hold the software that is installed on the controller with LabVIEW 8.6.x Real-Time Module and the LabVIEW 2009 Real-Time Module. For more information on this please check out this KnowledgeBase article.
I hope this is helpful! Let me know if you have any further questions.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

How do I configure my PCI-GPIB cards so that one is a controller and the other is a device being controlled by the first card

I have 2 PC's, both fitted with PCI-GPIB cards. One will be the system controller and the other will be a device on the GPIB bus. How do I configure both cards using LabWindows/CVI v7.0 to achieve this ? What commands are used to send and receive the data ?

Hi Pete,
For the controller board you don't really need to do anything. By default the GPIB interface is configured as controller.
The non-controller can be configured in MAX. Right-click on the interface, uncheck the ono-controller box and change the primary address. It is usually a good idea to set these parameters programatically. Use ibpad to set the primary address and ibrsc to release system control.
For the controller you can use a device descriptor (using ibdev) or a board descriptor (ibfind).
You can only open a reference to the non-controller board using ibfind (ibfind("gpib0"), for example). This will open a board reference. You cannot use a device reference because that implies that the board is capable of addressing the bus. On
ly the system controller can.
Here are some links I found on the web on this subject:
Passing GPIB Control -- System Controller vs. Controller In Charge
Tutorial: Programmatic File Transfers over the GPIB
Example: Using a C Program as a GPIB Non-Controller with LabVIEW as the GPIB Controller
Example: Serial Polling Between Two Computers (Controller and Non-controller)
Hope this helps.
DiegoF
National Instruments.

Land & Sea controller with LabVIEW?

Hello all,
I currently have the Land & Sea dynamometer setup with Dyno-MAX 2010 Pro and am in transition to a setup using LabView but intend on keeping the controller purchased from Land & Sea. However I am encountering the problem of finding a bridge for LabVIEW to communicate with this controller and was unsure if it is even possible. When I contacted Land & Sea all they would tell me is that the information on the controller was proprietary. Another key piece of information is that we are swapping out our analog to digital converter from the Land & Sea Dyno-MITE to NI's X Series. It could be possible that the Dyno-MITE makes conversions to the control signal before it even gets to the software, which could make this even more challenging. Everything else, such as our harness, dynamometer, sensors, etc. will remain the same. So to make things a bit more clear
Old Setup
Software: Dyno-MAX 2010 Pro
Analog to digital converter: Dyno-MITE
Controller: Land & Sea
New Setup
Software: LabVIEW
Analog to digital converter: X Series
Controller: Land & Sea
If anyone has any suggestions on how to proceed, or tips to use in LabVIEW on how to allow the controller to communicate with LabVIEW it would be greatly appreciated. I will post a link leading to pictures of the harness schematic as soon as possible. Let me know what other information you might need to help.
Best regards,
Travis

It is an eddy current controller with AC absorbers.
Here is a link to the Land and Sea website with their description:
http://www.land-and-sea.com/eddy-current-dynamometer/eddy-current-dynamometer.htm
Also here is a picture of the harness schematics:
More specifically:
where the red box is our controller connection, and the yellow box is for our RPM.
Thank you!

WAGO Linux Controller and LabVIEW

Similar Messages

Maybe you are looking for