HDPE suggests more recent 'history', so I would have expected the pipe
to be installed below 18. I wouldn't have thought our recent conditions
would have caused a problem at that depth. I'd put my money on the point
of entry in to the (old?) building. Get your spade out and have a look :-)
On
HDPE suggests more recent 'history', so I would have expected the pipe
to be installed below 18. I wouldn't have thought our recent conditions
would have caused a problem at that depth. I'd put my money on the point
of entry in to the (old?) building. Get your spade out and have a look :-)
On
Have a look at the second video (about 3/4 of the way through):
LINEAR CP-27 CNC LATHE
http://www.machinetoolsupplier.com/NEW-CNC-MACHINE-TOOLS
I considered the idea, but rejected it (too compromised, too expensive
to build).
Richard
On 17/11/2010 03:22, Igor Chudov wrote:
I have a Clausing
My unqualified thoughts :-)
I've seen these spikes a lot whilst tuning the servos on my mill. I
think they are a characteristic of FF1 tuning. It is very tempting to
tweek FF1 and watch the f-error generally tumble, only to be left with
these spikes. Note from Screenshot4 that the spikes
My KMB-1 M/X has one-shot pneumatic lube. The timer you describe fires
the solenoid valve (I've never checked the exact timing) and runs when
the servos are activated. The duty cycle is dictated by the profile of
the cam on the timer. The oil flow rate can be controlled by the the air
pressure
9.10 probably installed Grub2 which has no menu.lst. (I think upgrades
to 9.10 retain Grub legacy, new installs use Grub2 - quite different)
There is a useful starting point here:
https://help.ubuntu.com/community/Grub2
Richard
Andrew wrote:
On my ubuntu it's here:
/boot/grub/menu.lst
On
Dustin Monroe wrote:
Ok, I messed around with a 9v battery and adjusted the reference gain
and loop gain and got all three axis working without any following
errors.
You need to arrive at a properly tuned drive before closing the loop
with EMC and any further tuning, I'm not sure that you
On my drives, setting the signal gain to give the required speed in
relation to the input signal is the last thing to do. For my system, the
object is to arrive at a table speed of 300 ft/min with an applied
command of +-9V (leaving some head room). I increase the command signal
in small
Did you tune your amplifiers to give best response to a command input
prior to connecting EMC? The creep you describe can normally be reduce
by tuning balance/offset (some creep is still likely until the feedback
loop is closed).
Richard
Dustin Monroe wrote:
Hello,
First i will start with
It depends how you installed Karmic. If Karmic was a clean install, then
normally it should have installed grub2, if you upgraded from an earlier
version normally grub legacy will be retained. I'll assume it was a
clean install. One way to sort it: make a Super Grub Disc
Sorry, I hadn't understood that graphics were failing before X was starting.
I know booting in safe graphics is sometimes ignored.
However I found this:
https://wiki.ubuntu.com/EdgyKnownIssues/59618
I just tried it with my EMC2 8.04 disc and I am able to open the
xorg.conf (so you can at least
=10
# PID tuning params
DEADBAND = 0.15
P = 20
I = 0
D = 0.1
FF0 = 0
FF1 = 0.15
FF2 =0.00045
BIAS = 0.0005
Richard Arthur wrote:
Referring
Jon Elson wrote:
Chris Epicier wrote:
Warning: This is a rather long message. I hope the list moderator has
nothing against it.
Richard
Sorry, I hadn't understood that
graphics were failing before X was starting.
well I probably did not really stress that
Chris Epicier wrote:
Dear Jon
The part that lets me stay unsatisfied is, that I
cannot boot or install ubuntu past 7.10. 8.04 emc live cd
boots but the screen is garbled, it finally shows an
interlaced screen with the typical brown colour of the
desktop and as mentioned before, If I
Referring to:
http://imagebin.org/72841
I've added the motor-pos-cmd trace.
Jeff Epler wrote:
The coarse-position-command is the motor position before applying screw
compensation or backlash compensation, so it differs from the
motor-pos-cmd on machines that have these compensations enabled.
Looking at a plot in halscope, I was expecting the difference between
coarse-position-command and joint-pos-fb would be the same as the
f-error, it appears not to be. Can you explain please?
http://imagebin.org/72688
Thanks,
Richard
How can I change the Halscope background from black to white (useful
when printing hard copy).
Thanks,
Richard
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report
to be set low by the motion controller
when it looks for the index).
Only then the driver hardware will latch on the next index, and make the
pin high again, so motion knows index has happened.
Regards,
Alex
--
From: Richard Arthur rich
That resolved it. I just wish I understood it properly :-)
Thank you.
Richard
Jeff Epler wrote:
You probably need to connect the index-enable signal between the motion
controller and the encoder counter:
net Xindex-enable axis.0.index-enable =
hm2_5i20.0.encoder.00.index-enable
(this
I am moving from 2.17(working) to 2.33. I am using HM2-Servo 3 axis 5i20.
Halscope:
http://imagebin.org/68314
I expected homing to complete at the index (gpio 005). Homing is at
level 16.
I added this to the standard io block in hm2-servo.hal:
# X axis limit and home
newsig Xminlim-and-home
John Kasunich wrote:
Chris Radek wrote:
On Tue, Aug 07, 2007 at 06:47:59PM +0100, Richard Arthur wrote:
Just playing, but I notice that reversing the sign of the Min_Limit and
Max_Limit reverse the direction of travel when jogging (2.1.7). Is that
expected behaviour
John Kasunich wrote:
The scope trace shows that the the home input to the motion controller
is true during the first slope - that means EMC thinks it is already
on the switch, and is trying to get off of it.
From the HAL file:
# Connect limit/home switch outputs to motion controller.
Issue:
The direction of searching for the index seems to be the inverse of the
direction of THE_HOME_LATCH VEL when I would have expected it to be the
same.
What I did:
Update from (Ubuntu) 2.1.6 to 2.1.7. Generate new configs in my home
folder and modify to suit.
However, with the current
John Kasunich wrote:
Richard Arthur wrote:
John Kasunich wrote:
Richard Arthur wrote:
Issue:
The direction of searching for the index seems to be the inverse of the
direction of THE_HOME_LATCH VEL when I would have expected it to be the
same.
What I did:
Update
I would like to fit a VFD to the spindle of my 3 axis mill. How should I
set about controlling it? Apart from obvious speed control, I would
like to achieve oriented stop (boring and tool changer) I am currently
using an m5i20 and m7i33 under EMC 2.1.6.
Thank you,
Richard.
Have a look in the User Handbook, 5.3.6, [TRAJ] Section.
Regards,
Richard
lost wizz wrote:
Hi:
Am I correct in assuming that the config uses the unit inches for the
acceleration and max velocity? I have the following in the ini file and it
seems to work but it is not using the units
Snip:
I found a more disturbing problem - both versions seem to lose counts
going in one direction (but not the other). I have a 2500 line encoder
hooked up, so I should get 1 counts per rev. Going forward thats
exactly what I get. But turning it backwards, I get between 9700 and
9800
Entering a number from the numeric keypad in to the AXIS Touch Off
window does not work correctly. Keys 0, 5 and decimal point work; 1 to 4
and 6 to 9 don't. Standard number keys are fine. The numeric keypad
functions correctly in other applications. Using AXIS 2.1.6, Generic 105
key UK PC
John Kasunich wrote:
Richard Arthur wrote:
Entering a number from the numeric keypad in to the AXIS Touch Off
window does not work correctly. Keys 0, 5 and decimal point work; 1 to 4
and 6 to 9 don't. Standard number keys are fine. The numeric keypad
functions correctly in other
Why doesn't homing complete at the index pulse shown here:
http://imagebin.org/9073
(Homing with HOME_USE_INDEX = FALSE works okay)
EMC 2.1.6
From m5i20.ini:
[AXIS_0]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 4.0
MAX_ACCELERATION = 20.0
BACKLASH
It is single-ended (I had assumed a change in state was all that was
required). How do I invert the signal at HAL level. Would you expand a
little on why that may defeat the logic in the mesa board please?
Thanks
Richard
Jon Elson wrote:
Richard Arthur wrote:
Why doesn't homing complete
I have a problem with f-error being larger than normal when homing.
I ran this program :
%
G00 G40 G49 G80
G90 G54 G20 G61
G00 X0.2
G01 X0.1 F6.
X0.2
X0.1
X0.2
X0.1
X0.2
M02
%
and took a screenshot of HAL Oscilloscope to demonstrate normal f-error:
http://imagebin.org/8953
This next screenshot
Hello,
Would you be kind enough to help me with M5i20 configuration please. I
am using EMC2/AXIS v2.1.3. As a first step, I am trying to manual jog.
Jogging Y and Z almost immediately give 'joint following error' with no
visible movement, but I have found if I set the feed rate low, I can jog
I am trying to determine pinouts on my Litton encoders. They have 5
wires, two for 5V supply, two giving 1000 counts per rev, one giving 1
count per rev. Can I assume then that the 1000 counts per rev are
Channels A and B and the other is the index? Is there a rudimentary
method to
Hi,
I would like to retro-fit EMC to my Hurco KMB1x mill. It uses 3 no. HFC
servo amplifiers by Digiplan (Parker Hannifin) analogue +10V to-10V,
driving brushed dc motors with tacho and encoders, opto isolators on
limit switches and manual tool change. I am interested in using Mesa
card(s),
35 matches
Mail list logo
