0xBFFF0015 error on read portion of query

[Brainojack]

Hello,

I'm currently running into a 0xBFFF0015 error on the read portion of a query.  I am able to WRITE to the device to change set points and other operating modes.  I can also send QUERYs to which the device responds (see attached picture) but the error presents itself while reading the response.

Athough I get the information i'm looking for through QUERY there must be a way to avoid this condition.

I've attached the user's guide which has command syntax for WRITE's but no mention of termination characters on READ's.

Regards,
Drew

[Dennis_Knutson]

The termination character for a read should be the same as for a write. What do you have it set to?

[Brainojack]

The Termination Character for reads is set to " Line Feed - \n "

[Dennis_Knutson]

Strange. You should do an I/O Trace to see what is actually coming back.

[Brainojack]

I've performed the trace.  Its only two lines but perhaps you can take a look.  (i've zipped in order to attach)

[Dennis_Knutson]

Sorry, I'm posting by phone. Can you attach the results directly in the message?

[Brainojack]

I'll submit a screen grab of the IOTrace program and a txt export.

[Dennis_Knutson]

The write shows that only 5 bytes were sent - the termination character is not there. Please explicitly include the \n with the command.

[Brainojack]

Im away from the setup right now but I've played witht the permutations of the termination selection options (check boxes in my second picture) with the same results.  I also get this error with front panel VIs from the third party vendor (ILX).  I will try again on wednesday with the utility to view the transmitted bytes.

thanks for the assistance. 

[Brainojack]

Dennis,

I've toggled the option to explicitly send the ' \n ' after a write and obtain the same error

A description of the attachments:

1.  showing that i've toggled the termination on write

2.  Showing that only 5 bytes are sent

3. Manually sending the ' \n ' char (transmits as a ' . ' in the I/O trace)   <---step you wanted me to attempt

ran out of attachments so here is the log of the queries for the 2nd and 3rd pictures

1. viWrite (ASRL3::INSTR (0x0B94CF68), "*IDN?", 5, 5)
Process ID: 0x000015B8 Thread ID: 0x00000FB0
Start Time: 11:06:30.578 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)
Buffer Contents
00000000: 2A 49 44 4E 3F *IDN?

> 2. viRead (ASRL3::INSTR (0x0B94CF68), "ILX Lightwave,LDX-3565B", 1024, 23)
> Process ID: 0x000015B8 Thread ID: 0x00000FB0
> Start Time: 11:06:30.578 Call Duration 00:00:02.000
> Status: 0xBFFF0015 (VI_ERROR_TMO)
> Buffer Contents
> 00000000: 49 4C 58 20 4C 69 67 68 74 77 61 76 65 2C 4C 44 ILX Lightwave,LD
> 00000010: 58 2D 33 35 36 35 42 X-3565B

3. viWrite (ASRL3::INSTR (0x0B94CF68), "*IDN?.", 6, 6)
Process ID: 0x000015B8 Thread ID: 0x00000FB0
Start Time: 11:06:38.031 Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)
Buffer Contents
00000000: 2A 49 44 4E 3F 0A *IDN?.                                                   <-------------------------

> 4. viRead (ASRL3::INSTR (0x0B94CF68), "ILX Lightwave,LDX-356...", 1024, 27)
> Process ID: 0x000015B8 Thread ID: 0x00000FB0
> Start Time: 11:06:38.046 Call Duration 00:00:02.000
> Status: 0xBFFF0015 (VI_ERROR_TMO)
> Buffer Contents
> 00000000: 49 4C 58 20 4C 69 67 68 74 77 61 76 65 2C 4C 44 ILX Lightwave,LD
> 00000010: 58 2D 33 35 36 35 42 45 31 32 33 X-3565BE123