Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

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

zei0

Member Since 02 Jul 2014
Offline Last Active Jul 03 2014 01:39 PM

Find content

Posts I've Made

In Topic: obstacle detection

03 July 2014 - 11:36 AM

Paul,

I think the GO with a Shieldbase could easily achieve the same, maybe not as cheap but definitely doable.

Cheers Olaf

In Topic: Windows on Devices? When?

03 July 2014 - 11:36 AM

Hi All,

just registered on the windowsondevices web site, replied to their confirming email and some seconds later they replied again:

Quote: "Thank you for signing up for the Windows Developer Program for IoT. We�ll let you know when your kit has shipped."

So appearantly something has changed ....

Cheers,

In Topic: Mono bootloader for Netduino (and sample apps)

02 July 2014 - 03:17 PM

Hi Chris, What are the limitations of this method? I can get your two examples running but when I try to load a larger assembly it fails to run (no error is reported, netduino plus is unresponsive, runs when loaded in the traditional manor). I have put all the references that are used in the assembly into the bootloader program (necessary?) with no luck. Perhaps I need to do something differently when using multiple classes (also threading) or the memory foot print is now too large? Any help with this would be appreciated. Thanks again. Ryan Firmware v4.1.1 BETA 1 Traditional Method Total: (11856 RAM - 100832 ROM - 53025 METADATA) .pe file on SDcard (11KB) The debugging target runtime is loading the application assemblies and starting execution. Total: (12120 RAM - 101992 ROM - 53394 METADATA)

zei0

Community Stats

User Tools

Friends