# Typica - Data for Coffee Roasters

# Typica

## Data for Coffee Roasters

# Tips, Tricks, and Frequently Asked Questions

## What hardware does Typica work with?

See the Hardware Compatability Table to learn what hardware will work with Typica on which operating systems. If your device is not listed, Typica is not known to work with it. If you'd like to add support for additional hardware, patches are welcome. For new installations, the Phidgets 1048 is generally recommended.

## Does Typica work with my coffee roaster?

Almost certainly. If your roaster already has one or more thermocouples installed, it is possible to jump off of that to one of the supported pieces of data acquisition hardware. If you have an RTD, you might need to replace whatever that is connected to with something that can speak Modbus RTU. Home roasting machines are generally more difficult to connect and may require significant modification.

The below video demonstrates connecting a roaster to a computer using a Diedrich SR-1 and a National Instruments NI USB 9211, but the process is very similar with most other commercial coffee roasters and other data acquisition hardware that takes thermocouple inputs.

## Can multiple instances of Typica connect to the same database?

Yes. You'll need to configure PostgreSQL to allow network connections (it does not by default) and if you're using multiple coffee roasters you'll want to make sure these are configured with different IDs in the database. If you are using a software based firewall on the computer running PostgreSQL you will also need to make sure incoming connections are allowed.

## When configuring rate of change calculations, what is the difference between scale time and cache time?

A rate of change is logically a fraction where the numerator is how much the value has changed and the denominator is the amount of time that change takes place over. Scale time is the number of seconds used for the denominator of this fraction. If you are already used to thinking about rate of change over a certain amount of time, you can continue to use that. Otherwise, matching what you normally have the table view set to show is recommended. By default, that would be 30 seconds.

Measurement hardware is not perfect and presents data that is slightly noisy and of limited precision. Rate of change calculations can amplify that noise and make it difficult to use that information during the roast. Typica provides a way to smooth out that noise by presenting the slope of a linear regression of measurements taken in a given amount of time. Cache time is the number of seconds used for this. A smaller value will allow the rate to change more quickly while a larger value will be more resistant to noise. 10 seconds is a good starting point for this setting.

A good overview of using rate of change calculations in Typica is presented in the following video. The start of the video is an overview of why this is useful. Starting at 2:55 is a demonstration of how this looks in Typica. At 10:07 there's a walkthrough of all of the configuration details for this feature.

## How can I support further development of Typica?

Checks payable to Neal Wilson can be sent to

Neal Wilson
C/O Wilson's Coffee & Tea
3306 Washington Ave.
Racine, WI 53405
USA

If you would prefer to use a credit card, it is possible to do this with the blue "$ Support" button on the right side of the N3Roaster YouTube channel.

It is also possible to hire me for training at your company.

## Why can't I see the batch timer?

There are splitter handles between all of the indicators at the top of the logging window. If you move your cursor to the right of the rightmost visible indicator and click and drag to the left, that should become visible again. Several other elements of this window also have splitter handles that you can use to customize the size of different information displays.

## Can databases other than PostgreSQL be used with Typica?

Not currently. I'd like to add SQLite3 support in Typica 2.0 which would make it easier to support additional database managers.