Hello Guest it is April 18, 2024, 09:33:46 PM
Profile Guest

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.


Topics - ysymidi

Pages: 1 2 »
1
Mach4 General Discussion / I can't set Gage Block Height value.
« on: March 08, 2023, 01:12:51 AM »
Hello dear members,

I got recently attacked by a ransomeware and cleared all my PCs including Mach 4 setups...

I installed Mach 4 4809 + ESS283

And I copied screen from my backup.

But I can't set Gage Block Height. When I enter a value(like 15.0) and click on "Set Z" button, the value is turned to 10.4529.
I don't know where the value 10.4529 came from. ;(

Here is the linked script of "droGageBlock"


local inst = mc.mcGetInstance()

local val = scr.GetProperty("droGageBlock", "Value")
mc.mcProfileWriteString(inst, "PersistentDROs", "droGageBlock", string.format (val)) --Create a register and write to it

--local val = scr.GetProperty("droGageBlock", "Value")
--mc.mcProfileWriteString(inst, "OffsetsSettings", "GageBlock", tostring(val))
--mc.mcCntlSetLastError(inst, "Offsets: Fixture Z Gage block updated")



What should I do to solve this?

2
Mach4 General Discussion / Fast Probing, Back-off and Slow Probing in Manual Tool Change M6
« on: March 02, 2021, 03:08:22 AM »
Hello,

i thank you guys who give tons of help. ;)

With help from Daz, I've been able to run M6 so far.

But I'd like to shorten the time needed for tool change.

What code should I insert to probing twice?
(First with relatively fast feed(I think F300 would be enough), the second with slow/precise probing feed(F50 will do))

I think I need to back off about 2mm when the first probing is done. then the second probing starts.


Here is my M6 code I have used so far.

What should I add to the red below?


============================================================


function m6()
    local inst = mc.mcGetInstance();
    local xstart = mc.mcAxisGetPos(inst,0)
    local ystart = mc.mcAxisGetPos(inst,1)
    local guesslen = -100
    local selectedtool = mc.mcToolGetSelected(inst)
    local currenttool = mc.mcToolGetCurrent(inst)
    local toollen = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT, currenttool)
    if toollen == 0 then toollen = 50 end
    local probestart = guesslen + toollen

   if selectedtool == currenttool then   
   return
   mc.mcCntlSetLastError(inst, "Selected Tool = Current Tool")

   else
   
    mc.mcCntlGcodeExecuteWait(inst,"M05")
    mc.mcCntlGcodeExecuteWait(inst,"M09")

    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 Z0.000")
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 X1.700 Y1.100")

    mc.mcCntlGcodeExecuteWait(inst,"G04 P4000")
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 Z"..probestart)

    mc.mcCntlGcodeExecuteWait(inst,"G91 G31 Z-60 F100")
    mc.mcCntlGcodeExecuteWait(inst,"M07")
      local toolz = mc.mcAxisGetPos(inst,2)
      mc.mcCntlGcodeExecuteWait(inst,"M09")
   

    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Z0.000")
   local changetoo = mc.mcToolGetDesc(inst, selectedtool)
   wx.wxMessageBox("Please change to tool number "..selectedtool.." "..changetoo.." and press OK to continue")
    currenttool = selectedtool
    toollen = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT, currenttool)
    if toollen == 0 then toollen = 50 end
    probestart = guesslen + toollen
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 X1.700 Y1.100")
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Z"..probestart)
    mc.mcCntlGcodeExecuteWait(inst, "G91 G31 Z-60 F100")
    mc.mcAxisSetPos(inst, 2 , toolz)
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Z0.000")
--    mc.mcCntlGcodeExecuteWait(inst,"M03")
--    mc.mcCntlGcodeExecuteWait(inst, "G90 G00 X"..xstart)
--      mc.mcCntlGcodeExecuteWait(inst, "G90 G00 Y"..ystart)
    mc.mcCntlGcodeExecuteWait(inst, "G90 G00 X"..xstart.." Y"..ystart)
--    mc.mcCntlGcodeExecuteWait(inst,"G04 P3000")

    mc.mcToolSetCurrent(inst, selectedtool)
   mc.mcCntlSetLastError(inst, "Toolchange Finished")
    --wx.wxMessageBox('Toolchange Finished')
   end
   
end


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

end

3
Mach4 General Discussion / How can I make "Soft Limits on when Mach4 starts up"?
« on: February 27, 2021, 01:26:46 AM »
Hello,

I've been struggling with soft limits.

Before I updated my Mach4, soft limits were on when Mach4 started up.
(Of course, I can click on the soft limit button and turn it off if I need it.)

I just want my recently updated Mach4 to work the same way.

What would be the simplest way to make it? ;)


P.S. Of course, I do "Axis referencing" before machining parts.

4
Mach4 General Discussion / "Go To WorkZero" doesn't lift up Z axis.
« on: November 19, 2019, 12:15:52 AM »
Hi

I'm changing a MACH4 computer(upgrading thw S/W too from MACH4 older version to 4388), and confront some problems. ;(

I clicked on "Go To WorkZero" on the default screen.
I thought it would lift up the Z axis first, but the machine just moved its X and Y axis only.

So I opened the screen editor and open the script.

I found it did have Z axis movement in the script.
(I deleted "\nG00 Z0" at the end.)


GoToWorkZero()
--local inst = mc.mcGetInstance()
--mc.mcCntlMdiExecute(inst, "G00 G53 Z0\nG00 X0 Y0 A0")


Why the machine doesn't move Z axis?

5
Mach4 General Discussion / Don't stop when hitting a Limit Sensor
« on: November 13, 2019, 04:37:14 AM »
Hi members~

I made a fresh install of Windows 10 Pro in my Dell 9020M micro computer, and installed MACH4 4338 and ESS 250 plugin.

I finished configuration, and checked the home and limit senors work.
(I did it with "Diagnostics - ESS v250")

When I slowly(very slowly...  STEP by STEP) move an axis to a limit switch, MACH4 stops(E-Stop)., but when I jog the axis in normal speed(F1000?), MACH4 does not STOP on the limit switch and pass to the end of the axis keep making squeaking noise...

Why did happen?

And when I try to reference home, the axis just move to pass the home sensor.
(But in the Diagnostics - ESS v250, home sensor is correctly working.)

Would you please give me some help?

6
Mach4 General Discussion / When will the next official updated version of M4 be released?
« on: April 23, 2018, 09:19:14 PM »
Hello,

I'm currently working with M4 3663, but this doesn't support Korean characters.
I know 3713 supports it.

I'd rather install official release than beta release.
So I'm waiting for it.

Can anyone let me know when it will be released?

If that's too late, I think I need to install current up-to-date beta release.


Cheers,
Sawyer

7
Mach4 General Discussion / What changes PCID?
« on: February 13, 2018, 04:45:12 AM »
I run Mach4 on Dell i5 USFF PC.

When I upgraded its memory, PCID changed and I had to issue a new license file.

I thought this is unreasonable at first... but OK... I changed the hardware anyway...

Then... what if I make a S/W level change? like re-installing windows... etc?

Does this also change the PCID and I have to issue another licence?

8
Mach4 General Discussion / Mach4 does not support Unicode?
« on: February 12, 2018, 12:01:46 PM »
Hi,

I really appreciate all the help you members given to me.
I'm growing little by little. ;)

I had used DeskCNC for a while...
As you might know, it was discontinued a few years ago... very old fashioned software....
But it supported unicode and I didn't have to change folder names and .nc file names into pure English alphabet.
I just manage the file names in Korean language.

But Most recent Mach4 doesn't seem to support unicode.
If any Korean alphabet is included in the path to .nc file(no matter it is folder name or nc file name...), Mach4 cannot load it.

Mach4 doesn't support it? or I should change any configuration in Mach4?

9
Mach4 General Discussion / VistaCNC P2-S malfunctioning with Mach4
« on: February 08, 2018, 03:10:06 AM »
Hello Dear members~ ;)

I recently bought a P2-S USB MPG pendant from VistaCNC to use with Mach4.

I updated its firmware to work with Mach4.
(I downloaded the file from the official website of VistaCNC. Maybe the latest version.)

I copied 2 plugin files into Mach Plugin folder.

I thought it worked at first.

But I got problems....


I use Mach4 Hobby(Installed last Month), ESS (Plugin 216)+ MB2(Ver 2.0) in Windows 10 64bit.


1> F1(Ref Home)/F2(Zero All) runs with "Single" click. => These should be done with double click, right?

2> F3(Goto Zero) don't work. When I "Single" click at F3, Mach4 says "Axis 4 commanded while disabled"

3> In step mode, Can't I save the configuration? I don't use 1mm step... I usually use 0.01mm step. But when I restart Mach4, it turns to 1.00mm step that I don't use...

4> Can I edit F1/F2/F3/F4 functons? I want to allot a function to F4 too.

5> This is the crucial problem I have now... P2-S often becomes a brick... to use it I have to restart Mach4... I can't restart during machining work....


Anyone experienced the similar problems?

10
Mach4 General Discussion / M6 Doesn't work...
« on: February 07, 2018, 11:47:11 AM »
Hello Members,

I so much appreciate your help. ;)
I have almost no chance to get a help like this in my country...

I'm trying to run a manual tool change macro in Mach4.

I use ESS + MB2(ver2.0) + 4 step motors(Y axis has 2 motors, I configured B as Y-Slave in ESS plugin, so MACH4 doesn't know there is a slaved motor.)


When I put "T3 M6" in MDI and click on Cycle Start, nothing happens....
And I captured log as below.


Quote
2018-02-08 01:19:05.002 - API: mcCntlMdiExecute(inst = 0, commands = 't2 m6') (Mach4GUI)
2018-02-08 01:19:05.104 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1875
2018-02-08 01:19:05.104 - S_IDLE_on_exit
2018-02-08 01:19:05.104 - ACTION_start_mdi
2018-02-08 01:19:05.104 - S_MDI_RUNNING_on_entry
2018-02-08 01:19:05.104 - S_MDI_RUNNING2_on_entry
2018-02-08 01:19:05.105 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2018-02-08 01:19:05.115 - Signal id 1121, (Tool Change), changed from LOW to HIGH.
2018-02-08 01:19:05.116 - >>>>> ESS received a Tool Change Required notification.

2018-02-08 01:19:05.120 - >>>>> ESS received a Tool Change Done notification.

2018-02-08 01:19:05.121 - Signal id 1121, (Tool Change), changed from HIGH to LOW.
2018-02-08 01:19:05.121 - >>>>> ESS received a Tool Change Done notification.

2018-02-08 01:19:05.241 - Attempt transition from "MDI Running" on event "Stop" GcodeExec.cpp:1179
2018-02-08 01:19:05.241 - S_MDI_RUNNING2_on_exit
2018-02-08 01:19:05.241 - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2018-02-08 01:19:05.241 - S_MDI_RUNNING_on_exit
2018-02-08 01:19:05.241 - ACTION_stop
2018-02-08 01:19:05.265 - S_IDLE_on_entry


Following is the code that I want to use with my machine. But nothing happens...
(I got it from DAZ part3 code, and only modified XY position and Spindle On/Off)
Code: [Select]
function M6()
    local inst = mc.mcGetInstance();
    local selectedtool = mc.mcToolGetSelected(inst)
    local currenttool = mc.mcToolGetCurrent(inst)
    local xstart = mc.mcAxisGetPos(inst,0)
    local ystart = mc.mcAxisGetPos(inst,1)

    if selectedtool == currenttool then
    return
    mc.mcCntlSetLastError(inst, "ToolChange Activated But Not Required")
    else
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G0 Z0.0 \n X25.0 Y352.5")
--    wx.wxMessageBox("Please turn off spindle and click ok to continue") --can be removed if required
    RunProbe(currenttool)
    local toolz = mc.mcAxisGetPos(inst,2)
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G0 Z0.0")
    local changetoo = mc.mcToolGetDesc(inst,selectedtool)
    wx.wxMessageBox("Please change to tool number "..selectedtool.." "..changetoo.." and press ok to continue")
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G0 X25.0 Y352.5")
    RunProbe(selectedtool)
    mc.mcAxisSetPos(inst, 2 , toolz)
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G0 Z0.0")
--    wx.wxMessageBox("Please turn on spindle and click ok to continue") --can be removed if required
    mc.mcCntlGcodeExecuteWait(inst,"G90 G0 X"..xstart.." Y"..ystart)
    mc.mcToolSetCurrent(inst, selectedtool)
    mc.mcCntlSetLastError(inst, "ToolChange Finished")
    end
end

function RunProbe(tool)
    local inst = mc.mcGetInstance()
    toollen = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT, tool)
    if toollen == 0 then toollen = 50 end -- User Preference
    mc.mcCntlSetLastError(inst, "Changing to Fallback Length")
    local probestart = -60 + toollen
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G0 Z"..probestart.."\nG91 G31 Z-60 F100")
end

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




I don't think Mach4 correctly recognizes selectedtool and currenttool.
So... if I just get rid of the lines concerning selectedtool and currenttool from the code. M6 works...
But it always say... "Please change to tool number 2 and press OK to continue." always... number 2...... I don't know why...
This is always the same whatever tool number I put, such as T3, T4, T5.....

Code: [Select]
function m6()
    local inst = mc.mcGetInstance();
    local xstart = mc.mcAxisGetPos(inst,0)
    local ystart = mc.mcAxisGetPos(inst,1)
    local guesslen = -100
    local selectedtool = mc.mcToolGetSelected(inst)
    local currenttool = mc.mcToolGetCurrent(inst)
    local toollen = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT, currenttool)
    if toollen == 0 then toollen = 50 end
    local probestart = guesslen + toollen

--if selectedtool == currenttool then
--return
mc.mcCntlSetLastError(inst, "Toolchange Activated")
--else
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 Z0.000")
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 X25.000")
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 Y352.500")
    mc.mcCntlGcodeExecuteWait(inst,"G90 G53 G00 Z"..probestart)
    mc.mcCntlGcodeExecuteWait(inst,"G91 G31 Z-60 F100")
    local toolz = mc.mcAxisGetPos(inst,2)
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Z0.000")
local changetoo = mc.mcToolGetDesc(inst, selectedtool)
wx.wxMessageBox("Please change to tool number "..selectedtool.." "..changetoo.." and press OK to continue")
    currenttool = selectedtool
    toollen = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT, currenttool)
    if toollen == 0 then toollen = 50 end
    probestart = guesslen + toollen
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 X25.000")
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Y352.500")
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Z"..probestart)
    mc.mcCntlGcodeExecuteWait(inst, "G91 G31 Z-60 F100")
    mc.mcAxisSetPos(inst, 2 , toolz)
    mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G00 Z0.000")
    mc.mcCntlGcodeExecuteWait(inst, "G90 G00 Y"..ystart)
    mc.mcCntlGcodeExecuteWait(inst, "G90 G00 X"..xstart)
    mc.mcToolSetCurrent(inst, selectedtool)
mc.mcCntlSetLastError(inst, "Toolchange Finished")
    --wx.wxMessageBox('Toolchange Finished')
end
   
--end


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

end


What should I do....?
I'm desperately hopeless.... ;(

Pages: 1 2 »