Did somebody already run the Write File to Citadel Example with success ? This exemple aims at Importing Spreadsheet Data to the Citadel Database, and is given in the NI developer Zone --> Development Library --> Labview --> DSC --> Data Logging.
I can run the exemple as described without any visible problem. But when I look at Citadel (through MAX), I can't find any trace of the data I imported (sine_wave_one for instance). According to the SampleSpreadsheet.csv I used for import, I should find a trace in the database around the 21st of march 2002... But I found nothing.
You might want to double check two things. Double click on the engine icon in the task bar tray to open the engine manager window. Make sure the Log data is on and CHECK the show events. In the event window, make sure you are not getting any errors.
A common solution to this error is increasing the size of your input buffer. You can accomplish this by going to the Tag Configuration Editor. Click on the Configure pulldown menu and select Engine. This action will open the Engine Configuration window. Choose the Server tab. On this tab you will find an option for the Input Queue Size. The default is 2,000 elements. Try changing this number to 10,000 or 20,000. This change normally alleviates the error that you are getting.
I went ahead and tried it and it was not working for me either. There is one obvious bug and at least one non-obvious bug. The obvious problem is the File_location tag size. It is 80 characters. That's not too much. For example: C:\Program Files\National Instruments\LabVIEW 6.1\examples\Spreadsheet file.csv has 79 characters and barely makes it. You can view the tag value in Tag Monitor to check if it is not truncated. I recommend to increase the size to 260 (Microsoft MAX_PATH size).
The bad news is that the example still does not work for me. I am also getting Input Queue Overflow. Give me some time and I'll see if I can figure it out. I am pretty busy for the next two days. Hopefully Friday.
I found what the problem was in my case. It is likely that it is the same issue on your computer.
The example expects the configuration file (Write to Citadel.cfg) in the LabVIEW folder. I had placed it in the same folder where I unzipped the example (where my VIs where). That did not work.
When you run the example, it creates the config file in the LV folder if it does not exist, but it is going to be empty. Check the presents of the file and replace it with the copy from the example web site.
I am not sure how savvy LabVIEW programmer you are, but if you feel confident you can go ahead and try to debug the code.
The VI based servers are running on the background. You can however make the front panel visible during the execution - not the diagram. The debugging means you have to create a few indicators on the panel that will show what is going on on the diagram. These are the steps the enable the front panel during the execution: 1) Open the Write File to Citadel Server VI 2) File>>VI properties; select Window Appearance 3) Click Customize and check the Show FP when called and Show FP when loaded 4) Save it and relaunch the engine!
When you start the engine again, you should get th e server front panel. Once you'll have some indicators on the FP you'll be able to learn more about what is going on in the VI.
I have noticed that sometimes the example pops up with a File dialog box. I found out this was related to a race condition in the example. I am not sure if that's what you see.
Let me know.
Also if the example executes you should see the tag values changing - for example the string tags starts with "Row 0", "Row 1" ...
