Running Compact FieldPoint without LabView RT

In using Compact FieldPoint, how necessary is it to run
LabView RT instead of just LabView?

I believe it depends on what you are trying to do.
If you want to monitor your tags from a Windows based LV app, you should be fine.
If you intend to target your RT app at the Compact FP unit, you will need RT.
What are you trying to do with your Compact FP?
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

Compact FieldPoint without LabView RT

When using Compact FieldPoint, how necessary is it
to use LabView RT as opposed to just using LabView?

Currently, the only available controllers for Compact FieldPoint are the cFP-20XX series LabVIEW RT controllers. If you do not use LabVIEW RT, you do not take advantage of their full capabilities. However, the controllers publish all of their data items over the network just like the FieldPoint Ethernet Network Modules (FP-160X series) do. So you can use them as regular ethernet network modules and access them without LabVIEW RT, but you do not get to take advantage of their serial ports or embedded control abilities.
Regards,
Aaron

Run myapp.rtexe without LabVIEW ?

I would like to distribute my Real Time Target application, myrttapp.rtexe, to other users who do not have LabVIEW installed. I have a Windows side front panel application that communicates with it using shared variables. This is started as a standard myfpapp.exe in Windows. When I have LabVIEW installed on my Windows side PC, I can start myrttapp.rtexe using the Project Explorer > Build Specifications > rt. clk. myrttapp.rtexe > Run as startup. However, the people to whom I will be distributing myrttapp.rtexe, will not have access to the Project Explorer because then don't have LabVIEW installed.
Is there any way I can launch myrttapp.rtexe without using Project Explorer or LabVIEW?
Thanks in advance,
BenCh01
Solved!
Go to Solution.

Tst,
Your idea of using FTP VIs to transfer to the real time target CompactRIO an image from a source file on my Windows-side hard disk drive has been implemented in system replication tools, specifically the rtcopy.vi.
If the real time target root folder contains a c:\ni-rt.ini file, it should manually be set to have
RTTarget.ApplicationPath=c:\ni-rt\startup\startup.rtexe and
RTTarget.LaunchAppAtBoot=True.
This manual setting can be done within the HDD image that is transferred to the CompactRIO. It can be combined with the FTP VIs you suggest that I use, or with the rtcopy.vi system replication tool, to accomplish the same thing that is performed when Project Explorer is available with the LabVIEW development system, and a Build Specification > Rt click startup.rtexe > "Run as startup" is done.
Is this posting correct, so far?
My followup questions: you said I should stop whatever is running on the CompactRIO, over TCP, before downloading the new cRIO image. What VIs are to be used, to do stop what's running on the cRIO? I would like to stop both the program loaded into the CompactRIO-9014 controller and the NI-9103 FPGA. I read somewhere that enabling an rtexe file - does this mean loading the correct c:\ni-rt.ini file? - will override any startup VIs, and only the startup.rtexe will run, the Startup VIs will not. Does that mean that loading the CompactRIO and also the c:\ni-rt.ini file will preempt any Startup VIs previously running?
If so, then is it true that I don't have to go through TCP to stop the old cRIO and FPGA apps from running, enabling the rtexe file will preempt the old VI running on the cRIO?
Thank you, your experience goes where my mind dares not.
BenCh01

How can i make the .exe run on the computer without Labview?

.exe can't run on computer without Labview. Is there any way? Thank you.

You need to install the LabVIEW Runtime engine for your specific LabvIEW version.
In the project window you can create an installer that includes the Runtime Engine (RTE).
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Standalone application without labview ?

Hi
I am trying to build an .exe file using application builder in LabVIEW 7.0. Is it possible to build an application without labview dependency ? In short, I want something like an .exe file which will run on systems without labview. I know visual basic has this facility. Please let me know.
Thanks
Sridhar.
Kudos always welcome for helpful posts

"Maximus00" <[email protected]> wrote in message news:[email protected]..
> . . . I wanted an option where he can view my application without having
to install anything on his PC. Looks like that is not possible ? Am i right
?<br><br>Sridhar.
You are not right. It is possible. With LV 7.0 and previous versions (I
don't know if this still works for 7.1), the executable will run correctly
if lvrt.dll and the other support files are in the same directory. So you
could, for example, put your executable on a thumb drive. Copy all files
and folders in the C:\Program Files\National Instruments\shared\LabVIEW
Run-Time\7.0 directory to the thumb drive as well. Then your supervisor
could just run the program from the thumb drive without copying anything to
his computer. Or, if you want the drive back, he could copy the entire
contents to his drive without using an installer.
But this begs the question, if your supervisor is evaluating executables you
are creating in LabVIEW, what's the problem with installing LV Run-Time on
his computer?

Running a LabVIEW app on a MAC yosemite without LabVIEW

Hello all !
When you compile LabVIEW codes on a Mac, you create a ".app" instead of a ".exe". I would like to run my ".app" on another Mac running with Yosemite (OSX 10.10) and without LabVIEW on it.
I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work ...
Has anyone already done such a thing and would have a method to follow ? :-)
Thank you in advance !
Solved!
Go to Solution.

gvanhoeke wrote:
When you compile LabVIEW codes on a Mac....
LabVIEW VIs are always compiled. You are probably talking about building a standalone executable.
gvanhoeke wrote:
I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work
Instead of the "latest", you need the runtime engine that matches the LabVIEW version used to develop the program.
(Sorry, I have no direct experience with Macs)
LabVIEW Champion . Do more with less code and in less time .

Can I run code written in LabView on machines without the software loaded?

I am new to LabView and have purchased software with one license. The radios I am writing scripts for are controlled by laptops, can the scripts I write be run from these laptops without LabView loaded to them?

If you don't have LabVIEW Pro, then you can purchase the application builder alone:
http://sine.ni.com/nips/cds/view/p/lang/en/nid/10731
Matt Holt
Certified LabVIEW Architect

Selecting and running vi's on a compact FieldPoint 2120 via remote panel

Hi,
I'm trying to provide two html files to run two different vi's on a compact fieldpoint. I can run either of them by setting them as 'run as startup' in the Build Specification which creates the startup.rtexe program on the controller but the only way I can run two different vi's on the fieldpoint is by renaming the files in the startup directory before calling the html file (and that doesn't work that well). Is there a better process to allow different programs to be run on the compact fieldpoint via the remote panel/html calls?
thanks

Hey AgB2,
I think the best way to get multiple HTMLs linked to their respective VIs would be to set your VIs as the Startup VIs when you build the EXE to deploy to your Compact Fieldpoint. A KnowledgeBase article describing the steps to do this can be found here:
http://digital.ni.com/public.nsf/allkb/466EA9705F98E07786257687005E081B?OpenDocument
Next, all you'll need to do to get your two HTML files to run two different VIs will be these steps:
1.Build the HTML for each VI you want to control
2. Enable the WebServer for your cFP
3. FTP your HTML files to the www folder on your cFP
Once you restart the cFP, your EXE will run at startup with both VIs and you can access them by navigating to http://<ip address>/<vi name>.html. Just to double check, I did this on my computer and had no problem loading both HTMLs or taking control of both VIs at the same time.
Logan H
National Instruments
Applications Engineer

Run exe constructed in labview 6i without loaded nidaq drivers.

Exe is constructed using labview 6i. It would be convenient to install the exe and run time engine on the HDD,
and execute as a demonstration program, without loading the nidaq drivers.
No daq card in pc, nidaq would be on CD. Suggestions are appreciated.

If you want to run an exe without loading DAQ drivers, you will need to ensure that no DAQ calls are statically linked in the final executable. As waldemar.hersacher mentioned, you can do this by using VI server for all your DAQ calls, then calling stub routines if you are using the laptop for demo purposes. It would probably be easiest to put all your DAQ calls into a few subVIs and call those dynamically instead of each individual DAQ VI call. If you miss one, your launch will fail when DAQ is not present (you will get the standard LabVIEW searching for subVIs dialog and then a message telling you that you need the full version of LabVIEW to correct the problem).
There are lots of ways to switch between the "demo" mode and the "live" mode. A dialog which pops up on startup and is accessible from the menus is the most obvious.
Good luck. If you need more hints, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Why does it report missing *.dll when running standalone programs on a separate PC without LabVIEW?

I wrote a LabVIEW code to control GPIB, DAQ and Serial port. Then I built an installer including runtime engine. Everything works fine at the PC with the LabVIEW. I copy this installer folder to another computer without LabVIEW. I had no problem to install the program. But after I run the program, it started to ask for nilvaiu.dll. After I copied it under C\Windows\System32\, it started to ask for nimdbgu.dll, then niorbu.dll. Then it reported "The procedure entry point_pkgModulePackageEventLog@20 could not be located in the dynamic link library NIPALU.dll"
I guess it missed some drivers. So I installed NI-488.2 for Windows on the PC. But it did not solve the issue.

hi there
i recommend to update to DAQ 7.4. the performance is much better.
best regards
chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Is there a way of compiling a VI so that it runs on a PC without Labview installed?

Is there a way of compling/exporting/publishing a finished VI so that it runs on another PC without LabVIEW installed on it?
Message Edited by bluefocs on 04-29-2009 10:34 AM

You will always need the LabVIEW Runtime Engine of exactly that version the VI was built in.
Every VI is executable in the appropriate runtime engine without the need for the developement system.
In order to start the execution of a VI without using the developement system, you most often use .exe or sometimes .dll as files. And i think you are up to this.
You need the LV Application Builder to build an exe or dll containing your application. The Application Builder is part of the LV Professional Developement System, the other ones (Base and Full) can include it as an extra tool (liable to pay costs).
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Timed switching of channels on Compact Fieldpoint DO401

I am running a compact fieldpoint system with 4 x DO-401 modules in it. The idea behind my program is to create a control program that will switch the outputs of the DO-401 at predetermined times. These times being set/stored and then loaded when a certain sequence is required by the user.
I have achieved this in what seems a crude and basic way which seems to be slow to run.
In total i have 60 output channels to control, each one has a 'start time' and a 'duration' field allowing the user to state when the channel is to be switched and for how long.
My current solution is to have my program running in a flat sequence. Within this flat sequence I have 60 x smaller flat sequences.
The flow of these sequences are - Wait for the start time to be reached - Send a high value to the specific channel address (using CFP assistant), this switches the output of the channel on - Wait for the 'duration' time to be reached - Send a low value to the specific channel address, switching the output off.
This approach works but seems untidy and i am sure there is a better approach out there.
Can anyone suggest any ideas

Hello,
Take a look at the attached VI. This is an quick way to achieve what you are after. The code is documented so you can follow whats going on. On the Front Panel the user inputs a start time, which FieldPoint line it should be targeting and a duration in seconds.
To comment on the previous post this would be a more efficient and ultimately more accurate way of doing this, although the development time would be increased.
In LabVIEW there are VIs to pull out channel lists and devices from an IAK file so you could programatically decide which channels you could output to without any human interaction (after you set up a configuration file within LabVIEW.) These can be found in the Advanced palette in the FieldPoint sub-pallete.
Good Luck
Tom | NIUK
Attachments:
solution.vi ‏29 KB

How to install "Compact FieldPoint Embedded Data Logger Example Program" on cfp2200

i finally managed to get max to see the devices of my cfp2200.
(i had to disable every unused networkadapter due to overlapping subnets)
now i want to deploy the example programm "Compact FieldPoint Embedded Data Logger Example Program"
http://zone.ni.com/devzone/cda/epd/p/id/3221
i therefor have tried to install the runtime 8.5 on the target. however this is not possble, because i have labview 2010 installed and it gives the message:
"the host has a newer version available"
ok. runtime 2010 should work to - not?
i open a new project - import my *.iak-file and drag-n-drop the content of "cfp_data_logger_source.zip" onto the target.
now if i open the file cFPEmbeddedDataLogger.vi the run-button is cracked and by pressing it an errorlist opens.
the errors say stuff like:
target does not support this function/subvi
and
vi has been modified with a different applicationinstance
please help me to make this work.
i know that it is possible to get the programm to run on the cfp2200 even dough it is primaly designed for the cFP-2000, cFP-2010, cFP-2020, cFP-2100, cFP-2110,
cFP-2120.
big THANX already for you help !!!!!

Hi, thanks for your help=) I've manage to drag the file into my targeted controller. I am now doing the setting of the data logger program, but there's one thing I'm unsure of. May I know what does it mean by the cFP controller clock? http://zone.ni.com/devzone/cda/tut/p/id/3219 . Thanks. =)
Log On Startup
Start logging when the controller powers up.
Start Log Time
The time to start logging.
Stop Log Time
The time to stop logging.
Note: Make sure the clock is set correctly on the controller. The settings described above refer to the cFP controller clock.
Log Rate
The number of milliseconds to wait between each acquisition.
FP Drive For Data Files
The drive to store the log files in. The C: drive is the default for all cFP controllers. If you want to save to the removable CompactFlash drive on the cFP controller, select the D: drive.
Digital "Pause" Line
The Digital Input item to use as a "pause" button for data logging. Logging pauses when the signal is high. When the signal goes low again, a new file is created and logging continues if appropriate.
Note: Use only Digital Input items for the Digital "Pause" Line.
Tip: You can use DIP Switch 3 to block the current data from being logged. This switch works the same way as the Digital "Pause" line.
Logging Session Tag
Is stamped on the spreadsheet that the data logger creates.

DSC for compact fieldpoint(cFP)

which IO server type should be used for building DSC application for compact fieldpoint target?
when i use my computer as target then i get various options for IO server type like custom VI,opc client,epics,data set marker,modbus.But when i choose compact fieldpoint as target i got only epics and modbus options.Is there any problem with my HW/SW or with my concept?
kindly clearify.....
regards
vks

Hi,
if you just wanna use Labview for logging and graphics (using Ethernet) AND you do NOT use a Real-Time cFP-Controller then you do not need Labview Real Time.
E.g. if you use NI cFP-1804 - Ethernet/Serial Interface for Compact FieldPoint.
(http://sine.ni.com/nips/cds/view/p/lang/en/nid/202527)
If you are using a Real Time Controller than you will NEED Labview Real-Time.
You cannot work without it!!!
Best regards
Dippi

Why should I prefer NI Compact FieldPoint to Siemens S7-400 PLCs?

NI guys please answer:
Why should I prefer NI Compact FieldPoint controllers to Siemens S7-400 PLCs to build an automation and monitoring systems for a factory?
I am asking this because one of our clients insists to use Siemens S7-400 family of PLCs to build an automation systems and we want to convince them to use NI cFP, but we need help from NI advisors to bring more satisfying reasons to our clients in order to change their mind.
The case includes 51 AI, 15 AO, 108 DI and 51 DO.
The whole process of this chemical factory must be automated and also monitored in a control room in two touch screen monitors and a big 52" LCD panel.
Any help will be appreciated from NI advisors!

For what it's worth, I'd like to make a comment. It's difficult to compare the various PLC vendors with the NI line of products such as cFP because everyone has their various perceptions. In short for me, the NI products are far easier to program than typical PLC's because of the much greater flexibilty and the rich features found in the LabVIEW programming environment. I've programmed several PLC projects over the years that include GE Fanuc, Allen-Bradely, Omron and Siemens (Including the S7-400 series) I'll take the LabVIEW environment any day over miserable ladder logic and the other versions such as instruction lists. The customer gets a better product when it is easier to program and test. I often provide features for the customer using LabVIEW and cFP that I would never think of doing using ladder logic. The bottom line is that it's too easy to compare hardware without consideration of the software or benefits of features available.
And then there are the customer's perceptions. Just the other day I met with a potential customer who hates Siemens with a passion because he had experienced a lot hardware failures. Conversely I have other customers who will not accept NI products only because they are not familiar with them. For example, their technical personnel are familiar with Allen-Bradley and so that's what they want to stay with. I have a very large international customer who has a corporate mandate to use Seimens. It goes on...
I consider my time to be somewhat valuable, which means that I have different pricing structures that are based on what the customer wants. When a customer requires a non-NI product, I literally double the charge for programming time. Some jobs I win and some I lose. However, I'm very busy in the mean time and will continue the preference of vi's over PLC programming.

Running Compact FieldPoint without LabView RT

Similar Messages

Maybe you are looking for