I want to map a Physical IO Terminal State (e.g. EL1809) InfoData -> State which shows up as a UINT datatype. However when I try to create a link, this tag is unable to find the tag in the plc. Is there something I'm missing here?

Inputs:
iArray (Any type of array, integer array, char array, bool array etc..)

Outputs:
isArray(Bool)
nLowerBound(Int)
nUpperBound(Int)
nNumberOfElements(Int)

If the input is an array, isArrayshould be True and other outputs should be lower bound, upper bound and the elements count in the array. 
If the input is not an array, nLowerBound and nUpperBound should be -1 and isArray should be False,  nNumberOfElements should be 0.  

Examples: 

Happy coding! 

Inputs:
Enable (Bool)
Array1 (Any type of array, integer array, char array etc..)
Array2 (Any type of array, integer array, char array etc..)

Outputs:
ArrayDataMatch (Bool)
ArraySizeMismatch (Bool)
ArrayTypeMismatch (Bool)

If the arrays' data match, ArrayDataMatch should be True.
If the arrays' size don't match, ArraySizeMismatch should be True.
If the arrays are different types, ArrayTypeMismatch should be True.

Happy coding! 💻

Happy coding! 😊 

• On time
• Off time
• Pause time
• Total time
• Number of Flashing Before Pausing 

A sample function block and the output can be seen below: 

 fbCustomFlash(
            bStart:= bStart, 
            tOnDuration:= T#2s, 
            tOffDuration:= T#1s, 
            tPauseDuration:= T#4s, 
            tTotalDuration:= T#20s, 
            nBlinkCountBeforePause:= 3, 
            bOut=> bPWM);

Sample output for the values below: 

• On time = 1s
• Off time = 500ms
• Pause time = 3s
• Total time = 35s
• Number of Flashing Before Pausing = 4

Happy coding! 

Some items of note:

• Uses a GVL 2-d array and the block checks bounds.  Dimensions on the array can be changed to whatever size as long as the visualization is updated
• Uses latching HMI buttons to set the direction in X or Y (-1 or +1 makes cursor go left or right)
• Setup variables initializes and resets all variables on bootup
• Option for autoscrolling where the 'snake' will continue in a loop around the border of the screen
• Option for enable crashes let me disable the end of game when debugging the initial programming
• Option for scan time on a slider permits the game speed to change
• High score and current score display

Other arcade games that I wrote at this time were something similar to the PONG/tennis game as well as the stacking block tower.  All of these were running on an HMI for a machine that was being built and I had the opportunity to use a joystick that was required for normal machine operation - much more fun than clicking on the visualization screen!

• When a car gets close to the traffic light, if the light is red, it will stop.
• If the light is yellow, it will slow down and continue as long as the the red light is not on. After passing the traffic light, it will continue at regular speed. 
• If the light is green, it will continue at regular speed. 
• Check your distance with other cars to avoid collision.

The sample application can be seen below. We have used 3 cars for this simulation. Since the application has followed the object oriented programming style, it is quite easy to add additional cars into this simulation. 

-Max 15 flowing LEDs are allowed. 

-Start button is used to start the program when all the settings are provided by the user. 

-If a user enter 5s for the slowest time and set the speed bar to 0%, it will take LEDs to flow 5s from one end to the other. 

-If a user enter 1s for the fastest time and set the speed bar to 100%, it will take LEDs to flow 1s from one end to the other. 

A running program can be seen in the video below. You need to write the PLC logic for this HMI, but you are welcome to develop the HMI program as well. 

Share your implementation with the community! Good luck and happy coding! 😊 

Sample:

My challenge would be to carry out a project that performs addition, subtraction and division operations under OOP object-oriented programming, in which interfaces, polymorphism, etc... must be used,
The philosophy or the approach should not be changed to make it an interesting challenge and with a little difficulty in assuming concepts, it is also intended that it remain as a fluid programming that is the one that is most similar to the way we speak and the most natural...
I attach some photos so that we all follow the same structure and definition... I hope you have fun coding and looking for the solution to the exposed challenge...