- Posts: 5712
- Thank you received: 0
Recent PlasmaC Update and No Motion
Could you post your compressed config directory.
Edit:
Just to make sure we are on the same page I installed 2.9 from the Buildbot then installed the new plasmac.comp, edited plasmac.tcl as per the earlier post and I cannot get it to fault, it appears to do everything it should.
Please Log in to join the conversation.
- PurduePete
- Topic Author
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
Please Log in to join the conversation.
im unable to test on my machine other then simulations for now. i should be up and running for testing tommorrow.
Please Log in to join the conversation.
The new PlasmaC.comp uses this pin to clear offsets.
You need to find where else it is being used and change that Hal file to suit.
Edit: comment out line 291 in cnc_plasma.hal
Please Log in to join the conversation.
- PurduePete
- Topic Author
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
It does the same thing where it will retract to home after the job is complete and then not move any further with no jog control. I also still get nan every once in a while and have to restart linuxcnc until it goes away.
Please Log in to join the conversation.
Any error messages in the terminal?
Edit: you need to switch to manual mode to jog.
Edit2: In cnc_plasma_connections.hal try commenting out this line:
Please Log in to join the conversation.
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)
Please Log in to join the conversation.
- PurduePete
- Topic Author
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
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.
Please Log in to join the conversation.
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:
<machine-name>_connections.hal file, comment out all lines except:
Please Log in to join the conversation.
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.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.
Please Log in to join the conversation.
