Hello!
I would like to ask, if somebody could share some hints, why my client
can't restart execution of g-code file from middle of the file with
run from here - that is a waterjet machine and they frequently stop
the machine, if abrasive gets jammed etc. and then restart
approximately from the
On Wednesday 02 July 2014 03:32:35 Viesturs Lācis did opine
And Gene did reply:
Hello!
I would like to ask, if somebody could share some hints, why my client
can't restart execution of g-code file from middle of the file with
run from here - that is a waterjet machine and they frequently
On Wednesday 02 July 2014 04:44:28 Gene Heskett did opine
And Gene did reply:
On Wednesday 02 July 2014 03:32:35 Viesturs Lؤپcis did opine
And Gene did reply:
Hello!
I would like to ask, if somebody could share some hints, why my
client can't restart execution of g-code file from
Had similar problem years ago .
Had to go back in the gcode in order to reread some of the modular codes.
At this point I don't remember which ones.
Jim
On 14-07-02 05:20 AM, Gene Heskett wrote:
On Wednesday 02 July 2014 04:44:28 Gene Heskett did
We use Run From Line on a daily basis, and have found the best way to get
things to run properly is to go back to most recent spindle start/tool
call/operation start, and start from there. If he is starting from that line
G00 X76,4500 Y467,8691, I don't see anything to start the water jet, which I
On page 4 of the HAL Manual V2.6.0-pre4, 2014-06-12 a float is defined as 64
bits (i.e which I refer to as a double in my programming), which I take to be
the case within a HAL context.
However, on page 44 of the same Manual, it is defined as 32 bits (i.e typically
a float).
Which is correct?
Cecil,
You can send any bugs in the docs to me at bjt...@gmail.com
JT
On 7/2/2014 6:50 AM, Churms, Cecil wrote:
On page 4 of the HAL Manual V2.6.0-pre4, 2014-06-12 a float is defined as 64
bits (i.e which I refer to as a double in my programming), which I take to be
the case within a HAL
On 2 July 2014 12:50, Churms, Cecil cecil.chu...@debeersgroup.com wrote:
However, on page 44 of the same Manual, it is defined as 32 bits (i.e
typically a float).
Which is correct?
It changed at one point.
I guess the definitive answer is here:
On 2 July 2014 06:00, Gene Heskett ghesk...@wdtv.com wrote:
But that manpage is so concise its not giving all the details I need to
process it make it work.
A single instance of debounce can have many input/output pairs, but
only one debounce time.
So, if you want two debounces with the same
On Wed, Jul 02, 2014 at 11:50:23AM +, Churms, Cecil wrote:
On page 4 of the HAL Manual V2.6.0-pre4, 2014-06-12 a float is defined as 64
bits (i.e which I refer to as a double in my programming), which I take to be
the case within a HAL context.
However, on page 44 of the same Manual,
Jeff
Excellent answer - now I not only know, but also understand. The fact that the
documentation wasn't all updated is real-life ;-). Anyone expecting otherwise
hasn't attempted a project 1/1000th of the size of LinuxCNC.
I'll try to do my tuppence-worth of contribution, and feed any
On Wed, Jul 2, 2014, at 08:40 AM, andy pugh wrote:
A single instance of debounce can have many input/output pairs, but
only one debounce time.
So, if you want two debounces with the same debounce time use size=1
I think you meant size=2
If you want two debounces with different debounce
On Wednesday 02 July 2014 08:40:07 andy pugh did opine
And Gene did reply:
On 2 July 2014 06:00, Gene Heskett ghesk...@wdtv.com wrote:
But that manpage is so concise its not giving all the details I need
to process it make it work.
A single instance of debounce can have many input/output
On Wednesday 02 July 2014 08:59:54 John Kasunich did opine
And Gene did reply:
On Wed, Jul 2, 2014, at 08:40 AM, andy pugh wrote:
A single instance of debounce can have many input/output pairs, but
only one debounce time.
So, if you want two debounces with the same debounce time use
Cecil;
As a simple user of LinuxCNC, and one-time head of a large open source
project (that even Apple distributed) I thank you for your feedback, as it
will help make LinuxCNC better.
As my experience shows, many people use the software, but incredibly few
send in feedback or updates, so good
On Wednesday 02 July 2014 10:05:09 Gene Heskett did opine
And Gene did reply:
On Wednesday 02 July 2014 08:40:07 andy pugh did opine
And Gene did reply:
On 2 July 2014 06:00, Gene Heskett ghesk...@wdtv.com wrote:
But that manpage is so concise its not giving all the details I
need to
On 7/2/14 05:50 , Churms, Cecil wrote:
P.S. I am a newbie working systematically through the documentation, and
notice bugs/errata here and there, where I can usually work out what is
correct from the context. However, they are spelling/grammar/tech bugs
nevertheless. According to the
2014-07-02 14:15 GMT+03:00 Rick Lair r...@superiorroll.com:
We use Run From Line on a daily basis, and have found the best way to get
things to run properly is to go back to most recent spindle start/tool
call/operation start, and start from there. If he is starting from that line
G00 X76,4500
On 2 July 2014 21:12, Viesturs Lācis viesturs.la...@gmail.com wrote:
That machine uses standard M03/M05 to start/stop the water jet.
There is M05 2 lines earlier, thanks for the suggestion, I will ask
them to try restarting from spindle-related line.
The alternative is to MDI the M03 then
On 7/2/14 14:18 , andy pugh wrote:
On 2 July 2014 21:12, Viesturs Lācis viesturs.la...@gmail.com wrote:
That machine uses standard M03/M05 to start/stop the water jet.
There is M05 2 lines earlier, thanks for the suggestion, I will ask
them to try restarting from spindle-related line.
The
20 matches
Mail list logo
