MAX support of SNTP for Real-time controllers

Hey everyone,
I have some PXI systems that allow me to enter a Time Server IP address directly into the MAX setup for the device but I have some other PXI chassis that don't. Does this have to do with the version of Real-time they are running? Can anyone tell me what version of RT and MAX started supporting Time Servers natively through MAX for real-time controllers?
Thanks,
Craig

Hi craige,
It looks like SNTP synchronization is not fully supported for PXI systems:
http://forums.ni.com/t5/LabVIEW/Configuring-PXI-8184-controller-to-synchronize-to-SNTP-server/td-p/1...
However, for CompactRIO, synchronization with SNTP servers began with LabVIEW Real-Time 8.6:
http://digital.ni.com/public.nsf/allkb/F2B057C72B537EA2862572D100646D43
The forum post I linked above does have some links to customer created examples relating to NTP and SNTP Time Servers.
Please note that those examples are both unsupported and a little bit on the older side.
Regards,
Joel I.
Applications Engineer
National Instruments

Similar Messages

Could u plz help me to find simple example for how to save data file in a spread sheet or any other way in the real time controller for Sbrio 9642 using memory or usb flash memory

Could u plz help me to find simple example for how to save data file in a spread sheet or any other way in the real time controller for Sbrio 9642 using memory or usb flash memory

Here are a few Links to a helpful Knowledge Base article and a White Paper that should help you out: http://digital.ni.com/public.nsf/allkb/BBCAD1AB08F1B6BB8625741F0082C2AF and http://www.ni.com/white-paper/10435/en/ . The methods for File IO in Real Time are the same for all of the Real Time Targets. The White Paper has best practices for the File IO and goes over how to do it.
Alex D
Applications Engineer
National Instruments

Video Output for PXI Embedded Real-Time Controller ?

I plan to purchase a PXI Embedded Real-Time Controller for security monitoring.
Is it possible to use the video output of a PXI Controller running RTOS to display messages from a LabVIEW RT application ? According to the documentation, it seems that the use of the video output is only possible for PXI Controllers running Windows XP.
Does it exist a specific application to do this with LabVIEW RT ?
Thanx.
H.L.
Solved!
Go to Solution.

Hi Yann,
The situation seems a bit confusing as in the link you've given above using the local monitor from a pxi labview rt system as the HMI without a pc attached, two messages (here and here) say that it is possible to display an image on the video output of a PXI RT controller using a function of the NI-IMAQ librarey (namely, the IMAQ RT Video Out VI) !
I have the NI-IMAQ library but no PXI controller to test if this solution should work or not
Does anyone have the answer ?
Thanx,
H.L.

How to identify the Stanadard Extractor will support for Real time Data

How to identify the Stanadard Extractor will support for Real time Data Acquisation . Enabled

Hi
In the ROOSOURCE table you can find the extract structures, go through all the fields of the extractor and if you find all of your equired fields exist ok else try to enhance for teh needed fields and go with user exit to populate the data for that fields'

FieldPoint real-time controller or Ethernet interface

Good Afternoon,
The first feature listed on the FP-2000 product page is:
Stand-alone embedded real-time controller or Ethernet interface for PC-based distributed I/O.
Has anybody successfully implented a FP-2000 as an Ethernet interface for PC-based distributed I/O? In other words, have the FP-2000 act like a FP-1600?
There are some discussion forum threads that dance around the subject but I have not found one that really answers it.
Thanks,
Ed
Solved!
Go to Solution.

Hi edlad,
After playing around with a FP-2010 for a while, I do believe that you need to install LabVIEW Real-Time on the controller in order for it to work, even if you are technically not using it because you are not running a VI/executable on the controller. As far as your issue with installing LabVIEW 8.5.1 on a FP-2000, that is troubling because there should not be an issue doing this at all. In fact, I have personally been able to install LabVIEW 8.5.1 on many FP-2000s. For that issue, I would suggest reformatting the FP-2000 from MAX and try again.
ThinkG: Regarding your question about using a cFP-2220 to communicate with Lookout, I am not sure because Lookout support is handled by our Shanghai branch via email only. However, I do know that you can use that second ethernet port to communicate with another FieldPoint network module (cFP-180x) using the FieldPoint drivers. Here are a couple good KnowledgeBase articles regarding that configuration. I hope they are helpful.
http://digital.ni.com/public.nsf/allkb/F602F6F1B243282686257495007695BB?OpenDocument
http://digital.ni.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

Pxi 1042 configuration for Real-Time

I have purchased
PXI-1042
controller 8187
one module for data capturing.
I want to configure the said pxi for Real-Time purposes,
so what steps should I follow?
thanks
Abbas
Solved!
Go to Solution.

The Real-Time Deployment License is different from the LabVIEW RT module.
When you purchase a PXI controller, part of what you are buying is the operating system that is installed on it. If you purchased the controller with Windows on it then you purchased the copy of Windows that came with it. Now that you want to put the real-time operating system on it, you need to purchase the license for it.
But that's all legal stuff.
And you are correct that there is a copy of the RTOS on the controller. But if your controller has its disk formatted as NTFS you will not be able to use it. The RTOS requires that the hard drive be FAT32.
If your controller is FAT32 then you can boot into BIOS (hit delete while booting), and select Real-Time in the Boot Configuration to make your controller boot into Real-Time.
If you controller is not FAT32 then you will need to format the controller first, using the disks I have previously mentioned.
Please let me know if you have any questions.
Justin Parker
National Instruments
Product Support Engineer

Shared Variables for Real-TIme Robot Control

I'm really stuck in my efforts to use LV real-time in my hardware control application. I have a 6-axis industrial robot arm that I must control programmatically from my PC. To do this I've developed a dynamic link library of functions for various robot control commands that I can call using Code Interface Nodes in LV (using 8.5). This has worked great, that is, until I tried to port parts of the application to a real-time controller. As it turns out, because the robot control dll is linked with and relies so heavily upon several Windows libraries, it is not compatible with use on a RT target, as verified by the the "DLL Checker" application I downloaded from the NI site. When the robot is not actually executing movements, I am constantly reading/writing analog and digital I/O from various sensors, etc.....
This seemed to suggest that I should simply segregate my robot commands from the I/O activities, using my host PC for the former, and my deterministic RT loop on the target machine for the latter. I set up a Robot Controller Server (RCS) vi running on my host PC that is continuously looking for (in a timed loop) a flag (a boolean) to initiate a robot movement command. Because several parameters are used to specify the robot movement, I created a custom control cluster (which includes the boolean variable) that I then used to make a Network Shared Variable that can be updated by either the RT target or the host PC running the RCS. I chose NOT to use buffering, and FIFO is not available with shared variables based on custom controls.
Here's sequence of events I'd like to accomplish:
1) on my host PC I deploy the RCS, which continuously pools a boolean variable in the control cluster that would indicate the robot should move. The shared variable cluster is initialized in the RBS and the timed loop begins.
2) I deploy the RT vi, which should set the boolean flag in the control cluster, then update the shared variable cluster.
3) an instance of the control cluster node in the RCS should update, thereby initiating a sequence of events in a case structure. (this happens on some occassions, but very few)
4) robot movement commands are executed, after which the boolean in the control cluster is set back to its original value.
5) the RT vi (which is polling in a loop) should see this latest change in the boolean as a loop stop condition and continue with the RT vi execution.
With the robot controller running in a timed loop, it occassionally "sees" and responds to a change of value in members of the shared variable cluster, but most times it does not. Furthermore, when the robot controller vi tries to trigger that the movement has completed by changing a boolean in the control cluster, the RT vi never sees it and does not respond.
1) Bad or inappropriate use of network shared variables?
2) a racing issue?
3) slow network?
4) should I buffer the control cluster?
5) a limitation of a custom control?
6) too many readers/writers?
7) should I change some control cluster nodes to relative, rather than absolute?
8) why can't I "compile" my RT vi into an executable?
Any help would be greatly appreciated. Unfortunately, I'm writing this from home and cannot attach vi files or pictures, but would be happy to do so at work tomorrow. I'm counting on the collective genius in the universe of LV users and veterans to save my bacon.....
David

Hi David,
I'm curious why you decided to build a CIN instead of developing the code in
LabVIEW. Is there some functionality that that LabVIEW couldn't
provide? Can you provide some more information about the LabVIEW
Real-Time target you're using? What type of IO are you using?
It is impossible to get LabVIEW Real-Time performance on a desktop PC running
an OS other than LabVIEW Real-Time. Even running a timed loop in LabVIEW
for Windows won't guarantee a jitter free application. Also, no TCP based
network communication can be deterministic. This means Network Shared
Variables are also not deterministic (they use a TCP for data transport) and I
advise against using them as a means to send time critical control data between
a Windows host and a LabVIEW Real-Time application.
In general, I would architect most LabVIEW-based control applications as
follows:
- Write all control logic and IO operations in LabVIEW Real-Time. The
LabVIEW Real-Time application would accept set points and/or commands from the
'host' (desktop PC). The Real-Time controller should be capable of
running independently or automatically shutting down safely if communication to
the PC is lost.
- Write a front-end user interface in LabVIEW that runs on the desktop
PC. Use Shared Variables with the RT-FIFO option enabled to send new set
points and/or commands to the LabVIEW Real-Time target.
Shared variable buffering and RT-FIFOs can be a little confusing. Granted
not all control applications are the same, but I generally recommend against
using buffering in control applications and in LabVIEW Real-Time applications
recommend using the RT-FIFO option. Here's why: Imagine you have a
Real-Time application with two timed loops. Time-loop 'A' calculates the
time critical control parameters that get written to hardware output in
timed-loop 'B'. Loop 'A' writes the outputs to a RT-FIFO enabled variable
with a RT-FIFO length of 50. Loop 'B' reads the outputs from the shared
variable, but for some reason, if loop 'B' gets behind then the shared variable
RT-FIFO will now contain several extra elements. Unless loop 'b' runs
extra fast to empty the RT-FIFO, loop 'B' will now start outputting values that
it should have output on previous cycles. The actual desired behavior is
that loop 'B' should output the most recent control settings, which means you
should turn off buffering and set the RT-FIFO length to 1.
There is also a clear distinction between buffering and the RT-FIFO
option. The RT-FIFO option is used to add a non-blocking layer between
network communication and time-critical code in LabVIEW Real-Time
applications. It also provides a safe mechanism to share data between two
loops running in a Real-Time application without introducing unnecessary
jitter. Network buffering is a feature that allows a client to receive
data change updates from the server even if the client is reading the variable
slower than the server is writing to it. In the example I presented above
you don't need to enable networking because the shared variable is used
entirely within the Real-Time application. However, it would be
appropriate to send control set points from a Windows PC to the Real-Time
application using network published shared variables with the RT-FIFO option
enabled. If it is critical that the Real-Time application executed all
commands in the sequence they were sent then you could enable an appropriate
buffer. If the control application only needs the latest set point
setting from the Windows host then you can safely disable network buffering
(but you should still enable the RT-FIFO option with a length of 1 element.)
Network buffering is especially good if the writer is 'bursty' and the reading
rate is relatively constant. In the robot application I can imagine buffering
would be useful if you wanted to send a sequence of timed movements to the
Real-Time controller using a cluster of timestamp and set point. In this
case, you may write the sequence values to the variable very quickly, but the
Real-Time controller would read the set points out as it proceeded through the movements.
The following document presents a good overview of shared variable
options: http://zone.ni.com/devzone/cda/tut/p/id/4679
-Nick
LabVIEW R&D
~~

Check if real-time controller is connected to a PC

I have some applications that run on a PC that call (deploy and run) a VI on a PXI target from the .lvproj. However, I share the PXI with others (who use the same method). If they are using it or if they forget to disconnect my application tries to deploy and run the VI but crashes because the real-time controller is already being used by another PC. I would like to create a VI that would check to see if the PXI is busy (somebody else is already connected to it) so that I can run this test before trying to deploy my applications and thus fail gracefully.
I don't think any of the VIs on the Real-Time palette are what I'm looking for, so I tried opening an application reference and looking at what info I could get via property nodes. It appears that there is some promise here, I might be able to make do with the "Remote Panel:Connections To Clients" or "NI Security:Nobody Logged In?", but neither of these can be accessed remotely. I glanced at the invoke node, but nothing popped out at me, and I'm not really trying to invoke anything anyway so that seems like the wrong path. I'm thinking that my only option is to create a standalone app that I can pre-deploy and that my PC applications will have to call that asynchronously via remote app ref? I've never done that before, but I would imagine it is possible. It just seems so complicated for such a simple operation...why isn't this built in to LV? Am I missing something?
I apologize if this is a duplicate thread; I tried searching for the topic but didn't feel like I found the right keywords.

You are correct -- I do not understand what you want to do. However, now that I have this out of the way, I'm going to "take a guess" and then say "I don't think you can do that".
I'm dealing with a 1 PC/1 PXI system, where the PC and PXI share a private network (so there's never a "worry" about multiple PXIs). However, I want to be able to "control" what code the PXI is running, as I have multiple PC codes that are paired with multiple PXI counterparts. This turns out to be a somewhat difficult task (that I haven't fully figured out), one "piece" of which is that I haven't figured out how to "know" what the PXI is running at any given time.
The solution that I'm drifting towards is to "force" the PXI to be in one of two known states (and to force the user to go and reboot the PXI if this proves to be false). One state is running a Startup routine that "listens" for a command from the PC to load and transfer control to a particular "Real-Time Target" routine, which when it exits reboots the PXI (hence returning it to the Startup state). The other "state" is executing the appropriate Real-Time Target routine. Under this assumption, I never need to ask if the PXI is running, because I've programmed it to always be running.
I do use Network Streams to communicate with the PXI, so one thing my Host routine could (and probably will)) do is to attempt to connect to the Network Stream Engine running on the PXI. If it times out, then it is safe to assume that the PXI is not in a proper state, so I can get the PC to reboot the PXI, forcing it into a known state.
Hope this is helpful. I'd be interested in your ideas and experiences.
Bob Schor

FI CO Integation: Document type for real-time integration with FI not there

Dear Gurus,
This is the error message that I got and I am looking for a solution could anyone help me please.
I was doing simultaneous costing and doing Product Cost Collector reports.[KKBC_PKO]
This is IDES 6.00 ehancement package 4,
How do I define a document type for real-time integration with FI?
Message no. FAGL_COFI003
"Diagnosis: For CO documents to be transferred into Financial Accounting in company code 1000, -the system requires a document type".
How do I go about with this, need steps to resolve this please
Thank you
Saleem

Hi,
1. Check which variant is assigned to your company code '1000' using this IMG path
IMG->Financial Acctg (New)->Financial actg global settings (New) ->Real-Time integration of Controlling with Financial Actg ->Assign variants for Real-time Integration to Company codes.
2. Check if document type is assigned to the variant assigned to your Company code in this path:
IMG->Financial Acctg (New)->Financial actg global settings (New) ->Real-Time integration of Controlling with Financial Actg -> Define Variants for Real-Time Integration.
Hope this helps.

"Waiting for real-time target (RT PXI target) to respond" error when the program waits interrupts

Hi there,
I have developed an application to detect interrupts generated by a electronic card and act in consequence. The program has been developed in labview but it calls a dll; that was created with labwindows. The dll is programmed to open the visa communication, enable events and install the interrupt handler and when an interrupt is detected, it reads the value of the different registers of the card and returns it to labview to visualize them.
The problem is that when the program waits for an interrupt, a prompt appears with the message "Waiting for real-time target (RT PXI target) to respond" and the only option I have is to click on the button to disconnect from the pxi or just wait. If I wait and I generate an interrupt, the prompt disappears and the application visualize the data like it was expected.
To wait for the interrupt the following code has been programmed in the function:
while (flag == 0)
Sleep (1000);
When an interrupt occurs, the value of flag changes to 1 and the function continue without any problem. I am not really sure, but probably here is the problem and probably this is not the best way to wait for an interrupt because the sleep function suspends the thread for the configured time, but at least the computing load in the PXI is between 0% and 1%. I was wondering if somebody knows how to wait for an interrupt without "lost" the communication with the PXI and if there is a better way to do it.
Any answer will be welcome and thanks for them,
Jaime
Solved!
Go to Solution.

Hello Naity,
First of all, in which thread runs the waiting process? Is it scheduled in another thread than the function setting the flag?
It scheduled in the same thread that I use to configure the communications and configure the card. Anyway, here is the pseudo code of the function interrupt that I programmed under labwindows,.
char* interrupt(void)
1. Open visa communications
2.Install handler interrupt --> status = viInstallHandler (instr, VI_EVENT_PXI_INTR, IntrHandler, VI_NULL); // the function IntrHandler will be called when an interrupt occurs
3. Enable event PXI interrupt
4. Wait
while (flag == 0)
Sleep (1000);
5. Visualize the data coming from the interrupt (registers and values measured with the card)
6. Uninstall handler interrupt
7. Close visa session
The interrupt handler function IntrHandler is called immediately when an interrupt occurs and the pseudo code is like this
ViStatus _VI_FUNCH IntrHandler(ViSession instr, ViEventType etype, ViEvent event, ViAddr userhandle)
1. Disable some functions of the card to avoid damages.
2. Read registers and put them in a buffer
3. Change the value of flag ---> flag = 1;
In labview, I call the function interrupt with a call library function node (see the capture attached) and the program reads and saves the data from returned from the function.
Secondly, I am not sure this method is the most elegant. You could for example register an event with the function and, insteand of setting a flag to 1, trigger the event and schedule it in another thread (if the function is thread safe). This could reduce your CPU Load even more and seem a bit cleaner to me.
I've never used events before in labwindows but I will try to do it in this way. But anyway, I suppose that I should; somehow, wait the event to occurs in labview while the waiting for the event is programmed inside the dll...and probably the same prompt that i am trying to avoid is going to appear again, because I am not returning the "control" to labview (I mean, labview executes the dll and waits for the event to occur. Then the execution of the labview program is stopped in the call library function node executing the dll)
Third point, which environment of development are you using?
I am working with LV 2010 sp1 and Labwindows cv 10.0.1 and with the real time module.
I did also another test, I divided the program in different functions, one to initialize the communication, another to wait until a interrupt has been detected and the other to obtain the data from the interrupt and close communications. With labview I call first with the call library function node the function to initialize, later I call inside a while loop the wait function like this
int waitAseconds (double seconds, short stop_waiting)
if(flag==1 || stop_waiting == 1)
flag = 1; //to detect the stop_waiting button
printf("flagAA =1 stop waiting = %d time = %d\n", stop_waiting, clock());
return flag;
else
SleepUS(seconds*1000000);
//a++;
printf("flag a= %d stop waiting = %d time = %d\n", flag, stop_waiting, clock());
return flag;
and when the program detects an interrupt, the function returns to labview the flag and stops the loop. Finally, it reads the values and close communications.
In this way, the prompt appears but after running the application for 10 or 20 minutes and also i checked that there is a time gap between the executions in the loop.
Thanks for your reply and your help,
Jaime
Attachments:
capture.png ‏40 KB

Defining Account Determination for Real-Time Integr

Dear all,
I haven't understood yet about Account determination for the real-time integration of Controlling (CO) with Financial Accounting (FI).
Please tell accounting process that use this account. And give me a detail example.
Thanks so much
Minhtb

Hello
This is the new feature in New GL accounting
During allocations in Controlling, most of the postings created do not affect Financial Accounting. These postings do not update any G/L account transaction figures; they are postings within Controlling. If, however, an allocation in Controlling leads to a change in the functional area or any other characteristic (such as Profit Center or Segment) that is relevant for evaluations in Financial Accounting, a shift occurs between the affected items in the profit and loss statement. For this reason, this information has to be transferred to Financial Accounting. This reconciliation between Controlling and Financial Accounting takes place by means of real-time integration.
As a result of real-time integration, all Controlling documents that are relevant for General Ledger Accounting are transferred from Controlling to General Ledger Accounting in real time. This means that Financial Accounting is always reconciled with Controlling.
A document is created in Financial Accounting for each posting in Controlling. This means that the detailed information contained in the CO documents is always available in reports in New General Ledger Accounting. This information can be sorted by the following, for example:
●     Functional area
●     Cost center
●     Internal order
Real-time integration replaces the reconciliation postings from the reconciliation ledger. Consequently, you do not need a reconciliation ledger.
If, however, you do not set the Reconciliation Ledger Active indicator in Customizing for the controlling area, you cannot use the reports belonging to report groups 5A* (5AA1-5AW1). You set this indicator in Customizing for Controlling under General Controlling ® Organization ® Maintain Controlling Area. The reconciliation ledger serves as the data source for reports belonging to the report groups 5A*. You find these reports in the SAP Easy Access menu under Accounting ® Controlling ® Cost Element Accounting ® Information System ® Reports for Cost and Revenue Element Accounting.
Replacement reports are available as follows:
●     You find the reports in the SAP Easy Access menu under Accounting ® Controlling ® Cost Element Accounting ® Information System ® Reports for Cost and Revenue Element Accounting (New).
●     You can create additional reports in report group 5A21. You can assign the report group to any drilldown report of New General Ledger Accounting using the report-report interface.
●     From the report Financial Statements Actual/Actual Comparison, you can call up the report Cost Elements: Breakdown by Company Code. You find the report Financial Statement: Actual/Actual Comparison in the SAP Easy Access menu under Accounting ® Financial Accounting ® General Ledger ® Information System ® General Ledger Reports (New) ® Balance Sheet/Profit and Loss Statement/Cash Flow ® General ® Actual/Actual Comparisons.
You can define account determination for each controlling area. You do this in Customizing for Financial Accounting (New) under Financial Accounting Global Settings (New) ® Ledgers ® Real-Time Integration of Controlling with Financial Accounting ® Account Determination for Real-Time Integration. In this way, you use the same account determination as for the reconciliation ledger (transaction OK17). You can then use the reconciliation ledger reports to compare FI balances with CO balances.
Prerequisites
If you use real-time integration in at least one company code, you need to have activated company code validation for the related controlling area. You do this in Customizing for Controlling under General Controlling ® Organization ® Maintain Controlling Area ® Activate Components/Control Indicators. Otherwise, the reconciliation between Financial Accounting and Controlling at company code level is not possible.
In Customizing for Financial Accounting (New), you have processed the IMG activities under Financial Accounting Global Settings (New) ® Ledgers ® Real-Time Integration of Controlling with Financial Accounting.
Activate real-time integration for all company codes between which you want to make CO-internal allocations.
In the IMG activity Define Variants for Real-Time Integration, do not select all CO line items for transfer. If the same line items are to be transferred as through the reconciliation posting from the reconciliation ledger, select the following line items:
●      Cross-Company Code
●      Cross-Business Area
●      Cross-Functional Area
●      Cross-Fund (if you use Public Sector Management)
●      Cross-Grant (if you use Public Sector Management)
Features
Value flows within Controlling that are relevant for General Ledger Accounting such as assessments, distributions, confirmations, and CO-internal settlements are transferred immediately. The FI documents are posted with the business transaction COFI. They contain the number of the CO document. This means that you can call up the CO document from the FI document, and vice versa.
Activities
If a document could not be transferred because the posting period was blocked in Financial Accounting or no account was found, for example, the document is included in a postprocessing worklist. You need to check this worklist regularly and process any documents in it. From the SAP Easy Access menu, choose Accounting ® Financial Accounting ® General Ledger ® Corrections ®Post CO Documents to FI.
Example
An internal order for business area 0001 is settled to a cost center of business area 0002. The document from this allocation is transferred in real time to Financial Accounting.
Reg
assign points if useful

How configure Define Account Determination for Real Time Integration

Hi All,
I am doing configure of new company just know about how do i configure for Define account determination for real time intergration. what is the use? Pleaes give me some clarity with example.
Thanks
Pankaj

Hi,
Please go through the below link:-
http://help.sap.com/saphelp_erp2004/helpdata/en/22/c2cf4031288131e10000000a1550b0/content.htm
Regards,
Gaurav

Is vision development module in labview 8.6. sufficient for real-time image acquisition and analysis using a webcam

Hi,
I'm new to labview and trying to develop an eye-tracker using labview 8.6. It has the vision development module and i was wondering if this was sufficient for real-time image acquisition and processing or would i be needing any other software tools.
Solved!
Go to Solution.

Hello, certainly it is possible and sufficient for real-time tracking!
About eye tracking - if you need an example, you can find the code here:
https://decibel.ni.com/content/blogs/kl3m3n/2013/10/08/real-time-face-and-eye-detection-in-labview-u...
The code uses OpenCV functionalities along with the LabView UI (and some other functions like overlay).
Hope this helps a bit.
Best regards,
K
https://decibel.ni.com/content/blogs/kl3m3n
"Kudos: Users may give one another Kudos on the forums for posts that they found particularly helpful or insightful."

Process speed necessary for real time livetype & Motion

Does anybody remember the minimum processor speed necessary to
run LIVETYPE and MOTION from WITHIN FCP5...not as seperate apps?
The online spec sheets indicate the speeds necessary for running as seperate apps,
but not for real time from withing FCP5...at least, not the ones I can find.
Thanks.

Where did you encounter the promise of real time in FCP?
Can't be done AFAIK.
Even if possible, you'd only get a few misleading preview frames.
We've got our new biga$$ Macs arriving in a few weeks. I'll let ya know if anything happens real time in FCP.
bogiesan

TCP/IP Connecting with Real Time Controller

I have a host running Labview on a windows XP and a realtime embedded controller on a pxi chassis that acts as the server. When the realtime is started it automatically goes into listen mode and listens for a connection from the host. The host opens a connection. After a valid connection is open the Real-Time side goes into a TCP_Read and the host can then send commands that the real time processes and sends to the FPGA on the pxi-chassis.
Now the problem I'm having is how to handle the case when a TCP connection is lost. I can have the TCP_Read on the real-time error on a time out and then go into a listen mode but this isn't very logical because then the host will have to reconnect each time a time out occurs. So if I make the TCP_Read timeout be infinite and if the connection is lost (let's say I unplug the ethernet cable and re-plug it back in) then I cannot recover from this and the Real-time will need to be re-booted.
I've tried to send the Real-time into listen mode if the error code is other than a timeout error (code 56) and have it go back to TCP_read mode if it is a timeout error. But if the connection is lost by means of a physical way (such as me pulling the ethernet wire and plugging it back in) then the Real-Time never sees that the connection is invalid. The host on the other hand can detect it bc it will get an error when it's trying to write?
So my is:
Is there any way to prevent an infinite loop that needs a reboot and at the same time prevent the host from reconnecting every time there is a timeout?

Hi SJeane,
I apologize for taking so long to respond, but I wanted to test this on my end. In doing so, I realized that using the RT Reboot Controller.vi after the connection is lost does not work because the message to reboot cannot be relayed to the target without communication! Thus, to solve this problem, we have to approach it a different way. You mentioned that you tried programmatically clearing errors, but did you try to reestablish connection after clearing the errors? I tested this on my end with a FieldPoint controller, and the attached VIs resumed operation even after unplugging/replugging the Ethernet cable (no reboot). Will this solution work for you?
Peter K.
National Instruments
Attachments:
Reestablish.zip ‏39 KB

MAX support of SNTP for Real-time controller​s

Similar Messages

Maybe you are looking for

MAX support of SNTP for Real-time controllers