Hello Guest it is April 19, 2024, 11:58:21 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 - panaceabeachbum

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 »
31
still not working as expected , will oonly drill to a depth of 1.6" max

32
yes I updated with the macro you posted and it was still doing the same thing , but now that I think about it I have not rebooted since so maybe its just not loaded the new macro, I tend to leave the machine on for days at a time and just turn the servo amps off at night . wouldnt be the first time I have overlooked something basic

33
Good point Rich, I did probably post my observations in the wrong section , they just popped into my mind while typing my g83 question and I thought I would share them. I am in no way trying to find any faults with mach or the wizards .  I also wasnt refering to anyone thats posted openly with my other comment, but was responding to a couple of very nasty emails blasting me for pointing out something that I thought was a conerstone of basic geometry , the decimal point.

Hood I still cant get g83 to drill to the proper depths, anything I try under 1" drills to the proper depth but when I call out a depth over 1." it drills to some depth short of that dimension .

Could you zero your machine back some safe distance from the chuck and run a peck drill cycle something like g83 q.o5 z-2.2 f4.00 r.2  and watch your dro and see if it actualy drills to the full 2.2" ? On my machine this will drill to 1.6" depth perfectly but not the 2.2"  No hurry just curious if I am the only one having this problem  . I dont seem to have any problem if I keep the pecks (q) to .1" or greater or the total depth to 1" or less but the above string just seems to be problamatic

34
thanks , I have been copying and pasting the entire macro folder when updating , instead of just copying the oiler and tool changer macro . Thanks again , will update and give it a whirl

35
no big deal on the decimal point thing , if this were my project I would welcome constructive advice on how to better things, I get the impression that alot of folks would rather get defensive and explain things away than be open minded and consider another viewpoint  , my apologies for even bringing it up.

Back on the g83 subject I attached the file you mentioned , maybe its something simple . Thanks for offering to take a look.


36
Oh forgot to say,did you mean  to put G84 in the above example?
Hood

oops meant to put g83 for peck drilling

37
I dont think there is a universal std your correct , maybe i should rephrase to say that its pretty much an accepted practice that all numerals that are not comands (g4, g1, m* etc) have a decimal place in them and that some of the Mach wizards generate coordinates and feedrates that do not have decimal places.
If it was only the HAAS that had a problem with this it might be easy to say the problem is theirs , but since all the commercialy avail controllers (that I have) have problems with the lack of decimal points and all the cam software i have ever used puts decimal points in all coordinates and feed rates I would say its pretty much an accepted std here in the US.

I realize there are pre and post processors that are machine specific , but they in no way are intended to (or have the ability to) go thru code and look for missing decimal places. I also am not familiar with any gcode editors with this ability either.

I am in no way knocking Mach or the wizards, I recently read a post by Brian in which he mentioned cleaning up g28 to operate more like the excepted std so i assumed there was a desire to move as close to the center of the "std" way of doing things in the cnc world.

Generating huge strings of code where some coordinates have decimal points and some dont just seemed like an issue to me .   I have been a long term user of a number of cam programs and have been operating commercial cnc equipment for 20 years and its common place to use decimal points in all coordinates and feed rates .

As I pointed out in my initial post no its not a problem if your runnig the files in Mach as I am sure 99.99% of the members here are , I am just pointing this out in an attempt to better a great product , nothing more.  I know another user of mach that generates cut files for his plasma table to protype parts and then takes the code to another shop with a large commercial machine to cut thousands of parts who has also had the same issue.

38
youll get the hang of it , like most canned cycles once you figure out what each of the variables are you'll just starting writing the code manualy. now if we could just get a couple of other common canned lathe cycles active ;)

39
I have been using my big lathe quite a bit with mach this week . I have upgraded from an earlier version of mach and installed a smooth stepper at the same time so i am not sure which one is causing the problem . When i peck drill I cant get the depths called out .  G84 q.1 z-2.5  f1.00 r.1 only drills to a depth of 1.6"   I have run a number of drill files that were drilling to the proper depths before the upgrades that will not drill to the proper depth now
Machine moves the proper distance in all other functions.

I have noticed a couple of other things, that while they dont cause problems in Mach , are not std and do cause problems in other commercial cnc controllers. Just observations so please dont take ay of this the wrong way .
I am running Yasnac mx3 , milltronics cent7, sinumerik 802c and the latest thin controller from HAAS .

Some of the Mach wizards generate coordinates that are 5 decimal places , the haas controller, sinumerik and the Yasnac on mazaks and other eguip will only accept numbers to 4 places or they fault .

all the wizards seem to generate coordinates that sometimes do not have a decimal point if they fall on a whole number x1 , y3 etc . All  of the commercial controllers I am running have problems with any numbers that dont have decimal points .
quite often feed rates are generated with out a decimal point , same problem as above.

I realize 99% of the time files generated are run only in mach and all the wizard were/are written with this in mind , I am only pointing these things out as I am guessing the goal is to make everything as close to std gcode/programing as possible and the decimal point thing seems to cause problems on a number of machines


40
I have the same issue when generating files for my little 9x20, its just moving to a safe place to do a tool change if memory serves.  you just need to open the file in the editor and delete the g53 line  then save the file.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 »