PWM version
#1
Posted 28 February 2012 - 03:29 PM
#2
Posted 30 June 2012 - 03:15 AM
#3
Posted 30 June 2012 - 07:23 AM
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#4
Posted 18 August 2012 - 08:52 AM
With the 4.2 beta for Netduino Classic/Plus you would need Secretlabs.NETMF.Hardware for the PWM class. best to not reference to Microsoft.SPOT.Hardware.PWM.dll
Does this apply to the final release of the 4.2 framework as well?
I thought that new PWM and AnalogInput classes are suppose to better... if there is not way to use them, it kind of defeats the purpose
#5
Posted 18 August 2012 - 10:19 AM
#6
Posted 18 August 2012 - 11:54 AM
The final release includes the new AnalogInput and PWM classes by default. If you want to use the legacy ones, you can pull those in by explicitly adding them as references to your project.Does this apply to the final release of the 4.2 framework as well?
I thought that new PWM and AnalogInput classes are suppose to better... if there is not way to use them, it kind of defeats the purpose
Chris
#7
Posted 18 August 2012 - 02:44 PM
The final release includes the new AnalogInput and PWM classes by default. If you want to use the legacy ones, you can pull those in by explicitly adding them as references to your project.
I understand that there are two PWM classes one could use in his project, but i'm wondering which is better.
In my current project, i'm trying to build an IR emitter with a 38KHz carrier.
the Netduino PWM class can supply this frequency (SetPulse(26,8) for example) but modulating it is a problem: there is no start/stop, and changing the duration parameter takes too long (about 300us).
My hopes were that the new Microsoft PWM class would react faster or have a start/stop function, but from this post it seems that it is better not to use it.
moreover, it is not clear how to use it - how does the PWM enumaration relate to the Netduino GPIOs.
BTW, if it is not recommended to use the new classes, why were the old ones replaced..?
Thanks again,
C.
#8
Posted 18 August 2012 - 03:32 PM
#9
Posted 18 August 2012 - 03:57 PM
I would recomend using the new classes.
Thanks
Do you have any example for working with the new classes?
How does the Cpu.PWMChannel enumaration relate to the GPIO pins of the Netduino?
C.
#10
Posted 18 August 2012 - 05:50 PM
We're working on updates samples for the "Getting Started with Netduino" kit. In the meantime, grab a copy of the Netduino SDK 4.2.0 source from the downloads page...and it will show you how we wrap the new classes inside the legacy classes.Do you have any example for working with the new classes?
How does the Cpu.PWMChannel enumaration relate to the GPIO pins of the Netduino?
Regarding Cpu.PWMChannel... You can use those, but I'd recommend using "PWMChannels.PWM_PIN_D##" instead. Just like there is a Pins. collection for Cpu.Pin, there is a PWMChannels. collection for Cpu.PWMChannel. There's also an AnalogInputs. collection for the analog input pins.
Chris
#11
Posted 18 August 2012 - 09:21 PM
We're working on updates samples for the "Getting Started with Netduino" kit. In the meantime, grab a copy of the Netduino SDK 4.2.0 source from the downloads page...and it will show you how we wrap the new classes inside the legacy classes.
I'll do that.
Thanks!
#12
Posted 19 August 2012 - 04:31 AM
It will be nice to see a page somewhere that lists the new pin mappings at a glance.I'll do that.
Thanks!
In other words, newcomers, using MF 4.2, wanting to do the simple RGB sample app (10,000 example online), are not going to get this to compile:
PWM red = new PWM(Pins.GPIO_PIN_D0);
PWM red = new PWM( Cpu.PWMChannel.PWM_0, 10, 50, false);
Of course one can dig through the source, but that's like building an app to print an ASCII chart.
Then after mastering this, the new user can move on to the continuing confusion with the accidental (I hope) misuse of millisec and microsec (us vs. ms) in source code comments.
#13
Posted 19 August 2012 - 05:51 AM
http://wiki.tinyclr....x.php?title=PWM
My prediction is that a lot of people (like me initially) will be confused between these two:
Microsoft.SPOT.Hardware.Cpu.PWMChannel.PWM_5 (0 thru 7)
vs.
SecretLabs.NETMF.Hardware.NetduinoPlus.PWMChannels.PWM_PIN_D5 (5, 6, 9, 10)
#14
Posted 19 August 2012 - 12:36 PM
#15
Posted 29 January 2013 - 06:12 PM
Hi Cornelius, I would recomend using the new classes. The legacy classes are now wrappers around the new classes...so you'll get the most benefit by using Microsoft.SPOT.Hardware.AnalogInput/PWM instead of SecretLabs.NETMF.Hardware.AnalogInput/PWM. Chris
Hi Chis,
i have installed the .net microframework 4.2 (MicroFrameworkSDK_NETMF42_QFE2.msi) and in the Microsoft.SPOT.Hardware.AnalogInput
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users