Ok I have a question, you mentioned on one machine you are having these issues. Is it only on one machine? are the others OK?
Hood

Only bug #2 occurs on one machine. The rest of the issues are problems in all mach installs of 3.42.015. I've tried uninstalling mach deleting the mach folder, reboot, and reinstalling mach and still problem exists. I didn't try clearing anything in the registry though.

I will have a look tomorrow on my machines but I know for sure the DROs dont do that, well sometimes they are out 0.001 but that is a SmoothStepper thing and as I am in metric that is an insignificant number as its not cumulative. As I use the SS I cant test that one out for you.

 I think the pulse width was an issue on earlier versions  of the Dev revisions but sure that was sorted, certainly not seen reports of it recently. Mine are set to zero on all machines so obviously it doesnt affect me but I will test out tomorrow and see.

Programme extrema is still an issue in Turn I think, not sure about mill but again will check and see on my machines.

Never use CV settings but will test tomorrow if I get a chance.

Wouldnt call 5 a bug but rather a what you would like. Unless that is it is taking exceptionally long of which it did in some of the earlier Dev versions.

I am sure I get the prep move box but again will check for sure.

Hood



Hood

I will have a look tomorrow on my machines but I know for sure the DROs dont do that, well sometimes they are out 0.001 but that is a SmoothStepper thing and as I am in metric that is an insignificant number as its not cumulative. As I use the SS I cant test that one out for you.

Like I said sometimes they have 0.0013mm left in them when zeroing. I don't think that is an insignificant number. I asked for zero not close to zero.

Wouldnt call 5 a bug but rather a what you would like. Unless that is it is taking exceptionally long of which it did in some of the earlier Dev versions

The code that parses the Gcode is slow. It needs improvement, maybe needs to be rewritten using regular expressions.
 

I am sure I get the prep move box but again will check for sure.

There is no dialog box to cancel the prep move that has been added to tool changes.

I added a new bug #7. (see below)

Brian

1. Machine Coord DRO's don't always zero they will have 0.0013 left in them sometimes.

2. Step and Dir pulse lengths on some installs will reduce upon opening and closing the motor tuning window.

       ie.  Step=2  Dir=1    after opening, setting, closing , opening motor tuning will change each by -1   

3. Program extrema is not being calculated correctly.

4. Mach seems to be having issues saving CV state if you change the CV dist tolerence or turn CV dist on/off.
   Closing and opening the session fixes it, but I've learned mid session changes are risky behavior.

5.Mach is parses the code pretty slow when you open a file. I'm guessing it parses the code for gcode errors and finds program extrema.
I would like to be able to turn off the program extrema calculation method or see it rewritten using RegEX so that it parses faster.

6. If you jog the machine during tool change M6 (so as to be able to physically get to you spindle and change the tool upon pressing cycle
start mach moves to its previous position with no warning or way to cancel this. This needs to have the same dialog added that you get when using
"run from here".

7. Machine is always underfeeding. If I set feed rate to 100mm/min and give the machine plenty of room to make a single axis move and get up to speed
it is always under feeding by about 4mm/min, it never reaches the programmed feedrate and my max velocity is 800mm/min. It didn't do this in older mach versions.

Brian

Hello Brian,

1. Machine Coord DRO's don't always zero they will have 0.0013 left in them sometimes.

I think you are setting zero with the Reff command with no home switches .. This is a known problem at this time (I will fix it but it is working with home switches). Also if you are going to set zero you should use the Zero x,y,z buttons... Last what is your steps per unit ?? You may not be able to get to zero (Limitation of your machine) and this is as close as the software can make your machine round the digital steps to zero.

2. Step and Dir pulse lengths on some installs will reduce upon opening and closing the motor tuning window.

       ie.  Step=2  Dir=1    after opening, setting, closing , opening motor tuning will change each by -1   

This is fixed in 3.042.015

3. Program extrema is not being calculated correctly.

Could you please give an example of what is not correct? For example are you running loops with offset shifts and so on in the code? If so it is hard to tell if you are in the correct position when the reference position is changing That is the only time that I know when this is not correct..

4. Mach seems to be having issues saving CV state if you change the CV dist tolerence or turn CV dist on/off.
   Closing and opening the session fixes it, but I've learned mid session changes are risky behavior.

You should close and reopen the software to back up your settings...This is a very good idea

5.Mach is parses the code pretty slow when you open a file. I'm guessing it parses the code for gcode errors and finds program extrema.
I would like to be able to turn off the program extrema calculation method or see it rewritten using RegEX so that it parses faster.

It is also the calcs for drawing the toolpath that is slowing down the load time... In the diagnostics page please turn off the toolpath and tell me if you like that better.

6. If you jog the machine during tool change M6 (so as to be able to physically get to you spindle and change the tool upon pressing cycle
start mach moves to its previous position with no warning or way to cancel this. This needs to have the same dialog added that you get when using
"run from here".

Please have a look at the M6Start.m1s and M6End.m1s macros and change them to your liking This is the only way to change how the toolchanges are done

7. Machine is always underfeeding. If I set feed rate to 100mm/min and give the machine plenty of room to make a single axis move and get up to speed
it is always under feeding by about 4mm/min, it never reaches the programmed feedrate and my max velocity is 800mm/min. It didn't do this in older mach versions.

\
This has to do with how the feedrate is now calculated.. in the end are not far off (less then one %) this has to do with the amount that your CPU timing is off from what it should be...


Hope that helps you
Brian

After pressing 'feed hold' and then resuming the operation with cycle start the original feed rate had been forgotten and the system crawls with like an inch per minute.

With the inability to accelerate past 100% with the smooth stepper this is really a problem.

Cheers
Lemo

Hello,
Could you please give a bit more info?

Is the machine moving at the programed feedrate of when you did a feedhold?

Are you typing in a new feedrate into the DRO that you would like it to do and it is setting the feedrate back to what is in the program? I have changed much of the feedhold code to save the feedrate that you last where programed at..

Brian:

Just downloaded and ran 3.042.015 and have the same issue previously reported regarding 3.042.004 (see below).  The part was cut correctly, but looking at the weird numbers in the Tool: Table Display screen was really disconcerting.  Have gone back (again) to 3.041.

Previous post follows:

Downloaded and ran 3.042.004 version and had nothing but problems.  Code that ran perfectly in version 3.041 would not run without problems in arcs, etc.  One thing I noticed on the Diagnostics screen is the abs max x, y, z were all out of proportion to the drawing in the code in mill mode.   The figure in the code is 11.5 by 5.5 inches - the Diagnostics screen showed the max to be like 116 (somethings).  Yes, I copied my old xml file into Mach before running the code.  Yes, my native limits were in inches.   I had the same problem with another code.

Bob @ BobsShop

I've also had a problem with the feed rate but in my case I've adjusted it with the FRO +/- buttons. Then somewhere along the way the machine changes speed apparently on it'd own (Perhaps commanded by an F word but not to the extent it changes) and the FRO buttons don't do anything any more. You can adjust them from 0 to the max and press the FRO reset and the speed does not change. You're pretty much stuck with the speed you have unless you start the G-code program again.

Sage

Bob,
I would like nothing more then to fix your problem.. But you are giving me nothing to work with... If you doing show me the code that I need to run I will not look at the problem.. I have tested it and it worked with the files that I tested. So if you would Screen shots and GCode will go great lengths in helping me find the problem..
Thanks
Brian

Downloaded and ran 3.042.004 version and had nothing but problems.  Code that ran perfectly in version 3.041 would not run without problems in arcs, etc.  One thing I noticed on the Diagnostics screen is the abs max x, y, z were all out of proportion to the drawing in the code in mill mode.   The figure in the code is 11.5 by 5.5 inches - the Diagnostics screen showed the max to be like 116 (somethings).  Yes, I copied my old xml file into Mach before running the code.  Yes, my native limits were in inches.   I had the same problem with another code.

Bob @ BobsShop