Recent PlasmaC Update and No Motion

Purduepete's current configuration attached. lowpass is set to 50, debounce is 5,

how do i run his specific config as is, as a simulation? so i can poke and prod to see if i can get it to misbehave?
i was going to configure my 7i76e to match his setup 100% and try that to simulate his problem. (seems overkill but im half way to assembled)

Phillc54, I actually thought it was all good. If I run a program it runs fine with the torch off. No issues. If stopped in the middle there are no problems. If it completes no issues starting another. But when a cut program is run with the torch on only that program will complete. Runs great the whole time for the most part, I'll circle back to this, but after that program it will only do the first cut and then will do what it has been doing not moving after pierce.

I did have an issue running some 3/16 plate. Was trying a few different things and bumped my lowpass to 50 from 2 and debounce to 5 from 50. Because the THC was a lot more responsive it dove at the end cut when it hit a pierce. After it did it 3 or 4 times it retracted to its safe height and would not allow jog or anything after killing the cut program. Required a computer reboot as well.

Tesremos wrote: Purduepete's current configuration attached. lowpass is set to 50, debounce is 5,

how do i run his specific config as is, as a simulation? so i can poke and prod to see if i can get it to misbehave?
i was going to configure my 7i76e to match his setup 100% and try that to simulate his problem. (seems overkill but im half way to assembled)

Use the attached simplified hal file instead of cnc_plasma.hal

<machine-name>_connections.ini file:

comment out all [JOINT_n] lines begining with HOME_SEARCH_VEL, HOME_LATCH_VEL & HOME_FINAL_VEL

uncomment everthing in the ini file [APPLICATIONS] section

add APP = halshow my.halshow to the [APPLICATIONS] section if I need to watch any pins

<machine-name>_connections.hal file, comment out all lines except:

PurduePete wrote: Phillc54, I actually thought it was all good. If I run a program it runs fine with the torch off. No issues. If stopped in the middle there are no problems. If it completes no issues starting another. But when a cut program is run with the torch on only that program will complete. Runs great the whole time for the most part, I'll circle back to this, but after that program it will only do the first cut and then will do what it has been doing not moving after pierce.

I did have an issue running some 3/16 plate. Was trying a few different things and bumped my lowpass to 50 from 2 and debounce to 5 from 50. Because the THC was a lot more responsive it dove at the end cut when it hit a pierce. After it did it 3 or 4 times it retracted to its safe height and would not allow jog or anything after killing the cut program. Required a computer reboot as well.

Why are you changing the debounce value and the lowpass value. Are you taking Halscope readings that show this is required. Everyone I know uses the default values of lowpass = 0 and debounce = 5 which work well unless you have some electrical noise. A frequency of 2Hz seems a very odd number for lowpass and a debounce of 50 seems quite high. I am thinking that maybe you have electrical noise issues that you need to find. This may also have a bearing on the NaN reading that you occasionally get, I have not heard of that on any config I know about.

A NAN error or having to reboot to recover from a fault suggests a
hardware problem to me, perhaps on the host PC

Phillc54, at this point the only reason I've changed them is to just try something to get the machine running again. I messed with low pass initially because it helped with losing arc when I used mode 0. I use longer lead outs and it would dive. I never messed with debounce before this.

As for "nan", this was never an issue before the update. I had never even seen it before and didn't know that could read anything other than a number to be honest.