Productivity 1000, BTD (AB) equivalent

[the_msp]

I am rewriting a program for AB CPX, for SMC electric actuators. I have used both IO-Link and Ethernet/IP with AB CPX, and the most helpful instruction for these programs is the BTD (think that's what it's called, Bit Field Distribute).

Is there a similar instruction in Productivity 1000?

 

[sparkie]

You might take a look at one of these:


https://www.automationdirect.com/productivity/software/help


Go to "Instructions" and "Data Handling" and there are quite a few bit operations there, including logical operations and bit shifts / rotates / etc.


Here is a nice little overview of them all:
https://www.automationdirect.com/productivity/software/instructions


Sorry, it's kind of generic, but I'm not familiar with a BTD instruction.

 

[the_msp]

Thanks, AD CPD (Copy Data) looks close, here is the AB BTD:

https://www.manualslib.com/manual/1292352/Allen-Bradley-Logix5000.html?page=303

 

[sparkie]

I don't think there is a one-to-one correlation with instructions. It looks like you would use a LOGW with a SFR instruction. Use AND and for your bit mask put a 1 in each space of the bit mask that you want to copy from the other address. Then shift those bits into the address you want to shift them into with SFR.

 

[the_msp]

Thanks... having a go at this over the weekend...

 

[drbitboy]

The [Swap Byte] instructions are unnecessary, at least on that rung.

All of that can be done with simple AND and DIV (or bit-shift) instructions.

Should take no more than about half an hour to re-write that rung to make it simpler and easy to port.
_

 

[the_msp]

Well, it works Brian

 

[drbitboy]

Well, it works Brian

Well, you want it work in an environment that does not have BTD, so its current form is irrelevant.

​

 

[the_msp]

Thanks Brian, will give that a go.

Have attempted to add the drive, uploaded EDS OK,

not sure on some of the settings for assembly etc,

anyone good on productivity E/IP know how this translates from AB into AD?

http://www.plctalk.net/qanda/attachment.php?attachmentid=62927&d=1661406385

 

[the_msp]

...I put it as what I thought it should be, I'm getting error 0x127 in my Status Description, I have a rung to enable the drive and make it online, and I am getting TCP connected back as an input

 

[sparkie]

https://youtu.be/FXDNHxY4W9o


Give that a go. I haven't use EIP on AD, but that should get you started.

 

[the_msp]

Thanks... that helped narrow down the error code;

This error is returned when the Originator to Target (Output data) size specified in the Forward Open does not match what is in the Target. Consult the documentation of the Adapter device to verify the required size. Note that if the Run/Idle header is requested, it will add 4 additional bytes and must be accounted for in the Forward Open calculation. The Productivity Suite CPU always requires the Run/Idle header so if the option doesn't exist in the Scanner device, you must add an additional 4 bytes to the O -> T (Output) setup. Some devices may publish the size that they are looking for as an additional attribute (Unsigned Integer 16 value) of the Extended Error Code. An array can be defined for this field in order to view the extended error code attributes.

So through trial and error my connection status is now: Success

For anyone else following along trying to do this;

T->O Unicast, don't include header, Integer 16 Bit unsigned 1D array with 36 elements, then number of elements 18 at the bottom
O->T same as above just inclue header

 

[nickzzz]

Thanks... that helped narrow down the error code;



So through trial and error my connection status is now: Success

For anyone else following along trying to do this;

T->O Unicast, don't include header, Integer 16 Bit unsigned 1D array with 36 elements, then number of elements 18 at the bottom
O->T same as above just inclue header

I'm doing the exactly same thing. Thanks for your sharing. Saved a lot of time for me.

 

[the_msp]

No worries, actually in the end this was much simpler to do in AD than in AB. No BTD equivalent is needed.