Hello Guest it is March 28, 2024, 12:18:16 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 - KLJ

Pages: 1
1
G-Code, CAD, and CAM discussions / Re: Cumulative error in YZ
« on: February 26, 2018, 06:47:29 AM »
It was too late for me to edit the previous message, so here is an addendum:

EDIT: I just remembered one experience with a blueprint that was made for me by a customer in Australia on poster board type material.  When he rolled the material for shipment in a tube the differential in radii from one side to the other of the material caused a permanent distortion in the drawing (it was shortened linearly).  If I had scanned that drawing and used it without referring to and double-checking the longitudinal dimensions the error would have cumulative and I might be chasing after errors/wear in the CNC drive.

Alternatively, I also learned that expensive commercial scanners (like those used to copy blueprints) needed correction factors after the machine introduced repeatable linear errors during the feed process into the scanning bed/strip.  It was very expensive for me in terms of time and materials to discover all this.

2
G-Code, CAD, and CAM discussions / Re: Cumulative error in YZ
« on: February 26, 2018, 06:21:10 AM »
Ok, I understand what you were saying better now.

One of the problems with using large items made from a relatively strong polymer versus a wax as a burn-out material in the refractory is that the polymer will expand as it heats and burns.  With weak refractory this would cause cracking but with stronger material this MIGHT have resulted in a permanent expansion/distortion of the mold which the cast aluminum would then have assumed.

What I am trying to say is that you should be careful in attributing the problem during machining to coding problems alone.  Precision processes rely on each step being controlled and predictable -- try repeating the experiment with wax.

3
G-Code, CAD, and CAM discussions / Re: Cumulative error in YZ
« on: February 25, 2018, 10:17:37 PM »
What are you using the acronym "ABS" to designate?  Acrylonitrile butadiene styrene can be used as a fugitive pattern material in a precision lost wax casting process (I used to do this).

4
G-Code, CAD, and CAM discussions / Re: Cumulative error in YZ
« on: February 25, 2018, 04:55:28 PM »
My first thought is whether the temperature of the ABS work piece rose during machining.  The coefficient of thermal expansion could possibly introduce such an error.  Do you use a spray coolant at a constant temperature?

I cut out parts from Teflon and just recently had a customer contact me claiming that the Teflon piece did not fit the steel carrier.  I told him the ambient temperature in which I had cut the part.  During shipment I believe the package was exposed to sub-zero temperatures and the part simply had not been given time to stabilize at room temperature.

I hope this helps.

5
Chaoticone and Craig,

Thank you very much for your help!


When I purchased the machine I traveled to the city it was located and insisted that the supplier configure my PC to run the machine under Mach3.  He did and that lasted until the PC died last week.

I am glad that you mentioned the standards for writing G-code.  A couple years ago I took a software development class and one of the surprising take-aways was the instructor's strong expression of desirable and undesirable styles of writing code.  I plan on purchasing a text on how to program G-code more professionally (any suggestions?).   I had been using a very brief reference from the supplier of my first CNC machine obtained 16 years ago.  That was a real learning experience (trial by fire) where a large collection of parts arrived and (apparently) their assembly was assumed to be intuitively obvious for any Professional Engineer. That experience was why I demanded a ready to run machine the second time around as I had numerous other tasks in my business demanding my time.

Again, thank you both!

6
No problem, hope you get it sorted soon.

Yes, the jogging "feature" works with the older version of Mach3 while M0 is in effect.  I am not sure what the etiquette or rules are here -- is it possible to upload this old version in case someone else wants to use this "feature"? 

7
Being able to jog while Gcode was active was actually considered a bug and fixed in later versions. This is a perfect example of how a bug for some is considered a feature by others.

If your UC100 plugin will work with the older version using that older version is what you will need to do to take advantage of that bug (feature). Really the proper and industry standard fix would be to edit your Gcode but I can understand not wanting to do that.

Thank you for confirming that.  I have read the discussions about it being undesireable.  I am just trying to be methodical and determine whether what I am experiencing is somehow an artifact of my equipment or software. 

Yesterday I noticed that Yahoo mail was backing up and replacing "K" with "to" although I could copy and paste "K" with no problem.  Then years ago while using Paradox I entered a customer name which promptly crashed the system.  Nice.

8
Hi,
to my knowledge development on Mach3 ceased five years ago, so no it has not been re-written.

The latest build is 066 however many believe it to be buggy and prefer 062.

I rather suspect that there is some setting you are overlooking rather than a change in Mach3. As to what setting, I don't know, I upgraded to Mach4 about 18 months
ago.

Craig

Hi Craig,

Yes, the current version where the jogging does not work is 066.  I used an external sata drive enclosure to examine the version in use five years ago and it is: Version R3.043.022.  It appears to have been bundled with a UC100 controller.  I am using a new UC100 controller with the 066.  Perhaps this is involved.  Can you or another member confirm that you can or cannot jog while an M0 command is in effect with 066 or 062?  What about when you use Mach4?  Thanks!

Edit: I should mention that I believe the original UC100 controller to be genuine (I have the serial number and can provide photos).  I went to pains to assure that the new UC100 controller is genuine.

9
Thank you, Craig.

10
G-Code, CAD, and CAM discussions / Jogging in Mach3 while paused using M0
« on: February 23, 2018, 07:43:18 PM »
Hi,

Thank you in advance for your help.

About 5 years ago I loaded Mach3 into a PC to control a CNC router.  I wrote G code files to control the machine and used M0 to pause the program while the spindle is still running.  I then was able to jog the spindle a safe distance away and secure the pattern that I was cutting with retaining screws. Upon completing this I could resume operating the file and the spindle would automatically travel back to its original location (the coordinates on the line prior to the M0 command).

I had a problem with the motherboard in the old PC and so replaced the computer.  In the meantime I licensed another copy of Mach3.  Now when the program pauses at the M0 command I am unable to jog the spindle. 

Has the Mach3 program been altered in the intervening 5 years to disable the jogging function while the M0 command is active?

I have written at least several hundred G-code programs in the meantime and would like to avoid having to alter all of them to accommodate such a change.

Pages: 1