Shared variables with touchscreen of TPC-2106

Similar Questions

• HOW WE LINK SHARED VARIABLE WITH DEVICE (SENSOR MODBUS ADDRESS) IN E/S SERVER MODBUS

  I USE THE IO SERVER MODBUS WITH SHARED VARIABLES TO COMMUNICATE WITH THREE DEVICES (TEMPERATURE, PRESSURE AND LEVEL DEVICE). EACH DEVICE HAS ITSELF MODBUS ADDRESS TO BE IDENTIFIED IN THE E/S SERVER. THESE DEVICES ARE SUPPORTED BY THE MODBUS SERIES.

  (1) HOW CAN I CONNECT EACH DEVICE SHARED THE DEVICE TO HELP ADDRESS VARIABLE?

  (2) HOW DO I USE THE ADDRESS OF DEVICE FOR IDENTTIFY THE E/S SERVER APPLIANCE?

  COULD YOU HELP ME?

  Thank you

  Hello

  You will find attached a few slides explaining the different steps to create variables shared with e/s server Modbus.

  You can also have a look at the demo on the website.

  I hope this will help you communicate with your devices.

  Kind regards

• Deploy shared Variables

  I'm having a problem with the help of EVS. I use LV 8.6 (impossible to pass to 2010 at this hour, must "make it work").

  I used before shared variables with a GUI and PXI, but my setup is different now:

  PXI (called target) that "speaks" to the different controllers via Modbus TCP/IP. Separate interface for PXI PC to provide a user interface (called my host).

  I ran across messages spoken by calling the library method to deploy in the first level VI of the application. I want the PXI to deploy variables shared, because it will run constantly and the PC is optional. "Manually" transfer the shared variable library, in this case called the NetworkVars, for PXI so the PXI application can find? PXI will run independently once the program is fully developed.

  I have used Labview for a long time but have never had to do a lot with networking and sharing.

  Thanks for any help.

  I ended up upgrading to Labview 2010 and now everything works as it should. I will mention that it was a complete horror show trying to upgrade... including duty reload WinXP on my development computer, because the files have become corrupt. Now, I have to charge a ton of programs, at a later date, because they are there but are not related. Fun stuff.

  Thanks for all the help.

• Shared variable data type: can I choose a picture of a typedef custom, without making the table itself a typedef?

  Hi all

  I would like to pass a table to a cluster on my network. My group is typedef'ed, but I would avoid to pollute my project with an another redundant typedef.

  Is it possible to use the option "From Custom Control... ' of the shared variable with an array without saving the table as a new .ctl file?

  Oh, I didn't know you were using shared variables. I thought that you were just considered another option with TCP/IP or UDP or something like that. In this case, you will need to create a second custom control. This control would be a table with the cluster of typedef in there. Not need to make this new control itself a typedef however. Sorry, I know you were hoping for a different answer. I doubt a single file will really be "clutter" your project well

• "Not a valid error code" when you create a shared variable of data type custom

  I am trying to create a shared variable with a data type of a 2d double table. I created a custom control that contains a table with a numeric type for this 2d. Manager of distributed system v12 I select 'add a variable', then select 'of the custom control. Once select my control I get the following error: "invalid data type. You want to choose a different data type. Any advice as to why it doesn't work? Thank you.

  This seems to be recorded in the CAR #405941.  All this is a bit strange, but I'll try better possible workaround solutions I can.  I tested a large number of these myself, and here is what I found.

  1. make sure that the custom control you did was created in 2012 of LabVIEW or you save it in an earlier version.  If you save on an earlier version, you may also open the .ctl in LabVIEW 2012 and resave it (I needed to do).  I tried to create my own control in 2012, as well as save the control to a previous version, the two worked, but I don't end up with the same result (I don't understand this, but I wanted to mention it so that you know).

  2. it seems that you are able to make the variable shared by program by modifying the example of the community to adapt to your needs.  If you do not need to create many variables it may be the best option if it works for you.

  I would also try adding the variable of the LabVIEW project, you are working on that.  It wasn't a direct troubleshooting step but there are several ways of doing things in LabVIEW and, sometimes, one of them is working while the other does not.

  Edit: Example of community is here https://decibel.ni.com/content/docs/DOC-16863

• TPC-2012 cannot read the shared variable

  Hello

  I have a TPC-2012 and can not read variables shared with him. I welcomed the shared on a cRio-controller Variable. On another PC, the variable is read correctly, but not on the tpc-2012. What can I do? No error message is displayed on the TPC-2012 (Windows CE 5). The PTC can not write values in a shared Variable.

  Thank you

  Christian

  What LabVEIW Touch Panel version do you use? I don't know why static variables do not work correctly on your device. TPC-2012 comes with support preinstalled for shared variables, and it would be possible that it has been deleted or corrupted. Here are some steps you can follow:

  Install the Support of shared Variables
  How do we install the Support of Variables shared on the TPC-2012?

• published RT cRIO-9030 with network-a project of shared variables cannot communicate with host VI when compiled and deployed as executable startup.

  I have a project including a VI RT running on a cRIO-9030 and a host VI running on a desktop computer.  The two programs communicate via shared variables that are hosted on the cRIO.  As shows, when I run the screw of the project, everything works as expected.  When I compile the RT VI in a start-up executable can deploy for the cRIO, as well as the libraries of shared variables (the record of support in the build specification-oriented), I am unable to connect to the executable running in real time.

  

  I have 'Disable Autodeploy Variables' checked on the cRIO target, if I no longer get the prompt to stop the currently running application to deploy the variables.  The host VI opens and appears to run, but has no connection with shared variables (data does not update).  Compilation of the host VI as an executable file and it works outside the project result in the same behavior.

  I read some relevant posts / knowledge base articles related to this problem, but still can't seem to find a way around it.  I note a number of articles on the series in double bond of variables, but this is in contradiction with my possible behavior for this system: I finally have a number of cRIO controllers identical all runnning the same executable RT and want to be able to have a single host VI which allows the user to select from a list of available controllers (using the screw system configuration) and extract the host name of the controller selected, that would be later used for programmatic addressing of the variables on the host of part VI.

  In any case, I want to start with the simple fact of being able to get that first controller running without an open connection to the RT VI project.  With the deployed executable start, I checked via programmed behavior of LED application of the RT and FPGA are running on the cRIO.  The problem, I think, has to do with shared variables, but I'm not sure where to go from here.  I want to connect to RT executable running from the VI to the host (in project) to verify that the compiled executable of RT works as expected and then the subsequently compile host VI in an executable that can be run from any desktop on the local subnet.

  Thoughts?

  It seems that the error has now been corrected.  There were three things, I changed: the file startup.aliases in the startup on the target directory (Home: / lvuser/natinst/bin) put in 'localhost' as an alias for the controller.  I changed it to the IP address of the controller.  Then, I got some features of IO files in my application RT relative paths using the path obtained by the 'current path VI' VI.  As this path changes according to the location / delivery system, I had to create a VI that has used the Application property: type with a case properly structure band / build railroads desired regardless of the runtime system data files.  This may have broke my RT request.  Finally, I got a property node in one of my RT SubVIs, who attempted to change an indicator in the Subvi, which is not taken care of in an RT compiled executable.  I can't do this for debugging purposes somewhere along the way, but in any case, I removed it, and after a recompilation and the deployment of the executable of RT, everything seems to work as expected today.  The host VI on the desktop can connect to the application of the RT project, and when it is compiled into an executable file, which also works.

• Shared variable of subjects with the executable in real-time

  We have a PXi target running Labview time real 8.5 and we use a series of shared variables for communication between the target and the client software. The code was developed (and used) in the last 2 years, and presented no problems with the shared variables when they are deployed since the Project Explorer (for the target and the laptop based client software). However, when you try to run an executable version on the system time PXI real target of exactly the same engine code variable shared seems to fail during the initial loading. Since it is an executable, it is difficult to display errors, but it seems that the accident occurred at the beginning of the program when we try to initialize a number of shared variables. Sometimes it loads but probably only 10% of the time. When you plug the tool to debug for code and restarting the executable, runs without any problem. However, once we managed to capture and error (error-1950678982 the shared variable client side read buffer is full).

  I checked a number of messages in the Knowledge Base (e.g. how to deploy Variables of a compiled executable shared network?), but it still has not solved the problem. Thoughts and suggestions?

  Adrian

  I tested it for a few hours now and I can't make it fail again. The big difference in my implementation was to use your suggestion, and no wire the error cluster through the method since the error it generates caused a number of questions later. So let me summarize the final configuration that seems to work then:

  -during the execution and executable on a target time real 8.5, startup not connected to a client. Library of shared variable hosted on the target and should load by itself.

  -J' added a flat structure sequence on the vi 'main' (top of page vi executable) with a node (as shown above) Invoke method in the first structure with a timer to 10 seconds and the rest of the code in the second part of the structure. The shared variable library has been copied to the target in a data directory and the path provided to the method (the same way as above) and the IP address is that of the target.

  I discovered that it takes about 8-9 seconds for the shared variable engine and library to start (I don't remember is that past exactly that) and it is important to wait this time to initialize shared variables or the behavior is unpredictable. The method always generates the error 1043 (function not supported) but I simply ignore it now, and it seems to work.

  Thanks for your help! I will let you know if there is some instability in the future, but everything looks good from here.

• Problem with shared Variables

  Hello

  I have a project that contains two VI: reading and writing, a shared library that contains a Boolean value (published on the network, type: Bool, alias uncheck).

  In Write.vi (diagram), there is a block button and a shared var node related.

  The same thing in Read.vi

  Aims to make the .exe working on another PC.

  In the project, I created the program installation and application.

  I try to run it on the second PC, but it does not work.

  Need help.

  AS2307,

  Are your read and write screws both on the same computer as shared variables of accommodation?  Both of these screws are working on the development of your PC and they work as executables on your development PC?

  It would be useful to know exactly what you did this works and what you have tried that does not work as it is has a few caveats with the help of executable actions variables as described in the article below.

  http://www.NI.com/white-paper/5715/en/

• cRIO and 9234 modules do not work or communicate via fpga with accelerometers, fpga, connected to the real-time application is also related to shared variables related to modbus slave

  Hello

  I have a compact rio, which has a 4 way frame this chassis is the three modules of ni9234, they are related using FPGAs for application in real time, then using shared variables in the low-speed loop associated with a slave modbus to communicate with the domain controllers, the nor 9234 accelerometers linked to them with option ac coupled iepe on c modules , my problem is the real-time application seems to work well even when power loss occurs it restarts without problem and the fpga written hard disk portable bin files very well, but without an accelerometer connected I get readings of low noise as soon as I connect an accelerometer to one of the outputs 10 it just goes to a fixed number (0.03125) as soon as you unplug it again He returned to readout noise, I ran a scan on the modules and get only a spike when I connect or disconnect the accelerometer, I tested voltage at the pins on the module and I get 22 volts CC which makes it more likely that the material is not the problem, but software is perhaps the cause to hang up, I join the project and files for your perusal. I also realized a new project which, in mode directly linked scan has the module entry in the shared variable and the scenerio even once again. Help would be appretiated.

  Thank you very much

  Jason

  Whren using waveform with the 9234 acquisition, we recommend the following FPGA and RT model.

  http://sine.NI.com/NIPs/CDs/view/p/lang/en/NID/209114

  It can be extended as a datalogger with:

  http://zone.NI.com/DevZone/CDA/EPD/p/ID/6388

  or using shared variables combined with the analytical engine

  http://zone.NI.com/DevZone/CDA/tut/p/ID/9851

  The FPGA in all this, as well as the framework of RT have used successfully by 1000s of users.  I recommend giving these a try.

• TPC-2106 t related query

  I want to connect TPC-2106 t with the CompactRIO-9014 cable RS-232 (serial). Could I connect to end of data i.e. communication to send orders in real time PTC VI, who will present the CompactRIO and receive data from the PTC something generating VI real time indicator. If yes then please suggest me how do I do programming?

  You will not be able to do this with series. Is there a reason that you can't do it via ethernet?

  If you are using ethernet, you need to use shared variables or TCP/IP to publish the cRIO data and then program the TPC to read that data and display them on the screen. If you plan to use shared variables, you can deploy the variables shared on the cRIO himself. If you need to see some examples, open finder example (help-> find examples) and access Toolkit and Modules-> Touch Panel-> Networking. If you have any other questions, after return.

• Migration of desktop to TPC-2106

  I apologize if this isn't the right place to ask these questions.

  Currently, I have an application developed in LabVIEW 8.0.1 and am looking to buy a TPC-2106 touch panel computer to be mounted on a chassis of large Assembly. I've never used a PTC setup from BEFORE, so I have a few questions:

  1. Other than the TPC-2106 itself and the LabVIEW Touch Panel Module, what else do I need to buy?
  2. I am currently usiing a cDAQ-9172 USB with two 9211 modules and a 9205 module. This USB cDAQ would be compatible with the PTC and/or Windows CE?
  3. The PTC will work with LabVIEW 8.0.1?
  4. How the PTC to get programmed, exactly? I select as the target on my LabVIEW desktop PC and the program gets compiled/uploaded to the PTC? Does this mean that when I compile / upload it, PTC no longer has need to communicate with the desktop computer?

  First of all, you can get more chance announcement questions about LabVIEW Touch Panel Module on the Board of LabVIEW.  It is unlikely that many people browsing the FieldPoint jury would not know much about the programming of a touch screen.

  1. to use the TPC-2106, you need the hardware, development environment LabVIEW and the LabVIEW Touch Panel Module.  You also need to use DAQmx Base driver for your hardware to work, but it's free.

  2. as you must use DAQmx Base on your touchscreen, you are limited to material, that you can use.  The list of devices that can be used with the 2106 is listed in the file Readme of DAQmx Base and does not include the CompactDAQ chassis.  I also glued the table below.

  Devices in	Description
  NEITHER USB-6008	12-bit, 10 kech. / s, 8 channels 12 HAVE line DIO, meter device 1 event
  NEITHER USB-6008 OEM	12-bit, 10 kech. / s, 8 channels 12 HAVE line DIO, meter device 1 event
  OR USB-6009	14-bit, 48 kech. / s, 8 channels 12 HAVE line DIO, meter device 1 event
  OR USB-6009 OEM	14-bit, 48 kech. / s, 8 channels 12 HAVE line DIO, meter device 1 event
  NEITHER USB-6501	Line 24 Dio, 1 demonstration counter device
  NEITHER USB-9211 HAS	4 channels of, 24-bit thermocouple input module
  NEITHER USB-9215 HAS	4 channels of, ± 10 v DC, module 16-bit simultaneous sampling analog inputs
  NEITHER USB-9215 A BNC	4 channels of, ± 10 v DC, module 16-bit simultaneous sampling analog inputs
  NEITHER USB-9233	4 channels of, ±5 v C.A., DSA 24-bit simultaneous sampling with IEPE module
  NEITHER USB-9234	4 channels of, ±5 VAC/VDC, DSA 24-bit simultaneous sampling with IEPE module

  3 Touch Panel Module exists only for LabVIEW 8.2 and later versions, however, you can only now buy for 2009.

  4. it's okay.

• Support of the shared Variables in the third part XP embedded based of PTC?

  I sent a request in an embedded XP touch function (third party). The application works very well, but hosted on a RT (sbRIO Board) shared variables are not getting updated in the app on PTC

  1. the PTC is part of the project as a Windows XP Embedded Touch Panel

  2 NI TPC Service has been installed on the PTC and the application can be deployed remotely from the PC development via ethernet. (Where network connections and communications are OK)

  3. using distributed in the development computer systems manager, I can see that the shared variables are getting updates on the network

  I think that the problem can be solved if the following programs are installed on the TPC

  A. Support for variables that are shared for XPembedded

  B. shared Variable engine

  I tried to install the support of variables shared Program Files > National Instruments > Labview 8.6 > PDA > utilities > Variables > x 86 - but I get an installation error "cannot find the application for the Pocket PC applications Manager.

  Shared variable engine was installed from the ve220 folder. The program is installing. But the engine Variable is not start Control Panel > administrative tools > Services, Xpe, the service is stopped and cannot be started. When I try to start the service, I get the following error on PTC

  "Cannot start Service engine of National Instruments Variable on the local computer."

  Error 1053. Service has failed to demand launch or timely control.

  Please suggest solutions to the addresses above or another of the following:

  1. support of variables shared for XP built-in PTC

  2 Installer engine Variable shared.

  Thank you

  Krish

  Problem solved!

  Update for interested people working on XP Embedded PTC

  Just to ensure that shared Variables were indeed accessible to the TPC, I wanted to install Distributed Systems Manager 8.6 on the TPC. However given that the TPC was only 1 GB of DOM (disk on memory) and with all the software that I had tried, there remained only a few megabytes on the system. I had to add an another DOM of 2 GB.

  All products in the Installation went well, with the exception of the Logos NOR (Version 5.0). Logos OR installation has failed repeatedly.  I tried to install NI Logos separately, with the same results. Then I had this intuition that NI Logos had anything to do with the question.

  Then, I downloaded the new version of NI DSM 2009 SP1. Even if it were to settle on any fresh system without Labview, the installation would not proceed beyond the stage of configuration. I tried to install NI Logos of the folder on the download of new products separately and it worked magically!

  Once the new Logos (Ver 5.5) installed, the Shared Variable engine starts automatically and the shared Variables are finally unleashed - free stand up and shine! I thank Almighty God!

  On the lighter side, come to think of it - to run an application about 400 KB, we need NEITHER of Run Time, XP embedded, DSM, Logos...  (around 900 MB). Can make us everything simpler?  Invite your comments...

  Thank you

  Krish

• to connect to a shared variable (android)

  Hello

  I just started to learn how to use the dashboard data Labview for android.

  I made a very simple project, with a VI that generates random numbers. I also added a variable published network shared in this project, and I write the random number generated for this variable shared every second.

  I would like to read this value on my phone (Motorola Razr i, Android 4.1.2) android using the dashboard of data for an Android application.

  I have a wireless access point and both my laptop (that hosts the project, LabView, Labview 2013) and my smart phone is properly connected to the wireless router, and both gets from dynamic IP addresses.

  I start running my VI on the laptop and the variable shared within the lvlib correctly deployed and began to broadcast (I guess) its value to the network.

  I start the DD application on my Smartphone, I choose 'Connect shared variable to', I type the local IP address of my laptop, which is 192.168.0.100, and I try to connect.

  After some 'research' and waiting, I get a message "connection error".

  Do I did wrong?

  Thank you much for the help.

  Best regards

  
  

• Network shared Variable breaks rtexe

  I have a cRIO-9063 which I want to use for the control (PWM digital output for pumps signals) and measurement (temperature and voltage) of a system. In the ideal configuration the cRIO would be able to take measures and rebroadcast to a PC for monitoring and logging. The PC must be also able to change the digital output PWM on the cRIO lines. The cRIO should be able to continue to operate when the PC is not available. To do this, I use Scan interface for data acquisition and shared variables (single editor, no RT FIFO) hosted on the cRIO for network communication.

  I have developed the code for the target cRIO as well as my host PC meets my criteria. However, this code only works in development mode. When I try to build and deploy a rtexe on the cRIO, it does not work. I reinforced to the back and made a simple LED flashing user vi, ensure what I create and deploy properly. Slowly adding things to this flashing vi, I discovered it's shared network variables that break the vi once it is integrated into a rtexe.

  After flipping through other-related posts, I'll include the following:

  -There is no object on the remote VI front panel. Simply add a variable node shared is enough to break the vi (when it is deployed).

  -J' tried including my shared variable library in support of the construction directory, but what I saw there is not copied during construction or deployment. I manually copied the library to the /home/lvuser/natinst/bin/data / directory on the cRIO, then used an invoke node to deploy the cRIO variables when the software starts first. Even when you include a delay of 10 seconds after the invoke node, it did not work, just a mistake of 1043 at "the method or property is not supported in this version of LabVIEW."

  -NSV is referenced as absolute

  Some details of my configuration:

  LabVIEW 2015

  cRIO 15.0

  NOR-RIO 15.0

  Communication via ethernet, static IP

  Any help would be GREATLY appreciated. I suspect that I forget a few minor step or detail, otherwise am poorly understand exactly how and when shared network variables are deployed.

  I found shared to not be worthwhile over the years network variables.

  The RT EXE is not able to use the library to deploy to deploy the shared Variables.  See Help topic: http://zone.ni.com/reference/en-XX/help/371361M-01/lvprop/app_libdeploy_library/

  In general, SV are deployed once the project and they persist through reboots of the RT system.  In general, you should have a startup routine that checks the shared variables and expected for there to be without error on a node of the OAS and then move on to the rest of the program, defining the commissioning of values and check that they spread in the engine of the Variable is a typical method.

  See here for more information on the deployment of a variable in an application of the RT.  http://digital.NI.com/public.nsf/allkb/990508969805A7C086257619007189E7

  The section deployment of Variables shared in a real-time (RT) target running Headlessly is downstairs.  Because you are connected to an HMI PC, you should be able to use the library to deploy feature of the PC code targeting the cRIO.

  Usually, it's a faster, more scalable solution to replace your shared network Variables with a stream of network dedicated to the HMI and another for HMI - RT EXE commands.  You can send complex structures such as a cluster or even define the message as a cluster of enum and variant type to be able to use the Enum to convert the variant correctly according to the Enum value.