Hmmm…
Since there probably is no carriage, but maybe if it is an old printer: -
(Numbers are in decimal.)
Chr$(13) Carriage return, moves carriage (print head) to the left margin.
(Not necessarily the hardware left carriage shock absorber.)
(If you want to see something funny then write a small program that moves the carriage of an old printer from left mechanical stop column 1 to, say, column 132. Then back to column 2 and onto column 131, 3, 130, 4, 129, 5, 128… don’t have a coffee on the same table as the printer because harmonics are a wonderful thing.

)
Chr$(10) Line Feed, forces the paper to advance by one line.
Chr$(11) Vertical Tabulation. Seldom used on printers but forces position one line down.
(If no lower line is visible then invoke a Line Feed. Could be wrong on that, long time ago.

)
In VBA, vbNewLine…forces the
result of a carriage return + line feed even if the system does/does not require the Chr$(10) (UNIX and some versions of Mac.)
So why is the carriage return issued before the line feed? One answer is that some systems don’t need the line feed but that is incorrect. If a system doesn’t need a line feed then it should not be sent and the printers could be setup to automatically insert a line feed if required and not sent.
When a printer receives a carriage return that will be the longest, in time, of any job it has to do. Remember this goes back quite a while and the carriage was returned by a spring. So to save time the carriage return was issued first and while the carriage was returning a line feed, if required, was performed during transit. It was simply faster to do it that way.
Regards,
Chris.