I'm no help with any of the specific Python syntax, but here's a general outline:
1. You should create a task for Counter Output to generate PWM
2. When you configure Timing properties for the task, you'll likely need to use "Continuous Sampling" and "Implicit Timing".
3. And now here's the tricky thing, at least under the LabVIEW API. I suspect this is a device and/or DAQmx quirk and that it will also be true under Python though.
PWM control usually involves a constant frequency with a potentially variable duty cycle. But under DAQmx, you must also write to the frequency property to make it "digest" anything you write to the duty cycle property. So you probably need to write the new duty cycle first and then re-write the same old frequency to get DAQmx to "digest" both values.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
