n and report a warning in case this is not as expected.
Chris
Outlook for Android <https://aka.ms/ghei36> herunterladen
--
*From:* Otto Fowler
*Sent:* Thursday, December 13, 2018 4:43:34 AM
*To:* dev@plc4x.apache.org; Christofer Dutz
*Subject:* Re: Versioni
From: Otto Fowler
Sent: Thursday, December 13, 2018 4:43:34 AM
To: dev@plc4x.apache.org; Christofer Dutz
Subject: Re: Versioning for Datablocks
What exactly are you trying to protect from happening?
On December 12, 2018 at 14:19:11, Christofer Dutz
(christofer.d...@c-ware.de&l
rladen
From: Julian Feinauer
Sent: Wednesday, December 12, 2018 5:31:34 PM
To: dev@plc4x.apache.org
Subject: Re: Versioning for Datablocks
Hey all,
We spontaneously digged into it with wireshark and have generated a .cap to
evaluate.
The request is a "Get Block Info"
special address syntax for that usecase
and not add some new API functions.
Chris
Outlook for Android<https://aka.ms/ghei36> herunterladen
From: Julian Feinauer
Sent: Wednesday, December 12, 2018 5:31:34 PM
To: dev@plc4x.apache.org
Subject: Re: Versioni
Hey all,
We spontaneously digged into it with wireshark and have generated a .cap to
evaluate.
The request is a "Get Block Info" Request and the Response contains: "Code
timestamp", "Interface timestamp" and "Block checksum".
I will think about how or where we could implement this as I'm really
Hi all,
I had (have, in fact) a very interesting Discussion with an PLC programmer
about S7.
He told me that there is the possibility (or Siemens does that…) to read out
timestamps of “last changed” for each datablock.
This could be very interesting for us to avoid situations where someone chang
