#49 timestamps in capture

[Alec Agnese]

Hi. I need to be able to capture UART input, separating each line into 13 bytes. I was able to separate each line into a certain number of bytes by setting the data frame size and checking the "single" box, but I can't seem to do this in the capture file. Is there a way to do this?

Also, I need each new line (13 bytes) to have it's own timestamp. I think this is already set up, and should work once I figure out how to separate each 13-byte frame into a new line. in the capture file.

Last thing, is there a way to disable the "break" output? I'm getting '00' every time the RX line breaks, and it could mess with my log format. I'd like to just ignore this '00'.

Thanks! Please let me know if there is any extra info you need!

[Simon Bridger]

try the current development version at realterm.i2cchip.com. Makse sure to look through the changelog for changes relating to "timestanp"

" is there a way to disable the "break" output? I'm getting '00' every time the RX line breaks"
Probably not as a break IS data of 00
Conceptually it might be possible to remove the last character received after a line-break error. I don't really see how that would be normally useful, since linebreaks aren't a normal condition.
However feel free to make a feature request, and explain how there come to be multiple line breaks in your use case.

[Alec Agnese]

Thanks for the response. I'm using 3.0.1.44, and I found the problem with
the timestamps. I forgot to read the "fine print". I'm displaying hex data,
and for hex display I have to send a sync string at the end of each frame
to add a timestamp and start a new line. I made the change, and now it
works fine :)

As for the breaks, they seem to occur when my MCU (which is where the uart
data is coming from) dies.

Here's my application:
MCU running tasks and logging them over UART. It's powered by an energy
harvester (solar), so it dies from time to time. When it dies, I get the
"break" byte, which will confuse my log parser . So I was hoping there was
a way to ignore it, but I can work around it. When it wakes back up, it
continues running and logging tasks.

Thanks for the help!

Best,
Alec

On Thu, May 16, 2019 at 7:43 PM Simon Bridger crun@users.sourceforge.net
wrote:

try the current development version at realterm.i2cchip.com. Makse sure
to look through the changelog for changes relating to "timestanp"

" is there a way to disable the "break" output? I'm getting '00' every
time the RX line breaks"
Probably not as a break IS data of 00
Conceptually it might be possible to remove the last character received
after a line-break error. I don't really see how that would be normally
useful, since linebreaks aren't a normal condition.
However feel free to make a feature request, and explain how there come to
be multiple line breaks in your use case.

---

• [support-requests:#49]
  https://sourceforge.net/p/realterm/support-requests/49/ timestamps in
  capture*

Status: open
Group: V2.0.0.70
Created: Wed May 15, 2019 10:51 PM UTC by Alec Agnese
Last Updated: Wed May 15, 2019 10:51 PM UTC
Owner: nobody

Hi. I need to be able to capture UART input, separating each line into 13
bytes. I was able to separate each line into a certain number of bytes by
setting the data frame size and checking the "single" box, but I can't seem
to do this in the capture file. Is there a way to do this?

Also, I need each new line (13 bytes) to have it's own timestamp. I think
this is already set up, and should work once I figure out how to separate
each 13-byte frame into a new line. in the capture file.

Last thing, is there a way to disable the "break" output? I'm getting '00'
every time the RX line breaks, and it could mess with my log format. I'd
like to just ignore this '00'.

Thanks! Please let me know if there is any extra info you need!

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/realterm/support-requests/49/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Bachelor of Science in Computer Engineering, University of Florida, 2017
Tel: (954) 515-6446
Alec.agnese@gmail.com

[Alec Agnese]

Simon,

Something I forgot to ask about. I want everything that's printed to the
terminal to be written to a text file exactly as it appears in the
terminal. I tried disabling direct capture so that it captures from the
terminal, but it changes it to ascii. My incoming data is 13 bytes, then 2
sync bytes, and the terminal appends a timestamp and starts a new line. I
want all of that to get written to a .txt file as is. Could you point me in
the right direction? Thanks again!

On Fri, May 17, 2019 at 2:22 PM Alec Agnese alec.agnese@gmail.com wrote:

Thanks for the response. I'm using 3.0.1.44, and I found the problem with
the timestamps. I forgot to read the "fine print". I'm displaying hex data,
and for hex display I have to send a sync string at the end of each frame
to add a timestamp and start a new line. I made the change, and now it
works fine :)

As for the breaks, they seem to occur when my MCU (which is where the uart
data is coming from) dies.

Here's my application:
MCU running tasks and logging them over UART. It's powered by an energy
harvester (solar), so it dies from time to time. When it dies, I get the
"break" byte, which will confuse my log parser . So I was hoping there was
a way to ignore it, but I can work around it. When it wakes back up, it
continues running and logging tasks.

Thanks for the help!

Best,
Alec

On Thu, May 16, 2019 at 7:43 PM Simon Bridger crun@users.sourceforge.net
wrote:

try the current development version at realterm.i2cchip.com. Makse sure
to look through the changelog for changes relating to "timestanp"

" is there a way to disable the "break" output? I'm getting '00' every
time the RX line breaks"
Probably not as a break IS data of 00
Conceptually it might be possible to remove the last character received
after a line-break error. I don't really see how that would be normally
useful, since linebreaks aren't a normal condition.
However feel free to make a feature request, and explain how there come
to be multiple line breaks in your use case.

---

• [support-requests:#49]
  https://sourceforge.net/p/realterm/support-requests/49/ timestamps in
  capture*

Status: open
Group: V2.0.0.70
Created: Wed May 15, 2019 10:51 PM UTC by Alec Agnese
Last Updated: Wed May 15, 2019 10:51 PM UTC
Owner: nobody

Hi. I need to be able to capture UART input, separating each line into 13
bytes. I was able to separate each line into a certain number of bytes by
setting the data frame size and checking the "single" box, but I can't seem
to do this in the capture file. Is there a way to do this?

Also, I need each new line (13 bytes) to have it's own timestamp. I think
this is already set up, and should work once I figure out how to separate
each 13-byte frame into a new line. in the capture file.

Last thing, is there a way to disable the "break" output? I'm getting
'00' every time the RX line breaks, and it could mess with my log format.
I'd like to just ignore this '00'.

Thanks! Please let me know if there is any extra info you need!

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/realterm/support-requests/49/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Bachelor of Science in Computer Engineering, University of Florida, 2017
Tel: (954) 515-6446
Alec.agnese@gmail.com

--
Bachelor of Science in Computer Engineering, University of Florida, 2017
Tel: (954) 515-6446
Alec.agnese@gmail.com