User Defined Datatype UDT Tutorial - Explanation, Usage Examples & Custom Definition in RSLogix 5000

User Defined Data Type [UDT] Tutorial - Explanation, Usage, Examples & Custom Definition in RSLogix 5000
Visit SolisPLC.com for more Tutorials, Information & connect with the Community
User Defined Datatypes consume space on a controller. Therefore, you need to think strategically before combining your data in this manner. From a practical sense, this means that you don't want to include too much data which will not be used in your program. It is also important to make sure that the application for which you're using this data will actually need all those placeholders.
To illustrate the above principle with an example, let's consider a simple pump system. This system consists of inputs, outputs & operational tags. Critical inputs could be "start", "stop", "fault reset". Outputs we'd like to know about the system are "Status", "Faulted", "Running", "Speed", etc. Internal operation tags could be anything which will be used in programming the structure of the system. Using the bits we've covered above along with a few extra ones for programming the internal operation makes a lot of sense. We can define a UDT which will contain BOOLs, INTs, REALs as well as several arrays of undefined tags to accommodate the operational data.
An improper way to use a UDT would be to utilize it for a system which is extremely large such as an entire plant. Although you may get away with defining it as such, you will never be able to reapply such a UDT as opposed to our pump system above. It can be exported and imported into the next program which will use the UDT. It's also not advised to apply a UDT for an entire machine even if it will be built multiple times. In fact, try to restrict UDT usage to small systems which exist in any field: motors, pumps, conveyors, tanks, boilers, etc.
Full Tutorial: TBD
Check out my Udemy Cognex Class & Save! Click the link below or enter the coupon code “SOLISYTCOGNEXPROMO” to get the class for only 10$!
www.udemy.com/cognex-in-sight-machine-vision-industrial-development-scada/?couponCode=COGNEXLAUNCHPROMO
Find us on social media:
Web: solisplc.com/
Forum: solisplc.com/forum/
LinkedIn: www.linkedin.com/company/solisplc/
Facebook: SolisPLC
Instagram: solisplc
Twitter: Solis_PLC
Other Cool Content:
Cognex InSight Vision System - Job Change EtherNet IP CompactLogix Rockwell PLC RSLogix Studio 5000
kzbin.info/www/bejne/e6rbaYCrms6Xldk
RSLogix 500, RSLogix 500 Emulate & RSLinx Free Download from Rockwell Automation - PLC Programming
kzbin.info/www/bejne/jZjMo3Znba5ji6M
HMI Fundamentals - PanelView Plus Allen Bradley Terminal IP Settings for EtherNet Connectivity PLC
kzbin.info/www/bejne/mV7Vkp6miqyNlZI
HMI / PLC Fundamentals - Syncing & Sending PLC Time to HMI Terminal Mode Programming RSLogix 5000
kzbin.info/www/bejne/fYirfaOug9Wemqc
HMI / PLC Fundamentals - Linking Studio 5000 Tags to a PanelView Plus 1000 HMI Terminal Tutorial
kzbin.info/www/bejne/Z3yTinlnm9SrjM0
PLC Programming FOR Instruction - Logical FOR Loop Ladder Logic RSLogix Studio 5000 Example Tutorial
kzbin.info/www/bejne/lZnGc5Vnr8ukrbc
PLC Programming BSR Instruction - Bit Shift Right Register Ladder Logic RSLogix Studio 5000 Example
kzbin.info/www/bejne/iJ3ScpljfJhmh5o
Relevant Search Terms
rslogix udt, udt rslogix 5000, studio 5000 udt, rslogix 5000 user defined data type, rslogix udt example, user defined data type, user defined type

[@sabiopolackpolack7573]

Motor1.Running laching on rung zero should be XIC. I love watching your videos I would have more contact with you sir.

[@abdulrhmantammor5154]

Thank you for the great content!

[@SolisPLC]

Glad you enjoy it!

[@darcyfunk]

Thank you!

[@atharvajoshi3631]

I am very thankful to you..

[@ceilingwalker1]

THANK YOU!!!!!!

[@adhavtejashri]

rockwell structured text error in String UDT is invalid data type: argument must match parameter

[@gerardosanchez5396]

What is the difference between the following: DDT - Derived Data Type DFB - Derived Function Block UDT - User-defined Type

[@ardaarsen]

oh man I literally watched all the videos on KZbin. I still have no clue how to port my function blocks from Tia Portal and Codesys. Inputs, Outputs, Statics, Routines.. addressing way different. I had a colleauge moving back from USA, he said RSlogix was way different than European counterparts. Back then I called him bs sob...Now I see what he really meant..

[@brooksnelson7870]

I have a question. I have been working on a project. We are using analog lasers to measure a surface as a periodic task. We look at an analog input, scale the input, fill an array using a FFU,FFL, average the array, then push to a parameter. Currently we were using one but now we are looking at multiple on one machine. Should I create a UDT, or an AOI?I was thinking then when we have a piece of equipment that needs, say 2 lasers we import package, enable those input/outputs. But if another machine has 1 or N lasers, we could easily implement. The laser logic periodic task is 10 lines of ladder for one laser. The logic is the same for the others but would fill a different part of the array elements. Any suggestions is helpful. Thanks

[@SolisPLC]

That's a great question. The way to think about UDTs and AOIs is that their purpose is completely separate. Some applications require neither, one, the other or both. The UDT is used to contain data. If you have multiple machines of the same type, I would definitely create a UDT that would contain each element of that machine. For example, you could have measurement1, measurement2, the array into which you use the FFU and FFL as well as other parameters of that machine. The AOI on the other hand is used to encapsulate logic. In other words, if you need to create 10 rungs of logic that will do the calculations of your averages, arrays, etc, AND will use them multiple times (for each machine), it's a good idea to create an AOI. The advantage of that is that you can easily copy/paste this logic and only change the call on the AOI. The drawback is that you need to download to the PLC if you want to make changes as well as most technicians and mechanics not wanting to troubleshoot AOIs. In conclusion, I would say to keep things simple, but do experiment with an AOI when you commission the units and see how it goes. On the same note, if there's an opportunity to help you with this install or the PLC code, reach out to me directly @ [e-mail]

[@brooksnelson7870]

@@SolisPLC I sent you an email, hope you have some time to look over it.

[@vishalwangle7761]

I have question for you. In the example you used instruction are motor1.start,motor 1.stop. I understood that for start and stop you made a udt but from where did you take that motor1 tag?

[@awesomeoftheshizy]

He created it @6:30 when he right clicked the and chose New "motor". Because he chose the Data Type: UDT_ExamplePLCClass This class has subtypes (.STart, .Stop, .Running, .Speed_RPM) So now Motor1 also has these subtypes. the same way that "Timer1" has subtypes .DN or .EN

[@ardenburns8718]

Did i miss the part where the UDT is tied to a real world IO?

[@cobelali]

In this example, when Motor1.Timer[0].DN bit is energized, it can be used to control a coil that is tied to an output.

[@thiefgold0913]

Is a UDT a good way to go for recipe/variety setup.

[@SolisPLC]

Definitely. I've worked on multiple recipe handling systems and in every case, the recipe was a UDT that would contain ingredients, parameters settings for instrumentation, tank levels, temperatures, etc. It's a great way to combine all the tags into a single structure and make the code much more streamlined.