timlockert

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

Having replaced all components on the hardware feedback side, all evidence points to a failure of the stepper setup phantom axis to sustain ongoing position following. Any ideas why this would occur?

Will PEWin32 Pro2 Suite load in successfully on a Windows 8 platform? Tim

I have a three color offset printer application in which three axis are mastered to a phantom axis and the phantom axis is mastered to an aux axis feedback channel which is driven by an idler roller which tracks the paper as it passes through the machine. Intermittently, the whole system comes to an abrupt stop in a fashion that suggests the motors are being driven to zero speed, as opposed to coasting. The sudden stop damages the press plates. Mtr 1-3 Parker motors with GPH 30/60 Amps Mtr 4 phantom axis using stepper electronic feedback Mtr 6 aux axis This is a Turbo PMAC2 VME frimware version 1.938, with Sick/Stegmann absolute encoders and ACC51P Opt2 for all four channels. A fault on Mtr 1-3 generates a kill command that allows the rolls to coast and not damage the plates. A loss of feedback on Axis 6, with all other axis following, would step command the motors to zero speed, causing this proglem. I am in process of replacing the ACC51P and all cables and encoders to mtr 6. This problem would also be created if the phantom axis were to suddenly drop to zero speed. This occurred three years ago when the system was upgraded to the current processor. The original code was written using an integrated output feedback method that was not backwardly compatible with the current firmware version. The code was rewritten using the stepper method for phantom axis generation. The problem went away for about 18 months then reappeared with higher frequency. What possible causes are there for a stepper method phantom axis to suddenly stop when setup for position following of an aux. encoder?

Thanks, that is what I thought, though the manual specifically refers to Sigma 3. The presumption is that Sigma 3 and Sigma 5, 20 bit serial encoders, are identical, which is reasonable but not certain. Because the Sigma 5 is a popular series for use with our GEO Brick, perhaps a release would be in order.

Does the Geo Brick Opt 4C2 support the 20 bit serial feedback provided with Yaskawa Sigma 5 motors?

Were I to download all of the training PPT files, In what order would you suggest I view them?

[quote='Sina' pid='664' dateline='1282854538'] Tim, #1: Yes. As soon as you have servo counts, it means that the Gates are up and running and it would be OK to power up the encoders and the gate will detect the auto cycle of hall data on C channel input. #2: Your settings are correct for I7015, I7025 and I7035. #3: The address settings for Ix83s are correct. #4: Yaskawa motors/hall sensors are aligned properly so you would end up with the same settings for Ixx91 every time. However, you have a point about the fact that you can not change the location of the motor since you wouldn't get the halls updated (I'm not sure about this and since I don't have such an encoder here to test, I can't be 100% confident about it. I believe the encoder actually transmits the hall sensor states as the encoder moves after power up in which case you just follow the steps described in Turbo User Manual for determining the correct value for Ixx91) So now it would be a question for you: When you power on the encoder after the controller is up and running and encoder cycles through the quadrature states, registering its hall states to the gate, does it keep on multiplexing the hall states and index pulse in the C-channel? You can test this by looking at suggested Mx28 of each channel while you rotate the motor shaft. [/quote][hr] Thanks Sina, I'll let you know what I find out. When I determine correct value for Ix91 for these motors I'll send that along too. The Automation Direct line is popular around here so a good setup will be usefull.

It appears as if the Automation Direct Line of SVM & SVL motors use Yaskawa Sigma 1 feedback devices. We have these on a GEO Brick 3 axis application with NC Pro2 software. I need a little help with the Hall Effect first phase finding setup. #1 Delay 5VDC encoder power on until some period after TPMAC2 power on. Does 10 servo updates sound good before $$? #2 I7015, I7025, I2035 all set to 2 for DeMux Gate control #3 Motor X Power-On Phase Position Address I181=X:$78000 (UVW bits will show up in bits 0-2 of status word) I281=X:$78008 I381=X:$78010 #4 Motor X Power-On Phase Position Format Ixx91 ????? My apparent problem here is that the motor cannot be turned to read ongoing hall states. How do you determine the proper UVW phase reference and associated value of Ixx91? Trial and Error? Does the Yaskawa device have an accurately registered Hall State that can be entered?