![]() ![]() ![]() ![]() ![]() ![]() |
||
![]() |
||
![]() ![]() ![]() ![]() This board is for PLC Related Q&A ONLY. Please DON'T use it for advertising, etc. |
||
![]()
|
New Here? Please read this important info!!!
![]() |
#1 |
Member
|
3 Dimensional DINT and alarm values
Will the same trigger value in different dimensions create multiple alarms
Capture 1.PNG Thank you for your time and attention
__________________
"When nothing is going right, go left." "Even a fish wouldn't get into trouble if it kept its mouth shut." (I should probably look into this) |
![]() |
![]() |
#2 |
Member
![]() ![]() Join Date: Jan 2011
Location: NC
Posts: 1,118
|
Looking at your Imagine it seems you have an array with a length of 3 not a 3 dimensional Tag. A 3D tag would be Tagname[n,n,n] an Array with a length of 3 is Tagname[0], Tagname[1] and Tagname[2]. The imagine shown of the alarms will not activate because you have the trigger at the bit level. (Tagname[n].x) The only value a bit can have is 1 or 0.
Now if you have set your trigger to the DINT tagname in the trigger tab and also selected trigger type as bits then the numbers in the trigger column would correspond to the bits in the DINT -1. Like the last one in your imagine. tagname[2].27 = 28th bit. But your trigger only needs to be Tagname[2] The 28 in the next column is what infers Tagname[2].27 |
![]() |
![]() |
#3 |
Member
|
I might not be thinking about this correctly. I assumed "Array Dimensions" and the selection of the "3" mean this array would have three dimensions
My question should have been Would {Alarms_Motors(0).1} having a trigger value of 2 Conflict with {Alarm_Motors(1).1}having a trigger value of 2 Or are the separated by the dimension Capture 3.PNG Capture 4.PNG
__________________
"When nothing is going right, go left." "Even a fish wouldn't get into trouble if it kept its mouth shut." (I should probably look into this) Last edited by John Morris; December 3rd, 2019 at 11:14 AM. |
![]() |
![]() |
#4 |
Member
|
Each DINT and BIT of an array is independent of all the others
The value of one DINT or status of one BIT will not have any effect of the rest of the array. An array is just a nice way to group values together in a logical method.
__________________
Never underestimate the quality of idiots that will be running your machines ![]() http://aabeck.com |
![]() |
![]() |
#5 |
Member
|
Thank you for the confirmation
__________________
"When nothing is going right, go left." "Even a fish wouldn't get into trouble if it kept its mouth shut." (I should probably look into this) |
![]() |
![]() |
#6 | |
Member
![]() ![]() Join Date: Jan 2011
Location: NC
Posts: 1,118
|
Quote:
To use those values then your Trigger should be set up like this. Trigger Type should be set to Bit. Alarm Motors.PNG Your Message file would look like this. Alarm Motors1.PNG If you use {[ShortCut]Alarm_Motors[0].1 then the trigger value will have to be 1 to show the alarm message not 2. Last edited by cwal61; December 3rd, 2019 at 12:56 PM. Reason: typo |
|
![]() |
![]() |
#7 |
Member
|
I appreciate the clarification
Thank you
__________________
"When nothing is going right, go left." "Even a fish wouldn't get into trouble if it kept its mouth shut." (I should probably look into this) |
![]() |
![]() |
#8 |
Lifetime Supporting Member
![]() ![]() Join Date: Jun 2012
Location: Australia
Posts: 3,013
|
Just to clarify - this is not a three-dimensional array. It's a one-dimensional array with three elements. Which, as others have already clarified for you - are completely independent entities.
A one dimensional array might be called "Array_1D" and have a data type of DINT[4]. This then gives you four DINT's - Array_1D[0] through Array_1D[3]. You might represent it like this: Code:
Array_1D[0] Array_1D[1] Array_1D[2] Array_1D[3] Code:
Array_2D[0,0] Array_2D[1,0] Array_2D[2,0] Array_2D[3,0] Array_2D[0,1] Array_2D[1,1] Array_2D[2,1] Array_2D[3,1] Array_2D[0,2] Array_2D[1,2] Array_2D[2,2] Array_2D[3,2] ![]() |
![]() |
![]() |
#9 |
Member
|
Understood ASF, I appreciate your explanation.
FYI, be closer to your neck of the woods in the near future, have a start up of a new facility in New Zealand first quarter next year.
__________________
"When nothing is going right, go left." "Even a fish wouldn't get into trouble if it kept its mouth shut." (I should probably look into this) |
![]() |
![]() |
#10 |
Lifetime Supporting Member
![]() ![]() Join Date: Jun 2012
Location: Australia
Posts: 3,013
|
Ah, Kiwiland is nice that time of year. You really should pop your head in next door while you're here, it's only a three hour flight!
|
![]() |
![]() |
Bookmarks |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Factory Talk ME Alarm message as String text followed by a tag value (DINT) | kidtron123 | LIVE PLC Questions And Answers | 9 | February 19th, 2019 07:47 PM |
PV+1000 Program conversion to Compact logix | ian.smith7 | LIVE PLC Questions And Answers | 15 | January 25th, 2018 06:15 AM |
AdvancedHMI project example | timryder | LIVE PLC Questions And Answers | 23 | August 22nd, 2017 10:17 AM |
FTView ME Alarm Bug | arkansascontrols | LIVE PLC Questions And Answers | 4 | February 14th, 2016 04:43 PM |
Alarm Prevention on Powerup | Ken Roach | LIVE PLC Questions And Answers | 5 | June 8th, 2013 08:27 PM |