Real-time feedback system

My experimental setup (labview is being used to drive it) is as follows:
1. Give the physical system a random move -> 2. Acquire data using PXI-5124 digitizer -> 3. Perform some calculation on the data acquired -> 4. Accept/ reject the move based on the calculation
and go to step one. 
How do I know how much time the program took to acquire data and perform the calculation (step 2 and 3). so that I can set the proper loop timing. I'm using "Flat Sequence Structure" for each step/ sub-step.
Thanks

If you want precise information about timing, you need to do your own benchmarks. Go to Help->Find Examples. Search for "benchmark" and you should find "Benchmark Project.lvproj". It shows how to use RT Utilities pallete to make benchmarks on real time target.

Similar Messages

  • Who Makes National Instruments Real-Time Operating System?

    My simple question for reference is Who Makes National Instruments Real-Time Operating System?  I just need to know the company and if you happen to have a link to their website that would also be great!   Thanks.
    Michael B

    On Oct 8, 12:10 pm, tbob <[email protected]> wrote:
    > NI does not own a real time OS.&nbsp; They make Labview Real Time, but the OS is made and owned by other companies.&nbsp; There are several to choose from.&nbsp; If you Google "RTOS" you will see several hits.&nbsp; One of them is Express Logic's RTOS.&nbsp; <a href="http://www.rtos.com" target="_blank">www.rtos.com</a>
    > &nbsp;
    When you try to determine whether Real-Time RTX can coexist with
    Windows, National Instruments directs you to a Citrix Web Page for
    evaluation software. At Citrix's Web Page I couldn't find any
    evaluation software but the page mentions ETS And RTX versions of the
    Real-Time software. I also concluded Phar Lap was the original
    developer of the Real Time software. It appears Phar Lap was owed by
    Venturcom and then Citrix bought Venturcom. Phar Lap dates back to the
    19 eighties when PCs were first becoming popular
    Here is the link that led to these comments.
    http://digital.ni.com/public.nsf/allkb/03BC0810E60CE93286256E7D007B61F5
    Howard

  • About using the labview in real time DAQ system

    Hi All
        I designed a DAQ board based on PCI bus by myself, using labview for my graphic display application software. DAQ board generate PCI interrupt every 20us(50kHz). then PC respond it and read the data from DAQ board, that means the sampling frquency is 50kHz. the DAQ driver is generated by NI-VISA. it goes well after installing. I am sure that VISA detecte the PCI interrupt and triger a PCI interrupt event every 50kHz.
        But I face a problem, labview can not respond reading data in a real time. so does labview can not be used in the real time system? or is there something wrong with other else? if that is true, how can I solve it?
        by the way, I read the VISA help document. found there are two ways to respond PCI interrupt. one is callback, the other is queuing. I use the second way. I beg your help.

    I think you can use buffered signals with some changes on your circuit, with real time can be hard to implement with not supported hardware.
    Best regards

  • How to stop a thread in java 5 for a real-time system??

    Hi,
    In Java 5, thread.stop is deprecated. We need to modify some variable to indicate that the target thread should stop running. "The target thread should check this variable regularly........"
    We are currently developing a simple real-time operating system using the basic features of java. It is running on top of SunSPOT (JAVA5). My question is I need to stop a thread in a scheduler loop of a real-time operating system. We cannot check it regularly. Otherwise it is not a real-time operating system.Is there anyway else to do this?
    Thanks,
    Qing

    That's rather hard to answer. You say you are writing in Java, but you're writing an OS. BUt what's executing the Java - you need a VM of some form. Is that a real-time or non-real-time VM? How it does things ultimately controls how effectively you can do what you are trying to do.
    The simple answer is that Thread.stop() is deprecated and that it will not stop a thread in all situations anyway - eg trying to acquire a monitor lock. But all Thread.stop does is make an exception pending on the thread, and as the thread executes it polls to see if there is an exception pending. When this happens depends on the VM: it might be after every bytecode; it might be when the thread transitions states (eg thread-in-java, thread-in-vm, thread-in-native) - it all depends. But it is polling - just the same as checking that variable - it's just implicit in the VM rather than explicitly in your code.**
    The RTSJ adds a new form of asynchronous termination requests through the AsynchronouslyInterruptedException (AIE). But it only affects code that explicitly declares that it expects AIE to occur, and there are also deferred sections where the AIE will remain pending. Writing code that can handle AIE is very difficult because the normal Java rules are "bent" and finally blocks do not get executed inside AIE-enabled code.
    So as I said this is very hard to answer, it really depends what exactly you are running on and what you are trying to achieve.
    ** Note: some people used bytecode rewriting tools to add this kind of polling as a post-processing step. Perhaps that is something you might be able to do too.
    David Holmes

  • How do you interface a Renishaw laser real-time with NI DAQ?

    I understand that it is possible to acquire "real time" feedback from a Rensishaw Laser while measuring linear position, with the following modifiers applied.
    *The standard output is a digitized value to a proprietary (Renishaw) data acquisition (DAQ) card.
    *Renishaw lasers have a quadrature output facility on the back of the laser head. This permits capture of the �raw� interferometry signal. This raw signal is not compensated for environmental factors such as temperature, air pressure, humidity, etc.
    *The standard system integrates signals from an environmental unit for air temperature, pressure, and humidity, as well as signals from up to three material probes. Acquisition and pro
    cessing of these or equivalent signals would have to be considered to provide data for environmental compensation calculations (Edlen equation). This is mandatory in order to obtain accurate distance and velocity readings.
    *The quadrature output can communicate with other cards. (NI DAQ?)
    Specifics with regard to Labview software and required DAQ to read real time Laser output would be very much appreciated.

    You can use a counter available on the E-series MIO DAQ boards or the 660x counter boards. You can measure the position, frequency, and period of the output from a quadrature encoder. Examples on how to measure signals from a quadrature encoder for LabVIEW can be found on the web at ww.ni.com/support under the technical resource section search under the example programs section.
    You may also want to contact Renishaw to see if they have drivers available for LabVIEW and their DAQ equipment.

  • 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

  • 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.

  • Real-time database or non real-time database

    I know the scheduling mechanism in Oracle database is somewhat like the Linux OS which is not real-time. Does Oracle provide real-time database which has some real-time scheduling guaranteeing each user transaction to meet with a deadline ? Thx a lot.

    The Berkley DB that Oracle owns has been ported to QNX which is a real-time operating system.
    http://www.oracle.com/technology/documentation/berkeley-db/db/ref/build_unix/qnx.html
    Why, out of curiosity, are you looking into Oracle for a real-time system? That implies that you're running a real-time operating system on your servers, which is certainly unusual. I've heard of some ports of 9i to real-time operating systems, but that would certainly be unusual.
    Justin

  • 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

  • API's supported by Real-Time?

    I am working with a third-party vendor to get a driver working in LabVIEW Real-Time 8.  Can anyone send me a comprehensive list of the supported API's so I can forward on?  I know that the LabVIEW Real-Time Operating System only supports a subset of the Win32 API's but I don't know which ones.  Thanks. - Jerald

    KJ_Vandy wrote:
    For size reduction, LabVIEW Real-Time does not support all of the APIs listing from Ardence ETS.    To know what functionality is actually supported with a particular version of LabVIEW RT, NI provides a utility that will verify a DLL.
    http://digital.ni.com/public.nsf/allkb/0BF52E6FAC0​BF9C286256EDB00015230
    And in case you use any of the newer CompactRIO/Fielpoint targets running VxWorks you can forget any win32 API support. Only standard C runtime library support is available there.
    Rolf Kalbermatter
    Message Edited by rolfk on 04-09-2008 08:17 PM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • I am trying to translate the labview program to a real time labview programming....i wan to know what te the main isse that i need to focus on

    currently i am doing a lift monitoring system which made use of labview. Due to time constraint, i have decided to use the real time labview program. However i have no prior experience on the real time programmng, can i be enlighten on the main issue and what are the thing i ned to look out for. is thre any documentation that i can use?

    Derek,
    Programming for LabVIEW Real-Time is very similar to programming for LabVIEW for Windows. Many VIs do not need to be changed in order to run in LabVIEW Real-Time RT Engines. However, here are some issues to consider:
    1) Drivers
    2) File I/O
    3) Dialog Boxes
    4) Shared resources
    1) Drivers. If you application was written in LabVIEW for Windows, and then ported to run on an RT Engine on RT Series Hardware, you need to be sure that the drivers you are using are supported on your platform. See KB 28G97MZ8: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/aad11f924e5b5fd086256a310053a094?OpenDocument
    2) File I/O: If you are running your programs on an RT Series DAQ Device, it has no storage device, so file I/O operations will crash. See KB 26FBO0KN:
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/3c35f5e85476579d862569f50067462e?OpenDocument
    File I/O on RT PXI Controllers is supported in 8.3 filename format (no spaces in the filename allowed).
    3) When your application is deployed, (Operate>Download Application, Operate>Run, then File>Exit without closing RT Engine VIs), you VIs continue to run. However, the RT Engine runs headless with no keyboard, monitor (limited information displayed), or mouse, so any user interaction previously required by your VIs, such as Dialog boxes, will hang or crash your program. For user interaction with a deployed application, communicate to the Host PC using shared memory, VI Server, TCP/IP, DataSocket, or UDP. See ~\labview\examples\rt\rt communication.llb for examples.
    4) Even though your programs now run in a real-time operating system, you need to follow good real-time programming techniques. These include: using multithreading with critical tasks set to time critical priority. One time critical VI with no parallel loops. Avoid accessing or using shared resources in time crital VI (shared resources cause jitter). Shared resources include the memory manager (preallocate arrays used in time critical loops), global variables for interthread communcation (use RT Queues). For more information, visit the LabVIEW Real-Time Resource Library in the Developer Zone: http://zone.ni.com/devzone/devzone.nsf/webproducts/c25f8c664230613a862567df006abb06?opendocument

  • NI LabVIEW Real-Time for Desktop PCs compatibility!

    Hello,
    I'm pretending to acquire the NI LabVIEW Real-Time Deployment License for Desktop PCs. But before that, I need to be sure that this will work with other boards (not from NI).  
    Currently, I still don´t have all the project details. But there's a possibility of one board be from other supplier. 
    Can anyone tell me this, please. It's very urgent.
    Best regards,
    Paulo Carmo

    Hi Paulo,
    I guess that you will be disappointed but the response is clearly no.
    When you boot a Desktop PC as RT target, it loads with the basic real-time operating system (including drivers for ethernet, for harddrive, memory....). When you want to add drivers on this embedded system, it will be only possible to add National Instruments drivers such as DAQmx, DAQ, VISA ... The possibility to add others drivers (from others providers) is not supported.
    Hope it will help you,
    Regards
    David D. - Application Engineer - NI France

  • Error -1074384569; NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your database to the real-time system.

    Hello
    I have a VeriStand-Project (VSP) created with my Laptop-Host (LTH) which works with my PXI, while
    deploying it from my LTH. Then I have installed the whole NI enviroment for PXI and VeriStand use on a
    industrial PC (iPC). I have tried to deploy my VSP from the iPC to the PXI but the following error
    message arose on my iPC:
    The VeriStand Gateway encountered an error while deploying the System Definition file.
    Details: Error -1074384569 occurred at Project Window.lvlibroject Window.vi >> Project
    Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
    Possible reason(s):
    NI-XNET:  (Hex 0xBFF63147) The database information on the real-time system has been created with an
    older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your
    database to the real-time system. ========================= NI VeriStand:  NI VeriStand
    Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI
    VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize
    Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * • Unloading System
    Definition file... • Connection with target Controller has been lost.
    The software versions of the NI products (MAX/My System/Software) between my LTH and the iPC are
    almost the same. The only differences are:
    1. LabView Run-Time 2009 SP1 (64-bit); is installed on LTH but missing on iPC. The iPC has a 32-bit system.
    2. LabView Run-Time 2012 f3; is installed on LTH but missing on iPC.
    3. NI-DAQmx ADE Support 9.3.5; something strage on the LTH, because normally I am using NI-DAQmx 9.5.5 and all other DAQmx products on my LTH are 9.5.5. That means NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5.. On the iPC side all three products are 9.5.5.. That means NI-DAQmx ADE Support 9.5.5, NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5..
    4. Traditional NI-DAQ 7.4.4; The iPC has this SW installed. On the LTH this SW is missing.
    In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
    1. LabVIEW Real-Time 11.0.1
    2. NI-488.2 RT 3.0.0
    3. NI_CAN 2.7.3
    Unfortunately the above stated problem still arose.
    What can I do to fix this problem?
    I found a hint on http://www.labviewforum.de/Thread-XNET-CAN-die-ersten-Gehversuche.
    There it is written to deploy the dbc file againt.
    If this is a good hint, so how do I deploy a dbc file?
    I would feel very pleased if somebody could help me! :-)
    Best regards
    Lukas Nowak

    Hi Lukas,
    I think the problem is caused by differenet drivers for the CAN communication.
    NI provides two driver for CAN: NI-CAN and NI-XNET.
    NI-CAN is the outdated driver which is not longer used by new hardware. NI replaced the NI-CAN driver with NI-XNET some years ago, which supports CAN, LIN and the FLEXRAY communication protocol.
    You wrote:
    In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
    3. NI_CAN 2.7.3
    NI CAN is the outdated driver. I think that you should try to install NI-XNET instead of NI-CAN on your PXI-System, to get rid of the error message.
    Regards, stephan

  • Help needed in getting real time system performance monitor

    Hi,
    I need a real time system performance monitor for my solaris.
    i am able to graph system usage graph on a daily/weely basis using the ksar grapher.
    In the same way i need to capture the system utilisation real time to be viewed on a webpage. Please let me know if there are any free tool/scripts capable of doing it.

    Hi,
    Process Chain Errors
    /people/mona.kapur/blog/2008/01/14/process-chain-errors
    Common Process chain errors
    For Data Load Errors check this blog:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Implementation issues
    Lifecycle Implementation
    http://help.sap.com/bp_biv170/documentation/SolutionScope_EN.doc
    http://help.sap.com/bp_biv235/BI_EN/documentation/BWProjectPlan_EN.mpp
    Hope this helps.
    Thanks,
    JituK

  • HT1553 What is the best system for a real time cloud back up of documents?  My MacBook crashed, and I lost 2 hours of writing and could not find a way to restore it.

    My MacBook Pro crashed while I was rewriting a book, lost more than an hour of work and could not find a way to restore it.  Did not have Time Machine set up, but it appears that Time Machine does not have Real Time back up and documents must be manually stored.
    I need an automatic, real time back up to keep this from happening - I'm not happy my MacBook has crashed twice now.   What is the best cloud system for Real Time backup?   Thanks to anyone who can help me, I'm not the most astutde computer guy... James

    One way would be to use Dropbox, or a similar sync service, and just keep your critical documents in the appropriate folder. Dropbox, at least, keeps a local copy of everything and syncs automatically to the cloud whenver a change is made. Dropbox is free for up to 2GB of data.
    There are also true backup services such as CrashPlan+:
    http://www.crashplan.com/consumer/crashplan-plus.html
    which provide automatic backups whenver a change is detected. It's not free, but usually such services aren't too expensive unless you need to back up a lot of data.
    Regards.

Maybe you are looking for