Hello Guest it is April 18, 2024, 12:33:50 PM

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 - Flying Scot

Pages: 1 2 3 4 5 6 »
1
Mach4 General Discussion / Re: G code stops after M03 command
« on: August 25, 2023, 07:14:28 AM »
Problem found ignore all of above I cant figure out how to delete it.
a delay of 200 seconds in acceleration and deceleration was the problem
art

2
Mach4 General Discussion / Re: G code stops after M03 command
« on: August 25, 2023, 06:54:04 AM »
2023-08-25 11:31:26.207 [I    ] - API: mcCntlMdiExecute(inst = 0, commands = 's2000 m3
g90 g00  x25 y-10
') (unknown caller)
2023-08-25 11:31:26.309 [I    ] - Attempt transition from "Idle" on event "MDI Start" controller.cpp:2473
2023-08-25 11:31:26.309 [I    ] - S_IDLE_on_exit
2023-08-25 11:31:26.309 [I    ] - Signal id 1172, (Machine Idle), changed from HIGH to LOW.
2023-08-25 11:31:26.309 [I    ] - ACTION_start_mdi
2023-08-25 11:31:26.309 [I    ] - SoftSync()! Clearing planner.
2023-08-25 11:31:26.331 [I    ] - S_MDI_RUNNING_on_entry
2023-08-25 11:31:26.331 [I    ] - SoftSync()! Clearing planner. stateinterface.cpp:1351
2023-08-25 11:31:26.331 [I    ] - S_MDI_RUNNING2_on_entry
2023-08-25 11:31:26.331 [I    ] - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2023-08-25 11:31:26.331 [I    ] - 
2023-08-25 11:31:26.331 [I    ] - -----===== Mach4 build 4.2.0.4809, ESS build 285 =====-----
2023-08-25 11:31:26.331 [I    ] - 
2023-08-25 11:31:26.334 [MR   ] - 
2023-08-25 11:31:26.334 [MR   ] -    >>> ESS: SS Motor Mode - Spindle stopped, 'Spindle Motor Dir' not changed.
2023-08-25 11:31:26.334 [MR   ] - >>> ESS: Told to shut off the spindle by Mach4.
2023-08-25 11:31:26.335 [MR   ] - Signal id 1142, (Spindle Fwd), changed from LOW to HIGH.
2023-08-25 11:31:26.335 [MR   ] - 
2023-08-25 11:31:26.335 [MR   ] -    >>> ESS: SS Motor Mode - 'Spindle Motor Dir' set to Forward.
2023-08-25 11:31:26.335 [MR   ] - >>> ESS: Setting SS Motor 5 spindle to 2000.0 RPM on Range 0
2023-08-25 11:31:26.335 [MR   ] - >>> ESS: Spindle PID is not enabled.
2023-08-25 11:31:26.335 [MR   ] - Signal id 1141, (Spindle On), changed from LOW to HIGH.
2023-08-25 11:31:26.336 [MR   ] - Waiting 200.000000 seconds for spindle at speed... spindle.cpp:306
2023-08-25 11:32:39.655 [MR   ] - API: mcCntlCycleStop(inst = 0) (unknown caller)
2023-08-25 11:32:39.656 [MR   ] - ~~~~~~ESS: Laser and M62 outputs shut off by MSG_CYCLE_STOP
2023-08-25 11:32:39.656 [MR   ] - >>>>>>>> LASER - ESS: Laser PWM DISABLED due to a STOP event.
2023-08-25 11:32:40.554 [MR   ] - -----ESS: Reset Homing and Probing settings.
2023-08-25 11:32:40.554 [MR   ] - 
2023-08-25 11:32:40.554 [MR   ] -    $$$ ESS: Mach4 had a Cycle Stop - Force Output Stop Sates Now
2023-08-25 11:32:40.554 [MR   ] - Attempt transition from "MDI Running" on event "Stop" command.cpp:3456
2023-08-25 11:32:40.554 [MR   ] - ~~~~~~ESS: Laser and M62 outputs shut off by StopStates
2023-08-25 11:32:40.554 [MR   ] - S_MDI_RUNNING2_on_exit
2023-08-25 11:32:40.554 [MR   ] - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2023-08-25 11:32:40.554 [MR   ] - -----ESS: Reset Homing and Probing settings.
2023-08-25 11:32:40.554 [MR   ] -    $$$ ESS: Finished processing the Stop Event
2023-08-25 11:32:40.554 [MR   ] - 
2023-08-25 11:32:40.555 [MR   ] - S_MDI_RUNNING_on_exit
2023-08-25 11:32:40.555 [MR   ] - ACTION_stop
2023-08-25 11:32:40.555 [MR   ] - Done. spindle.cpp:311
2023-08-25 11:32:40.559 [MR   ] - >>>>>>>> ESS: DISABLING Laser PWM.
2023-08-25 11:32:40.578 [MR   ] - S_IDLE_on_entry
2023-08-25 11:32:40.580 [MR   ] - Signal id 1172, (Machine Idle), changed from LOW to HIGH.
2023-08-25 11:32:40.581 [I    ] - API: mcSpindleSetDirection(inst = 0, dir = 0) (unknown caller)
2023-08-25 11:32:40.581 [I    ] - Signal id 1142, (Spindle Fwd), changed from HIGH to LOW.
2023-08-25 11:32:40.581 [I    ] - 
2023-08-25 11:32:40.581 [I    ] -    >>> ESS: SS Motor Mode - Spindle stopped, 'Spindle Motor Dir' not changed.
2023-08-25 11:32:40.581 [I    ] - >>> ESS: Told to shut off the spindle by Mach4.
2023-08-25 11:32:40.582 [I    ] - Signal id 1141, (Spindle On), changed from HIGH to LOW.

This is the diagnostic log that shows waiting for 200 seconds (not sure where this comes from and also mentions laser

3
Mach4 General Discussion / G code stops after M03 command
« on: August 25, 2023, 06:29:10 AM »
I have been updating a Boxford vmc260 which has been running mach3 with USS and PMDX125 in windows 7 for 12 years.
The machine is now configured keeping the PMDX125 but changing to ESS and Mach4 in windows11. Having worked through getting tool change and probing working it was time to try running a simple program to drill a couple of holes centre drilling first to test the tool change.
After setting work coordinates and running the Gcode the machine carried out the tool change, started spindle (which is an ac servo set up as motor 5 step and direction) and immediately froze.
If you turn spindle off from the screen and back on again until the gcode reaches M05 and it pauses again.

I have stripped the gcode back to 2 lines:
S2000 m03
G90 G00 x25 y25
Run from MDI spindle starts but moves are not executed.
If I remove the S2000 m03 the move does work so it has to be due to the spindle command.
I have disabled ‘wait on spindle to stabilise in Control Spindle tab.
Mach4 V4.2.0.4809 licensed

Has anyone come across this or have any idea where I am going wrong?

Regards

Art

4
Mach4 General Discussion / Machipc could not be found
« on: August 19, 2023, 09:16:48 AM »
I have just replaced the pc on my mill (previously running mach3 for many years on windows 7 without problem until pc failed) with a new windows 11 computer with  a fresh installation of mach 4 v4.20 4809 using ESS.

The mill is all working but when
I try to edit the m6macro I get the error loading machipc  from file mach4hobby\modules/machipc.dll.  (the file is there)

I also tried V4.20 5036 but it gives the same error.

I then  installed the same versions on a windows 10 machine and the editor works fine which makes me think windows 11 is the problem but others are using it.

Does anyone have any ideas what could be the problem?

Art


5
Mach4 General Discussion / Re: Tool change Problem.
« on: May 15, 2020, 04:43:49 PM »
Hi Bill

Not really sure as I reloaded mach4 and started from scratch using Daz videos.

All working well today again

Arthur

6
Mach4 General Discussion / Re: Tool change Problem.
« on: May 13, 2020, 06:42:12 PM »
At last its all working.

I spent most of today going through Daz's tool change videos which helped me understand what was supposed to be happening.   
I think the biggest problem was me not understanding the process.

Using his M6 macro adapted for my machine tool changes  are all working accurately every time

It's at least 10 years since I set up my other machines on Mach3  and they have never given any trouble. (It seemed easier then)

Thanks again

Art

7
Mach4 General Discussion / Re: Tool change Problem.
« on: May 13, 2020, 10:50:26 AM »
Hi Bill

The M6  macro  moves spindle to tool change position and  measures   the tool offset and updates the tool table.
But it is updating table with the wrong offset.

Arthur

8
Mach4 General Discussion / Re: Tool change Problem.
« on: May 13, 2020, 08:55:23 AM »
Hi Stuart,

Is probably something stupid I am doing but it is very confusing and I am not making a very good job of explaining it.
On my mill in Mach3 I have permanently set tools and tools that require the length checked each time and it all works fine.

This is a new router I have built and at present I only have a few collets and so I have to change tool in collet now and again. I prefer to send spindle to check tool length at every tool change.
I start by selecting T1 which has zero offset set and setting G54 in the offsets section of Mach4 setting Z on an 8mm tool plate.
I then change to T2 say a 6mm cutter then set cutter offset in offsets section and the offset is set in tool table of -14.995.

I can then run a job with no M6 tool change with a single tool no problem.

Now to test the M6 tool change  I leave the same 6mm cutter in the collet and run T3 M6 G43 H3 ( this is just a test to try and find out what is wrong) the tool table shows the offset for T3 as -7.015. (as it is the same tool as T2 the offset should be -14,995)

If I then run T4 M6 G43 H4 again with the same 6mm tool fitted the offset now changes to -0.0080 (it should not change as is same tool that was fitted)
when I run it again as T5 M6 G43 H4 the offset returns to -7.015.  If I continue incrementing T and H the offset in the tool table keeps alternating  between -7.015 and 0.0080.
I know this is not normally what you would do in normal operation of the machine.
I am telling the machine a different tool is fitted, but is the same tool that has never been removed from the spindle so the tool table  so it should show the same offset each time.

Homing is very good on all axis even the 4th rotary one.

I don't build locos but I do have 1/3rd Burrell traction engine I have been building for many years.  Its mainly model Aircraft I build.

Workshops are a great place for self isolating.

regards

Arthur



9
Mach4 General Discussion / Re: Tool change Problem.
« on: May 13, 2020, 03:01:51 AM »
Hi Steve,

Thanks for spending the time on this I have been going round in circle for days on this one, even thought about going back to an old PC on windows 7 and Mach3.
I am new to Mach 4 but have been running mach 3 for ten years making model parts on my Boxford Mill and Boxford Lathe with tool turret. The plan was to update them to Mach 4 and windows 10 on new pcs with windows 10 and ESS.

I have tried G43 on next line but it makes no difference.

I am using an ER16 collet chuck on my router spindle.
I was leaving the same tool in the chuck as a test to try and Identify the problem. This tool was initially measured manually in the offset window giving an offset of -14.995 which is correct. (my tool plate is 8mm)

I did not change the tool as I was trying to identify the problem using the entries in the tool table.
By only changing the tool number and the offset number in the MDI line "Txx M6 G43 Hxx"  the tool table should show every entry as being the same length for each tool but as shown it does not.
That's why I am confused when using "T on M6 line is tool to use" The offset keeps changing each time and it is always wrong.
I have managed to attach the M6 macro I am using.

Best regards

Arthur

 


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

mc.mcCntlGcodeExecuteWait(inst, "G53 G0 Z0\nG53 G0 X700 Y65")--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 = 1--mc.mcToolGetCurrent(inst)
   
 if selectedtool == currenttool then
        mc.mcCntlSetLastError(inst, "Current tool == Selected tool so there is nothing to do")
 else
        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 connect probe","Click OK to continue" , 16)
        mc.mcCntlSetLastError(inst, "Probing in Progress!")
        mc.mcCntlGcodeExecuteWait(inst, " G91 G31 Z-150. F125.")--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

end

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

10
Mach4 General Discussion / Re: Tool change Problem.
« on: May 12, 2020, 07:59:15 PM »
Hi again Steve

I tried to attach the m5 macro to the post but for some reason it is not showing.

Art

Pages: 1 2 3 4 5 6 »