Error -70033 occured at Write Buffer.flx

I have a problem with WriteBuffer.flx it gives the error 70033. I am doing contour moves with four axis in vector space control.
There are also strange coercion dots on many motion VIs, that could indicate there is something wrong in my software.
Any ideas how to fix these problems?
Tommi

Can you post your vi?

Similar Messages

Labview 9.0: Error 1 occurred at Write To Measurement File

Hi
Our University recently got the latest version of Labview (9.0 32-bit) which I installed today.The labview file I am using (my6008v6.vi) used to work fine with the older version (8.5 i think). My write-to-file VI is enabled at certain time intervals in order to log data. As soon as it is enabled for the second time I get the following error:
Error 1 occurred at Write To Measurement File->Copy of murray6008v6.vi
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
I made a simple file (simplew2f.vi) to test this, with a button which I can press to enable/disable the writing of data. I am able to start writing data and then stop writing data but as soon as I try resume the writing the same error occurs.
This confuses me greatly since this wasn't a problem using the old version and my Labview knowledge is minimal. Any help would be appreciated.
Attachments:
my6008v6.vi ‏214 KB
simplew2f.vi ‏64 KB

So, which VI are you having problems with? Sounds like both...
Okay... - sigh - where to start....
Well.. Let's start with a few comments.
1. Try to stay away from the Express VI. I know the Marketing guys at NI will not like me for saying so, but I am saying so. They are a nice marketing feature that Grumpy Old Men like myself do not like. They make it easy to write quick code.. And I will limit my comments to that. (It's not your fault.. )
2. The wiring on your diagram is not clear or easy to read. Yes, with additional time and double-clicking each wire I can tell where they are going. However, a rule of thumb, alway wire from Left to Right. Never right to left. And do not run the wires under objects, even the ones you are wiring to.
3. simplew2f.vi: You should put a small delay in the While Loop. I ran it three times and it wrote to the files without error. And yes, I used LV2009.
4. my6008v6.vi: Avoid wiring from the top of the While Loop. At frist, it looked like the data was coming out of the While Loop because the wires went to the left side of all the index node of the Index Array function.
You should set your Browse Option for the file path to "Files or Folders" and "New or existing". I did that and I was not getting the error message you described.
R
Message Edited by Ray.R on 03-03-2010 08:33 AM
Attachments:
pathProperty.PNG ‏13 KB

DAQmx Error -200428 occurred at Write Dig Chan.vi

Hello,
I am trying to read the task name, channel name, and physical channel from a configuration file and using this information create a DAQmx task and two global virtual channels. Everything seems to be working ok (no error) until I am trying to write to one of the channels, then I get an "Error -200428 occurred at Write Dig Chan.vi". What am I doing wrong? Thanks for your help.
Peter
Attachments:
Write Dig Chan.vi ‏37 KB

Hello Corey,
I tried it out for both the Write Dig Chan.vi and the Write Dig Chan (modified).vi, but in both cases, I get the same errors as before.
Write Dig Chan.vi Error -200428
Write Dig Chan (modified).vi Error -200587
Attachments:
Write Dig Chan.vi ‏38 KB
Write Dig Chan (modified).vi ‏44 KB

FPGA An internal software error has occurred. memory write

Hi everybody
We are encountering an error during compilation of an FPGA VI. It is probably related to our use of FPGA block memory. We have a non-timed while loop that is reading from an FPGA host-to-target FIFO and writing into block memory (inside a sub-VI called z_scan_write.vi). In another loop (this one is timed-loop), there is a subVI called we z_scan_read.vi, inside which we read from the block memory.
Does anybody have an idea what is going wrong and how we could avoid this problem? Thank you very much in advance for any hint!
The full error message is as follows. Note that it refers to the above-mentioned two subVIs z_scan_write.vi and z_scan_read.vi...
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
nirviUIDToObject.vi<ERR>
Error getting object reference for UID.
All text parsed:
<CodeGenErr>
<ErrorCode>-61060</ErrorCode>
<DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
<Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
</ErrorInfoCallback>
</LineInfo>
<TreeInfo><TreeID>ProjItem</TreeID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
<UID>2747</UID>
<ObjectName>Memory Write 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>194</UID>
<ObjectName>Memory Read 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61060</ErrorCode>
<DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
<Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
</ErrorInfoCallback>
</LineInfo>
<TreeInfo><TreeID>ProjItem</TreeID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
<UID>2747</UID>
<ObjectName>Memory Write 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>194</UID>
<ObjectName>Memory Read 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
Solved!
Go to Solution.

Removing the two subVIs that read from/write to the block memory doesn't avoid the error showing up during compilation. The error details are obviously different now; they don't refer to the two subVIs (mentioned in the previous post) anymore...
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
nirviUIDToObject.vi<ERR>
Error getting object reference for UID.
All text parsed:
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>

Error -200609 occurred at DAQmx Write: Selected Buffer Size Too Small

Hello, I'm writing some simple test VI's that I will eventually build upon to make an externally clocked analog output VI. I started with a very simple program to output finite samples using the onboard clock with the DAQmx Timing.VI. When I run the program, I almost immediately get an error. The error message is below.
Error -200609 occurred at DAQmx Write (Analog DBL 1Chan 1Samp).vi:1
Possible reason(s):
Generation cannot be started, because the selected buffer size is too small.
Increase the buffer size.
Conflicting Property
Property: Output.BufSize
Corresponding Value: 1
Minimum Supported Value: 2
Task Name: _unnamedTask<1C>
I have used DAQmx VI's before in similar applications and never encountered this error. Additionally, I read at the link below that DAQmx Timing.VI should be generating the buffer automatically. Any ideas as what could be causing this?
Specs:
Windows 7
Labview 2012
PCIe-6353 as DAQ board
Below is a picture of my block diagram and the VI is attached.
Solved!
Go to Solution.
Attachments:
FiniteSamplesTest.vi ‏18 KB

Oops. Just realized my very silly mistake: I forgot to add the Start Task VI. I did so and it works as designed.

Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi, help? please!

Hey guys, I am new to LabView and I have thought myself everything that I know. I am an undergraduate student at NC A&T.
Okay so I took a peice of code that I acquired from Bristol, and it's for a Bristol Wavemeter V1.22. I first edited it to get a graph in there to show the data, and get a slope and Y intercept. Now I am trying to connect it to a computer that controls a COntinuum ND6000. We have existing code for the ND6000 that lets the two computers connect. I took the code out of there that was the part that connects them and now when I wired everything up, I get the "Error 63 occurred at DataSocket Write in getWavelength_v80 EDITED.vi" error message. it states; Possible reason(s):
LabVIEW: Serial port receive buffer overflow.
=========================
LabVIEW: The network connection was refused by the server. For TCP/IP, make sure the server is running and listening on the port you are trying to use. Firewalls can also cause a server to refuse a connection. For VI Server, make sure you have enabled VI Server from Tools>>Options>>VI Server:Configuration."
I tried making sure everything in the configuration was correct and it all is. Can you guys please help me?
Thank you.
I have attached the folder that it is located in because you do have to have the library function. The file is located in the Bristol Wavelength Meter V1.22\Programming Interface\LabVIEW example I.
Thank you again!
Solved!
Go to Solution.
Attachments:
6.jpg ‏153 KB
7.jpg ‏112 KB

So I went through and realized that I had the wrong port typed in by 1 number, I changed that and put in the correct port for the TCP address. Now when I run it I get this error message 66....
"LabVIEW: The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools>>Options>>VI Server:Machine Access on the server side."
Any help?? I checked the Server Machine access and all of them are set to allow.

Error -1073807346 occurred at VISA Write in rsspecan_core_write.vi

Possible reason(s):
VISA: (Hex 0xBFFF000E) The given session or object reference is invalid.
I'm using a USB to GPIB connection to a Rohde Schwarz FSV30 Spectrum Analizer from Windows 7.
My program works 100% in LabView but the problem comes in when I've compiled the program into an executable.
I have already installed the NI VISA Run Time Engine 5.0.1 and it still does not work.
I've also installed the NI-488.2 2.73 drivers for the GPIB unit.
Any ideas?
Solved!
Go to Solution.
Attachments:
Error -1073807346 occurred at VISA Write.png ‏30 KB

Hey,
the problem when building executables with LabVIEW is, that the driver core of the attribute based instrument drivers (esp.. the VIs which are creating this error) is linked while runtime dynamically to the VIs. The application builder which follows all dependencies and include them into the package fails in this case.
To get a running executable please add manually all VIs for the folder <inst lib>\rzspecan\_utility\rsspecan_core\callbacks\ to the LabVIEW project and everything should work fine.
For more details of this driver refer to http://www.rohde-schwarz.com/appnote/1ma170
So long, juergen

Error 5 occurred at Open/Create/Replace File in Write spreadsheet String.vi

Hi everyone,
can anyone help me with this problem?
"error 5 occurred at Open/Create/Replace File in Write spreadsheet String.vi "
I've been using this part of the program for over a year an suddenly this error occures. But not always, mainly at the very beginning of my tests when the file should not be open.
Info: I'm using a realtime PXI-System. Maybe the amount of data can cause the problem? (about 2MB)
Grüße
Meike
Attachments:
writeResults.jpg ‏345 KB
error5.jpg ‏52 KB

Hi Meike,
is the file opened by a different program? Do you try to access it by FTP in parallel to your VI?
You could use basic file functions instead of WriteSpreadsheetFile. That way you could open the file before starting the loop, keep it open all the time and close it once you're finished - with the added benefit of easier error handling…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Error 33172 occurred at Read & Write data transfer between two or more PF2010 controller

Hi,i need to do data transfer between two or more FP2010 controller.e.g. FP2010(A) & FP2010(B).
FP2010(A) need to transfer the measurement (from its I/O module) to FP2010(B) to do the data analysis.These data transfer should be synchronous btw two controller to prevent data lost.
From the vi used in the attachment,i encountered some problems at:
(1) Error 33172 occurred while publishing the data.Can i create and publish data under different item name?
(2) How to synchronies the read & write btw contorller?
All controller are communicating with each other directly without the need of a host computer to link them together
Is there any other method to do fast data transfer betwe
en controller?

Hi YongNei,
You were succesful in omiting enough information to make it very difficult to answer!
Please post your example.
Please tell us what version of LV-RT you are using.
Please define what you concider "fast data transfer".
Have you concidered mapping the FP tags of FP2010(A) to FP2010(B) and vise versa?
WHat exactly has to be syncronized?
If you have something that is close to working, share that.
Well, that as far as I can go with the info you have provided. Depending on the details, what you are asking could be anything from trivial to impossible with the currently available technology. I just can't say.
It would probably be a good idea to start over with a fresh question (sorry) because not many people are going to know what a a "
PF2010" is and I can not guarentee that I will be able to get back to you personally until next week-end.
Trying to help you get an answer,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Today is April 10, 2013. I try to login to iTunes connect and I keep getting the message "An error has occurred processing your request. Please try again later or send an email for assistance." It never tells us what email address we need to write to.

Today is April 10, 2013. I try to login to iTunes connect and I keep getting the message "An error has occurred processing your request. Please try again later or send an email for assistance." It never tells us what email address we need to write to.

The problem was solved by Apple Technical Help. The process is as flollows:
1. Open Safari
2. Menu item Safari-Reset Safari - remove all website data - reset
3. Now if you try to login on iTunes connect it will work.

"Write Buffer is Empty" Error Message

Hello All,
I am using a MC, USB-2416-4A0, controller and DasyLab V11. I am inputting 14 analog temps (TC Type T) and 6 voltages. I have two PID controlled analog outputs. I utilize a variety of displays.
When I run the program it launches and presents the first set of values on the displays. As soon as the displays change to real values the program reports out an error, "Write Buffer is Empty".
I have searched both the MC and DasyLab Libraries and this forum's historical posts with no solution. Any suggestions as to what I should do to eliminate the error.
Also, if it is not asking too much... How do you get the clock display to display in 12hr format. All we can get is military time format.
I have attached a copy of the program.
Thanks,
Bill...
Head Cook
Southern Smoke BBQ Team
Auburn,Alabama.
Attachments:
Smoker 3.DSB ‏102 KB

Hello Smoker,
you get the error message "Write Buffer is Empty" from MCC Analog Output module "Dev1-Ao0"? If yes please check if you use a timer based analog output mode (fixed output rate) for your device. This type of output make not sense for an PID control. You should use an software polled analog output mode with blocksize 1.
"... Also, if it is not asking too much... How do you get the clock display to display in 12hr format. All we can get is military time format. ..." - Do you means the clock example worksheet for 12hr format?
Best regards,
MHa

Error-50150 occured at DAQmx Write

Hello,
I am experiencing a seemingly random error in a large program. The error occurs in a part of the program that simulates tach signals to a CPLD. I have not been able to find out what conditions cause this error, it seems to be random in nature.
The full error reads this:
Error - 50150 occurred at DAQmx Write(Digital 1D U16 1Chan Nsamp).vi
Possible Reasons:
The software has entered an unknown state-usually as a result of a cascade failure induced by an unexpected series of state inputs. The operation could not be completed as specified and you should immediately terminate all further transactions if you are able to do so.
Task Name:TackABC_Write Port0 U16
The device we are using is a PCI-DIO-32HS, with Labview 7.1, NI-MAX 4.1, and DAQmx drivers 8.3.1. The task writes 3 signals to the CPLD, and it works most of the time, but every so often this error will occur. I was wondering what could be the cause of an error like this?
Thanks, Steve

Hello Brian, thanks for the response.
I made a mistake in my last post, it is actually a DAQmx clear task in place of the stop task vi i mentioned. When we first received this error it had no clear task at the end, but I added one. Even with this the error has still shown up from time to time. Would it help at all to add a reset device vi afte the clear task vi?
I took some screenshots for you as well. The first shot is of the function in question, the second is the same shot with the case turned to false, and the third is the inside of the main subvi. When the error occurs it focuses on the write vi that is inside the subvi. Let me know if there is more info I could grab that would make things mroe clear.
Thanks,
Steve
Attachments:
SS3.JPG ‏160 KB
SS1.JPG ‏189 KB
SS2.JPG ‏181 KB

Error -50400 occurred at Invoke Method: FIFO.Read in Host.vi

Hey there,
we have sensors on an Engine which are connected to a NI cRIO 9014 board (with a NI9411 6-channel digital input modul) and go from there via network to a host computer.
cRIO board: the cRIO board collects the data from the engine and stores it in a buffer, this is because the network is to slow for the magnitude of data
host computer: the host computer reads over the network the buffer on the cRIO board, on the host computer it takes out specific portions of the data to create pressure graphs of the engine
Error:
Error -50400 occurred at Invoke Method: FIFO.Read in Host.vi
Possible reason(s):
The transfer did not complete within the timeout period or within the specified number of retries.
This error occurs in the following scenario:
- engine is running
- cRIO is running
When I press the start button (boolean 3) in the host.VI to start the reading of the data from the board AFTER I pressed the run button of the host VI.
The Error would not occur if I pressed the start button (boolean 3) BEFORE I pressed the run button of the host VI.
We tried to increase the time out, but it still did not work, the error occurs!
We would be really happy if you could look over it and help us in this case! If you need further informations or if we need to clarify some specific portion, please let us know!
We included the VI's in the attachement!
Thanks in advance!
Solved!
Go to Solution.
Attachments:
Host.vi ‏152 KB
C_RIO.vi ‏92 KB
Cyl_Pres.lvproj ‏196 KB

Chrisse,
There are a few things wrong in your application, if I may offer some suggestions.
First, your while loops are not running in parallel. In fact, they are in while loops with a true constant wired to them. I am not sure if this is by design for debugging, or on accident. I would put the Polling(read pulling zero elements) outside your main while loop.
Your second nested while loop (the one polling the # of elements and then pulling them out) is going to run just once, and may pull only a few samples. I don't think that is what you are looking for here, and there are a couple ways we can go here. You could continuously poll until you have 0 elements available for x amount of time, then you know you have no more samples available and you can process all the data OR you can put all of your data processing as part of that loop and just always write to file immediately as x samples are pulled.
Also, your main loop's stop condition is (i <= 3) Therefore, it will run once and then stop. Maybe you mean >=3?
Also, you have 'append to file' disabled on your write to spreadsheet, so everytime you write you are overwriting old data. If you want to continuously write, you will be losing data. This can be cured by either setting this to true(requiring a new file name or programatically deleting the old spreadsheet every time you run the vi) OR you can collect all of your data in a shift register, and only write to file once you have all your data available.
The error you are seeing is because you try to close your FPGA reference twice. You only need to close it once.
After seeing your overall picture, I think this can all be cured by simply hardwiring your Read to get your 1440X4 elements, but as we have seen, this does not work. Something is happening in your system....this is what I want you to do...run just the following code...and let me know how many elements remaining it gives you...Once the number has settled(I hope it does and your engine doesn't keep running), hit stop, and all the values will be put on a graph for you. My broken wires are because I do not have the FPGA VI.
Message Edited by Robbob on 04-21-2009 01:48 PM
Rob K
Measurements Mechanical Engineer (C-Series, USB X-Series)
National Instruments
CompactRIO Developers Guide
CompactRIO Out of the Box Video
Attachments:
numelements.jpg ‏39 KB

Error -1073807253 occurred at VISA Read in transient SR830.vi VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.

Hi,
I am have written a program with labview to make transient c-v measurement using a stanford research SR830 lockin amplifier. The program seems to be runing fine, but sometimes it is givvibg an error:
Error -1073807253 occurred at VISA Read in transient SR830.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
Error -1073807253 occurred at VISA Read in transient SR830.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
but if I press ok, the program again starts running. What might be the poblem? BTW I googled a bit and I see that in the labview topic "RS-232 Framing Error with HP 34401A Mulitmeter" by pkennedy32 this is what is said about framing error:
""Framing Error" in an RS-232 context means a very specific thing - when the receiver was expecting a stop bit, the line was not in SPACE condition. This can be the result of:
1... Baud rate mismatch (although other problems would likely crop up first).
2... Data Length problem, If I send 8 data bits and you expect 7, the stop bit is in the wrong place.
3... Parity setting mismatch - If I send 7 data bits + parity and you expect 7 data bits and no parity, the stop bit is in the wrong place.
4... Mismatch in # Stop bits - If I send you 7 Data bits + parity + one stop bit, and you expect 7 data bits + parity + TWO stop bits, the second one might not be correct, although most devices do not complain about this.
But, I must say that this is the same com port setting that I use to measure c-v hysterysis, but I never gt this error there.
I attach the program herewith for your kind perusal. Please help me resolve this issue.
Thanks in advance.
Solved!
Go to Solution.
Attachments:
transient SR830.vi ‏94 KB
csac.vi ‏8 KB
sr830 initialize1.vi ‏15 KB

@Dennis Knutson you are right I checked the read indicator in backslash mode, and instead of a \n it is sending \r. So I changed the \n in my write strings to \r. But, if I keep the CLOSE VISA outside my loop instead of inside as you suggested, the termination character appears to come in the middle of the read string instead at the end. And since the read terminates at the \r so it is displaying some junk value before the \r, but if I put the CLOSE VISA outside the loop and play along with the bytes at the read buffer, I see the whole read string with the \r at the end of the string. But, whenever the values are in exponential form (when close to zero) like 6.938839 e-5, I always get a time out error whatever be the timeout that I put at the VISA initialize. And subsequently, if I stop the program and run it again the machine program hangs and I donot get any reading. Then after I close it again and start, sometimes it hangs for some more or starts working. If I put an arbitrarily large byte count at the READ VISA, then I always get the time out before the operation completed error.
@ Ravens Fan I have removed the CSAC VI altogether and taking the CH! And CH” reading separately, instead as one string. So, no more issues with that.
I use the control at the delay so that I can choose how much delay I want to set, and I use the math operation because I am using adding up the delay time to keep track of the time elapsed. Because in the end I have t plot a time vs. CH! And CH” readings.
I am not sure but probably I am making some silly errors. Please help me out.
Attachments:
transient SR830-2.vi ‏103 KB
sr830 initialize1.vi ‏15 KB

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

Error -70033 occured at Write Buffer.flx

Similar Messages

Maybe you are looking for