On 02/20/2014 12:01 PM, Charles Steinkuehler wrote:
> Peter's solution will work. I was going to add a dead-band to the PID
> control internal to the HAL component that talks to the PRU, but Peter's
> suggestion of pushing the PID outside the PRU driver and into HAL makes
> a lot more sense.
I mig
John;
I do everything in metric; the Preferences->Preamble, when I change G20 to
G21, and save, it does not seem to have saved next time I run the program.
Still trying to run through this program, but thank you for your efforts -
I think the effort is worth it.
JohnS.
--
Hi,
I've been looking into the canned cycles in LinuxCNC and the relative
version is odd.
The gcode documentation has an example:
G0 X1 Y2 Z3
G91 G98 G81 X4 Y5 Z-0.6 R1.8 L3
It should make a nice pattern, but it drills in the wrong direction
(down-to-up). The R-word need to be -1.8 (negative) to
ngcgui (and pyngcgui) now support Bertho Stultien's
Gcode-meta-compiler (gcmc) in git master and in recent
buildbot debs.
Ngcgui creates entry boxes to simplify testing and use of:
a) single-subroutines gcode files (.ngc)
b) gcode meta compiler files (.gcmc)
Notes:
1) gcmc (version >=1.4
Charles
I am pleased I have found this thread, myself and a friend both have
small mill setups with type 34 steppers, and Gecko 201s running at 50
volts, and we have been trying to set them up with Beaglebones, and
machine kit, we are both new to linux, and thought it was some setting
we had wr
On 2/20/2014 2:07 AM, Schooner wrote:
> What is commonly done with manual mill conversions of the turret knee
> mills is to motorise the quill and leave the knee as manual.
> The quill is disconnected from the rack and pinion arrangement and large
> plate clamp is attached to the bottom of the qui
John
Does the metric units work. I tried with mm and MM but I get an error
that says mill instance has no attribute 'units'
On 2014-02-20 19:47, John Thornton wrote:
> I just uploaded 1.6.3 with some more content in the help file.
>
> JT
>
> On 2/20/2014 8:42 AM, Marius Liebenberg wrote:
>> John
John
I did a tapping process with spot, drill, chamfer and tap. When I
generated the Gcode it gave me an error that said the counter bore depth
was null or zero. I pushed the chamfer depth button again and the error
was gone.
It only happened the once and I cannot recreate the error now.//I am
Peter's solution will work. I was going to add a dead-band to the PID
control internal to the HAL component that talks to the PRU, but Peter's
suggestion of pushing the PID outside the PRU driver and into HAL makes
a lot more sense. The existing HAL PID component is vastly more
sophisticated than
I just uploaded 1.6.3 with some more content in the help file.
JT
On 2/20/2014 8:42 AM, Marius Liebenberg wrote:
> John did you update the version in the about box? I am still seeing
> 1.6.1. Now I dont know if I screwed up the extract.
>
> On 2014-02-20 16:24, John Thornton wrote:
>> Ok, 1.6.2 i
I can't follow what you did to get the error, can you reproduce it?
JT
On 2/20/2014 8:34 AM, Marius Liebenberg wrote:
> I saw that but you where quicker on the draw:)
> If you did not choose counter bore it would give a null value error. If
> you did the calculation on the bore tab it would go aw
Hi,
I looked at the DIR line on a bare beagle bone with no attachments. The DIR
line can end up toggling after a move has stopped. But it does not *always*
end up toggling after a move. Pressing the "power" button in AXIS clears the
situation until a future move. The STEP line does remain
no, you might have found a new one... let me see if I can reproduce it.
JT
On 2/20/2014 8:34 AM, Marius Liebenberg wrote:
> I saw that but you where quicker on the draw:)
> If you did not choose counter bore it would give a null value error. If
> you did the calculation on the bore tab it would g
The version updates from a variable so it is automagic.
JT
On 2/20/2014 8:42 AM, Marius Liebenberg wrote:
> John did you update the version in the about box? I am still seeing
> 1.6.1. Now I dont know if I screwed up the extract.
>
> On 2014-02-20 16:24, John Thornton wrote:
>> Ok, 1.6.2 is uploa
What I forgot to update is the variable...
JT
On 2/20/2014 8:42 AM, Marius Liebenberg wrote:
> John did you update the version in the about box? I am still seeing
> 1.6.1. Now I dont know if I screwed up the extract.
>
> On 2014-02-20 16:24, John Thornton wrote:
>> Ok, 1.6.2 is uploaded. Fixed th
The drivers have been working on mach3 for the last 5years with no
problem,and also work no problem with linuxcnc on a pc.
I believe jeff pollard has scoped the output on the dir line and it is
clearly visible.
On 20/02/14 16:43, Josiah Morgan wrote:
> Mark,
> when this happens, have you tried u
Mark,
when this happens, have you tried unplugging the step and dir(everything
but enable) from the beaglebone to verify that it isn't just coming from
microstepping on the driver itself?
I know I've experienced similar crackling sounds on some stepper drivers
that was completely isolated from inpu
On 2/20/2014 10:21 AM, Mark Tucker wrote:
> Ok i am not well enough conversed to explain this in detail,but i will try.
> Having recently been involved with the beaglebone/machinekit setup,i
> accidently came across a problem.
> I found that speradically the motors would make a noise like "frying a
On 2/20/2014 9:53 AM, Dave Cole wrote:
>
>
> On 2/20/2014 9:23 AM, Peter C. Wallace wrote:
>> On Thu, 20 Feb 2014, Dave Cole wrote:
>>
>>> Date: Thu, 20 Feb 2014 09:07:17 -0500
>>> From: Dave Cole
>>> Reply-To: "Enhanced Machine Controller (EMC)"
>>>
>>> To: emc-users@lists.sourceforge.net
>
Steve!
Here is your sample of gcode running the newest TP
Original TP
http://imagebin.org/294551 (limit of the 1 segment look-ahead)
New TP (which does arc-arc , Line-arc and line-line look-ahead.)
http://imagebin.org/294550
Robs hard work is awesome! (and it keeps improving)
sam
On 04/07/2
Ok i am not well enough conversed to explain this in detail,but i will try.
Having recently been involved with the beaglebone/machinekit setup,i
accidently came across a problem.
I found that speradically the motors would make a noise like "frying an
egg" after movement had finished.
This after
I dont know your board and driver but did come across an
incompatibility between a bob and driver where both have the LED
series resistor needed meaning the opto in the driver is not driven
hard enough.
Dave Caroline
On 20/02/2014, Marius Liebenberg wrote:
> Rusty
> Have look at the pulse width
Rusty
Have look at the pulse width requirements of your BOB and driver board.
You can set it in the HAL file
Look here as well:
wiki.linuxcnc.org/cgi-bin/wiki.pl?Stepper_Drive_Timing
http://linuxcnc.org/docs/html/config/stepper.html
http://www.linuxcnc.org/docs/2.4/html/hal_parallel_port.html
I am rather new to this, and I don't know of anyone locally to help
(Huntsville, AL area). Using a Sain Smart B.O.B and Driver boards. All
three axes work correctly when instructed to traverse in a negative
direction, however, when instructed positive, only travel half the
distance. I have trie
On Thursday 20 February 2014 10:11:28 John Thornton did opine:
> Ok, 1.6.2 is uploaded. Fixed the self induced error and added content to
> the help file.
>
> JT
Got that one John and a big thank you. Haven't unpacked it yet though.
> On 2/20/2014 7:59 AM, Marius Liebenberg wrote:
> > Never m
On Thursday 20 February 2014 10:05:45 John Thornton did opine:
> Hey Gene and anyone else,
>
> I added counterbore to my mill G code generator in version 1.6.0.
>
> http://gnipsel.com/files/g-code-generator/
>
> Any feed back is appreciated.
>
> JT
Good to hear John, I should be in a position
On Thursday 20 February 2014 09:14:28 Schooner did opine:
> IMHO if you motorise the knee instead of the quill, you lose all the
> benefits of the knee elevation for adjusting to workpieces and manually
> touching off the Z tool, in favour of a very slow and potentially
> troublesome Z axis which
On 2/20/2014 9:23 AM, Peter C. Wallace wrote:
> On Thu, 20 Feb 2014, Dave Cole wrote:
>
>> Date: Thu, 20 Feb 2014 09:07:17 -0500
>> From: Dave Cole
>> Reply-To: "Enhanced Machine Controller (EMC)"
>>
>> To: emc-users@lists.sourceforge.net
>> Subject: [Emc-users] Index (Encoder) Homing
>>
>
On Feb 19, 2014, at 12:42 AM, Charles Steinkuehler
wrote:
> If I'm following things correctly, you're doing something very similar
> to the HAL gantry component I just created: applying the same commanded
> position to each gantry joint, providing for an offset between the
> individual joints to
John did you update the version in the about box? I am still seeing
1.6.1. Now I dont know if I screwed up the extract.
On 2014-02-20 16:24, John Thornton wrote:
> Ok, 1.6.2 is uploaded. Fixed the self induced error and added content to
> the help file.
>
> JT
>
> On 2/20/2014 7:59 AM, Marius Lie
I saw that but you where quicker on the draw:)
If you did not choose counter bore it would give a null value error. If
you did the calculation on the bore tab it would go away. Was it that one?
On 2014-02-20 16:22, John Thornton wrote:
> Give me a moment, I just spotted an error with the counterbo
Ok, 1.6.2 is uploaded. Fixed the self induced error and added content to
the help file.
JT
On 2/20/2014 7:59 AM, Marius Liebenberg wrote:
> Never mind I'll just use the Linux box. It work very well on that.
> Thanks John
>
> On 2014-02-20 15:49, Marius Liebenberg wrote:
>> This one is on Windoze
On Thu, 20 Feb 2014, Dave Cole wrote:
> Date: Thu, 20 Feb 2014 09:07:17 -0500
> From: Dave Cole
> Reply-To: "Enhanced Machine Controller (EMC)"
>
> To: emc-users@lists.sourceforge.net
> Subject: [Emc-users] Index (Encoder) Homing
>
> Has anyone setup encoder index homing recently with the H
Give me a moment, I just spotted an error with the counterbore...
JT
On 2/20/2014 7:59 AM, Marius Liebenberg wrote:
> Never mind I'll just use the Linux box. It work very well on that.
> Thanks John
>
> On 2014-02-20 15:49, Marius Liebenberg wrote:
>> This one is on Windoze
>>
>> On 2014-02-20 15
Dave man why dont you start a new thread the proper way. Now your stuff
is all mixed up in another thread.
On 2014-02-20 16:07, Dave Cole wrote:
> Has anyone setup encoder index homing recently with the Hostmot2 driver?
>
> I'm using a 7i43-2 board with a 7i33 and it cannot find the index pulse
>
Ok, I can try and run it on windoze I have a couple of them running.
JT
On 2/20/2014 7:49 AM, Marius Liebenberg wrote:
> This one is on Windoze
>
> On 2014-02-20 15:44, John Thornton wrote:
>> I'm on 10.04 and Python version is 2.6.5.
>>
>> Run from a terminal and let me know the error msg. Dunno
Oh, and I have 1.6.1 up now.
JT
On 2/20/2014 7:49 AM, Marius Liebenberg wrote:
> This one is on Windoze
>
> On 2014-02-20 15:44, John Thornton wrote:
>> I'm on 10.04 and Python version is 2.6.5.
>>
>> Run from a terminal and let me know the error msg. Dunno if I can fix it
>> or not...
>>
>> JT
>
Has anyone setup encoder index homing recently with the Hostmot2 driver?
I'm using a 7i43-2 board with a 7i33 and it cannot find the index pulse
during the final phase of the homing process.
The search velocity is negative and the latch velocity is positive.
I've read the manual, the man 9 host
Never mind I'll just use the Linux box. It work very well on that.
Thanks John
On 2014-02-20 15:49, Marius Liebenberg wrote:
> This one is on Windoze
>
> On 2014-02-20 15:44, John Thornton wrote:
>> I'm on 10.04 and Python version is 2.6.5.
>>
>> Run from a terminal and let me know the error msg.
This one is on Windoze
On 2014-02-20 15:44, John Thornton wrote:
> I'm on 10.04 and Python version is 2.6.5.
>
> Run from a terminal and let me know the error msg. Dunno if I can fix it
> or not...
>
> JT
>
> On 2/20/2014 7:32 AM, Marius Liebenberg wrote:
>> Hi John
>> I had to rebuild my laptop s
I'm on 10.04 and Python version is 2.6.5.
Run from a terminal and let me know the error msg. Dunno if I can fix it
or not...
JT
On 2/20/2014 7:32 AM, Marius Liebenberg wrote:
> Hi John
> I had to rebuild my laptop so now I am on Python 3.3 and there seem to
> be issues. What is the version that
Hi John
I had to rebuild my laptop so now I am on Python 3.3 and there seem to
be issues. What is the version that I should use rather?
On 2014-02-20 14:59, John Thornton wrote:
> Hey Gene and anyone else,
>
> I added counterbore to my mill G code generator in version 1.6.0.
>
> http://gnipsel.co
Hey Gene and anyone else,
I added counterbore to my mill G code generator in version 1.6.0.
http://gnipsel.com/files/g-code-generator/
Any feed back is appreciated.
JT
--
Managing the Performance of Cloud-Based Applica
If the knee is motorized and has position feedback you could adjust the
knee position according to the tool length offset.
The slow motion of the knee would not affect the cutting as it would happen
only once per tool change.
It would be an intuitive action also as the tool gets longer the table ge
IMHO if you motorise the knee instead of the quill, you lose all the
benefits of the knee elevation for adjusting to workpieces and manually
touching off the Z tool, in favour of a very slow and potentially
troublesome Z axis which requires all movements to be inverted in a
somewhat counter-int
On 02/20/2014 12:24 AM, Marius Alksnys wrote:
> Rudy,
>
> I tried your robot6kins module, had to invert some joints due to
> different joint directions on my robot. It seems that my DH parameters
> are correct - I tested different positions and checked XYZ coordinates
> offline. But I get following
46 matches
Mail list logo
