-
Posts
1,285 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by huskermcdoogle
-
-
Thank you Husker,
so i know i have to edit the post, because there is no way to change it on the controller.
I will try output the b-axis as a parameter like #132.
Than i will set a parameter in the controller on the PFH-4800 #131 to 1.
Than i will set a parameter in the controller on the HCN-5000 #131 to 1000.
So everytime Mastercam is output a rotation ,like for example, 45 degrees
the nc code is
G00 G17 G21 G40 G80 G90
G91 G28 Z0.
T13 T14 M06
G91 G28 Z0.
G28 X0. Y0.
#130=45
#132=#130*#131
G90 G54
B#132
With that i can program both machines with only one post.
What will the PFH do if you command 180000 with no decimal place? Is it a full fourth on the PFH? If it goes to the right place why not just let it ride and use the format for the HCN?
Husker
-
Hello,
i have a problem with our new MAZAK HCN-5000.
It's a Horizontal machine with a index table of 0,001 degrees.
If you like the b-axis to go for example 45 degrees you have to program b45000.
On our older MAZAK PFH-4800 we have a index table of 1 degrees.Here you have to program b45.
The PFH-4800 has the controler 640M and the HCN-5000 the Matrix.
Someone of the MAZAK users can tell me a parameter where i can change the HCN-5000 to program also with b45 ?
Because i don't want to change all my programs and can program both machines with one post on Mastercam.
If there is no way to change a parameter on the machine,
where can i edit the mpmaster to ouput the b-axis with that format of 1000 ?
Thanks
Dreas
As Far as I know you can't change it on the machine. We had the same issue the issue you have is you have the NC positioner, not the nc rotary table. I just changed my post and let it ride. To change the post look at the link to the post I started on practical machinist two years ago. Its just a format statement. Pretty simple fix just don't remember the details off the top of my head.
Post Format Issue - Practical Machinist
Good Luck
Husker
-
When using the Nethasp locally, do I need to do anything in the nethasp.ini file? It finds it with no custom configurations.
Husker
-
Are you running X5? If so, did you install under the default file path locations? (Program Files / Shared mcamx5 / My mcamx5)
Something else to try:
First, make backups of your Configuration File, Keymapping File, and Toolbar States File.
Next, delete the existing copies. Then start Mastercam. Mastercam will generate new 'Default' files. If this fixes the lag issue, then you'll need to dump your old files and modify the new ones to your preferences.
So I went through and did that latter items you have described in your last posts. Absolutely no change. Still slow for that. Mind you that is the only slow thing other than saving a 80Mb file.... Just right clicking in the operation manager that is. Right clicking in the graphics screen is the normal instant response.
As for the computer, Dell Precision T3500, 2.8ghz Xeon 64bit WIN7, 6GB ram, unfortunately it is an ATI card, but doesn't seem to have any trouble(Firepro V4800). I wasn't having this problem for the first year of operation using X4 then I switched to X5 everything was cool for a month or so, now the right click in operations manager is slow. The only thing that has changed since the upgrade to X5MU1 was going from a regular hasp to a nethasp, and come to think of it things changed about the same time. I have the same issue in X4MU3
As for my nethasp setup. I am currently set up using it locally (same config as the other computer that I had trouble with this in the past). The other computer that I have setup using MCam on the Nethasp as no lag issues with the right click menu in the operations manager.
Does the machine validate the hasp every time you right click in the ops manager screen?
Thanks,
Husker
-
Husker/Sled,
Where are your Temp files being written? Check in the Configuration file, in the Files Tab. Look at 'Temporary files root'.
There is a check box below the 'Data paths' section that has an option: 'Use Windows Temp Directory'. Is this checked?
If it is checked, I would expect your path to look like C:\Users\*your user name*\APPDATA\LOCAL\TEMP\mastercam
With Mastercam closed, try navigating to that folder and deleting any folders listed inside the ...\TEMP\mastercam folder.
Something else you can try is running 'RAM-Saver' on your file. See if that clears out a bunch of data or not. Are you Keymapping or Toolbar files located on the Network? IF SO, try saving them locally and setting your configuration file to point there.
Does your IT Department run any kind of security on the servers or network being used?
After clearing out the Temporary Files, try setting all your files to be read locally from your C: Drive. (This is just a test to see if the Network is responsible for the problem, or if it is Mastercam). If you are still experiencing issues, a re-installation may help.
Hope that helps,
Did everything here, though none of my files are being read from the network. There were only a few temporary files in the users local... folder.
No improvement.
Any other ideas? What about the hasp?
Husker
-
Don't see anything going on when I right click. Beyond Stumped on this one. I was thinking about uninstalling and re-installing, because this is getting old while creating new programs.... Slows the the rhythm way down. Nobody from the resellers/dealers that have customers experiencing this. Could it have to do with running a nethasp locally?
Because that is the only commonality I can think of between this mcam system and the last one I had this trouble with.
Any easy way to test this nethasp theory.
Husker
-
Yeah I ended up figuring out that that feature was useful when I was doing a lot of multi-part transform operations with a single tool. Combine 4 or five operations, (contours, drill ops...), then transform the group onto the next part with a retract and approach in between the parts. Comes in very useful. It is nice for operators proving out new parts too, breaks up the code a little more.
Husker
-
Wow cool thanks... worked perfect..Ref points... never used them..That was easy..
Not a problem. Its nice when you can get good answer on the forums isn't it. Now if I can just solve my own problems.......
-
Use two operations set your retract and clearance planes inside the hole/pocket then use reference points to get the tool into and out of the hole.
I attached a picture and also a link to a mcx file to look at.
Is this basically what you are trying to do?
http://dl.dropbox.com/u/29828272/Example.png
File Link
Husker
-
I am getting a radius error with some code on a od turn profile. Can you guys help me out with this?
I am using a number 1 insert radius. I have .015 in cor comp, and 3 for the od turn profile.
G0 T0202
G96 S350 M3
G41 G0 Z2.605
X1.2
G1 X1. F.015
X0.
G40 X.1414 Z2.6757
G0 G42 X.6508
Z2.7004
G1 Z2.6004 F.007
X.7185 Z2.5666
G3 X.798 Z2.4707 R.1356
G1 Z2.0494
G2 X.8667 Z2.015 R.0343
G1 X.8837
G3 X.9058 Z2.0104 R.0157
G1 X.9908 Z1.9679
G3 X1. Z1.9569 R.0156
G1 Z1.4069
(Program stops here)
G3 X.9908 Z1.3958 R.0156
G1 X.915 Z1.3579
Z1.35
X.9687
G3 X1. Z1.3343 R.0157
G1 Z.8344
G3 X.9892 Z.8226 R.0156
G1 X.875 Z.7729
Z.6444
G3 X.8658 Z.6333 R.0156
G1 X.755 Z.5779
Z.45
G40 X.8964 Z.5207
G0 X1.064
G53 X0.
G53 Z-5.
Jason
Use I J K not R. Math errors will go away because the control will calculate the radius.
Husker
-
after manul entry
on post
n$, "M30", e$
comment$
mergesub$
clearsub$
mergeaux$
clearaux$
"%", e$
this will give after m3o the comments on manual entry codes
This sparked a good way to do it.... I have figured it out and added it into my post.
Basically you need to do the following things.
Define the variable "peofid" in the variable initialization section.
Then change the following sections:
Original:
peof$ #End of file for non-zero tool phsm_off pbld, n$, "M09", e$ pbld, n$, "M89", e$ pbld, n$, "G91 G30", "Z0.", e$ pbld, n$, "G30", "X0.", "Y0.", e$ if lock_codes = one & rot_on_x, pbld, n$, *sunlock, sunlockcomm, e$ rotretflg = 1 pbld, n$, "G91", *sg28, protretinc, e$ rotretflg = 0 if lock_codes = one & rot_on_x, pbld, n$, *slock, slockcomm, e$ comment$ if not(index), n$, *sg90, e$ n$, "M30", e$ mergesub$ clearsub$ mergeaux$ clearaux$ "%", e$
add the "peofid = 1"
add "comment$" after the M30 and comment out the original "comment$
Modified:
peof$ #End of file for non-zero tool phsm_off peofid = 1 pbld, n$, "M09", e$ pbld, n$, "M89", e$ pbld, n$, "G91 G30", "Z0.", e$ pbld, n$, "G30", "X0.", "Y0.", e$ if lock_codes = one & rot_on_x, pbld, n$, *sunlock, sunlockcomm, e$ rotretflg = 1 pbld, n$, "G91", *sg28, protretinc, e$ rotretflg = 0 if lock_codes = one & rot_on_x, pbld, n$, *slock, slockcomm, e$ #comment$ if not(index), n$, *sg90, e$ n$, "M30", e$ comment$ mergesub$ clearsub$ mergeaux$ clearaux$ "%", e$
Then change the following line in the manual entry section.
From:
if gcode$ = 1006, n$, pspc, scomm$, e$
To:
if gcode$ = 1006, [ if peofid = 1, [ " ", e$ " ", e$ n$, pspc, scomm$, e$ peofid = 0 ] else, n$, pspc, scomm$, e$ ]
Good luck to anyone that may want to to do this.
Thanks Everyone,
Husker
-
nobody else other than sledgeek and myself are experiencing this?
-
-
hmm... maybe do it by a misc. integer?
This would go in your peof$ section:
If mi10 = one, n$, "CODE HERE", e$
Yeah I thought about that, but the problem I have is that the Manual Entry is an operation itself, so it won't do the EOF yet, and I can't edit my probing into my post, that wouldn't make any sense at all.
Husker
-
You could use manual entry to output code. If it is a common file that you will use regularly write it in the editor and save it as a text file. When you open the manual entry set the source to "use text file" then go select it.
You'll want to set the NCI output as code, if you need any comments to be output you should have those in parenthesis when you save the text file.
I use manual entry from time to time, but it won't insert it at the right place. It needs to be after my safe retract and pallet change prep M30 BS.
Husker
-
I don't know about getting it after the M30, but you could always put an M30 at the start of your file.
Not a clean way to do it. Then you would have some oddball code and some weird errors when it gets to your true end of file statements.
-
Guys,
We have an FMS, and probe about 80% of the parts we run in it (Flimsy Aluminum Casting Work). Anyway, I hate editing code and do as little as possible, but one things that I always do is write all of my probing cycles by hand because there is hardly a single part that is cut and dry simple probing. I have heard and seen people use custom drill cycles to do probing, but have no interest in that, seems too cumbersome. Anyway, the way our system handles file transfer is to just bring in the programs(one file) and work offsets(single g10 file), then it calls the offset program and then calls the workpiece program. So what I end up doing is I toss the probing subroutine in the end of the program file after the M30 and all is cool, it gets into the control anyway. I then use a subprogram call (drill cycle) to put the probe in the spindle and call the length offset, then call my probing sub.
Long Story Short.
Is there a way to use Manual Entry to toss a chunk of code after the M30 so I don't have to paste in my sub after posting?
Thanks,
Nick
-
is there anything added to the Windows default right click menu? Like a 3rd party when you right click and select "Open With"?
No
-
Oh and both x4 and x5 do it now. Same time delay.
-
File size in this case doesn't make a difference. I have had files that make it slow, but that takes well over 100 operations before that happens. Saving is also a PITA in this case. I routinely have files over 100MB, they take a while but file size doesn't seem to slow things down, just the number of operations / the size of the operation data. Main thing is a blank file takes forever. If I shut off my antivirus, it makes no difference. Anyone else?
Husker
-
Had the same issue on an old yasnac mx3, just caught it before it crashed. No alarm, just skipped ahead, no hesitation, lots of head scratching as a result. I kept just restarting the program from the right place, had no idea what it was until I had stared at the code for a day or so.... Then it hit me like a truck, felt pretty stupid. But in that case I found the problem during prove-out, and didn't let it run without me restarting at that point because it was not so kosher. Sorry to hear you had some bad unexpected results.
Husker
-
Hey guys,
When I right click in the operation manager I get a very slow response. This has been a problem for me with other computers in the past, with x2 ,x3 and x4. This current computer was fine with x4 and x5, never had a problem but now all of a sudden it has a huge lag when I right click. This is obnoxious because now it takes 3 seconds each time for me to wait for the menu to come up. Anyone else experience this? Nothing has seemed to change with the computer, everything else processes fine and snappy.
Thanks,
Husker
-
Guys,
When I use a dwell value in the G81/G82 drill cycle in the MPMaster Post / MDef I get the proper output for that particular cycle, but every other drill cycle(g81) will then end up with a P0 on the second line... May of just answered my own questions here... Yup, I did, just had to use my brain...
For those that might be interested and searching in the future... You need to modify the following line, replace dwell$ with the portion underlined. Now my question at this point would be how to make the dwell portion modal, and not call it on subsequent points, unless it changes, this much I think is outside of my post modding knowledge. Help on this subject would be appreciated.
Is this what the ! is for instead of the * to force?
pdrill_2$ #Canned Drill Cycle, additional points
pdrlcommonb
pcan1, pbld, n$, pdrlxy, pzout, pcout, pindexdrl, prdrlout, [if dwell$, dwell$],
feed, strcantext, e$
pcom_move
Peace Folks
Husker
-
"IS the feed value of 20 correct? multiplying by -1 will only change the sign which is fine if the value itself is correct. what is fr$ formatted for? fs and fmt assignments are what I am taking about. "
No 20 isn't the feedrate he programmed, 20 would actually be a programmed feed of 2ipm. -20 is what was is posted out by default or some such thing, I fought and fought this issue and got nowhere with it.
Husker
Cell macro serialization
in Machining, Tools, Cutting & Probing
Posted
Did you get this figured out?