Feature Request

phillc54 wrote:

I have thought about this and never came up with a good way to implement it.

Well, what if you just had a drop down that mimic'd the one in the run panel/tab? Then if you picked from an existing material type, it would populate the g-code with that information. If you dont choose a material type, it can default to using whatever is displayed in the run panel/tab when you cut (exactly how it is right now). Choosing the material type and having it use the actual kerf width, rather than the other method may prove useful if other features ever work their way into the Conversational. I know features are limited when cutter comp is running.

Also, I forgot to mention today during a cut interruption the Z Axis bounce at the top (offset problem) was present. I am honestly not sure what I did to cause it, I couldnt duplicate it, but I'm not sure the offset stuff is completely sorted out?

Speculating, but it may have been after I got a Joint Following Error and had to turn the machine back "on" with the orange button. I honestly cant recall as I did a lot of messing around this evening. Clicking the orange power button off and then on and re-homing solved it, and it didnt seem to come back.

Ok, so the Z axis offset wiggle/spring effect is definitely back. I apologize in advance for the lengthy post. Just trying to be thorough

This relates to the Joint following error stuff that @Mud was having. I didn't want to muddy that post. I believe there might be some ini settings that aren't helping anything, but the Joint 3 error is related because it's highlighting a problem with the Z axis offset/probing stuffs. Even Peter seemed surprised he was only getting this on the Z axis joint. Similarly, I've slowed my Z velocity and Accelerations WAY down, and previously followed Peter's advice to increase my StepGen numbers. I think my settings are fine at this point.

I want to be clear that I only get the Z axis following error on my Z axis, and only when retracting from a cut.

I noticed that when the torch retracts at the M5 $0, it changes pitches. It's like it's executing two different Z movements, at two different speeds. Sometimes it is more pronounced than others (when it does it the loudest, it always results in the Z wiggle). I did notice that I can't get this to happen below 92.2 inches per minute. (I did a lot of probing to figure that out ). My default setup speed is 150ipm. The machine is actually capable of much faster, so hopefully we get this ironed out. I attached a zip of my config folder so you can see the axis' settings.

Steps to reproduce:

1. Turn the setup speed greater than 92.2ipm (my default was 150ipm)
2. Run the G-Code posted below
3. Jog Z down then up to see if you got the Z wiggle
4. Run the G-Code posted below
5. Jog Z down and then up, you should have the Z axis spring/wiggle now

One time I had an error where it would go to the probe height and sit. It would not progress past that until I shut down Linuxcnc and restarted it. So far, I could not get it to reproduce the error, that only seemed to happen once and I couldn't figure out what I did to get it to mess up.

After a bunch of testing, I did get a few Joint 3 follow errors. Since I'm running Torch Disabled at this time, I can see exactly where it stopped. Without knowing exactly what is going on inside the code, it seems like after a cut it rapids to the probe height, and then rapids to the top of the Z travel (or wherever you had it parked when you started). Is that correct? It routinely gives the Joint Follow error near the probe height, on torch retract, which if what I suspect about how the Z movements execute is true, maybe it's because there's something weird going on with the offsets/movement speeds and it's asking the joint to make some really tiny movements too quickly that are causing it to error out?

If you listen closely to the youtube video below, when the torch retracts at the end of the cut, you can hear that for a super brief period, there is a portion of that Z movement that speeds up and sounds way faster than the rest. As I said, this is more pronounced the times that result in ending with the Z Wiggle.



Hopefully that helps, happy to gather more data if needed. Thanks!

rodw wrote:

What happens if you reduce your Z axis acceleration in your ini file?

Please see above post (#181020):

snowgoer540 wrote:

Similarly, I've slowed my Z velocity and Accelerations WAY down, and previously followed Peter's advice to increase my StepGen numbers. I think my settings are fine at this point.

phillc54 wrote:

Is there any change if you put a G0 Xn Yn movement between the M68... line and the G20... line

As long as you mean:
Then no, there is no change:

phillc54 wrote:

Yep, that is what I meant. I'll have a look see when I get back home. In the meantime can you post your config.

In the spirit of anticipating the needs of the lead developer, I posted a .zip of my config folder a few posts up: Here, for your convenience

Thanks Phill