Hi,
I am experiencing some annoying drawbacks with the possibilities of TIME variables:
* TIME variables cannot be used/interacted with in the HMI. For example, a user cannot enter a custom time delay for an alarm in the HMI. It has to be a number (i.e. in whole seconds), and then converted.
* TIME variables in HMI can _only_ be shown in text dynamics, i.e. not in text fields.
* It is not possible to convert TIME to to any number. Normally I would expect to be able to convert it to an int and get the milisecond value of the variable. It is strange that it works the other way around; I can convert an integer of miliseconds into a TIME variable.
What is the reason for these limitations?
Hi fluxmodel,
I suppose it simply prevents you cramping a 32bit TIME into a 16bit INT 
It works when using a TO_DINT conversion.
Cheers
DivisionByzero
Hi fluxmodel,</p>I suppose it simply prevents you cramping a 32bit TIME into a 16bit INT ;)</p>It works when using a TO_DINT conversion. </p>[https://forum.plcnext-community.net/uploads/JD0QGRM3MRDV/image.png</a></p>Cheers</p>DivisionByzero</p>
Hm… Good point. I have never given any thought to the size of a TIME variable.
Anyways, I am confused that it works with DINT, as the conversion table in the help file (Home → Function/Function Block Reference → Implicit Data Type Conversion) don’t list is as a possibility:
image.png
Apologies, I pasted the wrong image in my previous post. That was showing the implicit conversion.
Here are the list with both implicit and explicit conversion possibilities:
(In the help file at Home → Function/Function Block Reference → IEC 61131-3 Functions and Function Blocks → Data Type Conversion)
Maybe the table is outdated because the help for TO_DINT shows TIME as a valid input
Cheers
