A project suggestion - for Netduino, Plus, or mini.

I was looking at the early membership dates, in July, and then when I joined in September, and noticed Chris said the Forum has had the 1000th member. Then I keep reading about the Netduino, the Plus,and the Mini being 'sold out" frequently. Sorta means there must be more than a few reading, playing, and either getting stuff built, or maybe getting bogged down in the hardware/software swamp. Lots of writers talking abut how they did this and that with the Arduino, but can't do the 'same thing' with the Netduino. Sorta means there are a lot of Netduino owners we don't hear from ! I'm sure all the more experienced members can agree, it all starts to be easier once you get through the 'mechanics', once you do the "Hello world" example, and have a little solid footing. Now, I'll be the first to admit, my solid footing isn't the best. But, I'm retired, and get off focus real easy. (Can you hear the gales of laughter from my wife?). What I would like to do is suggest some practical projects, that will be doable by almost all, and that should help people get started and keep smiling. ANd some of this thinking comes after reading , and enjoying, the book that got released a short while ago, "The Internet of Things". Project suggestion # 1: Read a DS18B20 sensor, and pass the data to a running program on the PC. No Internet, no extras, nothing fancy. But, it would make for a solid beginning. ANd it seems to me that between four or five folks on here, it would be quick and simple. Have I done it? Nope, I've done parts and pieces, and gotten side tracked trying to pass data to my .NET website ! And nothing exotic, or complicated. But it would give people, especially beginners, a place to hang their experience hat, and go forward. I would also suggest commented, detailed commented, code. Sooned or later, we're going to get a Netduino Wiki spot, and this type of project is a good place to build out from. My thoughts, for what they're worth!

I'm relatively new to the game, but I'm very interested in assisting with this project. I'd just need to pick up the sensor. Perhaps we can get some access to the Sandbox for this?

Project suggestion # 1: Read a DS18B20 sensor.... And it seems to me that between four or five folks on here, it would be quick and simple.

Edit 2011-02-18: Removed the attachment, please refer to the original OneWire post - the archive published there also contains firmware binaries.

Attached is source code of a custom firmware with 1-Wire native driver, managed dll and sample application that demonstrates usage of 1-Wire commands and DS18B20 sensor. This is a next version to OneWire Alpha, and it has been sent to Chris and his team for review and possibly inclusion in the official firmware.

Please note the timing of 1-Wire functions is based on code generated by RealView compiler, it has to be adjusted for other compilers. Additionally, it relies on slow timer and duration of pin state change functions for short delays that slow timer cannot handle, because I was not able to properly calibrate the existing HAL microsecond delay functions.

Enjoy

You say "no internet" -- does that mean "no network"? My sous vide controller basically does what you describe, and sends the temp back via debug and network. There is an extra piece in the form of a onewire>rs232 controller, since the netduino doesn't support onewire directly, yet. Some links: Reading temp from DS18B20: http://forums.netdui...ch__1#entry5962 Graphing data over the network: http://forums.netdui...ch__1#entry4637 My sous vide thread: http://forums.netdui...ch__1#entry6196 The DS18B20 is a very cool chip. Once onewire is supported in the netduino, it will be a piece of cake to use.

OK, I asked for this ! First of all, CLosedEyeSeeing, I didn't even know there was a Sandbox brewing, so thanks. I have my application in now ! And being new to this, hopefully you can help me explain, and ask, the dumb questions. CW2 & Bill.French are two that I really hoped would pop up. Both of you are at ease with the C# side, and apparently comfortable with the hardware. My initial reaction to CW2's posting was to back up. I know what you're saying, and I can follow most of the code, but if I'm not comfortable doing that, many others are not going to be either. If I start some questions based on your initial answer, would you help me with some explanations ? I want to keep in mind there are some.many on here that say they can't solder. And I suspect more than a few that have no idea what you mean by managed code, native drivers, and a sample application. I think it is possible to breakdown this thread so that anyone, with a Netduino, Plus, or Mini could put together some blocks, hook up a few wires, and see information appear on the PC screen. But, I'd like to back up from even graphing, maybe just a text block, and the numbers appearing. Remember, I'm thinking the "Hello World" side of things at first. Bill French, of course, I'm really angling to be invited to drive a couple miles over to Alfred from Waterboro for some of that sous vide steak, just to get that out in the open ! < smile > On the serious side, I bought the kit from Anderson, and started playing with it. Then I started using the Arduino talking to the Netduino , so I didn't need the Anderson solution. Of course, then I got completely sidetracked and am trying to relearn how to pass data to my own site, so I don't need to rely on Pachube ! I understand that the Netduino, which uses slower managed code, ie C#, doesn't have the response time to support a DS18B20. And I understand that native code to support OneWire is in the plans, and will eventually be 'part of?" the Netduino firmware, and then more easily utilized. So, what to do in the interim. I liked the solution of the Anderson RS232/Onewire converter, but you know, how is that really different or much cheaper, than just buying a Arduino to use with the Netduino? But look at the beginner out there, the first thing he reads is he needs to go out and buy an Arduino, after he's made the choice to go with a Netduino !! So, maybe we can stall a bit, and back up. And yep, Bill, not even a network, just passing data back on ? maybe a USB/TTl adapter to a Windows form with a text box. WHat can it pass back for data? Since this is initially just a step above the Blinky Light example, how about, I don't know, the ref voltage, input from a light sensor, etc? You would have your PC communicating with the Netduino, regardless of version, and updating a textbox on the Windows form. Sure beats up the problems with starting new with Visual Studio Express, the Netduino Family, and a couple wires. And leaves the whole thing open to some great explanations of code, hardware, etc. From there it could go anywhere, adding the Ethernet with the Plus, TTL RS-232 from one part of the house to another, what can you measure in a house with the mini that's useful and easy to do ? Enough from me. Beat me up!

I know what you're saying, and I can follow most of the code, but if I'm not comfortable doing that, many others are not going to be either. If I start some questions based on your initial answer, would you help me with some explanations ?

Yes, of course.

So, what to do in the interim. I liked the solution of the Anderson RS232/Onewire converter, but you know, how is that really different or much cheaper, than just buying a Arduino to use with the Netduino? But look at the beginner out there, the first thing he reads is he needs to go out and buy an Arduino, after he's made the choice to go with a Netduino !!

From what I've been reading, OneWire is actually really hard. The timings are very precise. Even the Adruino playground references Dr. Anderson's chip as an alternative that "reduces the workload inside the Arduino". Some sort of interrupt or other delay in the middle of it and you're sunk.

Although I might just be trying to justify my purchases to myself.

From what I've been reading, OneWire is actually really hard. The timings are very precise. Even the Adruino playground references Dr. Anderson's chip as an alternative that "reduces the workload inside the Arduino". Some sort of interrupt or other delay in the middle of it and you're sunk.

Although I might just be trying to justify my purchases to myself.

I've been bouncing around on my thoughts on this one. Part of me started to be a purist, and stay with the Netduino. Then I ordered the package from PhAnderson, for a couple reasons: one, it's under $10 bucks, and two, I was curious. Go read his site, and you can't help but be intrigued!

A week later, I received a small envelope with a sheet of paper, and a plastic envelop inside. I'm at that stage now. You can service 6 DS18B20s with it. As soon as I get my focus back on the hardware end, I'll give it a spin. Upside says it's cheaper than buying an Arduino, and doesn't seem that it will use more I/O pins on the Netduino.

When you say the OneWire is actually really hard, I chuckled. All the more reason to get it running! But, it made me think , is it really hard, or is it a matter of reliablity and stability ? I'd love for some input from others. I tend to build stuff and forget about it. Is OneWire going to be more, or less. stable with different methods?

It does require soldering. And that apparently stops some folks. It shouldn't but I understand the apprehension.

I've been bouncing around on my thoughts on this one. Part of me started to be a purist, and stay with the Netduino. Then I ordered the package from PhAnderson, for a couple reasons: one, it's under $10 bucks, and two, I was curious. Go read his site, and you can't help but be intrigued!

A week later, I received a small envelope with a sheet of paper, and a plastic envelop inside. I'm at that stage now. You can service 6 DS18B20s with it. As soon as I get my focus back on the hardware end, I'll give it a spin. Upside says it's cheaper than buying an Arduino, and doesn't seem that it will use more I/O pins on the Netduino.

When you say the OneWire is actually really hard, I chuckled. All the more reason to get it running! But, it made me think , is it really hard, or is it a matter of reliablity and stability ? I'd love for some input from others. I tend to build stuff and forget about it. Is OneWire going to be more, or less. stable with different methods?

It does require soldering. And that apparently stops some folks. It shouldn't but I understand the apprehension.

Were you able to get the OneWire controller working, I also ordered it, but I found the "schematic" less than useful.

I got the phanderson controller working -- check my links above.

Yep, working fine. I received a piece of paper with the schematic on one side, and the other side filled with different sensors and how to hook them up. Plus the information on the PHAnderson site contains a lot of info. I had more problems with the code than anything else, but that's just me. I forgot each Netduino, Plus,Mini has its own set of references. Currently I'm working on a WIndows form that receives the data. All the projects make the Netduino do something, but getting the data back out, NOT using the USB seems to be more difficult. I can see why using the USB when debugging is a problem, but what the code is running without debuging, why can't we use the USB back to a WIndows program? Next on my list is getting that data back to a website. Why can't I have my own website recieve temp data, and post it in a text box? Probably pretty easy on a Plus, but beyond me so far !

I can see why using the USB when debugging is a problem, but what the code is running without debuging, why can't we use the USB back to a WIndows program?

Actually, you can...it's just tricky. [A community member sent us a sample which turns the Netduino into a mouse of sorts...but then you have to get it back into "debugging mode".]

We've also created an HID comm channel which will work nicely; we'll release it once the Atmel USB glitch is fixed...and then it will be pretty straightforward.

Chris

CW2, I am attempting to give this latest one-wire firmware a run. I am confused because the ER_CONFIG and ER_FLASH files appear to be missing from the attachment in this thread. My guess is that the .proj files in the attached solution are supposed to build the files locally? However, the .proj aren't being recognized by my VS install so instead I am just getting directories listed, instead of projects. The local build of the .csproj files is working fine. I would greatly appreciate any guidance in getting the latest one-wire firmware files, either attached here or built locally.

I am attempting to give this latest one-wire firmware a run. I am confused because the ER_CONFIG and ER_FLASH files appear to be missing from the attachment in this thread.

Well, the attachment does not contain the firmware binaries, because it is based on rather old source code revision (4.1.0.3), which does not include certain features that are currently under development (e.g. PWM) and also all the bug fixes. If you are interested, I can build it and send it to you, if you don't mind the limitations.

I guess my confusion goes one layer deeper. I am trying to utilize your latest improvement attached in this thread, most notable search. In order to do that I thought I needed to deploy a special build of the firmware. Is it possible to use the search function with the stock firmware? Do the ER_CONFIG and ER_FLASH in the other thread work with the solution in this thread? If I do need a firmware version that is not present in the forums I would greatly appreciate if you could attach it here. Thanks for all your efforts in making it so easy to utilize this sensor on the Netduino platform.

I guess my confusion goes one layer deeper. I am trying to utilize your latest improvement attached in this thread, most notable search. In order to do that I thought I needed to deploy a special build of the firmware. Is it possible to use the search function with the stock firmware? Do the ER_CONFIG and ER_FLASH in the other thread work with the solution in this thread?

Unfortunately, it is not possible to use any 1-Wire functions with the stock firmware, because it does not contain the native driver. The old firmware will not work with the new source, because assemblies differ (the new one contains more functions), you will get 'invalid checksum' error during deployment.

If I do need a firmware version that is not present in the forums I would greatly appreciate if you could attach it here.

I have updated the original OneWire post, the attached archive now contains firmware binaries.