Suggest timestamp/binary feature in capture

If you have specific questions or problems with any of my Freeware applications, post them here.

Suggest timestamp/binary feature in capture

Postby spachner » Wed Oct 13, 2010 12:35 am

Dear Roger,

I am quite happy with the current beta of CoolTerm and would like to suggest two little features I would really need (ideas taken from the windows tool TeraTerm).

1) Please add an option to prefix any captured line with a timestamp down to milliseconds like:

Code: Select all
2010-10-12 11:12:13:555 <text line captured>

2) Please add an option to capture as a binary file (without time stamp of course) rather than a text file.

Thanks a lot for contributing your work to the community!

spachner
spachner
 
Posts: 4
Joined: Wed Jul 01, 2009 1:57 am

Re: Suggest timestamp/binary feature in capture

Postby roger » Thu Oct 28, 2010 10:08 pm

Thanks for your suggestions. It was time to wrap up v1.3.0, thus this will have to wait until a future release.

1) Please add an option to prefix any captured line with a timestamp down to milliseconds like:

Code: Select all
2010-10-12 11:12:13:555 <text line captured>


Something like this can fairly easily be implemented.

2) Please add an option to capture as a binary file (without time stamp of course) rather than a text file.

Please explain this a little more. Currently, received data is captured in raw format, i.e. every character in the capture file is exactly as received, even if it is not ASCII data. Is this what you mean when you say "binary"?
User avatar
roger
Site Admin
 
Posts: 215
Joined: Fri Apr 24, 2009 12:41 am

Re: Suggest timestamp/binary feature in capture

Postby spachner » Fri Oct 29, 2010 1:06 am

roger wrote:Thanks for your suggestions. It was time to wrap up v1.3.0, thus this will have to wait until a future release.

1) Please add an option to prefix any captured line with a timestamp down to milliseconds like:

Code: Select all
2010-10-12 11:12:13:555 <text line captured>


Something like this can fairly easily be implemented.

Great, I looking forward to it!
2) Please add an option to capture as a binary file (without time stamp of course) rather than a text file.

Please explain this a little more. Currently, received data is captured in raw format, i.e. every character in the capture file is exactly as received, even if it is not ASCII data. Is this what you mean when you say "binary"?


I haven't tested what CoolTerm is actually capturing when non printable characters are received. When everything is captured regardless of any interpretation then the capture is already binary and I am happy.
I would like to have CoolTerm a Mac OS replacement of Windows TeraTerm (http://www.teraterm.net/) which has this binary option. TeraTerm needs this binary option to bypass any interpretation during logging because TeraTerm is able to interpret received line delimiters from all platforms which is actually a very nice feature which would be great to see in CoolTerm, too.

Again, many thanks for your work and responsiveness.

regards

Stefan
spachner
 
Posts: 4
Joined: Wed Jul 01, 2009 1:57 am

Re: Suggest timestamp/binary feature in capture

Postby roger » Fri Oct 29, 2010 12:34 pm

spachner wrote:When everything is captured regardless of any interpretation then the capture is already binary and I am happy.

Yep, that's what it's doing. What you receive is what gets written to the file, byte for byte.

I would like to have CoolTerm a Mac OS replacement of Windows TeraTerm (http://www.teraterm.net/) which has this binary option. TeraTerm needs this binary option to bypass any interpretation during logging because TeraTerm is able to interpret received line delimiters from all platforms which is actually a very nice feature which would be great to see in CoolTerm, too.

When capturing, line delimeters are written to the file as they are received. e.g. CR+LF is written to the file as CR+LF, regardless of the platform.

So, what you're essentially asking for, aside from what CoolTerm is already doing, is an ASCII option, with timestamps, if I understand your request correctly. What should happen to non-printable characters in this capture mode?
User avatar
roger
Site Admin
 
Posts: 215
Joined: Fri Apr 24, 2009 12:41 am

Re: Suggest timestamp/binary feature in capture

Postby spachner » Sat Oct 30, 2010 1:55 am

roger wrote:So, what you're essentially asking for, aside from what CoolTerm is already doing, is an ASCII option, with timestamps, if I understand your request correctly. What should happen to non-printable characters in this capture mode?


For my usual logging purpose non printable chars are actually not intentionally used (besides the line delimiters) and mainly caused by transmission errors and could be just skipped in display and capture when the new ASCII option is enabled.

But the translation of received line delimiters would be quite helpful in display and capture. This would go hand by hand with the timestamp feature since one has to decide when a line ends and a new time stamp has to be inserted on arrival of the very next char.
When I think about, the time stamp feature would actually be help full in the display, too. So the timestamps could not only be added in capture, but also in the display.

Have a nice weekend

spachner
spachner
 
Posts: 4
Joined: Wed Jul 01, 2009 1:57 am

Re: Suggest timestamp/binary feature in capture

Postby snider43 » Mon Aug 04, 2014 1:19 am

I was able to work with the binary feature in capture. By following the steps, only I was able to perform it and I appreciate your kind assistance. Initially, all look complex for me and some errors popped out, however, the resolutions given here make it easy for me to implement it.


----------------------------------
David
http://topgunfishingcharters.com/
snider43
 
Posts: 1
Joined: Thu Jul 24, 2014 11:25 pm


Return to Support

Who is online

Users browsing this forum: No registered users and 1 guest

cron