Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: Overloaded on May 06, 2014, 02:59:25 PM
-
MDI G28 does nothing.
M47 rewinds but does not repeat.
:)
-
Sim does not do G28 at this time.
M47 is replaced by M99. Forget everything you knew of M47. :)
Steve
-
G28 /30 does work here It goes to the way point then back to 0,0,0. I just do not know the parameters to set for G30 P2-4 so I cannot test that part.
There is just NO g28.1
Just a thought, (;-) TP
-
Well Sh*t ... there it is (M99) right there in the manual .... my fault, sorry. :P
(I hate it when that happens) ::)
Thanks,
Russ
Steve, can you narrow it down to what specific aspects of Mach4 you are most interested in getting exercised for testing ? (if any)
Actual running of code ?
As mentioned, screen issues can wait.
Special requests for convenience/preference could maybe wait ?
Just want to optimize all efforts in order to expedite reaching your goal as efficiently as possible.
You've probably got some pretty big fish to fry, saute' the minnows later. :)
Thanks again,
Russ
:)
-
G28 /30 does work here It goes to the way point then back to 0,0,0. I just do not know the parameters to set for G30 P2-4 so I cannot test that part.
There is just NO g28.1
Just a thought, (;-) TP
neither work here T, 28 or .1,
are you on the new release ?
Russ
-
New release, Tested G28 and G30 both seem to work correctly I just cannot preset the G30 P2-4 parameters to create the GOTO Point. I can shift the G28 position with refall then offset. It returns to true home
If you type in G28 X10 Y10 It will then Goto the way point of X10 Y10 Then return back to home at 0,0.
Same with G30 just no way to set teh G30 Pxx positions. still looking
(;-) TP
-
Hello Terry
The registers for the G30 are as follows:
G_30_XPOS 5181
G_30_YPOS 5182
G_30_ZPOS 5183
G_30_APOS 5184
G_30_BPOS 5185
G_30_CPOS 5186
G_30_P2_XPOS 5301
G_30_P2_YPOS 5302
G_30_P2_ZPOS 5303
G_30_P2_APOS 5304
G_30_P2_BPOS 5305
G_30_P2_CPOS 5306
G_30_P3_XPOS 5311
G_30_P3_YPOS 5312
G_30_P3_ZPOS 5313
G_30_P3_APOS 5314
G_30_P3_BPOS 5315
G_30_P3_CPOS 5316
G_30_P4_XPOS 5321
G_30_P4_YPOS 5322
G_30_P4_ZPOS 5323
G_30_P4_APOS 5324
G_30_P4_BPOS 5325
G_30_P4_CPOS 5326
That should help you
-
Thank You Brian that helps a lot. The more parameters I have on hand the Better conditional Gcode looks.
Is there a way to pull all the parameters out for a parameters list??
(;-) TP
-
Works here I tested both modes G90 /G91 with P1 P2 P3 P4. XYZA
Now a question (;-) would it be possible to USE the G30 with or without the waypoint move from a parameter call instead of the G90/G91 flip flopping. Mach3 was nice being able to turn OFF the Waypoint move.
Say #*********x = 1 is ON #*********x = 0 is OFF
Sometimes that way point move is nice to have and sometimes it is a pain in the rear programming wise.
(;-) TP
-
Sorry, we are going to stick with the standard way point convention. I know it is odd but it is what we have all lived with for years.
Now if you would like to move to a position of the G30 you could look up the registers and do a g53.
G0 g90 G53 X[5181] Y[5182] Z[5183]
Not tested but it should work.. I use G53 because I hate G28 / G30
-
Well with us older forgetfull dudes it is easier to remember G30 P4 than to remember where it actually is in Positional code G53 X24.124 Y36.9876 Z6.78632 each time we need to revisit there. (;-)
Tools and service calls are very expensive .
(;-) TP
-
Sorry, we are going to stick with the standard way point convention. I know it is odd but it is what we have all lived with for years.
Now if you would like to move to a position of the G30 you could look up the registers and do a g53.
G0 g90 G53 X[5181] Y[5182] Z[5183]
Not tested but it should work.. I use G53 because I hate G28 / G30
That way did not work but this way did.
#5181 = 1 #5182 =2 #5183=3 #5184 =4
G0 g90 G53 X#5181 Y#5182 Z#5183
-
Are the registers for the G30 suppose to be persistant ???
(;-) TP
-
Yeah I can see that I forgot the # But you got the idea
Not at this time..
-
I was just curiuos as testing showed P1 and P3 are NOT persistant BUT P2 and P4 ARE persitant. Where are the persistant values stored.
In Mach3 I have a Var report that I can search thru ALL the #vars and report their values.
It wouold be NICE to have one for MAch4. Currently with #vars and params and Registers I am flying Blind.
(;-0 TP
-
I have a plugin here that will report the # vars. It has been added to the Reg plugin. It will be in the next release
Thanks
Brian
-
HIYA Brian I might be time to create a Mach4 dictionary the defines WHAT are all these things ( #var,#param, Registers)and WHAT they should be called officially to avoid confusion.
That way everyone speaks the same terms.
Just a thought, (;-) TP
-
I call them what you like but the #var and #param are stored in registers.. they are all the same sort of.
Thanks
Brian
-
I have always known them as
a # var such as #1 or A in a G65
A # param is a parameter for a function such a #5061 A axis probe trip position OR set #9999 =1 to turn ON/OFF a function
A register is where these are stored and can be called anything as Number or a Name
Just a thought, (;-) TP
-
Yeah that is what I said... :)