Hello Guest it is March 28, 2024, 11:28:33 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 - barneskite28

Pages: 1 2 3 4 5 6 7 8 »
1
i noticed tonight my post processor was mach3, so i changed it to mach4 and no issue since!  so the g code can cause the software to close in my case!

2
Hi Its an MB2 + ESS for the motion controller...
The licence is good, just checked.
Other thing i noticed just now, is I'm getting a message that says "failed to retrieve file times for c\mach4hobby\profiles....... Macros\M162.mcc'
The system failed to find the file specified"
This appeared from nowhere - i didn't modify anything.
It really frustrates me that Mach4 just cant be stable for a long time...... i use the machine sporadically, so it could be switched off for 2 months and the amount of times it has changed itself is just weird.. i have never had any other software that does this.

3
Mach4 General Discussion / Mach4 software crash at same point in gcode
« on: March 28, 2023, 06:38:40 PM »
I have a weird problem, where (repeatably) when i run a certain gcode file, the software just exits at the same point and there is no mach present..
Machine just halts but does not stop spindle etc
No errors or warnings

Ant ideas??

4
Mach4 General Discussion / Re: Again with the tool setter
« on: June 16, 2022, 04:11:20 AM »
Hi,
Essentially my machine is referenced to the home switches - which are all proximity switches.  The tool lengths reference the distance from the spindle nose, and the work offset is just a zero point at a specific machine coordinate.  In this case i have had good luck with power down and power on - but with Mach4 being so buggy it sometimes does not store the last WCS.  If i am doing a critical job i have also cut a reference circle into my bed/fixture plate - so if all else fails i can model from that point and always ensure to reset within a couple of thou.  The issue that i do have as i mentioned before - is on the z0 moving on the foirst couple of cycles - it did it twice today - the first run being 130mm too high, and the second being 0.8mm too low.  after another setting of z0 it was fine 

5
Mach4 General Discussion / Re: Again with the tool setter
« on: June 01, 2022, 09:46:07 AM »
Hey Barneskite28,

Did you ever find a resolution to this?  I have been researching the gauge line method for tool offsets, and this is a quagmire of 'scripts' written by all sorts of folks with differing opinions.  And, the posts from the folks who actually might know what is going on act like scripting is something everyone is adept at.  I agree with one of your first comments - we pay for this, especially the Industrial version.  On top of that, we can't get support direct, as we are OEM and our vendor knows less than we do.

So - did you find a solution?  Were you attempting to use the 'master tool' or 'gauge line' foundation for your tool offset?  I really want my tool offsets to be independent from any table or bed reference, only referenced from the gauge line or spindle nose - like every other machine we have. 

Thanks - and I appreciate your frustrations!

Yes i did manage to get my code working, and i used the dimension from the spindle face to the tool setter to make the tool length calculations.  Up to now this has been working ok apart from a coupe of issues that are unrelated in my mind to the code.  First issue is sometimes the fist tool change after power up (and yes, after activating offsets first and then zero the workpeice) can be ~10mm off, forcing me to re-zero the work piece z0 after which all tool changes are spot on.  Second issue, is recently out of the blue Mach4 started to hang when the tool setter was reached - every time.  powered down and back up and the same story.  No idea why but it caused me a massive pita, had to detlete mach, reinstall and restore the mach config and then reinstate the same code which then worked fine again.  This is more frustrating than getting it to work in the first place, and proves to me that for some reason known only to the programmers Mach4 is not robust and stable enough to provide reliable operation.  For me it has worked fine for 100's of power cycles, then out of the blue screwed itself up with no input from me.  It just started happening one time after power up and would not go away without me reinstalling everything.

The other strange issue i have seen is sometimes during the homing sequence mach has a pause after reaching the endstops.... not all the time though.  I have checked the PC and it is running fine with no lack of resources, and nothing else running.

I will re-post my working tool change script for you so that you can see how it works for mine, and you can modify for your machine.

6
Mach4 General Discussion / Re: Strange mach4 behavior
« on: May 04, 2022, 06:26:43 PM »
1 the first time i run gcode the tool is set, height is set, but the first z move is often wrong by 10mm or so.  after re-setting the wpc 0 its fine.

I am having the exact same problem. Z axis exactly moves down about 10mm and crashes. I ruined countless end mills.

Have you find a solution?
I didn't find a solution other than reducing rapid first run, resetting the program if the tool is not close to where I expect it should be from the top of the workpiece, then we setting the z height if needed.

7
Mach4 General Discussion / Re: Strange mach4 behavior
« on: April 21, 2022, 03:32:40 PM »


My M6 macro

Code: [Select]
function m6()
   
local inst = mc.mcGetInstance()

----------------------------------------------------------------------------------
--change lines here to either auto rapid, or manually jog to a tool change position
----------------------------------------------------------------------------------
--Manual Lines. Uncomment line below to allow you to manually jog to a tool change position.
--local MyChoice = wx.wxMessageBox("Click OK, \nThen Jog to A Safe Tool Change Position,\nInsert New tool,\nThen Click Cycle Start.","Click OK to continue" , 16)
---------------------------------------------------------------------------------
--Auto Lines.  Uncomment both lines below (and comment out local MyChoice line above) to automatically move to tool change position.
--Edit to include the machine coordinate values of that tool change position.

--AUTO LINES
mc.mcCntlGcodeExecuteWait(inst, "G53 G0 Z-5\nG53 G0 X200.0 Y20.0")--Move the Z to Home.Then to the X, Y Coords for our touch pad.
mc.mcCntlSetLastError(inst, 'Now in Tool Change Position. Hit Cycle Start!')
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
local posmode = mc.mcCntlGetPoundVar(inst, mc.SV_MOD_GROUP_3) --get the current mode so we can return to it when macro ends
local selectedtool = mc.mcToolGetSelected(inst)
local currenttool = mc.mcToolGetCurrent(inst)
   
 if selectedtool == currenttool then
        mc.mcCntlSetLastError(inst, "Current tool == Selected tool so there is nothing to do")
        do return end
 end
  mc.mcCntlToolChangeManual(inst, true);
  mc.mcCntlSetLastError(inst, "Current tool == " .. tostring(selectedtool) .. "   Previous Tool == " .. tostring(currenttool))
  mc.mcToolSetCurrent(inst, selectedtool)

  --local MyChoice = wx.wxMessageBox("Click Ok to Begin Probing the New Tool","Click OK to continue" , 16)
    mc.mcCntlGcodeExecuteWait(inst, "G53  G90 G0 X24.0 Y436.0")--
        mc.mcCntlSetLastError(inst, "Probing in Progress!")
        mc.mcCntlGcodeExecuteWait(inst, " G90 G31 Z-95. F150.")--probe the new tool
local probedz = mc.mcCntlGetPoundVar(inst, mc.SV_PROBE_POS_Z) -- Z Probe position in Machine coords
        mc.mcCntlGcodeExecute(inst, string.format('G ' .. posmode))--return to pre macro mode G90, or G91
  mc.mcCntlGcodeExecuteWait(inst, "G00 G53 Z0 ")--Retract
 
local NewOffset = probedz
  mc.mcToolSetData(inst, mc.MTOOL_MILL_HEIGHT, selectedtool, NewOffset)
  mc.mcCntlSetLastError(inst, string.format("Auto tool setting complete, Offset = %.4f", NewOffset))
wx.wxMessageBox("Toolchange Complete.\nTLO Set")
end

if (mc.mcInEditor() == 1) then
 m6()
end


8
Mach4 General Discussion / Re: Strange mach4 behavior
« on: April 21, 2022, 03:32:24 PM »
Update- after re-installing mach 4 and ess again the behaviour is repeatable..
same issue log below

2022-04-21 20:17:37.297 - Logging Enabled.
2022-04-21 20:17:37.335 - SoftSync()! Clearing planner. gcodeexec.cpp:168
2022-04-21 20:17:37.626 - Waiting on planner to drain before waiting on SetStill... runcanon.cpp:92
2022-04-21 20:17:37.626 - Waiting on SetStill...
2022-04-21 20:17:37.626 - Controller::RunCanonBuffer called AddStopReportRequest() runcanon.cpp:101
2022-04-21 20:17:37.626 - Requesting a stopped report for axis 0 motors.
2022-04-21 20:17:37.626 - Requesting a stopped report for motor 0.
2022-04-21 20:17:37.626 - Requesting a stopped report for axis 1 motors.
2022-04-21 20:17:37.626 - Requesting a stopped report for motor 1.
2022-04-21 20:17:37.626 - Requesting a stopped report for motor 5.
2022-04-21 20:17:37.626 - Requesting a stopped report for axis 2 motors.
2022-04-21 20:17:37.626 - Requesting a stopped report for motor 2.
2022-04-21 20:17:37.805 - API: mcMotionSetStill(inst = 0, motor = 0) (Called by ESS)
2022-04-21 20:17:37.805 - SetStill(): Motor 0 last position reported = 55389.1500 controller.cpp:1400
2022-04-21 20:17:37.805 - Axis 1 reports that it is still moving! controller.cpp:1407
2022-04-21 20:17:37.806 - >>>--- ESS: Reporting Stopped: Motor 0 55389.150000   #B
2022-04-21 20:17:37.806 - API: mcMotionSetStill(inst = 0, motor = 1) (Called by ESS)
2022-04-21 20:17:37.806 - SetStill(): Motor 1 last position reported = 440396.0000 controller.cpp:1400
2022-04-21 20:17:37.806 - Axis 1 reports that it is still moving! controller.cpp:1407
2022-04-21 20:17:37.806 - >>>--- ESS: Reporting Stopped: Motor 1 440396.000000   #B
2022-04-21 20:17:37.806 - API: mcMotionSetStill(inst = 0, motor = 2) (Called by ESS)
2022-04-21 20:17:37.806 - SetStill(): Motor 2 last position reported = -960.0000 controller.cpp:1400
2022-04-21 20:17:37.806 - Axis 1 reports that it is still moving! controller.cpp:1407
2022-04-21 20:17:37.806 - >>>--- ESS: Reporting Stopped: Motor 2 -960.000000   #B
2022-04-21 20:17:37.806 - API: mcMotionSetStill(inst = 0, motor = 5) (Called by ESS)
2022-04-21 20:17:37.806 - SetStill(): Motor 5 last position reported = 440396.0000 controller.cpp:1400
2022-04-21 20:17:37.806 - All motors marked as still.
2022-04-21 20:17:37.806 - >>>--- ESS: Reporting Stopped: Motor 5 440396.000000   #B
2022-04-21 20:17:37.806 - Waiting on SetStill is Done!
2022-04-21 20:17:37.858 - SoftSync()! Clearing planner. controlset.cpp:210
2022-04-21 20:17:37.858 - API: mcCntlGcodeExecute(inst = 0, commands = 'g43 h4.0') (unknown caller)
2022-04-21 20:17:37.972 - SoftSync()! Clearing planner. gcodeexec.cpp:168
2022-04-21 20:17:38.126 - SoftSync()! Clearing planner. controlset.cpp:210
2022-04-21 20:17:38.126 - Signal id 1052, (Output #2), changed from LOW to HIGH.
2022-04-21 20:17:38.128 -        ESS: Activating output Port3-Pin9 - Y309 solenoid 1
2022-04-21 20:17:38.629 - Signal id 1052, (Output #2), changed from HIGH to LOW.
2022-04-21 20:17:38.629 -        ESS: Deactivating output Port3-Pin9 - Y309 solenoid 1
2022-04-21 20:17:38.629 - API: mcCntlGcodeExecute(inst = 0, commands = 'g53 G31 z-150 f200') (unknown caller)
2022-04-21 20:17:38.742 - SoftSync()! Clearing planner. gcodeexec.cpp:168
2022-04-21 20:17:38.744 - Attempt transition from "MDI Running" on event "Probe" runcanon.cpp:536
2022-04-21 20:17:38.744 - S_MDI_RUNNING2_on_exit
2022-04-21 20:17:38.744 - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2022-04-21 20:17:38.745 - ACTION_start_probe
2022-04-21 20:17:38.746 - >>>>> ESS Probe 0, Starting.

2022-04-21 20:17:38.748 - S_MDI_PROBING_on_entry
2022-04-21 20:17:38.748 - Signal id 1173, (Machine Probing), changed from LOW to HIGH.
2022-04-21 20:17:38.750 - Probing: Waiting on exit event... runcanon.cpp:267
2022-04-21 20:17:38.750 - Waiting on planner to drain before waiting on SetStill... runcanon.cpp:92
2022-04-21 20:17:38.751 - >>>>ESS: Switching from NORMAL to PROBE state for Probe 0
2022-04-21 20:17:38.979 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:39.209 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:39.439 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:39.663 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:39.886 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:40.113 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:40.341 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:40.567 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:40.798 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:41.024 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:41.248 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:41.473 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:41.702 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:41.932 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:42.160 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:42.386 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:42.609 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:42.839 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:43.068 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:43.293 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:43.518 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:43.752 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:43.984 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:44.211 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:44.434 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:44.664 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:44.888 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:45.113 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:45.344 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:45.572 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:45.801 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:46.028 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:46.255 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:46.480 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:46.704 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:46.928 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:47.152 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:47.376 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:47.604 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:47.830 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:48.054 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:48.282 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:48.506 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:48.734 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:48.958 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:49.183 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:49.411 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:49.641 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:49.869 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:50.092 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:50.323 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:50.549 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:50.777 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:51.002 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:51.225 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:51.456 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:51.682 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:51.907 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:52.130 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:52.355 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:52.585 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:52.810 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:53.038 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:53.263 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:53.490 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:53.718 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:53.945 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:54.168 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:54.394 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:54.622 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:54.851 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:55.080 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:55.305 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:55.534 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:55.759 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:55.984 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:56.211 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:56.438 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:56.663 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:56.891 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:57.118 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:57.345 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:57.575 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:57.805 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:58.029 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:58.258 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:58.487 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:58.715 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:58.943 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:59.172 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:59.401 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:59.628 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:17:59.854 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:00.080 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:00.306 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:00.533 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:00.761 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:00.988 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:01.220 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:01.448 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:01.673 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:01.899 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:02.126 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:02.353 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:02.582 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:02.806 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:03.035 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:03.263 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:03.490 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:03.714 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:03.938 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:04.165 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:04.394 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:04.616 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:04.845 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:05.074 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:05.303 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:05.525 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:05.753 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:05.981 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:06.204 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:06.431 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:06.654 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:06.884 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:07.107 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:07.334 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:07.565 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:07.801 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:08.030 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:08.258 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:08.489 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:08.722 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:08.949 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:09.176 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:09.402 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:09.629 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:09.855 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:10.082 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:10.310 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:10.538 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:10.761 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:10.988 - -----ESS: Checking for Probe0 Strike, none yet...
2022-04-21 20:18:11.046 - Signal id 161, (Probe), changed from LOW to HIGH.
2022-04-21 20:18:11.047 - Signal id 186, (Motion Inhibit), changed from LOW to HIGH.
2022-04-21 20:18:11.047 - -----ESS: Mach ACKs Probe0 input signal ON!
2022-04-21 20:18:11.047 - Signal id 5, (Input #4), changed from LOW to HIGH.
2022-04-21 20:18:11.053 - API: mcMotionSetProbePos(inst = 0, motor = 0, position = 55389.1500) (Called by ESS)
2022-04-21 20:18:11.053 - API: mcMotionSetProbePos(inst = 0, motor = 1, position = 440396.0000) (Called by ESS)
2022-04-21 20:18:11.053 - API: mcMotionSetProbePos(inst = 0, motor = 2, position = -35288.0000) (Called by ESS)
2022-04-21 20:18:11.053 - API: mcMotionSetProbePos(inst = 0, motor = 3, position = 0.0000) (Called by ESS)
2022-04-21 20:18:11.053 - API: mcMotionSetProbePos(inst = 0, motor = 4, position = 0.0000) (Called by ESS)
2022-04-21 20:18:11.053 - API: mcMotionSetProbePos(inst = 0, motor = 5, position = 440396.0000) (Called by ESS)
2022-04-21 20:18:11.053 - ^^^^^^ ESS: Success! Probe0 Strike. Switching from PROBING to PROBING_CLEANUP state.
2022-04-21 20:18:11.081 - ^^^^^^ ESS Probe0 Finished: The device is still and the buffer is empty.
2022-04-21 20:18:11.082 - API: mcMotionClearPlanner(inst = 0) (Called by ESS)
2022-04-21 20:18:11.082 - API: mcMotionSetProbeComplete(inst = 0) (Called by ESS)
2022-04-21 20:18:11.083 - Recording latched probe positions.
2022-04-21 20:18:11.084 - Attempt transition from "Probing" on event "Probe Complete" machapi.cpp:1519
2022-04-21 20:18:11.085 - S_FILE_PROBING_on_exit
2022-04-21 20:18:11.085 - Signal id 1173, (Machine Probing), changed from HIGH to LOW.
2022-04-21 20:18:11.085 - ACTION_stop_probe
2022-04-21 20:18:11.086 - >>>>> ESS Probe 0, Done

2022-04-21 20:18:11.089 - S_MDI_RUNNING2_on_entry
2022-04-21 20:18:11.089 - Waiting on SetStill...
2022-04-21 20:18:11.089 - Signal id 1180, (Feed Hold Disabled), changed from LOW to HIGH.
2022-04-21 20:18:11.089 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2022-04-21 20:18:11.089 - Controller::RunCanonBuffer called AddStopReportRequest() runcanon.cpp:101
2022-04-21 20:18:11.090 - Requesting a stopped report for axis 0 motors.
2022-04-21 20:18:11.090 - Requesting a stopped report for motor 0.
2022-04-21 20:18:11.090 - Requesting a stopped report for axis 1 motors.
2022-04-21 20:18:11.090 - Requesting a stopped report for motor 1.
2022-04-21 20:18:11.090 - Requesting a stopped report for motor 5.
2022-04-21 20:18:11.090 - Requesting a stopped report for axis 2 motors.
2022-04-21 20:18:11.090 - Requesting a stopped report for motor 2.
2022-04-21 20:18:11.090 - 
2022-04-21 20:18:11.090 - -----===== Mach4 build 4.2.0.4612, ESS build 278.1 =====-----
2022-04-21 20:18:11.090 - 
2022-04-21 20:18:11.825 - Signal id 1180, (Feed Hold Disabled), changed from HIGH to LOW.
2022-04-21 20:18:11.826 - Waiting on SetStill is Done!
2022-04-21 20:18:11.826 - SyncPosition()! Clearing planner.
2022-04-21 20:18:11.826 - Probing: Exiting hold because of probe strike. gcodeexec.cpp:792
2022-04-21 20:18:11.826 -
2022-04-21 20:18:11.826 -
2022-04-21 20:18:11.826 - !!!!!!! ESS: The Inhibit Motion input signal is active! Mach will not generate motion!!!!!!!

2022-04-21 20:18:11.826 - .^^^^^ESS: Switching from PROBING_CLEANUP to NORMAL state.^^^^^
2022-04-21 20:18:11.826 -
2022-04-21 20:18:11.827 -
2022-04-21 20:18:11.884 - API: mcMotionSetStill(inst = 0, motor = 0) (Called by ESS)
2022-04-21 20:18:11.884 - SetStill(): Motor 0 last position reported = 55389.1500 controller.cpp:1400
2022-04-21 20:18:11.884 - All motors marked as still.
2022-04-21 20:18:11.884 - >>>--- ESS: Reporting Stopped: Motor 0 55389.150000   #B
2022-04-21 20:18:11.884 - API: mcMotionSetStill(inst = 0, motor = 1) (Called by ESS)
2022-04-21 20:18:11.884 - SetStill(): Motor 1 last position reported = 440396.0000 controller.cpp:1400
2022-04-21 20:18:11.884 - All motors marked as still.
2022-04-21 20:18:11.884 - >>>--- ESS: Reporting Stopped: Motor 1 440396.000000   #B
2022-04-21 20:18:11.884 - API: mcMotionSetStill(inst = 0, motor = 2) (Called by ESS)
2022-04-21 20:18:11.885 - SetStill(): Motor 2 last position reported = -35301.0000 controller.cpp:1400
2022-04-21 20:18:11.885 - SoftSync()! Clearing planner. controlset.cpp:210
2022-04-21 20:18:11.885 - All motors marked as still.
2022-04-21 20:18:11.885 - >>>--- ESS: Reporting Stopped: Motor 2 -35301.000000   #B
2022-04-21 20:18:11.885 - API: mcMotionSetStill(inst = 0, motor = 5) (Called by ESS)
2022-04-21 20:18:11.885 - SetStill(): Motor 5 last position reported = 440396.0000 controller.cpp:1400
2022-04-21 20:18:11.885 - All motors marked as still.
2022-04-21 20:18:11.885 - >>>--- ESS: Reporting Stopped: Motor 5 440396.000000   #B
2022-04-21 20:18:11.886 - API: mcCntlGcodeExecute(inst = 0, commands = 'G90 G53 G1 Z0.0000 F600.0') (unknown caller)
2022-04-21 20:18:12.000 - SoftSync()! Clearing planner. gcodeexec.cpp:168

9
Mach4 General Discussion / Strange mach4 behavior
« on: April 21, 2022, 11:49:26 AM »
Hi Guys,
  its been a while since i had a need to post but i have an issue with mach4.

First a bit of background - its a home built machine and i have been running mach for a while now.  i have noticed sometimes there is some odd behaviour as below
1 the first time i run gcode the tool is set, height is set, but the first z move is often wrong by 10mm or so.  after re-setting the wpc 0 its fine.
2 Every few months the config messes up somehow - not sure what causes it but i have to restore and get back to square 1
3 Sometimes when homing for the first time there is a small delay - 1 or 2 seconds - between moving the axis.  This is not all the time but sometimes

Now i have a new problem.....

After some tidying yesterday i changed the usb port for my rs485 adapter (spindle running through modbus), today i go to use my machine and firstly the tool change option is set to 'm6 is the next tool' - after changing back 3 times it finally stayed and i went to do an m6 (which includes tool height measure).  The routine started as normal and moved to tool change pos, waited for the tool, and then moved to the probe, air blast and start the probe movement.  When the tool reched the probe, the machine stopped and seemed to get 'stuck'- - no error, no e-stop, but no further movement and could only be moved after a reset.  The normal behaviour would be to move z back u and return to previous state.

I have no clue what could be causing this.... very weird.  I dont know why it wont move past the tool probing routine - it has done 1000's using the same m6 script no issue!

10
Mach4 General Discussion / Re: Modbus control huanyang GT vfd
« on: November 14, 2021, 01:38:24 PM »
Hi,
the whole point about putting the code in a macro IS NOT TO EFFECT THE SPEED.....it is a means for you put put the code
in a 'sandbox' so you can play with it until you understand it and get it to work, just throwing random corrections at the code will not do it.

Double check the Register Diagnostics, it shows that function2 Is included in the path.......what evidence do you use to support the contention that its
not part of the path?

Craig
If you check the tree, the path is modbus0/wrtvfd..... etc.  I got the code finally working with the help of James, massive thankyou! i will post the working version here
Code: [Select]
-----------------------------------------------------------------------------
--   Name: PMC Module
--Created: 03/27/2015
-----------------------------------------------------------------------------
-- This is auto-generated code from PmcEditor. Do not edit this file! Go
-- back to the ladder diagram source for changes in the logic

-- U_********* symbols correspond to user-defined names. There is such a symbol
-- for every internal relay, variable, timer, and so on in the ladder
-- program. I_********* symbols are internally generated.

local VFD_Spindle_controller = {}

local hReg, hSig, rc
local mInst = 0

-- Generated function for MachAPI.
local function Read_Register(path)
    hReg, rc = mc.mcRegGetHandle(mInst, path)
    if (rc == mc.MERROR_NOERROR) then
        local value, rc = mc.mcRegGetValue(hReg)
        if (rc == mc.MERROR_NOERROR) then
            return value
        end
    end
    return 0
end

-- Generated function for MachAPI.
local function Write_Register(path, value)
    hReg, rc = mc.mcRegGetHandle(mInst, path)
    if (rc == mc.MERROR_NOERROR) then
        rc = mc.mcRegSetValue(hReg, value)
        if (rc == mc.MERROR_NOERROR) then
            return
        end
    end
    return
end

-- Generated function for MachAPI.
local function Read_Signal(path)
    hSig = 0
    rc = mc.MERROR_NOERROR
    hSig, rc = mc.mcSignalGetHandle(mInst, path)
    if (rc == mc.MERROR_NOERROR) then
        local state = 0;
        state, rc = mc.mcSignalGetState(hSig)
        if (rc == mc.MERROR_NOERROR) then
            return state
        end
    end
    return 0
end

-- Generated function for MachAPI.
local function Write_Signal(path, v)
    hSig = 0
    rc = mc.MERROR_NOERROR
    hSig, rc = mc.mcSignalGetHandle(mInst, path)
    if (rc == mc.MERROR_NOERROR) then
        mc.mcSignalSetState(hSig, v)
    end
end

-- Generated function for signal read.
local function Read_U_b_FSpindle_CW()
    return Read_Signal(1142)
end

-- Generated function for signal read.
local function Read_U_b_FSpindle_CCW()
    return Read_Signal(1143)
end

-- Generated function for signal read.
local function Read_U_b_FSpindle_ON()
    return Read_Signal(1141)
end

-- Call this function to retrieve the PMC cycle time interval
-- that you specified in the PmcEditor.
function VFD_Spindle_controller.GetCycleInterval()
    return 10
end


-- Call this function once per PLC cycle. You are responsible for calling
-- it at the interval that you specified in the MCU configuration when you
-- generated this code. */
function VFD_Spindle_controller.PlcCycle()
    --mInst = mc.mcGetInstance()

    if     (Read_U_b_FSpindle_CCW() == 0 and Read_U_b_FSpindle_CW() == 1 and Read_U_b_FSpindle_ON() == 1) then
       Write_Register("modbus0/wrtvfdcmd0", 1)
    elseif (Read_U_b_FSpindle_CCW() == 1 and Read_U_b_FSpindle_CW() == 0 and Read_U_b_FSpindle_ON() == 1) then
       Write_Register("modbus0/wrtvfdcmd0", 2)
    else --if Read_U_b_FSpindle_ON() == 0) then
       Write_Register("modbus0/wrtvfdcmd0", 5)
    end

    local registerHandle=mc.mcRegGetHandle(mInst,"modbus0/wrtvfdspeed0")
local commandedSpeed=mc.mcSpindleGetCommandRPM(mInst)
-- mc.mcCntlSetLastError(mInst, tostring(commandedSpeed))
local registerValue=(commandedSpeed/12000)*10000
mc.mcRegSetValue(registerHandle,registerValue)
end

return VFD_Spindle_controller

The big problem was for some reason the register was not getting written. Maybe an internal mach problem

Pages: 1 2 3 4 5 6 7 8 »