Sebastian Kuzminsky wrote: > The pwmgen.XX.enable HAL pin gets initialized to 0 and sent to the FPGA > on module load. When the user changes the HAL pin, the new value is > sent to the FPGA. Eric, can you verify that the HAL enable pin for the > PWM in question does get set to 1?
Another thing to check is: are you setting pwmgen.00.scale? When you set the pwmgen's "value" pin, it gets turned into a pwm duty cycle by this formula: duty_cycle = value/scale (clipped so duty cycle stays within the -1.0 to +1.0 range). So a simple way to test it is to leave the scale parameter at the default (1.0), then "setp value" to values between -1 and +1 to try to drive the pwm outputs. -- Sebastian Kuzminsky "Much of what we learned from the sense of touch was unscientific prejudice, which must be rejected if we are to have a true picture of the world." -- Bertrand Russell ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users