Mark Anderson

You will need to create a web service to handle the SQL input.

 

I have created something similar using WCF REST. My netduino posts a JSON string to my service and then the service saves the values in the database.

Would you mind posting your solution (never done anything with REST or JSON before)

v2 of baord has been in design for the last few months,  will be able to show the new design by Feb.  Many imporvements and innovations

Cool. looking forward to it

Thanks Mario

Hi mark,

You could write a custom app using MFDeployEngine. Check out this command-line prototype we made for Mac and Linux--which would also work on Windows.

Or you could create a custom app like "Netduino Update" which flashes the board in bootloader mode. Or you could store the assemblies on a MicroSD card and then load them into RAM dynamically.

There are some additional methods which we're exploring for future versions of hardware/software (based in part on some work we're doing with AGENT)...and you could also hack into the Netduino firmware and build your own support.

Chris

Thanks Chris

This one sounds like the easiest option: "[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]Or you could store the assemblies on a MicroSD card and then load them into RAM dynamically"[/color]

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]I think it would be a killer feature for the Netduino to have a mechanism to check an update location and be able to do this automagically[/color]

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]Regards[/color]

[color=rgb(40,40,40);font-family:helvetica, arial, sans-serif;]Mark[/color]

You may find a lot of examples in the Internet. Here are some pretty well explained (and far better than my English-surrogate):

http://www.all-elect...ic/debounce.htm

http://www.eng.utah..../debouncing.pdf

 

A good hardware debounce circuit (i.e. filter) actually prevents false transitions (both edges) on the input pin. That's important, because you are using the interrupt, and on every edge the handler is called. That is, a lot of useless overhead.

So, if you want to use the interrupt, I'd recommend to implement a good hardware debounce circuit (2nd link, fig. 3 is the best one).

 

Since you probably won't like adding lot of parts (especially whereas you have many buttons), I'd suggest to avoid the interrupt and use a trivial polling. Let a dedicated thread running for all the buttons polling, then filter in a full-software fashion the actual inputs.

I bet on the far lesser overhead than the dozens of interrupt callback calls.

 

Good luck!

Thanks mario. i can't really use polling for my application. If I can't figure out how to disable interrupts, I'll go with a hardware option

Regards

Mark