Machsupport Forum
Mach Discussion => Mach Screens => Topic started by: voyager1972 on April 14, 2019, 03:15:00 PM
-
i have a stepmores 10*5 cnc running mach3,,,,,i have tried screenset 2010,,,,bigtex probing screenset,,,,i am having issues with both,,,,,,,sometimes it works ,,,other times it drives the cutter into the bed,,,,,not consistent,,,alot of the times it retracts the z axis triggering e stop...the machine is running a xhc motion card. has anyone had any success on a chinese machine with double probing macros?
-
There are alternative macros on my website for use with the 2010 screenset and Chinese controllers. Have you tried those?
-
ill download and try those ,,ill let you know how i get on,,,,,,,,thanks
-
i have tried the chinese macros,,,still the issue remains,,,,,i will remove the fixed tool probe completely,,and try the toolchange using the moveable probe which came on the machine just to rule out interferance..
-
Interference won't cause it to drive into the bed.
-
i have installed the chinese macros,,,,seems to be running better although there was a few glitches,,,,a few times after the fixed plate touch off ,the spindle did not retract ,just stayed in the fixed plate location....i will load some gcode tomorrow and try a test cut and see how it goes.
-
I suspect that it's your XHC card. I know that some people could not get that card to work correctly.
-
I have been planning on upgrading to uccnc ...so i will probably go down that road,,,,,thanks again ger21.....
-
I suspect that it's your XHC card. I know that some people could not get that card to work correctly.
From XHC plugin change log
V2.38.4 2015.7.8
1. add probe variable 2000-2003,but it maybe still could not compatible with mach3 screen 2010.
if you want to probe with screen 2010, please replace the GetVar(2002) with getoemdro(802),
GetVar(2001) with getoemdro(801),GetVar(2000) with getoemdro(800).
-
thanks reuelt for your reply,,,i have downloaded the latest update for my card and will transfer it to the plugins folder of mach3,,,,regarding the replacement of "GetVar(2002) with getoemdro(802),
GetVar(2001) with getoemdro(801),GetVar(2000) with getoemdro(800)" .,,,,,,do i need to do this in certain macro files or all of them ??
-
The macros on my website already have those changes.
-
i have just found the update for my exact motion card which is the MKX-IV the last update has this info in the release note for that update, it goes as follows
"
1.Set the probe user dro 2000,2001,2002 to replace the variable 2000,2001,2002.
so user could getuserdro(2000) to replace the GetVar(2000) when probing.
2. auto update acceleration to card when jogging
3. support slave axis seperate home
V2.39.8 2016.9.12
1.optimize the break resume function. "
do i have to do anything other than copy the NcUsbPod.dll file into the plugins folder ??
-
hi ger21,,,,,i will copy the updated plugin to the plugins folder and see if the update helps,,, i have copied the text from the changelog and placed in my last post i made
-
1.Set the probe user dro 2000,2001,2002 to replace the variable 2000,2001,2002.
so user could getuserdro(2000) to replace the GetVar(2000) when probing.
I'm not sure what they mean here. You may need to add DRO's to the screen, numbered 2000,2001, and 2002. Then edit the macros as described.
-
i will have a tinker later and let you know,,,,hopefully the motion controller update cures the issues,,,,,your 2010 screenset is a superb peice of work,,,and would help me alot with Machining times
-
there is a big difference between GetVar(2000...2002) and GetOEMDro(2000...2002)
a good Motion controler uses the Variables 2000.2002 to strore the axis values exactly when
the probe was hit (allmost realtime), nothing will happen with OEMDro 2000...2002
V2.38.4 2015.7.8
1. add probe variable 2000-2003,but it maybe still could not compatible with mach3 screen 2010.
if you want to probe with screen 2010, please replace the GetVar(2002) with getoemdro(802),
GetVar(2001) with getoemdro(801),GetVar(2000) with getoemdro(800).
if you use OEMDro 800...802 you will allways get the value from the probe hit + overtravel depending
on the time the axis Needs to stop.
-
My thought was that they may be writing to OEMDRO2000, 2001,2002, ...
But maybe their notes are completely wrong.
-
from Mach3Mill_1.84 doc
chapter 10.7.12 Straight Probe – G31
description:
After successful probing, parameters 2000 to 2005 will be set to the coordinates of the
location of the controlled point at the time the probe tripped and a triplet giving X, Y and Z
at the trip will be written to the triplet file if it has been opened by the M40
macro/OpenDigFile() function (q.v.)
example code:
N010 (probe to find center and diameter of circular hole)
N020 (This program will not run as given here. You have to)
N030 (insert numbers in place of <description of number>.)
N040 (Delete lines N020, N030, and N040 when you do that.)
N050 G0 Z <Z-value of retracted position> F <feed rate>
N060 #1001=<nominal X-value of hole center>
N070 #1002=<nominal Y-value of hole center>
N080 #1003=<some Z-value inside the hole>
N090 #1004=<probe tip radius>
N100 #1005=[<nominal hole diameter>/2.0 - #1004]
N110 G0 X#1001 Y#1002 (move above nominal hole center)
N120 G0 Z#1003 (move into hole - to be cautious, substitute G1 for G0 here)
N130 G31 X[#1001 + #1005] (probe +X side of hole)
N140 #1011=#2000 (save results)
N150 G0 X#1001 Y#1002 (back to center of hole)
N160 G31 X[#1001 - #1005] (probe -X side of hole)
N170 #1021=[[#1011 + #2000] / 2.0] (find pretty good X-value of hole center)
N180 G0 X#1021 Y#1002 (back to center of hole)
N190 G31 Y[#1002 + #1005] (probe +Y side of hole)
N200 #1012=#2001 (save results)
N210 G0 X#1021 Y#1002 (back to center of hole)
N220 G31 Y[#1002 - #1005] (probe -Y side of hole)
N230 #1022=[[#1012 + #2001] / 2.0] (find very good Y-value of hole center)
N240 #1014=[#1012 - #2001 + [2 * #1004]] (find hole diameter in Y-direction)
N250 G0 X#1021 Y#1022 (back to center of hole)
N260 G31 X[#1021 + #1005] (probe +X side of hole)
N270 #1031=#2000 (save results)
N280 G0 X#1021 Y#1022 (back to center of hole)
N290 G31 X[#1021 - #1005] (probe -X side of hole)
N300 #1041=[[#1031 + #2000] / 2.0] (find very good X-value of hole center)
N310 #1024=[#1031 - #2000 + [2 * #1004]] (find hole diameter in X-direction)
N320 #1034=[[#1014 + #1024] / 2.0] (find average hole diameter)
N330 #1035=[#1024 - #1014] (find difference in hole diameters)
N340 G0 X#1041 Y#1022 (back to center of hole)
N350 M2 (that's all, folks)
as written, a good Motion Controller or PP machine will have the exact result of G31 in
uservars 2000...2002
-
My thought was that they may be writing to OEMDRO2000, 2001,2002, ...
But maybe their notes are completely wrong.
you seem to be right, missed the post with the Changelog notes.
Looks like they are writing UserDro 2000...
-
'This is a Probe z surface macro supplied by XHC of China
FeedCurrent = GetOemDRO(818) 'Get the current settings, OEM DROs (818)=Feedrate DRO
ZCurrent = GetOemDro(802) 'OEM DROs (802)=Z DRO
GageH = GetOEMDRO(1001) 'OEMDRO(1001)=Gage Block Height
ZNew = ZCurrent - 6 'probe down max. 6 inches
Code "G90F5" 'slow feed rate to 5inches/MIN
SetOemDRO(818,5)
Code "G4 P1" 'Pause 1 second to give time to position probe plate
Code "G31 Z" &ZNew
While IsMoving()
Sleep(10)
Wend
Call SetDro (2,GageH) 'DRO(2)=Z DRO
FinalMove = GageH + 1 ‘move 1 inch above gage height
Code "G0 Z" &FinalMove
Code "F" &FeedCurrent 'restore starting feed rate
SetOemDRO(818,FeedCurrent)
'Note that there are also, FRENCH and ITALIAN probing macros (posted in this forum) that DO NOT use those legacy setvar() and getvar() functions.
-
all those "probing" macros will work, no question,
but the Point is the accuracy you whant to have?
but this is a complete other discussion and offtopic here.
-
'Note that there are also, FRENCH and ITALIAN probing macros (posted in this forum) that DO NOT use those legacy setvar() and getvar() functions.
GetVAR() is not a "legacy" function. It's the proper and only accurate way to read the trip point. And the majority of chinese controllers do not support it's use.
-
GetVAR() is not a "legacy" function. It's the proper and only accurate way to read the trip point. And the majority of chinese controllers do not support it's use.
thats what i tryed to say. ;)
-
It is perhaps as Craig has been saying all along, in many other postings - if you want accurate and reliable machining / probing / etc. then forget the cheap Chinese controllers.
Tweakie.
-
i will leave the screensets for a while,,,,,,,with my normal setup i have added the big tex m6 strart macro,,,,at least now i have the spindle move to the fixed plate location where i can change the tool and use the auto toll zero function,,,then continue with the cut. when i get more time i will sort a new controller,,, has anyone tried the " AXBB-E ethernet motion controller and breakout board combined controller " from the company behind of uccnc .
-
'Note that there are also, FRENCH and ITALIAN probing macros (posted in this forum) that DO NOT use those legacy setvar() and getvar() functions.
GetVAR() is not a "legacy" function. It's the proper and only accurate way to read the trip point. And the majority of chinese controllers do not support it's use.
See attached cut from "Mach3 V3.x Macro Programmers Reference.pdf" by NFS.
-
EVERY function is in the "legacy" list.
-
has anyone tried the " AXBB-E ethernet motion controller and breakout board combined controller " from the company behind of uccnc .
I have one, but have not tried it with Mach3. I bought it for use with UCCNC.