Initial Height Skip (IHS) not functioning properly

More
4 years 5 months ago #243748 by phillc54
Hmm, it works fine here (on a sim).
It works down to a Skip IHS value of 0.4.
 

Please Log in or Create an account to join the conversation.

More
4 years 5 months ago #243751 by Uthayne
It's confusing because it works as intended if I do not enable the torch. It probes the first hole and then finishes the remainder without probing (THC Enabled, not active obviously because of no torch voltage).

When I enable the torch and actually cut it probes each time. There are no errors while cutting which would disable IHS skip.

Please Log in or Create an account to join the conversation.

More
4 years 5 months ago #243756 by phillc54

It's confusing because it works as intended if I do not enable the torch. It probes the first hole and then finishes the remainder without probing (THC Enabled, not active obviously because of no torch voltage).

When I enable the torch and actually cut it probes each time. There are no errors while cutting which would disable IHS skip.
That is odd because it probably wouldn't reach full velocity on those holes, THC would not be activated, then it should fall back to:
Code:
If the THC is disabled or if THC is enabled and not activated then the IHS skip will occur if the start of the cut is less than Skip IHS distance from the last successful probe.

Please Log in or Create an account to join the conversation.

More
4 years 5 months ago #243757 by Uthayne
My thoughts exactly

Please Log in or Create an account to join the conversation.

More
4 years 4 months ago #244690 by Uthayne
So I believe I've narrowed down the issue with this to this particular line in the plasmac.comp where axis_x_finish is set (see below).

When thc is enabled (but not active during a cut), it should use this block of code to determine the cut_offset and in turn compare that to skip_ihs_distance:
Code:
else if((axis_x_finish || axis_y_finish) && first_cut_finished){                             cut_offset = sqrt(pow(axis_x_finish - axis_x_position, 2) + pow(axis_y_finish - axis_y_position, 2));                             axis_x_finish = 0;                             axis_y_finish = 0;                         }

However, axis_x_finish and axis_y_finish are always set to 0 if auto_volts is enabled based on my testing. The causes the cut_offset calculation to be incorrect.

Here is the line which I believe is incorrect, as it is the only place that axis_x(y)_finish is set.
Code:
if(thc_enabled && ((!use_auto_volts || (use_auto_volts && target_volts)) || !torch_enable)){                     axis_x_finish = axis_x_position;                     axis_y_finish = axis_y_position;                 }else{                     axis_x_finish = 0;                     axis_y_finish = 0;                 }

Watching halmeter while cutting I can see that target_volts is always 0. This causes the ((!use_auto_volts || (use_auto_volts && target_volts)) to always be false when auto volts are enabled, and the OR comparison to !torch_enabled is always going to be false when we are cutting anyway. In turn, this causes axis_x_finish to always be 0 which breaks the IHS skip logic later on. This is verified by ENABLING THC, but DISABLING TORCH which causes the above else if statement to be true and axis_x/y_finish is correctly set. I mentioned that IHS skip functions properly if I do a dry run but not while the torch is on.

What is target_volts supposed to be set at? Should the statement be ((use_auto_volts || (!use_auto_volts && target_volts))?

I haven't dug into this any deeper after realizing that disabling auto volts causes IHS skip to function properly again. This should get me by for now...

Please Log in or Create an account to join the conversation.

More
4 years 4 months ago - 4 years 4 months ago #244702 by phillc54
target_volts is the voltage that the THC is attempting to maintain. If the velocity doesn't reach the cut feed rate then there will be no target voltage set.I can see what is happening (or not happening), I think a new flag is required to indicate whether THC was active at the end of the cut.

Edit:The attached patch seems to work OK, I will do a bit more testing tomorrow and will push if all goes well. 
Last edit: 4 years 4 months ago by phillc54.
The following user(s) said Thank You: Uthayne

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.392 seconds
Powered by Kunena Forum