Netduino home hardware projects downloads community

Jump to content

The Netduino forums have been replaced by new forums at This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.

Dr Who

Member Since 08 Jun 2012
Offline Last Active Aug 16 2017 05:23 PM

#65163 Can a Netduino model 1 power external logic directly?

Posted by Dr Who on 04 June 2016 - 03:38 PM


As the topic subject asks, "Can a Netduino model 1 power external logic directly?". I've a new design taking shape, and whilst I know that when running a device via USB to program it, the answer would be "No.",but what happens afterwards?


This would be ordinary TTL stuff, circa 1980.


Incidentally I've successfully mounted it inside a "Project Enclosure kit" from Radio Shack. Plus a prototyping shield as designed by Makershed. 

#65104 Driving relay coils using a Netduino

Posted by Dr Who on 27 April 2016 - 01:32 PM


New project time here. Right now I have running a Netduino using an edited form of one of my PAL driver programs to talk to an SN7437 wired to send the output of the first gate to go to the second's first input. There's also a red LED attached to first's output. The one for second is connected to a SSR who's activating the 24V coil in the counter.

Here's my code:

using System;
using System.Threading;
using Microsoft.SPOT;
using Microsoft.SPOT.Hardware;
using SecretLabs.NETMF.Hardware;
using SecretLabs.NETMF.Hardware.Netduino;

namespace palout4
    public class Program
        public static void Main()
            // write your code here
            OutputPort i0 = new OutputPort(Pins.GPIO_PIN_D2, false);
         //   OutputPort i1 = new OutputPort(Pins.GPIO_PIN_D3, false);
         //   OutputPort i2 = new OutputPort(Pins.GPIO_PIN_D4, false);
         //   OutputPort i3 = new OutputPort(Pins.GPIO_PIN_D5, false);
         //   OutputPort i4 = new OutputPort(Pins.GPIO_PIN_D6, false);
         //   OutputPort i5 = new OutputPort(Pins.GPIO_PIN_D7, false);
         //   OutputPort i6 = new OutputPort(Pins.GPIO_PIN_D8, false);
         //   OutputPort i7 = new OutputPort(Pins.GPIO_PIN_D9, false);
          //  OutputPort i8 = new OutputPort(Pins.GPIO_PIN_D10, false);
         //   OutputPort i9 = new OutputPort(Pins.GPIO_PIN_D11, false);
         //   OutputPort i10 = new OutputPort(Pins.GPIO_PIN_D12, false);
         //   OutputPort i11 = new OutputPort(Pins.GPIO_PIN_D13, false);
            while (true)
             //   i1.Write(true);
             //   i2.Write(true);
             //   i3.Write(true);  
             //   i4.Write(true);  
             //   i5.Write(true);  
             //   i6.Write(true);  
             //   i7.Write(true);  
              //  i8.Write(true);  
         //       i9.Write(true);
            //    i1.Write(false);
            //    i2.Write(false);
            //    i3.Write(false); 
            //    i4.Write(false);
            //    i5.Write(false);
            //    i6.Write(false); 
            //    i7.Write(false); 
          //      i8.Write(false);
          //      i9.Write(false);
              //  i1.Write(true);
              //  i2.Write(true);
              //  i3.Write(false);  
              //  i4.Write(false);
              //  i5.Write(false); 
              //  i6.Write(false); 
              //  i7.Write(false); 
         //       i8.Write(true);
         //       i9.Write(true);
          //      i1.Write(true);
          //      i2.Write(true);
          //      i3.Write(false); 
          //      i4.Write(false); 
          //      i5.Write(false); 
          //      i6.Write(false); 
          //      i7.Write(false); 
         //       i8.Write(true); 
         //       i9.Write(true);
         //       i8.Write(false);
         //       i9.Write(false);
         //       i1.Write(false);
         //       i2.Write(false);
         //       i3.Write(false);
           //     i4.Write(false);
          //      i5.Write(false);
          //      i6.Write(false);
          //      i7.Write(false);
          //      i8.Write(false);
          //      i9.Write(false);
           //    i1.Write(true);
           //    i2.Write(true);
           //    i3.Write(false); 
           //    i4.Write(false); 
           //    i5.Write(false); 
           //    i6.Write(false);
           //    i7.Write(false); 
         //       i8.Write(true);
         //       i9.Write(true);
         //       i1.Write(false);
         //       i2.Write(false);
         //       i3.Write(true);
         //       i4.Write(true); 
         //       i5.Write(true);
         //       i6.Write(false);
         //       i7.Write(false);
         //       i8.Write(false);
         //       i9.Write(false);

I'm keeping the format that I found worked for the earlier efforts, however it's the driving circuits that I'm stuck on. That one I described is the first one I tried. So naturally it worked.


Oddly enough the circuit refused to work with a Basic Stamp2 device.

#64966 I broke the forum at this location, please HELP!!!

Posted by Dr Who on 07 March 2016 - 02:48 AM

Simple really, report it to the webmaster. That person will have to repair the damage caused by the system. You are not at fault here.

#64012 Discussion on the Parallax Forum regarding the boards used here

Posted by Dr Who on 01 September 2015 - 04:05 AM


Inside the Parallax Forum one user posted an interesting and wrongly phrased post regarding the Netduino, which is here:


Eventually he gets set right, and naturally people discuss a couple of points regarding a comparison between the N1 and the Mini, and then N2 and finally the N2P, but the N3 wasn't mentioned.


The interesting issue is that the people eventually realize that the comparison between the Propeller and the Netduino is an Apple and a big crate of Oranges issue.


I strongly suggest reading it before responding. I leave for the reader a guess who this Buck Rogers is.

#63472 Getting started with Netduino Mini (early instructions)

Posted by Dr Who on 13 July 2015 - 04:33 AM

After several months, trying this again :-). Reset my mini by applying 5v to the gold erase pad, attempted to connect via SAM-BA and it says "no valid processor found". 


I am connecting via FTDI breakout USB cable in 3.3V mode:

- ground to pin 23

- 3.3V to pin 21

- RXD from breakout board to pin 11

- TDX from breakout board to pin 12



Any thoughts?


Well yes. When uploading fresh firmware to the little guy, the user needs to connect to the RS232 points at RS232 levels. The FTDI breakout produces TTL: or CMOS compatible output levels. So you'd need USB to RS232 adapter to do that. I normally use one for the Basic Stamp gang to make it work since its within four solar diameters of the specifications in the FTDI datasheet for just such a design. It also expects 5v at the positive voltage connection when working. The TTL management connections are fine for sending it the firmware for TTL stuff although you might need to do the same thing as you just did for the regular fresh firmware for it.


I expect Chris will chime in with appropriate things as soon as he's around.

#63103 What is the latest firmware version for Netduino 1

Posted by Dr Who on 10 June 2015 - 09:05 PM

But what would be involved in shaping 4.3 to work on gen1 hardware? Is it flash space? Or and this is the more difficult to answer question, the way the hardware is constructed?


I once got into (via e-mail no less) a discussion concerning Linux and its differences across architectures. Suffice to say the proponent for System Z won it, and not because he's an excellent speaker on that subject in real life. It turns out that the only difference between Linux on Intel and the same bird on System Z is just the hosting architecture. And in fact whole teams spend their days working out how to move the work-load from one to the other, and thence free up on-time on the Intel box to stuff that can only be run on it properly.


Look at it this way, what is involved in translating a function from the Arduino to the Netduino? There are plenty involved here, too many to list in this venue, but to put it simply, the dialect that the Arduino, ah, speaks. isn't the same as the one the Netduino normally,ah, speaks.



Now Chris what's with the gentleman who is quite tall, and wearing worn out clothes and a very long striped scarf, along with a big brimmed hat and a very pretty, but some what below average young lady, and both staring into your shop?

#63050 Netduino and BS2 working together to solve problems

Posted by Dr Who on 04 June 2015 - 04:52 PM


My latest accomplishment, is to have a Netduino 1, wearing a BOE Shield from Parallax poking an installed part, blinking LEDs, and then sending the output to a BS2.


That Parallax BS2 also mounted on its own BOE (Board of Ed, so named because they were frequently used in schools until fairly recently.) is receiving the data and sending to an attached LCD display.




I invite comment.

Attached Files

#62086 Netduino Mini not playing nicely with SAM-BA 2.15

Posted by Dr Who on 12 April 2015 - 04:49 PM

Ive run into a wall attempting to upgrade my Netduino Mini from NetMF 4.1 to 4.2.


I've learned that the bootloader will need to be updated before upgrading from NetMF 4.1. I learned Ill need to use SAM-BA to install the bootloader, and I can only flash the Mini over its RS232 serial interface (not its TTL interface)


The theorys great, but things seem to come unstuck for me when I try to use SAM-BA.


I followed these setup steps:

  1. Completely reset the Mini with 5v to the tiny reset pad for ~1 second. 
  2. My laptop does not have native serial RS232 so Ive set up for the bootloader flash with a USB->RS232 FTDI breakout board. Board RX connected to Mini TX. Board TX connected to Mini RX. Board Gnd connected to Mini Gnd. My setup looks pin perfect to Frodes.
  3. Powered up the Mini with 9v to pin24 and Gnd to pin23. The obligatory breadboard LED glows to confirm that I had indeed provided power to the device
  4. Checked all the COM settings were good, 115200 8 N 1
  5. Run SAM-BA 2.15, selected the FTDI-presented COM port (the only COM port listed), selected AT91SAM7X512-EK, and hit Connect

Theres a flurry of TX/RX traffic on the FTDI LEDs and then SAM-BA returns a dialog titled Invalid Chip ID. I get the same dialog when any AT91 device is selected in step 5.


Thinking that my Mini could be dead, I lifted it from the ZIF socket and tried again checking the RX/TX LEDs. This time there was no RX traffic, which Ive interpreted as meaning the Mini is alive and can respond to SAM-BA when I click the Connect button.


Ive googled until Chrome shows every  relevant link in purple (been there, read that!).. so now Im kinda stuck.


Id be stoked to hear anyones wisdom on this topic. Thanks in advance!



First things first. Did you follow everything in that thread? I bumped, and hard as well, into the same issue with mine. I found that it would need to be power-cycled and that means to turn the board off, wait a few moments, and turn it back on. Then follow the deployment steps.


Incidentally the Wiki describes exactly how the tool is supposed to be configured, also that you're supposed to connect to it, the Mini via an RS232 connection. Since most modern systems do not have them that means we need to use proper Serial from USB adapters, and oddly enough FTDI makes the proper chip for that. You then need an adapter who embodies that design. Oddly enough a company in California (USA) makes an adapter for that purpose, normally useful for programming their devices who still use Serial as a deployment method.


Here are the links for the adapters: (That one has the working cable enclosed.) (That one does not have the working cable enclosed.)


Depending on where you are based, a store front firm named Micro Center sells the first entry directly. They are also recognized sellers for NetDuino devices which I find supportive. They also sell Parallax items and even those dratted things which our hosts based the shape of the others on. 


The reason why I'm pushing the use of those items is that the adapter you chose, which is a breakout board probably designed by Sparkfun, translates the signals into TTL levels, a second chip, which is a MAX232 chip translates them into those idiotic RS232 voltage levels. Frode's idea may have used one that they make which coincidentally is functionally equivalent to the two I name, (The FTDI company that is.) The SPFE breakout board which I use here also, is just the front end, the MAX232 does the heavy lifting and the final voltage translation.


So in conclusion to completely solve your problems you need to be using either of those two adapters, and then a DB9 connector connected to it, and the appropriate pins connected to the Mini, which is an easy summary. 


And more important is that the photo he supplied, doesn't show the full features behind the adapter he chose. So I've provided both. (I have both here. One was bought before the other.)


Incidentally Chris you can pay me Tuesday for the reply today.

#61512 Things we can learn from GHI

Posted by Dr Who on 04 February 2015 - 05:54 PM

And Microsoft did not drop the Framework. They just redid their site and created a new series of releases for later releases of VS. 

#54144 Interrupts and Events Continue Firing

Posted by Dr Who on 18 November 2013 - 04:34 AM

Well yes.

Mouser. Also Digi-Key. And then Jameco.


Be warned Mouser loves hobbyists. Digi-Key doesn't mind them. And Jameco is still trying to figure them out. In the case of Jameco, should you decide to buy something from them, be prepared to buy a lot of items you might need. Even if that need is months to years later.

#54121 Raspberry Pi and dot Net MicroFramework

Posted by Dr Who on 17 November 2013 - 12:01 AM


Theoretically this belongs over on the Mono forum area, but it really belongs anywhere.... Mark offered a suggestion as it applied to my problem of configuring a Netuduino to communicate with a Raspberry Pi. The idea came from one individual's idea to use his as an HDMI shield for an Arduino.


Inside this blog happened to be two references. One was to a library and header for the Pi itself. The second was this one for the Visual Studio it builds properly on Visual Studio 2012 Desktop express. And not on Visual Studio 2010 Express. As it happens that second one, a complaint is for C Sharp of course. There are issues with it.


The author shows an example, I managed to get it to build on VS2012, but since I do not have any of the SDK pieces installed for Visual Studio 2012 I didn't manage to get it built that way, it was built as a regular one.


Strangely enough it worked via mono on the Pi.


So the question now becomes, what happens when someone installs the SDK pieces for Visual Studio 2012 and did not remove the ones for Visual Studio 2010?


And suggestions are appreciated for at least being able to build the simple blink example in VS2010 since that's the one release of Visual Studio for building stuff on MicroFramework I understand.

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.