RadiMation Error: 805328368: Difference between revisions
| Line 7: | Line 7: | ||
[https://forums.ni.com/t5/LabVIEW/Lecroy-Waverunner-TCP-IP-vs-LXI/td-p/1584422 Post Usage LXI/TCP-IP] | [https://forums.ni.com/t5/LabVIEW/Lecroy-Waverunner-TCP-IP-vs-LXI/td-p/1584422 Post Usage LXI/TCP-IP] | ||
More information how to change the communication protocol on the device can be found in the manual of the device. | More information how to change the communication protocol on the device can be found in the manual of the device or by going to the webpage of LeCroy. | ||
For a explanation and introduction to the protocol please read: | |||
[https://teledynelecroy.com/doc/introducing-the-lxi-interface LeCroy-Introducing the lxi interface] | |||
When you have changed the protocol to LXI and are still having issue please contact our support for further assistance. | When you have changed the protocol to LXI and are still having issue please contact our support for further assistance. | ||
Revision as of 12:39, 25 March 2020
Binary block buffer couldn't be found
This a known issue when using the LeCroy WaveSurfer en WaveRider. Make sure that the device is in LXI mode when using it with RadiMation. When you get the Error "Binary Block buffer can't be found" it could indicate that the device is set to TCP/IP mode. Please verify if this is the case. Set the communication protocol to LXI and then try to connect again. When the device is configured via TCP/IP it will respond correctly to the check devices test but it will give an error when running the test.
For further information please read this form post regarding the use of TCP/IP, LXI and the Lecroy waverider in combination with different software. Post Usage LXI/TCP-IP
More information how to change the communication protocol on the device can be found in the manual of the device or by going to the webpage of LeCroy. For a explanation and introduction to the protocol please read:
LeCroy-Introducing the lxi interface
When you have changed the protocol to LXI and are still having issue please contact our support for further assistance.