What are the limitations of using labview 8.5.1 developers suite verses a real-time module in field point applications?

What are the limitations of using labview 8.5.1 developers suite verses a real-time module in field point applications? Can an exe. be loaded onto a field point controller or does the controlling program have to reside on a PC for example?

centerbolt is correct, you can't load a .exe or even run a program on the fieldPoint controller unless you have the Real Time module.  However, that does not mean you can't use your FieldPoint bank without the Real Time module. 
From LabVIEW for windows you can make calls to the fieldpoint IO using the fieldpoint read/write functions. 
This program runs on the PC not the FieldPoint controller.  If you loose network connection to the fieldpoint, your program will loose connection to the IO.  For many data logging applications this type of arrangement can work just fine.  However, if this is the only type of application you are ever going to run, then you may as well not buy the Real Time controller for your fieldpoint but the network controller only. 
If your application requires more reliability, and/or greater determinism than can be achieved by running a program on windows, then you should use the LabVIEW Real Time module and develop a program that can run down on the FieldPoint controller independent of windows.
Message Edited by StevenA on 07-22-2008 04:14 PM
SteveA
CLD
FPGA/RT/PDA/TP/DSC
Attachments:
fp pallet.PNG ‏6 KB

Similar Messages

  • What are the limitations regarding use of video in an iBook: length, file size, etc?

    What are the limitations regarding use of video in an iBook: length, file size, etc?

    Total book size is 2.0GB max. Length would be relative to size based on quality.
    See:
    - Optimizing performance in your iBooks Author books
    - iBooks Author: Add video to your iBook

  • What are the limits of using windows internal database in RMS?

    hi,
    We dont have SQL server to use and opting to use windows internal database
    What are the limits of using windows internal database in RMS?
    tnx

    Hi,
    the main limitation is that you cannot access a SQL express from remote (even there are tricks to work around that), so you cannot add another machine to the RMS cluster. 
    Microsoft's recommendation for production systems is to use a full SQL server, what allows you clustering and running all sorts of maintenance tasks.
    Other than that SQL Express has a 10GB total limitation for all databases running on that server.
    See also http://technet.microsoft.com/en-us/library/dd772673(v=WS.10).aspx for RMS hardware and software requirements. 
    Hope that helps,
    Lutz

  • What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi

    What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi ?
    I am modifying an existing workspace for a new product, and it seems like more work to add the vi's into a LabVIEW project
    does it gain anything in the long run

    Hi Rusty,
    I wanted to quickly clarify on the integration between TestStand and LabVIEW Projects.
    As Jeff mentioned, some of the big benefits of using LabVIEW Projects is to organize code and to namespace them.
    For instance if you had a project called "Power Supply" that housed all your power supply code and had a VI in that called "Initialize", and another project called "Temperature Chamber" that also had a VI called "Initialize", both these VIs are namespaced by the project, so there is no longer confusion about which "Initialize" VI is being used.
    Now from a TestStand point of view, in prior version of TestStand, we lost some of this benefit because TestStand did not know about TestStand projects and called VIs simply as un-namespaced VIs. However, in TestStand 2010 (released last year, free eval available at ni.com/teststand), we added the ability to (optionally) call VIs within the context of their projects. This means that:
    VIs are now namespaced by their project, even when called from TestStand
    VIs can use project specific constructs like NI-DAQmx tasks and conditional compilation settings
    Note: When creating deployments, the VIs maintain their projects and namespacing, so this benefit holds true for deployments as well.
    Additionally, someone had mentioned looking into using lvlibs to namespace your VIs for deployment. Two comments:
    With TestStand 2010, this is no longer neccessary since the project itself namespaces the VIs
    You might also want to look into LabVIEW Packed Project Libraries, which combined several VIs into a single file. Think of it as a DLL specific to LabVIEW that is as easy to call as normal LabVIEW VIs. TestStand 2010 can call VIs that are exposed by PPLs. In addition, the deployment utility can automatically pack your VIs into PPLs for deployment.
    Hope this is helpful!
    Jervin Justin
    NI TestStand Product Manager

  • End of memory. Labview + Real time module + Compact Field Point 2120

    My name is Michele Ciampichetti, I'm writing from Italy.
    Frist of all, excuse for my english.
    This is my first experience with Labview, and the application is not so easy. We use Labview 8.2.1
    Our system is costituited by two different parts: there is a Compact Field Point 2120 as remote target whit some I/O card, and a PC used to releave data and memorize them (host).
    The comunication between the two targets is performed by ethernet lan with Shared Variables not bufferized and not real-time fifo.
    The problem is this: the sistem requires a big number of Vis and Variables (about 20 Vis per target and 50 variables localizated in 5 different librarys all in the remote target), and it should store data, acquisited by the FieldPoint, on a database (SQL Server 2005), one time per minute. This storage is made by Labview Database Connectivity Toolkit, and it work correctly. The problem is an excessive consumption of RAM on the PC.
    The question is this: The use of many shared variables or vis, bring the memory to always grow? I try to explain myself. When we start our application, after the first minute and registration on the database, the memory grow of approximately 1,3 Megabytes. This is repeated every minute, and after approximately two ours, Labview break down and display "Not enought memory".
    We look the on-line help for one solution, and we have found that the variables (local and shared), the concatenate funcion, the array and Vi indicators copy in memory their older value when updated. Is possible that this is the cause of our problem? There is a method to avoid it? How labview uses memory? It is possible set it up for not maintain older value in memory?
    We need to run the application up to 4 days for complete its work, is a long test for a climatic room.
    We're looking forward to hearing from you.
    Best regards
    Michele

    centerbolt is correct, you can't load a .exe or even run a program on the fieldPoint controller unless you have the Real Time module.  However, that does not mean you can't use your FieldPoint bank without the Real Time module. 
    From LabVIEW for windows you can make calls to the fieldpoint IO using the fieldpoint read/write functions. 
    This program runs on the PC not the FieldPoint controller.  If you loose network connection to the fieldpoint, your program will loose connection to the IO.  For many data logging applications this type of arrangement can work just fine.  However, if this is the only type of application you are ever going to run, then you may as well not buy the Real Time controller for your fieldpoint but the network controller only. 
    If your application requires more reliability, and/or greater determinism than can be achieved by running a program on windows, then you should use the LabVIEW Real Time module and develop a program that can run down on the FieldPoint controller independent of windows.
    Message Edited by StevenA on 07-22-2008 04:14 PM
    SteveA
    CLD
    FPGA/RT/PDA/TP/DSC
    Attachments:
    fp pallet.PNG ‏6 KB

  • What are the limitations of using RMI over http with EJB?

    We have a requirement for an intranet application where the majority of the clients
    (Swing clients) will be able to connect directly using either T3 or IIOP. However,
    there are a number of clients that will need to traverse a firewall.
    We could use SOAP, but I dont want to lose the value that RMI gives us (clustering,
    security, statefullness support etc). I am thinking of using RMI over http - which
    Weblogic supports.
    I have been trying to find some documentation on the topic - but havent succeded
    so far. What I would like to understand is: What limitations I would have using
    RMI over http. Do I lose anything (apart from performance) using http?
    Regards,
    Nick

    You will have to enable tunneling on the server side and I have not heard of any
    complaints of using it.
    Shiva.
    Nick Minutello wrote:
    In fact, we are not using applets - and its not an internet application. We are
    using Java Webstart and Swing on our intranet (the problem of the size of the
    weblogic.jar is a pain - but well known)
    The question for me is; Apart from performance, are there any limitations to using
    RMI over http?
    Can we also use JMS over http?
    -Nick
    Shiva Paranandi <[email protected]> wrote:
    "Old wine new bottle".
    The biggest problem with the approach of Applets like
    stuff connecting to weblogic is the size of the classes that need to
    be supplied to the
    users. The applets/swing would need a lot of weblogic classes which you
    need to
    supply as jar file. This file can be in the order of MBs depending on
    the
    weblogic version. we had a similar kind of problem and migrated the applets
    to use
    servlets instead of directly invoking ejbs or jms topics etc. Having
    the applets
    connect
    to servlets you would still benefit from the features of clustering etc.
    and added to
    that
    you would reduce the number of remote calls.
    Shiva.
    Nick Minutello wrote:
    We have a requirement for an intranet application where the majorityof the clients
    (Swing clients) will be able to connect directly using either T3 orIIOP. However,
    there are a number of clients that will need to traverse a firewall.
    We could use SOAP, but I dont want to lose the value that RMI givesus (clustering,
    security, statefullness support etc). I am thinking of using RMI overhttp - which
    Weblogic supports.
    I have been trying to find some documentation on the topic - but haventsucceded
    so far. What I would like to understand is: What limitations I wouldhave using
    RMI over http. Do I lose anything (apart from performance) using http?
    Regards,
    Nick

  • What are the limitations in terms of data size  or performance while using csv or text file as datasource?

    <p>Also what are the limitations in terms of data size  or performance related issues while using csv or text file?</p><p>Is it the best practice to use csv , text file to use as a datasource to improve performance?</p><p>Please Advice.... </p><p>&#160;</p>

    <p>Hi,</p><p>Create Same Data Input for CSV and Text File ,Create 2 different reports one for CSV and One for Text ,run them one you have done that.</p><p>Go to Report Menu and Select Performance Information .Use the Data in that to check which one is good datasource to improve performance</p><p>Cheers</p><p>Rahul</p>

  • What are the limitation of the 4 Port Gigabit ethernet Security Service Module (4GE SSM)?

    I was wondering if anyone can help me out. I am trying to create a redundancy topology which require several connections to an ASA 5510. I am looking at extending the connections to my ASA 5510 appliance with the four port gig ethernet security module (4GE SSM). I am trying to find out what the limitations are on this particular module.
    I have heard that there might be limitations to the 4GE SSM. Such as the interfaces on this module might process data separately from the ASA 5510 appliance. My question is does the ASA four port gig ethernet security module (4GE SSM) interfaces act as a extension of the ASA 5510 appliance or does it process and filter data separate from the ASA 5510 appliance ?
    My concerns are that the 4GE SSM does not utilize all the security features of the ASA 5510 appliance, and that it just separates traffic into security zones. I interpret that to mean that each interface can be placed in a separate security level in which case has a separate security algorithm and uses the security level to force security policies. Nothing more.
    My second question if relevant would be what are the limitations?
    Thank you for your help on this topic.
    mike

    The 4GE SSM just gives you the four additional ports. It doesn't increase the processing capacity of the 5510 (a relatively low end box whose replacement - the 5515X -  has been out since this past spring). It works off the same configuration script and CPU as all the built-in ports.
    The only limitation I can think of off the top of my head is that members of an Etherchannel cannot span the SSM and the built-in ports.

  • What are the limitations of remote API?

    Excuse me,
    I am new to Oracle BPEL, and going to customize the worklist application using remote API.
    I read the Sample Worklist Application for learning the remote API.
    When I learning about task attachment's API,
    I saw a thread
    RemoteWorklistServiceClient -- attachment
    Suddenly, I found that there is different between local and remote API.
    Would anyone like to tell me what are the limitations of remote API?
    By the way, could there is any API for retrieve process list?
    The reason is I am trying combine some feature of the console into my worklist application
    such as list process with details, deploy/undeploy process, active/retired process lifecycle and turn on/off process state.
    I only found how to start process:
    Locator lLocator = new Locator({Domain}, {Domain.Password}, {Properties});
    IDeliveryService lDeliveryService = (IDeliveryService) lLocator.lookupService(IDeliveryService.SERVICE_NAME);
    lDeliveryService.request({ProcessName}, {OperationName}, {NormalizedMessage});
    Thank you very much ^^
    Roy

    Excuse me,
    I got the answer by testing the remote API
    And I have another question about the BPEL API which used in the console
    I have success construct the class com.oracle.bpel.client.Locator
    It providing a set of methods for invoking Oracle BPEL
    However, the methods always using WhereCondition as parameter
    therefore, I need to know about the database.
    1. Could anyone tell me where can I found the database schema?
    2. There are some deprecated APIs what is the preferred APIs of them?
    - IDeliveryService.SERVICE_NAME
    - IDeliveryService.request({Process}, {Operation}, {NormalizedMessage})
    - IDeliveryService.post({Process}, {Operation}, {NormalizedMessage})
    Thank you very much ^^
    Roy

  • What are the limitations of ODI?

    ODI is an E-L-T tool of its first kind and has good performance when copared to ETL because of its architecture.
    BUt what are the limitations of ODI?
    And What are the strong points to recommand ODI to the clients?

    what are the limitations of ODI ::
    (i) it won't support multi target We cant say it wont support. We can achieve this using IKM mTI or using some logic in a single interface. But directly you can't drag multiple table into interface (target canvas)
    (ii) Interfaces are depending on KM so to implement any new logic we need to know about Jython Not exactly. But yes if you know jython it is more helpful for this. Discussed
    http://www.linkedin.com/groups/How-was-ODTUG-Ask-Experts-140609.S.197740849?view=&gid=140609&type=member&item=197740849

  • What are the limitations of AJAX in BEA Weblogic 10.2 ?

    Hi All,
    I am wondering if some one could tell/summaries what are the limitations of AJAX in BEA weblogic portal 10.2 ??

    Please reask this question in the WebLogic Portal forum:
    WebLogic Portal
    I think you'll need to be more specific as well. Are you referring to portlet development, in which the portlet uses a javascript library, drag/drop functionality in Dynamic Visitor Tools, etc?
    http://edocs.bea.com/wlp/docs102/clientdev/ria.html#wp1008891

  • What are the limitations of layout builder

    Hello BPS Experts,
    what are the limitations of the layout builder.
    Suggestions appreciated.
    Thanks,
    BWer

    Hi,
    One of the major one, I would say is needs SAP GUI without which it cannot be used.
    The same is no longer applicable to Integrated planning as it has a web based interface.

  • What are the limitations of apex 3.2.1

    Hello All,
    what are the limitations of apex 3.2.1
    thanks/kumar

    Hi Kumar,
    as Tony already pointed out, there are no hard limitations for Oracle APEX.
    As APEX runs in the database you can do whatever your Database can do (call Packages, use Analytic Functions, even call Java in the Database, create complex Queries with literally limitless joins).
    The Output of APEX is HTML and can be influenced by your templates and your code, so again you are only limited by your imagination. Add a different CSS and your Layout looks different. Add some JavaScript Code and your Forms behave different, are more interactive and so on.
    brgds,
    Peter
    Blog: http://www.oracle-and-apex.com
    ApexLib: http://apexlib.oracleapex.info
    Work: http://www.click-click.at

  • Wiki or Robohelp - What are the benefits of using a wiki vs publishing projects in robohelp?

    What are the benefits of using a wiki vs publishing projects in robohelp? I currently use RH9/RH9 Server and  publish multiple SSL.  The company is looking to stop using Robohelp and replace our online help authoring tool  (RH) with a wiki. Are there any benefits of going to a wiki environment.  What RH features/functions that I have today will i not have by having IT import our robohelp files into a wiki?
    I know that a wiki is not an authoring tool, but someone must think it is and we'll still have all the functionality of publishing multiple SSLs, reports, etc once in the wiki environment.  Any comments - is this the best route?

    Hi,
    There are many differences. The idea of a wiki is to allow anyone to view and/or edit the content. Depending on the wiki system, you can set access control for viewing and editing.
    Wiki's typically have simple syntax (html in a wiki is a serious security risk), allow image embedding, links and attachments. You will need to learn the specific syntax (rather easy, but also very limited).
    What will you lose? This depends on the features available in the wiki system as well as the available plugins. A few downsides:
    - WYSIWYG editor limited, if at all.
    - No snippets
    - No variables
    - Dropdowns (may be possible through plugins)
    - Index
    - Styling based on css classes (mostly supported through HTML which is a security concern)
    - Only one version of your support system: multiple versions require multiple installations/configurations.
    - No searching in attachments.
    - No CBT (Though some wiki's allow comments in the wiki code)
    - No Word/FrameMaker import.
    - You have to create your own CSH calls.
    On the upside:
    - Most wiki systems are free, even for commercial use.
    - The syntax is quite simple, allowing you to quickly write text.
    - Wiki's typically offer good support for syntax highlighting.
    - They are very easy to set up.
    - Most wiki's have plugins to enable comments.
    The greatest downside in my opinion is that you always have the latest version of all files. Whenever you update a page, everyone immediately has the latest version. And if you want to create help for a feature that isn't released yet, you will have to use access control to make sure not everyone sees the (unfinished) help for the unreleased feature. With RoboHelp you have a single source that creates a one way output.
    We use both RoboHelp and wiki's: RoboHelp for customer help and wiki internally to share knowledge. And sharing knowledge is what wiki's are designed for.
    Greet,
    Willam

  • What are the limitation or drawbacks of ESB?

    Can any one let me know what are the limitation or drawbacks of ESB?
    Fred

    Hi Fred,
    This is new question and different to this post's title :)
    When it concerned to security of an ESB management portal, there are two more often used practices.
    It’s being a web portal-a thin client, it can be accessed outside the BizTalk server- not like admin console (admin console can be accessed outside BizTalk server, it’s another matter). So
    that administrator can view fault
    details when they get error alert and action faulted messages. Follow the steps detailed here to achieve this.
    Another practice is installing
    ESB management portal in
    multi-machine environment with minimal access
    configuration, then here an excellent article step-by-step guidance on this topic.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Maybe you are looking for