Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: Ducman56 on September 07, 2015, 04:29:54 PM
-
I am having a problem with the z axis on my 6040 machine and am looking for some help if possible.
I have drawn up a simple 2d engraving in Aspire 4.5 and selected a 45 deg included angle engraving tool with a 0.2mm flat point.
The aspire has out put the code for me which when I run it show a flat depth maximum of 1mm in the code when running on Mach3, at no point does it show any deeper cut.
However, when I measure the actual cut, it is 1.72mm deep. the other 2 axis are the correct sizes. This depth of cut is constant throughout the design
I checked the calibration of the z axis, and it is correct as near as I can measure.
Any suggestion gratefully received.
On another tack, during a cut, there was a judder and the cut was displaced laterally by 40mm on the x axis at one point, it then continued on and completed the cut perfectly after, just 40mm offset. The tool returned to zero after the cut, which was also offset by 40mm on the x axis. The work piece had not moved and the travel of the spindle was unchanged, i.e. it had not slipped on the screw somehow.
Again bright ideas for a check and solution please !!
-
Could you post your .xml file (rename it to a unique name ie. Ducman.xml) so we can try to find the cause of these two problems.
Tweakie.
-
Ok many thanks for the swift response, .xml file attached as requested
-
My recommendations…
Reduce your Kernel speed from 100kHz to 35000Hz (25000Hz may be even better).
Reduce your Velocity & Acceleration settings for your X and Y axes by approx. 30% from their current values.
Check your requirement for input signals (Config. / Port & Pins) – you are specifying pins 7,8,9 which are not allowed (these are output signals used in Motor Outputs).
Check your requirement for Output #1 as you are specifying pin 5 which is a duplicate of your Y axis Direction signal.
Uncheck Use WatchDogs in General Config.
Try that for starters and let us know how you get on.
Tweakie.
-
Thanks very much for the feedback I will try what you suggest, The figures there are what came as the configuration file for the machine, I do not understand them so did not alter them.
I have done the first 2 items
However like I say, I do not understand what you have suggested, I am assuming the changes will not cause any problems ?
"Check your requirement for input signals (Config. / Port & Pins) – you are specifying pins 7,8,9 which are not allowed (these are output signals used in Motor Outputs)."
"Check your requirement for Output #1 as you are specifying pin 5 which is a duplicate of your Y axis Direction signal."
I have found these but now what do I do? change them to what?? like I say, sorry don't understand, surely all this stuff is preselected by manufacturer?? or is my ignorance just being highlighted again :-[
Seriously, thanks for the help, but I need more cyber hand holding I am afraid
-
Basically… the LPT parallel port, as far as Mach3 is concerned, has Input pins and Output pins (10-13 & 15 being Input pins and 1-9,14,16 & 17 being Output pins with pins 18-25 being Ground). Input pins cannot be used as Outputs and visa-versa.
Your equipment manufacturer should have an understanding of this and provide you with settings for Mach3 that are correct.
However, the world is not perfect so we make do…
I would disable the X,Y,Z Input Signals (specifying pins 7,8,9)
Also disable Output #1 (specifying pin 5)
Try it and see.
Tweakie.
(I have been using Mach3 for more than 10 years now and I am still learning ;) )
-
OK,thanks again :D this is a USB connected card not parallel does that make a difference?
-
OK,thanks again :D this is a USB connected card not parallel does that make a difference?
It may well make a difference - which external motion controller are you using ??
Tweakie.
-
Xulifeng-Mach3-USB-Motion-Card
-
The Xulifeng emulates the parallel port, using the same pin numbering for the inputs and outputs.
Which version of Mach3 are you using ??
Tweakie.
-
Version R3.043.066
-
Whilst Leafboy say that their product supports R3.043.066 there have been issues reported here on the forum which would indicate otherwise.
In addition to the things I have mentioned perhaps reverting back to an earlier version of Mach3 may also be a prudent move (earlier versions can be found in ftp downloads http://www.machsupport.com/software/downloads-updates/).
Tweakie.
-
OK thanks, any suggestions as to which version please?
-
We all seem to have our own personal choice but I use R3.043.056 if that's any help.
Tweakie.
-
Cheers, I will try that with the mods you suggested to kernel and accelleratiuon, but not ports and pins I guess ?
-
OK, I installed the older version of mach3 with the suggested modifications.
I produced a series of test squares to cut using different tools to see what would happen, code attached.
These are simple squares, cut with an engraving tool for the fist 3 using code generated by Aspire in Vcarve, profile and pocket options without the 'display on 3d model' selected, the second 3 with that option selected, all set to 1mm depth of cut by Aspire. The third set of 3 use the same Aspire options but with a 2mm ball nose tool.
The results were interesting and confusing.
The first 3 cut to 1.80mm deep, the second 3 to , 2.10 mm and the 3rd set to3.46 ! I then changed the tool to a 4mm mill and using the code from the ball end setup and ran that, these cut to 2.18mm deep.
I had manually set the depth z=0 so it was not an issue with the auto zero tool, I also checked the calibration in the approved method and all was spot on. ( the x and y axis cuts were precise)
Then, just when I thought I could not get more confused :-[ I set the 4mm end mill to z=0 dropped the depth using Mach3 to 1mm and simply ran a straight line cut by jogging the x axis across, it cut to 1mm deep. So it would appear that the Mach3 is working correctly (??)
I have to say I did not notice any difference in the performance with the changes made to the Mach3 version or the suggested modifications to kernel speed etc. but this was a very simple set of code and perhaps it would be more stable on more complex cuts.
As a self-confessed ignoramus on these matters I am totally baffled, why, when the code shows -1mm Z in all cases, should it cut differently in the different examples when the calibration would appear to be OK.
I am saving the files from Aspire in what I think is the correct format, Mach2/3 Arcs (mm) (*.txt), and as the x and y are correct I can't be that far out, can I ??
I even installed Mach3 on a different, more powerful computer, just in case that was a problem source, but the results were the same.
-
I ran a series of tests today using a very simple square cut calculated from Aspire, see attached file.
Following advice from the Aspire forum, I changed line N10 in 2 ways , once I changed the G43 to G49 and the H1 to H0, then I removed the G43 and the H completely.
I ran the test cut 3 times, as generated, with g49 H0, and without G43 h
There was no appreciable difference in the cut depths, which were all +-1mm :) as required, I ten ran the logo file which I had first noticed the problem on, and it also was correct.
i think the reversion to the earlier Mach3 must have done the trick, I did check the version which came with the machine, which I did not use because it was a cracked copy, I just went ahead and bought a real one and downloaded the latest version when I bough it, the original one was 3.043.056, do you think I should revert to that? or leave it as is because it appears to be working OK now?
Thanks again to all for your inputs, most valued :)
-
the original one was 3.043.056, do you think I should revert to that? or leave it as is because it appears to be working OK now?
Leave it as it is (If it ain't broke don't fix it) ;)
Tweakie.