Yes my file contains both CR and LF
This is the contents of my one line file in ASCII and HEX:
ABCD <-- ASCII
414243430D0A <-- Hex dump
This is what the PLC "sees" after Arbitration with STX/ACK, sending the <REMOTE> and <READ ReadFile.txt> then waiting 1 second:
ABCD<OK>
414243443C4F4B3E0D
This is the TBASIC code that I use to display the results of the READ file service on the LCD:
A$ = ""
H$ = ""
I = INCOMM(1)
WHILE I<>-1
A$ = A$ + CHR$(I)
H$ = H$ + HEX$(I,2)
I = INCOMM(1)
ENDWHILE
SETLCD 2,1,A$ ' Display ASCII String
SETLCD 3,1,H$ ' Display HEX String
I'm using the INCOMM(1) command as it does less processing to the characters received on the COMM1 port.
Is there a possibility that the changes to support Unicode characters have affected the TLServer 3.15?