Sebastian,
Can you tell me what run-time file or files changed? My target machine was
built from precompiled packages so it doesn't have the development tools
loaded. I will need to compile on my development machine and then transfer
the binaries.
Thanks,
Eric
I squished a silly bug with the
Eric H. Johnson wrote:
Can you tell me what run-time file or files changed? My target machine was
built from precompiled packages so it doesn't have the development tools
loaded. I will need to compile on my development machine and then transfer
the binaries.
The fix is entirely in pwmgen.c,
Sebastian,
Next I'd want to check the electrical state of the IO pins. With
SVST8_4, pwmgen.00 appears on pins 15 (PWM), 19 (Dir), and 23 (Not Enable).
Bust out a voltmeter and carefully hook it to pin 23. Then twiddle
pwmgen.00.enable high and low and see if the voltage on pin 23 varies as
-users] Another problem with Hostmot2 and m5i20
Sebastian,
Next I'd want to check the electrical state of the IO pins. With
SVST8_4, pwmgen.00 appears on pins 15 (PWM), 19 (Dir), and 23 (Not Enable).
Bust out a voltmeter and carefully hook it to pin 23. Then twiddle
pwmgen.00.enable high
Eric H. Johnson wrote:
Sebastian,
Next I'd want to check the electrical state of the IO pins. With
SVST8_4, pwmgen.00 appears on pins 15 (PWM), 19 (Dir), and 23 (Not Enable).
Bust out a voltmeter and carefully hook it to pin 23. Then twiddle
pwmgen.00.enable high and low and see if the
Sebastian,
The dir signal appears to be working properly as well. If .value is 0 or
positive, pin 19 is low, if .value is negative then pin 19 is high.
As for the PWM, I am measuring it with a meter, not a scope, but it does not
change (the voltage measured will typically be proportional to duty
Eric H. Johnson wrote:
The dir signal appears to be working properly as well. If .value is 0 or
positive, pin 19 is low, if .value is negative then pin 19 is high.
As for the PWM, I am measuring it with a meter, not a scope, but it does not
change (the voltage measured will typically be
Sebastian,
You can find the dmesg output posted here:
http://pastebin.com/mfae4a88
Regards,
Eric
Well that's very odd...
Try loading the hostmot2 driver will all debugging enabled:
loadrt hostmot2 debug_idrom=1 debug_module_descriptors=1
debug_pin_descriptors=1 debug_modules=1
Then
Eric H. Johnson wrote:
Sebastian,
You can find the dmesg output posted here:
http://pastebin.com/mfae4a88
Regards,
Eric
Well that's very odd...
Try loading the hostmot2 driver will all debugging enabled:
loadrt hostmot2 debug_idrom=1 debug_module_descriptors=1
I squished a silly bug with the hostmot2 pwmgen driver. It bit other
people but not me because I had an old forgotten work-around in the hal
config file I test with... If you had problems with pwmgen before,
please give CVS TRUNK a try again.
--
Sebastian Kuzminsky
Theo: Julian? I
Peter C. Wallace wrote:
I presumed the selecting of one PWM in the configuration set the direction
of the GPIO, as it does for the step and direction outputs for the two
steppers in the configuration.
Regards,
Eric
It should...
Is the PWM pin high or low?
Did you start with
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
Sebastian,
The enable pin for the PWM is getting set. If I set the enable to true, and
then set the value to say 5.0, when I do a show pin I do in fact see that
the enable pin is true and that the pwm value pin is 5.0.
Per your other email, I would think that this also proves that the scale is
Eric H. Johnson wrote:
The enable pin for the PWM is getting set. If I set the enable to true, and
then set the value to say 5.0, when I do a show pin I do in fact see that
the enable pin is true and that the pwm value pin is 5.0.
Per your other email, I would think that this also proves
Sebastian,
Yep, sounds like all the HAL pins params are set right. Just to make
sure, you've added the hm2_5i20.read() and .write() functions to a realtime
thread, and you've started the realtime kernel, right?
Yes. If I had not, then I don't think anything would work. As it is, my
steppers
Sebastian et al,
I had just got the stepper outputs working before I went on vacation and am
just now getting back to it. I am using Hostmot2, the m5i20 board and
SVST8_4 configuration, configured for 2 steppers, 1 pwm and no encoders. I
am also using just the patch applied to the most recent
On Tue, 9 Sep 2008, Eric H. Johnson wrote:
Date: Tue, 9 Sep 2008 20:28:21 -0400
From: Eric H. Johnson [EMAIL PROTECTED]
Reply-To: Enhanced Machine Controller (EMC)
emc-users@lists.sourceforge.net
To: emc-users@lists.sourceforge.net
Subject: [Emc-users] Another problem with Hostmot2
Peter,
I presumed the selecting of one PWM in the configuration set the direction
of the GPIO, as it does for the step and direction outputs for the two
steppers in the configuration.
Regards,
Eric
Sebastian is probably the one to ask, but, did you have the driver enable
the PWM0? Not the HAL
I presumed the selecting of one PWM in the configuration set the direction
of the GPIO, as it does for the step and direction outputs for the two
steppers in the configuration.
Regards,
Eric
It should...
Is the PWM pin high or low?
Did you start with Sebastians HAL file? I know he has
19 matches
Mail list logo
