Del, Drop me a zip2go of the file you're posting from And I'd be happy to take a look and walk you through the changes you want to make. Hope all is well there at Royster's Thanks,

Awesome. Thanks Dave.

Does anyone know if I can add the selected compensation type and direction to the header and tool changes? I figure there's got to be a string somewhere with that data in it.

You can also look at the NC file size listed just beneath the toolpath in your operations manager. If a toolpath has been created, the file should at least be more than 1k. Typically, .8K is what I see on an empty toolpath. If you have a signifigant toolpath size, but still don't see it, regenerate the path and see if the pocket toolpath flashes but disappears. If it does, you've got the visibility turned off on that path.

Jeff, Try turning off infinite look ahead in your toolpath parameters, That will show you if your problem is comp VS. contour related. If you like, feel free to e-mail me the file and I'll gladly look at it for you.

SnagIt works really well, too.

quote: In X2 math functions are back also... Yay! I hadn't checked that yet.

C Beack, You've got mail. Hope it helps.

A customer of ours first noticed the problem, it's not a terribly bad thing, it just takes longer. Just seeing if anyone else noticed this and if anyone has any ideas for getting around it.

Is anyone else seeing this? X Mill, Xmr1 Mill, Xmr2 Mill, All do this V9 Does not. Create a simple 2-d contour, like a rectangle Assign a 2-d contour at a depth of -1" abs. and a feedplane of .1" inc. do not use depth cuts. Before rapid to retract pt. there's a feed move to Z-.9" Now turn on depth cuts and repost. Anything different? I get the exact same nc file with the exception that the z move is to z.1" am I missing something?

this problem is occurring on 2 sepatare PC's, and it is consistent, the menu is simply not there. so odd. it wouldn't appear to be memory related, but I could be wrong.

(Hope it's not too late for a V9.1 question:) Can anyone tell me why V9.1 sp2 router would fail to have an allocations tab in the screen>config menu?

Yeah, there's quite a bit going on right now. Seriously, though, I don't have as much time to monitor the forum now, but I still take customer calls so if you're having trouble with anything, feel free to buzz me. It's hard to help on the forum, all the really experienced guys beat me to the punch! of course, That's why the forum is great. Good to see you're using it, Del. Take care.

A while back, some were talking about having problems with surface rough pocket giving wierd arc moves at the machine. Milltronics trouble thread Anyway, I have a customer who shared the same troubler this morning, and actually called milltronics on it. It appears now as if his trouble was caused by the trig help function in the control (centurion 7), which was generating the arc moves. Turning it off at the beginning of a program (PB81=2) fixed the problem, and you can turn off the cancel at the end of a program (PB81=0) Inserting these two solved his problem, justr thought anyone might like to know.

From the former... Agie Thread Still having problems with this machine. The txt File below is an output from the current post, which appears correct The file is for a 10 MM circle, threaded at 0,0 (the center of the arc) and chained from the vertical quadrant. 1mm tab, one rough with tab cut. No comp. %N000 D01 P01 T01 G43 N001 G03 X+005000 Y-005000 J-005000G44 N002 G01 X+000000 Y+005000G40 N003 G03 X-004007 Y+004900 I-005000G44 N004 G03 X-000993 Y+000100 I-000993 J-004900G44 /N005G40M00 N006 G01 X-001000 N007 G01 X+000000 Y-005000G40 N008G45M21M02 After the Tab, the machine should return to 0,0. What the machine is doing is moving to x 000100 and y-000008 at first look, I believed the machine was ignoring line n004 but the machine does cut that arc. Is this a comp issue and how is comp assigned and cancelled within this old agiecode? If not, what could it be?

Me three.

So all three files are downloaded to the machine?

What are the SBL and SBR files used for?

Thanks very much, Guys. Roger, I'm using the generic agie from MR2 with this, is this the latest version available? I can get with the post dept. if not. Thanks Again,

Can anyone tell me how the excellence evolution for Agie classic works? I'm looking at an SBL file generated when posting and I'm not seeing Gcode. Is this supposed to be this way? I am familiar with the older agie machines but this is all greek to me thus far. any help would be appreciated. Thanks,

Gord, Runaway is a common problem that usually occurs in a servo system that has lost encoder feedback. the problem results when the optical encoder's feedback is lost at the controller. As a result, the machine keeps applying more and more power to the axis to drive it to the correct location. This would usually keep occuring until the machine hits an overrun or faults the servo drive. Problems like this can be caused by any number of issues ranging from breaks in the encoder wires to faulty encoders to bad boards, and so, they are often difficult to locate when in a no different situation. One thing that may help is to note how many axes are running away. If it's more than the z, it is more likely a board

Mowens, You may want to get a copy of the V9 post reference guide from your reseller, if you haven't already. If you have, there's a pretty clear table in there showing you the NCI codes and parameters. It's in the Volume 3 under "the NCI file". I use it all the time. HTH,

shouldn't. However, when updating the hasp with new codes(i.e. maintenance or perm codes) that has to be done at the pc to which the hasp is connected. In addition, If your net hasp server is running on a separate PC from the one the hasp is connected to it will likely give you some trouble. However, it's been my experience that as long as you can read the hasp the first time, it usually sticks unless something changes, like an update for security, or the IP of the server.

sorry, the mori is an NL 1500 with a mits control.

check your network, if communications drop out for the right second it should tell you that the sim has become disconnected. Not to steer this post or anything, but it brings the question of whether or not you can change the timeout value used when mcam looks for the nethasp. I've often wondered about this. You also may have a non-static IP at your PC where the nethasp is located, if so, your IP address could change and when it does (if you have setup a static IP in the nethasp.ini file) you would have to remove the call to a specific IP from the .ini. I would look into that possibility as well.