24HR Time in Compactlogix

[industrial 951]

Hello all and Happy New Year... almost

I need to get the 24 hr time in a compactlogix PLC (Version 33). I am having a hard time with the data conversion of GSV and Wall Clock time. Here is what I have so far...

DTOS - Convert Hour (INT) to String
DTOS - Convert Minute (INT) to String
CONCAT- Concatenate Hour and Minute String
STOD - Convert from String to DINT

Seems to work however it is truncating the zeros, for example, 0702 = 72, 1001 = 101.

Does anyone have a better solution for this? Would this be easier in Structured Text?

 

[TheWaterboy]

as integers (Hours * 100 + Minutes) then DTOS that value.

 

[drbitboy]

as integers 10000 + (Hours * 100 + Minutes) then DTOS that value, then extract the last four characters

e.g.

ADD PLC_Clock[3] 100 temporary_int
MUL temporary_int 100 temporary_int
ADD temporary_int PLC_Clock[4] temporary_int
DTOS temporary_int hhmm_string
MID hhmm_string 4 2 hhmm_string

​

 

[chelton]

....
I need to get the 24 hr time in a compactlogix PLC (Version 33).
.....

What data type/radix do you want to represent the 24hr time String / integer?
Is this for display on HMI or for other time calculations?

 

[industrial 951]

An Integer value. this is for an operator set point to select the time frame that a pump is allowed to run.

 

[padees]

You might be able to do something silly like this...


Happy New Year!

 

[lostcontrol]

as integers (Hours * 100 + Minutes) then DTOS that value.

This is by far the best way to do what you are after .

 

[padees]

I guess I didn't read it carefully.


I don't know, but if I wanted a pump to run for x hours and x minutes, I would just use integers.


The only strings I like are associated with bikinis and cheese. LOL


Have a good one!

 

[chelton]

I would keep the hours/minutes as separate integers. Makes everything else easier, comparisons against the RTC etc.

 

[padees]

That mess I posted above was from 2019. I had to do 3 shifts of start of shift, 1st break, lunch break, 2nd break, end of shift's. Operator had to poke a few things on the Red Lion Graphite to track.


I can tell you that the PLC wall clock in a 5380 is more accurate than the Red Lion G15 clock.


I don't know if they ever did sync these to a master.

 

[lostcontrol]

I would keep the hours/minutes as separate integers. Makes everything else easier, comparisons against the RTC etc.

Perhaps, but it is sometimes more intuitive for the operator to enter the time SP in that format.
For me, I prefer 24hr format in a single word. Just makes it easier for readability

 

[drbitboy]

as integers (Hours * 100 + Minutes) then DTOS that value.

Looking at the code in Post #1, if INT Time24Hr is the goal, then the DTOS is not even needed.

 

[chelton]

Perhaps, but it is sometimes more intuitive for the operator to enter the time SP in that format.
For me, I prefer 24hr format in a single word. Just makes it easier for readability

If the number is in Hex/BCD maybe. In decimal clamping the value entered or incrementing/decrementing becomes more difficult. How do you prevent invalid numbers like 173 or 265 from being entered? Or do you have to enter the minutes and hours separately?

 

[industrial 951]

Thanks for all the answered guys! I think post 2 is going to work for me.