LabVIEW
VISA Write /Read
Hi Fredo,
@Fredo123Danzel wrote:
Unfortunately, I don’t have LabVIEW 2019.
I only use LabVIEW 2022
File -> Save for previous…
@Fredo123Danzel wrote:
I tested my system using PuTTY and found it to be very fast. That’s why I would like to develop a LabVIEW VI that can perform similarly to PuTTY.
What do you think of my VI, please?
Again, we need to know a lot more information on the messaging protocol your device is using. We can accomplish what you are asking, but you have to use the protocol to get anything useful out of it.
@Fredo123Danzel wrote:
use an RS232 communication (FTDI). The supported baud rate by the board is 115200 bps.
I send hexadecimal frames using VISA Write, and I would also like to read hexadecimal data.
You misunderstood crossrulz' request. The things you mention here were already quite clear. But there are about zillion ways to transfer binary data (you don't transfer hexadecimal data, that is just the format your logger chooses to present the binary data to you).
The data is binary obviously but in order to transfer binary data there needs to be some sort of format: start character, end character, possible CRC data, length of message or how that length is encoded, etc. etc. Are multibyte values little endian or big endian?
Without this information it is simply impossible to come up with a good programmatic algorithm to receive and decode the data, or generate according data to send to the device. So far you just showed pictures of the protocol logging with some random numbers shown in hexadecimal notations. No real explanation about what each of those messages should mean, which part is protocol signaling and which part is data. You need to provide this protocol documentation, we can't invent it ourselves. You have the device with which you can do experiments. I and everybody else here can investigate unclear and missing protocol documentation only if we can get our hands on the hardware itself and do trial and error, which is not an option here.
@Fredo123Danzel wrote:
I send hexadecimal frames using VISA Write, and I would also like to read hexadecimal data.
And how are those frames defined? Is there any documentation from your device?
Your still are very vague.
First, are those hex values simply the hexadecimal values of the bytes you sent over the line or are you converting your binary data to hexadecimal text to send as ASCII text?
What is the meaning of the individual values? Why does the command start with 1C or maybe 1C20, or is it rather 1C20AB? What are the remaining data before the CRC? Do you know the algorithm to calculate the CRC? What is it?
Similar questions about the response.
Is every command always 8 bytes long? And every response 10? If not how does the receiver know how many bytes to read?
