[Power PMAC wont recognize an ACC-11E in the IDE]

Worked great Thank you

one documentation thing that was a little confusing in the documentation

GateIo[i].PartType = 8  (This worked)

the manual says:

GateIo[i].PartType contains an integer representing the type(s) of hardware interface of the board containing the IOGATE ASIC. It is derived from an identification IC associated with the ASIC, which is read automatically at power-up/reset. It reports as “nan” (not-a-number) if no ASIC with this index is present. Each bit specifies one type of interface that could be present. The bit is set if that type of interface is present with the IC. It is possible that multiple interface types could be present.

Bit 0 (value 1): Servo 

Bit 1 (value 2): MACRO 

Bit 2 (value 4): Digital I/O 

Bit 3 (value 8): Analog I/O

I would have thought this was a Digital I/O as opposed to Analog I/O.  

 

[Power PMAC wont recognize an ACC-11E in the IDE]

I am trying add an acc-11e I/O board to my Power Pmac Umac style Rack.  When  I install  the acc-11e it is not recognized by the system even after $$$***.  I tried with an ACC-65E picked up perfectly but the ACC11e was not recognized.

using   the current version  of the power PMAC IDE

Any Thoughts?  

[Using T variable in motion program]

it is possible to use the READ command to send parameters to subroutines.  For example  G04 X10.5 can be used to create a Dwell by creating a program 1000 with a line 4000.  G04 in the main program jumps to the that subprogram line then using a READ(X) command that will assign D27=10.5 then do a DWELL(D27*1000) to create a 10.5 second dwell.   This is Great but I want to use a T value but the default function  of T is to call subprogram 1004.  This works OK when you are using T to define a Tool Pocket but not so well when T defines a Tool Number between 1-999. It is not practical to create a subprogram with entries for all 1000 possible tool numbers when practically only 10-20 of them will ever be used.

  Long windup to ask the question, is it possible to use the READ(T) command to get a value from a program line like   T183G06?  I want to use G06 to command the Tool Change and extract the 187 and use it to look up the Tool Length and the Pocket that stores Tool Number 187.   I have not had success trying this.  

 

[M Variable usage]

Ok that makes scene, so no problem using the self defined M variables for general use. What about when I want to compile the PLC. Do I need to do anything special? Would my PLC's execute faster if I some how forced them to be 24 bit?

Thanks

[M Variable usage]

This should be a simple one. Using a TurboPMAC you can "undefine" an M variable like this:

M100->*

I can still assign a value to M100 , I assume a 24bit Integer? and use it in my programs. It works fine.

In looking through the manual there is a section that talks about making additional timers and it says I need to assign my M variable to "An open memory location"

 

From the User Manual:

If more timers are needed, use memory address X:$0. This 24-bit register counts up once per servo cycle.

Store a starting value for this, then each scan subtract the starting value from the current value and

compare the difference to the amount of time to wait. By subtracting into another 24-bit register, possible

rollover of X:$0 is handled gracefully.

Define the following M-variables with on-line commands:

M0->X:$0,24 ; Servo counter register

M85->X:$0010F0,24 ; Free 24-bit register <=====

M86->X:$0010F1,24 ; Free 24-bit register <=====

Then write as part of the PLC program:

M85=M0 ; Start of timer

M86=M0-M85 ; Time elapsed so far

WHILE (M86

M86=M0-M85 ; Time elapsed so far

ENDWHILE ; Exit PLC program here when

 

Here is the question,why do I need the 2 marked steps, why can't I just use

M85->*

M86->*

 

The reason I ask is that I normally just find an unused M variable then do the

Mnnnn->* and use it like a P variable. After reading this in the manual I am afraid I am going to get into trouble doing what I am doing.

[Axis Hardware Failure?]

The specification for the Umac is 130F I assume that is ambient in the panel. My panel ambient is about 85F. i Just put a thermocouple on the rack and measured about 130F. The panel doors are open so air flow is reasonable. I have a cooler that comes on at 90F and it is NOT on.

[Why is "DISABLE PLC" not working as expected?]

just had the same problem

add a space between PLC and the number

Disable PLC 3 not Disable PLC3

[Axis Hardware Failure?]

I am using a new Umac the rack is relatively full. 3 Digital I/O cards, 2 4axis analog cards, an analog I/O card and a serial absolute encoder card. After the machine has been on for some time, 10+ hours, suddenly the z axis faults under following error. The machine is sitting static. Z is holding position as a Non-counter balanced Z axis.

 

So Z starts to fall and the machine trips out. The only Error is Z axis following Error. The axis Drive is an allen bradley Ultra 3000 drive running in analog torque mode. The amplifier shows no error.

Using Allen Bradly software and running a trace on the drive, it shows the analog torque command signal dropping to zero. It certainly looks like the DAC output just dropped to zero for no reason. It was quite warm in the panel the aluminum UMAC rack is about 130-140 F .

 

If I restart everything comes back but the next failure happens quit quickly.

 

has there been any problems with the 4axis cards not working correctly?