Sebastian,
>> If you're using the latest stepgen.c (top-of-tree TRUNK & 2.2 branch),
then you don't need the raw stuff starting on line 30. <<
Ok, I will take them out.
>> Looks like you're using the same stepper timings as I do on the steppers
I test with - is that correct for your setup too? <<
>> Looks like you're using the same stepper timings as I do on the steppers
I test with - is that correct for your setup too? <<
I used them for a start and they seem to work.
>> Oops, and it looks like the u32 stepgen timing parameters are commented
out, and the old float ones are being used. I'm not sure how those
floats get read in, but they might all read as (u32)0, which could also
cause your steppers to not work. <<
>> Oops, and it looks like the u32 stepgen timing parameters are commented
out, and the old float ones are being used. I'm not sure how those
floats get read in, but they might all read as (u32)0, which could also
cause your steppers to not work. <<
Sorry about that, I went back to the old drivers because at least the stepper motors worked. As you can see, I have two sets of parameters, one for the old driver and one for the new driver. I just enable the set approrpiate for the current driver.
>> I see you have the Axis 2 motor command hooked up to the LaserPower net
and from there to pwmgen.00.value. Since you're not setting
pwmgen.00.scale it'll default to 1.0. You should be seeing full PWM
(100% duty cycle) when Axis 2 amp enable is on and Axis 2 motor position
is +/- 1. Is that not happening? <<
>> I see you have the Axis 2 motor command hooked up to the LaserPower net
and from there to pwmgen.00.value. Since you're not setting
pwmgen.00.scale it'll default to 1.0. You should be seeing full PWM
(100% duty cycle) when Axis 2 amp enable is on and Axis 2 motor position
is +/- 1. Is that not happening? <<
For testing purposes, I comment all that out and just use LaserPower linked to the pwmgen.00.power. Then set it manually through halcmd. Since I do not have a scope, I use the laser power to indicate whether the PWM is changing. Basically it comes on at a fairly low power, and does not seem to change.
When I measured the PWM with a meter, I got about the full 3.3 V, but thought that was just the meter. It is new, and I have not tried it on PWMs before. On many meters you can get a good estimate of the duty cycle through the voltage readings, but this one seems to show only 0 and 3.3V. However if it really were 3.3, then the output of the laser should be significantly higher.
>> One thing that would help debugging this is to set things up so you
think you *should* be seeing a strong pwm dutycycle, and then run (with
halcmd) "setp hm2_5i20.0.raw.dump-state 1" and "show all", and pastebin
the output of those two commands and also the dmesg after them. <<
>> One thing that would help debugging this is to set things up so you
think you *should* be seeing a strong pwm dutycycle, and then run (with
halcmd) "setp hm2_5i20.0.raw.dump-state 1" and "show all", and pastebin
the output of those two commands and also the dmesg after them. <<
I will try to post that shortly.
>> This would be much easier of your CNC machine was on the net, but I
understand sometimes that's a hassle to do.... <<
>> This would be much easier of your CNC machine was on the net, but I
understand sometimes that's a hassle to do.... <<
Unfortunately the computer box is panel mounted to the machine, so a real pain to disconnect and move to where there is an internet connection.
Regards,
Eric
------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
