The moles will be anywhere from 10 yards to 35 yards from the central controller and up to 10 yards from each other.

I'm at the conceptual stage of a project and would like some advice. The project can best be described as a game. The "Whack-a-Mole" game is a pretty close approximation of what I'm trying to do except the "moles" are further apart. If you don't know what this game is, watch this 22 seconds of video: https://www.youtube....h?v=D0n8N98mpes

There will be n number of devices in the network and one master controller. I'm thinking the controller will be a laptop, but I'm open to other ideas.

Each device will "display" according to an algorithm running on the master controller. If the mole is whacked while its displayed, a signal should be sent back to the master controller with the time it was whacked.

So my question is what is the best way for the master controller to communicate with the moles? After doing some research, it seems to me that each mole should be an N+2 with a Edimax BR-6258n wireless router running the NeonMika webserver. However, my concern is speed. Would Bluetooth be a better option or maybe one of the Xbee protocols? What about using a Mini instead of a N+2?

I'm in the process of converting a PLC application over to the Netduino in order to reduce cost. I've been using Crouzet PLC's but they are too expensive and have too little RAM. The Netduino with a keypad, 2 line LCD and a cheap 4 relay board will do what I need at a fraction of the cost.

It looks like this wiring diagram may have been for the N+: http://netmftoolbox....ailable classes

The N+2 has pins SC and SD. When I wired my RTC to these pins, everything worked.

I purchased this RTC: http://www.adafruit.com/products/264

But when I go to set the time using the Toolbox.NETMF.Hardware.DS1307 I get the following error:

"Something went wrong setting the time. Did you use proper pull-up resistors and is there a 3V battery connected?"

The wiring is pretty simple and I've double checked it (see pic).The kit has the resistors and the battery, any ideas?

Here is the code where it fails:

DS1307 RTC = new DS1307();

RTC.SetTime(2013, 7, 29, 23, 14, 0);

here is the toolbox code where the call is throwing an exception

public void SetTime(DateTime Time)

{

// Writing 7 bytes to the buffer, starting at address 0

int BytesTransferred = this._Device.Write(new byte[] {

0x00,

(byte)Tools.Hex2Dec(Time.Second.ToString()),

(byte)Tools.Hex2Dec(Time.Minute.ToString()),

(byte)Tools.Hex2Dec(Time.Hour.ToString()),

(byte)Tools.Hex2Dec(((int)Time.DayOfWeek).ToString()),

(byte)Tools.Hex2Dec(Time.Day.ToString()),

(byte)Tools.Hex2Dec(Time.Month.ToString()),

(byte)Tools.Hex2Dec((Time.Year - 2000).ToString())

});

if (BytesTransferred != 8) throw new ApplicationException("Something went wrong setting the time. Did you use proper pull-up resistors and is there a 3V battery connected?");

}

Thanks Grant, I'll check this out when I get back from my out-of-town trip!

When I finally took the time to figure out how the breakout board was wired to the IC, it became more obvious how to wire it up. Thanks for all your help!

Grant,

Ok, I have wired SER_IN to pin 11

L_CLOCK to pin 10

/OE to gnd

/reset to Vcc

But there is one more pin on the breakout board, (CLOCK) that I'm not sure what to do with. Please see my wiring diagram. I would like to control each LED seperately.

Thanks for the reply Grant. Yes, I figured this out myself after you pointed me in the right direction.

Can someone point me to an example of using this breakout board with the Netduino?

https://www.sparkfun.../products/10680

I would like to use the .Net Microframework Toolbox, but it's not obvious to me how to wire it up.

http://msdn.microsof...y/ee434782.aspx

socket.listen(backlog)

backlog = The maximum number of incoming connections that can be queued for acceptance. Try

serverSocket.Listen(10);

Thanks for the quick reply Chris. Do I also need to change the AssemblyVersion in AssemblyInfo.cs?

I've upgraded to vs2012, .netmf 4.3 and flashed the firmware successfully. I've upgraded my projects and their references to the 4.3 dlls, but when I go to deploy my programs the I'm getting errors with the .net microframework toolbox. I downloaded the 4.3 DLLs but I'm getting the following.

Hi cce1911,
 

In each project, go to project properties (right-click on the project name, select the "properties" menu option).

Then change the "Target Framework" from NETMF 4.3 to NETMF 4.2. It will probably close the window for you when you do this, to save the changes.

Then change the target framework back to NETMF 4.3.

Repeat the above for each project. If there are forty, it may take you 15 minutes. Tedious and no fun, but it should change everything from 'pre-production 4.3' to 'production 4.3.1' for you.

Now

Chris,

I just wanted to let you know that I was able to resolve my problem by compiling the toolbox with the 4.3.1 code.

-Capel

I have downloaded the source, but I'm not real sure how to upgrade it to 4.3.1. Do I have to change the target framework on all 40 projects? Do I have to manually edit the AssemblyInfo files and change AssemblyVersion("4.3.1.0")?

Am I missing something? I downloaded the N+2 Version (10.12.12) and have it running,  but I can't create the "network name". Its not a parameter in

Server WebServer = new Server(PinManagement.OnboardLED, 80, false, "192.168.1.25", "255.255.255.0", "192.168.1.1");

[font="arial, helvetica, sans-serif;"]Does the N+2 version have this?[/font]

What version of Visual Studio is this built in? I get an error saying the project is incompatible with VS2010.

I have code that works fine when running on N2, but when I run the same code on the N2+ I get a System.ArgumentException on this line of code:

// Input Trigger - This input starts the cycle

InterruptPort inpTrigger = new InterruptPort(Pins.GPIO_PIN_A5, true, Port.ResistorMode.Disabled, Port.InterruptMode.InterruptEdgeLow);

It is simply a button to start my program running.

BTW I am using:

using SecretLabs.NETMF.Hardware.NetduinoPlus;

Any suggestions?

-Capel

Upon closer examination, here is the debug output:

A first chance exception of type 'System.ArgumentException' occurred in Microsoft.SPOT.Hardware.dll

A first chance exception of type 'System.ArgumentException' occurred in Microsoft.SPOT.Hardware.dll

An unhandled exception of type 'System.ArgumentException' occurred in Microsoft.SPOT.Hardware.dll

Any suggestions?

Ok, so I referenced

using SecretLabs.NETMF.Hardware.Netduino;

and I still get the same exception.

I next tried moving the button assignments around and now I get the same exception, but on a [font="arial, helvetica, sans-serif;"]different InterruptPort assignment.[/font]

[font="arial, helvetica, sans-serif;"]Keep in mind that I'm moving from a Netduino 2 to a Netduino + 2. Chris' post refers to N+ to N+2.[/font]

This was a strange issue and I never did figure out why the N2 code would not run on the N+2, I did find a work around.

Basically, I defined the input using the Auto-Repeat button (http://forums.netdui...n-press-sample/) and it worked. Don't ask me why this worked, but it did.

I found the problem with my code. In the server app, the 2nd while loop should have had totalread instead of 0 for the second parameter of the .receive call. I was overwriting the data each time. Maybe this will help someone in the future...

Zero, so far I have only tested with a single client.

If I look at the byte array data, after receiving all the data, every byte above 255 has a value of 0. It's as if it stops reading at 255. If I debug.print in the while loop filling "data", I get the following output:

client accepting data client.Receive sizeinfo: currentread = 4, totalread = 4 total message size = 3296 client.Receive data: currentread = 252, totalread = 252 client.Receive data: currentread = 256 totalread = 508 client.Receive data: currentread = 256 totalread = 764 client.Receive data: currentread = 256 totalread = 1020 client.Receive data: currentread = 256 totalread = 1276 client.Receive data: currentread = 256 totalread = 1532 client.Receive data: currentread = 256 totalread = 1788 client.Receive data: currentread = 256 totalread = 2044 client.Receive data: currentread = 256 totalread = 2300 client.Receive data: currentread = 256 totalread = 2556 client.Receive data: currentread = 256 totalread = 2812 client.Receive data: currentread = 256 totalread = 3068 client.Receive data: currentread = 228 totalread = 3296 client.Receive data final: currentread = 228 totalread = 3296

So it is accepting 256 bytes each time, but they are all zero. Obviously, I don't understand what's going on:(