[ 
https://issues.apache.org/jira/browse/PLC4X-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049709#comment-17049709
 ] 

Łukasz Dywicki edited comment on PLC4X-181 at 3/2/20 10:20 PM:
---------------------------------------------------------------

Hey [~cgarcia], since java 8 there is official {{java.time}} package which is 
intended to handle both date and time related operations. There are types which 
can represent DATE ({{LocalDate}}), TIME_OF_DAY ({{LocalTime}} or 
{{OffsetTime}}), with support for timezones if necessary.
TIME as an amount (such as cycle time) and not point in the time can be 
reported using {{Duration}} (nanos up to days) or {{Period}} (days, months, 
years).

Best,
Łukasz


was (Author: splatch):
Hey [~cgarcia], since java 8 there is official `java.time` package which is 
intended to handle both date and time related operations. There are types which 
can represent DATE (`LocalDate`), TIME_OF_DAY (`LocalTime` or `OffsetTime`), 
with support for timezones if necessary.
TIME as an amount (such as cycle time) and not point in the time can be 
reported using `Duration` (nanos up to days) or `Period` (days, months, years).

Best,
Łukasz

> Reading / Writing of basic types PLC S7.
> ----------------------------------------
>
>                 Key: PLC4X-181
>                 URL: https://issues.apache.org/jira/browse/PLC4X-181
>             Project: Apache PLC4X
>          Issue Type: Improvement
>          Components: Driver-S7
>            Reporter: César García
>            Priority: Major
>             Fix For: 0.6.1
>
>
> The reading / writing of the basic S7 data types is corrected. In this 
> version it focuses on the S7-300 and S7-400 devices.
> It also corrects the handling of arrangements associated with the basic types.
> In the case of complex variables of type time (DATE, TIME, TIME__OF_DAY, 
> etc.), since there is no direct equivalence in Java, its conversion is left 
> at the user application level.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to