08-04-2008 04:16 AM
08-04-2008 05:31 AM
Hi Roxy,
Are you trying to write to the CompactRIO locally? If so try writing to the C: drive instead of the 😧 drive, as that is the local storage for the cRIO.
Regards
Steve
08-04-2008 09:42 PM
hi ..
i have tried ur suggestion but it doesn't save the data yet . Do you have any other idea ? Thank you .
roxy
08-05-2008 05:09 AM
08-05-2008 08:43 AM
08-05-2008 11:00 AM
Hi Roxy,
To clarify, your cRIO controller (NI cRIO-9012) has 128MB of nonvolatile storage where it is able to store data. So when you use the "Write to Measurement File" VI within the "NI 9233 (Host)" VI it is automatically storing data to the memory within your cRIO controller.
This data can be viewed by
This should bring up the folder containing the data file. You should then be able to access the data file from there.
However, this is not an ideal way of storing data as the nonvolatile memory is used for storing the software as well as any information which may be stored during aquisition. By writing data files to this memory it could potentially fill up the controllers memory.
A much better method would be to create network communications between the "NI 9233 (Host)" and a Windows Host. This can be done by TCP, Shared Variables, UDP or VI server communication. This will allow you to write measurement files directly to your computers hard drive from the Windows host rather than the RT host. This will aid in keeping the memory free in the RT Target (cRIO).
An example of this can be found in the NI Example Finder within LabVIEW, under the headings Real-Time>>Network Communication as shown in the .jpeg file I have attached.
Hope this helps
Regards
Steve
08-06-2008 03:28 AM
08-06-2008 10:46 AM
Hi Roxy,
I've had a look at your example VIs as well as your project, and have written (and attached) two example VIs which should illustrate a solution to your query.
Hope they help
Regards
Steve
08-07-2008 04:27 AM
08-07-2008 09:20 AM
Hi Roxy,
I've written another simple example VI for you and attached a few .jpeg files which should help illustrate my following explanation.
Firstly, the scaling of the x-axis will depend on the timing implemented in the code of the VI, for example if there is no timing the units of the x-axis will be milliSeconds, in the example I've written I have stated for the code to execute every 100mS so each increment on the x-axis corresponds to 0.1second. To convert into seconds you will need to go into the chart's properties dialog box, go into the "Scaling" tab and then configure the "Multiplier" field based on the code timing (as shown in ChrtProp Dialog Box - Scales.JPG).
To format the chart to display time similar to a that of a stopwatch display you will have to go into the chart Properties dialog box and configure the scaling tab similar to that in ChrtProp Dialog Box - Display Format.JPG.
In order for the chart to display all the data from t=0 to finish just right-click on the x-axis and select "AutoScale X".
Hope this answers your questions
Regards
Steve