Armadillo852

MrPLC Member
 View profile  See their activity

  • Content count

    378

  • Joined

  • Last visited

Posts posted by Armadillo852

  4. Posted

    Hey All,

       I have an issue trying to get my indirect addressing working. Not sure what I am doing wrong. Hopefully something simple.

    What I want to do is copy data from one dint to another based off of counter position.

    I will always read in the source at the same word, but want the data written to a certain word based off of a counter value.

    I have a single rfid reader that will read, but I need to read 16 different rfid's and dump them into 1 place. Then i will transfer all 16 rfid's read into another word all at once. 

    Here is my code. What am i missing here?

     

     

  8. Posted

    On 7/16/2020 at 1:54 PM, Kris Salmons said:

    Thank you all so much for the helpful suggestions!

    So far, we have verified the subroutine instruction is not controlled by MCR or other latching logic.  There are no cross-references or duplicated tags for the base tag or the MOV instruction's destination.  We double-checked the base tag's scope but I had not considered the MOV function's destination tag scope.  Tomorrow (7-17) is our next opportunity to troubleshoot the problem and we'll give it a shot.  Again, I appreciate the feedback!

    Am I missing something here? You say the base tag has no cross-references or duplicate tags. How is this bit being controlled? Are you just toggling this bit in the PLC? What exactly is turning this bit on?

    1 person likes this

  11. Posted

    On 5/17/2020 at 10:20 PM, ElectronGuru said:

    Great video, Tim, but it left me with a question way off this topic. I left the RS500 world a few years ago for ControlLogix, and the CLX processors have only recently updated to have 64 bit words. Specifically, the L8 is the only CLX controller (that I know of) with a 64 bit word, the LINT. The thing that jumped out at me immediately in your video was the L data file in the RS500 program. A quick search showed me two SLC 5/05 controllers that are 64 bit. Who knew? I didn't! Anyway, just for fun I created a new RS500 project using an L553 and still can't find L as an available data file type. I'm using RS500 Pro, V12. Where can I find that L data file?!

    From the manual here:   https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm003_-en-p.pdf    Page 852.

     

    These processors use a LINT as well:   LINT data type is a 64-bit integer. The LINT data type can be used in numerous instructions on Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, or GuardLogix 5580 controller however the LINT data type cannot be used in most instructions on CompactLogix 5370, ControlLogix 5570, Compact GuardLogix 5370, GuardLogix 5570 controllers. Consider the following when using LINT data type on CompactLogix 5370, ControlLogix 5570, Compact GuardLogix 5370, GuardLogix 5570 controllers.

     

    Tip: LINTs can only be used with copy (COP, CPS) instructions. They are used with the CST/WallClock Time attribute, time synchronization and Add-On Instructions. You cannot add, subtract, multiply, or divide this tag type.

    1 person likes this

  15. Posted · Edited by Armadillo852

    If you are not using any safe torque off wiring, make sure you have a jumper installed into S1, S2, and S+. This will bypass the integrated safe torque off feature.

     

    Also, if not using the safe torque off, the drive must be set at the default settings. I.E. right out of the box states.

  23. Posted

    On 1/6/2020 at 0:44 PM, Vertex said:

    Its version 17. I have every version up to 32 on my computer. Not sure why it is opening in service edition like I said. I verified that customer didnt send me file from a service version PC, and made sure they didnt have source code locks on, but can't seem to come up with solution. 

    Understood. But version 16 has a few issues that effect other versions. If you do not have the latest version of 16, I would start there. I have seen version 16.0 do some weird things.