Roll your own controller with this gadget

  • Active since 1995, Hearth.com is THE place on the internet for free information and advice about wood stoves, pellet stoves and other energy saving equipment.

    We strive to provide opinions, articles, discussions and history related to Hearth Products and in a more general sense, energy issues.

    We promote the EFFICIENT, RESPONSIBLE, CLEAN and SAFE use of all fuels, whether renewable or fossil.
Status
Not open for further replies.

mwk1000

Member
Nov 12, 2008
158
Southern MI
Just ran across this looking for some wifi gear and thought of the home grown controller fans out here. 60$ at sparkfun and they seem to have rolled in the relays,temp sensor feeds ( add our own sensors ) and a basic command language over USB so no need to go after an arduino if you are looking to get something off the ground fast.

Certainly looks like an interesting starting point.

http://www.canakit.com/Media/Manuals/UK1104.pdf
 
You and me both! Relays and temp sensors connected to a simple command language. Begging for use. I was trying to hunt down a WiFi enabled power switch ( TCP/IP ) not just RF and ran across this.

I thought about it a bit more and it would REQUIRE a computer to operate so in that sense I like the arduino better since when I upgrade ( and break ) my computer system I do not have to worry about the effect on heating my home. Since I'm in the computer biz I am ALLWAYS trying something and breaking something.
 
Amazing what $1.50 can buy you this little 8-bit PIC microcontroller with an USB interface! Then add a few relays and some software all ready to go for $50.

I ordered the 16-sensor PC sensor system from the folks in china...and while the sensors all seem fine, the little USB interface they provide seems to keep crapping out on me. Even with the sensors just sitting on the bench, nothing moving, after awhile I keep smelling the controller and it dies. Happened to a few different ones. So I'm peeking around for an alternative simple interface to all of these Dallas 1-wire sensors. I see this device can readily handle six sensors, one on each of its own I/O lines. I wonder if the software would support multiple sensors on each I/O pin? Or I wonder if the PIC can be reprogrammed readily over the USB interface so one could write their own code for the PIC?

But I have to agree, a nice simple device like this with a easily to use command language, with some logical constructs and simple programming "interface" would make a really great way to control a complete system....
 
I had the same thought since I have 9 sensors on one pin today. My guess was not as it is setup. Looks like they opted to do one sensor one pin.

I was thinking Perl or Lua , Back in the 90's we used stacks of 16 and 32 serial port port terminal servers to monitor datacenters. I used perl for 95% of it. I have done some strange gadgets , Toll gates on the ambassador brige, Kidney dialysys machines, X.25 packet nodes by the 1000's, 3-4 axis NC milling machines, most high end Telcom switches, computer consoles .... Boilers :)
 
No I can't really say. I am not familiar with that but having it's own aquastat would seem to me to imply setting up a zone an controling the pump directly without the need for this gadget.
 
bpirger: 16-sensor PC sensor system ... crappingout

I used the 16-sensor unit before the 1-wire became available, and I now have in use two systems using the 1-wire mini-LAN, one operating 17 sensors and the other 16 sensors. I did have trouble with sensor failure on the 16-sensor unit. One USB controller for the 1-wire physically broke, so I ordered a replacement plus a couple of extras, just in case. None of the 1-wire USB sensors has failed. I use them only for data logging and computer screen monitoring -- not wireless, not web-enabled and not controlling. I also have in use pre-made DS18B20 sensors and I have made and encased my own DS18B20 sensors. No 1-wire sensor has failed.

The roll-your-own gadget looks very interesting. If I was starting over I think I would try something like this, still might although I have a lot invested in mechanical and electronic aquastats, boiler controls, and set-up. It might be time to start playing again.

I also would look at a completely wireless system or wi-fi with repeater system. My boiler is in the shop, no phone line and beyond the range of the wi-fi in the house.
 
Jim:

None of my actual sensors have died either, just the little USB controller. This is the one with the two "audio" jacks that plug in, and then the sensors all attach with endless "y" cables. I get it to work, but then within an hour, one of the channels on the USB adapter will crap out. Has happened on three different USB adapters...the little jobs in the green plastic. I think it is the actual USB to serial interface chip.

Are you saying you finally got one of these little USB guys to work reliably for you, or did you have to get to something else? I just want to monitor as well....
 
I get it to work, but then within an hour, one of the channels on the USB adapter will crap out.

I was having this trouble too, extremely frustrating. The channel would work, then it would not. After considerable angst I discovered that the sensor, the one provide by the mfr, was intermittent. With the right wiggle or pull on the cable, I could get the sensor to work, sometimes, and then for awhile, and then not at all. I just replaced the sensor and all was OK. What was worse was that my first replacement sensor exhibited the same problem. Drove me crazy. The next sensor replacement was OK.

I don't use endless Y cables to the controller. I use Cat5e, both greens for ground to all sensors, both reds for +5vdc to all sensors, and both oranges (1 plug) and both reds (2nd plug) for data; all connections soldered, and then all coming to the two plug jacks to the controller. This has worked well for sensors up to about 35 feet of cable; haven't tried anything further.

EDIT: What I described was for the LAN 1-wire; not the TemPer 16. I don't know what to do if there is a bad sensor with the 16, as the addressing seems to be fixed and mated to the sensor. I tried to use the 16 controller with 1-wire sensors and I could not get it to work.
 
Status
Not open for further replies.