Line Feed problems
Moderator: sergey
Re: Line Feed problems
Hi,
Thanks for sending the log files in. We have had a chance to analyse them and try to replicate the issue in our lab.
The serial debug shows that your equipment is sending a 0x0A 0x0D (LF + CR). Whilst this is uncommon, it is handled correctly by the VT100 terminal screen (the main GetConsole screen). Most operating systems and text editors will have a problem with this line ending format (e.g. Notepad on Windows, TextEdit on Mac, etc) which may show no new lines, funny characters at the end of lines, or duplicate new lines.
The console log file that you emailed in shows a strange format - 0x0D 0x0A 0x0D - i.e. an additional CR has been added before the LF character. Some editing and transfer software and can be configured to add in extra characters if the line format is unrecognised (possibly in this case, Windows software wouldn't allow a bare LF without a leading CR, or if transferring via telnet the telnet protocol does some line-ending conversion)
I suspect that is where you are seeing the issue, or alternatively in some middleware that is processing the file whilst getting it off your iPad.
We have set up a situation to replicate this in our lab - a serial device sending data with 0x0A 0x0D as new lines and have captured both the serial debug and the console log (as you have), and cannot replicate the issue![Sad :-(](./images/smilies/icon_e_sad.gif)
Is it possible that the file has been edited in some way before sending it to us - e.g. a mail gateway that is scanning and modifying attachments, a Windows editor that is configured to auto-save, etc?
There are two more things you could try:
- you can transfer the files out of GetConsole via iTunes. Connect your iPad/iPhone, go into the iTunes page for your phone, click the Apps butting, scroll to the very bottom of the page and you will see how to copy the "logs" folder to your computer.
- We have a dropbox account that you could upload directly from GetConsole to double check that the console log hasn't been corrupted in any way
In addition, is it possible that the file you send to the vendor doesn't expect these strand [0x0A 0x0D (LF + CR)] line endings and instead something more common like CR+LF or just LF?
Thanks for sending the log files in. We have had a chance to analyse them and try to replicate the issue in our lab.
The serial debug shows that your equipment is sending a 0x0A 0x0D (LF + CR). Whilst this is uncommon, it is handled correctly by the VT100 terminal screen (the main GetConsole screen). Most operating systems and text editors will have a problem with this line ending format (e.g. Notepad on Windows, TextEdit on Mac, etc) which may show no new lines, funny characters at the end of lines, or duplicate new lines.
The console log file that you emailed in shows a strange format - 0x0D 0x0A 0x0D - i.e. an additional CR has been added before the LF character. Some editing and transfer software and can be configured to add in extra characters if the line format is unrecognised (possibly in this case, Windows software wouldn't allow a bare LF without a leading CR, or if transferring via telnet the telnet protocol does some line-ending conversion)
I suspect that is where you are seeing the issue, or alternatively in some middleware that is processing the file whilst getting it off your iPad.
We have set up a situation to replicate this in our lab - a serial device sending data with 0x0A 0x0D as new lines and have captured both the serial debug and the console log (as you have), and cannot replicate the issue
![Sad :-(](./images/smilies/icon_e_sad.gif)
Is it possible that the file has been edited in some way before sending it to us - e.g. a mail gateway that is scanning and modifying attachments, a Windows editor that is configured to auto-save, etc?
There are two more things you could try:
- you can transfer the files out of GetConsole via iTunes. Connect your iPad/iPhone, go into the iTunes page for your phone, click the Apps butting, scroll to the very bottom of the page and you will see how to copy the "logs" folder to your computer.
- We have a dropbox account that you could upload directly from GetConsole to double check that the console log hasn't been corrupted in any way
In addition, is it possible that the file you send to the vendor doesn't expect these strand [0x0A 0x0D (LF + CR)] line endings and instead something more common like CR+LF or just LF?
Who is online
Users browsing this forum: No registered users and 6 guests