hi
i found here
https://github.com/kubroid/bernardo_7i43/blob/master/pendant.hal
this
# step multiplier multiplexer
loadrt conv_s32_u32
addf conv-s32-u32.0 servo-thread
in line 64 65 66
question is in addf conv-s32-u32.0 servo-thread
or need to be --addf conv_s32_u32.0 servo-thread
or it does n
2014-10-20 19:26 GMT+03:00 Chris Radek :
> On Mon, Oct 20, 2014 at 04:05:06PM +0100, andy pugh wrote:
> > On 20 October 2014 15:39, Chris Radek wrote:
> >
> > > I admit I used halmeter and not the docs... I think they are
> > >
> > > #define EMC_MOTION_TYPE_TRAVERSE 1
> > > #define EMC_MOTION_TY
2014-10-20 17:39 GMT+03:00 Chris Radek :
> #define EMC_MOTION_TYPE_PROBING 5
Thank you very much for the tip, I already had spent considerable
amount of time, trying to figure out, how to determine, when machine
is doing a probing move, so that the probe can actually be deployed
without any additi
On 20 October 2014 15:22, Chris Radek wrote:
> I do not understand why motion.motion-type does not work for this.
> This is exactly the information it gives you.
It looks like it does.
Aram, all you need to do is compare the output of motion.motion-type
to something and send the output to a pin
On 20 October 2014 17:26, Chris Radek wrote:
> http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=src/emc/nml_intf/motion_types.h;h=8d9a430a09e002cb32f76b844ddfc7e0a2bcac17;hb=9f04c26dcc6705e1a9a33d3b4185bf4b607e236c
I learned two things today:
1) motion.motion-type is more useful than I tho
On Mon, Oct 20, 2014 at 04:05:06PM +0100, andy pugh wrote:
> On 20 October 2014 15:39, Chris Radek wrote:
>
> > I admit I used halmeter and not the docs... I think they are
> >
> > #define EMC_MOTION_TYPE_TRAVERSE 1
> > #define EMC_MOTION_TYPE_FEED 2
> > #define EMC_MOTION_TYPE_ARC 3
> > #define
On 20 October 2014 15:39, Chris Radek wrote:
> I admit I used halmeter and not the docs... I think they are
>
> #define EMC_MOTION_TYPE_TRAVERSE 1
> #define EMC_MOTION_TYPE_FEED 2
> #define EMC_MOTION_TYPE_ARC 3
> #define EMC_MOTION_TYPE_TOOLCHANGE 4
> #define EMC_MOTION_TYPE_PROBING 5
> #define
On Mon, Oct 20, 2014 at 03:33:56PM +0100, andy pugh wrote:
> On 20 October 2014 15:22, Chris Radek wrote:
>
> > I do not understand why motion.motion-type does not work for this.
> > This is exactly the information it gives you.
>
> Has that changed relative to the docs? Docs say:
I admit I use
On 20 October 2014 15:22, Chris Radek wrote:
> I do not understand why motion.motion-type does not work for this.
> This is exactly the information it gives you.
Has that changed relative to the docs? Docs say:
"motion.motion-type OUT S32
These values are from src/emc/kinematics/tc.h
1: Linear
On Fri, Oct 17, 2014 at 01:29:15PM -0700, a k wrote:
> I want really identify what kind of motion in any given moment -- is it G1
> (cutting -metal removing etc) or is it G0 (rapid motion to the next
> starting point)
I do not understand why motion.motion-type does not work for this.
This is exa
why not use the simple M3 M4 M5 codes for start stop ,
is this for 3d printing or pick and place ?
you could use a macro to do switching on and off or running code
On 20 October 2014 10:53, andy pugh wrote:
> On 20 October 2014 09:24, a k wrote:
> > so, i can not remap G0 and/or G1.
> > right
Hi Aram.
I was not exactly right before.
You have to use M67 Synchronized Analog Output that will allow you to
activate up to 16 analog output values (default AO number is 4 from 0 to 3 )
.
The Hal pins related to M67 are floating point type and their names are:
motion.analog-out-00
motion.analog-
On 20 October 2014 09:24, a k wrote:
> so, i can not remap G0 and/or G1.
> right/wrong?
That's what the docs say.
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
--
Comprehensive Server
Hi
by looking documentation
14. Remappable Codes 14.1. Existing codes which can be remapped
The current set of *existing* codes open to redefinition is:
· Tx (Prepare)
· M6 (Change tool)
· M61 (Set tool number)
· M0 (pause a running program temporarily)
·
Hi
i do not know a lot what emc2 can and can not do. so i open for all
recommendations.
about ---M1xx G1 X100 Y240 F100
so for example instead G1 will be M101G1
and instead G0 will be M102G0
system will pick up M101 and M102
am i right?
if so who will altered code that instead G0 put in M102G0 and
Why do not use a custom M function syncronized to do that ?
M1xx G1 X100 Y240 F100
Into the M1xx you can fit the Hal code to perform what you need.
Il giorno 17/ott/2014 21:30, "a k" ha scritto:
> About:
> I was wondering if motion.motion-type would work but that
> distinguishes between lines and
About:
I was wondering if motion.motion-type would work but that
distinguishes between lines and arcs rather then feeds or traverses.
Motion can be 2 type -- first -- when machine does deposition/cutting -
actual work and second - when machine position themself to the
next beginning point.
when ma
Hi Sebastian.
I was looking at the Integrator Manual at the section that describes the
motion Hal component.
Il giorno 17/ott/2014 20:49, "Sebastian Kuzminsky" ha
scritto:
> On 10/17/2014 08:44 AM, alex chiosso wrote:
> > Just a note .
> > The debugging pins aren't listed into the PDF doc (as I c
On 10/17/2014 08:44 AM, alex chiosso wrote:
> Just a note .
> The debugging pins aren't listed into the PDF doc (as I can see) .
> I was watching that documentation .
> Thanks again.
Which document are you looking at, Alex?
The only pdf i can see that mentions motion pins at all is this one:
htt
On 10/17/2014 08:35 AM, andy pugh wrote:
> On 17 October 2014 15:14, alex chiosso wrote:
>
>> Is "motion.motion-type" listed and described into the documentation ?
>> I didn't see any reference to this pin
> http://www.linuxcnc.org/docs/html/man/man9/motion.9.html
>
> (It is listed under debugging
Just a note .
The debugging pins aren't listed into the PDF doc (as I can see) .
I was watching that documentation .
Thanks again.
Alex
On Fri, Oct 17, 2014 at 4:40 PM, alex chiosso wrote:
> Thank you .
> I am blind . :-)
>
> Alex
>
> On Fri, Oct 17, 2014 at 4:35 PM, andy pugh wrote:
>
>> On 1
Thank you .
I am blind . :-)
Alex
On Fri, Oct 17, 2014 at 4:35 PM, andy pugh wrote:
> On 17 October 2014 15:14, alex chiosso wrote:
>
> > Is "motion.motion-type" listed and described into the documentation ?
> > I didn't see any reference to this pin
>
> http://www.linuxcnc.org/docs/html/man/m
On 17 October 2014 15:14, alex chiosso wrote:
> Is "motion.motion-type" listed and described into the documentation ?
> I didn't see any reference to this pin
http://www.linuxcnc.org/docs/html/man/man9/motion.9.html
(It is listed under debugging pins, and it is incorrect when it says
"These val
Hi Andy.
Is "motion.motion-type" listed and described into the documentation ?
I didn't see any reference to this pin .
Am I wrong ?
Regards
Alex
On Fri, Oct 17, 2014 at 1:32 PM, andy pugh wrote:
> On 17 October 2014 11:35, Marius Alksnys wrote:
> > Maybe motion.current-vel and comp hal compo
On 17 October 2014 11:35, Marius Alksnys wrote:
> Maybe motion.current-vel and comp hal component, connected to some
> output pin will do the task for you?
Yes, that is probably easier than a remap, I was answering the
question asked rather than the question intended.
I was wondering if motion.m
Maybe motion.current-vel and comp hal component, connected to some
output pin will do the task for you?
On 10/13/2014 08:23 PM, a k wrote:
> Hello
> is it possible to make to emc2 send/generate signal like I/O signal-5 V DC
> - when system reads G0 -rapid move?
> thank you
> aram
On 16 October 2014 21:24, a k wrote:
> in addition
> when machine will read
> G0.1 or G0.2 etc unallocated G-codes---
> will system generate Error - unrecognized code or simply skip them and move
> to the next ?
If the code doesn't exist, that is an error.
If you have created the code, then the
in addition
when machine will read
G0.1 or G0.2 etc unallocated G-codes---
will system generate Error - unrecognized code or simply skip them and move
to the next ?
On Thu, Oct 16, 2014 at 1:13 PM, a k wrote:
> Hi
> i did mistake -instead F0 i should say G0 and G1.
> sorry.
> i can see that G0
Hi
i did mistake -instead F0 i should say G0 and G1.
sorry.
i can see that G0 and G1 not remappable
but G code from ---14.2. Currently unallocated G-codes:
can be remap.
am i right?
thanks
aram
On Mon, Oct 13, 2014 at 10:56 AM, andy pugh wrote:
> On 13 October 2014 18:23, a k wrote:
> > Hel
On 13 October 2014 18:23, a k wrote:
> Hello
> is it possible to make to emc2 send/generate signal like I/O signal-5 V DC
> - when system reads F0 -rapid move?
Yes. But you might have to read some documentation.
http://www.linuxcnc.org/docs/html/remap/structure.html
Section 4.1 says that F is re
Hello
is it possible to make to emc2 send/generate signal like I/O signal-5 V DC
- when system reads F0 -rapid move?
thank you
aram
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Com
31 matches
Mail list logo
