RoastLogger with USB & webcam input

[GreenBean]

The PEEK rod I ordered has arrived and I have machined two thermocouple fittings without problems. The material is easy to machine provided you use sharp tools with low speed and high feed.


The fittings are approximately 21 mm long x 12 mm diameter with one end turned down to fit into a 6mm diameter hole drilled in the rear wall of the Hottop. They are drilled to suit a 3mm diameter thermocouple sheath and two M3 grub screws are provided at the cold end to lightly clamp the thermocouple in place. They are shown with stainless steel grub screws as I have not yet received the nylon grub screws.

I think that using 3mm stainless steel sheathed grounded thermocouples with a sheath length of 40 to 50 mm and something like these fittings, fixed to the rear wall of the Hottop with JB Weld should provide a simple trouble free installation (see previous post dated April 7 2013 for the other perceived advantages).

If anyone would like to try this approach but does not want to make their own fittings PM or email me and we may be able to come to some arrangement.

[simonp]

Looks like a nice solution

[CakeBoy]

Yes, very much so

[GreenBean]

Looks like a nice solution

Yes, very much so

Hopefully it will still look like a good solution after testing.

[GreenBean]

I have been asked a number of times over the last year if it is possible to run the RoastLogger on the Raspberry Pi. In the last few days the question came up again on home-barista.com.

The RoastLogger was not designed to run on the Pi and the limited memory available limits the speed at which it can run but it can be done. I have only done a quick test but this was successful with it logging/charting data from a TC4/Arduino for about ten minutes.

I do not wish to support running the RoastLogger on the Pi due to the limited speed but if anyone wishes to experiment with this the following notes may be helpful:

1. You should use the fastest available version of Java with a JIT compiler. I used Oracle JDK 1.8.

2. Use the Raspbian Wheezy distribution for compatibility with the above java. I used 2013-02-09-wheezy-raspbian.img.

3. To communicate with serial devices such as the TC4/C replace the librxtxSerial.so file included in the RoastLogger distribution with one compiled for the Pi's ARM processor. You can do this from a terminal on the Pi by first installing librxtx and then copying the relevant file to the RoastLogger distribution as follows:

$ sudo apt-get install librxtx-java

$ cp /usr/lib/jni/librxtxSerial.so /home/pi/[folder you install RoastLogger under]/RoastLogger/lib/lib/librxtxSerial.so

[GreenBean]

A RoastLogger update to version 1.8 is now available. This update provided much more comprehensive alarm settings for all users, a number of enhancements to the charting and a minor change to the Arduino Controller.

The last several updates to the RoastLogger have concentrated on enhancements to the Arduino Controller which is only of interest to TC4/Arduino users. This update addresses requests by users of other inputs, in particular the provision of additional alarms, which has been by far the most requested enhancement.

Up to 16 separate alarms can now be set, 8 triggered by temperature and 8 by the number of seconds after first crack. Alarms are entered into tables that act in the same way as the action tables in the Arduino Controller. All alarms can be enabled/disabled together as well as individually. Alarms can be triggered by all input devices including the Arduino Controller.

For further information see the following version information and the RoastLogger website.

Version 1.8 - 20/4/2013

Alarms tab:

Now allows up to 16 separate alarms to be set, 8 to be triggered when a set temperature is reached on T1 (BT) and 8 to be triggered a set number of seconds after first crack starts.

An "Enable alarms" check box has been added so that all alarms can be enabled or disabled together.

All alarms now work with all inputs so they can be used with the Arduino Controller if desired. Unless Arduino Controller users specifically want this it is suggested they uncheck the "Enable alarms" check box.

Chart:

Increased height of current roast chart marker arrows to provide more clearance from curves. Users may need to increase chart axis maximum temperature settings
to allow more headroom for markers.

Changed the curve smoothing characteristics.

Added a new menu option to use an alternate chart renderer which applies anti-aliasing to curves. This renderer also uses less smoothing.

Added a menu option to show a spinner in the chart to allow the current roast line thickness to be set in several steps.

It is suggested users try the various combinations of line thickness and anti-aliasing/smoothing to determine what works best for them.
Once you have decided what works best for you the spinner can be hidden by unchecking Menu Options | Show line thickness spinner in chart.

As with previous versions only the chart curves are smoothed. The raw (unsmoothed) data is displayed in the log, all
temperature displays, tables, chart markers etc.

Arduino Controller:

Heater and fan sliders now show the initial % setting as soon as a connection to the TC4/Arduino is established.

Help file:

Updated in line with the above.

[GreenBean]

Apologies for another update but a few minor issues have arisen and I have decided it is better to issue an update now before too many users update to the previous version.

For further information see the following version information and the RoastLogger website.

Ver 1.8.1 21/4/2013

Fixed a few minor issues as follows:

Alarm tab:

Disabled row sorting in the alarms tables as this can cause confusion. Sorting is not necessary as alarms are performed in the correct order regardless of their position in the table.

Fixed an issue which, in some circumstances, could stop the "Enable alarms" check box state being restored correctly on startup.

Updated help file to include information on the action of the alarm table check boxes.

Options Menu:

Changed the default setting (the initial setting used on a new install) of "Show RoR gradients" to checked and "Force windows size/position on start" to unchecked.

[GreenBean]

A few questions keep cropping up regarding specific functionality of the RoastLogger. I have attempted to answer these questions below:

1. Can I set actions at T1 (Arduino Controller action tables) or alarms at T1 (Alarms Tab alarm tables) at a temperature below drop in temperature?

Yes, the actions at T1 and alarms at T1 tables are activated 60 seconds after drop in to allow actions/alarms at temperatures below the drop in temperature.

2. Can I set actions at T1 (Arduino Controller action tables) or alarms at T1 (Alarms Tab alarm tables) after first crack starts?

Yes, the actions at T1 and alarms at T1 tables are active from 60 seconds after drop in until the end of the roast. The actions after first crack and alarms after first crack tables are active from clicking the first crack start button to the end of the roast.

3. The roast stage marker button at the bottom of the chart tab scrolls through all roast stages in turn. Can I skip the "Second crack start stage" and immediately mark beans ejected?

Yes, you can use the "e" or "E" key at any time to immediately mark beans ejected and stop logging and charting. The chart tab must be focused to receive keyboard input for this to work.

[GreenBean]

A minor update to the RoastLogger to version 1.8.2 is now available. It is suggested that you only need to download this update if you are interested in the minor changes listed in the following version information.

For further information see the following version information and the RoastLogger website.

Version 1.8.2 13/5/2013

1. Added a menu option to disable logging and charting of T2 (ET). This is intended to be used by TC4/C users connecting via the Arduino Controller who only have one (BT) thermocouple connected. Checking this option allows them to log and chart T1 (BT) only. Users should select this option before starting a roast as it is disabled during roasting. Whilst this option can be used with any input it should only be necessary for Arduino Controller users. All other inputs, including a TC4/C connected via the SerialDMMReader (DMM tab), can start T1 and T2 inputs separately.

2. Minor change to ArduinoController startup/reset code to fix an issue which only affects the following specific case:

User stops and restarts the controller mid roast with either the fan or heater slider set to exactly 50%. In this specific case only on restarting the slider would show the correct setting but the Arduino would be set to 0.

3. Updated copyright message in log.

4. Updated help file to include the new menu option.

[GreenBean]

A further minor update to the RoastLogger is now available. This update changes the action of the chart tab roast stage marker button and the logger tab save button. It is suggested that you only need to update to this version if you are interested in these minor changes which are described in more detail below:

For further information see the following version information and the RoastLogger website.

Version 1.8.3 18/5/2012

1. Changed the action of the chart tab roast stage marker button. This button can now be used to mark load beans which starts logging and charting. At the end of a roast (after eject beans has been clicked) the button is disabled. Once you save or clear the log from the previous roast the button is enabled again allowing the next roast to be started from the chart tab. Even when this button is disabled a roast can always be started by the log tab load beans button. In this case if the previous log has not been saved it will be auto saved to the last used location and a note added to the notes tab to advise the file name and path used.

2. Changed the action of the logger tab save log button. This button now both saves the current log and clears the log and chart ready for the next roast. Previously it was necessary to click both the save log and clear log buttons to prepare for the next roast. This change avoids the need for users to remember to click both buttons to prepare for the next roast. The saved log can always be reloaded via the template tab if you need to view it after saving.

3. Help file updated accordingly.

[GreenBean]

Randy Glass has been kind enough to update the RoastLogger user manual to include all changes (except the experimental PID) to the RoastLogger up to May 2013.  The update also includes an appendix on troubleshooting common issues and a clearer explanation of the tips for fine tuning of action settings for computer control. Thanks Randy

The manual is excellent and is recommended reading for all RoastLogger users. It covers installation, initial setup and use of RoastLogger for all input devices. It is in PDF format and can be read online or downloaded to your hard drive. To view the manual go to the RoastLogger website then click on the user manual icon. If you have recently visited the RoastLogger website you may need to refresh the page or delete your browsers cache to view the new manual.

[GreenBean]

Randy Glass has made a further update to the RoastLogger user manual to clarify a few minor issues. Thanks Randy.

To view or download the updated manual (version 1.2.2) follow this link then click on the user manual icon.. If you have recently viewed or downloaded the manual you may need to empty your browsers cache to view the updated manual.

[GreenBean]

An update to the RoastLogger to version 1.9 is available. This update provides multi-language capability for the RoastLogger and the included SerialDMMReader.

The update includes a language editor so that users can provide and test their own translations and, hopefully, make them available for others. If users provide me with a copy of the translated language files I will include them in future distributions of the RoastLogger.

For further information see the following version information, the RoastLogger website and the detailed instructions provided by the language editor.

Version 1.9 14/6/2013

Added multi-language capability to the RoastLogger and the included SerialDMMReader.

Added a language editor to the RoastLogger distribution. The language editor is intended to assist users in extracting language files from the relevant jar files, editing the files by adding a translation for a new language, inserting the resulting language files back into the relevant jar files and testing the result by running the RoastLogger. The language editor provides guidance on each of these steps to make the process as painless as possible.

This allows users to translate their copy for their own use and, hopefully to send a copy of the translated files to me for inclusion in future distributions of the RoastLogger.

In order to keep the effort required for translation to a minimum only the key text on displayed forms and the relevant tooltip text is offered for translation.

To use the editor, download and install version 1.9 or above of the RoastLogger, ensure that the RoastLogger is not running, open the LanguageEditor folder and double click the RoastLogger-LanguageEditor.jar then follow the instructions the editor provides.

[GreenBean]

A minor update is available that updates the RoastLogger to version 1.9.1, the SerialDMMReader to version 0.7 and the LanguageEditor to version 1.2. The update only affects language translation. Unless you are interested in language translation you do not need to download this update.

For further information see the following version information and the RoastLogger website.

RoastLogger version 1.9.1 SDMMReader version 0.7 LanguageEditor version 1.2

This update only affects language translation. Unless you are interested in language translation
you do not need to download this update.

The RoastLogger and SerialDMMReader have been updated to internationalize more strings, that is to offer more strings for translation. In the previous revision I used a wizard in my IDE to extract all the strings for translation and it seems to have missed a random selection of strings for some unfathomable reason.

The update of the LanguageEditor involves a minor change to ensure that, if users extract the default language file from the jar, they can not overwrite any previous translation in the selected language.

[GreenBean]

I have wanted to experiment with using a Teensy rather than an Arduino in a TC4 like device for some time. I suggested this along with the perceived advantages (see below) to JimG several months ago. Jim clearly does not have time to experiment with this at present so I have decided to design and build a new PCB to test these ideas. The first prototype boards are in production and I should have them for testing in about three weeks time.

The new board is intended to provide an interface between the RoastLogger and a Hottop roaster. It is not a TC4/TC4C and has none of the inputs and outputs of the TC4 and is designed solely to control Hottops. It uses much of the logic that Jim and I developed for the HTC/HTShield and includes the same ADC as the TC4 for compatibility with existing sketches.

The RoastLogger Hottop Controller board (RL-HT-CRTL) should provide the same functionality for controlling a Hottop as a TC4C/HTC or Arduino/TC4/HTShield. A different sketch (firmware) is required as the Teensy is not entirely compatible with an Arduino. I have prepared a sketch (RL-HT-CTRL.ino) for testing with the new boards.

As the minimum order for PCB's is 10 units I will have some spare boards available. If testing goes well I could make up a few more boards for anyone who wants to convert their Hottop to computer control using the RoastLogger and can not wait for Jim to get back into production.

I do not wish to go into business making these boards but, if testing goes well with the first prototype boards, I will advise more details and could make up a few boards on a first come first served basis.

The perceived advantages of the RL-HT-CTRL board over existing (Arduino based) solutions are:

1. Allows the user to load precompiled sketches without needing to download and install the Arduino IDE or know anything about programming or compiling sketches. They would just have to download a very small Teensy Loader program that loads sketches onto the Teensy. I would compile the necessary sketches and and make them available for download .  Users just plug in the board via USB, open the loader program, click file open and point to the compiled sketch that I provide and in about a second it is loaded ready to go.  This means that users can easily update the firmware. I would make precompiled versions available to download so users could choose from versions that output in C or F and that are suitable for their chosen thermocouple type (K,J,T).  They just select the one they want and load it onto the device in a few seconds.  Note that any boards I supply would be preloaded with the users chosen configuration.

2. Has a smaller footprint than existing boards (smaller than an Arduino Uno) allowing for installation on the left hand side wall of the roaster as viewed from the rear fan cover. This removes the need to make a separate bracket.

3. The Teensy 2.0 plugs directly into the RL-HT-CTRL board, no interconnecting cables are necessary.

4. The Teensy loader program does not require any drivers in any operating system.

5. Serial communication with the RL-HT-CTRL does not require any drivers in any operating system but does require an .inf file in Windows. A suitable .inf file for Windows users can be downloaded from the Teensy website.

6. Provides the possibility of communicating with the RoastLogger via USB HID in future (this would require some rewriting of the RoastLogger). This would provide much more robust communication and make it plug and play from a user perspective. That is the user would not need to select serial ports, set baud rates etc. They would just have to plug in the USB cable and the RL-HT-CTRL would be recognised and communication would begin automatically. If this was implemented in the future there would be no need for any driver in any operating system including no .inf file required in Windows.