---
Based on about a billion irc discussions, it seems like my
implementation of the charge pump in stepconf is at odds with every
stepper breakout board in the world.
The following untested patch makes the charge pump be activated by
"amplifier enable" when an external estop input is available.
I don't have a stepper breakout with a charge pump feature, so I can't
test this. If you have a horse in this race, please try out the patch
and let me know whether it makes stepconf's charge pump setup work
sensibly.
src/emc/usr_intf/stepconf/stepconf.py | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/src/emc/usr_intf/stepconf/stepconf.py
b/src/emc/usr_intf/stepconf/stepconf.py
index a982974..8d1001d 100755
--- a/src/emc/usr_intf/stepconf/stepconf.py
+++ b/src/emc/usr_intf/stepconf/stepconf.py
@@ -804,7 +804,14 @@ class Data:
if pump:
print >>file, "loadrt charge_pump"
- print >>file, "net estop-out charge-pump.enable
iocontrol.0.user-enable-out"
+ if ESTOP_IN in inputs:
+ # breakout boards with estop inputs and charge-pump outputs
+ # seem to all treat charge-pump signal present as an
+ # amplifier enable. Whatever, guys.
+ print >>file, "net xenable => charge-pump.enable"
+ print >>file, "net estop-out <= iocontrol.0.user-enable-out"
+ else:
+ print >>file, "net estop-out iocontrol.0.user-enable-out =>
charge-pump.enable"
print >>file, "net charge-pump <= charge-pump.out"
if pwm:
--
1.5.4.3
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
