Interfacing Siemens Desigo PXC Building Automation controller with LabVIEW

Hello everyone,
I am currently trying to interface Siemens building Automation controller Desigo PXC100-E.D http://www.buildingtechnologies.siemens.com/bt/global/en/buildingautomation-hvac/building-automation...
with LabVIEW using OPC servers. I had once interfaced the S7-300 PLC of Siemens with simatic step-7 software with LabVIEW but in this case I don't which driver should I select and don't know is it possible or not. If any one of you have similar sort of expierence please I need advice..
Thanks
Naqqash.
Naqqash

Hi,
As you have described I've done the whole configuration. I am using MatrikonOPC for BACnet and as I've checked my device and the software are working properly. Now what I am trying to is that I am connecting the BACnet OPC server with LabVIEW so that the MatrikonOPC act as a connection layer between my device and LabVIEW. So that I will be able to change values directly from my LV vi. Now when I connect that Bacnet OPC with LabVIEW using the same procedure for PLC it gets connected because it is showing all the tags from the device. But after doing the whole procedure which is the same according to the tutorial 'connecting LV to any PLC using OPC' when I deploy the variables I am getting some error. I am attaching the screenshot of the error. Please let me know if I am doing any thing wrong.
PS: I am using a virtual machine and I've tried the whole thing with the NI OPC servers as well according to the tutorial but still when i deploy variables I am getting this error.
Naqqash
Attachments:
OPC_error.JPG ‏22 KB

Similar Messages

Is it possible to build a project with Labview 2010 on a Windows XP system, that is useful for a system with windows 7 on it?

Hi there,
I am planning to use Labview 2010 in a short time.
But before I'm going to use it I have some questions.
I know it is possible to run Labview 2010 in an XP environment. But is it also possible to, when running Labview 2010 on a XP system, to build a project to a version that is useful in a Windows 7 environment?
Or do I have to run Labview 2010, when I want to build a project that is useful on a Windows 7 system, on a system with Windows 7?
Please give me some information.
I hope to hear from one of you soon.
Regards,
Kenny
Solved!
Go to Solution.

Is it possible to build a project with Labview 2009 on a Windows XP system, that is useful for a system with windows 7 on it?
Thanks.
Philippe B.
Certified Associate Developer / Dépt Moyens d'essais
www.ingenia-system.com

IS APPLICATION BUILDER 6 COMBATIBILE WITH LABVIEW 7 ?

IS APPLICATION BUILDER 6 COMBATIBILE WITH LABVIEW 7 ?

No it's not but it is a free upgrade last time I checked. Go here and click on the Upgrade Advisor link. You will need the serial number of your current app builder.
p.s. LabVIEW 7.1 was released today so you might want to skip 7 and go straight to the latest.

Building a dll with labview for CVI

Hi,
I am making some abstract hardware layers for some instruments and i use to work with Labwindows CVI. But i have found ONE instrument, the Instek pst3201 alimentation which is ONLY created with Labview.
So i downloaded the 8.6 LV demo and builded the llb projet in order to obtain some .dll, .h and .lib files and included it to a CVI project in order to construct an intermediate Dll level.
Everything builds fine, like usually when i use an IVI driver but my problem is that when i try to call this intermediate Dll level with my abstact hardware layer using LoadLibrary, nothing is returned like if the DLL doesn't exist.
So my question is : Do you think that this is a problem from CVI (and i repeat that i have made a lot of others abstract hardware layers using IVi drivers except that this time i haven't got any .fp or .c but a .h and i include the .lib to the project), or a problem from Labview and i should use the LV Application builder if it's different ?

Hi,
It's seems that you have no exported function. What function do you have in your header file? did you tryed to create a really simple dll (doing an addition for example ) in LabVIEW only to verify that you are correctly creating the dll?
Manuel R
AE dans une autre vie

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

How to build demo versions with Labview ?

Hello,
is it possible to design Labview applications in a kind,
that it is possible to generate "demo versions" of it ? Demo version in the means of feature-limited crippled versions of a full instrumentation software, where SOME hardware access is denied, but you can load and view and analyse data.
Of course it might be useful to compile this demo version with the Labview Application Builder,
What might be the business modell for demo versions:
A hardware manufacturer creates a Labview application which controls the manufacturer's components, and allows instrumentation and data recording. The application is not free but sold for extra money.
As pre-sales benifit, the manufacturer would like to send the (compiled) Labview application to future customers.
Now the problem is, that the customer has not (all) the external devices or PCI/USB devices,
on the other hand the hardware manufacturer does not want to give the "full application" as gilft to the customers.
Now with traditional software development with C++, Java, C#,
either a demo version is gained from the full version by replacing some module with hardware access by modules wth "empty" function body or with function body which return constant values instead of accessing the hardware.
In the world of process industry, usual process control systems may supply "alternative" values if the original device is not available.
What kind of software structure must I build with Labview, to do the same ?
Now the problem with Labview applications is
Labview applications depend on drivers. Drivers depend on hardware.
So if the FULL commercial version of the Labview program accesses a DAQmx driver, GPIB driver or any other hardware driver by a VI,
and often this means that a special manufacturer VI is used in the Labview program which does the actual hardware access,
how to modify the software to make a demo version
a) so that IF the customer buys the hardware and gets the hardware driver, he still does not have the full version
b) so if the customer neither has the hardware nor the driver, he still can run the Labview software and load an view data, push buttons, can execute menu items even can manipulate data ect, can use the manufacturer's VI
Unfortunately, it is no solution just to delete "some" of the VIs with hardware access from the distribution of the demo version, as this just causes error messages during the loading of the (compiled) Labview demo application.
Message Edited by hemmerling on 01-11-2007 12:35 AM
Message Edited by hemmerling on 01-11-2007 12:37 AM

Thanks alot.
Conditional Disable and Diagram Disable Structures
http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/cond_diagram_disable/
are indeed at least a part of what I wanted.
Anyhow, as such "suspended" VIs are often the *source* of signals,
so there must be an addtional method how to provide "alternative" signals for the demo version,
which does not make the administration / further development the full version too complicated...
For example: The VI for an external signal generator device is disabled, but alternatively it would be nice if the users of the demo version can get a fixed sinus signal instead...
How to do that with Labview and the "Conditional Disable and Diagram Disable Struktures",
and can I test this all even without Labview Application Builder, in the full development system ( so that I don´t need the compiler for frequent checking ) ?
Btw, with what version was this "Conditional Disable and Diagramm Disable" feature introduced ? Is ist already available with Labview 7.0, /.1 ?
Sincerely
Rolf

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!

Watlow F4 Controller with LabView

Hello all,
I have a HX300 circulating chiller that uses a Watlow F4 controller. I want to control the F4 controller and monitor the conditions from it such as pressure rate and temperature using LabView. I heard of the Modbus driver that helps make this communication possible and have downloaded it. I am using the LabView 8.6 version and followed the necessary steps to include it into Labview. I have very little experience with Labview and am wondering how to begin writing the code for this. Any help is very much appreciated!
Thank you,
Eric
Solved!
Go to Solution.
Attachments:
labview 86.zip ‏1900 KB

Start here:
http://www.ni.com/gettingstarted/labviewbasics/
and here:
http://www.ni.com/academic/students/learn/
and here:
http://labviewwiki.org/LabVIEW_tutorial#External_Links
And if you have an active SSP here:
http://sine.ni.com/myni/self-paced-training/app/main.xhtml
After all of that open the Examples in the code you posted and see if they work.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Can i build an application with Labview 2009 for Windows 7?

Hello
i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
Solved!
Go to Solution.

Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application. After installation I had to move the files from 1 location to the other to make it work.

Build Specifications gone with LabVIEW 2009

I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
Is this a known issue and is there a fix for it?

Hello,
this might be a corrupt project file. Does this only happen with this project?
If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
Regards,
Joseph Tagg

Build application with LabView 8.2 Prof

Hello,
in the past (V 6.1) it was possible to build LabView application with a complete setup routine, not only *.exe. In Version 8.2 I dont find these option. Anybody knows where to find it?
Best regards
Robert

I think that what you want it's to create an installer. See the steps on the attach picture.
Software developer
www.mcm-electronics.com
PS: Don't forget to rate a good anwser ; )
Currently using Labview 2011
PORTUGAL
Attachments:
teste.png ‏333 KB

Problem when building an executable with labview 6.1

I use LabView 6.1 and I want to build up an executable. I use the labview application builder to do this. I have already built up executables and I had no problems but this time I just obtain a labview vi library which is called "internal.llb" each time I try to compile my vi's. Do you have an idea to solve my problem please ?

Make sure that you have "Single target file containing all VIs" selected
under Build Option in the Target Tab of the App builder. Sounds like you
have "Small target file with external file for subVIs" selected with the
target being a llb.
-Tom
"gege" wrote in message
news:[email protected]..
> I use LabView 6.1 and I want to build up an executable. I use the
> labview application builder to do this. I have already built up
> executables and I had no problems but this time I just obtain a
> labview vi library which is called "internal.llb" each time I try to
> compile my vi's. Do you have an idea to solve my problem please ?

Can I use an AutomationDirect T1H-EBC ethernet base controller with Labview?

Do I need to purchase an opc server?

Yes, You will need to purchase some type of communication "translator". If you purchase an OPC server, then you can use the datasocket VI's in LabVIEW to communicate to the device via OPC.

Error when building Installer with USI 1.5.0 with Labview 8.5

I used to build an installer with Labview 8.2 and included this additional installer USI 1.5.0 but now with labview 8.5 it gives me an error:
"Locate the "NI LabVIEW" distribution. LabVIEW needs to copy a component installed or updated by the distribuiton to conitnue building the installer"
Any advice

Hi reza_sed,
Thank you for contacting National Instruments. When you get this message, are you prompted for a location of this installer (CD drive or something)? Sometimes if components are installed together, certain dependencies are created. You might be able to add the installer to a LabVIEW 8.2 installer with no problem, but the installer cannot be found when using a different version of LabVIEW. You might try uninstalling USI, then copying the install files from the CD or from our website to your hard drive and then installing from there. Then, you should be able to include the additional installer.
Another thing that may be happening is that the LabVIEW Run-Time Engine you have for 8.5 does not support NI-USI. The full version of the Run-Time Engine supports NI-USI, but the web browser only version does not. Make sure you select the full version when installing.
Donovan

ABAP & OLE Automation Controller

Hi everybody,
When I use ABAP & OLE Automation Controller to build a Excel file, I don't find a documentation about the values of the properties parameters.
For example:
(DATA gs_cell TYPE ole2_object.)
SET PROPERTY OF gs_cell 'HorizontalAlignment' = -4108 .
I found in Visual Basic Editor all properties of the OLE objects. But the number -4108 remains a mystery for me.
Where can we find this value ?
I tried to read the official Microsoft and ABAP documentation without success.
Can you help me ?
I thank you in advance.
Patrocle

Hi,
I use http://msdn.microsoft.com/en-us/library/ms262200.aspx site
In the documentation for Range.HorizontalAlignment You can find it uses XlHAlign:
http://msdn.microsoft.com/en-us/library/bb241313(v=office.12).aspx
Name                    Value     Description
xlHAlignCenter               -4108     Center.
xlHAlignCenterAcrossSelection         7     Center across selection.
xlHAlignDistributed          -4117     Distribute.
xlHAlignFill                   5     Fill.
xlHAlignGeneral                   1     Align according to data type.
xlHAlignJustify               -4130     Justify.
xlHAlignLeft               -4131     Left.
xlHAlignRight               -4152     Right.
Regards,
Przemysław

Interfacin​g Siemens Desigo PXC Building Automation controller with LabVIEW

Similar Messages

Maybe you are looking for

Interfacing Siemens Desigo PXC Building Automation controller with LabVIEW