M67 Problem
31 Aug 2011 11:20 #12869
by Kap1eC
M67 Problem was created by Kap1eC
M67 Problem
Hello all. Need help with M67 command.
Anybody try to use this command? When I use it nothing happens in motion.analog-out-**.
For example:
%
M67 E0 Q1
G01 X10 F500
M67 E0 Q2
G01 X20 F500
M67 E0 Q5
G01 X30 F500
%
But motion.analog-out-00 = 0 all time. What's wrong?
In forums I read that M67 need patch, but all licks is bad. May be someone have this patch? =(
Need help.
Hello all. Need help with M67 command.
Anybody try to use this command? When I use it nothing happens in motion.analog-out-**.
For example:
%
M67 E0 Q1
G01 X10 F500
M67 E0 Q2
G01 X20 F500
M67 E0 Q5
G01 X30 F500
%
But motion.analog-out-00 = 0 all time. What's wrong?
In forums I read that M67 need patch, but all licks is bad. May be someone have this patch? =(
Need help.
Please Log in or Create an account to join the conversation.
31 Aug 2011 21:15 #12881
by andypugh
Replied by andypugh on topic Re:M67 Problem
Well, you are right, it doesn't work. Not in 2.4.6, not in 2.5.
Not that that is much help, but it isn't anything you are doing wrong.
Would M68 work for your purposes?
Not that that is much help, but it isn't anything you are doing wrong.
Would M68 work for your purposes?
Please Log in or Create an account to join the conversation.
01 Sep 2011 13:44 - 01 Sep 2011 13:45 #12884
by Kap1eC
Replied by Kap1eC on topic Re:M67 Problem
Every M68 command stops motors, but I need continuous motion with analog output control.
May be something ideas?
I try to use free axis as analog signal (for example B axis). I changes value in digital output with commands M62\M63. In moments, when value changes I takes coordinate of axis B.
This is work. Motors moves without stops, but speed is less that I wrote in G code.
May be something ideas?
I try to use free axis as analog signal (for example B axis). I changes value in digital output with commands M62\M63. In moments, when value changes I takes coordinate of axis B.
This is work. Motors moves without stops, but speed is less that I wrote in G code.
Last edit: 01 Sep 2011 13:45 by Kap1eC.
Please Log in or Create an account to join the conversation.
01 Sep 2011 13:53 #12885
by PCW
Replied by PCW on topic Re:M67 Problem
Maybe speed is limited by the B axis acceleration or velocity,
you might try setting the maximums for these up really high
since they don't control a mechanical axis.
you might try setting the maximums for these up really high
since they don't control a mechanical axis.
Please Log in or Create an account to join the conversation.
01 Sep 2011 14:01 #12886
by Kap1eC
Replied by Kap1eC on topic Re:M67 Problem
I try to increase speed in this axis, but nothing changes.
I also try to use M43.1 command. Its immediately sets the tool offset, which can be read from HAL. But it stops motion too =(
I also try to use M43.1 command. Its immediately sets the tool offset, which can be read from HAL. But it stops motion too =(
Please Log in or Create an account to join the conversation.
01 Sep 2011 14:38 #12887
by PCW
Replied by PCW on topic Re:M67 Problem
Which parameters did you set?
Please Log in or Create an account to join the conversation.
01 Sep 2011 15:30 #12890
by Kap1eC
Replied by Kap1eC on topic Re:M67 Problem
Parameters? What do you mean? I changed max velocity and max acceleration in [axis 4].
---
I want to change laser power during his movement. Value of power need take from G code file. Any ideas?
---
I want to change laser power during his movement. Value of power need take from G code file. Any ideas?
Please Log in or Create an account to join the conversation.
01 Sep 2011 16:58 #12893
by PCW
Replied by PCW on topic Re:M67 Problem
I am trying to understand why adding an axis that is not velocity or acceleration limited slows your motion. Do you have step functions in your analog out?
Please Log in or Create an account to join the conversation.
01 Sep 2011 17:14 #12894
by Kap1eC
Replied by Kap1eC on topic Re:M67 Problem
No. Without M62\M63 speed is normal. I think that these commands don’t work in real time.
Please Log in or Create an account to join the conversation.
01 Sep 2011 17:26 #12895
by andypugh
Replied by andypugh on topic Re:M67 Problem
Kap1eC wrote:
Can you show us the HAL file?
We have been here before, trying to help someone modulate laser power, so at least we won't be repeating the same errors.
M67 ought to be the correct solution. I am hoping that now we know it doesn't work, someone will make it work.
In the meantime, a spare axis is the way to go, I think. Just link the axis position cmd to a pwmgen in HAL, and it should all happen in real time.
You might want to consider moving the axis through very small distances, and then having a pwmgen with a large scale factor to compensate. However, setting the velocity limits of that axis to be very high should help. You might still be limited by the global max accel and max velocity limits (in the [TRAJ] section), hence my suggestion to make the moves very small in G-code and compensate elsewhere. 0 to 1 might be a good starting point that still makes sense.
Parameters? What do you mean? I changed max velocity and max acceleration in [axis 4].
---
I want to change laser power during his movement. Value of power need take from G code file. Any ideas?
Can you show us the HAL file?
We have been here before, trying to help someone modulate laser power, so at least we won't be repeating the same errors.
M67 ought to be the correct solution. I am hoping that now we know it doesn't work, someone will make it work.
In the meantime, a spare axis is the way to go, I think. Just link the axis position cmd to a pwmgen in HAL, and it should all happen in real time.
You might want to consider moving the axis through very small distances, and then having a pwmgen with a large scale factor to compensate. However, setting the velocity limits of that axis to be very high should help. You might still be limited by the global max accel and max velocity limits (in the [TRAJ] section), hence my suggestion to make the moves very small in G-code and compensate elsewhere. 0 to 1 might be a good starting point that still makes sense.
Please Log in or Create an account to join the conversation.
Time to create page: 0.113 seconds