I hope you can help me. There have been many changes since I last used the system.
I wanna make a system with two Servo motors.
Two years ago I made a sucessful test with a motorboard for big DC motors.
But I think the code changed.
Can I still use this command in 4.3?
you don’t need to use the L298 to drive a standard servo, the L298 is for DC motors. All you need is a standard PWM signal.
I don’t think that answers the question you asked, but it should reorient your thinking - you don’t need the L298 gadgeteer driver to get the servo to work.
TinyCLR is a nice very early alpha preview but far away from stable and far away from done and its missing to much features compared to your stable version of NETMF 4.3
based on the past TinyCLR releases it seems it could be feature equal to NETMF in one year from now on
Gadgeteer is still an option for you if you really want - although the core netmf capabilities changed from where you came so you may still need to re-learn some of these things.
PWM pin mapping comes from the definition of the PWM object; the first parameter is Cpu.PWMChannel.PWM_3 which references a physical channel, and that is linked back to a specific pin. What that pin’s capabilities are, are listed in the GHI provided helper GHI.Pins. Add that reference, and you can browse to see sockets and enclosed pin definitions. I’d suggest you actually use the GHI provided mapping, GHI.Pins.FEZRaptor.Socket18.Pwm7 looks to be the right place to connect it.
PWM reference not being found means your app needs another reference so that it can locate the correct calling procedure pattern - just add the Microsoft.SPOT.Hardware.PWM reference and you’re done.
you’d need to dig into the driver code that the L298 motor module used, because it’s abstracting the PWM component away from the user. I don’t think you need to worry about this, just move on and learn something new.
You added a USING statement, not a REFERENCE. You add references in the right hand panel in VS, in “references”, right click and say Add Reference, select it from the list.
You are addressing the pin that is connected to PWM Channel 3. It’s completely up to the person who implemented the firmware to map that - so it’s a GHI question that I can’t answer and doesn’t have a clear logical mapping. But if you add the GHI.PINS reference that I told you about, you get easy access to the correct PIN mapping without concern for the channels-to-pins (this is why GHI give you this!). There are three pins in Socket18 that have PWM capability.