Ask everyone a question!
After labview receives the data sent by TCP, parsing the string through the "matching mode" will show that the parsed data will change from a value (such as 12dBm), the second becomes 0, then becomes 13dBm, and then the second becomes 0. Change as follows: 12 ->0
13 ->0
14 ->0
15 ->0
Note: After receiving the TCP command, it will be resolved through the "matching mode" immediately.
This problem is not easy to upload code. After uploading the code, you must have the corresponding platform debugging to see this result.
Can anyone give me some direction?
Riki Posted on January 6, 2021
After uploading the code, you must have the corresponding platform debugging to see this result.
Vina Posted on January 6, 2021
Without the program, guess the problem may be as follows:
1. It is possible that the host side is sending two kinds of data alternately, which causes you to parse correctly the first time, and the second time because the received data is different, it is parsed as 0. This can be ruled out by highlighting + probe monitoring the connection value between TCP received and matching.
2. There is a problem with your TCP receiving settings. Maybe you didn't wait for the host to send data, which resulted in empty data being read? For example, the number of bytes read by TCP is too small, the receiving mode is wrong, etc. The same method can be used to exclude.
3. The expression of your matching pattern is wrong. Maybe two of the signals sent from the host match your expression. If you happen to have a loop, it may be split into three segments.
Hatcher Posted on January 6, 2021
You can add probes to see the specific changes, and connect all the four lines output from the matching mode to the display controls.
