cncguru
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Downloads
Posts posted by cncguru
-
-
I believe there is an app note for the ECC203 & SL-3300 that was written by Mike Esposito. There was a lot of time and effort utilized to get that working properly and consistently, but it has been stable ever since. They are running together on about 25 machines at OEM and more added every week.
-
Has there been success or testing with the KEB Automation drive products? Fought with there F6K drive, sent back for testing(nothing wrong), and OEM gave up on product. The F6K would power-up ok and the ECat LED's would come to life like normal until CK3E would attempt to enable ECat then drive ECat LED would go red and the slave could be seen during an "ecat reset" but never goes to PreOp state. The CK3E error is $98110024. One note about the KEB drives: They don't have the ability to set address through hardware, it bases its address on where its plugged in the chain.
-
Don't forget to Incremental Arc Center vs Absolute Arc Center. You don't have G90.1 or G91.1 defined in Program 1000.
-
With PVT mode your program has to be written to control the blend at such a transition acc/dec and velocity. This can be "fun" (sarcasm) at a direct reversal since you want to bring velocity to zero then back up to desired velocity. Therefore the block at reversal brings velocity to Zero and the next block set velocity back to desired velocity. Now acc/dec may need modification as well through the transition.
As Dave mentioned LINEAR with Lookahead active makes this very simple since the velocity Ixx16 and acc/dec limits Ixx17 are active and firmware prevents exceeding them through all moves of the program.
In PVT mode, observing the acceleration and velocity limits are the responsibility of the programmer, unlike in Linear blended mode.
You may find that letting Pmac do more control of the trajectories is easier than PVT.
See this example from the Turbo User manual:
SPLINE1 TM20
P1=0
WHILE (P1<10)
P2=0
WHILE (P2<359)
X(P1*SIN(P2))
P2=P2+1
ENDWHILE
X(P1*SIN(P2))
P1=P1+1
ENDWHILE
If you change the first line to LINEAR mode, then Pmac will observe acceleration and velocity limits while creating the overall trajectory.
'Not sure if this is exactly what you want, but something to consider.
-
Unfortunately I don't get on here enough or I could have easily directed you on this. I use a PLC dedicated to switching between Kinematic(I)/Tool Point vs Joint Mode(XYZAB) which works very well. Another note on tool point in NCPro2 is you must use G43.1 H# and then add/subtract offset in the kinematics routine. The G43 H# will manipulate the parsed positions based on the offsets which if you are not aware of this it will drive you nuts trying to find out why it works testing directly in Pmac, but not from NcPro2.
-
Also of note – when you abort a PVT sequence in progress PMAC will decelerate to a stop. If the jog move starts before this occurs PMAC will use the current velocity, acceleration and jerk for the starting point of the jog move. You may want to verify that the stop is complete - not just that the program is complete.
In your logic around the start of the jog command I would wait for inposition and desired velocity zero after the ABORT before starting the jog. This plays into what Steve mentioned above. I have had the issue you describe only the resulting profile was a lot worse. It has to be a timing issue since it only happens 1 in 500 times.
-
That would have been my first thought is Spindle At Speed. You can also use G25/26 for testing this type of thing. Spindle Speed Detect ON & OFF. I have run into this more time than I can count. Does this machine use encoder feedback to determine speed or the analog feedback? Also note that the yellow bar sometimes gets out of sink especially while mcodes are executing & McodeAtFront registry settings also play a part.
After intensive trouble shooting it is determined that the hang up is associated only with M3, spindle on, and the spindle at speed signal.
It's hot in southern Louisiana in July!
Tim Lockert
I have UMAC with Adv900, TPMAC2, ACC24E2A 4x, ACC65E. A pretty straightforward retrofit of an Eagle mill. The program code uses M98 with three different file calls, one to setup and start coolant, one to perform repetitive drilling cycles, and one to end the cycle. Here is a code snippet:
N1 M98(c:\cnc\startnc.nc)L1
N2 X-0.3177 Y-8.0255
N3 M98(c:\cnc\drillnc.nc)L1
N4 X-0.3177 Y-6.0255
N5 M98(c:\cnc\drillnc.nc)L1
N6 X-0.3177 Y-4.0255
The program loads the first called program startnc.nc, that looks like this:
N05 G90 G17 G20
N10 M8
N15 M3 S100
N20 G0 G53 Z-0.5
N21 G0 G54 X0 Y0
N23 G0 Z.500
N25 M8
N30 M1
N35 M99
The program hangs with the yellow highlight at the top line. The M8 coolant on executes (turns on). NC shows N10000 as current line. The Buff is Open, in Auto, and CS Status shows Program running, federate at 50%. G90 G17 G20 show active If I load Startnc.nc directly, the same thing happens.
With drillnc.nc the program looks like this:
/M8
M3 S1500
G0 Z0.250
G1 Z-2.120 F3.0
G0 Z0.250
M99
This progam, if loaded directly, does the same thing. If M8 is starting line it executes coolant on and hangs. If M8 is deleted, M3, S1500 line runs (spindle comes to speed) and the program hangs, top line yellow highlighted, as described above.
If the M3 S1500 line is deleted. The G code motion lines executed completely to the end.
The really odd thing is that there are two machines at this site, one machine will run these exactly copied programs without problem. The one I am working on does not seem able to return from the Prog1001 Mcode call.
Any ideas?
Tim Lockert
-
NCpro 5.2 running on Win7.
Everything seems to work but the program rewind button.
Is this button handled through a PLC or is it handled from within the
front end Nc program?
If it is handled through a plc, which one, were?
Can program rewind be activated from a plc if I want to have some
event cause a rewind?
Mark
This is handled in the Reset PLC. The rewind section is towards the end.
-
All of the M-Variables used in the Advantage 900 system are in the header files. Adv900.h, Address.h, Oem.h, and a End User Specific header file "YourMachine"_UserDefines.h. These do not match the suggested M-Variables at the end of the Software Reference Manual so be careful with that. This is also the names used through out the GMT Files and the Standard Plc's & Pmc's.
-
There is a way to change the functionality of the buttons with Designer, but I think you want columns added for instance Geometric Tool Offsets vs Tool Z Length vs Cut Comp and Wear. Now the registry can be modify to display and make use of additional columns. You can add the geometric for XY for sure, but if you want additional buttons they would need to be added with Designer.
Example: These 2 entries control what gets displayed in the Tools Page.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PMAC\Device0\Nc0\NCUI 32\Tool Offsets]
"toolOfsAxis"="ZZWWRR"
"toolOfsAxisType"="010147"
Z Axis - ZZ -> 0=Geometry 1=Wear
W Axis - WW -> 0=Geometry 1=Wear
Cut Comp - RR -> 4=Diameter/Radius 7=Wear
Example 2: Spindle w 90 degree 23 (12 X & 12 Y) head multi-drill common drill point in corner offset from spindle center line. Common drill point entered as a Geometric Tool Offset on the Tools page.
The OFFSET pages has all the axis buttons defined and those get turned ON/OFF with the registry also though there is one slight issue with the order that can be confusing, but easy to work around.
Is it possible to modify the functionality of the SetX and SetZ button page in the Lathe code? The UI in the Lathe has an input cell for the diameter of the tool set location (analogous to the block height for the mill code) from which the tool offset is calculated. Is it possible to add a cell for the Z height of the tool set location as well? Rarely do necessarily want the tool set station location to be Z0. This would be equivalent to having both Diameter and Block Height as input variables on the UI. The most generalized solution of course would be to allow the operator to enter the set station offset in each coordinate that is active (five offsets for a five axis machine, etc.)
I am assuming the answer is no, so does anyone else have any nice solution to this problem?
-
Yes I have run NCPro2 on Windows 7. Main thing is the correct driver must loaded. The signed driver may not be part of the NC download yet. If not you have to download the latest PeWinPro2 and install over the top of NC so the signed driver is available and then it worked fine. It has been very stable in a production environment so far.
-
OK,1000 blocks/sec,that's great!
But what kind of communication can do so fast? Is't USB? Does Ethernet Can do so fast? And what's about PCI or ISA,how much blocks they can reach? I mean if i had make the feedrate at 400% or more higher.
Thanks
The USB typically max throughput is 600-800 blocks per sec. For high block throughput PCI is best. You can get higher than 1000 blocks per sec but you may have to play with clock settings to go faster than that. DNC should not be required if buffers are setup correctly. The program would have to be bigger than you PC hard drive for this to be an issue. I have customers running programs over 100MB, but searching for mid program starts can be painful do to search speed. Careful with parametrics when using large programs also.
The trouble of ppnc's workoffsets
in Power PMAC
Posted
Well this is actually an array issue and not an issue at all once you understand the system. The edits to make this work are on the ppmac side not the HMI side. The file ncinterfacedefinitions.pmh is where the edits take place then all will be write with the world.
The axis order has everything to do with how the edits take place. I have run into this many times and very easy to correct.