Hello Guest it is May 23, 2019, 05:40:15 AM

Author Topic: Comments about Mach4 in Demo  (Read 63278 times)

0 Members and 1 Guest are viewing this topic.

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #80 on: April 30, 2014, 04:05:39 PM »
I also noticed that the Gcode comments are not displayed on screen.

(;-) TP

Offline smurph

*
  • *
  •  1,085 1,085
  • "That there... that's an RV."
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #81 on: April 30, 2014, 10:14:10 PM »
I also noticed that the Gcode comments are not displayed on screen.

(;-) TP

This is an option now.  It is set on the general tab of the configuration dialog.

Steve

Offline smurph

*
  • *
  •  1,085 1,085
  • "That there... that's an RV."
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #82 on: April 30, 2014, 10:22:11 PM »
HIYA Brian , looking at the fixture and tool tables I see that we can now use the keyboard to move around in the values windows to do updates to the values which is VERY GOOD  BUT I do not see a way to EXIT out with a mouse.

Also reviewing the G98/99 calls I see we can now GOTO a sequence line.  Can I assume the the sequence number is the LINE # ??

Can we expect conditional in the near future to make that useful.

Also the calls are not consistant.

M98 Pxx Qxx Lxx      Where Q calls the GOTO line #

M99 Pxx                Where P calls the goto Line #

Would it not be more consistant for the Q to be used in both cases to call the GOTO line#  ??

I think you can close the table windows with the standard ALT-F4.  But I will see if I can make it work with the Escape key.  Maybe I can make that work.  But we are getting into the weeds of the window framework there.  If it won't work across all platforms, I'm kind of stuck with the least common denominator.

I did the M98/M99 with the help and direction of a very experienced Fanuc programmer and the Peter Smid book.  I think it is correct.  But I will look at it.

Ok, I just checked.  There is no Q address for M99.  P it is.  Inconsistent, yes.  Incorrect, no.  The sequence number is defined by the N address, not line number.

Steve

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #83 on: April 30, 2014, 10:43:42 PM »
HIYA Steve, while you are looking at teh exscape sequence could you take a look at the values entry sequence ? As is on a line say tool #3 when you enter in a value an press ENTER it skips DOWN to the next Tool # line instead of to the right in order to finish adding values for THAT tool #.

It makes it very clumsy to add tool /fixture parameters as after each entry you then have to shift back up then move over to the right in order to add the next tool parameter.

I tested the M99 P## earlier but it stuck in the loop over and over in the sub call BUT the M99 Q seemed to work ok. Maybe I muffed the test somehow I will go back and retest the sequencing again.

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #84 on: April 30, 2014, 11:21:23 PM »
HIYA Steve M99 Pxx it is. When I tried the M99Qxx it just ignored it with NO error code and it just seemed to work. I do notice that there is liitle to no error codes in the gcode side it will take just about anything and just ignore what it does not know and go on without erroring out or wwrning you there is bad code.

Another item When trying to create a new program from edit Gcode you cannot open a new  file. You must first load an OLD program then edit and rename.

Also you say you can turn on comments in config but MY version does not have a mach config, it is greyed out and you cannot access it.

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #85 on: April 30, 2014, 11:33:26 PM »
Another problem with the Gcode editor is sometimes when you return to Mach4 it locks up mach and crashes OR it closes and then tell you it cannot load a file at this time.

Some times it works just fine

???? (;-) TP

Offline smurph

*
  • *
  •  1,085 1,085
  • "That there... that's an RV."
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #86 on: April 30, 2014, 11:38:07 PM »
Can we expect conditional in the near future to make that useful.

We already have it.  Full Fanuc custom macro B with full G65 and G66 support as well.  It is a Mach 4 Industrial feature.  Not part of Mach 4 Hobby as Mach3 never had it.  However, it is turned on in the Beta build if you want to try it out.  SETVN and gcode labeling of subs is not finished yet.  Passing an E address as a parameter to a G65 is not legal either as we use E as scientific notation.

One thing to note is that CV is NOT interrupted with the conditional statement.  So the conditions are evaluated at the point at which the look ahead processes them.  So if you want the condition to be evaluated in sync with the machine run, then you must use an exact stop preparatory code right before the conditional statement.  That is the mode that we are currently using.  This mode has advantages in producing smooth movement with calculated moves.  The other option is that all conditional statements will break the CV chain ensuring that the evaluations are always synced with the machine run.  This mode is not used at this time and favors code path switches based on external inputs.  I will possibly make a switch so that a M code can control which mode.  But for now only the first mode it supported as I feel it is the most flexible because you can control when the evaluation happens with exact stop.

IF [condition] GOTO <seqnum>
IF [condition] <statement>
WHILE [condition] DO<level>
...
END<level>

We support the standard 3 level nesting.

HIYA Steve, while you are looking at teh exscape sequence could you take a look at the values entry sequence ? As is on a line say tool #3 when you enter in a value an press ENTER it skips DOWN to the next Tool # line instead of to the right in order to finish adding values for THAT tool #.

It makes it very clumsy to add tool /fixture parameters as after each entry you then have to shift back up then move over to the right in order to add the next tool parameter.

I tested the M99 P## earlier but it stuck in the loop over and over in the sub call BUT the M99 Q seemed to work ok. Maybe I muffed the test somehow I will go back and retest the sequencing again.

The entry sequence in the grid is controlled by the window framework.  I can't change it.  I have already tried.  :(

Let me know the results of your M98/M99 test.  Because I had that working flawlessly at one point.  Looking at the code, any Q address on the M99 will be ignored.  It is definitely looking for a P address.  Also, keep in mind that the M99 P address must refer to a sequence number in the calling program, not a line number.

Steve

Offline smurph

*
  • *
  •  1,085 1,085
  • "That there... that's an RV."
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #87 on: April 30, 2014, 11:48:11 PM »
HIYA Steve M99 Pxx it is. When I tried the M99Qxx it just ignored it with NO error code and it just seemed to work. I do notice that there is liitle to no error codes in the gcode side it will take just about anything and just ignore what it does not know and go on without erroring out or wwrning you there is bad code.

Another item When trying to create a new program from edit Gcode you cannot open a new  file. You must first load an OLD program then edit and rename.

Also you say you can turn on comments in config but MY version does not have a mach config, it is greyed out and you cannot access it.

So the M99 question is answered then. 

As for the errors...  Don't produce bad code!  :)  All kidding aside the interpreter does not currently check M codes for sanity.  I will look and see what I can do there.

And I will address the editing of a new file.  I never even thought of trying to do that!  I always load up an existing file.  Someone asked what the point of this thread was earlier.  Well...  this is it!!!

We have done our absolute best to get Mach 4 ready with as few issues as possible.  Obviously we have spent a great deal of time on it and even suffered criticism as a result.  But there is no possible way we can cover all of the potential issues as many of them might not show up due to how Brian or I operate Mach.  Each user has their own way of doing things and that is the point of this thread.  To find those problems!

The G code editor file load might be file sharing violation issue.  Two editors open maybe?  See if you can nail that one down as I have not see that.

Disable the control and the Mach config will light up. 

Steve

Offline BR549

*
  •  6,865 6,865
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #88 on: May 01, 2014, 01:21:12 AM »
HIYA Steve the error codes are not just a problem in Mcodes(;-)

Try G02     (with no I or Js) it does not error out here it ignores it and goes on.  And there are more.

So with the current mode of conditional I can use the G60 to create an exact stop then call parameters that are ONLY available at that time. My current Fanuc macroB is very rusty BUT it should not take long to knock the dust off of it(;-) I spent a long time converting macroB to Machmacro now I have to go the other way(;-)

I switched Mach4 to ADMIN rights and the crashing of the Gcode editor has stopped for now.

(;-) TP

Offline smurph

*
  • *
  •  1,085 1,085
  • "That there... that's an RV."
    • View Profile
Re: Comments about Mach4 in Demo
« Reply #89 on: May 01, 2014, 01:45:31 AM »
G02 with no I or Js is perfectly acceptable.  It is a modal command.  Consider:

%
F30
G02
X.. Y.. I.. J..
X.. Y.. I.. J..
X.. Y.. I.. J..
G01
X..  Y..
M02

And:

G02 F30  (switch to G02 mode)
G01 X0 Y0 F30 (switch to G01 mode.  Previous line ends up as a no op)
...

Got any more?  There might be some and I would like the know as I'm not ever using all of the G codes.  I tend to use CAM because I'm lazy.  :)

Steve