Pierce height would exceed Z axis maximum limit while ohmic probing
17 Apr 2021 20:03 #206219
by bevins
OK so if I get what your saying it gets a false probe say half way down and thinks the material is actually higher than it is and tries to go up.
I am using the one of the first Ohmic sensing circuit's rodw put out.
I will check the validity of this. It happens alot so I should be able to see the ohmic lite go on before it hits the material.
Ohmic sensing circuit.....
Replied by bevins on topic Pierce height would exceed Z axis maximum limit while ohmic probing
I am not using ohmic3, I am using Ohmic2. Not the thcad but input into mesa.
I don't understand what you're trying to tell me..?
It is using continuity ground energizing a relay not using thcad for the ohmic probe.
I don't have a problem with the dirty metal at all. I still dont understand the issue with the "Pierce height would exceed Z axis maximum limit while ohmic probing". I read the error message. This only makes sense to me iof after the first probe, it knows where the Z is, then for some reason plasmac comp raises the Z all the way up. Can I limit this because that would probably fix the error message becasue it would go no where near the Z max limit.
Since you arent using a THCAD (I thought you were), then I don't understand why you are using ohmic2. Ohmic, ohmic2, and ohmic3 are all components for doing "hypersensing" with a Mesa THCAD.
I've explained the error message. You are getting a false trip during the probe. It then thinks your material is MUCH higher than it is. And because of that, it knows that it has no room to get to pierce height. The message is valid.
I know nothing about your ohmic circuit, so I guess I can't tell you why you are getting false trips, but that's what is happening. You proved that because it works when you disable ohmic probing.
Finally, the torch goes to the top when this happens because you've encountered an error that caused the program to pause. When the program pauses, the torch goes up to the top. That's normal PlasmaC behavior, and has nothing to do with probing.
OK so if I get what your saying it gets a false probe say half way down and thinks the material is actually higher than it is and tries to go up.
I am using the one of the first Ohmic sensing circuit's rodw put out.
I will check the validity of this. It happens alot so I should be able to see the ohmic lite go on before it hits the material.
Ohmic sensing circuit.....
Attachments:
Please Log in or Create an account to join the conversation.
18 Apr 2021 11:48 - 18 Apr 2021 11:57 #206296
by bevins
I'll try that but I dont see the difference really.I didnt see the relay fire when I got this message last night. I was checking after snow sent me in this direction.
OK I attached the config and gcode where it goes no faster than 60 as it shows in the gui.
Valid arc lost.... I dont get that one. IT was at the end of an operation when it is leading out. Why would I get arc loss. The gcode was M5 cut stop, so why would the program pause? line 102 of gcode
Replied by bevins on topic Pierce height would exceed Z axis maximum limit while ohmic probing
Can you post a compressed file of your config and also the gcode file you are having issues with in regards to cut velocity.
When it stops with CYCLE PAUSE flashing is there a popup error message or a error message in the terminal.
Here is another way of wiring relays for ohmic similar to what islander261 was using, it may be worth a try.
Warning: Spoiler!
I'll try that but I dont see the difference really.I didnt see the relay fire when I got this message last night. I was checking after snow sent me in this direction.
OK I attached the config and gcode where it goes no faster than 60 as it shows in the gui.
Warning: Spoiler!
Valid arc lost.... I dont get that one. IT was at the end of an operation when it is leading out. Why would I get arc loss. The gcode was M5 cut stop, so why would the program pause? line 102 of gcode
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.128 seconds