Pouvez LabVIEW DSC Run on embedded XP

Similar Questions

• Creating a single setup program, including the DSC Run-Time module

  Hello

  I would like to know if it is possible to add the DSC run-time of an installer?

  I'm using LabVIEW and DSC 8.6 and I do not have the license for the DSC run-time.

  In the "Additional installers", I checked the health empty boxes:

  • OR Distributed System Manager
  • NEITHER deployment DSC increased support for LabVIEW 8.6
  • OR LabVIEW Run-Time Engine
  • NEITHER Measurement & Automation Explorer 4.5
  • Engine OR Variable

  When I open MAX after the installation, I do not see the database of the Citadel, and there is no trace of the execution from DSC module.

  How can I have a single installer that will do the work?

  Thanks in advance

  Hello

  Yes, as long as your customer has performance DSC system installed and enabled on their computer, they should be able to use your exe with Setup included. Then you wouldn't need an installer for it because it would be already installed and the computer should have MAX and the database of the Citadel. You will not be able to install the RTS as an extra Installer, unless you activate it on your machine. I hope this helps.

• LabVIEW DSC 2015 with Labview 2015 64-bit

  Hi all

  I would like to know if it is possible to install the labview DSC 2015 with Labview 2015 64-bit module. When I run the Setup program, a message appears telling me to install Labview before installing the DSC Module. Maybe I need to install a 32-bit version of Labview? If anyone has an idea...

  Thanks for all,

  Alex,

  From the Readme of LabVIEW file:

  Supported modules

  LabVIEW 2015 (64 bit) supports only the NI Vision Development Module. Refer to the documentation of the Vision Development Module for more information. No additional modules support LabVIEW 2015 (64-bit).

  Looks like you need to run 32-bit LabVIEW.

  Bob Schor

• There is a possibility to run Labview projects or to set them off from a batch file or if the exist and the ability to control labview or run it from an external application?

  Hi, I m a bit new in LabVIEW and I'd like to ask a few questions...

  -There is a possibility to run Labview projects or to set them off from a batch file or if the exist and the ability to control labview or run it from an external application?

  -One API PI or raspberry beaglebone exists for LabVIEW?

  -Power supply Wich can recommend you control with LabVIEW? (some chip solution witn 0 - 30v / 0 - 3A DC)

  Thank you very much for your advice!

  Best regards

  Elena

  Elena,

  I know raspberry, so no comment on that.

  For the rest:

  -Do you want to create tools for developers? If so, we must look in the API of project VI and VI server. If this isn't the case, please compile your application LV as executable and call this one using a batch file.

  -LV prefer specific supplies. LV is a programming language. There are several power supply providers (including OR) which provide directly the LV API for their power supplies. So, essentially, the approach is:

  1. choose food that serves your needs.

  2. check if the power supply has a standard interface for programming (such as Ethernet, GPIB, or if the power supply is PXI, is already providing a programming interface!)

  3. check if the LV API (so-called "instrument driver") is available for the device. In the case of a PXI system, get you a device driver (for example NI DCPower).

  4. check if the LV samples are available (for example in the Finder for example LV once you have installed the driver).

  Norbert

• LabView - DSC Runtime

  I'm working on an application to control a cable laying barge offshore. I am considering the use of the DSC Module, but I am concerned about two things:

  (1) is the component of the viewer historical data of the measurement and Automation Explorer included with the Runtime of DSC?  In other words, the distribution and using a licensed version of the Runtime DSC, users of my program will have access to this utility to browse and export data from the database of the Citadel?

  (2) the application that I'm getting is vital.  There will be at least a backup computer on the barge with a Runtime installed and licensed from DSC.  However, in an emergency, can the application distribution be loaded on another computer and works in "Évaluation" mode for a while so that the license for the DSC Runtime is set?

  Thanks for your help,

  Joe

  Hey Joe,

  Looks like you got the right answer to your first question!  To answer your second question, unfortunately, the DSC Run-Time does not include an evaluation mode.  It must be allowed during installation for the feature.  If you have the DSC Run-Time on two PCs, you would need to have two licenses.  Please let me know if you have any other questions!

• LabVIEW 2011 Run time engine installation issue

  I try to install Labview 2011 Run time engine as downloaded here: http://joule.ni.com/nidu/cds/view/p/id/2534/lang/en

  on my laptop Windows 7 Pro. I have the hard drive shared in the C and D drive with plenty of space on each.

  Initially the office IT guy tried to do the installation as an administrator and for some reason any installed at "D:\Program NIUninstaller Instruments\" for some reason any. He went through the installation without error, but after restarting, it seems that some of the components are installed. I never installed anything else OR on this computer, but after installation I see NI License Manager and Datasocket under National Instruments in the start menu. If I re - run the installer it seems to think that everything is installed and there is something to remove, but it is obviously not.

  Subsequently the computer gave me administrative privileges on my account so I have been playing with various combinations of uninstall and reinstall myself but with the same result each time.

  Any ideas would be very appreciated.

  Hi Robert,.

  you have installed the RunTimeEngine.

  What else you expect to see in your Start menu after doing? What's missing?

• How to read the tag bluetooth data in labview 2015 running on Windows 10

  Hi all

  I have a Development Board Nordic semiconductor nr51. This card is programmed as a tag bluetooth which simply announces his address with 16 bits of data appended to the end.

  My laptop came with loan materials smart bluetooth. I installed an app interactor lighthouse to bluetooth on my laptop and the software is able to detect the tag as if shown on the image below.

  

  I wanted to write a LabVIEW program that will simply be careful bluetooth headlights and notify me in my computer every time a lighthouse with the specified address is detected. This mobile application below is provided by the manufactuerer of the Board of Directors and I wanted to develop a LabVIEW program something similar to what will read the given data and extract values.

  

  Somehow, all the sample applications provided data only shows how to read and write in a connected bletooth device but not analysis for tags. I also tried using the Bluetooth ' discover ' and it does not detect the bluetooth beacons.

  Could someone provide me with the necessary information or example program for detecting / reading of tags bluetooth in LabVIEW 2015 running on Windows 10?

  Do I need to install a third-party software to read data from bluetooth?

  Bluetooth in LabVIEW function nodes using the Winsock interface to access bluetooth resources. This works very well for Bluetooth 2.0 devices but not Bluetooth 4.0 devices WHEAT aka. Microsoft has created a completely different interface for these resources API as the model of overall service for WHEAT devices has radically changed.

  The API to use WHEAT devices is the API of the GATT (generic attribute profile) in Windows. There is supposedly a .net interface available that you can try to use (Windows.Devices.Bluetooth.GenericAttributeProfile). The WinAPI to lower level (https://msdn.microsoft.com/en-us/library/windows/hardware/hh450825(v=vs.85).aspx) is a C DLL API and does not lend at all to be called directly by the LabVIEW call library node, since some of the parameters of the function are quite complicated and you need to also access the SetupDI APIs to enumerate resources WHEAT and even harder to function parameters. In order to access this low-level API to write an intermediate DLL which results in low level API C a more acceptable API for LabVIEW.

  Another possible problem is that Windows don't at least in Windows 8 not allows devices to pair per program. Microsoft wanted to force developers in the use of the "inbox" experience, which means that all users must go through Microsoft provided service pairing, instead of each request for implementation of his own matching technique.

• HP Thin Client running Windows Embedded don't profile with attributes DHCP

  My company has a large population of HP Thin Clients that are not attached to our AD domain and therefore cannot do dot1x because they have no certificates.

  We decided to do the profiling for these devices. We present a few attributes, two of these DHCP attributes.

  About 90% of our profile of thin clients, as expected, but the other 10% will refuse to work. We need to statically assign them to a group of identity to authenticate properly.

  A lot of troubleshooting reduced us to query DHCP the thin client sent was not received by the strategy node. A TAC engineer looked over the config switch, IP helper address configuration and said that everything seems to be configured correctly.

  The only explanation is that it seems that these specific thin clients were not finishing the DHCP process before reassigned switch the VLAN of the port. So when the dhcp request has been sent, the thin client was already in our vlan "invited" who does not dhcp to the ISE.

  It's very strange, because we have so many thin clients that works properly. It's only a handful that do not. We have not been able to further refine to something specific. They are running Windows Embedded Standard 7 and a majority of them are HP t5740. I don't see Windows or HP updates available for these units and not sure if there are any registry hacks available to expedite the DHCP process.

  Has anyone ever come across something similar to this?

  It's pretty obvious to me, the end point isn't you get profiled before there was authenticted, which means that you do not correspond to the profiling conditions defined in rules 6 and 7, which means it will match the rule 11 (I think, having not seen your real rules). What I expected this, is that endpoint gets profiled, if ISE receives the attributes of this endpoint via dhcp e.g. forwarding help. Then, what should happen is, that it should issue a certificate of authenticity to the switch, which will lead to the passage to be re - authenticate this ending point, which now must have customization attributes you are trying to match. However if the DHCP packet never reaches ise, it won't work. That's why I think you should do a trace of package on the ise server, to see if the packets actually reach ise. If they don't you will probably need to find another way to profile, or activate dhcp for assistance on your guest virtual local network. Have you looked at the attributes of endpoint maybe after 30 seconds? They change?

• I want to write the program in Labview which runs on PIC Microcontroller.

  Is there some toolkit or similar, which will allow me to write code for micro PIC (10F or 12F)?

  In fact, I believe that the LabView embedded only works with specific processors and will not work with 8-bit images.  Yes, serial to transfer data instead of writing code to run on the controller.

  Kind regards

  Joe S.

• How to debug the program Labview that runs in the target of the RT of a Compact RIO

  I use CRIO-9073 for the acquisition of data from sensors. Program Labview is written in RT target and target FPGA. It is posssible to make step wise execution for the program written in the target RT and FPGA target the way purpose us for the debugging of the program in general OS.

  MJM,

  The only way to use the debugging on a VI wrote to FPGA tools is to simulate running on the host computer. You can then deploy the compiled FPGA code on the target and run your VI RT in debug mode if you use the communication of the façade with the host PC.

• LabView 8.5.1 embedded works on Windows 7 64 bit or 32 bit?

  I would like to install LabView 8.5.1 on Windows 7. Is it possible with 64 or / and 32-bit? Thank you!

  Thanks a lot for your help.

  So I just installed LabView
  integrated Blackfin 8.5.1 on Windows 7 64 bit and it still works
  without 'XP mode' also with the USB-emulator and VisualDSP ++ 5.0. Notice: the
  DVD - the installation program is not running on W7 (error-12) but you can install all
  module separately by using the configuration of modul of the DVD files.

  I'm happy, thank you...

• Using VI Server to check whether another executable LabVIEW is running

  Hello to you all, helpful people.

  I need to have a single executable check LabVIEW if an different LabVIEW executable is running.  The simplest way to do seems to be to ask Windows if the name of the executable runs.  A good thread is here.

  However, this requires the use of a tool (task list) that does not exist on all Windows operating systems I need support (all flavors of XP, Vista and 7).  In addition, even if I found an equivalent for each OS, I need to make sure that they continue to work and update my program whenever a new OS was released.

  A much better solution would seem to be to use Server VI in LabVIEW, so it is cross-platform.  However, despite reading over my printed manuals, by reading lots of subjects in the electronic manual, scanning through the forums and make some limited looking for a manual on the Web site of NOR, I still can't understand the basics of the implementation of a communication server VI between two executables.  It's very frustrating, because I'm sure it's a simple task, but I can't find the right instructions.

  A lot of instructions to configure a server VI say to go to tools-> Options-> VI Server: Configuration and enable the TCP/IP option.  Which seems exaggerated, if I only need communication on a local computer, but ok.  However, in other places told me that this sets the default settings for the instance of the main application (another subject I am still unclear on), so how does it apply to my existing LabVIEW project?  My current project is an executable, and I thought I would create a new build for the second executable specification.  Executable has all my existing code, while B executable would have just a reference VI available server ping, in order for an executable say if it is running.

  So I built executable B, and I joined his VI for your reference.  Deciding that the VI settings programmatically server configuration will be more comprehensible, I put options that seemed logical: a unique TCP Port number listen to Active = True, TCP/IP access list = IP Address of my computer and the executable = B.vi VI access list.

  In my test executable A.i, which I use to this get up and running before changing my main code, I use Open Application references with the IP of my computer, the unique port number and a short timeout.  I hooked up to a property App node to determine if I get the correct connection.  All I really need is to check the name of the Application and I'm good.  However, I keep getting 'LabVIEW.exe.

  If anyone call tell me that I forget in this simple configuration, I would be very grateful.  Some basics on something else I'm missing about how works the server VI, how the tools-> Options from the settings relate to all, etc., would be a big bonus.  Eventually I'll need a way to specify no IP address of the computer (or a way to interrogate LabVIEW), so I can broadcast these two executables on any random PC.

  Thank you in advance for your help!

  -Joe

  P.S. in the preview window that all of my text has run together; I hope sincerely that is not happy when he published, in particular given its length.  If so, I apologize!

  The application ini file should contain the following line:

  Server.TCP.Enabled = True

  Not to mention that this is a better way to see if your inside an executable file:

  

  Tone

• Write real Labview 8.2 Twincat embeded application variables

  Hello

  I am currently using Labview to write and read variables defined by an embedded application of Twincat.

  I set the following variables in Twincat:

  Lab_lecture_real % MW100: REAL;
  Lab_ecriture_real to % MW102: REAL;

  Mo1% Lab_lecture_bool: BOOL;
  Lab_ecriture_bool % MB2: BOOL;

  Based on the VI given by Beckhoff to Twincat ADS/OCX (http://infosys.beckhoff.com/english.php?content=../content/1033/tcsample_labview/html/tcsample_labvi... =), I managed to read the variables 'Lab_ecriture_real' and 'Lab_ecriture_bool' and write through 'Lab_lecture_bool '.

  However, I forgot to write in "Lab_lecture_real", which is a real.

  I enclose my VI, everything seems to be connected correctly. However, I do not understand why it works for a Boolean variable, rather than a true. The method used for writing a real is perhaps different from Boolean.

  Can you stress me about this, please?

  Kind regards

  Stéphane

  Why you set the length for the REAL number 8 in VI?

  It is in the documentation of the OCX elsewhere?

• POUVEZ, NOR-CAN1500, POUVEZ Labview drivers

  Hello

  I am currently using Labview 64 2015 on win 7 64 bit.

  When loading NICAN1500.exe (CAN labview drivers) it forces me to load it in the Program Files (x 86) folder. LabVIEW is installed in Program Files (without x 86)

  After loading it in x 86 drivers folder do not appear in the palettes.

  I loaded twice. Force suggested install NI of CMD did that and still forces me to load it into the x 86 folder.

  Help please.

  BR,

  Florence

  Well well, according to the white paper of OR you can use their drivers CAN on 32-bit LabVIEW only. The drivers themselves are 32-bit... It can run on 32-bit or 64-bit Windows 7, but the version of LabVIEW is limited to 32 bits if you plan to use CAN.

  I'm sorry.

• LabVIEW DSC Client\Server application. How to install the executable on the client.

  Hi all

  I'm currently programming an Client\Server application.  The server application must host shared variables, and the client application must read.  The client application reads the shared variable in the indicator of their connection with the properties of the indicator.  I started programming and the client application and the server are in the same project.  In the client application I am lie the indicator to the library in my project that has the "My Computer" as the address.  My question is how do I tell the executable installed on any computer, that I wanted to use the variables shared on the server?  I have LabVIEW 2009 DSC.

  Thank you

  If by "data binding", you hear the Variables defined on your computer, then Yes, unless you want not linked to new variables on each executable, in this case here is an example that can help.