RT Memory Poke Error 3 (Out of Zone)

[Doogie2K]

LabView: v6.1 RT
Real-Time Card: PCI-7030 (6040E)
PC Specs: P4 2.80 GHz, 512 MB RAM
OS: Windows XP Pro, SP1

I'm currently trying to save data from the RT card to the computer hard drive.  Since direct file I/O is not supported, I decided to try storing the data in memory, then extract it from the Windows side later.  Unfortunately, when I try to perform either a write or a poke, and whether I try to do it as an array (Read/Write [SGL]) or as individual data (Read/Wrote/Poke/Peek DBL), it comes up with an Error 3, "Out of zone."  No other explanation is present in any of the help files, which leaves me wondering, what is a zone, and how am I out of it?  Is there a designated area for user memory that I'm not writing to?  (I've attempted to write to 0x0, 0x1000, and 0x2000.)  And perhaps more importantly, is this even the right way to go about such a thing?  Is there a better way to store/extract the data, or am I on the right track and simply having issues with the details?

[MattP]

Hello,

Communicating between the RT board and Windows via the 1k of built-in shared memory is a valid method for small amounts of data, and you can also go the TCP/IP and VI Server routes.   Examples ship with the LabVIEW Real-Time Module that demonstrate the functionality of these different methods. These examples are located in the LabVIEW directory on your hard drive in the [LabVIEW Folder]\Examples\Real-Time\RT Communication.llb library. These will demonstrate the best practices for using all of the modes of communication, and will be your best resource.

You may have received the Out Of Zone error if the device number that you were attempting to write to was not valid.  Take a look also at the example posted here that demonstrates the procedure as well.

[Doogie2K]

I discovered that later.  I'm now fighting with TCP/IP, which is giving me a rather bizarre problem (which would be best discussed in its own thread, assuming my question isn't answered elsewhere already).

Thanks for your help.

[MattP]

You're always welcome to create a new thread for the TCP/IP issues, though if you're still running into problems on this thread, please post back and we'll be happy to assist you!