HI Kim,
Yup, that's it.
Les
On 28/03/11 00:09, Kim Kirwan wrote:
Hi Les,
Thanks very much for submitting this bug fix.
I have entered your fix, please take a look and
let us know if this is what you wanted:
Here's the git commit diff:
Thanks. I think I will have to go down that route because ClassicLadder
is being a real CPU hog. Without the CL GUI loaded my average CPU load
with Axis running is 20%. With Modbus enabled and the ClassicLadder GUI
running, CPU load averages 80%.
Les
On 28/03/11 06:16, Kirk Wallace wrote:
I
I have changed over to making my own MPG's using the cheap ($24) AMT102
settable encoders. I make the shaft and wheel myself and fit a couple of BCD
rotary switches in a neat little box. I tend to keep them simple.
Currently I am making a substantial unit with two handwheels mounted in an
On 03/27/2011 01:56 PM, Kirk Wallace wrote:
Why not? I found it to be a great fit for HMIs, and fearsomely easy.
Granted, if you already hack pics and avrs in your sleep, it probably
has little to offer, but for the other 99.7% of humanity, it makes
simple things easy and moderately complex
On Sun, 27 Mar 2011 09:12:30 +0100, you wrote:
I am a great believer in having 1 MPG per axis. I use high resolution
encoders (500 lines upwards) and proper hand wheels so the machine can
be operated as a manual. The hand wheels have friction but no indents,
just like a manual machine. With a
Les Newell wrote:
Thanks. I think I will have to go down that route because ClassicLadder
is being a real CPU hog. Without the CL GUI loaded my average CPU load
with Axis running is 20%. With Modbus enabled and the ClassicLadder GUI
running, CPU load averages 80%.
I haven't looked at the
Les,
I think something else may be wrong.
I have used Classic Ladder quite a bit and I don't have any CPU loading
issues at all.
The last setup I did was driving step and direction motors via a LPT
port on an Intel 330 based Atom motherboard.
Last year Jeff Epler cleaned up the Modbus code
On Sun, Mar 27, 2011 at 2:19 PM, David Keeton pkeet...@woh.rr.com wrote:
This is the line of the program in question
G0G90G54T1
The next line is the M6 command.
Is it ok to have G0 command without any axis word in one line with
G90, G54 and toolchange commands? Did You try breaking
I think that was the local exchange. I grew up in Fremont, OH and we
were always FEderal 2, which changed to 332, my grandmother in WV was
SKyline-X- don't remember the number. I remember my dad making the call
as it was operator assisted and you told her or him the city you wanted
and the
Blind tapped holes are everyday occurrences commercially, its not a
problem.
Right! While I prefer through holes, there are plenty of places where I
can't go through.
One thing I make is some cabinet rails that are 8 - 11 long, and have
threaded holes in the
ends. The part I copied was
Steve Blackmore wrote:
On Sun, 27 Mar 2011 09:12:30 +0100, you wrote:
I am a great believer in having 1 MPG per axis. I use high resolution
encoders (500 lines upwards) and proper hand wheels so the machine can
be operated as a manual. The hand wheels have friction but no indents,
Hello, gentlemen!
I have a question about creating g-code for a machine with awkward kinematics.
Basically my problem can be reduced to following issue:
How can I create g-code, if I know the path of tool in XY plane and a
path in XZ plane? I have 2 paths that I have to merge together -
execute
Hmm, well if I load the user mode part of CL with --nogui then the cpu
load is about 20% but I don't have modbus. If I remove the --nogui then
I get the GUI, modbus works and CPU load goes up to 90%.
Les
On 28/03/11 16:46, Dave wrote:
Les,
I think something else may be wrong.
I have used
13 matches
Mail list logo