|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
cRIO File Writing Problem
My team is experiencing problems trying to write files to the cRIO. I have examined the threads on CD, and noticed you have to use the function "Priv_SetWriteFileAllowed(1);" to allow writing to the cRIO flash memory. I call this function in our program while including <WPILib.h> and I get the error that it is an undeclared function call.
I am wondering if I am possibly not including the correct header file for that call, or if I even need to call that anymore to access the memory. Thanks, -Ian McInerney Programmer, Team 2022 |
|
#2
|
||||
|
||||
|
Re: cRIO File Writing Problem
I believe that Pirv_SetWriteFileAllowed(1) applies to images (I read that somewhere). I have written a Log class that successfully writes to the cRIO without the use of that function:
http://gist.github.com/296373 Also, this thread might be of use to you: http://www.chiefdelphi.com/forums/sh...ad.php?t=79548 Last edited by davidalln : 09-03-2010 at 10:57. |
|
#3
|
|||
|
|||
|
Re: cRIO File Writing Problem
Upon further investigation of the image library files, I found that the prototype for that function was not in the headers anymore, so I had to add one.
This is what it looks like: IMAQ_FUNC int Priv_SetWriteFileAllowed(UINT32 enable); Thanks for all your help. -Ian McInerney Programmer, Team 2022 |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Team 3132 - Sample code for writing to a file on the cRIO | SteveGarward | C/C++ | 0 | 05-02-2010 07:26 |
| Data File Writing ... cRIO vs. Driver Station | Ziaholic | NI LabVIEW | 3 | 31-01-2010 15:20 |
| Writing to DriverStation cRio screen | alexjplant | NI LabVIEW | 2 | 17-01-2009 10:59 |
| Reading binary data from a file and writing it in VB | complete | Programming | 1 | 02-01-2006 21:21 |
| Problem with reading and writing EEPROM | DKolberg | Programming | 4 | 16-03-2004 19:29 |