Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time is not logged #47

Closed
GoogleCodeExporter opened this issue Jun 12, 2015 · 1 comment
Closed

Time is not logged #47

GoogleCodeExporter opened this issue Jun 12, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. back to back roasts
2. pressing "reset"
3.

What is the expected output? What do you see instead?
When capturing events such as Dry End and First Crack the time of event is not 
logged so logged data looks like : 132C : 00:00, when it should read 132c : 4:47


What version of the product are you using? On what operating system?
0.5.5 on OSX Lion


Please provide any additional information below.
This only happens on the roast after the first roast. If the application is 
closed and reopened this sometimes fixs the problem but it always returns.
We were using a Omega Datalogger, just upgraded to a TC4C board.


Original issue reported on code.google.com by marvells...@gmail.com on 15 May 2012 at 11:34

@GoogleCodeExporter
Copy link
Author

Should be fixed in v0.6

Original comment by luther.m...@gmail.com on 9 Jan 2013 at 7:47

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant