NorthSouth
Member
I rewired my roaster's bean temp thermocouple output away from the roaster control panel and into a phidget 1048 and installed a laptop with Artisan.
I connected a new thermocouple to the roaster control panel so it wouldn't get upset.
The new thermocouple is located in the fresh air, not touching the roaster.
The roaster would henceforth only show the ambient air temp.
Why didn't I leave the roaster control panel alone and install the new thermocouple for Artisan by drilling a hole in the drop door etc? I'm lazy.
Prior to starting the burner, both thermocouples reported roughly the same (ambient) temp so I thought all was well.
I started my first roast.
At charge temp, I loaded the beans into the drum and informed Artisan of the event.
As the roast proceeded, it was looking much slower than usual, given the elapsed roast time & reported temp.
Near what should have been the end of the roast, the beans were much lighter than usual and the reported temp was much higher than usual.
I kept going for a little while and lost my nerve, not wanting to damage the roaster with high temperatures. I dumped the beans.
They looked (and sounded and smelled) just starting first crack.
I started to puzzle this one out.
I have previously roasted these beans and am very familiar with them.
The roast, from charge to dump, was 45sec longer than normal.
I kept my burner settings the same as I normally would.
So how were the beans under roasted?
A light went on in my head.
I had forgotten to configure the thermocouple as type J (Artisan defaults to type K for my phidget).
So the both the charge and drop temps must have been reported as being much higher than the truth.
I configured the thermocouple correctly for Artisan and did another roast.
Bingo!
Moral:
Don't be lazy.
If I had 2 thermocouples (old way and new way) both reporting bean temp, I would have immediately found the issue.
Sorry for the long post.
I'm feeling quite happy with the ultimate result, even though I ruined one roast.
I connected a new thermocouple to the roaster control panel so it wouldn't get upset.
The new thermocouple is located in the fresh air, not touching the roaster.
The roaster would henceforth only show the ambient air temp.
Why didn't I leave the roaster control panel alone and install the new thermocouple for Artisan by drilling a hole in the drop door etc? I'm lazy.
Prior to starting the burner, both thermocouples reported roughly the same (ambient) temp so I thought all was well.
I started my first roast.
At charge temp, I loaded the beans into the drum and informed Artisan of the event.
As the roast proceeded, it was looking much slower than usual, given the elapsed roast time & reported temp.
Near what should have been the end of the roast, the beans were much lighter than usual and the reported temp was much higher than usual.
I kept going for a little while and lost my nerve, not wanting to damage the roaster with high temperatures. I dumped the beans.
They looked (and sounded and smelled) just starting first crack.
I started to puzzle this one out.
I have previously roasted these beans and am very familiar with them.
The roast, from charge to dump, was 45sec longer than normal.
I kept my burner settings the same as I normally would.
So how were the beans under roasted?
A light went on in my head.
I had forgotten to configure the thermocouple as type J (Artisan defaults to type K for my phidget).
So the both the charge and drop temps must have been reported as being much higher than the truth.
I configured the thermocouple correctly for Artisan and did another roast.
Bingo!
Moral:
Don't be lazy.
If I had 2 thermocouples (old way and new way) both reporting bean temp, I would have immediately found the issue.
Sorry for the long post.
I'm feeling quite happy with the ultimate result, even though I ruined one roast.