stacyh3's Content

#198 TMP36 Temperature Sensor/SB Protoshield

Posted by stacyh3 on 10 August 2010 - 08:29 PM in Netduino 2 (and Netduino 1)

P.S.

We could add an "internal 3.3V analog reference" option in a future board revision. Would that be a valuable feature for everyone here? We'd make it optional and selectable in code.

Chris

It seems like this would be useful. Especially so for people who are "porting" Arduino projects.

Stacy

#317 SerialPort class?

Posted by stacyh3 on 12 August 2010 - 07:25 PM in Netduino 2 (and Netduino 1)

Hello all, I have included a reference to System.IO and a using statement for System.IO.Ports, but the SerialPort class doesn't show up. What am I missing? I'm sure it's probably something simple that I'm overlooking. Thanks!

#318 SerialPort class?

Posted by stacyh3 on 12 August 2010 - 07:28 PM in Netduino 2 (and Netduino 1)

Oh yes, and I tried other references like Microsoft.SPOT.IO. Oh SerialPort, come out, come out wherever you are!

#319 SerialPort class?

Posted by stacyh3 on 12 August 2010 - 07:30 PM in Netduino 2 (and Netduino 1)

Sorry for the traffic, but I just found it. Microsoft.SPOT.Hardware.SerialPort in case anyone else is looking. csh

#761 I2CDevice protocol

Posted by stacyh3 on 18 August 2010 - 03:37 PM in Netduino 2 (and Netduino 1)

I've been working with the DS1307 Real Time Clock mounted on the SparkFun breakout board. In reading data from the clock, I am able to use the following code successfully:

            // Go to address zero.
            transaction = new I2CDevice.I2CTransaction[]
            {
                I2CDevice.CreateWriteTransaction(new byte[] {0})
            };

            result = clock.Execute(transaction, i2c_timeout);

            // Read data
            var data = new byte[7];
            transaction = new I2CDevice.I2CTransaction[]
            {
                I2CDevice.CreateReadTransaction(data)
            };

            result = clock.Execute(transaction, i2c_timeout);

It appears that you should be able to do something like this:

            // Read data
            var data = new byte[7];
            transaction = new I2CDevice.I2CTransaction[]
            {
                I2CDevice.CreateWriteTransaction(new byte[] {0}),
                I2CDevice.CreateReadTransaction(data)
            };

            result = clock.Execute(transaction, i2c_timeout);

This would combine the write to the clock to set the address and the read to get the data. This causes the netduino to freeze and requires me to unplug the clock and erase the netduino code. I'm okay with doing this in two steps, I'm just curious if it's "supposed" to work in one combined transaction.

Thanks!

Stacy

#766 I2CDevice protocol

Posted by stacyh3 on 18 August 2010 - 05:27 PM in Netduino 2 (and Netduino 1)

Very curious. It should work as a single step (and in fact, that's the preferred way to do it with I2C). We tested the RTC on the Adafruit Datalogger shield using the I2C feature similarly and it worked well... We'll get one of these in the lab and run it through the logic analyzer and debugger to see what's going on

Is this the board you're using?

Chris

Yes, that's the board. And I am using the latest netduino firmware with the analog fixes. It almost feels like a timing issue. Like the read may be happening to quickly after the write. of course, that's just a gut feel, since things seem to work fine when I separate the calls.

My connection are 5V and ground as indicated. SCL to Analog 5, and SDA to Analog 4.

Thanks! Let me know if there's any further debugging I can do.

Stacy

#812 Reading Serial Connection

Posted by stacyh3 on 18 August 2010 - 11:22 PM in Netduino 2 (and Netduino 1)

Check out this thread: Serial Port Class. I had the same problem. You need to add a referennce to the Microsoft.SPOT.Hardware.SerialPort assembly. It has part of the System.IO.Ports namespace in it.

Let me know if you need any more help.

Stacy

#853 I2CDevice protocol

Posted by stacyh3 on 19 August 2010 - 04:52 PM in Netduino 2 (and Netduino 1)

I think I may have found my issue. One of my pull-up resistors was not connected corectly. I usually double check my hardware connections since I'm a hardware novice, but I missed this. Thanks to a magnifying glass, I found the issue. Now the RTC chip is responding reliably every time and I can combine I2C read and write transactions. Yay! I'll keep testing to make sure that there wasn't some other anomaly. Thanks, Stacy

#1002 TMP36 Temperature Sensor/SB Protoshield

Posted by stacyh3 on 21 August 2010 - 11:32 PM in Netduino 2 (and Netduino 1)

yes please

Selectable in code would be cool.

I also had a question about pull-up resistors. In wiring my I2C clock chip, I used external pull-up resistors. Is it possible to use the internal pull-up for this? I'm not really using the pins as input per-se, but if I plug in an I2C device, it likely needs pull-up resistors. Yes, I'm a hardware newbie... I'll bet it shows. :rolleyes:

Stacy

#1266 .NET micro Framework device

Posted by stacyh3 on 25 August 2010 - 01:14 AM in General Discussion

My 2 cents, I like the idea of a variety of boards. If I need Ethernet in my project, I'd choose that one. If not, then I'd choose the base model. Some things can be done with "shields", but having them integrated is cleaner and smaller. Stacy

#1267 Electronics Books

Posted by stacyh3 on 25 August 2010 - 01:23 AM in General Discussion

Hey everyone,

I'm a long time developer and very new to electronics. Can anyone recommend any books on the subject matter to get me up to speed?

I'm in the same boat. This book has been fan-freakin-tastic: Make: Electronics

Stacy

#1285 I2CDevice protocol

Posted by stacyh3 on 25 August 2010 - 01:26 PM in Netduino 2 (and Netduino 1)

I can post the code later today. Eventually this will be part of a larger project that I'll also share with the community. It's still pretty rough at this point, but it does work

Stacy

#1366 DS1307 Real Time Clock

Posted by stacyh3 on 26 August 2010 - 10:15 PM in Project Showcase

Attached is some code for using the DS1307 Real Time Clock chip via the I2C bus. The code includes a simple test application. Nothing facny, but it works. It also shows the use of extension methods which are pretty handy. The code comments include instructions on connecting the DS1307. Also, I scavanged an old ribbon cable and soldered one end to the SparkFun breakout board for the clock chip. I added pins to the other end to make is easy to use for prototyping. I figured that when I mounted this into a project box, it would be handy as well since it will allow easy access to the backup battery. Enjoy! Stacy

Attached Files

RealTimeClockTest.zip 9.93KB 934 downloads

#1367 BlinkM

Posted by stacyh3 on 26 August 2010 - 10:20 PM in Netduino 2 (and Netduino 1)

I was running into some odd issues too. It turned out to be my pull-up resistors. I guess most people know to double check this, but I figured I suggest it anyway. Stacy

#1376 I2CDevice protocol

Posted by stacyh3 on 27 August 2010 - 12:34 AM in Netduino 2 (and Netduino 1)

I can post the code later today. Eventually this will be part of a larger project that I'll also share with the community. It's still pretty rough at this point, but it does work

Stacy

The code is posted in the projects section.

Stacy

#1563 Feedback on proposed SD card mounting functions...

Posted by stacyh3 on 31 August 2010 - 12:21 PM in Beta Firmware and Drivers

This would be very useful. I assume that I would attach an interrupt to the card detect pin to determine when the card is inserted/removed. Stacy

#1632 Motor Control in an Airsoft gun

Posted by stacyh3 on 01 September 2010 - 04:12 PM in General Discussion

Hello all,

I'm pretty new to electronics and still developing basic design skills (I'm a software person). I'm hoping someone can give me some simple guidance.

My son and one of his friends are modifying an electric airsoft gun so that the firing mechanism is controlled by a microcontroller. They want to be able to have the trigger be a button press that the microcontroller reads and depending on the programming will activate the motor in the airsoft gun. There's a little lever in the gun that moves each time the gun is fired. By adding another switch that this lever will hit, we can count how many times the gun has fired. The microcontroller can then be programmed to give us variable bursts when firing.

My questions are:

Does this seem reasonable so far?
What's the best way to control the motor?
Should we use a MOSFET or a solid state relay? What are the practical differences in the two?
Anyone care to venture a circuit diagram that will help us?

I realize that being new to this, my questions may not all be well-formed, but I'm hoping this will get us moving in the right direction.

Thanks,
Stacy

#1640 Motor Control in an Airsoft gun

Posted by stacyh3 on 01 September 2010 - 07:40 PM in General Discussion

Thanks! I'll check out those links. I'll take all the knowledge I can get on this one. If anyone else has thoughts, please chime in. I'm going to try to get some photos of the mechanism in the airsoft gun. It's all very heavy and mechanical. I'm also worried about how we're thinking of using a moving lever to tap a switch that will count shots. If we can get that and the motor control nailed, then the rest is just software. Stacy

#1654 Motor Control in an Airsoft gun

Posted by stacyh3 on 01 September 2010 - 08:58 PM in General Discussion

Yes, those ideas make more sense than the switch. I'll take another look at the lever in the gun to see what we can do. This is fantastic help. Thanks very much!

The motor is this one: ICS Turbo-3000. I haven't found an actual spec sheet yet. We just need to control on/off really.

I also ran across this: Using a transistor to control high current loads with an Arduino which seems like it would work.

Thanks again!

#1659 Motor Control in an Airsoft gun

Posted by stacyh3 on 02 September 2010 - 01:18 AM in General Discussion

Okay. I'm starting to understand a bit more. I'll ask my son and his friend to look on the motor itself for any additional specs, and I'll look at the types of transistors you mentioned. I appreciate the great explanations! It makes this fun for novices like me when we get such great help. Thanks! Stacy

#1670 Motor Control in an Airsoft gun

Posted by stacyh3 on 02 September 2010 - 10:57 AM in General Discussion

Very cool! Thanks! I'll keep this thread up to date as we make progress. Stacy

#1674 Metal Detector Robot

Posted by stacyh3 on 02 September 2010 - 02:15 PM in General Discussion

I just need more time!!!
I want to make one of these: Metal Detector Robot. This would be so cool with a Netduino with Ethernet. Imagine a little web service on the device that would give PGS coordinates of the found items and you could use on a laptop to see the location in Bing Maps.

So many cool things!!!

#1707 Serialization

Posted by stacyh3 on 02 September 2010 - 10:29 PM in Netduino 2 (and Netduino 1)

Reflection.Serialize/Deserialize seems to work fine in the emulator, but not on the actual hardware. Is it not implemented in the release? Is it planned? Thanks, Stacy

#1735 Serialization

Posted by stacyh3 on 03 September 2010 - 12:23 PM in Netduino 2 (and Netduino 1)

I don't think Serialization is available on any of the .net platforms (Netduino or Fez). Besides, for a microcontroller serialization is SLOW.

Slow depends on the application don't you think? For my application it's okay it it's a bit slow. I need to deserialize once at startup and then the intervals between serialization are pretty long - on the order of minutes to hours.

In any case, if people are using the emulator, be aware that Reflection.Serialize and Reflection.Deserialize work fine, but they appear not to be in the Netduino firmware. This is not a major problem for me since I just implemented my own code for what I need, but it's good to know what's there and what's not.

#1874 Real Time Clock

Posted by stacyh3 on 07 September 2010 - 12:04 AM in Netduino 2 (and Netduino 1)

And of course, if you're using the DS1307, check out my post w/code here: DS1307 Real Time Clock.

This clock is pretty inexpensive and works well. I'm sure that there are better ones out there with alarms, etc.