Design surface like .NET Gadgeteer for Netduino GO?
#1
Posted 18 May 2012 - 05:09 PM
Here is a blog post showing how it works.
Has anyone given any thought to having this for Netduino GO?
#2
Posted 18 May 2012 - 10:26 PM
I believe it's considered, but instead we made auto detection of modules, so it actually doesn't matter how the modules are connectedHas anyone given any thought to having this for Netduino GO?
I kinda like that approach more, instead of "you can only plug module X in socket Y or it won't work (or even harm your device)"
- Arron Chapman likes this
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#3
Posted 21 May 2012 - 11:16 AM
I believe it's considered, but instead we made auto detection of modules, so it actually doesn't matter how the modules are connected
I kinda like that approach more, instead of "you can only plug module X in socket Y or it won't work (or even harm your device)"
How does this work?, if you connect two modules of same type, two buttons or two led's, how do you know which is which? are there unique serialnumbers on all modules? (cant see any evidence of that on my button?)
--
Asbjørn
#4
Posted 21 May 2012 - 04:08 PM
Two ways:How does this work?, if you connect two modules of same type, two buttons or two led's, how do you know which is which? are there unique serialnumbers on all modules? (cant see any evidence of that on my button?)
If I've put the buttons on sockets 2 and 4, and the leds on sockets 1 and 3;
NetduinoGo.Button btn1 = new NetduinoGo.Button(); // button on socket 2 NetduinoGo.Button btn2 = new NetduinoGo.Button(); // button on socket 4 NetduinoGo.RgbLed led1 = new NetduinoGo.RgbLed(); // led on socket 1 NetduinoGo.RgbLed led2 = new NetduinoGo.RgbLed(); // led on socket 3Or I could do:
NetduinoGo.Button btn1 = new NetduinoGo.Button(GoSockets.Socket2); NetduinoGo.Button btn2 = new NetduinoGo.Button(GoSockets.Socket4); NetduinoGo.RgbLed led1 = new NetduinoGo.RgbLed(GoSockets.Socket1); NetduinoGo.RgbLed led2 = new NetduinoGo.RgbLed(GoSockets.Socket3);
- Arron Chapman likes this
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#5
Posted 21 May 2012 - 11:15 PM
For a few more technical details on this...How does this work?, if you connect two modules of same type, two buttons or two led's, how do you know which is which? are there unique serialnumbers on all modules? (cant see any evidence of that on my button?)
Each module has a 128-bit device type UUID. When you connect to an RGB LED, for instance, the go!bus stack finds the first unused module with that device UUID.
We could also support connecting via device ID + serial number in the future...although that would be an optional feature for modules, not a required one.
Chris
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users