Pulse and Direction Input Power Brick AC

[abeard]

We've recently started using Power Brick ACs as a replacement for our Power PMAC chassis. One feature we rely upon is the ability to configure an encoder input in 'pulse and direction' mode. We use this to feed a 32kHz pulse train from a timing card for use as an external time base. We're having difficulty getting this feature working on our Power Brick. Questions:

a) Is pulse-and-direction CHA *input* supported on the Power Brick AC?

b) Does the setup differ from the Power PMAC and if so how?

Thanks,

~Andy

[abeard]

An additional question is what is the best way to verify that this is working properly. Would polling the value of ServoCapt be sufficient or should we verify functionality by viewing the output of a virtual motor tied to the encoder so we can view the encoder table processed value?

 

We've recently started using Power Brick ACs as a replacement for our Power PMAC chassis. One feature we rely upon is the ability to configure an encoder input in 'pulse and direction' mode. We use this to feed a 32kHz pulse train from a timing card for use as an external time base. We're having difficulty getting this feature working on our Power Brick. Questions:

a) Is pulse-and-direction CHA *input* supported on the Power Brick AC?

b) Does the setup differ from the Power PMAC and if so how?

Thanks,

~Andy

[steve.milici]

This is definitely supported in the Power Brick AC – it is equivalent to the ACC-24E3 in all aspects (electrical and programming – pinout is different though).

 

You should monitor the following to see the result of the pulse decode – these are in order of their PMAC “food chain” of processing:

Motor[x].Pos (virtual motor position, should target the following ECT entry: Motor[x].pEnc = EncTable[n].a)

EncTable[n].DeltaPos (time base value)

EncTable[n].PrevEnc (processed raw counter value)

Gate3.Chan[j].ServoCapt (raw counter value, should be the target of this ECT entry: EncTable[n].pEnc = Gate3.Chan[j].ServoCapt.a)