Hello Guest it is March 28, 2024, 05:08:55 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - litronics

Pages: 1
1
Additional to my probing interrupted error I have another strange isse.

I can run my Macro twice with just that "probing interrupted" error. At the third execution I get an additional error saying "Probing signal active!  Cannot continue."

Unfortunately this error message is not issued somwhere internal MACH4 and my macro doesn't get any feedback on that error and I cannot act appropriately.

As in the other Post - here is the log the macro generates (the mentioned error message is on line 92):
Code: [Select]
M1005 debug: initial check on probe contact: 0
M1005 debug: calculated StartHeight (-39) and StopHeight (-70)

M1005 debug: do the first probing with higher speed
G-Code:
G00 G80 G40 G49 G90
G00 G53 Z0.0
G00 G53 X307.0000 Y490.0000
G00 G53 Z-39.0000
G91 G31 Z-70.0000 F500.


Probing interrupted
M1005 debug: verify probe contact after quick approach: 1

M1005 debug: retract spinde
G-Code:
 G91 G00 Z1.0000


M1005 debug: slow tool probe
G-Code:
 G91 G31 Z-1.5000 F20.


M1005 debug: verify probe contact after slow approach: 1

M1005 debug: move spinde all the way up: G90 G00 G53 Z0.0


M1005 debug: Probed Z-Value: -107.4575 and calculated ZOffset: 0.1425

Auto tool setting complete, Offset = 0.1425
M1005 debug: initial check on probe contact: 0
M1005 debug: calculated StartHeight (-39) and StopHeight (-70)

M1005 debug: do the first probing with higher speed
G-Code:
G00 G80 G40 G49 G90
G00 G53 Z0.0
G00 G53 X307.0000 Y490.0000
G00 G53 Z-39.0000
G91 G31 Z-70.0000 F500.


Probing interrupted
M1005 debug: verify probe contact after quick approach: 1

M1005 debug: retract spinde
G-Code:
 G91 G00 Z1.0000


M1005 debug: slow tool probe
G-Code:
 G91 G31 Z-1.5000 F20.


M1005 debug: verify probe contact after slow approach: 1

M1005 debug: move spinde all the way up: G90 G00 G53 Z0.0


M1005 debug: Probed Z-Value: -107.6175 and calculated ZOffset: 0.017500000000013

Auto tool setting complete, Offset = 0.0175
M1005 debug: initial check on probe contact: 0
M1005 debug: calculated StartHeight (-39) and StopHeight (-70)

M1005 debug: do the first probing with higher speed
G-Code:
G00 G80 G40 G49 G90
G00 G53 Z0.0
G00 G53 X307.0000 Y490.0000
G00 G53 Z-39.0000
G91 G31 Z-70.0000 F500.


Probing interrupted
M1005 debug: verify probe contact after quick approach: 1

M1005 debug: retract spinde
G-Code:
 G91 G00 Z1.0000


M1005 debug: slow tool probe
G-Code:
 G91 G31 Z-1.5000 F20.


Probing signal active!  Cannot continue.
M1005 debug: verify probe contact after slow approach: 1

M1005 debug: move spinde all the way up: G90 G00 G53 Z0.0


M1005 debug: Probed Z-Value: -108.75 and calculated ZOffset: 1.15

Auto tool setting complete, Offset = 1.1500

As I am not changing anything between the execution of the macro I really don't understand where this error comes from.

Any idea is highly appreciated!

2
I am working on my automated tool length sensor and struggling with some errors which are not connected to my LUA script.

Within the M1005 macro I have added a lots of debugging messages to get a understanding what's going on. This is my log:
Code: [Select]
Home switch Z Home tripped!
Home switch X Home tripped!
Home switch Y Home tripped!
M1005 debug: initial check on probe contact: 0
M1005 debug: calculated StartHeight (-39) and StopHeight (-70)

M1005 debug: do the first probing with higher speed
G-Code:
G00 G80 G40 G49 G90
G00 G53 Z0.0
G00 G53 X307.0000 Y490.0000
G00 G53 Z-39.0000
G91 G31 Z-70.0000 F500.

Probing interrupted
M1005 debug: verify probe contact after quick approach: 1

M1005 debug: retract spinde
G-Code:
G91 G00 Z1.0000


M1005 debug: slow tool probe
G-Code:
G91 G31 Z-1.5000 F20.


M1005 debug: verify probe contact after slow approach: 1

M1005 debug: move spinde all the way up: G90 G00 G53 Z0.0


M1005 debug: Probed Z-Value: -107.4775 and calculated ZOffset: 0.12249999999999

Auto tool setting complete, Offset = 0.1225

Within the log there is a line saying "Probing interrupted". This line is actually NOT logged from my macro.

Is anybody able to explain where this message comes from and how I could find out why the probing has been interrupted there?

3
Mach4 General Discussion / Tool Length / Soft Limits - Questions
« on: April 17, 2018, 09:28:26 AM »
Hi all,

I am really new to the CNC world and starting to learn how everything works together.

Currently I am trying to understand the tool lenght offset together with the soft limits and how they connected.

To figure out the tool length I am using the script provided in the LUA scripting manual with some changes to fit my machine and a fixed tool length sensor.
Soft Limits are configured to stop jogging close to the end positions in all axes.

With a tool offset of 0 that works really well - but lately I had the issue that I couldn't run the code and MACH complained that I command Z-axis beyond soft limits.
But sitting in front of the machine everything was fine and I can't see (except the tool length offset) why this would happen.

So from a work coordinate system I could travel up to +69 (which is also the soft limit Z=0 on machine coordinate system) then I commanded "G01 Z65" and get the message that I command beyond configured soft limits.

Funny as I can jog to that hight easily but not command to it.

I guess I have either some problems understanding how soft limits work or I did something wrong while setting the tool offset.

As I believe that soft limits only work with machine coordinates and not interfer with work coordinates there must be an issue with the offset field I am using.

As I would like to measure the tool offset based on a gauge line  - what field do I need to use to separate soft limits from the tool length offset?

Thanks for reading this long post and your suggestions!

4
Mach4 General Discussion / G53 G00 G90 Z0 - movement with Build 3485
« on: March 25, 2018, 06:05:54 AM »
Just updated to the latest build.

The block "G53 G00 G90 Z0", to my understanding, should move only the Z-axis to the machine coordinate 0 and not move in any other direction. In my case the spindle goes all the way up.

However, since the update this block also moves X- and Y-axis to some coordinate what it shouldn't do.

Does anyone experience the same?

5
Hi,
my MACH4 installation has issue using the right codepage/character sets and I am wondering if I it is possible to configure it somewhere.

Mainly I have two issues:

1. If I have a German special character (ä,ö or ü) within the filename, MACH4 is not able to open that G-Code file and I get the error message that the file could not be found.
2. When opening a G-Code file containing those characters they are replaced by some other characters within the "G Code" window. However - the editor, when clicking on edit code, works fine.

Anybody an idea if that is configureable somewhere or do I need to open an issue ticket?

Thanks for your help!

6
Mach4 General Discussion / Rotating tool path
« on: March 15, 2018, 01:07:21 PM »
Hi all,

I am coming from WinPC NC and just started to use MACH4.
From the WinPC interface I have the option to rotate the tool path in 90° steps to align it on the workarea.

Am I not seeing this option in MACH or is it not possible?

Thanks for your help!

7
Thanks Allan!

tose two lines are working :)

8
Hi all,
I just started to get my head arround the LUA stuff and trying to get a simple singnal scirpt working.

As a simple starting point I wanted to use my Probe to actually trigger the status of an general output.
I have added a few lines of code in my SigLib in the Screen Load script:

Code: [Select]
[mc.ISIG_PROBE] = function (state)
    inst = mc.mcGetInstance()
    local out1handle = mc.mcSignalGetHandle(inst, mc.OSIG_OUTPUT1)
    local out1state = mc.mcSignalGetState(out1handle)
    if (state == 1) then     
        mc.mcSignalSetState(out1state, true)
    else
        mc.mcSignalSetState(out1state, false)
    end
end,

As far as I understand it should act on my Probe as input.
Get the handle and state for desired output and set it accordingly.

However - this doesn't actually work.

What am I doing wrong here??

Pages: 1