I'm not sure why you are getting an exception in the Shieldbase dll, but you need to specify a pin for the Chip Select. 

 

http://www.netduino....o/schematic.pdf

 

If you're using a device connected to GoSocket 3 you would use (Cpu.Pin)4 as can be seen in the above schematic. 

 

Also, I and others have run into SPI bugs when running under ~3000 kHz. So you may want to up your speed. 

Thank you yogotie.

ST updated their website - all the links fro STDFU Test links are broken and I couldn't find good ones. 

It is a little ambitious, but you can create GoBus modules using other microprocessors as "modules". In doing this, you gain all the GPIO pins of the new microprocessor. 

 

I have done this with a Parallax Propeller and am also doing it with a Netduino Plus 2. Unfortunately, the code isn't public yet (it will be by April). If you are not interested in the wait and want to start writing your own drivers, don't be afraid to PM me for help. 

 

Also, keep in mind that every GoBus is essentially a SPI bus - if you find a SPI I/O expander you could talk directly to it over the GoBus - granted, you will have to write a custom driver and will lose the benefits of GoBus 1.5/2.0. 

 

Good luck!

Paul you were absolutely correct, I changed the values to > 0x20 and now it's working, thanks a lot.  

 

Chris - not that it matters but it's the Adafruit FTDI Cable

Yes, I flipped the wires and nothing changed. 

I am trying to get a Netduino Plus 2 to communicate with PuTTy.

 

using System;using System.Net;using System.Net.Sockets;using System.Threading;using Microsoft.SPOT;using Microsoft.SPOT.Hardware;using SecretLabs.NETMF.Hardware;using SecretLabs.NETMF.Hardware.Netduino;using System.IO.Ports;namespace NetduinoPlusRx{    public class Program    {        static SerialPort port;        public static void Main()        {            // write your code here            port = new SerialPort(SerialPorts.COM2, 115200, Parity.None,8,StopBits.One);            port.Open();            while (true)            {                port.Write(new byte[] { 0x01, 0x02, 0x03 }, 0, 2);                Thread.Sleep(100);            }        }    }}

 

PuTTy isn't picking up anything. I have an FTDI cable with Ground connected to Ground, and Rx/Tx connected to pins 3/2. 

 

Any thoughts/obvious errors?

 

Hello,

 

I have a Netduino Go and a Netduino+2 both connected to my computer and Visual Studio refuses to deploy code to them. 

 

However, if only one is connected at a time then code deploys fine. 

 

In 'Device Manager' they both show up as "Netduino". 

 

Is there a workaround to have multiple Netduino's be programmed from one machine at the same time? Or do I have to program them individually?

 

Thanks,

bsilvereagle

ALOK

 

You will need something on the computer COM ports sending the wireless and something on the Netduino deciphering it. 

 

XBee's have the potential to do this if the Netduino's can be programmed on the serial lines (not sure if they can be). 

Steve,

 

http://www.amazon.co...y/dp/1430224533

 

Has all the information you need to reverse engineer the NXT sensor i2c if I remember correctly. It's on a bookshelf that's not in my dorm so I can't double check. 

2. For existing shields which use I2C, you'll want to connect jumper wires between SDA/SCL and A4/A5 for the moment. We're working on an enhancement for the I2C class which will mirror the I2C data on A4/A5 by default (and also turn off the mirroring...so you can get two extra GPIOs instead). That new feature will be available in a December firmware update, giving us the best of both worlds. The same firmware update will bring I2C to Shield Base.

I am using a Shield Base with a Netduino go and was wondering when I2C was going to be implemented. Is there a firmer date than "December" from the above quote? Or if there was an alpha/beta firmware that already implemented I2C for the shield base.

Thanks for all the good work.