You might be able to pick up something from following the discussion
that took place on the mailing list:
https://sourceforge.net/p/emc/mailman/emc-developers/thread/a5532f65bdcb68eb960fa463c3fcef34%40mail.swcp.com/#msg31458545
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and i
The very last line is a question - he was asking if those files are
available and someone could send them in email. I am interested in
them as well.
Viesturs
piektd., 2025. g. 1. aug., plkst. 11:29 — lietotājs andy pugh
() rakstīja:
>
> On Thu, 31 Jul 2025 at 18:11, yoyo via Emc-developers
> wro
On Thu, 31 Jul 2025 at 18:11, yoyo via Emc-developers
wrote:
>
> Hi All,The followig is two emails from over a decade ago.
...
Indeed. and the work was merged into LinuxCNC and Rob is now the
software team leader at Tormach (according to Linkedin).
Did you have a question, or was this just a st
Hi All,The followig is two emails from over a decade ago.
[Emc-developers] Proposing a Lookahead implementation for the EMC2 module
From: Robert E. https://www.dropbox.com/s/p1g1zbwmviv5cn7/LinuxCNC%20Lookahead%20Proposal.pdf
I'm obviously a bit of an outsider to emc development, so any feedback
I was doing some minor doc changes to 2.9 and master and I noticed that there
is a sim for 'craftsman' which appears to be python2/gtk2.
Is anyone intending to convert it to python3/gtk3 or should it be removed?
___
Emc-developers mailing list
Emc-de
On Fri, 9 Sept 2022 at 13:29, Hans Unzner wrote:
> > Hmm, well, not wanting to throw too much chaos into the mix, but this
> > isn't DOS and the actual files are called .ini so I would have
> > preferred a consistent ".ini".
> File types are usually used with capital letters, like PDF file,
Le ven. 9 sept. 2022 à 14:29, Hans Unzner a écrit :
>
> File types are usually used with capital letters, like PDF file, HTML
> file and so on. In these cases they are abbreviations in contrast to "INI".
> But wouldn't it a bit weird and inconsistent to have PDF, HTML, HAL and
> .ini files?
>
10
Am 08.09.22 um 00:13 schrieb andy pugh:
On Wed, 7 Sept 2022 at 11:14, Steffen Moeller wrote:
Now, it happened that the "linuxcnc -h" output is quoted in the
documentation, and that had some "ini" that we could either leave as it
is (and be inconsistent within the documentation but consisten
On Wed, 7 Sept 2022 at 11:14, Steffen Moeller wrote:
> Now, it happened that the "linuxcnc -h" output is quoted in the
> documentation, and that had some "ini" that we could either leave as it
> is (and be inconsistent within the documentation but consistent with the
> source code)
Hmm, well, no
Dear all,
Thank you for you trusting us so much with the many (mostly)
weblate-translation-motivated changes to the documentation. A good part
of that exercise means to decide about what spelling or what word to use
for what thing. Somewhen on IRC we decided to go for the Wikipedia-like
all-caps
Greetings all;
Just re-built the rpi version from github, no problems evident, but
thought I'd scan thru the docs for new things.
On page 3 of the Docs pdf, the date of the Copyright says 2016. Should
that not be rigged to substitute the current year so its always up to
date?
The additional
> On 20. Aug 2020, at 13:34, andy pugh wrote:
>
> On Thu, 20 Aug 2020 at 12:21, John wrote:
>
>> /usr/bin/env: ‘linuxcnc-python’: No such file or directory
>> make: *** [../docs/src/Submakefile:562: .html-images-stamp] Error 127
>
> One for Rene,
> https://github.com/LinuxCNC/linuxcnc/blob/m
On Thu, 20 Aug 2020 at 12:21, John wrote:
> /usr/bin/env: ‘linuxcnc-python’: No such file or directory
> make: *** [../docs/src/Submakefile:562: .html-images-stamp] Error 127
One for Rene,
https://github.com/LinuxCNC/linuxcnc/blob/master/scripts/linuxcnc-python.in
If you run ./configure then it
No problem. I did try and make docs on master and got an error that is
not obvious as to what it means.
/usr/bin/env: ‘linuxcnc-python’: No such file or directory
make: *** [../docs/src/Submakefile:562: .html-images-stamp] Error 127
JT
On 8/20/20 6:10 AM, andy pugh wrote:
On Thu, 20 Aug 2020
On Thu, 20 Aug 2020 at 11:58, John wrote:
>
> I do see it in master...
That would explain it, sorry for the confusion.
I was juggling a VM window and a github window, both on my iMac trying
to compile a list of which hal components have spanish translations
and which don't.
It is quite likely th
I do see it in master...
JT
On 8/20/20 5:56 AM, John wrote:
I just built 2.8 docs and I don't see the filter-kalmann HAL
component. Where is the filter-kalmann HAL component in the docs? I
don't see it in the man pages which is where I assume your talking about.
I don't see any comp or c fil
I just built 2.8 docs and I don't see the filter-kalmann HAL component.
Where is the filter-kalmann HAL component in the docs? I don't see it in
the man pages which is where I assume your talking about.
I don't see any comp or c file by that name in src/hal/components...
JT
On 8/19/20 8:21 PM
I assume your working with the 2.8 docs? I'll see what's up.
JT
On 8/19/20 8:21 PM, andy pugh wrote:
I know why the new filter-kalmann HAL component does not show up in
the Spanish docs. It is because those use a static version of
index_es.tmpl and it isn't mentioned there.
But the English doc
I know why the new filter-kalmann HAL component does not show up in
the Spanish docs. It is because those use a static version of
index_es.tmpl and it isn't mentioned there.
But the English docs seem to generate the links by looking through the
tree, so it should show up.
--
atp
"A motorcycle is
> On Mon, 13 Jul 2020 at 22:08, N wrote:
>
> > Maybe you need tell it is UTF8 unless there already is and ctan package.
> > Without this is it might be you must enter the character code instead of
> > actual character.
>
> Have you found where the .tex files exist during docs generation? I
> t
On Mon, 13 Jul 2020 at 22:08, N wrote:
> Maybe you need tell it is UTF8 unless there already is and ctan package.
> Without this is it might be you must enter the character code instead of
> actual character.
Have you found where the .tex files exist during docs generation? I
think that would
On Sun, 12 Jul 2020 15:39:22 +0100
andy pugh wrote:
> On Wed, 8 Jul 2020 at 08:23, N wrote:>
> > From the last free rows I am pretty sure Chinese font package CJKutf8 is
> > missing. Could also find a few rows at top "no support" but would guess
> > they are also for other languages but are n
On Wed, 8 Jul 2020 at 08:23, N wrote:
> From the last free rows I am pretty sure Chinese font package CJKutf8 is
> missing. Could also find a few rows at top "no support" but would guess they
> are also for other languages but are not sure.
That helped, (apt-get install latex-cjk-all )
But onl
I'll pull that in the morning during free time and see if I can get the
PDF's to build.
JT
On 7/7/2020 6:48 PM, andy pugh wrote:
I realised recently that the new Chinese dos were not being built.
I have tried to fix this, and the HTML docs very nearly work (and
should be viewable on the build
On Wed, 8 Jul 2020 at 19:14, Jon Elson wrote:
> Of course, I can't read the Chinese, but it does display.
Yes, but all you are seeing there is the Github rendering of the
asciidoc source.
HTML doc generation also works, but PDF docs don't. (and break the
build on the buildbot)
--
atp
"A moto
On 07/08/2020 09:25 AM, andy pugh wrote:
On Wed, 8 Jul 2020 at 12:27, John wrote:
Odd, when I try and view a page on github I get a 404 page not found.
https://github.com/LinuxCNC/linuxcnc/blob/andypugh/cn_docs/docs/src/getting-started/Master_Getting_Started_cn.txt
The main page comes up, the
On Wed, 8 Jul 2020 at 12:27, John wrote:
>
> Odd, when I try and view a page on github I get a 404 page not found.
>
> https://github.com/LinuxCNC/linuxcnc/blob/andypugh/cn_docs/docs/src/getting-started/Master_Getting_Started_cn.txt
It looks like the links don't work (I see no reason for those to
Odd, when I try and view a page on github I get a 404 page not found.
https://github.com/LinuxCNC/linuxcnc/blob/andypugh/cn_docs/docs/src/getting-started/Master_Getting_Started_cn.txt
Are the Chinese docs only on your branch?
JT
On 7/7/20 6:48 PM, andy pugh wrote:
I realised recently that the
> I realised recently that the new Chinese dos were not being built.
>
> I have tried to fix this, and the HTML docs very nearly work (and
> should be viewable on the buildbot scratch fairly soon)
> https://github.com/LinuxCNC/linuxcnc/tree/andypugh/cn_docs
>
> But the PDF docs give problems that
I realised recently that the new Chinese dos were not being built.
I have tried to fix this, and the HTML docs very nearly work (and
should be viewable on the buildbot scratch fairly soon)
https://github.com/LinuxCNC/linuxcnc/tree/andypugh/cn_docs
But the PDF docs give problems that I don't fully
On Monday 16 October 2017 07:56:47 Gene Heskett wrote:
> On Monday 16 October 2017 04:38:53 andy pugh wrote:
> > On 15 October 2017 at 23:07, Gene Heskett
wrote:
> > > motion.spindle-revs IN FLOAT
> > > For correct operation of spindle synchronized moves,
> > > this signal mu
On Monday 16 October 2017 04:38:53 andy pugh wrote:
> On 15 October 2017 at 23:07, Gene Heskett wrote:
> > motion.spindle-revs IN FLOAT
> > For correct operation of spindle synchronized moves,
> > this signal must be hooked to the position pin of the spindle
> > encoder.
> >
>
On 15 October 2017 at 23:07, Gene Heskett wrote:
> motion.spindle-revs IN FLOAT
> For correct operation of spindle synchronized moves, this
> signal must be hooked to the position pin of the spindle encoder.
>
> should be satisfied by:
> net spindle-vel-fb-rps <= hm2_5i25.
On Sunday 15 October 2017 09:18:36 Gene Heskett wrote:
> On Sunday 15 October 2017 04:56:09 andy pugh wrote:
> > On 15 October 2017 at 02:10, Gene Heskett wrote:
> > > In the Ducumentation.pdf, there is a remark in the g33 command
> > > description about needing to hookup both the spindle-at-spee
On Sunday 15 October 2017 04:56:09 andy pugh wrote:
> On 15 October 2017 at 02:10, Gene Heskett wrote:
> > In the Ducumentation.pdf, there is a remark in the g33 command
> > description about needing to hookup both the spindle-at-speed and
> > the encoder.n.Z (index) to something. I seem to have
On 15 October 2017 at 02:10, Gene Heskett wrote:
> In the Ducumentation.pdf, there is a remark in the g33 command
> description about needing to hookup both the spindle-at-speed and the
> encoder.n.Z (index) to something. I seem to have lost one or the other
> in this little puff of smoke from th
Greetings all;
In the Ducumentation.pdf, there is a remark in the g33 command
description about needing to hookup both the spindle-at-speed and the
encoder.n.Z (index) to something. I seem to have lost one or the other
in this little puff of smoke from the ptc on a 5i25.
By slowing things down
On Sunday 17 May 2015 18:54:54 Kirk Wallace wrote:
> On 05/17/2015 02:23 PM, Gene Heskett wrote:
> > On Sunday 17 May 2015 13:58:49 John Thornton wrote:
> >> Gene,
> >>
> >> A wiki search can be done two ways, at the bottom of every wiki
> >> page is a search button or do a google site search like
On Sunday 17 May 2015 18:54:42 John Thornton wrote:
> My shop cat Woody wandered off one night and never came back, don't
> you go doing that! I named him woody because one winter I found him
> living in the wood stack next to the garage. It took him 3 days to eat
> a tiny bowl of dry food... after
My shop cat Woody wandered off one night and never came back, don't you
go doing that! I named him woody because one winter I found him living
in the wood stack next to the garage. It took him 3 days to eat a tiny
bowl of dry food... after a while he got his appetite back and when I
let him in
On 05/17/2015 02:23 PM, Gene Heskett wrote:
> On Sunday 17 May 2015 13:58:49 John Thornton wrote:
>> Gene,
>>
>> A wiki search can be done two ways, at the bottom of every wiki page
>> is a search button or do a google site search like this:
>
> Humm, I must have gotten stoned and missed it, John,
On Sunday 17 May 2015 13:58:49 John Thornton wrote:
> Gene,
>
> A wiki search can be done two ways, at the bottom of every wiki page
> is a search button or do a google site search like this:
Humm, I must have gotten stoned and missed it, John, as I am now trained
to look for the search box at th
Gene,
A wiki search can be done two ways, at the bottom of every wiki page is
a search button or do a google site search like this:
searched all of linuxcnc
stuff to search for site:linuxncnc.org
search just the wiki
stuff to search for site:wiki.linuxcnc.org
JT
On 5/17/2015 12:07 PM, Gene He
On Sunday 17 May 2015 09:52:18 John Thornton wrote:
> I've created a branch called 2.7_Docs where I've combined the User,
> Integrator and HAL manual into one document. I used to think it made
> sense to have separate user and integrator manuals but now I feel that
> most users are the integrators
Thanks. I for one think that this will lead to the
documentation being more accurate and easier to
navigate.
> -Original Message-
> From: John Thornton [mailto:j...@gnipsel.com]
> Sent: Sunday, May 17, 2015 9:56 AM
> To: EMC Developers List
> Subject: [Emc-developers]
I've created a branch called 2.7_Docs where I've combined the User,
Integrator and HAL manual into one document. I used to think it made
sense to have separate user and integrator manuals but now I feel that
most users are the integrators as well so that separation is only a
limitation for the
I've created a branch called 2.7_Docs where I've combined the User,
Integrator and HAL manual into one document. I used to think it made
sense to have separate user and integrator manuals but now I feel that
most users are the integrators as well so that separation is only a
limitation for the
If it applies to 2.5 then make the patches for 2.5 and they will get
pushed uphill. I just pushed the patch. If you don't mind can you can
send the patches to jthornton at gnipsel dot com that is my documents
computer and sometimes I might miss it here.
Thanks
John
On 12/7/2012 6:31 AM, Anders
On Fri, Dec 7, 2012 at 1:58 PM, John Thornton wrote:
> Is the patch for 2.5 or master?
>
my patch is for v2.5_branch.
I also noticed the list of ca 110 components isn't complete. Would you want
further patches for v2.5_branch or for master?
>
> The html man pages are generated by magic somehow
Is the patch for 2.5 or master?
The html man pages are generated by magic somehow... might be in the
submakefile I'm not sure.
John
On 12/6/2012 1:22 PM, Anders Wallin wrote:
> I was browsing this:
> http://www.linuxcnc.org/docs/2.5/html/hal/components.html
>
> and thought that listing all of t
the man page io.1 is a redirect to iocontrol.1 for some unknown reason.
You would have to ask Alex why he created the page on Wed, 17 Oct 2007.
I see no reason to keep it myself unless someone chimes in...
John
On 12/6/2012 1:38 PM, Anders Wallin wrote:
> Looking at:
> http://www.linuxcnc.org/d
Looking at:
http://www.linuxcnc.org/docs/2.5/html/
why is there both a component "io.1" and a component "iocontrol.1" listed?
They seem to be identical?
Anders
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. F
I was browsing this:
http://www.linuxcnc.org/docs/2.5/html/hal/components.html
and thought that listing all of the ca 110 components in one big list could
be improved.
Here's a patch, what do you think?
A similar organization into subsections of "Realtime components and kernel
modules" over here
sorry, this was meant as a private reply to a private question
foot-in-mouth,
- Michael
Am 26.08.2012 um 16:50 schrieb Kent A. Reed:
> On 8/26/2012 5:09 AM, Michael Haberler wrote:
>> (sidenote: deviating from the stream/file descriptor model is a capital
>> design defect in NML/RCS, and it is
On 8/26/2012 5:09 AM, Michael Haberler wrote:
> (sidenote: deviating from the stream/file descriptor model is a capital
> design defect in NML/RCS, and it is pretty much unfixable).
Knowing how many platforms were in the mix back in the heyday of AMRF, I
suspect this "design defect" was more of
On Sun, 26 Aug 2012 08:08:49 +, Chris Morley wrote:
>>From time to time I was thinking on Stuart's talk about
>> error/debugging messages.
> While working on Gscreen I added a message system.
>
> It uses HAL pins to trigger a dialog/ desktop notification/ sound.
> I think this would work fine
Am 26.08.2012 um 10:08 schrieb Chris Morley:
>
>> From time to time I was thinking on Stuart's talk about error/debugging
>> messages.
> While working on Gscreen I added a message system.
>
> It uses HAL pins to trigger a dialog/ desktop notification/ sound.
> I think this would work fine for
>From time to time I was thinking on Stuart's talk about error/debugging
>messages.
While working on Gscreen I added a message system.
It uses HAL pins to trigger a dialog/ desktop notification/ sound.
I think this would work fine for user created components and ladder programs.
It would be a lo
Ouch! that whole section is terrible... I'll update 2.5 with some more
sensible text and hope it gets pushed up to master.
John
On 5/30/2012 1:21 AM, Michael Haberler wrote:
> this is also a bit confusing:
>
> http://www.linuxcnc.org/docs/devel/html/gcode/gcode.html#_g28_g28_1_go_to_predefined_p
this is also a bit confusing:
http://www.linuxcnc.org/docs/devel/html/gcode/gcode.html#_g28_g28_1_go_to_predefined_position_a_id_sec_g28_g28_1_a
(same for G30ff)
G28 - makes a rapid traverse move from the current position to the absolute
position of the values in parameters 5161-5166. The param
Am 29.05.2012 um 16:56 schrieb Kenneth Lerman:
> On 5/29/2012 10:39 AM, andy pugh wrote:
>> On 29 May 2012 14:57, Michael Haberler wrote:
>>
>>> that said: there is still no way to retrieve the current *absolute* machine
>>> position, that is, without any offsets.
>> Actually, there is, but it
On 5/29/2012 10:39 AM, andy pugh wrote:
> On 29 May 2012 14:57, Michael Haberler wrote:
>
>> that said: there is still no way to retrieve the current *absolute* machine
>> position, that is, without any offsets.
> Actually, there is, but it is non-obvious. You can use G28.1 or G30.1
> to store th
On 29 May 2012 14:57, Michael Haberler wrote:
> that said: there is still no way to retrieve the current *absolute* machine
> position, that is, without any offsets.
Actually, there is, but it is non-obvious. You can use G28.1 or G30.1
to store the current absolute position, and then read it ba
2012/5/29 Michael Haberler :
> right. I'll make that change.
>
> Any opinion on a new '54XX absolute machine position' feature?
>
Could You, please, shine some light in my corner and share some
example, where this would be useful?
I feel that it would be cool feature to have a parameters for pure
right. I'll make that change.
Any opinion on a new '54XX absolute machine position' feature?
- Michael
Am 29.05.2012 um 16:06 schrieb John Thornton:
> The only part that is confusing to me is "In absolute machine
> coordinates" it might be more intuitive to say "In relative machine
> coordina
The only part that is confusing to me is "In absolute machine
coordinates" it might be more intuitive to say "In relative machine
coordinates"
John
On 5/29/2012 8:57 AM, Michael Haberler wrote:
> the current manual describes:
> http://www.linuxcnc.org/docs/devel/html/gcode/overview.html#_number
the current manual describes:
http://www.linuxcnc.org/docs/devel/html/gcode/overview.html#_numbered_parameters_a_id_sub_numbered_parameters_a
5420-5428
Current Position including all offsets and in the current program units for X,
Y, Z, A, B, C, U, V & W. In absolute machine coordinates, vo
On 3/29/2012 10:47 AM, Michael Haberler wrote:
> looking at the very nice Zguide manual (http://zguide.zeromq.org/page:all)
> and how it was built I stumbled over http://code.google.com/p/wkhtmltopdf/,
> which converts html to pdf.
>
> I thought I give it a stab and see how the online docs come o
looking at the very nice Zguide manual (http://zguide.zeromq.org/page:all) and
how it was built I stumbled over http://code.google.com/p/wkhtmltopdf/, which
converts html to pdf.
I thought I give it a stab and see how the online docs come out in pdf if
processed with wkhtmltopdf.
I ran those c
I'm looking for a Latex-aware fellow to help out here:
so far highlighting for PDFs had to be disabled by this incantation:
:ini: {basebackend@docbook:'':ini}
:hal: {basebackend@docbook:'':hal}
:ngc: {basebackend@docbook:'':ngc}
If the below latex fragment is added to
/usr/share/texmf-texlive/t
On Thu, 2012-02-09 at 11:36 -0600, Jon Elson wrote:
... snip
> Yes, if the docs don't adequately describe how this system of putting
> settings in the
> .ini file and then having HAL code in a HAL file that reads them and
> makes the
> settings to the HAL component, then it does need to be put in
John Thornton wrote:
> I have to disagree with this, you can have unlimited INI options if
> you call them from your HAL file and as we all know this only confuses
> new users when they see a snippet in the manual and assume that it is
> used by LinuxCNC in some way other than how it is used to
I have to disagree with this, you can have unlimited INI options if you
call them from your HAL file and as we all know this only confuses new
users when they see a snippet in the manual and assume that it is used
by LinuxCNC in some way other than how it is used to bring all the
settings to on
On 8 Feb 2012, at 20:14, Jon Elson wrote:
>>
> I think it may be uncommon for servo systems. Most servo systems use
> PID, and the
> PID and FFx parameters are loaded from the .ini file. Also, INPUT_SCALE,
> OUTPUT_SCALE, following error settings, axis limits of travel, etc.
> normally all
andy pugh wrote:
> On 8 February 2012 10:16, Chris Morley wrote:
>
>
>> But most (all?) configs use substitution to apply the INI settings to HAL
>> components.
>>
>
> My own HAL files typically make no reference to the INI file at all. I
> don't know how common that is.
>
I think it ma
:
>
> > But most (all?) configs use substitution to apply the INI settings to HAL
> > components.
>
> My own HAL files typically make no reference to the INI file at all. I
> don't know how common that is.
>
> --
> atp
It's common.
look at the sample configs, stepconf and pncconf configs.
On 8 February 2012 10:16, Chris Morley wrote:
> But most (all?) configs use substitution to apply the INI settings to HAL
> components.
My own HAL files typically make no reference to the INI file at all. I
don't know how common that is.
--
atp
The idea that there is no such thing as objective
> On 8 February 2012 03:27, Chris Morley wrote:
> > While they are specific to these drivers, they are still INI options and
> > belong in the INI section.
> > There are lots of INI option that are specific to certain components.
>
> I don't really understand this statement. As far as I know no
On 8 February 2012 03:27, Chris Morley wrote:
> While they are specific to these drivers, they are still INI options and
> belong in the INI section.
> There are lots of INI option that are specific to certain components.
I don't really understand this statement. As far as I know no HAL
hardware
While they are specific to these drivers, they are still INI options and belong
in the INI section.
There are lots of INI option that are specific to certain components.
I think we just need to note that very few boards utilize it.
output_offset was in PNCconf for a long time until I figured out
Do those drivers read the output_offset from the INI file? If it is
driver specific it belongs in the driver chapter.
John
On 2/6/2012 5:36 PM, Chris Morley wrote:
I've been meaning to bring this up ...
output_offset found in the INI section under servo needs some
clarification.
Not all c
I've been meaning to bring this up ...
output_offset found in the INI section under servo needs some clarification.
Not all components / boards use this feature.
For instance hostmot2 has no provision for output_offset on it's pwmgen.
In fact it seems only servo to go and motenc honors this s
I don't know of any setting in gedit, I've just been using my eye and
the enter key.
John
On 8/22/2011 5:25 PM, Chris Morley wrote:
I'm not much of a doc guru any more but I did notice that the
conversion has CRLF at about 72 as opposed to the old lyx way. So to
be consistent with the conv
I'm not much of a doc guru any more but I did notice that the
conversion has CRLF at about 72 as opposed to the old lyx way. So to
be consistent with the converted docs you might want to limit line
length to 72 cols. Also make sure it compiles and your good to go
I'm not much of a doc guru any more but I did notice that the conversion
has CRLF at about 72 as opposed to the old lyx way. So to be consistent
with the converted docs you might want to limit line length to 72 cols.
Also make sure it compiles and your good to go.
The write up looks fine to me
Hi guys.
I updated the 'getting started manual' images for pncconf (hope thats OK)
I also wrote some pncconf docs for the manual.
I figured some of the doc guru's should approve them so here they are.
Chris M
= Point n Click Configuration Wizard (PNCco
86 matches
Mail list logo
