Trying to use Linx with STM32F4 about linx HOT 4 OPEN

Hello @samkristoff @spathiwa i had some success with the communication but I am stuck at Load Device config vi,
Error: in the Load Device config all the modules are working until the LSB reaches 10, once it reaches 10 instead of sending all the response packet at once the data is splitting into multiple packets(see example)

for example
when the LSB is at 10 if the data size is 0 the response packet is 255, 6, 0,10,0,0 instead of 255,6,0,10,0,15 and in the second iteration its sending 0 and 15
i am not sure why its causing this issue i sent couple of days to understand the issue but no luck, can you please let me know what's causing this issue

from linx.

Can you post a screenshot of the error.
Did you modify any of the LINX VIs?

from linx.

A couple thoughts. The UART buffer size on the device is defined here . This determines the max packet size since it has to fit in the buffer. Yours looks fine.

Decimal 10 is LineFeed (LF) in ASCII. I think the VISA driver uses LF as a delimiter by default but the LINX VI should disable that under the hood.

from linx.

Thanks for the reply @samkristoff i didn't modified any Linx vi's. "Decimal 10 is LineFeed (LF) in ASCII." this makes sense whenever the LSB or MSB bit reaches 10 its chopping the data into two
for ex if the data packet is[ 255,6,0,10,0,15] at 10 instead of sending the whole packet i am seeing [255,6,10,0,0] and [0,15,0,0,0]
this issue is only happening on STM 32 board when i tried with Arduino Uno the data was not corrupted at bit 10

One more issue that i am facing was with set device baud rate Vi, the issue was during the execution of this vi it will first disconnect the existing serial communication and reinitializes with the new baud rate right, when its reinitialize the communication instead of using the same COM port a new alias resources was created with Port binding and initializing the communication with the new alias; this is only happening on STM 32 board there was no issue with UNO

My guess was the port was not getting closed properly is there any way to make sure the port closes properly?

Note: the device was connected to COM 9
new alias were created every time when the serial was initialized

from linx.