1-D Array of 3 elements to waveform(DBL) help needed

[MrSafe]

I figured something out..I have a software that does exactly what i want when it comes to screen capture i have another software that monitors a specific port of my likings. I am communicating with the analyzer via GPIB to USB. I noticed the capture has the command "MMEM" along with several other commands we can see in the drivers. I have attached the file so you can see what I see; I will update you with anything i find.

[smercurio_fc]

Ah, so that instrument is actually running NT. Well, that's different. More than likely you want to use the "NT Hardcopy Device" VI. The captured stream you provided doesn't show the full commands, so it's hard to say what they are. Did you use NI-SPY to get that communication stream? If so, you can increase the buffer size. It looks like it's using MMEM as the destination device, and then using the MMEM:COPY command to save it to the analyzer's hard drive. The "Memory Operations" VI will do the latter.

[MrSafe]

Yes NI SPY..could you guide me on how to increase the buffer size.

[smercurio_fc]

Select the Spy -> Options... menu item, and then set the settings as shown in attached screenshot.

[MrSafe]

Updated the log now we can see more of the commands in more detail

[smercurio_fc]

That's pretty much the same as before. The write commands have "..." so you only see the first few characters. Instead of exporting to a text file, just upload the NI Spy file. Do a File -> Save As, and upload that saved file.

[MrSafe]

Done

[smercurio_fc]

Darn, that's using a newer version of NI-Spy so I can't open it. Without the full commands, I'll have to go with guesswork. Here's what it looks like it's doing:

1. Setting the hardcopy device to use memory. This can be done with the "NT Hardcopy device" VI.
2. Naming the file in memory. This can be done with the "Memory Operations" VI, using "File to be printed or plotted" for the "Memory Operation" selection.
3. Turning on display updated. This is done with the "Display Update" VI.
4. Initiating the hardcopy and waiting. The first part can be done with the "Initiate Hardcopy" VI. I did not find a VI to do the other part, which is the *WAI command.
   
5. Requesting the memory data. This is the MMEM: DATA? command, followed by the name of the file, which should be the same as that used in (2). There is no VI to do this, but it would work in the same way as the "Read Trace Data" VI except you don't need the typecasting. The data (string) can be written to disk.

I'll try to whip up something tomorrow morning. Time for me to go home.


Message Edited by smercurio_fc on 06-30-2008 05:44 PM

[MrSafe]

ahah killing me friend. Thank you very much I am hammering away as we speak to come with some sort of solution myself but it looks like I will have to continue tomorrow as well and compare what I get to what you whip up.


Thank you again.

[smercurio_fc]

Well, I managed to get NI-Spy 2.5 and open up the capture file, and it's pretty much as I had said in my last post in terms of the steps. Attached is a VI that attempts this, using the driver VIs. Note that the "Memory Read" VI is one that I wrote since there is no "Memory Read" VI in the driver set. Please read the comments on the block diagram.

For the "filename (on analyzer)" use something like "C:\screencap.wmf", or "C:\screencap.bmp", depending on file format.


Message Edited by smercurio_fc on 07-01-2008 09:57 AM