Discussion:
Error -1074388984 occurred at CAN Write (Multi-Chan Single-Samp 1D Dbl).vi
(too old to reply)
Clarence
2008-06-24 18:10:12 UTC
Permalink
I keep running into an error with CAN Write.  The error keeps telling me that I have to many messages in the CAN Write que and need to clear then or that the messages might be to short or that I may have to wait until there is a successful read.  I believe the memory is full....Any suggestions
Clarence
2008-06-24 18:10:12 UTC
Permalink
This is also more on the error:
 
Possible reason(s):
NI-CAN:  (Hex 0xBFF62008) Write queue overflow.  Solutions for CAN Object: Increase the length of the write queue; Wait for Write Success state prior to calling Write; To transmit recent data only, set the write queue length to zero. Solutions for Net Interface: Wait for Write Mult state then repeat Write; Get Number of Entries Free attribute and Write that number of frames.
Song_M
2008-06-25 23:10:18 UTC
Permalink
Hey Clarence! How are you doing?  Usually, when this error occurs, it is because there are no CAN devices acknowledging the data sent on the bus.  The write buffers would get full and get sent over and over again.  Please post your NI spy logs.  A procedure on how is linked below.http://digital.ni.com/public.nsf/allkb/8D890EC09B15C05A86256E6F007E3E86?OpenDocumentAlso, did you try running some simple commands over the example VI?  Thank you!
Clarence
2008-06-30 20:10:13 UTC
Permalink
1.  nctInitialize ("Fuel Value,Pump duration angle,Pump a...", 0, 3, 0, 1)Process ID: 0x00000578         Thread ID: 0x000001BCStart Time: 15:38:26.656       Call Duration 00:00:00.015Status: 0 (VI_SUCCESS)
2.  nctStart (1)Process ID: 0x00000578         Thread ID: 0x000001BCStart Time: 15:38:26.671       Call Duration 00:00:00.000Status: 0 (VI_SUCCESS)
> 3.  nctWrite (1, 1, NULL)> Process ID: 0x00000578         Thread ID: 0x000001BC> Start Time: 15:38:26.671       Call Duration 00:00:00.000> Status: 0xBFF62207
4.  nctClear (1)Process ID: 0x00000578         Thread ID: 0x000001BCStart Time: 15:38:26.671       Call Duration 00:00:00.063Status: 0 (VI_SUCCESS)
Clarence
2008-06-30 20:10:14 UTC
Permalink
Im still having the same problem. I am working on going through the examples.  Thanks for your help and hopefully we can come up with a solution...
DirkW
2008-07-01 14:10:07 UTC
Permalink
No, its not the same problem. Now you have the 62207 error, which means that you have not specified all required inputs.
DirkW
Song_M
2008-07-01 16:40:08 UTC
Permalink
Hey Clarence! DirkW is right, it seems like this is a different error than you originally posted.  Could you try to run the simple GPIB communication example VIs to run simple commands?  If we can get that to work, then we can work on getting the application to work. 
Clarence
2008-07-11 17:40:10 UTC
Permalink
Okay.  With these examples do you need some type of VISA drivers to be installed on your computer.  When I look for the example on the LABVIEW Help page there are a lot of different choices.  I chose the LABVIEW GPIB.vi example to use.  Is this the correct example and how do i use it?
Clarence
2008-07-11 17:40:10 UTC
Permalink
If i use the basic serial read and write example, I recieve this error: 
 
Error -1073807202 occurred at Property Node (arg 1) in VISA Configure Serial Port (Instr).vi->Basic Serial Write and Read.vi
 
Possible reason(s):
LabVIEW:  (Hex 0xBFFF009E) VISA or a code library required by VISA could not be located or loaded.  This is usually due to a required driver not being installed on the system.
 
 
Clarence
2008-07-11 17:40:10 UTC
Permalink
What is GPIB?
Song_M
2008-07-15 02:10:07 UTC
Permalink
Hey Clarence! My apologies regarding GPIB.  You are correct, you will need NI-VISA drivers to perform serial communication.  For future reference, you can get NI-VISA 4.3 drivers here:http://joule.ni.com/nidu/cds/view/p/id/988/lang/enI apologize again for mentioning GPIB, our communications should actually be focused more on CAN.  If you could, please use the simple example finder CAN VIs, and send me the full NI SPY log for the most up to date error you are receiving.  We will go from there!  Thank you Clarence!
Loading...