HDD vs. Pellets Update

It’s been a cold ride here in New Hampshire for a few weeks. However, like a campfire, on average we may end up less than average on HDD’s for the month. I say like a campfire, because it always seems that one side is too hot and one too cold to really enjoy it, however on average….It’s raining hard here today, so once again the snow is leaving. This will ruin the skiing and winter sports and yet it’s really too cold to enjoy summer sports. Winter in Northern New England has become a lot like southern New England. But that’s a different topic.

HDD vs. Pellets Mid January

The pellets seem to be a pretty steady 14HDD per bag. And so a ton this time of year lasts about two weeks, maybe a little longer. We bought our first ton this year, I was using up old stock and we bought a ton from Tractor Supply, their brand. I am liking them a lot, they seem to not cause any ash build up problems at all. I will buy them again. If you add up all the bags used and divide by 50 bags/ton we are at 4.22 tons heating season to date, for a total cost of $947.39 at the cost of $224.50/ton.


2013 in review

The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.

Here’s an excerpt:

A New York City subway train holds 1,200 people. This blog was viewed about 7,200 times in 2013. If it were a NYC subway train, it would take about 6 trips to carry that many people.

Click here to see the complete report.


HDD Update for the first week of December

In the first week of December I have used 15 bags of pellets to heat the house and shop including hot water. This weeks heating and hot water costs were $64.50.  In the last post I calculated a monthly usage of 68 bags if this month followed the trend for December 2012 Heating Degree Days (HDD).  So with 22.6% of the month gone I have used 22.0% of the fuel predicted.  Probably not a good sign considering it will get colder as the month goes on (probably).  In the first week the HDD were 224 in Springfield, VT.  Last year the first week of December there were 211 HDD and not until the 3rd week was the weekly total as high as 224 barely topping this years first week at a whopping 226.  So this may indicate a colder month than last year’s December.

No further progress on the boiler rebuild, I got distracted by obtaining a “free” hot tub.  It had a fried control board, as well as a fried pump motor.  I am sure the two are related and this should give me a clue as to how to fix the control board but, I have decided to replace the control board with a home built board consisting of relays.  Several of these relays will be controlled by switches by the operator, and several will be controlled by an Arduino  for example controlling the circulator pump and heater as well as reading the temperature sensors and reading the operators desire to raise or lower the temperature.  That will probably keep me occupied in my spare time for a week or so.  The second project in the shop is a sander which is giving me problems.  I ended up buying a second sander to make sure I would be able to meet my contractual obligations but in the meantime, there is a sander taking up a lot of space while I wait for parts.  It is a treat to work on it inside however, so I am not complaining just rationalizing why I am not working on the new boiler feed for chips.


Minor Software changes can make life much more convienient

DSC00698This time of year in New Hampshire it is warm days and cool nights.  Pleasant for the most part but it is still fall.  There can be some rainy raw days that need a touch of heat and to heat the hot water or maybe the day is warm enough but just cloudy so you want to heat the hot water for showers.  So in other words the boiler can often run for 3-4 hours per night, maybe one or two evenings per week.

Shutting the unit down before the upgrade consisted of unplugging the unit which includes all the controls except the draft fan.  This of course shuts off the feed and everything else but the fire still burns the remaining fuel.  I keep the draft fan on to minimize any smoking that might occur otherwise.  I live on the second floor of the building and the boiler is on the first floor so typically I would walk down unplug the unit, take a shower and then go back down and unplug the draft fan.  More than once I have had to go down later after forgetting to unplug the draft fan.  So I added a physical button, the Attn button, to the front of the control panel, and rewired the control box to relay control the draft fan.  Now with a minor software change made I can go down hit the button and the unit shuts the auger feed immediately and then after twenty minutes turns off the relay for the draft fan.  It’s so cool my girlfriend wants to go push the button.  Can life get any better?


Summer’s almost over, time to start thinking about heat

2013 Boiler design flow chart

I know it’s early on the calendar but my focus is starting to shift back to my heating hobby.  After two years of experimenting I have a proven performer with both the mechanical unit and the software I used last winter.  I could change nothing and go through the winter fairly smoothly but there is  always room for more improvement.   So this is my plan:  1) Build a new unit very similar to the proven unit I have been using but with greater feed range capability to allow the unit to feed wood chips as well as pellets.  By building a complete new unit I can always roll up the proven unit after the experiment is over and the data collected and resume heating without a hiccup.   2) Make slight modifications to the boiler to allow a larger interface plate between the feed unit and the boiler.  This will allow a greater range of experimentation with burner designs.  3) Continue making small experimental changes to the working pellet unit such as a vibrator for ash removal, different burner designs, different draft designs.  4)  Continue to make changes and improvements to the software.  To start I would like three modes of operation.  Continuous, run for some amount of time, and run until a set time.  I changed the software to run to a set time by calendar date last spring but it was built into the software by date not menu or button choice.  I would like to have the option of running for a few hours for both experimentation and also to occasionally heat hot water and be able to choose these options by menu.  This fall I am sure I would like the unit to be able to take the chill off and then shut down.    5) Build a chip dryer.  This is going to get to be a priority , I know the days are getting a little shorter and it is amazing how much less solar there is in the fall.  Time to giddy up on that one.

I know I have to prioritize the work, and work as time and cash flow allows.  But I think the first step will be to make a new interface plate and boiler opening.  This will allow standardization for the next design and this work can be done while there is no particular need for heat.  I went dumpster diving the other day and got a great new electrical box, so I guess I can get going on the that part of the new burner feed.  I like free stuff.  I may hit that dumpster again soon.

In the mean time it is still summer and there is still sailing weather.


Fire!

Well of course there’s fire in the burner that’s how it works. After today however the Arduino should be able to sense the fire since I added a photo resistor,  commonly known as a flame sensor, bought at a furnace supply store. With the Arduino’s ability to sense flame, the addition of automatic self starting should be enabled.  The ability to determine if fuel is building up should also add safety to an already proven safe unit.

The sensor I obtained is a flame sensor used in a normal oil or gas fired burner.  The flame sensor allows me to sense the light corresponding to a fire currently burning. The sensor cannot determine if the fire went out or if the flame sensor can no longer see it but functionally it makes no difference to me.  I am interested in either condition and the response is the same to both conditions, turn off the fuel feed.    If the fire went out, no need to keep feeding fuel, that will simply clog the  feed chute and make a mess.  If the fuel has backed up the feed chute so much as to shield the flame sensor, there is excess fuel, turn off the fuel feed.  Physically the sensor is mounted to “look” through the back of the feed slide.  This positions was chosen purposefully to determine if fuel was backing up.

Because the flame sensor is a resistor, I am using a voltage divider circuit to measure the voltage and then using the software to check the voltage with a if – then statement.  The software determines if the voltage is high enough to indicate flame or too low indicating dark.  I have been  recording various sensor data to the micro SD over the heating season, so I will record the voltage overnight and we can see the range of data tomorrow.  If anything this should be a good time of year for the test since the fire is needed to maintain the temperature in the building, it is mid 30’s F here today, but the fire is not required to be too vigorous since the temperature is not extremely cold.

Pictures and data to follow.


Fuel savings built into the software

I added a function to check for the time of year and hour of day to shut the boiler down automatically, I mentioned this in the last post. But as the days get warmer I wanted to make additional changes. I probably ought to be calculating the HDD and comparing to the present outside temperature to calculate a dynamic time needed for adequate heat, however that seemed too complicated so I wrote a simple function to check for date and time. At this time of year it shuts the boiler off at midnight. In March it ran until 3 am.

void FuelSavingsDateCheck() {//start function
DateTime now = RTC.now();  //get the data from the RTC
Month =now.month(),DEC;    //get the month from the RTC
Day =now.day(),DEC;        //get the day from the RTC
hour = now.hour(),DEC;     //get the hour from the RTC
if (Month ==12 && Day <15)  //month of December before the 15th
{//start if section
if (hour >3 && hour <9)  //shut off time of 3 am
FuelTest =0;
else
FuelTest =1;
}// end if section
if (Month == 3 && Day >15)  //after March 15th
{//start if section
if (hour >3 && hour < 9)  //at 3am shutoff burner
FuelTest =0;
else
FuelTest=1;
}// end if section
if (Month == 4)              //month of April
{//start if section
if (hour ==0 && hour < 9)  //midnight shutoff
FuelTest =0;
else
FuelTest=1;
}// end if section
}//end function


The view from April, Daylight savings time adjustment for your RTC

The boiler has worked flawless all winter, I am happy with the software and hardware but with all things mechanical there is room for improvement. I have just started my 7th ton of pellets. And I really don’t want to get into my 8th and don’t think I will have to, especially if I institute some energy conservation in the software. This is the time of year that I would normally burn what my grandmother called a “trash fire”. In her case it was some cardboard boxes from the trash and maybe an odd shaped piece of wood or two. Just enough for 3-4 hours in the evening, letting it burn out overnight since the days get up to 40°F or 50°F there’s no need for more fire than that. Later in the month most of the nights will be above freezing. But I still want to light the boiler in the evening mostly for the hot water and then turn it off at 2-3 am, so I wrote that into the software and it has gotten the consumption down to 1-2 bags per day. I also added a function in the software to change the real time clock for Daylight savings time and back automatically. It’s not fully tested but I think it will work OK.

void DaylightSavingsSchedule(){//start function
if (Year ==2013 && Month ==11 && Day ==2 && hour ==2&&DaylightTest ==0)//fall back an hour
FallBack();
if (Year ==2013 && Month ==11 && Day ==4 && hour ==2&&DaylightTest ==1)//reset flag
DaylightTest =0;
if (Year ==2014 && Month ==3 && Day ==9 && hour ==2&&DaylightTest ==0)//spring forward an hour
SpringForward();
if (Year ==2014 && Month ==3 && Day ==10 && hour ==2&&DaylightTest ==1)//reset flag
DaylightTest =0;
if (Year ==2014 && Month ==11 && Day ==2 && hour ==2&&DaylightTest ==0)//fall back an hour
FallBack();
if (Year ==2014 && Month ==11 && Day ==3 &&DaylightTest ==1)//reset flag
DaylightTest =0;
if (Year ==2015 && Month ==3 && Day ==8 && hour ==2&&DaylightTest ==0)//spring forward an hour
SpringForward();
if (Year ==2015 && Month ==3 && Day ==9 && hour ==2&&DaylightTest ==1)//reset flag
DaylightTest =0;
if (Year ==2015 && Month ==11 && Day ==1 && hour ==2&&DaylightTest ==0)//fall back an hour
FallBack();
if (Year ==2015 && Month ==11 && Day ==2 &&DaylightTest ==1)//reset flag
DaylightTest =0;
if (Year ==2016 && Month ==3 && Day ==13 && hour ==2&&DaylightTest ==0)//spring forward an hour
SpringForward();
if (Year ==2016 && Month ==3 && Day ==14 && hour ==2&&DaylightTest ==1)//reset flag
DaylightTest =0;
if (Year ==2016 && Month ==11 && Day ==6 && hour ==2&&DaylightTest ==0)//fall back an hour
FallBack();
if (Year ==2016 && Month ==11 && Day ==7 &&DaylightTest ==1)//reset flag
DaylightTest =0;
}//end function

void SpringForward(){//start function
DateTime now = RTC.now(); //get the data from the RTC
now =now.unixtime()+3600; //subtracts an hour from the time
RTC.adjust(DateTime(now.unixtime())); //resets the time to an hour earlier
DaylightTest =1; //flag variable so it won’t go back in time continously
}//end function

void FallBack(){//start function
DateTime now = RTC.now(); //get the data from the RTC
now =now.unixtime()-3600; //subtracts an hour from the time
RTC.adjust(DateTime(now.unixtime())); //resets the time to an hour earlier
DaylightTest =1; //flag variable so it won’t go back in time continously
}//end function


I am considering adding Ethernet capability

By adding Ethernet capability I can write the data I am currently collecting on the micro SD card to a browser directly. This means I could pull up Firefox and go to my Arduino’s IP Address and see the data.  This will give me the ability to read the data from anywhere on my home network as well as anywhere I can get internet connectivity, potentially allowing me to review data from a smart phone remotely. Additionally I could control relays from a remote location as well. But for now the ability to ease the data collection and monitor the process remotely will be a great first step. First I have to buy an Ethernet shield.  For those of you not familiar with Arduino this means an additional plug-in board that will stack on top of the Arduino pins.

Ethernet Shield

Ethernet Shield

Here’s a picture of just the Ethernet shield, the connection point you see on the front is the plug-in point for the Ethernet connection. This is a RJ-45 connector. I was able to get a 100 foot Cat 5 with installed RJ-45 connectors for $27 at Home Depot.

Ethernet Shield stacked on an Arduino UNO, note upper connection is the RJ-45 Ethernet connection

Ethernet Shield stacked on an Arduino UNO, note upper connection is the RJ-45 Ethernet connection

At present I have already have a prototype shield plugged into my Arduino Uno. This allows me to easily disconnect and update the Uno without disturbing any wiring connections. There are quite a few wiring connections for the RTC or Real Time Clock, the LCD display, the outside temperature thermister, the boiler water tank thermister, the Auger Feed pipe thermister as well as Relays to turn on the Auger motor and boiler tank water circulator. But when I attempted to plug in a prototype shield into the Ethernet shield there was interference with the RJ-45 connection point. The prototype shield would have grounded itself on the metal so I have ordered Stacking headers to extend the height above the shield. More when the headers arrive.


Work out the software bugs to test burn, Step 8 of a DIY Record

Over the summer and fall I have written and tested a number of programs to have the building blocks of a working program.  I knew the key this year would be the ability to log data.  Of course to log data and have it mean something you have to have good data.  So I spent several days working the bugs out of OpenLog, which works but I would not recommend.  I also spent some time figuring out a combination of moving averages which resultx in stable data.

Of course the integration process was a train wreck.  The arrays used for moving average data smoothing were declared wrong so that bug had to be found and fixed.  The Serial LCD needed to be replaced, and my soldering iron wouldn’t work.    A few of the functions are timed and there were some issues with those functions.  The code for Open Log was not robust enough, once I worked out all those issues, which took most of the weekend, it is finally ready to test.

I had a plow in the shop for repair and soaked up the spilled hydraulic fluid off the floor with some sawdust, actually pellets that got wet.  So the hydraulic oil soaked sawdust is in the hopper to be burned.  It’s burning now, so tomorrow I should have some excel data which will help me make decisions to improve the software.  At this point I am not sure it will be valid however, it is really taking a long time to come up to temperature with the sawdust.   Another data point.

Boiler hooked up and burning for the first time

Boiler hooked up and burning for the first time