Another plasma component...
What is verified: p_comp:float-switch is connected to my input pin and is correct when checked with Hal Meter
When I run imperial_squares.ngc test file it rapids to the touchoff point and begins to lower the Z axis. At this point I have my hand on the floating z to trigger the float switch. After it has traveled a bit I will engage the float switch. It continues to move Z- for a bit (not always the same amount, but always a considerable amount after contact) and I can verify this by monitoring p_comp:offset-counts. At some point, it will slow down and reverse direction, looking for the switch to unlatch. When that happens it then does continue on with firing the torch.
I've tried altering the debounce delay from 1 to 10 and 100. Nothing changes.
Could you let me know the following values in the Configure tab of the GladeVCP panel:
Trying this out on my machine and I believe I've made all of the necessary machine input/output edits to get it running, but I'm having issues with the probing sequence, mainly detecting initial probe contact.
If Probe Speed is greater than Max. Speed, set it to a value equal to or less than Max. Speed and let me know if that fixes the problem.
Debounce delay should be as low as possible, 1 works well for the mechanical microswitch I have tested with.
You also need the following changes in your ini file:
[AXIS_Z] MIN_LIMIT = -3.0 (this should be equal to [JOINT_2]MIN_LIMIT) MAX_VELOCITY = 0.50 (this should be double [JOINT_2]MAX_VELOCITY) MAX_ACCELERATION = 20 (this should be double [JOINT_2]MAX_ACCELERATION)
Btw, these were my settings on the gladevcp panel:
Max. Speed : 30
Setup Speed : 15
Probe Speed : 40
I'll update these as well
Edit: I found that changing configuration modes (0, 1, 2) was not updating. Not sure if this was handled somewhere else, but I fixed it by adding "setp plasmac.mode [PLASMAC]MODE" to the plasmac.hal file
1. IHS can be disabled if new cut start position is less than 'Skip IHS' distance (in machine units) from the last cut end position. Skip IHS is disabled on errors. For example if there is a arc failure while cutting then IHS will be performed regardless of where the cut is.
2. Config file has been changed so it doesn't use gladevcp.persistence. This causes problems when adding new features that require saving. Existing config files will be automatically updated on the first run.
There are three hal pin name changes associated with IHS disable that will need to be changed in any existing plasmac.hal and plasmac_panel.hal files:
plasmac.axis-min-limit is now plasmac.axis-z-min-limit plasmac.axis-max-limit is now plasmac.axis-z-max-limit plasmac.axis-position is now plasmac.axis-z-position
You may wish to consider using the last IHS point for your distance origin rather than the end of the previous cut. Your method assumes an accurate height at the end of the previous cut.
Thanks guys, yes I was assuming that the last cut height would be accurate.
Yes John is right, You need to base your distance calculation from the last probe event as that is the last time we know the height was accurate.
I see in the Hypertherm ArcGlide manual (p159) that they do it this way but disable it if THC was not active or Sample Voltage mode was inactive. Which I forgot to do...
So which way to go, or make it user selectable or am I trying to do too much here...
THC Enabled and Sample Voltage problem has been fixed.
I think when I did this, I started with a needs_probe pin that was true when it needs to probe on power up. Once probed, I turned it off and only enabled it when it was > the skip probe distance. That made the pin independent of any plasma cutting.
By connecting the output to a motion digital pin, M66 Pnn L0 (wait on input immediate) would return the state in #5399 so you could branch to the probe routine or not in gcode but you can do that in the component.