03-12-2014
07:10 AM
- last edited on
11-11-2025
06:09 PM
by
Content Cleaner
Hi,
I am very new to LabVIEW and having only used it in the last 3 months, I've managed to put together some codes to get the Instron 5800/8800 to work partially. There's a lot of things that I still do not understand but it has been quite exciting learning so much. So far, I've managed to set the crosshead to move based on my criteria, but I will experience an error mid-way through data logging. Currently, I set the data to read out while the crosshead is still moving, and I realised that it's when the cross-head reaches its end point that I will experience an EABO error (sent by the machine). The extraction of data from my buffer will continue for a few rounds but will eventually terminate without full readout. The machine uses GPIB and I'm using VISA in my codes. The data readout is done in a loop and has delays that match the time required for the buffer to be filled. I've looked through the NI website on EABO (https://www.ni.com/en/support/documentation/supplemental/22/gpib-error-codes-and-common-solutions.ht... error but I still can't figure out what is wrong. Any idea what is causing the problem? Any help or suggestion would be much appreciated.
Thank you!
03-12-2014 07:35 AM
03-12-2014 10:12 AM
Thanks Dennis for your reply. Should the EOI be counted as 1 byte? Right now I'm reading 4008 bytes, which is calculated from a buffer size of 500 x 2 columns x 4 bytes per column + 8 bytes for header. I have included the section of my code that doesn't work properly. In my TDMS file, my samples are in multiples of 500 (which is expected. I get a range of 6-8 buffer read out). The wait time is set at 1000ms, which is the amount of time required for my buffer to fill. The part before the loop calls the machine and data logger to start, and similarly the part after the loop clears the machine and data logger.
03-12-2014 10:45 AM
03-12-2014 11:20 AM
Yes it's compliant, as I managed to get a read out for a few loops. I wasn't exactly calculating; just showing how the value of 4008 bytes was derived. Since my return byte is correct, then the error is not to do with the visa read...then what is wrong?
03-12-2014 11:39 AM
03-12-2014 12:14 PM
Sorry but now I'm not following you. The instrument returns 4008 bytes, so I've set VISA to read 4008 bytes. I have tried with 5000 to VISA Read and it still reads 4008 bytes.
03-12-2014 02:38 PM