Hello Guest it is May 17, 2024, 03:31:28 PM

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.


Messages - Brian Barker

561
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 05, 2008, 07:58:06 PM »
Bob,
Thanks for the code to test with!!! Now to see if I can find the trouble ;)
Thanks
Brian

562
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 05, 2008, 02:03:12 PM »

Quote
1. Can you not force SetMachZero() to set the DRO to zero at its current position? I'm not understanding why this needs to be calculated I just want to push 0 to the DRO.

It is a digital signal.. that is as close as you can set it ... It is so close that I would think it is okay :)
Just to help people there is NO SetMachZero()  call. in VB.. there is an OEM button ...


Quote
4. One job I'm running is 0.25" in size with features as small as 0.005" the next job is 12" in size with very few small features. I find CV dist tolerance to be a nice feature but an appropriate distance is different if you part is large or small.

If you are going to be doing parts like that you NEED to have more steps per unit..


Quote
5. I was referring to mach's toolpath display not mach itself. I find myself turing the toolpath on and off. On so I can look and off so I can run cause mach runs better with toolpath off on large gcodes. I'm guessing without a major rewrite of the viewport there's not much that can be done.

I am looking to change the display code in the next major update... this is a large job and need to have a good release of what we have now before I start :P)

Quote
6. Copy and pasting stupidity. Sorry. Not yet  I'll try this on Friday when I'm back at the shop and post my result.
I understand!

Quote
7. Given 100mm/min is program feed, it is a single axis move, actual feed is 96mm/min, and there is plenty of distance to accelerate to that velocity and the max velocity of the machine is >100 100- 4 = 96/100 = 96% = 4% off in speed.
No fair... you can't change the numbers on me... that is not what you posted! The problem is that we are reporting what it IS doing.. this is something that we will look into more in the next large rev.. for now it is what it is  ..

Thanks
Brian



563
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 05, 2008, 01:38:12 PM »
Hello Bob,
This is fine but know that with out examples you are not going to see any fix for that bug.. part of the low cost of the software is that fact that we need your help to make it better.. I can not fix what I can't see  :) .

So it will get fixed if an other reports the problem and makes it so I can see it.. (Crystal ball is broken)

Thanks
Brian

564
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 05, 2008, 09:08:11 AM »
Hello,
1.) 1/800 = .00125 or if you round the DRO .0013.. If you would like a machine that can zero you need to have a greater number of steps per unit...

2.) I would like to see the XML that you are working with... if you look for the PulseWidth and DirPulse I would like to know if it is getting saved to the XML.. also exit the software as soon as you make the change to back up the XML

3.) NA

4.) What are you doing that you need to change all the settings of you machine as you are running.. the stuff that you are talking about should be set one time. If you are going to change the settings one time I don't see that there is a problem with shutting down and restarting.

5.) There is no way to lower the resource's... The Driver is taking 50% of the CPU power to make the P Port a motion controller.

6.) I see you have the same reply as 5.) ... So tell me if you have changed your macro..

7.) 800 - 4 = 796 796/800 = .995 so it is 99.5% on so it is .5% off in speed... I think that is less then 1 % :)
I could add this to the doalig at some point but this change will make the new manual incorrect... So at this time I am going to wait.

Thanks
Brian


565
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 04, 2008, 11:23:38 PM »
Hello,
post a Gcode file and tell me what you are doing.. I am NOT seeing this trouble here.. I trust that you are seeing it but if I don't see it I will not be able to fix it.
Thanks
Brian

566
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 04, 2008, 09:12:55 AM »
Hello Sage,
The other versions of Mach3 would look at the Feedrate of the head of the lookahead.. this would reset your feed rate to the lookahead on a feed hold.. This fix was to talke that out, so please be sure that you are on the latest Dev version..
Thanks
Brian


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

567
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 04, 2008, 09:10:28 AM »
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

568
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 04, 2008, 08:47:14 AM »
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..

569
General Mach Discussion / Re: Bugs in Mach 3.42.015
« on: November 03, 2008, 09:42:28 AM »
Hello Brian,

Quote
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.

Quote
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

Quote
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..

Quote
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

Quote
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.

Quote
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

Quote
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

570
Mach3 under Vista / Re: Installation fails during install of 3.041
« on: October 12, 2008, 07:19:04 PM »
I wish there was a way to pass out a prize for the oddest problem :) I think you may get it LOL..

Thank you for your hard work at finding the solution... I never would have gotten that one :(

Thanks
Brian