Netduino home hardware projects downloads community

Jump to content


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.

Andre Trollip

Member Since 18 May 2012
Offline Last Active Dec 30 2015 06:24 PM
-----

Posts I've Made

In Topic: Max Power of Vdc Rails

30 September 2014 - 07:23 AM

Thanks a lot for the clear explanation CW2. Appreciate it.

 

buy in the mean time I decided to power the component from a separate power source I'd probably need close to the limit. I'll rather play iy safe.

 

Ciao,

Andre


In Topic: Powering EasyDriver and Netduino

29 August 2014 - 11:54 AM

If you are worried that the driver board will feed current back to the 12V supply, then add a rectifier diode in the positive line between the battery and the driver so it can only take current - that should protect the Netduino from high voltages.

(Note that the EasyDriver circuit does not have any protection for its own logic supply, so I don't think they are expecting any problems like this. However they do have a 30V tolerant input.)

 

You might also add a similar diode to the Netduino supply input and add a big capacitor after the diode so that short brown outs are less likely to reset the Netduino.

 

Thanks a lot Paul. The feedback is exactly what I was worried about. I had the first diode in place and the cap as you recommend, but not the second one.

 

I will let you know how it turns out. I think I damaged the driver somehow because it stopped working at some point while I was fiddling. Waiting for a couple of new ones I ordered. At the same time I ordered some Polulu ones (Allegros A4988). I'd like to compare the two.

 

Thanks for your help.


In Topic: Microframework static constructor method

27 August 2014 - 12:05 AM

That would be perfectly safe and valid to do.


In Topic: Microframework static constructor method

26 August 2014 - 12:38 PM

As is the case with all class types, the type information for a static class is loaded by the .NET Framework common language runtime (CLR) when the program that references the class is loaded. The program cannot specify exactly when the class is loaded. However, it is guaranteed to be loaded and to have its fields initialized and its static constructor called before the class is referenced for the first time in your program.

To put it differently, the only guarantee that the CLR makes (with regards to static constructors) is that the static constructor will have run before any member (field, property or method) is accessed. Regardless of whether the accessed member is static or not. Other than that, you should not rely on a static constructor running at a specific point in time (or order).

 

As long as the CLR doesn't breach this principal, it can be implemented differently for the tinyCLR, .Net CLR, Any CLR etc. ;-)


In Topic: High Pass Filter

04 August 2014 - 06:28 PM

Hi Mario,

 

Thanks very much for this.

 

Yes I know it's not really subject appropriate, but I find I get more concise and quicker answers on electronic questions than on other electronics forums.

 

Thanks again.


home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.