Real time control application

I am going to use NI PXI-6070E for real-time control application, can someone provide sample programme for me?
Thanks a million!

Many examples can be found in the LabVIEW Example finder (Help->Example finder), in the ...Programme\National Instruments\LabVIEW 7.1\examples directory or on ni.com, e.g. here are some RT examples:
http://zone.ni.com/devzone/devzone.nsf/webproducts/c25f8c664230613a862567df006abb06?opendocument
The 6070 is only a multifunction DAQ card, you still need a RT controller, e.g. the 8187:
http://sine.ni.com/apps/we/nioc.vp?cid=13981〈=US
Kai Kratt

Similar Messages

Initial Error during Real-time control

Hello all,
I am currently controlling a DC motor in real time by using an simple PI controller.
Unfortunately, I found that there is some initial error when the desired motor speed (which i desired) is zero, the error signal come from the actual DC motor is oscillating at -3.
What should i do in order to make the initial signal to zero?
Thank you very much.

Ok barp, i had work out for many scale (-0.1, 0.01, 0.1, 0, 1, 2, 10, 100, 500, 1000, 2000, 3000) and i will show you here. P/S: Red color= Actual motor speed, Green color= Setpoint(desired Speed), and the white color= controller signal.

Real-time control of properties

I'm poking around for a way to manually control a property of a layer in real-time, like you might do with pitch, playback speed, and volume on a MIDI controller. Ideally, I'd like for AfterEffects to capture the changes as keyframes, or something like that. I'd love to be able to drag a scrubber, or draw on a canvas with a stylus, and have AE translate those real-time movements into changes in clip properties.
I don't have a lot of experience with expressions, but I know how to write code. I think, with some research, I can get this to happen by using the Write-On effect, drawing on a canvas with the stylus, and then linking various properties to the X and Y coordinates of the brush. This is a decent partial solution -- at least I could capture organic movement and apply it to these properties, so I wasn't so hung up working with curves and Eases and quirky intermediate keyframes.
But it would be awesome if there was a plugin... or some precedent technique or expression... that would let me preview the clip in real time at a low resolution, and then use the stylus or mouse to capture movement as I watched. It would be a great tool for syncing certain properties to a soundtrack, creating complex and organic animations, stuff like that. I'd love to be able to do this with the TimeWarp property, and preview it as I went along.
"Changing properties" and "Controlling behavior" plus "Real-time" didn't come up with anything relevant, either here or in Google. Anyone have any leads as to how this type of thing might be achieved?

As Mylenium says, Motion Sketch is one way. There are also some specific features that have this kind of thing built in, like sketching with the Puppet tools and recording paint strokes.

Error 53 PID Autotune with Real-time fieldpoint control

Hi!
I cannot perform the autotuning PID parameters in fieldpoint cFP-2000 (Real-time control).
It gives me the error 53 as you see in the attachment file. It seems to be because of the autotune wizard vi...???
How can i solve this problem?
Thanks for your help!
Nunix
Portugal
Attachments:
error 53.bmp ‏166 KB

Hello,
LabVIEW RT does not currently support the autotuning feature, because the procedure invokes a wizard that requires user interaction. LabVIEW RT does not support this type of user interface. This wizard is tightly integrated with the PID function itself and would require significant redesign to work in LabVIEW RT.
It is the autotuning VI itself that is not compatible with LabVIEW RT. You can use the "PID Autotuning.vi" as long as you are not targeted to your RT engine. Run your VI in development mode with the "PID Autotuning.vi" in your code. After you receive your tuned gain settings, replace the autotuning vi with the normal "PID.vi" and use your tuned gains for the inputs. You can now target to your RT engine with tuned gains.
Hope it s help.
Isabelle
Ingénieur d'applications
National Instruments France

Scheduling in Real-Time Java

Hello,
I have some questions concerning how scheduling in fact is intended to be performed in a RTSJ based Real-Time Java System.
As far as I understood, RTSJ requires pre-emptive priority-based dispatching of Schedulable objects.
This means that the execution eligibility of a schedulable entity is mainly its priority.
That causality is reflected within the specification with the (one-and-only specified) PriorityScheduler, which is the base scheduler for actual Real-Time Java applications.
Furthermore, there is a notion of extensibility of that PriorityScheduler described by RTSJ,
in order to provide further scheduling mechanims and feasibility analysis algorithms (please correct me if there are any wrong assumptions).
This is the point, where everything becomes really weird to me ...
As far as I could investigate, in most RTSJ implementations based on a POSIX compliant system underneath (like Java RTS does on RTLinux or Solaris)
each (Realtime)JavaThread is mapped 1-to-1 to a light-weight process on the operating system level (e.g. a pthread).
So far, we have no "green threads" within the JVM, but real LWPs scheduled by the OS.
The difference between "normal" and "real-time" threads lies in the scheduling policy used for that mapping.
While normal Java threads probably map to SCHED_RR or SCHED_OTHER, real-time threads are scheduled by the OS via the SCHED_FIFO policy in order to achieve a better real-time predictability.
However, the OS's scheduling mechanisms automatically make decisions about the right positioning of a LWP within an appropriate run-queue, due to thread's preemption, blocking or release (even dynamic priority changes) activities and its scheduling policy.
That's exactly why I ask myself, what is the need of a Scheduler representation within a JVM?
Furthermore, how a Scheduler extension is able to incorporate with the threading model and the underlying scheduling mechanisms of the OS?
One point could be a situation where a real-time JVM runs directly on top of the bare hardware and has to perform scheduling decisions on its own.
The Scheduler API could then be understood as an extension mechanism of a kind of JVM-intern scheduler (e.g. the PriorityScheduler), thereby allowing scheduling decisions to be made even in user defined Scheduler implementations.
A similar use case for an OS-based scenario could be if a JVM is intended to pass scheduling/threading routines of the underlying OS (eg. a part of the POSIX API)
up to the Java application level in order to provide the opportunity for a kind of application defined scheduling (like e.g. in the MaRTE OS).
Unfortunatelly, after introspecting the RTSJ API, both conclusions seem to me to be wrong.
So far, Java RTS seems not to provide any mechanism for reaction on scheduling events/decisions, neither intra-JVM nor from an underlying OS outside of the JVM.
Furthermore, there is no notion for incorporation with the base PriorityScheduler for making extended scheduling decisions.
I hope this post could bring me more light into the scheduling idea behind Real-Time Java systems as intnded by the RTSJ.
Sincerely,
Vladimir

Vladimir.Nikolov wrote:
That means, that a scheduling policy different to PriorityScheduler can only be assigned to a Schedulable object if it is supported by the OS and the JVM?Well it has to be supported by that implementation of the RTSJ. Howe that is done - ie whether it requires OS support - depends on that VM, the OS and the actual scheduling policy.
It also seems that at the current state of the art the PriorityScheduler representative within the JVM is intended only for manipulating a feasibility set of Schedulable objects (supporting online feasibility analysis)?
However, since user-defined scheduling is not intended by the specification, applications have to rely on the feasibility analysis based on the underlying/supported scheduling mechanisms.
Thus, in the current Java RTS implementation this would be the "default" feasibility mechanism based on the PriorityScheduler.
Unfortunatelly I can not figure out the need of maintaining a feasibility set, since feasibility, as specified for the PriorityScheduler, is a simple asumption that we have "an adequatly fast machine to handle the periodic and sporadic load"?
I actually assumed that feasibility analysis performs real cost budgeting taking into account deadlines and so on, but it seems to be specified simply to make a negative statement always when aperiodic tasks are involved ?The RTSJ scheduling framework provides support for feasibility analysis by defining the admission control methods eg setXXXIfFeasible. However the RTSJ does not, and can not, mandate any non-trivial feasibility algorithm because in simple terms no such general algorithms exist. There are some static feasibility tests in the literature and you could apply those offline to your application (assuming you can find the values of all the "magic" numbers in such formulae - which is generally not the case). At present the RTSJ doesn't support even these simple feasibility tests because blocking-time is not recorded in the release parameters - something being addressed in RTSJ 1.1. In any case unless there is a pluggable framework for feasibility tests it would be a waste of time for VMs to implement them given they can (more) easily be done offline using other tools.
Only dynamic admission control is really of interest and as far as I am aware no such general dynamic admission control policies exist (anything you find in the literature is very context specific). So it is left up to an implementation as to whether they try and define dynamic admission control algorithms - and so far none have because they don't have one.
In "Getting More Flexible Scheduling in the RTSJ" Wellings and Zerzelidis propose some (more or less) "minor" extensions to the RTSJ API in order to enable hierarchical scheduling within the fixed priority framework.
Since Andy Wellings is a member of the RTSJ Technical Interpretation Committee, is there any attempt to evolve the specification in a similar direction as described above, in order to support more flexible scheduling mechanisms and feasibility analysis?If there is ever a RTSJ 2.0 then more sophisticated scheduling support is one of the items on the wishlist. But there's no guarantee there ever will be a RTSJ 2.0
David Holmes

Real Time Communication

HI Gurus,
Can any one tell me what is REAL TIME COMMUNICATION.
Also I request information / details on RTCIS.
Regards
Ajoy

Hi Ajoy,
1.1 Application Scenarios for Real Time Communications
There are two classes of applications: client and server. Client class applications have one real-time client per computer, such as the traditional instant messenger (IM) application. Server class applications typically act on behalf of multiple users or communicate with many hundreds of users simultaneously. Server class applications are often based around intelligent applications that interact with users. These applications can be divided into two categories: notification Apps that send information to a client and interactive Apps that accept and respond to a client. A third type of server class applications, Web-based clients, interacts with users through a Web server.
1.2 Notification Applications
Notification Apps are real-time applications that send information to multiple clients from a centralized server (see Figure 1). The one-way transmission means that clients cannot communicate directly with the notification App. Instead, clients must choose which events they wish to receive by using some other technique, such as a Web application.
One example of a notification App is an application that notifies all of the users of a particular e-mail server that the server is about to go offline. Another useful notification App would send alerts in cases of severe weather.
1.3 Interactive Apps
Interactive Apps are applications that allow multiple clients to communicate with a central server in real-time, as Figure 2 shows. They are different from notification bots in that interactive bots support two-way communications with a client. Using this approach, you can build an application that interacts with users in real-time. Within this scenario, there are two main sub-scenarios. The first provides a user with information and waits for the user to respond, such as an application that notifies users about changes in stock prices and then gives the user the option to buy or sell. The second waits for the user to request a session with the App and then responds to requests that the user supplies, such as a calendar application that allows a user to schedule meetings and other events while receiving reminders just prior to the meeting or event.
1.4 Web-Based Clients
Web-based clients provide the same basic functionality as the traditional IM client through a Web interface, thus allowing the widest possible audience to use the application, as Figure 3 illustrates. It also has the side effect of eliminating the need for a user to download local software, which reduces user concerns about the download containing a potential virus. These types of clients are useful to organizations that wish to provide a Web-based front end to their internal IM system. For example, a company might wish to use a Web-based IM client to connect customers with a support group. Doing so maximizes the number of customers that can connect with the support group.
Real Time Communications Data Flow
It's critical that organizations planning large deployments of real-time communications applications ensure that those applications can scale to meet the desired goals. The RTC Client API is very efficient for client class applications for which each client runs on its own computer. To build a scalable RTC Client API application that services multiple clients with a single computer, you need to ensure that the application is scalable when you design it.
The Real-time Communications (RTC) Client API is a set of COM interfaces and methods designed to create PC-PC, PC-phone, phone-phone audio/video calls, or text-only Instant Messaging (IM) sessions over the Internet. Application sharing and whiteboard (An application that displays a window for two users to exchange information) can also be added to PC-PC sessions. Presence information is used to track the location of buddies (or contacts) for communication purposes. This information is available through the RTC Client API on a SIP registrar server.
The RTC Client API:
1.Supports multiparty phone-phone calls
2.Uses SIP-based signaling and presence communications
3.Integrates with the Microsoft Office RTC proxy and registrar server
4.Supports provisioning with ITSPs or third-party corporate-deployed servers
5.Integrates signals over IP and PSTN networks
I hope this will be useful for you.
Thanks,
Swamy Kunche

VI on LabVIEW real-time is loading and running a DLL which has been deleted from the machine

OK, this is a weird one (at least, to me :-) )
I have a small real-time demo application VI that I am writing, using some new VIs I just created. My new VIs are wrapper functions for a DLL, using Call Library Function Nodes.
In the process of debugging, I decided to delete the DLL and run without it, to confirm that I am actually loading and using the DLL (since it seemed to have stopped doing something it had successfully done just a little while earlier).
The VIs that use that DLL still run, and at least some of them actually do what they are supposed to do. But the DLL does not exist on the real time machine! Not only did I delete it, reboot the machine, and check that it was gone, but through my ftp program I searched the whole hard drive for that DLL and did not find it (the search succeeded in finding a different DLL which did exist on the system, so the search-via-ftp is working).
How could this happen? What am I missing? Could this somehow be the result of a corrupted VI or is there some more logical explanation for the phenomenon?
Thank you.
Batya

Nathan is right at least for the Phrlap ETS based RT systems. For VxWorks you have to (or maybe used to have) to download the shared library to the controller before you could deploy an executable that makes use of them. For Pharlap ETS systems if you deploy a VI library dynamically to a machine it will download everything including shared libraries to the the RT target memory and run it from there. Only if you create an executabel and "install" it to the target and run it from there will it use whatever VIs are in the executable and also use the shared libraries that have been installed onto that system (at least for Pharlap ETS RT targets. As mentioned before for VxWorks targets, the deploy process even for executable installation did for some reasons not take care about moving the according *.out library to the target together with the rtexe).
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Hi, I would like to ask about how to capture data from real time loop.

Hi,
Here is some overvier of my project:
I have done real time control using labview 9.0. I used PID controller.
In order to optimise this controller, I need to capture data from my sensor(input) and actuator (output).
1. For example while real time control is running. I need to capture 1000 sample data (sensor(input) and actuator (output)).
Then I will used these data for PID optimisation on the other loop without intefere my real time loop.
2. When PID optimisation is completed, I will sent its PID parameter to real time control loop.
3. These operation is done in parallel.
Anybody can help me to solve these. Your idea may solve my problem.
TQ

Typically you will have to use RT FIFO or Queue communication to avoid any impact to your time critical loop.
Best regards
Christian

Hypervisor: Create Standalone Real-Time Application (Error at deploying: File not found)

Hello,
I am using Hypservisor. With "Build Specifications" in the project explore I want to create a standalone real-time application.
In my first try I only want to print some texts onto the real-time console (HyperTerminal) using the function "RT Debug String.vi". I built the real-time application successfully and got the rtexe-file locally on the windows system. But as I tried to deploy the application to the target system, I got the error: "File not found". Please check the attached file "error.txt" for details.
I don't understand which file is not found. Or I used "\" as path separators. Is it wrong? I'd appreciate if you'd have any idea of the problem. Thank you very much.
Regards,
Scarletice
Solved!
Go to Solution.
Attachments:
ERROR.txt ‏1 KB
builds.zip ‏153 KB

Hello Casey,
Thank you very much for your reply and your interest in our project. We are using Real-Time Hypervisor for the setup of our test stand. We use the Windows system to show the GUI and the Real-Time system for the real-time machine control and online data storage. We use shared variables and shared memory for the data exchange between the two systems.
The system works generally quite fine now. But we still have to face new problems at each step forwards. I'm sure, I'll have more questions. I'd appreciate your advices. Thanks sincerely.
Best regards,
Scarletice

Real-Time Application doesn't run; source code works fine

The short version is I'm programming a cRIO and apparently the RT code isn't running after being deployed and I can't figure out why. This is further complicated that I'm doing all this remotely and I don't have direct access to the unit since I'm 500 miles away. I'm working through a couple of other guys who know some LabVIEW, but neither works at the site so they have to explicitely travel out there every time I have a bright idea.
I was out there a few weeks ago. During this time I created a simple cRIO code, since I'm new to cRIO, that allowed the user to move a control and change a graph. It worked fine, but I should note it did not have an FPGA component. After that I worked on the real code, which reads some sensors, displays the results on a UI and logs the results. This did have FPGA. I used it in the LabVIEW environment and it worked fine, but I ran out of time before I could complete a release version and deploy the RT as a compiled application. I sent them the release version later, my contact deployed it but got network stream errors when running the UI.
After hours of looking at network problems and sending over debug versions, I tried creating a log on the RT level so I could see what was going on. The log doesn't even open, even if it's the first command in the code. I pored through the forums and found http://forums.ni.com/t5/LabVIEW/cRIO-Troubleshooting-creation-and-deployment-of-startup/td-p/1956475... which took me in a new direction.
I had my contact use the RT debug console and when he pulls up the RT front panel, it shows a broken run arrow. He clicks it and nothing happens -- no running, no bug list. If he pulls up the bug list manually, it's empty. Again the RT works fine if you run it through LabVIEW and not as a compiled real-time application. He also noticed that the Open FPGA VI was grayed out on the block diagram. No other icons are.
So the problem appears to be that the compiled RT application is getting some kind of error but not telling me what it is, and it seems to be related to opening the FPGA. I've recompiled the FPGA and RT. I've had him recompile the RT himself, but not the FPGA because it would take hours. He's downloading everything correctly to the cRIO. The RT is set to run automatically. He's rebooting the cRIO every time he deploys the RT. They have LabVIEW on a computer there but it doesn't have the right drivers to run the code from the LV environment. I'm resisting having them install the dirvers because downloading big files is complicated there due to security restrictions and a lousy network connection at a remote site. Besides that doesn't solve the problem of the RT executable not running the same as the source code, which according to the thread above appears to be a thing.
The latest thing I'm trying is that I sent him instructions for how to build a source distribution from the project I sent and try deploying that to the cRIO. Even if that works I'm not sure that's an acceptable solution because I assume running the VI rather than the EXE is slower, and they need speed on this project.
I simply have no idea where to go from here. I probably need to get direct acess to the cRIO and I might be able to convince them to ship it to me so I can figure this out, but I'm not sure where I'd even start other than the standard voodoo debugging of "try stuff at random until something works". I'm open to suggestions if anyone has managed to solve this before.
Code snippet of the first part of the project is attached, though I'm not sure how much good it will do. I'm really stumped and the client is getting frustrated with how much of the budget is going to fix this.
Solved!
Go to Solution.
Attachments:
RTMainSnippet.png ‏623 KB

Have you checked the cRIO error log? Usually I'd access it through the LabVIEW project (right-click on the target, don't remember the exact menu options and I don't have the RT toolkit installed on this machine to check), but it must be stored somewhere on the cRIO as well, although I don't know if it's in a human-readable format.
Which cRIO are you using? What exactly do you mean by "debug console"? (This may be related to the cRIO - the newer ones have video out, although I don't know if that's what you're referring to.) With a broken run arrow, you won't get an error list unless you're running in the development environment.
Have you confirmed that the software installed on the cRIO matches the version you're using for development, including patch level? Get someone to connect to the cRIO with Measurement and Automation Explorer, and get a list of the software installed on the cRIO.
Sounds like the ability to connect with a remote debugger would be helpful here, if you can get the right drivers installed on the machine with LabVIEW that's connected to the cRIO. Make sure all driver versions match what you're using. Any chance you could then do a remote desktop connection from your work site to the remote LabVIEW machine?

Build real-time application with Compact RIO

Good afternoon,
I am currently trying to run a VI on compact RIO and would like to control it through remote front panel. I followed steps on this link http://digital.ni.com/public.nsf/allkb/AB6C6841486E84EA862576C8005A0C26 and successfully done everything with a simple example.
However when I moved on and did the same thing to a more complicated VI (my purpose is to make this VI work), everything was fine until I reboot the compact RIO. After a few seconds connection lost between the host computer and cRIO, and I had to shut it down and delete the startup file (with extension .rtexe).
I am not sure what happened since everthing works fine with simple VI but not the complicated one. It could because the second VI has many sub VIs as well as objective functions loaded in it, it could also because the VI takes too much memories of the CRIO and stop it from connecting to the host computer.
If anyone have any ideas of how to make it work please let me know.
Thanks very much
Carl

Hello zzzfreedom,
There are a number of potential issues I can see with the VI you're trying to deploy as a startup executable. How do you intend to interact with this VI? Are you running the front panel as a remote panel or connecting to the VI using debug tools? A few points:
- Your VI will run immediately when the RIO boots unless you're using debugging tools to prevent this from happening, keep that in mind. It looks like you've accounted for this and required an initialize or network trigger of some sort for some of your loops, but the AI loop will start quickly and appears that it may require user input.
- You have several "user prompt" style express VIs. These will not work (or will not work as expected) on a standalone RT target. There is usually no front panel to interact with!
- Like dialogs, event structures watching for user interaction probably aren't going to do what you want.
- You are writing quite a bit of data to the VI's front panel, and there is at least one chart indicator. Again, how will the user interact with this VI? It looks like you need a host VI that will run on a machine the user will interact with.
- You're using quite a few local variables. It looks like you've taken a lot of care to protect against race conditions, but this causes a lot of data copies and tends to be error prone.
- I've not analyzed all cases, but it looks like you have a number of places where the execution of a timed loop may be blocked under certain conditions. This will likely rail the CPU due to the much higher priority of the timed loops.
- What will happen if you lose connection with the server in your TCP command loop? it doesn't look like there is any way for the user to reconnect without restarting the RIO.
If you do intend to run this as a remotely accessible VI on your RT target, another point to note is that when running from the development environment, the front panel of your VI executes on the host machine. Once you deploy it as a remote front panel or debuggable RTEXE, everything is hosted on the RIO, and this has the potential to bog things down quickly.
Here are a few references I think you might find helpful:
LabVIEW Help: Real-Time Operating Systems - see considerations for Express VIs and Front Panel interaction
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_osnotes/
LabVIEW Help: Real-Time Module on VxWorks Targets - see unsupported features
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_vxworks/
NI LabVIEW for CompactRIO Developer's Guide -lots of good general information on architecting RT applications, network communication and hosts, etc. It looks like you're using the RIO Scan Engine, so the FPGA portion might not be relevant at this time.
http://www.ni.com/compactriodevguide/
Best Regards,
Tom L.

Embedded LV 8.0 Real-Time application on cFP-2120

Hi!
I'm working on a project which involves programming of a real-time application running on a cFP-2120. The purpose of the application is to control the motion over 7 test-objects with a servomotor. Test-objects have 3 sensors each. Remote control of the application is necessary. The program should have a GUI which shows graphics of sensordata and buttons to open other VIs like set-up, details, logging etc.
Could i just build an application like it was meant to run on a pc, deploy it to the cFP-2120 and use Connect to Remote Panel ?
Or
Should I build separate VIs;
-the program which always runs on the cFP-2120 and
-the User Interface which is runned on a computer now and then which gets value from Network-Published shared Variables
I need some tips here

I would definitely go for the second option, esp. if you want to have this program for a longer time.
It's much easier to write a good GUI on the PC without the limitations of a real time OS. There you have to keep too many things in mind (esp. no dynamic arrays, performance issues due to GUI programming, not too many sub VIs)... So write a quite minimal control software for FP and do all the interface stuff on the PC. Then you can easily log all the data into a database (if you have the DSC Engine) as well.
Cheers,
Carsten

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

Dynamic Update in real time with slider control

We have requirements to display complex data in a graphical format. So far this has gone well by leveraging ADF and DVT components (dvt:Map, dvt:gauge, dvt:bargraph, af:tables, af:inputNumberSlider, etc.); however, we recently have been asked to add real-time animation of these controls over time. In brief, the user requires the ability to control the on-screen visualization of data by sliding the control on an af:inputNumberSlider (or equivalent) that represents a multi-month time scale. While sliding this control, the user expects to see the data visualization controls dynamically update in real time, keeping up with the rate at which the user moves the slider control. Think of this like a flip book animation where the slider controls the page the user is looking at and they can flip through the pages forwards or backwards at any desired speed. The time slider increments are one hour.
Our current application architecture:
Oracle ADF Fusion Web Application (v 11.1.1.5)
EJB 3.0
Eclipselink
Oracle 11g
Any kind of help is highly appreciated.
Thanks,
Mehabub

Hi,
the af:inputNumberSlider does not provide this functionality. Your alternative is a custom component (or any component that raises a client JS event) and call an af:serverListener in a custom event to send the notification to the server.
Frank

How to update the HTML file so that we can Control our process in real time

After installing following three steps as per the lookout 4 online help I am unable to Monitor and control the Process in HTML format, which was exported manually in lookout server.
1) Creating a Web Client Page in Lookout
2) Download a Lookout Web Client
3) Setting Up Own Web Server
My browser shows only the instance, which I have uploaded manually without any update
Problem: How to automatically update/refresh the HTML file so that we can Monitor/Control our process in real time/bi-directional mode.

Hi,
It seems like your process is not updating. When you create a Web Client, it uses ActiveX which lets you control the Lookout process fully. Make sure that you run the process. You can do this by pressing CTRL+Spacebar which puts it in Run-mode. Perhaps then you may see your graphs, etc updating.
Also, please refer to page 11-1 of the Users Manual linked below:
http://www.ni.com/pdf/manuals/322390a.pdf
What kind of Web Server are you using? Make sure all the settings in it are done properly. If you have LabVIEW, you can use the LabVIEW Web Server.
Hope this information is helpful. Please let us know if you have any further questions.
Regards,
A Saha
Applications Engineer
National Instruments
Anu Saha
Academic Product Marketing Engineer
National Instruments

Real time control application

Similar Messages

Maybe you are looking for